Ridgeway · Operations ScanSynthetic demo

A SAMPLE, WITH THE EVIDENCE OPEN

Ridgeway Operations Scan

Explore a finding, check its assumptions, and follow it back to the records.

Synthetic data. Ridgeway is a fictional operation. Every operating row and cost input in this demo is illustrative. Customer uploads and scans are not available in this public preview.

SYNTHETIC SAMPLE · 90 RECORDS

Planted operational gaps

Thirty days of synthetic production records with deliberately planted downtime and scrap at Mill B. Review supported comparisons with unknown economics.

Financial inputs and additional demand are unknown. Supported operational quantities remain visible; missing economics are not treated as zero.

Selecting an example opens its previously calculated result. The costs example uses the same operating records with a separate assumptions version.

Download this synthetic CSV

YOUR NEXT REVIEW

Where to investigate

Review each comparison, its evidence, and the next checks before deciding what to change. Recovery is unconfirmed; these separate comparisons should not be added.

Measured comparisons: 4 · Needing more data: 4.

Review capability coverage

RECORD QUALITY

Recorded evidence

Source records checked
90
Records with issues
0
Measured comparisons
4

Each comparison uses its own eligible rows. An issue can affect several fields; issue counts must not be added as distinct rows. Ratios use 1 to mean 100%.

CONDITIONAL FINANCIAL SCENARIOS

Largest single modeled recovery scenario

No supported opportunity has all the assumptions required for a financial scenario.

0 priced scenarios · 6 unpriced opportunities.

  • The range ends at the largest single priced scenario; it is not an upper bound on the operation's total opportunity.
  • Related loss scenarios may describe the same output or process, so their financial amounts are not added.
  • The lower bound is zero because realizing recovery has not been demonstrated.
  • Some possible opportunities lack a supported financial model or the required customer assumptions.

Capability coverage

  • Recorded output against target

    Measured · 90 eligible / 0 excluded records

  • Downtime within scheduled time

    Measured · 90 eligible / 0 excluded records

  • Scrap as a share of output

    Measured · 90 eligible / 0 excluded records

  • Recorded changeover duration

    Insufficient data · 0 eligible / 90 excluded records

    Missing fields: Changeover time.

    • The listed fields must be mapped before this capability can be calculated.
  • Recorded cycle time against ideal

    Insufficient data · 0 eligible / 90 excluded records

    Missing fields: Actual cycle time, Ideal cycle time.

    • The listed fields must be mapped before this capability can be calculated.
  • Labor hours per output unit

    Measured · 90 eligible / 0 excluded records

  • Overtime as a share of labor hours

    Insufficient data · 0 eligible / 90 excluded records

    Missing fields: Overtime.

    • The listed fields must be mapped before this capability can be calculated.
  • Ideal production time within the schedule

    Insufficient data · 0 eligible / 90 excluded records

    Missing fields: Ideal cycle time.

    • The listed fields must be mapped before this capability can be calculated.

Assembly · Bracket

Recorded output against target

Measured from eligible records · descriptive evidence

15 eligible records · 0 excluded records · 15 dates

2026-01-02 through 2026-01-30

Recorded total units
4500 units
Sum of total units across eligible records in this work center and product scope.
Recorded target units
4500 units
Sum of recorded targets across eligible records in this scope.
Target attainment ratio
1 ratio
Total eligible output divided by total eligible target; a ratio of 1 means the recorded target was met.
Net gap below target
0 units
The larger of zero and total eligible target minus total eligible output. Over-target output offsets shortfall within this scope.

Evidence and limitations

  • At least five eligible records cover at least three distinct dates; these are engineering review thresholds.
  • No exclusion, repeated-scope ambiguity, or dominant record was detected by the checks used for this group.
  • The calculation describes the submitted eligible records and does not extrapolate to unobserved production.
  • This comparison does not establish why the observed result occurred.
  • Target attainment compares recorded total output with target; it does not silently substitute good or saleable output.
  • The source target has not been independently checked for feasibility or commercial demand.

Source fields: Date, Work center, Product, Total units, Target units.

Example source rows: 7, 13, 19, 25, 31. These are traceable examples, not the full calculation input.

Next investigation

  1. Confirm what the production target represents and whether target and recorded gross output cover the same product and period.
  2. Confirm additional customer demand, contribution margin and practical recoverability before treating a target gap as a scenario for additional sales.

Back to scan investigation

Assembly · Housing

Recorded output against target

Measured from eligible records · descriptive evidence

15 eligible records · 0 excluded records · 15 dates

2026-01-01 through 2026-01-29

Recorded total units
3000 units
Sum of total units across eligible records in this work center and product scope.
Recorded target units
3000 units
Sum of recorded targets across eligible records in this scope.
Target attainment ratio
1 ratio
Total eligible output divided by total eligible target; a ratio of 1 means the recorded target was met.
Net gap below target
0 units
The larger of zero and total eligible target minus total eligible output. Over-target output offsets shortfall within this scope.

