DecisioWorks

RECORDED RUN · MASTER PRODUCTION PLANNING

Stamping: from input data to a reviewable plan

Start by connecting demand, time and material availability under finite capacity. Then compare the plan after changing management preferences. This guide follows a recorded baseline and re-run.

Recorded 2026-08-31 · DecisioWorks v1.4.0 · Commercial Enterprise license · API records, not a live run on this page

The business question

What time-phased production plan can be generated from the given demand, capacity and material conditions? After changing load- and waiting-related objectives, did demand coverage, load or shortages change? Planners need to inspect both physical quantities and how the plan is evaluated.

Input: connect the business objects

Input scale in this sample
ObjectRecordsBusiness meaning
Order lines1,920Demand items, quantities and due dates
Capacity50Work-center availability by time unit
Operation-material links38Materials required by operations
Material availability500Material readiness by time unit
Time units25A shared time coordinate for demand, capacity and results
Work centers3One parent workshop and two production lines, not three machines

The capacity.used field represents the occupied or unavailable proportion, from 0 to 1. It is not the utilization calculated by this solve. Establishing that meaning gives everyone the same capacity baseline.

Configuration: expose constraints and objectives

Baseline and adjusted configuration
SettingBaselineAdjusted
Capability workflowproduction_planningUnchanged
Demand, capacity and material constraintsEnabledUnchanged
Soft capacity constraintcapacity_soft = trueUnchanged
Inventory constraintDisabledUnchanged
job_bias weight-0.001-0.003
waittime weight12
Solver resources16 threads / 120-second limitUnchanged

After reading and checking the data, an orchestration recipe assembles objectives and constraints and calls GOCK to generate a plan. Analysis then examines planned quantities, shortages, load and objective details. The re-run uses the same data and retains configuration differences for review.

Output: did the business quantities change?

Baseline and re-run from the same API comparison
MeasureBaselineAdjusted
Valid candidates returned11
Plan result rows6666
Total demand / output680,500 / 680,500680,500 / 680,500
Final shortage00
Planned load rate31.74%31.74%
Weighted job_bias-7,854.678-23,564.034
Recorded elapsed time14.41 seconds14.29 seconds
Action events / errors12 / 012 / 0

The aggregate business quantities stayed the same, while weighted job_bias changed with its weight. That score change alone does not demonstrate a production improvement. Matching aggregates also do not prove that every task assignment stayed identical; detailed results are needed for that assessment.

Apply the approach to your own planning

  • Check that order, work-center, route, material and time identifiers connect correctly.
  • Separate mandatory conditions from soft constraints that can be expressed through a penalty.
  • Keep an approved baseline and, where possible, change one factor per comparison.
  • Review detailed plans and business measures with the planner responsible for accepting changes.