Auto‑Batching – Detailed Overview

How to Use This Guide

This guide is structured so that readers can start with the high‑level concept of Auto‑Batching (Sections 1–4), then dive into practical usage (Sections 5–6), configuration details (Section 7), comparisons and best practices (Sections 8–9), and finally a summary. New schedulers can read straight through, while experienced users can jump directly to the section they need.

1. What Auto‑Batching Does

Auto‑Batching uses a defined rule set – Schedule Templates – to automatically organize production items. All logic is deterministic:

1. Select template
2. Group items by Production Group
3. Check capacity (quantity or factor)
4. Assign to batch
5. Overflow to next like batch when required
6. Display full batch distribution in Scheduled Items

Auto‑Batching typically completes in under 10 seconds, regardless of item count.

Requirements at a Glance:

• A valid Schedule Template
• Production Groups on all relevant parts
• Items must be eligible and unscheduled
• The schedule must not be finalized
• Date-driven filters must include the items

2. Schedule Templates – Foundation of Auto‑Batching

Schedule Templates are the core engine behind Auto‑Batching. They define the rules that determine how items are grouped, where they are assigned, and in what order they flow through production. Auto‑Batching cannot function without a Schedule Template, and the quality of the template directly impacts scheduling speed, efficiency, and accuracy.

A Schedule Template acts as a repeatable batching blueprint, enabling plants to run consistent daily or weekly schedules without recreating batch structure from scratch.

2.1 What Schedule Templates Do

A Schedule Template defines the complete structure of a schedule, including:

• Which batches exist (e.g., Batch 1, Batch 2, Batch 3)
• Which Production Groups belong in each batch (e.g., Double‑Hung → Batch 1, Casement → Batch 2)
• Capacity limits for each batch (quantity‑based or scheduling‑factor‑based)
• The order in which batches should appear (sequence)
• How items should be sorted within each batch (Part → Size → Color, etc.)

These rules ensure Auto‑Batching applies the same logic every time, no matter who is scheduling or how many items are involved.

2.2 Why Schedule Templates Matter

1. They eliminate repetitive manual batching

Without a template, a scheduler must manually create batches, assign Production Groups, and manage capacity every day. With a template, Auto‑Batching predefines all of this and applies it instantly.

2. They enforce production alignment

Templates mirror how the production floor actually runs. Each line, shift, or cell has known:

• Product mixes
• Cycle times
• Capacity limits
• Physical staging constraints

Templates guarantee that schedules created in FeneVision match these real-world parameters.

3. They ensure cross‑scheduler consistency

A plant may have multiple schedulers or rotating staff. Templates ensure all users create schedules with:

• The same batch layout
• The same production group grouping
• The same sort order
• The same capacity flows

This eliminates human variability.

4. They prevent accidental overload

Capacity limits within templates ensure batches never exceed the limits defined for the line’s capabilities, especially when using Scheduling Factor for high‑complexity items.

5. They enable fast, reliable Auto‑Batching

A well‑designed template allows Auto‑Batching to organize hundreds of items in seconds. Poor or incomplete templates lead to:

• Overflow where it shouldn’t occur
• Misassigned Production Groups
• Large manual cleanup workloads

2.3 Components of a Schedule Template

The template is composed of several interrelated rule sets.

1. Batch Definitions

Each batch is a discrete production grouping.

Examples:

• Batch 1: DOUBLE‑HUNG
• Batch 2: CASEMENT
• Batch 3: AWNING

Templates may include many batches depending on the line.

2. Production Groups

Each batch is assigned one or more Production Groups that determine which items belong there.

Examples:

• DOUBLE‑HUNG
• CASEMENT
• AWNING
• DOOR

Auto‑Batching uses these associations to place items in the correct batch.

3. Capacity Type

Two options:

• Line Item Quantity (capacity based on item count)
• Scheduling Factor (capacity based on item complexity)

Capacity is one of the most influential aspects of batching behavior.

4. Capacity Limit

Defines the maximum load per batch:

• For quantity: total number of units
• For factor-based: total factor points allowed

This ensures predictable workflow and prevents bottlenecks.

5. Sort Fields

Sort fields determine how items are ordered within the batch.

Typical sort sequence:

• Part
• Color
• Size

Sorting affects:

• Operator organization
• Machine file output
• Work route grouping

6. Batch Sequence Order

Defines how batches appear in the Scheduling UI and how Auto‑Batching processes them.

Examples:

• 1 → 2 → 3
• LINE1 → LINE2 → LINE3

Sequence order matters when items overflow into subsequent like batches.

2.4 How Schedule Templates Interact with Auto‑Batching

During Auto‑Batching, FeneVision reads the template in a deterministic sequence:

1. Identify the template assigned to the schedule
2. Read the batch list in sequence order
3. For each batch:
   • Gather all items belonging to assigned Production Groups
   • Apply capacity rules
   • Assign items until capacity is exhausted
