APS and ERP actuals: building an executable production plan

Management challenge

APS accounts for capacity, materials, equipment, shifts, routings and orders so that a plan is not merely recorded but realistically executable.

When the problem becomes visible

• Plans are repeatedly rebuilt by hand
• Bottlenecks become visible only after a delay
• Procurement and production use different horizons

How to design the solution

This approach keeps the discussion focused on management control rather than only on system functions.

• Define planning rules
• Prepare routing and capacity master data
• Agree the horizon and level of detail
• Integrate APS with ERP and BI

Common mistakes

The most common mistakes appear when a team trades architecture quality for launch speed.

These mistakes may be hidden during a demonstration but become visible in production operation.

• Expect full optimisation from ERP
• Leave routing data unclean
• Plan without production and procurement involvement

Key takeaways

• APS complements ERP rather than replacing it.
• Plan feasibility depends on constraint quality.
• Scenario planning reduces manual recalculation.
• BI is needed to monitor actuals and variances.

Working answer

A digital initiative should first be framed as a management decision: define the object, data, constraints, action owner and verification method. Technology selection follows that framing. For this task, the initial evidence is “material availability is disconnected from the schedule”, and the decision boundary concerns work centres and calendars.

The practical focus is plan feasibility under capacity, material, routing and deadline constraints. A decision is ready for approval when the object, owner, baseline, permitted action and outcome evidence are explicit; the reference object in this article is plan, actuals and rescheduling causes.

Applied analysis: APS and ERP actuals: building an executable production plan

The practical framing of “APS and ERP actuals: building an executable production plan” connects process, data and authority. Work centres and calendars defines the boundary, while “plans are repeatedly corrected manually” identifies the moment when a decision is required.

Use “material availability is disconnected from the schedule” as the scenario input and “assemble data and constraints” as the testable response. Preserve the source, time and data version in the record.

Review the risk “no feedback from execution” before expanding scope. If the control fails in the first cycle, postpone scaling and refine the data, authority or decision boundary.

• Working object: Work centres and calendars.
• Diagnostic signal: Material availability is disconnected from the schedule.
• Response action: Assemble data and constraints.
• Controlled risk: No feedback from execution.

Signals in the starting situation

The work starts with an observable situation, not with interface selection. The diagnostic signal for this article is: material availability is disconnected from the schedule. It should be supported by a real example such as a document, data sample, decision record or registered variance.

The first scope is limited to one object and one decision. Changing every process, master-data set and system at once obscures causality. For the signal “plans are repeatedly corrected manually”, a representative boundary is a period, business unit or transaction class where the situation can be tested again.

• Indicator: Plans are repeatedly corrected manually. Analysis needs an actual example and the resulting change in production routings.
• Diagnostic signal 2: Bottlenecks are found after release. Its record contains an example and impact on work centres and calendars.
• Management signal 3: Orders compete for the same resource. Use condition: a link to an actual example and to materials and availability.

Process and data boundary

Describe the boundary through object records rather than system names. For work centres and calendars, record meaning, identifier, source, quality owner and update event; for materials and availability, also document the relationship rule.

Test the link between work centres and calendars and materials and availability using an end-to-end example. The team performs “verify the outcome”, traces transformations and identifies where a discrepancy arises, who corrects it and which dependent outputs are recalculated.

• Record 1. Object: Orders and priorities. Required details: identifier, lineage, quality rule and update event. Signal: Bottlenecks are found after release.
• Control record 2. Object: Production routings. Observable signal: Orders compete for the same resource. Accountability: semantic owner and quality owner.
• Boundary 3. Object: Work centres and calendars. Define the source, frequency, permitted transformations and response to “material availability is disconnected from the schedule”.

Accountability boundary

State the decision before compiling requirements. It identifies plan, actuals and rescheduling causes, the role authorised to choose, the permitted action and the evidence participants will use to accept or reject an option.

Do not combine the signal “material availability is disconnected from the schedule” and the risk “no feedback from execution” into one measure: the former describes an observable state, while the latter describes a possible consequence. The action “assemble data and constraints” connects them in a testable scenario.

• Decision 1: object — orders and priorities; signal — orders compete for the same resource; action — assemble data and constraints.
• Decision 2: object — production routings; signal — material availability is disconnected from the schedule; action — assign roles and actions.
• Decision 3: object — work centres and calendars; signal — the plan cannot explain a delay; action — verify the outcome.

A practical decision model

The method is a sequence of decisions rather than a universal checklist. For materials and availability, each output is used at the next step: the model supports the scenario, the scenario defines data and requirements, and requirements become test and acceptance criteria.

For work centres and calendars, the sequence may change with scale and constraints, but assumptions are always documented. When source data is incomplete or a decision involves an external party, the dependency receives an owner, review date and condition for proceeding. The first action is “assemble data and constraints”.