Evidence and limitations

  • At least five eligible records cover at least three distinct dates; these are engineering review thresholds.
  • No exclusion, repeated-scope ambiguity, or dominant record was detected by the checks used for this group.
  • The calculation describes the submitted eligible records and does not extrapolate to unobserved production.
  • This comparison does not establish why the observed result occurred.
  • Target attainment compares recorded total output with target; it does not silently substitute good or saleable output.
  • The source target has not been independently checked for feasibility or commercial demand.

Source fields: Date, Work center, Product, Total units, Target units.

Example source rows: 4, 10, 16, 22, 28. These are traceable examples, not the full calculation input.

Next investigation

  1. Confirm what the production target represents and whether target and recorded gross output cover the same product and period.
  2. Confirm additional customer demand, contribution margin and practical recoverability before treating a target gap as a scenario for additional sales.

Back to scan investigation

Mill A · Bracket

Recorded output against target

Measured from eligible records · descriptive evidence

15 eligible records · 0 excluded records · 15 dates

2026-01-02 through 2026-01-30

Recorded total units
4500 units
Sum of total units across eligible records in this work center and product scope.
Recorded target units
4500 units
Sum of recorded targets across eligible records in this scope.
Target attainment ratio
1 ratio
Total eligible output divided by total eligible target; a ratio of 1 means the recorded target was met.
Net gap below target
0 units
The larger of zero and total eligible target minus total eligible output. Over-target output offsets shortfall within this scope.

Evidence and limitations

  • At least five eligible records cover at least three distinct dates; these are engineering review thresholds.
  • No exclusion, repeated-scope ambiguity, or dominant record was detected by the checks used for this group.
  • The calculation describes the submitted eligible records and does not extrapolate to unobserved production.
  • This comparison does not establish why the observed result occurred.
  • Target attainment compares recorded total output with target; it does not silently substitute good or saleable output.
  • The source target has not been independently checked for feasibility or commercial demand.

Source fields: Date, Work center, Product, Total units, Target units.

Example source rows: 5, 11, 17, 23, 29. These are traceable examples, not the full calculation input.

Next investigation

  1. Confirm what the production target represents and whether target and recorded gross output cover the same product and period.
  2. Confirm additional customer demand, contribution margin and practical recoverability before treating a target gap as a scenario for additional sales.

Back to scan investigation

Mill A · Housing

Recorded output against target

Measured from eligible records · descriptive evidence

15 eligible records · 0 excluded records · 15 dates

2026-01-01 through 2026-01-29

Recorded total units
3000 units
Sum of total units across eligible records in this work center and product scope.
Recorded target units
3000 units
Sum of recorded targets across eligible records in this scope.
Target attainment ratio
1 ratio
Total eligible output divided by total eligible target; a ratio of 1 means the recorded target was met.
Net gap below target
0 units
The larger of zero and total eligible target minus total eligible output. Over-target output offsets shortfall within this scope.

Evidence and limitations

  • At least five eligible records cover at least three distinct dates; these are engineering review thresholds.
  • No exclusion, repeated-scope ambiguity, or dominant record was detected by the checks used for this group.
  • The calculation describes the submitted eligible records and does not extrapolate to unobserved production.
  • This comparison does not establish why the observed result occurred.
  • Target attainment compares recorded total output with target; it does not silently substitute good or saleable output.
  • The source target has not been independently checked for feasibility or commercial demand.

Source fields: Date, Work center, Product, Total units, Target units.

Example source rows: 2, 8, 14, 20, 26. These are traceable examples, not the full calculation input.

Next investigation

  1. Confirm what the production target represents and whether target and recorded gross output cover the same product and period.
  2. Confirm additional customer demand, contribution margin and practical recoverability before treating a target gap as a scenario for additional sales.

Back to scan investigation

Mill B · Bracket

Recorded output against target

Measured from eligible records · descriptive evidence

15 eligible records · 0 excluded records · 15 dates

2026-01-02 through 2026-01-30

Recorded total units
3930 units
Sum of total units across eligible records in this work center and product scope.
Recorded target units
4500 units
Sum of recorded targets across eligible records in this scope.
Target attainment ratio
0.873333333333 ratio
Total eligible output divided by total eligible target; a ratio of 1 means the recorded target was met.
Net gap below target
570 units
The larger of zero and total eligible target minus total eligible output. Over-target output offsets shortfall within this scope.

Possible recovery to investigate

570 units in this recorded scope. Recovery is unconfirmed.

The larger of zero and total eligible target minus total eligible output. Over-target output offsets shortfall within this scope.

No financial estimate is attached to this opportunity.