4. Overflow remaining items into the next like batch
5. Apply sort fields within each batch
6. Display final batch structure in Scheduled Items

Because the logic is deterministic, Auto‑Batching produces the same result every time unless the underlying data (Production Groups, Scheduling Factors, item selection) changes.

2.5 Accessing Schedule Templates in FeneVision

To open the Schedule Template editor:

1. Go to Production → Scheduling
2. Right‑click in the Schedule Batch Display area
3. Select Schedule Templates

This displays all templates available to the user along with their batch structures and group assignments.

2.6 Relationship Between Templates and Daily Scheduling

Schedule Templates are designed for repeatability. Most plants create:

• Daily templates (standard production days)
• Line‑specific templates (line 1 vs line 2)
• Specialty templates (remake day, shapes only, end‑of‑day cleanup)
• Exception templates (rush‑order influx days, labor-limited days)

Templates reflect standard operating procedure. Schedulers then use Auto‑Batch to apply that SOP consistently.

2.7 How Template Quality Impacts Auto‑Batching

The template determines whether Auto‑Batching produces:

• Clean, balanced batches
• Predictable overflow behavior
• Proper product grouping
• Correct sequencing and sort order
• Accurate workload distribution

Poor template design often results in:

• Incorrect batch assignment
• Excessive overflow
• Manual cleanup work
• Daily schedule variability
• Production inefficiencies

This is why later sections (especially Section 7 and Section 9) focus on best practices and configuration techniques.

3. Production Groups

Production Groups are the organizational backbone of Auto‑Batching. They define what type of product each manufactured line item represents, and they determine where those items belong when Auto‑Batching assigns them to batches. Without reliable Production Group values, Auto‑Batching cannot correctly group items or follow the template rules.

Production Groups must be carefully configured, consistently maintained, and mapped correctly across all products to ensure predictable scheduling behavior.

3.1 What Production Groups Are

A Production Group is a label applied to each ordered part or product that identifies its manufacturing category.

Examples of common Production Groups include:

• DOUBLE‑HUNG
• CASEMENT
• AWNING
• SLIDER
• DOOR
• SHAPES / SPECIALTY

These categories reflect how the production floor operates. For example, Double‑Hung units may flow through a different assembly line or require different hardware than Casements or Doors.

A Production Group can be:

• A fixed value, such as “DOUBLE‑HUNG,” selected in Part Setup
• A scripted expression that returns different groups based on size, options, or other conditions

3.2 Why Production Groups Are Critical for Auto‑Batching

Auto‑Batching uses Production Groups as the primary grouping driver when assigning items to batches.

During Auto‑Batching, FeneVision:

1. Reads each item’s Production Group
2. Groups all items by these values
3. Places items into the batch(es) assigned to that Production Group within the active Schedule Template
4. Honors batch capacity while placing items
5. Moves remaining items into the next like batch if overflow occurs

Production Groups therefore determine:

• Which batch an item belongs to
• How overflow is handled
• How consistently similar products stay together
• How predictable and efficient batch production flow will be

If Production Groups are inconsistent, missing, or logically incorrect, Auto‑Batching will misgroup items - or fail to batch them at all.

3.3 Where Production Groups Are Defined

Production Groups are assigned to parts in the Product Setup area:

Setup → Products → Parts → Production Group (Each ordered part has this field.)

For more complex cases, scripting allows dynamic Production Group assignment.

This is commonly used for:

• Combined units
• Mulled assemblies
• Casements that shift to AWNING categories based on direction
• Items where color, size or other options affect the production process

When a Production Group is updated in Setup, FeneVision provides an option to re-evaluate existing unscheduled items so Pending items reflect the new grouping.

3.4 Examples of Production Group Behavior

Simple example:

• All DOUBLE‑HUNG parts → Batch 1
• All CASEMENT parts → Batch 2

Auto‑Batching groups by these Production Groups and fills batches accordingly.

Overflow example:

If DOUBLE‑HUNG has batches:

• Batch 1 DH
• Batch 4 DH (overflow)

And Batch 1’s capacity is exceeded:

• First items fill Batch 1
• Additional DH items flow automatically into Batch 4

Special cases using scripted groups:

A scripted Production Group might return:

• CS‑LARGE for casements over 64"
• PW‑SMALL for picture windows under 36"
• CUSTOM‑ARCH for radius shapes

These map to different batches in the Schedule Template.

3.5 How Production Groups Interact With Schedule Templates

Schedule Templates assign each Production Group to one or more batches.

Example mapping inside a template:

Auto‑Batching uses these mappings to decide where to place items.
If a Production Group is not present in the template, Auto‑Batching cannot place those items.

For best results:

• All Production Groups used in your product catalog should appear in the template.
• Each Production Group should appear only once per template to avoid ambiguous assignment.
• Overflow batches should be created intentionally rather than relying on accidental spillover.

3.6 Operational Implications of Production Group Quality

Accurate Production Groups lead to:

• Predictable batch structure
• Faster scheduling
• Fewer manual corrections
• Improved line balancing
• Cleaner sorting for downstream machine files
• Reduced shop‑floor confusion

Poor Production Group hygiene causes:

• Misassigned items
• Unexpected overflow
• Mixed product types in the same batch
• Large manual adjustments
• Increased defects or delays in assembly

Because Production Groups drive Auto‑Batching more than any other single factor, they should be reviewed periodically - particularly after new product configuration work.

3.7 Best Practices for Production Groups

Based on documented behavior and field experience:

1. Keep Production Groups simple and intuitive

Names should match production line terminology. Avoid cryptic abbreviations unless they are standard plant language.

2. Maintain one Production Group per part

A part should map to exactly one logical Production Group.

3. Use scripting for dynamic cases

Scripting is ideal when:

• Option combinations change production flow
• Size determines which line runs the product
• Complex assemblies need special handling

4. Validate after configuration changes

Whenever product configuration changes:

• Re-check Production Group values
• Ensure templates include all active Production Groups

5. Audit Production Group usage quarterly

This ensures:

• No obsolete groups remain
• New products are properly categorized
• Templates stay aligned with actual production

3.8 Summary

Production Groups are the categorization engine behind Auto‑Batching. They tell FeneVision what each product is and where it belongs in the batch structure. When configured cleanly, Production Groups create clear and consistent production flow. When misconfigured, they create chaos that no template can fix.

4. Capacity Types

Auto‑Batching supports two capacity models:

A. Line Item Quantity

• 1 item = 1 unit of capacity
• Ideal for standard products with similar cycle times

B. Scheduling Factor

• Capacity = Σ (Quantity × Scheduling Factor per item)
• Ideal where build times vary significantly across product types
• Used in operations with:
  • Continuous-frame combined windows
  • Complex shapes
  • Mulled assemblies
  • High‑option configurations

Where defined: Setup → Products → Parts → Scheduling Factor (Details tab)

Example Scenario: When to Use Scheduling Factor (Best Practice)

Scenario Overview

A manufacturer produces both standard windows and more complex continuous‑frame combination units. Even though both count as “one unit” in order quantity, the combination unit takes 4–5× longer to build.
Relying on simple quantity capacity would overload the line. Using Scheduling Factor correctly models the true workload.

Product Types on the Same Line

Template Setup

Batch 1 Capacity: 500 "factor" points

Why?

• ~100 standard windows
• OR ~20–25 complex combination units
• OR a balanced mixture of both

This is much closer to actual labor time than unit count.

Example Day’s Orders

Total Load: 390 factors

All items fit comfortably into Batch 1 (capacity = 500).

If another 15 continuous-frame units (67.5 factors) arrive:
New total = 457.5 → still fits.

Add another five (22.5): 480 → fits.

Add five more: 502.5 → exceeds capacity → Auto‑Batching overflows the remainder into Batch 2.

Why This Works So Well

Using Scheduling Factor:

• Prevents massive overloads where “215 units” hides the real workload
• Keeps each batch aligned with real production time
• Ensures mix of simple + complex product does not unintentionally delay a shift
• Provides predictable throughput
• Keeps line balance consistent for operators

5. Running Auto‑Batching (Workflow)

Auto‑Batching can be triggered in several different locations inside the Scheduling screen. The correct method depends on whether you want to batch orders, selected items, or the entire schedule.

Step 1: Create or Open a Schedule

1. Go to Production → Scheduling.
2. Select the Production Location.
3. In the Schedule Batch Display area, right‑click and choose Add Schedule.
4. Enter the Target Release Date and select a Schedule Template.
5. The schedule loads with empty batches based on the template.

Step 2: Review Available Items

Items appear in one or both of these grids:

• Available Items (Orders) grid. This groups items by order.
• Available Items (Items) grid. This groups items by individual line items.

Items must have a valid Production Group, valid dates, and must not already be scheduled.

Step 3: Triggering Auto‑Batching

Auto‑Batching can be triggered in three different ways. Each option serves a different purpose.

Method 1: Auto‑Batch Selected Orders (Orders Grid)

Use this when you want to batch all items within entire customer orders.

1. Select one or more orders in the Available Items (Orders) grid.
2. Right‑click and choose Auto‑Batch Selected Orders.
3. The system evaluates all items in the selected orders and assigns them to batches.

Best used when:

• You want to batch several full orders quickly.
• The day’s workload has low variability.

Method 2: Auto‑Batch Selected Items (Items Grid)

Use this when you only want to batch specific items instead of all items from an order.

1. Select one or more items in the Available Items (Items) grid.
2. Right‑click and choose Auto‑Batch Selected Items.
3. Only the chosen items are evaluated and assigned to batches.

Best used when:

• You want to schedule only part of an order.
• You are splitting orders across multiple days.
• You must schedule specific items that need priority.

