P_00006 — Committed orders are sequenced through manual asset-by-asset judgment
One testable operational mismatch: the schedule records orders and required dates, while the feasible asset allocation and sequence remain in planner judgment.
| Problem ID | Name | Solution IDs | Statement type | Status |
|---|---|---|---|---|
P_00006 | Committed orders are sequenced through manual asset-by-asset judgment | S_00005 | market_hypothesis | draft |
kind: problem_catalog
schema_version: 1
problems:
- id: P_00006
solutionsIds:
- S_00005
priority: 45
name: 'Committed orders are sequenced through manual asset-by-asset judgment'
status: approved
statement_type: market_hypothesis
applies_to_icp_ids: []
situation: >-
Accepted orders can run on several production assets or sites, those
assets differ in output and suitability, and sequencing must also account
for due dates, changeovers, run continuity, location, and freight.
operational_mismatch: >-
The production record holds required dates and available orders, but it
does not resolve asset allocation and sequence across the relevant
constraints. A planner manually constructs and revises the production
arrangement using experience and inspection of each line.
possible_consequences:
- 'Unslotted orders remain outside the active sequence until a planner places them.'
- >-
Asset, changeover, and run-length tradeoffs must be reconsidered manually
as the schedule changes.
- >-
The resulting sequence depends on planner knowledge that is not
represented in the schedule.
observable_signals:
- 'Scheduling is described as Tetris, manual slotting, or fitting orders into gaps.'
- 'A planner reviews several eligible assets before placing an order.'
- 'Orders with required dates remain unslotted in the scheduling view.'
- >-
Changeover reduction and keeping similar work running are manual
scheduling objectives.
disconfirming_signals:
- >-
The scheduling system produces a feasible asset and sequence assignment
using maintained rates, capabilities, due dates, and changeover rules.
- >-
Planners review recorded exceptions rather than manually placing the
ordinary order population.
confirmation_questions: []
evidence_requirement: >-
One representative scheduling cycle showing the orders available, the
initial system-generated allocation if any, the planner's manual changes,
and which constraints drove those changes.
evidence_ids: []
prohibited_claims:
- 'That manual scheduling necessarily causes late delivery or lost margin.'
- 'That production scheduling can or should operate without planner review.'
- 'Any quantified changeover, utilization, freight, or output improvement.'