Evidence and limitations

  • At least five eligible records cover at least three distinct dates; these are engineering review thresholds.
  • No exclusion, repeated-scope ambiguity, or dominant record was detected by the checks used for this group.
  • The calculation describes the submitted eligible records and does not extrapolate to unobserved production.
  • This comparison does not establish why the observed result occurred.
  • Target attainment compares recorded total output with target; it does not silently substitute good or saleable output.
  • The source target has not been independently checked for feasibility or commercial demand.
  • A customer-provided currency is required to express this scenario financially.
  • A customer-provided recovery fraction is required; Atlas does not guess recoverability.
  • A customer-provided contribution margin per additional unit is required for the target-gap scenario.
  • Additional customer demand has not been confirmed, so target-gap output is not priced as additional sales.

Source fields: Date, Work center, Product, Total units, Target units.

Example source rows: 6, 12, 18, 24, 30. These are traceable examples, not the full calculation input.

Next investigation

  1. Confirm what the production target represents and whether target and recorded gross output cover the same product and period.
  2. Confirm additional customer demand, contribution margin and practical recoverability before treating a target gap as a scenario for additional sales.

Back to scan investigation

Mill B · Housing

Recorded output against target

Measured from eligible records · descriptive evidence

15 eligible records · 0 excluded records · 15 dates

2026-01-01 through 2026-01-29

Recorded total units
2625 units
Sum of total units across eligible records in this work center and product scope.
Recorded target units
3000 units
Sum of recorded targets across eligible records in this scope.
Target attainment ratio
0.875 ratio
Total eligible output divided by total eligible target; a ratio of 1 means the recorded target was met.
Net gap below target
375 units
The larger of zero and total eligible target minus total eligible output. Over-target output offsets shortfall within this scope.

Possible recovery to investigate

375 units in this recorded scope. Recovery is unconfirmed.

The larger of zero and total eligible target minus total eligible output. Over-target output offsets shortfall within this scope.

No financial estimate is attached to this opportunity.

Evidence and limitations

  • At least five eligible records cover at least three distinct dates; these are engineering review thresholds.
  • No exclusion, repeated-scope ambiguity, or dominant record was detected by the checks used for this group.
  • The calculation describes the submitted eligible records and does not extrapolate to unobserved production.
  • This comparison does not establish why the observed result occurred.
  • Target attainment compares recorded total output with target; it does not silently substitute good or saleable output.
  • The source target has not been independently checked for feasibility or commercial demand.
  • A customer-provided currency is required to express this scenario financially.
  • A customer-provided recovery fraction is required; Atlas does not guess recoverability.
  • A customer-provided contribution margin per additional unit is required for the target-gap scenario.
  • Additional customer demand has not been confirmed, so target-gap output is not priced as additional sales.

Source fields: Date, Work center, Product, Total units, Target units.

Example source rows: 3, 9, 15, 21, 27. These are traceable examples, not the full calculation input.

Next investigation

  1. Confirm what the production target represents and whether target and recorded gross output cover the same product and period.
  2. Confirm additional customer demand, contribution margin and practical recoverability before treating a target gap as a scenario for additional sales.

Back to scan investigation

Assembly · Bracket

Downtime within scheduled time

Measured from eligible records · descriptive evidence

15 eligible records · 0 excluded records · 15 dates

2026-01-02 through 2026-01-30

Recorded downtime minutes
0 minutes
Sum of recorded downtime minutes across eligible records in this scope.
Recorded scheduled minutes
7200 minutes
Sum of scheduled minutes across eligible records after repeated schedule scope has been checked.
Downtime share
0 ratio
Total eligible downtime minutes divided by total eligible scheduled minutes.

Evidence and limitations

  • At least five eligible records cover at least three distinct dates; these are engineering review thresholds.
  • No exclusion, repeated-scope ambiguity, or dominant record was detected by the checks used for this group.
  • The calculation describes the submitted eligible records and does not extrapolate to unobserved production.
  • This comparison does not establish why the observed result occurred.
  • Recorded downtime can include necessary or unavoidable time; its full duration is not established recoverable time.
  • Machine downtime has no confirmed monetary cost basis in this model.

Source fields: Date, Work center, Product, Downtime, Scheduled time.

Example source rows: 7, 13, 19, 25, 31. These are traceable examples, not the full calculation input.

Next investigation

  1. Review the downtime events, their recorded reasons and scheduled time coverage with the people responsible for the process.
  2. Separate necessary stops from time that might be avoidable before planning an intervention. Recorded downtime alone does not establish recoverable time or cost.

Back to scan investigation

Assembly · Housing

Downtime within scheduled time

Measured from eligible records · descriptive evidence

15 eligible records · 0 excluded records · 15 dates

2026-01-01 through 2026-01-29

Recorded downtime minutes
0 minutes
Sum of recorded downtime minutes across eligible records in this scope.
Recorded scheduled minutes
7200 minutes
Sum of scheduled minutes across eligible records after repeated schedule scope has been checked.
Downtime share
0 ratio
Total eligible downtime minutes divided by total eligible scheduled minutes.