Method 3: Auto‑Batch All Items on the Schedule (Schedule Detail View)

This option evaluates every item currently assigned to the schedule. It removes all previous batch assignments and reassigns everything using the Schedule Template.

1. In the Scheduled Items grid at the bottom of the screen, right‑click anywhere.
2. Select Auto‑Batch All Items on This Schedule.
3. The system clears existing assignments and reassigns all items to batches according to template rules.

Best used when:

• You want to re‑batch after manual adjustments.
• You have added new items to the schedule and want a clean redistribution.
• You want the template rules applied exactly as configured.

This is the most comprehensive Auto‑Batch action because it evaluates the entire schedule at once.

Step 4: Review Scheduled Items

After Auto‑Batching is triggered:

• Items appear in the Scheduled Items grid under their assigned batches.
• Batch capacity usage is visible.
• Overflow behavior is reflected if applicable.
• You can make manual adjustments by moving, unbatching, or changing quantities.

Step 5: Finalize and Release

When the schedule is ready:

1. Finalize the schedule.
2. Release it to production.
3. Machine files, production reports, and other downstream processes can proceed normally.

6. Manual Adjustments and Re‑Batching

After Auto‑Batching assigns items to batches, users still have full control over adjustments. FeneVision allows several types of manual edits, along with multiple ways to re‑batch items so that changes remain aligned with template rules. This section provides a clear breakdown of each available action and when to use it.

6.1 Manual Adjustments Users Can Make

Manual adjustments are available from the Scheduled Items grid. These actions allow schedulers to refine or override auto‑assigned values.

Unbatching Items

Use this when an item should be removed from its assigned batch and returned to Available Items.

How to unbatch:

1. Right‑click the item in the Scheduled Items grid.
2. Select Unbatch Item.
3. The item appears back in the Available Items grid for reprocessing.

Common uses:

• Removing items accidentally scheduled.
• Moving items to a different day.
• Replacing items with corrected versions.

Note: Manual adjustments override Auto‑Batching only temporarily. If a re‑batch operation is performed later, all manual moves, quantity changes, or sequence edits may be replaced unless you use selective re‑batching.

Moving Items Between Batches

Use this when the system’s assignment is correct but you want a different batch placement for operational reasons.

How to move an item:

1. Right‑click the item.
2. Select Batch Item.
3. Choose the target batch from the list.

Common uses:

• Adjusting for hardware availability.
• Balancing operator workload.
• Reordering items for workflow staging.

Changing Scheduled Quantity

Some orders are partially scheduled. Users can reduce the scheduled quantity without unbatching the rest of the order.

How to adjust quantity:

1. In the Scheduled Items grid, locate the Schedule Qty field.
2. Edit the quantity directly.

Common uses:

• Splitting a large order across multiple days.
• Scheduling only what materials can support for the shift.

Editing Batch Properties

Batch properties can be modified when a user needs different capacity or description values.

Examples of editable properties:

• Batch name or description
• Capacity values
• Sequence order

This is typically done when the template is used as a starting point but specific daily conditions require updates.

6.2 Re‑Batching Options

Re‑Batching is very flexible. FeneVision supports several re‑batching workflows depending on what changed.

Method 1: Re‑Batch Selected Items

Use this when a few items need to be realigned with template rules without affecting other assignments.

How to re‑batch only certain items:

1. Highlight one or more items in Scheduled Items.
2. Right‑click and select Auto‑Batch Selected Items.
3. The system reassigns only the selected items based on the active template.

Common uses:

• Partially scheduled items changed after initial batching.
• Items were manually moved incorrectly.
• A group of items received updated Production Group or date values.

Method 2: Re‑Batch All Items on the Schedule (Full Re‑Batch)

This option resets the entire schedule and reapplies the template to all assigned items.

How to run a full re‑batch:

1. Right‑click anywhere in the Scheduled Items grid.
2. Select Auto‑Batch All Items on This Schedule.
3. FeneVision clears all current assignments and rebuilds the batch structure using template rules.

What the system does:

• All existing batch placements are removed.
• All unscheduled items for the schedule are evaluated.
• All items are reassigned based on Production Groups and capacity.
• Overflows are handled automatically according to the template.

Common uses:

• Large manual changes have created inconsistencies.
• The schedule’s flow needs to be “reset” to match template logic.
• New orders were added after initial batching.
• Users want a clean and consistent schedule before release.

This method guarantees the closest possible match to template configuration.

Method 3: Unbatch First, Then Re‑Batch

Some scenarios require the user to unbatch items first, then run Auto‑Batch with a clear state.

Use this when:

• Item attributes have changed (Production Group, Scheduling Factor, dates).
• Items were previously manually forced into non‑template batches.
• You want to ensure no stale data remains in the assignment.

Process:

1. Unbatch affected items.
2. Trigger Auto‑Batch using any of the methods in Section 5.

6.3 When Users Should Re‑Batch vs. Manually Adjust

Use Manual Adjustments When:

