PlaysbyMoat8
Back to the library
The workflow guideFinance

Compare order mixes against scarce capacity

Evaluate product priorities using their contribution and use of the limiting resource.

6 implementation stepsIntermediate

How this works

Evaluate product priorities using their contribution and use of the limiting resource.

Compare feasible production mixes using the resource that actually limits output. Contribution per constrained minute can guide a simplified scenario, but demand limits, other bottlenecks and relevant variable costs must remain explicit.

Before you start

Defined operating scope

Production priorities compete for a known scarce resource with measurable demand and contribution.

Required source material

Obtain Demand; Variable costs; Constraint time. If connectors are unavailable, use authorized files with the same fields.

Decision and exception rules

Another resource becomes limiting in the proposed mix. Add that constraint and recompute feasibility.

Prepare the inputs

product_economics
Required

Selling price and incremental variable costs

Use consistent currency and cost definitions.

constraint_usage
Required

Required scarce-resource time per unit

Validate the current limiting resource.

demand_limits
Required

Confirmed or scenario demand by product

Do not assume unlimited sales.

available_capacity
Required

Usable constrained time and other limits

Account for planned downtime and mandatory commitments.

Implementation, step by step

  1. Establish the working record

    • Confirm the selected records, effective versions and responsible owner.
    • Check product_economics, constraint_usage, demand_limits, available_capacity before beginning. Record the source version and the selected scope; an unavailable value stays unknown rather than becoming an inferred fact.

    Checkpoint: The input record identifies the selected product_economics and any missing required fields.

  2. Validate the limiting resource

    • Validate the limiting resource and ensure each product’s capacity consumption is comparable.
    • Recalculate contribution, capacity use and demand bounds for every scenario.

    Checkpoint: A saved intermediate result for: Validate the limiting resource.

  3. Compare contribution per constrained unit

    • Calculate contribution per unit and per constrained unit using deterministic arithmetic, preserving the chosen cost definition.
    • Check mandatory orders, setup effects and other constraints omitted from the simplified model.

    Checkpoint: A saved intermediate result for: Compare contribution per constrained unit.

  4. Model feasible order mixes

    • Model feasible order mixes within demand and capacity limits, then compare contribution and unmet demand with assumptions visible.
    • Recalculate contribution, capacity use and demand bounds for every scenario.

    Checkpoint: A saved intermediate result for: Model feasible order mixes.

  5. Reconcile the proposed result

    • Recalculate contribution, capacity use and demand bounds for every scenario.
    • Check mandatory orders, setup effects and other constraints omitted from the simplified model.

    Checkpoint: The listed discrepancies have a named reviewer or an explicit unresolved status.

  6. Package the result and unresolved work

    • Verify demand, capacity and costs; avoid replacing financial reporting with a simplified model.
    • This scenario model does not replace financial reporting or promise realized profit.

    Checkpoint: A production-priority scenario comparison. Unresolved items remain visible in the review record.

Decisions along the way

Another resource becomes limiting in the proposed mix.

Add that constraint and recompute feasibility.

Demand is insufficient for the highest-ranked product.

Cap it at supported demand and allocate remaining capacity to feasible alternatives.

Cost definitions mix fixed allocations with incremental costs.

Reconcile the intended decision model before interpreting the ranking.

What you will produce

constraint-aware-order-mix-result.json

JSON

A production-priority scenario comparison. Label proposed and completed states separately.

Include: product · unit_contribution · constraint_time · contribution_per_constraint · mix_quantity · capacity_used · scenario_assumptions · status · evidence_reference · review_note

constraint-aware-order-mix-review.md

Markdown

Keep the evidence and unresolved decisions needed to apply this result, including exceptions involving available_capacity.

Include: source_reference · question · owner · next_action

Check the result

  • Recalculate contribution, capacity use and demand bounds for every scenario.
  • Check mandatory orders, setup effects and other constraints omitted from the simplified model.
  • Inspect product_economics and constraint_usage in both the original and output; confirm that record identity and interpretation survived the transformation.
  • Verify demand, capacity and costs; avoid replacing financial reporting with a simplified model.

When something goes wrong

Another resource becomes limiting in the proposed mix.

Add that constraint and recompute feasibility. Retain the affected evidence and recovery status.

Demand is insufficient for the highest-ranked product.

Cap it at supported demand and allocate remaining capacity to feasible alternatives. Retain the affected evidence and recovery status.

Cost definitions mix fixed allocations with incremental costs.

Reconcile the intended decision model before interpreting the ranking. Retain the affected evidence and recovery status.

A worked example

SYNTHETIC EXAMPLE · NOT A REPORTED BUSINESS RESULT

Request

Compare order mixes against scarce capacity for the following bounded example; prepare the result for review.

Inputs

Synthetic example: Product A contributes 30 units and needs 3 constrained minutes; B contributes 20 and needs 1. Capacity is 60 minutes, demand B at most 30 and A at most 20.

Expected result

Synthetic expected result: One feasible prioritized mix is 30 B and 10 A, using 60 minutes and contributing 900 units. This simplified result depends on the stated demand, cost and single-constraint assumptions.

Run a small pilot

Start small

Trial a representative batch containing the ordinary case and the exception demonstrated above.

Record the baseline

Record current preparation time, review effort and correction types for the same records.

Agree success criteria

Agree acceptable review and error limits; measure feasible scenarios accepted; contribution and capacity assumptions reconciled with actuals.

Stop or revise

Cost definitions mix fixed allocations with incremental costs. Pause affected records and apply this recovery: Reconcile the intended decision model before interpreting the ranking.

Keep the scope clear

  • This scenario model does not replace financial reporting or promise realized profit.
  • Production and commercial owners approve order priorities and customer commitments.

Check before using

Verify demand, capacity and costs; avoid replacing financial reporting with a simplified model.

Business activities

  • Plan inventory and production
  • Manage finances and accounting

Editorially adapted workflow; not independently tested.

FROM A RECIPE TO YOUR WORKFLOW

Bring the company context together.

This workflow needs reliable inputs before it needs a better prompt. Moat8 Vault brings working information into a readable archive for the AI tools you use.

For this recipe: Demand · Variable costs · Constraint time

Start with one recurring task, agree which sources to use, and review the first result with your team.

Discuss this workflow

What does your team do?

Choose the recurring work you would like to improve.

A field guide, made for work.

Plays is a curated library of anonymized business workflows. Each recipe explains the inputs, steps, tools, and checks you can adapt to your team. These are editorial guides, not independently tested implementations.

When you share a company website, the guide may read a limited number of public pages on that website. Messages and retrieved page text are sent to our AI provider, NVIDIA, to recommend relevant workflows. Share a general description rather than confidential information.

Saved workflows and selected activities stay in this browser. Your chat history and selected company website are kept in this tab and cleared when you reload or start a new chat. The server does not store conversations. Live source monitoring is not enabled.

If you allow analytics, PostHog receives page views and actions such as workflow saves, skill downloads and link clicks. Random browser and session identifiers connect these actions without identifying you by name. Your choice and browser identifier expire after 90 days; sessions restart after 30 minutes of inactivity or 24 hours. We use local storage, not analytics cookies. Messages, company URLs, search text, full referrers and IP addresses are not sent. There are no person profiles or session recordings. You can decline or withdraw in Analytics settings; Do Not Track and Global Privacy Control keep analytics off.

Read the Plays Privacy Notice ↗