Evidence and limitations

  • At least five eligible records cover at least three distinct dates; these are engineering review thresholds.
  • No exclusion, repeated-scope ambiguity, or dominant record was detected by the checks used for this group.
  • The calculation describes the submitted eligible records and does not extrapolate to unobserved production.
  • This comparison does not establish why the observed result occurred.
  • Recorded downtime can include necessary or unavoidable time; its full duration is not established recoverable time.
  • Machine downtime has no confirmed monetary cost basis in this model.

Source fields: Date, Work center, Product, Downtime, Scheduled time.

Example source rows: 4, 10, 16, 22, 28. These are traceable examples, not the full calculation input.

Next investigation

  1. Review the downtime events, their recorded reasons and scheduled time coverage with the people responsible for the process.
  2. Separate necessary stops from time that might be avoidable before planning an intervention. Recorded downtime alone does not establish recoverable time or cost.

Back to scan investigation

Mill A · Bracket

Downtime within scheduled time

Measured from eligible records · descriptive evidence

15 eligible records · 0 excluded records · 15 dates

2026-01-02 through 2026-01-30

Recorded downtime minutes
0 minutes
Sum of recorded downtime minutes across eligible records in this scope.
Recorded scheduled minutes
7200 minutes
Sum of scheduled minutes across eligible records after repeated schedule scope has been checked.
Downtime share
0 ratio
Total eligible downtime minutes divided by total eligible scheduled minutes.

Evidence and limitations

  • At least five eligible records cover at least three distinct dates; these are engineering review thresholds.
  • No exclusion, repeated-scope ambiguity, or dominant record was detected by the checks used for this group.
  • The calculation describes the submitted eligible records and does not extrapolate to unobserved production.
  • This comparison does not establish why the observed result occurred.
  • Recorded downtime can include necessary or unavoidable time; its full duration is not established recoverable time.
  • Machine downtime has no confirmed monetary cost basis in this model.

Source fields: Date, Work center, Product, Downtime, Scheduled time.

Example source rows: 5, 11, 17, 23, 29. These are traceable examples, not the full calculation input.

Next investigation

  1. Review the downtime events, their recorded reasons and scheduled time coverage with the people responsible for the process.
  2. Separate necessary stops from time that might be avoidable before planning an intervention. Recorded downtime alone does not establish recoverable time or cost.

Back to scan investigation

Mill A · Housing

Downtime within scheduled time

Measured from eligible records · descriptive evidence

15 eligible records · 0 excluded records · 15 dates

2026-01-01 through 2026-01-29

Recorded downtime minutes
0 minutes
Sum of recorded downtime minutes across eligible records in this scope.
Recorded scheduled minutes
7200 minutes
Sum of scheduled minutes across eligible records after repeated schedule scope has been checked.
Downtime share
0 ratio
Total eligible downtime minutes divided by total eligible scheduled minutes.

Evidence and limitations

  • At least five eligible records cover at least three distinct dates; these are engineering review thresholds.
  • No exclusion, repeated-scope ambiguity, or dominant record was detected by the checks used for this group.
  • The calculation describes the submitted eligible records and does not extrapolate to unobserved production.
  • This comparison does not establish why the observed result occurred.
  • Recorded downtime can include necessary or unavoidable time; its full duration is not established recoverable time.
  • Machine downtime has no confirmed monetary cost basis in this model.

Source fields: Date, Work center, Product, Downtime, Scheduled time.

Example source rows: 2, 8, 14, 20, 26. These are traceable examples, not the full calculation input.

Next investigation

  1. Review the downtime events, their recorded reasons and scheduled time coverage with the people responsible for the process.
  2. Separate necessary stops from time that might be avoidable before planning an intervention. Recorded downtime alone does not establish recoverable time or cost.

Back to scan investigation

Mill B · Bracket

Downtime within scheduled time

Measured from eligible records · descriptive evidence

15 eligible records · 0 excluded records · 15 dates

2026-01-02 through 2026-01-30

Recorded downtime minutes
900 minutes
Sum of recorded downtime minutes across eligible records in this scope.
Recorded scheduled minutes
7200 minutes
Sum of scheduled minutes across eligible records after repeated schedule scope has been checked.
Downtime share
0.125 ratio
Total eligible downtime minutes divided by total eligible scheduled minutes.

Possible recovery to investigate

900 minutes in this recorded scope. Recovery is unconfirmed.

Sum of recorded downtime minutes across eligible records in this scope.

No financial estimate is attached to this opportunity.

Evidence and limitations

  • At least five eligible records cover at least three distinct dates; these are engineering review thresholds.
  • No exclusion, repeated-scope ambiguity, or dominant record was detected by the checks used for this group.
  • The calculation describes the submitted eligible records and does not extrapolate to unobserved production.
  • This comparison does not establish why the observed result occurred.
  • Recorded downtime can include necessary or unavoidable time; its full duration is not established recoverable time.
  • Machine downtime has no confirmed monetary cost basis in this model.
  • This capability has no supported financial model in the current calculation version.

Source fields: Date, Work center, Product, Downtime, Scheduled time.