• Only a few items need small corrections.
• Capacity is fine but the sequence should change.
• The scheduler understands operational constraints requiring overrides.

Use Re‑Batching When:

• Many items were manually moved and the schedule is inconsistent.
• New orders were added after initial batching.
• Production Groups or Scheduling Factor values were updated.
• You need the schedule to reflect template rules exactly.
• Operators report the batch distribution looks unbalanced.

6.4 Impact of Re‑Batching on Production Planning

Re‑Batching ensures:

• Accurate workload distribution
• Updated capacity consumption
• Correct Production Group grouping
• Minimal manual interpretation errors
• Better downstream performance for machine files, staging, or assembly sequencing

Schedulers should review the schedule after any re‑batch to ensure operational feasibility.

7. Schedule Template Configuration

Schedule Templates define exactly how Auto‑Batching organizes items into batches. They are the blueprint for batch structure, capacity rules, production group assignments, and sort order. This section provides a complete, detailed walk‑through of how to create, modify, and maintain Schedule Templates, along with best‑practice guidance to ensure templates reflect real production needs.

7.1 Accessing Schedule Templates

You can access the Schedule Template editor directly from the Scheduling screen.

How to open the template window:

1. Go to Production → Scheduling.
2. In the Schedule Batch Display area, right‑click.
3. Select Schedule Templates.

The template window opens and displays two main panels:

• Template List (left side)
• Batch Template Definition (right side, with detail grids)

7.2 Template List (Left Panel)

This section controls which templates exist and which template is the default when creating a new schedule.

Adding a new template

1. Click the next empty row.
2. Type the name of your new template (for example: Daily Main Line, Premium Line, High‑Volume, Screens‑Only).
3. (Optional) Check System to make it available to all users.
4. (Optional) Check Default to make it the automatically selected template when a new schedule is added.

Best‑practice guidance

• Use clear template names that match real‑world production lines or shifts.
• Keep only one Default template to avoid confusion for new schedulers.
• Maintain separate templates for unusual workflows (rush orders, end‑of‑day consolidation, remake‑only schedules).

7.3 Batch Template Definition (Right Panel)

This is where you define the individual batches within a template. Each row represents one batch.

Batch Columns Explained

Best practices

• Keep batches in logical production order (e.g., DH → CS → AWN).
• Leave slight buffer capacity to avoid constant overflow into a next batch.
• Use Scheduling Factor for lines where complexity varies significantly.

7.4 Production Group Assignment for Each Batch

Production Groups tell Auto‑Batching which types of products belong in a batch.

Where Production Groups are assigned

In the lower section of the template screen, you will see a grid listing all Production Groups.

To assign production groups to a batch:

1. Click the batch you want to edit.
2. Check the box next to each Production Group that belongs in that batch.
3. Use the arrow buttons to reorder the group assignment within the batch.

How Auto‑Batching uses these assignments

• Auto‑Batch first groups items by Production Group.
• It then places those groups into the batch where that Production Group is assigned.
• If capacity is reached, remaining items go to the next like batch (for example, Batch 1 DH → Batch 4 DH).

Best practices

• Assign only groups that truly run on that line.
• Maintain separate templates when the production mix changes heavily.
• Put the highest‑volume groups first in sequencing.

7.5 Sort Field Configuration (Lower‑Right Panel)

Sort fields determine how items appear within each batch. This affects how production staff see items and how machine files may order them.

To configure sort order:

1. Click the batch or batch area you are editing.
2. In the Sort Fields list, choose a sort column, such as:
   • Part
   • Size
   • Color
   • Options
3. Add multiple sort fields to create a multi‑tier sort (for example: Part → Size → Color).
4. Use arrow buttons to set the sort priority.

Best practices

• Primary sort should always be the most meaningful production category (typically Part).
• Use Size or Color as secondary fields for more predictable shop‑floor organization.
• Do not overuse sort fields; keep it simple unless the line requires strict patterns.

7.6 Saving and Using a Template

Once your template is configured:

1. Click OK to save the template.
2. The template becomes selectable when adding a new schedule.
3. When a scheduler creates a schedule using this template, all batch structures, production groups, capacities, and sort fields apply automatically.

7.7 Example: Daily Schedule Template

Template Name: Daily Schedule
System: Enabled
Default: Enabled

Batches:

• Batch 1
  • Description: DOUBLE‑HUNG
  • Type: Line Item Quantity
  • Capacity: 100
• Batch 2
  • Description: CASEMENT
  • Type: Line Item Quantity
  • Capacity: 80
• Batch 3
  • Description: AWNING
  • Type: Line Item Quantity
  • Capacity: 60

Production Groups (in order):

1. DOUBLE‑HUNG
2. CASEMENT
3. AWNING

Sort Fields:

1. Part
2. Color
3. Size

7.8 Template Management Best Practices

