S_00005 — Generated work-center allocation and schedule reflow

This solution addresses P_00006; the problem owns the forward reference in its ordered solutionsIds array.

kind: solution_catalog
schema_version: 1
solutions:
  - id: S_00005
    proofIds: []
    priority: 60
    name: 'Generated work-center allocation and schedule reflow'
    status: approved
    mechanism: >-
      When a manufacturing order is confirmed, generate its dependent work
      orders, assign them to compatible work centers using maintained capacity,
      load, and performance information, and calculate their planned dates.
      Present that arrangement on the work-order timeline and allow the remaining
      active schedule to be reflowed after conditions change, while preserving
      work that has already started for planner review rather than rebuilding
      every placement manually.
    capabilities:
      - name: 'Generate routed work orders with recorded dependencies when a manufacturing order is confirmed'
        classification: native
        conditions:
          - 'The manufacturing order must have a valid routing and bill of materials.'
          - 'The manufacturing order must be eligible for confirmation under the configured work-in-progress policy.'
        evidence_ids: []
      - name: 'Assign compatible work centers using capacity, availability, and load-balanced scoring'
        classification: native
        conditions:
          - 'Compatible work centers, sites, routing eligibility, and production characteristics must be maintained.'
          - 'Assignments are only as reliable as the current work-center and active-work-order data.'
        evidence_ids: []
      - name: 'Forward-schedule and reflow active work orders using dates, dependencies, capacity, and recorded blocked periods'
        classification: native
        conditions:
          - 'Work-center calendars and blocked periods must be recorded correctly.'
          - 'Work orders that have already started remain fixed rather than being rescheduled.'
          - 'Only forward scheduling was verified in MCP server d8189168.'
        evidence_ids: []
      - name: 'Review work-center assignments and planned dates on the work-order timeline'
        classification: native
        conditions:
          - 'The generated arrangement remains subject to planner review and correction.'
        evidence_ids: []
      - name: 'Configure work-center output, availability, changeovers, minimum quantities, sites, and warehouses'
        classification: configured
        conditions:
          - 'The customer must define and maintain its production constraints and operating parameters.'
          - 'Configuration and data-migration effort cannot be sized before the existing rules and records are inspected.'
        evidence_ids: []
    expected_outcome_hypotheses:
      - 'Confirmed work can enter the production record with a proposed work-center assignment and planned dates rather than remaining unslotted.'
      - 'A schedule change can trigger recalculation of the remaining active work while preserving work already in progress.'
      - 'Planners can review generated assignments and exceptions instead of manually constructing every ordinary placement.'
      - 'Maintained capacity, dependency, and changeover information can be applied consistently when the sequence is recalculated.'
    limitations:
      - >-
        The confirmation-hook documentation identifies a hardcoded 24/7
        scheduling assumption. Multi-shift and non-continuous calendar behavior
        must be verified before relying on the initial schedule.
      - >-
        The implementation demonstrates forward scheduling and load-balanced
        scoring, not proof of a globally optimal production sequence.
      - >-
        Site and warehouse relationships are represented, but freight cost,
        delivery routing, and transportation constraints were not verified as
        scheduling objectives.
      - >-
        Scheduling around recorded maintenance windows does not establish a
        preventive or predictive maintenance capability.
      - >-
        Incorrect routing, output, capacity, changeover, calendar, or required-date
        data can produce an unsuitable schedule.
      - 'Work already in progress is preserved and may constrain the recalculated arrangement.'
    prohibited_claims:
      - 'That production scheduling operates without planner review.'
      - 'That the generated sequence is globally optimal.'
      - 'That the mechanism optimizes freight or transportation cost.'
      - 'That it provides preventive or predictive maintenance.'
      - 'That every unslotted order will receive a feasible placement.'
      - 'Any quantified changeover, utilization, freight, output, margin, or delivery improvement.'