Example source rows: 6, 12, 18, 24, 30. These are traceable examples, not the full calculation input.

Next investigation

  1. Review the downtime events, their recorded reasons and scheduled time coverage with the people responsible for the process.
  2. Separate necessary stops from time that might be avoidable before planning an intervention. Recorded downtime alone does not establish recoverable time or cost.

Back to scan investigation

Mill B · Housing

Downtime within scheduled time

Measured from eligible records · descriptive evidence

15 eligible records · 0 excluded records · 15 dates

2026-01-01 through 2026-01-29

Recorded downtime minutes
900 minutes
Sum of recorded downtime minutes across eligible records in this scope.
Recorded scheduled minutes
7200 minutes
Sum of scheduled minutes across eligible records after repeated schedule scope has been checked.
Downtime share
0.125 ratio
Total eligible downtime minutes divided by total eligible scheduled minutes.

Possible recovery to investigate

900 minutes in this recorded scope. Recovery is unconfirmed.

Sum of recorded downtime minutes across eligible records in this scope.

No financial estimate is attached to this opportunity.

Evidence and limitations

  • At least five eligible records cover at least three distinct dates; these are engineering review thresholds.
  • No exclusion, repeated-scope ambiguity, or dominant record was detected by the checks used for this group.
  • The calculation describes the submitted eligible records and does not extrapolate to unobserved production.
  • This comparison does not establish why the observed result occurred.
  • Recorded downtime can include necessary or unavoidable time; its full duration is not established recoverable time.
  • Machine downtime has no confirmed monetary cost basis in this model.
  • This capability has no supported financial model in the current calculation version.

Source fields: Date, Work center, Product, Downtime, Scheduled time.

Example source rows: 3, 9, 15, 21, 27. These are traceable examples, not the full calculation input.

Next investigation

  1. Review the downtime events, their recorded reasons and scheduled time coverage with the people responsible for the process.
  2. Separate necessary stops from time that might be avoidable before planning an intervention. Recorded downtime alone does not establish recoverable time or cost.

Back to scan investigation

Assembly · Bracket

Scrap as a share of output

Measured from eligible records · descriptive evidence

15 eligible records · 0 excluded records · 15 dates

2026-01-02 through 2026-01-30

Recorded scrap units
0 units
Sum of recorded scrap units across eligible records in this scope.
Recorded total units
4500 units
Sum of total units across eligible records in this work center and product scope.
Scrap rate
0 ratio
Total eligible scrap units divided by total eligible output units; this uses output volume as the denominator.

Evidence and limitations

  • At least five eligible records cover at least three distinct dates; these are engineering review thresholds.
  • No exclusion, repeated-scope ambiguity, or dominant record was detected by the checks used for this group.
  • The calculation describes the submitted eligible records and does not extrapolate to unobserved production.
  • This comparison does not establish why the observed result occurred.
  • Scrap counts are paired with output volume and are not used alone to rank different products.

Source fields: Date, Work center, Product, Scrap units, Total units.

Example source rows: 7, 13, 19, 25, 31. These are traceable examples, not the full calculation input.

Next investigation

  1. Review scrap and total output together for the same product and period, and check how rejected, reworked and scrapped units were recorded.
  2. Confirm that the scrap cost applies to this product and which costs could actually be avoided before relying on a financial scenario.

Back to scan investigation

Assembly · Housing

Scrap as a share of output

Measured from eligible records · descriptive evidence

15 eligible records · 0 excluded records · 15 dates

2026-01-01 through 2026-01-29

Recorded scrap units
0 units
Sum of recorded scrap units across eligible records in this scope.
Recorded total units
3000 units
Sum of total units across eligible records in this work center and product scope.
Scrap rate
0 ratio
Total eligible scrap units divided by total eligible output units; this uses output volume as the denominator.

Evidence and limitations

  • At least five eligible records cover at least three distinct dates; these are engineering review thresholds.
  • No exclusion, repeated-scope ambiguity, or dominant record was detected by the checks used for this group.
  • The calculation describes the submitted eligible records and does not extrapolate to unobserved production.
  • This comparison does not establish why the observed result occurred.
  • Scrap counts are paired with output volume and are not used alone to rank different products.

Source fields: Date, Work center, Product, Scrap units, Total units.

Example source rows: 4, 10, 16, 22, 28. These are traceable examples, not the full calculation input.

Next investigation

  1. Review scrap and total output together for the same product and period, and check how rejected, reworked and scrapped units were recorded.
  2. Confirm that the scrap cost applies to this product and which costs could actually be avoided before relying on a financial scenario.

Back to scan investigation

Mill A · Bracket

Scrap as a share of output

Measured from eligible records · descriptive evidence

15 eligible records · 0 excluded records · 15 dates

2026-01-02 through 2026-01-30

Recorded scrap units
0 units
Sum of recorded scrap units across eligible records in this scope.
Recorded total units
4500 units
Sum of total units across eligible records in this work center and product scope.
Scrap rate
0 ratio
Total eligible scrap units divided by total eligible output units; this uses output volume as the denominator.