• Create one template per line or shift. This avoids mixing incompatible products.
• Review templates quarterly. Production patterns change; templates must match real output.
• Use Scheduling Factor for mixed‑complexity lines. Prevents overwhelming a batch with expensive items.
• Document template usage. Each template should include a note explaining when to use it.
• Avoid cloning templates excessively. Too many templates confuses schedulers; maintain a clean list.

8. Comparison: Auto‑Batch vs Manual Batching

Auto‑Batching and manual batching both exist in FeneVision because each method serves different operational needs. This section provides a detailed comparison to help schedulers, production managers, and support teams understand the strengths, limitations, and ideal uses for each approach.

8.1 How the Two Methods Work

Manual Batching

Manual batching is a fully user‑driven process. Schedulers inspect items one by one, determine the correct batch based on product type and capacity, and manually place items into batches.

Characteristics:

• Drag‑and‑drop workflow
• Full user discretion
• All sorting and grouping decisions are made manually
• No automated capacity management beyond user observation

This method is most common in older workflows or organizations that have not standardized Production Groups or Schedule Templates.

Auto‑Batching

Auto‑Batching is a rules‑driven process that uses the active Schedule Template to automatically assign items into batches.

Characteristics:

• Groups items by Production Group
• Fills batches up to capacity limits (quantity‑based or factor‑based)
• Automatically overflows to the next “like” batch when capacity is reached
• Applies sort fields for intra‑batch ordering
• Runs in under 10 seconds, even for large schedules

Auto‑Batching dramatically reduces labor and creates a consistent batching structure.

8.2 Detailed Feature‑Level Comparison

8.3 When to Use Manual Batching

Manual batching is ideal when human judgment is required:

• Rush or hot orders that must be inserted into specific batches
• Same‑day changes that defy template rules
• Special production events such as maintenance windows or partial line operation
• Experimental batches during commissioning of new lines
• Customers with unique or irregular product lines where no stable pattern exists

Manual batching empowers a scheduler to override rules when flexibility is more important than speed or consistency.

8.4 When to Use Auto‑Batching

Auto‑Batching is the preferred method for most scheduling operations, especially when:

• Production follows a recurring daily pattern
• Orders contain high quantities of standardized product types
• A plant needs predictable throughput and load balancing
• The production line relies on consistent product grouping
• Scheduling Factor is required to keep workloads aligned with actual labor time
• Schedulers need to minimize the risk of human error
• The organization wants multi‑scheduler consistency (two users should produce the same batching result)

In nearly all modern FeneVision deployments, Auto‑Batching becomes the primary method once templates are properly configured.

8.5 Combining Both Methods

Many plants find success using both approaches together, rather than choosing one exclusively.

A common hybrid workflow:

1. Use Auto‑Batching to build the full schedule structure quickly.
2. Use manual adjustments to resolve exceptions, like:
   • High‑priority items
   • Material shortages
   • Production constraints
   • Late‑stage rush orders
3. If manual changes become too large, use Re‑Batch All Items on This Schedule to re‑apply template rules cleanly.
4. Finalize.

Why the hybrid method works:

• Auto‑Batch gives consistency and speed.
• Manual adjustments provide operational control and last‑minute flexibility.

This is the most common real‑world approach used by customers with high-volume window production.

8.6 Real‑World Example: Manual vs Auto‑Batching

Suppose a schedule contains:

• 140 double‑hung
• 60 casement
• 20 awning
• 15 special‑order shapes

Manual Batching Day

• Scheduler manually drags items into DH, CS, AW, SHP batches
• Must manually avoid exceeding capacity
• Takes 20–40 minutes
• Sorting within batches may be incomplete
• Risk of accidentally mixing items (e.g., 2 casements in DH batch)

Auto‑Batching Day

• Auto‑Batch groups all items by Production Group
• Applies template capacities and sort fields
• Automatically overflows as needed
• Runs in about 5–10 seconds
• Items appear fully sorted and sequenced
• Scheduler only needs to review or adjust exceptions

This illustrates the practical efficiency gains and consistency Auto‑Batching provides.

8.7 Key Takeaways

• Auto‑Batching is the primary method for most plants due to speed, consistency, and capacity enforcement.
• Manual batching is still necessary for exceptions, urgent changes, and unusual production days.
• Together, the two methods create a flexible, reliable scheduling workflow.
• Templates and Production Group accuracy determine Auto‑Batch success, making Sections 2 and 7 critical to long-term performance.

9. Best Practices

Auto‑Batching delivers the greatest value when Schedule Templates, Production Groups, and operational processes are designed intentionally. The following best practices reflect real-world manufacturing success patterns, consistent FeneVision implementations, and guidance from support, product, and deployment teams.

These recommendations help ensure Auto‑Batching produces predictable, efficient, and production‑ready schedules every time.

9.1 Best Practices for Template Design

A well‑designed Schedule Template is the single biggest driver of Auto‑Batch success. Templates dictate grouping, sequencing, capacity limits, and the logic behind overflow. Poorly designed templates lead to manual corrections, inconsistent production flow, or operator confusion.

