21 — Enterprise resource planning and production execution

A released manufacturing plan describes intended work. It does not prove that materials were available, that the right assembly was installed, or that a particular inspection passed. Production needs a controlled route from intention to action and from action to evidence. Enterprise resource planning (ERP) connects demand, supply, inventory, orders and financial consequences. Production execution controls and records the work performed on the shop floor. The two responsibilities overlap operationally, but confusing them leaves gaps in the product record.

In the utility-vehicle programme, SAP provides the selected ERP platform. This operating model assigns it responsibility for material planning, purchasing and inventory transactions, production orders and business actuals. Detailed operation dispatch, operator instructions, machine interactions and evidence capture need an explicit execution arrangement. A manufacturing execution system (MES) may supply these functions; a controlled manual arrangement may be sufficient for some low-volume work. SAP markets Digital Manufacturing separately as a manufacturing operations platform, illustrating why the name SAP alone does not settle the execution architecture. Its public overview supports this capability distinction, not a claim that this programme has licensed or configured it. SAP Digital Manufacturing.

Establish an executable handover

Manufacturing engineering supplies the manufacturing bill of materials (MBOM), the bill of process (BOP), instructions and inspection dependencies appropriate to the vehicle configuration. The MBOM organises required material for production; the BOP describes operations and their relationships. Product definition establishes what the delivered vehicle must be. Production planning turns those inputs into time-bound commitments against available resources and supply.

The handover must identify its scope. It includes the released definition and plan revisions, vehicle applicability, material requirements, operation dependencies and unresolved restrictions. Planning must know whether an item is released for procurement, installation or both. An early order for the bought engine can be legitimate while a cooling interface remains unresolved, but that does not authorise installation against an incomplete connection definition.

Teamcenter is the lifecycle environment for the controlled engineering and manufacturing definitions in this architecture. NX and Capital remain relevant authoring environments for mechanical and electrical information. SAP receives the subset needed for its assigned business functions. This is a logical division of responsibility, not a prescription for native object names or a claim of automatic transfer. The selected versions, integration products and mappings must be tested before information is relied upon in production.

The exchange should carry stable identities, revisions, applicability and release context, together with a receipt that the receiving system understood them. A material identifier translated into an ERP code must remain traceable to its technical identity. A successful network transfer is insufficient if the receiving plan loses a vehicle restriction. Reconcile both the business content and its control meaning.

Orders authorise work within limits

A production order groups authorised work, material demand, timing and actuals for business control. Its existence must not override technical restrictions. The order for Vehicle 01 can contain a released chassis stage and a blocked cooling installation stage, provided execution distinguishes them reliably. Where the system cannot enforce partial release clearly, use separate controlled work packages rather than an ambiguous overall status.

Production control owns scheduling and dispatch within the released envelope. Engineering owns technical changes to product definition. Manufacturing engineering owns changes to the method, with appropriate review of product and evidence consequences. Procurement owns supplier commercial transactions within its authority. An operator facing a mismatch needs a route to those decisions, rather than permission to infer that the order must be correct.

Order changes also need timing rules. A revised plan should not silently replace instructions already used to complete work. Preserve the instruction revision actually performed, identify outstanding operations affected by the revision, and assess completed work for rework or additional inspection. Otherwise the database can appear current while concealing a vehicle built to an earlier method.

Inventory is a physical and technical question

Inventory records establish quantities, locations and business status. Production also needs to know whether those items are usable for a particular purpose. A cooling module can be physically present yet unavailable because it awaits inspection, lacks supplier evidence, or has the wrong connector for the allocated harness. “In stock” therefore cannot be the only readiness criterion.

Receiving should establish identity at the granularity needed for control: part type and revision, supplier identity, serial or lot where relevant, and the evidence supplied. Inspect and quarantine according to the material and quality plan. Preserve the relationship between the supplier's identification and the programme's identity; relabelling must not erase the origin needed for later investigation.

Allocation reserves supply for demand. Picking selects actual material. Issue records its movement or consumption against work. Installation establishes its use at a particular vehicle occurrence. Those events may happen close together, but they answer different questions. A module issued to Vehicle 01 may remain on a trolley or be returned unused. Posting consumption does not by itself establish the installed serial number.

The same distinction applies to purchased engines and transmissions. A purchase-order line identifies what was ordered; a receipt identifies what arrived; the installation record identifies which physical unit was fitted. Software and calibration supplied with those units must be identified where they affect compatibility, performance or support. A correct mechanical part number with an unsuitable calibration is not a complete configuration match.

Substitution needs technical permission

An inventory shortage creates a business problem. It does not create technical interchangeability. An alternative item needs a defined basis for use: approved interchangeability within the product definition, an applicable change, or a bounded concession supported by the necessary authorities. Procurement can establish price and availability, but cannot establish electrical compatibility merely by selecting a supplier catalogue equivalent.