Evidence and limitations

  • At least five eligible records cover at least three distinct dates; these are engineering review thresholds.
  • No exclusion, repeated-scope ambiguity, or dominant record was detected by the checks used for this group.
  • The calculation describes the submitted eligible records and does not extrapolate to unobserved production.
  • This comparison does not establish why the observed result occurred.
  • Scrap counts are paired with output volume and are not used alone to rank different products.

Source fields: Date, Work center, Product, Scrap units, Total units.

Example source rows: 5, 11, 17, 23, 29. These are traceable examples, not the full calculation input.

Next investigation

  1. Review scrap and total output together for the same product and period, and check how rejected, reworked and scrapped units were recorded.
  2. Confirm that the scrap cost applies to this product and which costs could actually be avoided before relying on a financial scenario.

Back to scan investigation

Mill A · Housing

Scrap as a share of output

Measured from eligible records · descriptive evidence

15 eligible records · 0 excluded records · 15 dates

2026-01-01 through 2026-01-29

Recorded scrap units
0 units
Sum of recorded scrap units across eligible records in this scope.
Recorded total units
3000 units
Sum of total units across eligible records in this work center and product scope.
Scrap rate
0 ratio
Total eligible scrap units divided by total eligible output units; this uses output volume as the denominator.

Evidence and limitations

  • At least five eligible records cover at least three distinct dates; these are engineering review thresholds.
  • No exclusion, repeated-scope ambiguity, or dominant record was detected by the checks used for this group.
  • The calculation describes the submitted eligible records and does not extrapolate to unobserved production.
  • This comparison does not establish why the observed result occurred.
  • Scrap counts are paired with output volume and are not used alone to rank different products.

Source fields: Date, Work center, Product, Scrap units, Total units.

Example source rows: 2, 8, 14, 20, 26. These are traceable examples, not the full calculation input.

Next investigation

  1. Review scrap and total output together for the same product and period, and check how rejected, reworked and scrapped units were recorded.
  2. Confirm that the scrap cost applies to this product and which costs could actually be avoided before relying on a financial scenario.

Back to scan investigation

Mill B · Bracket

Scrap as a share of output

Measured from eligible records · descriptive evidence

15 eligible records · 0 excluded records · 15 dates

2026-01-02 through 2026-01-30

Recorded scrap units
120 units
Sum of recorded scrap units across eligible records in this scope.
Recorded total units
3930 units
Sum of total units across eligible records in this work center and product scope.
Scrap rate
0.030534351145 ratio
Total eligible scrap units divided by total eligible output units; this uses output volume as the denominator.

Possible recovery to investigate

120 units in this recorded scope. Recovery is unconfirmed.

Sum of recorded scrap units across eligible records in this scope.

No financial estimate is attached to this opportunity.

Evidence and limitations

  • At least five eligible records cover at least three distinct dates; these are engineering review thresholds.
  • No exclusion, repeated-scope ambiguity, or dominant record was detected by the checks used for this group.
  • The calculation describes the submitted eligible records and does not extrapolate to unobserved production.
  • This comparison does not establish why the observed result occurred.
  • Scrap counts are paired with output volume and are not used alone to rank different products.
  • A customer-provided currency is required to express this scenario financially.
  • A customer-provided recovery fraction is required; Atlas does not guess recoverability.
  • A customer-provided scrap cost per unit is required to price recorded scrap.

Source fields: Date, Work center, Product, Scrap units, Total units.

Example source rows: 6, 12, 18, 24, 30. These are traceable examples, not the full calculation input.

Next investigation

  1. Review scrap and total output together for the same product and period, and check how rejected, reworked and scrapped units were recorded.
  2. Confirm that the scrap cost applies to this product and which costs could actually be avoided before relying on a financial scenario.

Back to scan investigation

Mill B · Housing

Scrap as a share of output

Measured from eligible records · descriptive evidence

15 eligible records · 0 excluded records · 15 dates

2026-01-01 through 2026-01-29

Recorded scrap units
120 units
Sum of recorded scrap units across eligible records in this scope.
Recorded total units
2625 units
Sum of total units across eligible records in this work center and product scope.
Scrap rate
0.045714285714 ratio
Total eligible scrap units divided by total eligible output units; this uses output volume as the denominator.

Possible recovery to investigate

120 units in this recorded scope. Recovery is unconfirmed.

Sum of recorded scrap units across eligible records in this scope.

No financial estimate is attached to this opportunity.

Evidence and limitations

  • At least five eligible records cover at least three distinct dates; these are engineering review thresholds.
  • No exclusion, repeated-scope ambiguity, or dominant record was detected by the checks used for this group.
  • The calculation describes the submitted eligible records and does not extrapolate to unobserved production.
  • This comparison does not establish why the observed result occurred.
  • Scrap counts are paired with output volume and are not used alone to rank different products.
  • A customer-provided currency is required to express this scenario financially.
  • A customer-provided recovery fraction is required; Atlas does not guess recoverability.
  • A customer-provided scrap cost per unit is required to price recorded scrap.