1. Create one template per production line or shift

Each line may have different:

• Product mixes
• Cycle times
• Batch size constraints
• Physical staging capacities

Creating line‑specific templates ensures Auto‑Batch aligns with real production constraints.

2. Keep template capacity slightly below actual physical limits

Never set batch capacity equal to the absolute maximum of what a line can produce.

Reason: Leaving margin prevents overloading batches when real‑world tasks (rework, operator interruptions, long-cycle items) appear.

Example: If a line can technically handle 520 factor points, set capacity to ~480–500 to create a buffer.

3. Order production groups by frequency

Place the most common groups first in the template sequence.

Benefits:

• Predictable batch layout
• Better operator familiarity
• Cleaner downstream reporting
• Easier overflow interpretation

It also reduces the number of overflow batches needed on heavy days.

4. Use Scheduling Factor for any line with variable complexity

Templates should use Line Item Quantity only when products are relatively uniform.

Use Scheduling Factor when your product mix includes:

• Continuous-frame combinations
• Mulled or coupled units
• Units with multiple sash or lite groups
• High‑option configurations
• Specialty shapes

This ensures batch capacity reflects real production time, not merely item count.

5. Document template purpose and usage rules

Schedulers may rotate, and clarity is essential for consistent operation.

Good template names include:

• “Main Line – Daily Standard”
• “Specialty Shapes – Wed/Fri Only”
• “Premium Line – Assemblies”
• “Line 2 – DH/CS Mix (Factor-Based)”

Add documentation such as:

• Which orders it is intended for
• Any exceptions
• Which production groups are expected
• Rules for overflow handling

6. Maintain “exception templates”

Sometimes a schedule falls outside the typical pattern.

Examples:

• A large multi‑story order that dominates the day
• Plant maintenance limiting line availability
• Weather impacts on labor
• Short-shift days

Exception templates keep the main template clean and reliable while still giving schedulers necessary flexibility.

9.2 Best Practices for Operational Use

Designing good templates is only half of the equation. The other half is operating Auto‑Batching consistently and efficiently day‑to‑day.

1. Use Auto‑Batching for daily or recurring schedules

If your shop runs predictable daily or weekly cycles, always use Auto‑Batch for those schedules.

This ensures:

• Consistency across days and shifts
• Predictable batch‑to‑batch behavior
• Less human error
• Cleaner reporting and machine file generation

2. Use manual adjustments only for exceptions

If an unexpected constraint arises (material shortage, rush order, operator absence), use manual adjustments sparingly to handle the edge case.

Examples:

• Move a single priority item into an earlier batch
• Remove 2–3 items for material issues
• Shift a batch sequence for operational workflow reasons

The majority of the schedule should still reflect Auto‑Batch template logic.

3. Re‑Batch after significant changes

If the schedule has become messy due to many manual adjustments, the best practice is:

1. Right‑click inside Scheduled Items
2. Choose Auto‑Batch All Items on This Schedule
3. Let FeneVision reflow everything cleanly

This ensures:

• Capacity usage is recalculated
• Overflow rules are reapplied
• Production Groups realign correctly
• Sorting is re‑enforced

4. Keep Production Groups clean and consistent

Production Group accuracy is critical. If Production Groups are incorrect, Auto‑Batch logic becomes unpredictable.

Best practices:

• Audit production groups quarterly
• Avoid one‑off or “junk” Production Groups
• Ensure replacement parts and variants share correct grouping

Better Production Group hygiene means better Auto‑Batch results.

5. Review the schedule before releasing

Even if Auto‑Batching is fully trusted, a scheduler should always perform a basic audit:

Check:

• Any unexpected overflow
• Any extremely large or small batches
• Scheduling Factor load (if applicable)
• Unusual sequencing or sort anomalies
• Items accidentally left in Available Items

A one‑minute review prevents downstream waste.

9.3 Best Practices for Maintaining Stable Systems

Auto‑Batching performance depends on good long‑term maintenance across data, templates, and production processes.

1. Update templates when production flow changes

Production evolves. Templates must evolve with it.

Triggers for updating templates:

• Adding new equipment
• Changing cycle times
• Changing product categories or groups
• Introducing new complex or high‑effort product types
• Significant changes in operator count or shift patterns
• High overflow frequency appearing suddenly

2. Calibrate Scheduling Factors regularly

For factor-based lines, recalibration should occur every 6–12 months.

Use empirical timing:

• Stopwatches
• Operator tracking
• Station timing history
• Productivity metrics

Correct Scheduling Factors lead directly to better batch load balancing.

3. Monitor batch overflow trends

Frequent overflow may indicate:

• Capacity set too low
• Production Groups incorrectly assigned
• High volume of specific product types
• Seasonal demand spikes
• Template misalignment

Adjust templates to reduce overflow patterns if they negatively affect workflow.

