S_00012 — Reviewed production-cost comparison by order quantity

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

The closest existing record was S_00009. That record reruns configured management reports over existing transactions, while this mechanism compares manufacturing-order cost across representative run quantities before a planner makes a production-quantity decision. The duplicate review therefore found only partial overlap and approved a materially distinct record.

kind: solution_catalog
schema_version: 1
solutions:
  - id: S_00012
    proofIds:
      - PF_MULTI_006
    priority: 50
    name: 'Reviewed production-cost comparison by order quantity'
    status: approved
    mechanism: >-
      Use each manufacturing order's ordered quantity, completed quantity,
      planned cost, and actual cost to compare historical production economics
      across representative run quantities for the same item and comparable
      work-center conditions. Present confirmed sales-order demand and current
      stock quantities as operating context, without treating them as expected
      stock value. If the customer later supplies and approves a separate
      expected-stock valuation and inventory carrying-cost method, configure
      that calculation as an explicitly customer-supplied extension. Until that
      extension exists, the mechanism is a production-cost comparison only and
      does not establish the total economic cost or preferred batch size.
    capabilities:
      - name: 'Record planned and actual cost on each manufacturing order'
        classification: native
        conditions:
          - 'The manufacturing order must contain the correct ordered and completed quantities.'
          - 'Production reports, work orders, time tickets, material consumption, labor, and scrap must be recorded completely.'
          - 'The configured manufacturing costing strategy must be applied consistently across compared orders.'
          - 'Planned and actual costs must use compatible units and currency.'
        evidence_ids: []
      - name: 'Compare historical manufacturing-order cost by run quantity'
        classification: configured
        conditions:
          - 'The customer must define which items, variants, work centers, routings, and periods are comparable.'
          - 'The comparison must retain ordered quantity, completed quantity, planned total and per-unit cost, and actual total and per-unit cost.'
          - 'Changes in material, labor, routing, equipment, costing strategy, and product specification must be identified before orders are compared.'
          - 'The configured view must reconcile its totals to representative manufacturing orders.'
          - 'Configuration and testing effort cannot be sized before representative order history is inspected.'
        evidence_ids: []
      - name: 'Read confirmed sales-order demand and current stock quantity as context'
        classification: native
        conditions:
          - 'Sales orders and stock records must be current and use compatible item and unit identifiers.'
          - 'Only confirmed sales-order demand is verified as a native demand source.'
          - 'On-hand and available stock are current quantities; neither is expected stock value.'
          - 'Demand and stock quantities must not be converted into economic cost without a separately approved method.'
        evidence_ids: []
      - name: 'Derive an expected scrap assumption for a candidate quantity'
        classification: configured
        conditions:
          - 'The customer must define how completed-order scrap history is converted into an expected value.'
          - 'The customer must define the minimum representative history and treatment of outliers or changed operating conditions.'
          - 'No native expected-scrap model was verified.'
          - 'Configuration and testing effort cannot be sized before representative manufacturing history is inspected.'
        evidence_ids: []
      - name: 'Product-native expected-stock valuation and inventory carrying-cost calculation'
        classification: unavailable
        conditions:
          - 'The user explicitly stated that expected stock value and cost of carrying do not exist.'
          - 'No dedicated expected-stock valuation or inventory carrying-cost implementation was verified in MCP server d8189168.'
          - 'This capability must not be presented as shipped, configured, or on the roadmap.'
        evidence_ids: []
      - name: 'Apply a customer-supplied expected-stock valuation and inventory carrying-cost calculation'
        classification: configured
        conditions:
          - 'The customer must supply and approve the expected-stock calculation.'
          - 'The customer must supply and approve the inventory valuation basis, carrying-cost method, rate, and time horizon.'
          - 'The source records and fields required by the customer calculation must be identified and maintained.'
          - 'No expected-stock or carrying-cost inputs were supplied for this record, so this capability is currently blocked.'
          - 'The configured result must be reconciled to representative historical periods before operational use.'
          - 'Configuration and testing effort cannot be sized before the customer method and source data are inspected.'
        evidence_ids: []
      - name: 'Present a reviewed production-quantity comparison before release'
        classification: configured
        conditions:
          - 'A configured view must expose the source manufacturing orders, quantities, planned costs, actual costs, variances, and assumptions.'
          - 'A planner must review the comparison before using it in a production-quantity decision.'
          - 'Without the customer-supplied expected-stock and carrying-cost extension, the view must be labeled production-cost comparison rather than total-economic-cost comparison.'
          - 'No dedicated native batch-size comparison or release gate was verified.'
          - 'Configuration and testing effort cannot be sized before the review workflow is inspected.'
        evidence_ids: []
    expected_outcome_hypotheses:
      - 'A planner can compare planned and actual manufacturing cost across representative historical run quantities.'
      - 'The comparison can show whether production-cost behavior differs between smaller and larger completed orders without asserting why.'
      - 'Confirmed demand and current stock quantities can be reviewed beside manufacturing cost without being misrepresented as expected stock value.'
      - 'If a customer later supplies a valid expected-stock and carrying-cost method, the production-cost comparison could become one input to a broader total-economic-cost comparison.'
    limitations:
      - 'The native product records planned and actual manufacturing-order cost but does not provide expected stock value or inventory carrying cost.'
      - 'Without expected-stock valuation and carrying cost, the mechanism does not calculate the total economic cost required by P_00013.'
      - 'Current on-hand or available stock quantity is not expected stock value and must not be used as a substitute.'
      - 'Historical planned and actual cost relationships may not predict a future run after changes in material, labor, routing, equipment, costing strategy, or product specification.'
      - 'Actual scrap history does not establish expected scrap for a candidate quantity without a customer-approved method.'
      - 'A customer-supplied economic-cost extension is not currently available because its method and inputs have not been supplied.'
      - "The configured extension's implementation effort and accuracy cannot be established before the customer method and source data are inspected."
      - 'This mechanism does not optimize the production queue, automatically select a batch size, or replace planner judgment.'
    prohibited_claims:
      - 'That the product natively calculates expected stock value or inventory carrying cost.'
      - 'That current on-hand or available stock quantity is expected stock value.'
      - 'That planned-versus-actual manufacturing cost is the same as total economic cost.'
      - 'That the lowest historical production cost identifies the preferred future batch size.'
      - 'That a larger batch necessarily lowers total economic cost.'
      - 'That a smaller batch necessarily lowers total economic cost.'
      - 'That a customer-supplied expected-stock or carrying-cost calculation exists before the customer provides and approves it.'
      - 'That the configured extension is available out of the box or has a known implementation effort.'
      - 'That historical cost or scrap relationships will continue unchanged.'
      - 'That the mechanism automatically selects or releases a production quantity.'
      - 'Any quantified saving, scrap reduction, carrying-cost reduction, or return on investment.'

Outstanding

1. proofIds reaches approved PF_MULTI_006. That proof has never been executed, and its listing of all seven verticals rests on product-surface evidence with no vertical scope. Do not treat its approved lifecycle status as evidence that the comparison has been executed in this audience.
2. Every capability has evidence_ids: []. The implementation checks from MCP server d8189168 are deployment-specific observations, not canonical evidence records. Route formal product evidence through W9.
3. The total-economic-cost comparison is blocked. The product does not provide expected-stock valuation or inventory carrying cost, and no customer-supplied method or inputs were provided for a configured extension.
4. Configured effort is unknown. Inspect representative manufacturing-order history, the customer's comparison rules, any customer-supplied economic-cost method, and the required review workflow before estimating implementation work.