Target Setting & Calculations

Last updated: June 25, 2026

Target Quantity is a production value that can be enabled in Production > Settings that provides a benchmark for productivity based on the ideal performance a Line can achieve creating a particular product. 

Target is different from Demand in that while Demand represents the planned Production, Target represents what is possible given current circumstance. As such, they will rarely have equivalent values.

The pitch Target Quantity is automatically set by L2L once the pitch is the current pitch (the current date and time fall within the scope of the pitch), and is based on several properties of the pitch:

  1. Active/Inactive

    • Target is only set for Active pitches, as this represents a pitch where production is planned to be performed

  2. Downtime

    • Any downtime experienced within a pitch, automatically calculated by L2L from Dispatches against the Line with a "Down (red)" Impact to Production, is subtracted from the available production minutes as part of the pitch Target Quantity calculation 

      • ex) For 15 minutes of downtime in a 60 minute pitch, a duration of 45 minutes (60 - 15 min) will be used for the Target calculation

  3. Operator Count

    • This is specified on the pitch either through the Operator Count field on the pitch edit modal or is derived by L2L from the Users checked into the Line during the pitch

  4. Actual Product

    • The Actual Product for a pitch is defined either by the Product field on the pitch edit modal or is automatically pulled from the Current Order widget in the Operator Portal when the pitch is saved

  5. Apply Planning Rate to Target: the value for Cycle Time in the Target calculation will vary according to whether this setting is toggled on in Production > Settings

  • Apply Planning Rate to Target not enabled (FALSE)

  • Target = {[Planned Production Time (min) – Production Downtime (min)]*60 (s/min)} / [Ideal Cycle Time (s)] 

  • The Ideal Cycle Time is determined when the pitch is saved and is then used in Target-related calculations for the current pitch.

  • Ideal Cycle Time is defined by

  • Product Order Group Pitch Cycle Time

  • OR Ideal Cycle Time in Line Cycle Time table by

    • Line

    • Product: Actual Product recorded on pitch

  • OR Line Cycle Time in Line Cycle Time table by

    • Line

    • Product: Actual Product recorded on pitch

    • Operator Count: actual Operator Count on pitch

      • Cycle Time for the largest Operator Count that is less than the pitch Planned Operator Count if specific count not identified

      • OR only Cycle Time in the Cycle Times per Operator Count table will be used (when only a single Operator Count and Cycle Time is listed)

  • OR Line Cycle Time in Line Cycle Time table by

    • Line

    • Default Product

    • Operator Count: actual Operator Count on pitch

      • Cycle Time for the largest Operator Count that is less than the pitch Planned Operator Count if specific count not identified

      • OR only Cycle Time in the Cycle Times per Operator Count table will be used (when only a single Operator Count and Cycle Time is listed)

When to use it

  1. High-Efficiency, Automated Lines: For highly predictable, mature, automated lines where deviations from ideal cycle times are rare or strictly treated as a loss.

  2. OEE (Overall Equipment Effectiveness) Benchmarking: When you want to measure true equipment capability and uncover every second of hidden waste (speed losses).

Why to use it

  • Unmasks "Hidden" Speed Losses: If operators are running the line slower than its engineered capability, using the Ideal Cycle Time forces this gap to show up as a performance loss, highlighting coaching or maintenance opportunities.

  • Standardization: Keeps targets completely objective and uninfluenced by fluctuating team performances or historical inefficiencies.

  • Apply Planning Rate to Target enabled (TRUE)

  • Target = {[Planned Production Time (min) – Production Downtime (min)]*60 (s/min)} / [Cycle Time (s)]
     

The cycle time used for the pitch is determined when the pitch is saved and is then used in Target-related calculations for the current pitch.

  • Cycle Time defined by

    Product Order Group Pitch Cycle Time

    OR Build Sequence Cycle Time for active Build Sequence on pitch

    • Cycle Time defined by

    Product Order Group Pitch Cycle Time, when available

    OR Build Sequence Cycle Time for active Build Sequence on pitch

    • OR Line Cycle Time in Line Cycle Time table by

    Line

    Product: Actual Product recorded on pitch

    • Operator Count: actual Operator Count on pitch

    Cycle Time for the largest Operator Count that is less than the pitch Planned Operator Count if specific count not identified

    OR only Cycle Time in the Cycle Times per Operator Count table will be used (when only a single Operator Count and Cycle Time is listed)

    • Planning Rate: if defined for the Line and Product combination

    Cycle Time = Cycle Time by Line, Product (s) / [Planning Rate % /100]

    • OR Line Cycle Time in Line Cycle Time table by

    Line

    Default Product

    • Operator Count: actual Operator Count on pitch

    Cycle Time for the largest Operator Count that is less than the pitch Planned Operator Count if specific count not identified

    OR only Cycle Time in the Cycle Times per Operator Count table will be used (when only a single Operator Count and Cycle Time is listed)

    • Planning Rate: if defined for the Line and Product combination

    Cycle Time = Cycle Time by Line, Product (s) / [Planning Rate % /100]

When to use it

  1. High-Variable or Manual Assembly Lines: Lines that heavily rely on human operators where performance naturally fluctuates due to fatigue, product mix complexity, or learning curves.

  2. New Product Ramp-Ups: If a brand new product is introduced and the team is expected to run at only 70% efficiency during the first month of production.

  3. Scheduling & Materials Planning Alignment: When your production targets must match the realistic commitments made to supply chain planning and logistics.

Why to use it

  1. Boosts Team Morale: Setting an unachievable "ideal" target day after day can demotivate teams. A planning-rate adjusted target gives the shop floor a realistic, motivating goal to chase.

  2. Accurate Schedule Attainment: It prevents the system from projecting unrealistic output numbers, ensuring that downstream processes (like shipping or packaging) are planned around what the line will actually produce under current conditions.

Missing values within the Line Cycle Tables can result in blank Target Quantity values on the Operator Portal