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
No supported positive opportunity
Thirty days of synthetic records meeting their recorded targets without recorded downtime or scrap. Missing fields still limit coverage; this scenario does not establish that an operation is loss-free.
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.
This scan did not identify a positive opportunity in the comparisons it could assess. This result describes the eligible records and supported methods in this report; other operating losses may remain unmeasured.
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 · 0 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.
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
Confirm what the production target represents and whether target and recorded gross output cover the same product and period.
Confirm additional customer demand, contribution margin and practical recoverability before treating a target gap as a scenario for additional sales.
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
Review the downtime events, their recorded reasons and scheduled time coverage with the people responsible for the process.
Separate necessary stops from time that might be avoidable before planning an intervention. Recorded downtime alone does not establish recoverable time or cost.
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
Review the downtime events, their recorded reasons and scheduled time coverage with the people responsible for the process.
Separate necessary stops from time that might be avoidable before planning an intervention. Recorded downtime alone does not establish recoverable time or cost.
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
Review the downtime events, their recorded reasons and scheduled time coverage with the people responsible for the process.
Separate necessary stops from time that might be avoidable before planning an intervention. Recorded downtime alone does not establish recoverable time or cost.
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
Review the downtime events, their recorded reasons and scheduled time coverage with the people responsible for the process.
Separate necessary stops from time that might be avoidable before planning an intervention. Recorded downtime alone does not establish recoverable time or cost.
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: 6, 12, 18, 24, 30. These are traceable examples, not the full calculation input.
Next investigation
Review the downtime events, their recorded reasons and scheduled time coverage with the people responsible for the process.
Separate necessary stops from time that might be avoidable before planning an intervention. Recorded downtime alone does not establish recoverable time or cost.
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: 3, 9, 15, 21, 27. These are traceable examples, not the full calculation input.
Next investigation
Review the downtime events, their recorded reasons and scheduled time coverage with the people responsible for the process.
Separate necessary stops from time that might be avoidable before planning an intervention. Recorded downtime alone does not establish recoverable time or cost.
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.
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.
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.