4. Align Auto‑Batch processes with downstream modules

Good scheduling helps:

• Machine files
• Saw batching
• Glass optimization
• Work route routing
• Inventory demand forecasting
• Truck loading

Ensure templates are designed with these downstream processes in mind.

5. Train schedulers thoroughly

Schedulers should understand:

• What each template is for
• Which Production Groups map to which batches
• How capacity works (especially factor-based)
• How to make safe manual adjustments
• When to choose re‑batching over manual edits
• How to identify incorrect Production Group assignments
• When and why to escalate production anomalies

A highly trained scheduler minimizes risk and increases throughput.

9.4 Summary of Best Practices

• Design templates intentionally and revise as production evolves.
• Use Scheduling Factor when complexity varies across product types.
• Operate Auto‑Batch daily for consistent schedules.
• Use manual adjustments only when needed.
• Re‑batch when schedules drift too far from template logic.
• Maintain Production Groups rigorously.
• Audit schedules daily before release.
• Train schedulers and document template logic clearly.

These best practices ensure that Auto‑Batching delivers on its full promise: highly efficient, consistent, and accurate production scheduling.

10. Summary

Auto‑Batching transforms production scheduling in FeneVision from a manual, time‑consuming task into a fast, rule‑driven, and highly consistent workflow. By leveraging well‑designed Schedule Templates, reliable Production Groups, and appropriate capacity models, Auto‑Batching organizes all available items into production‑ready batches in seconds.

The system groups items by Production Group, respects batch capacity limits, applies defined sort logic, and automatically manages overflow into subsequent like batches. When templates are maintained and used consistently, this results in predictable batch structures, balanced workload distribution, and smoother downstream processes such as machine files, assembly flow, staging, and trucking.

Manual adjustments remain available for exceptions, rush orders, or operational constraints, and re‑batching options allow users to return to a template‑perfect distribution at any time. Together, Auto‑Batching and FeneVision’s Scheduling tools provide a flexible yet controlled environment that supports both daily recurring schedules and unique production scenarios.

With accurate data, thoughtful template design, and ongoing best‑practice maintenance, Auto‑Batching delivers significant efficiency gains, reduces human error, and helps manufacturers achieve more stable, repeatable, and scalable production scheduling.

11. Glossary

Auto‑Batching A FeneVision scheduling feature that automatically assigns available production items into batches using preconfigured Schedule Templates. It groups items by Production Group, enforces batch capacity, applies sort fields, and handles overflow into like batches. Runs deterministically and typically completes in under 10 seconds.

Schedule Template A reusable configuration that defines how Auto‑Batching organizes items for a given production line or shift. It specifies batch definitions, Production Group assignments, capacity limits, sequence order, and sort fields. Templates must exist before Auto‑Batching can run.

Batch A discrete production grouping within a schedule. Defined in the Schedule Template and used to organize items into logical production sets such as DOUBLE‑HUNG, CASEMENT, etc. Batches include capacity limits and sequence numbers.

Production Group A categorization assigned to each ordered part in Part Setup. Auto‑Batching uses the Production Group field to group items, determine which batch they belong to, and ensure similar product types flow together. Can be a fixed value or a scripted expression.

Batch Capacity The maximum load that can be placed into a batch during Auto‑Batching. Defined per batch in the Schedule Template. Capacity may be measured in:

• Line Item Quantity: 1 unit per item
• Scheduling Factor: item quantity × per‑item complexity factor

Capacity is used only for Auto‑Batching and is not linked to the FeneVision Capacity Planning module.

Scheduling Factor A numeric value on each ordered part representing its production complexity or time requirement. Used when capacity is defined by factor instead of unit count. Auto‑Batch sums factors (Qty × Factor) until the batch capacity is reached.

Overflow Batch / Next Like Batch A subsequent batch assigned the same Production Group(s) and used when the primary batch reaches capacity. Auto‑Batching automatically places remaining items from a Production Group into the next like batch to preserve grouping.

Available Items (Orders) A scheduler grid showing unscheduled orders grouped by order number. Used for Auto‑Batching entire orders.

Available Items (Items) A scheduler grid listing individual unscheduled line items. Used for batching selected items instead of entire orders.

Scheduled Items The grid showing items already placed into batches for the active schedule, whether manually or using Auto‑Batching. Supports manual adjustments like moving items, unbatching, or editing quantities.

Unbatch A manual action that removes an item from its assigned batch and returns it to Available Items for rebatching or rescheduling.

Re‑Batch A process where Auto‑Batching is applied again – either to selected items or to the entire schedule clearing prior assignments and redistributing items according to the Schedule Template rules.

Sequence Order The order in which batches appear in the schedule and are processed during Auto‑Batching. Used to determine overflow direction and visual sequence in the Scheduling UI.

Sort Fields Criteria defined in Schedule Templates that control how items are ordered inside each batch (e.g., Part → Size → Color). Affects shop‑floor organization and downstream machine file sequences.