Consider the supplier's changed cooling-module connector. The proposed replacement affects a specific connection between cooling module and harness. Engineering checks the pair and its surrounding design; manufacturing engineering checks installation and inspection; quality checks required evidence; procurement deals with the supplier commitment. Once authorised, planning allocates compatible combinations and prevents accidental mixing.

Vehicle 01 may retain the original module and harness arrangement if that remains its approved configuration. Vehicle 02's existing orders need supplier confirmation and any contractual amendment. Vehicles 03 and 04 may use the new arrangement in their released plans. A generic replacement rule applied to all outstanding demand could undo those carefully differentiated decisions. Applicability must survive into allocation and dispatch.

Keep supersession and actual use distinct. A new preferred item may replace an old item for future purchasing without requiring every installed instance to be removed. Conversely, a mandatory change can require action on already installed equipment. The execution system must receive the specific implementation instruction rather than infer either outcome from an item-master status.

Capture work as evidence-bearing events

An execution record should identify the vehicle, the operation and instruction revision, the responsible person or equipment, relevant material instances, results and exceptions. Record the time and context needed to interpret the event. Use direct measurements where the procedure requires them; a tick indicating completion should not replace required values or observations. Do not collect detail merely because a screen permits it.

For the cooling module, record mechanical installation separately from fluid connection completion and electrical checks. Link each connection to its endpoints and vehicle context. A common hose type can occur in more than one position; the type identity alone cannot tell an investigator which joint was completed. A changed installation sequence may also alter inspection access, so the instruction revision matters alongside the component revision.

Where electronic collection is unavailable, controlled travellers can carry the same responsibilities. They need identifiable issue, legible entries, exception handling and reconciliation into the enduring record. Scanning an incomplete traveller does not make it complete. If the shop loses system access, define which work may continue, how local records are protected, and who reconciles duplicate or conflicting entries before further release.

Correct records by preserving the original event and the reason for correction. Backdating a revised instruction to make it appear applicable to completed work destroys the evidence needed to judge that work. If the physical state is uncertain, conduct a survey or repeat the necessary inspection. A database repair cannot stand in for an engineering finding.

Actuals and physical configuration

Labour, material consumption, scrap and completion transactions support cost and planning. Installation, removal, replacement, software loading and accepted inspection records support physical configuration and acceptance. Some systems may hold both classes, but authority must be assigned explicitly. SAP is not automatically the owner of every as-built record because it owns production orders.

A coherent arrangement can keep financial and inventory actuals in SAP, detailed execution evidence in an MES or controlled record service, and a reconciled physical configuration index linked through Teamcenter or another designated configuration service. The implementation must nominate the authoritative record for each fact and define how contradictions are resolved. Copies may support use elsewhere, but they must retain origin and revision context.

Order closure should distinguish administrative completion from product readiness. A financially settled order may still have an unresolved concession or missing test report. A technically acceptable vehicle may have outstanding commercial reconciliation. Use separate conditions and owners so one closure cannot imply the other. The delivery release then checks the relevant evidence across those boundaries.

Customer change during execution

The customer raises revised payload and hot-climate requirements in DOORS while production continues. Requirement revision, contractual agreement and technical implementation are separate events. Planning first identifies exposed orders, material and work packages. Engineering establishes the solution and applicability; commercial authority establishes changed obligations and supplier commitments. Production stops or protects only the affected work boundaries, rather than either freezing everything or proceeding blindly.

Vehicle 01 needs an actual-state assessment, including installed equipment and completed connections. Vehicle 02 needs an order and supplier assessment. Vehicles 03 and 04 need updated planned demand. The resulting implementation plan can include rework, cancellation, return, new procurement, revised instructions and additional tests. Track these actions to each vehicle, including evidence that an action was unnecessary where the assessment justifies that conclusion.

The change is not closed because the MBOM was revised or an order was amended. Closure requires reconciliation of intended configuration, executed work and accepted evidence for each affected unit. A blocked supplier acknowledgement or missing retest remains visible as an implementation exception, with an owner and an explicit delivery consequence.

Scale makes reconciliation essential

At millions of occurrences and thousands of participants, informal reconciliation fails. Over years of manufacture, older revisions coexist with newer plans, suppliers change, and units progress at different rates. Expensive contracts can lock in supply before installation detail is final. Stable identity and vehicle applicability must therefore travel with every meaningful transaction.

Batch exchange and delayed connectivity may be acceptable where the work can tolerate them. The important choice is the maximum permitted delay and the action when information is stale. Prevent duplicate postings through controlled transaction identity, detect rejected exchanges, and reconcile totals with configuration-sensitive exceptions. These are implementation requirements, not assumed connector features.

A useful daily view shows released work, usable material, blocked operations and missing evidence separately. It allows production to recover schedule while preserving the technical boundary of its authority. Quality and nonconformance explains how exceptions found during that work receive a defensible disposition.