Source fields: Date, Work center, Product, Scrap units, Total units.

Example source rows: 3, 9, 15, 21, 27. These are traceable examples, not the full calculation input.

Next investigation

  1. Review scrap and total output together for the same product and period, and check how rejected, reworked and scrapped units were recorded.
  2. Confirm that the scrap cost applies to this product and which costs could actually be avoided before relying on a financial scenario.

Back to scan investigation

Assembly · Bracket

Labor hours per output unit

Measured from eligible records · descriptive evidence

15 eligible records · 0 excluded records · 15 dates

2026-01-02 through 2026-01-30

Recorded labor hours
120 hours
Sum of recorded labor hours across eligible records in this scope.
Recorded total units
4500 units
Sum of total units across eligible records in this work center and product scope.
Labor hours per recorded output unit
0.026666666667 hours per unit
Total eligible labor hours divided by total eligible output units.

Evidence and limitations

  • At least five eligible records cover at least three distinct dates; these are engineering review thresholds.
  • No exclusion, repeated-scope ambiguity, or dominant record was detected by the checks used for this group.
  • The calculation describes the submitted eligible records and does not extrapolate to unobserved production.
  • This comparison does not establish why the observed result occurred.
  • Labor hours per unit has no confirmed efficiency baseline for estimating avoidable labor.
  • A labor hourly rate alone does not establish hours or costs that can be avoided.

Source fields: Date, Work center, Product, Labor time, Total units.

Example source rows: 7, 13, 19, 25, 31. These are traceable examples, not the full calculation input.

Next investigation

  1. Confirm whether labor hours and output cover the same crew, product and reporting period.
  2. Establish a comparable labor baseline and identify which hours or costs could be avoided before estimating savings.

Back to scan investigation

Assembly · Housing

Labor hours per output unit

Measured from eligible records · descriptive evidence

15 eligible records · 0 excluded records · 15 dates

2026-01-01 through 2026-01-29

Recorded labor hours
120 hours
Sum of recorded labor hours across eligible records in this scope.
Recorded total units
3000 units
Sum of total units across eligible records in this work center and product scope.
Labor hours per recorded output unit
0.04 hours per unit
Total eligible labor hours divided by total eligible output units.

Evidence and limitations

  • At least five eligible records cover at least three distinct dates; these are engineering review thresholds.
  • No exclusion, repeated-scope ambiguity, or dominant record was detected by the checks used for this group.
  • The calculation describes the submitted eligible records and does not extrapolate to unobserved production.
  • This comparison does not establish why the observed result occurred.
  • Labor hours per unit has no confirmed efficiency baseline for estimating avoidable labor.
  • A labor hourly rate alone does not establish hours or costs that can be avoided.

Source fields: Date, Work center, Product, Labor time, Total units.

Example source rows: 4, 10, 16, 22, 28. These are traceable examples, not the full calculation input.

Next investigation

  1. Confirm whether labor hours and output cover the same crew, product and reporting period.
  2. Establish a comparable labor baseline and identify which hours or costs could be avoided before estimating savings.

Back to scan investigation

Mill A · Bracket

Labor hours per output unit

Measured from eligible records · descriptive evidence

15 eligible records · 0 excluded records · 15 dates

2026-01-02 through 2026-01-30

Recorded labor hours
120 hours
Sum of recorded labor hours across eligible records in this scope.
Recorded total units
4500 units
Sum of total units across eligible records in this work center and product scope.
Labor hours per recorded output unit
0.026666666667 hours per unit
Total eligible labor hours divided by total eligible output units.

Evidence and limitations

  • At least five eligible records cover at least three distinct dates; these are engineering review thresholds.
  • No exclusion, repeated-scope ambiguity, or dominant record was detected by the checks used for this group.
  • The calculation describes the submitted eligible records and does not extrapolate to unobserved production.
  • This comparison does not establish why the observed result occurred.
  • Labor hours per unit has no confirmed efficiency baseline for estimating avoidable labor.
  • A labor hourly rate alone does not establish hours or costs that can be avoided.

Source fields: Date, Work center, Product, Labor time, Total units.

Example source rows: 5, 11, 17, 23, 29. These are traceable examples, not the full calculation input.

Next investigation

  1. Confirm whether labor hours and output cover the same crew, product and reporting period.
  2. Establish a comparable labor baseline and identify which hours or costs could be avoided before estimating savings.

Back to scan investigation

Mill A · Housing

Labor hours per output unit

Measured from eligible records · descriptive evidence

15 eligible records · 0 excluded records · 15 dates

2026-01-01 through 2026-01-29