• Frame the problem is the action at stage 1. The output documents production routings.
• At position 2, the action is “identify the management object”; its result is work centres and calendars.
• Stage 3: assemble data and constraints. The working artefact describes materials and availability.
• Stage gate 4 connects the action “assign roles and actions” with the result “plan, actuals and rescheduling causes”.

Events, data and exchange

Describe data exchange as a contract between owners. For materials and availability, specify the triggering event, system of record, mandatory fields, pre-transfer control and the recipient's response to an error.

Choose the transport mechanism after frequency and resilience requirements are known. Check “material availability is disconnected from the schedule” on both sides of the interface to distinguish a source error from transformation, delivery or loading failure.

• Subject area 5: Plan, actuals and rescheduling causes. Verification basis: system of record, owner authority and the signal “plans are repeatedly corrected manually”.
• Object 4: Materials and availability. Record fields: source, semantic owner, quality owner and refresh rule. Control signal: The plan cannot explain a delay.
• Boundary 3. Object: Work centres and calendars. Define the source, frequency, permitted transformations and response to “material availability is disconnected from the schedule”.

Who makes the decision

For plan, actuals and rescheduling causes, the role model determines more than screen access. In the action “assemble data and constraints”, it identifies who changes a rule, authorises an exception, accepts risk and confirms the outcome. The accountability matrix is tied to decisions and artefacts rather than abstract departmental participation.

A business–IT disagreement is resolved by the decision owner using agreed evidence. The architect does not replace the business owner, and the project manager does not define the meaning of a measure. For plan, actuals and rescheduling causes, this separation is especially important because of the risk “excessive or insufficient granularity”.

• Business owner is accountable for production routings and confirms the action “assemble data and constraints”.
• Role: Architect. Decision object: work centres and calendars; verified step: assign roles and actions.
• Data owner decides within materials and availability; the basis is prepared through “verify the outcome”.
• For plan, actuals and rescheduling causes, the assigned role is Project manager; its control duty is to frame the problem.

Acceptance criteria

Verification of plan, actuals and rescheduling causes starts with the baseline. The sample, period, calculation rule, known exceptions and interpretation owner are preserved. After the change, the same scenario is repeated under comparable conditions; a new method or data population is documented as a separate version.

A functioning feature is not yet acceptance evidence. A user must receive the signal “material availability is disconnected from the schedule” from the agreed source, understand its lineage, make an authorised decision, execute the action through the working environment and observe confirmed actuals for work centres and calendars.

• Criterion 1 uses orders and priorities; the result is compared with the baseline using one method. Signal: Material availability is disconnected from the schedule.
• Criterion 2: Production routings; evidence needs a baseline sample, expected change, interpretation owner and source of actuals. Test signal: The plan cannot explain a delay.
• Criterion 3. Object: Work centres and calendars. Test fields: baseline, target change, source and owner. Signal: Plans are repeatedly corrected manually.
• 4. Acceptance object: materials and availability; compare the baseline sample, expected change and confirmed actuals. Test signal: Bottlenecks are found after release.

What can distort the outcome

For the risk “no feedback from execution”, define an observable condition and control decision. The record also includes the owner, response time, execution evidence and rollback rule if the control fails.

An assumption concerning materials and availability remains valid only until its review event. If the source, scope or accountable role changes, update the decision boundary and repeat the affected test.

• The risk scenario “ideal standards instead of actual constraints” is addressed through “identify the management object” and confirmed using materials and availability.
• Controlled constraint: excessive or insufficient granularity. The owner performs “assemble data and constraints” and provides plan, actuals and rescheduling causes.
• For the risk “mixing planning horizons with dispatching”, assign the action “assign roles and actions” and evidence “orders and priorities” in advance.
• Risk review starts with the condition “a scenario without priority rules”. The decision uses the action “verify the outcome” and data about production routings.

Where to begin

The first session examines one real case involving work centres and calendars. Participants bring a source document or sample, data-flow diagram, current procedure and an example of “material availability is disconnected from the schedule”.

The session ends with a decision on the next format rather than a wish list. Assign an owner and due date to “assemble data and constraints”; assign an additional test or stop condition to the risk “excessive or insufficient granularity”.

• Frame the problem is the action at stage 1. The output documents production routings.
• At position 2, the action is “identify the management object”; its result is work centres and calendars.
• 4. Acceptance object: materials and availability; compare the baseline sample, expected change and confirmed actuals. Test signal: Bottlenecks are found after release.
• Evidence item 5 describes plan, actuals and rescheduling causes, comparable test conditions and the person accountable for interpretation. Signal: Orders compete for the same resource.