Recorded labor hours
120 hours
Sum of recorded labor hours across eligible records in this scope.
Recorded total units
3000 units
Sum of total units across eligible records in this work center and product scope.
Labor hours per recorded output unit
0.04 hours per unit
Total eligible labor hours divided by total eligible output units.

Evidence and limitations

  • At least five eligible records cover at least three distinct dates; these are engineering review thresholds.
  • No exclusion, repeated-scope ambiguity, or dominant record was detected by the checks used for this group.
  • The calculation describes the submitted eligible records and does not extrapolate to unobserved production.
  • This comparison does not establish why the observed result occurred.
  • Labor hours per unit has no confirmed efficiency baseline for estimating avoidable labor.
  • A labor hourly rate alone does not establish hours or costs that can be avoided.

Source fields: Date, Work center, Product, Labor time, Total units.

Example source rows: 2, 8, 14, 20, 26. These are traceable examples, not the full calculation input.

Next investigation

  1. Confirm whether labor hours and output cover the same crew, product and reporting period.
  2. Establish a comparable labor baseline and identify which hours or costs could be avoided before estimating savings.

Back to scan investigation

Mill B · Bracket

Labor hours per output unit

Measured from eligible records · descriptive evidence

15 eligible records · 0 excluded records · 15 dates

2026-01-02 through 2026-01-30

Recorded labor hours
120 hours
Sum of recorded labor hours across eligible records in this scope.
Recorded total units
3930 units
Sum of total units across eligible records in this work center and product scope.
Labor hours per recorded output unit
0.030534351145 hours per unit
Total eligible labor hours divided by total eligible output units.

Evidence and limitations

  • At least five eligible records cover at least three distinct dates; these are engineering review thresholds.
  • No exclusion, repeated-scope ambiguity, or dominant record was detected by the checks used for this group.
  • The calculation describes the submitted eligible records and does not extrapolate to unobserved production.
  • This comparison does not establish why the observed result occurred.
  • Labor hours per unit has no confirmed efficiency baseline for estimating avoidable labor.
  • A labor hourly rate alone does not establish hours or costs that can be avoided.

Source fields: Date, Work center, Product, Labor time, Total units.

Example source rows: 6, 12, 18, 24, 30. These are traceable examples, not the full calculation input.

Next investigation

  1. Confirm whether labor hours and output cover the same crew, product and reporting period.
  2. Establish a comparable labor baseline and identify which hours or costs could be avoided before estimating savings.

Back to scan investigation

Mill B · Housing

Labor hours per output unit

Measured from eligible records · descriptive evidence

15 eligible records · 0 excluded records · 15 dates

2026-01-01 through 2026-01-29

Recorded labor hours
120 hours
Sum of recorded labor hours across eligible records in this scope.
Recorded total units
2625 units
Sum of total units across eligible records in this work center and product scope.
Labor hours per recorded output unit
0.045714285714 hours per unit
Total eligible labor hours divided by total eligible output units.

Evidence and limitations

  • At least five eligible records cover at least three distinct dates; these are engineering review thresholds.
  • No exclusion, repeated-scope ambiguity, or dominant record was detected by the checks used for this group.
  • The calculation describes the submitted eligible records and does not extrapolate to unobserved production.
  • This comparison does not establish why the observed result occurred.
  • Labor hours per unit has no confirmed efficiency baseline for estimating avoidable labor.
  • A labor hourly rate alone does not establish hours or costs that can be avoided.

Source fields: Date, Work center, Product, Labor time, Total units.

Example source rows: 3, 9, 15, 21, 27. These are traceable examples, not the full calculation input.

Next investigation

  1. Confirm whether labor hours and output cover the same crew, product and reporting period.
  2. Establish a comparable labor baseline and identify which hours or costs could be avoided before estimating savings.

Back to scan investigation

REPRODUCIBLE SAMPLE

Source and calculation versions

These synthetic CSV records passed through the same parser and deterministic analysis pipeline used by configured Atlas scans. The sample has a confirmed mapping; it is not a customer upload or a customer success story.

Sample
Planted operational gaps
Demo version
1
Parser version
1.0.0
Calculation version
1.0.0
Mapping version
1
Assumptions version
1
Source SHA-256
a42a66cc43703ca9977393dd76e14cb787bab76d7f6c5afa4979d8eadff2d619
Canonical records SHA-256
4a8da8404e84a6ee69f0c575d8d6625d496b9a727f82470e5934831ec51c1bf0
Result SHA-256
4ce26a144cafb32e5adf16184cb85708e845874629c6101273eaeabfd33693f3

Evidence row numbers refer to the downloadable CSV. All eligible rows contribute to each calculation; the displayed source rows are examples. These examples do not establish causes, available capacity, or guaranteed recovery.

Download synthetic CSVDownload calculated resultDownload saved row evidenceDownload version manifest

Start with the records you already have.

The Free Operations Scan offer is one complete scan, including supported findings, evidence, confidence and assumptions. A useful result may show no positive opportunity or insufficient data.

Customer uploads and scans are not available in this public preview.

See what data to prepare →