Model-based engineering enterpriseSearch the book
In this chapter

17 — Supply-chain strategy and technical procurement

Buying a component transfers work across an organisational boundary. It does not remove the engineering needed to decide what is required, whether the supplier can provide it, how it will fit and what evidence will demonstrate suitability. A low purchase price can conceal expensive integration, missing data or an inability to support the product after delivery. Supply-chain strategy therefore begins with the product and the business capabilities needed to deliver it.

The four-vehicle programme buys its combustion engine and transmission, makes chassis and mounting brackets internally, and uses supplier-designed heating, ventilation and air conditioning (HVAC) and harness assemblies. These boundaries place different responsibilities on procurement. Buying a catalogue engine requires selection and integration. Buying a designed harness also requires agreement about design inputs, interface ownership, manufacturing data and change control. Neither transaction can be described adequately by a part number and delivery date alone.

Decide what the business must retain

A make-or-buy decision compares complete ways of obtaining an outcome. Internal manufacture requires skills, equipment, capacity, process definition and inspection capability. External manufacture requires supplier capability, a suitable technical package, commercial arrangements, logistics and effective technical oversight. Compare these alternatives over the required lifecycle rather than comparing the supplier quotation only with internal material cost.

Retained capability matters particularly where the business must integrate competing constraints. A supplier can design the HVAC package while the vehicle business retains authority for overall thermal performance, packaging, electrical capacity and customer acceptance. Outsourcing all detail design does not create an external owner for decisions spanning several suppliers unless that responsibility is deliberately assigned and supported by information and authority.

The engine and transmission illustrate the limits of buying mature products. Their established designs can reduce development work, but suitability still depends on installation, duty, cooling, controls, maintenance access and operating restrictions. The selected combination must be assessed in the vehicle context. A supplier’s reputation is useful evidence of capability; it is not evidence that this particular installation meets the applicable requirements.

For the cooling module, compare purchasing a complete module with buying radiator, fan and hoses separately. A complete module may simplify internal assembly and place more integration within one supplier’s scope. It may also constrain packaging, complicate replacement sourcing or hide component changes. Separate purchases offer different control but leave the vehicle business responsible for more interfaces. The decision should identify who owns mechanical attachments, fluid interfaces and electrical compatibility in either arrangement.

Qualify capability for the actual work

Supplier qualification asks whether a supplier can perform a defined scope under the expected conditions. It should examine relevant technical competence, manufacturing capacity, process control, inspection capability, data delivery, change discipline and continuity of supply. Commercial resilience and dependence on lower-tier suppliers also matter. Qualification is specific enough to reveal the risks of the proposed work; it is not a permanent declaration that every product from the company is suitable.

Separate supplier qualification from product approval and shipment acceptance. A capable harness supplier can still submit an unsuitable design. An approved harness design can still be manufactured incorrectly. A conforming shipment can still arrive too late. These are different problems with different evidence and owners. Procurement coordinates the overall supplier relationship, engineering judges technical suitability and quality specialists establish appropriate product and process assurance with manufacturing and engineering.

A new supplier may require staged qualification. Start with evidence review and a representative sample, then demonstrate critical operations and assess initial deliveries. The extent should follow consequence and uncertainty. Routine commercial material and a bespoke safety-relevant package need different scrutiny. No universal audit frequency or certification requirement follows from the fictional vehicle setting; applicable contractual and sector obligations must be identified separately.

For supplier-designed items, examine whether the supplier can maintain configuration records and communicate changes before shipment. A supplier that produces good prototypes but cannot identify which connector revision was installed in each delivered harness creates a problem during series manufacture and service. Where lower-tier substitutions are possible, establish which changes require notification or consent and how their effects will be assessed.

Specify the purchase package

The technical package should explain what is being purchased, its applicable revision or baseline, quantities and delivery expectations, interfaces, required evidence and permitted alternatives. Identify whether the supplier must build to controlled definition, design to requirements or supply an existing product with declared limits. Ambiguous combinations cause disputes: the supplier may price manufacture only while the buyer expects responsibility for design adequacy.

For the harness, inputs include endpoint and circuit requirements, connector interfaces, routing constraints, environmental conditions and applicable vehicle variants. Outputs can include the supplier’s controlled design, interface data, inspection evidence and identification of delivered assemblies. Decide which data the vehicle business needs for integration, acceptance and support. Do not demand every internal supplier working document without a reason; equally, do not defer essential maintenance or change information until after the contract has been placed.

For the engine, obtain enough information to assess and plan installation: physical interfaces, service envelopes, relevant operating limits, connection requirements and evidence supporting the selected use. Where detailed proprietary information is unavailable, agree a usable alternative such as controlled interface data or a supplier-backed assessment. Record the residual limitation. The absence of a full internal model does not automatically prevent integration, but an undocumented assumption about a critical interface is not an adequate substitute.

A procurement package must name the authority that can approve alternatives. A buyer can negotiate price without having authority to declare a different material or connector technically equivalent. An engineer can assess equivalence without having authority to vary the contract. Establish both routes before urgency makes an informal email the effective control mechanism.

Commit to long-lead equipment deliberately

Vehicle 02 already has major components ordered while Vehicles 03 and 04 remain in planning. This creates an important distinction between an evolving design and an existing purchase commitment. The engine order may be commercially firm while some installation details remain under development. The programme must know which decisions are fixed by that order and which remain open.

An early order can be sensible where the selected equipment is stable across credible design outcomes. Where uncertainty remains, negotiate options appropriate to it: reserving capacity, purchasing common material, delaying variant selection or defining a later configuration confirmation point. Such arrangements have commercial consequences and require supplier agreement. They are alternatives to examine, not rights that exist automatically.

The release decision should identify the information used, outstanding assumptions, cancellation or alteration exposure, storage implications and the latest practical change point. Procurement needs a configuration-specific demand signal. “Buy four engines” is incomplete if different accepted requirements may lead to different equipment or accessories on later vehicles.

Long lead time includes engineering review, supplier development, qualification, transport and incoming acceptance where those activities are needed. Promised factory completion is not the same as material available for use. The integrated plan should expose those intervals and their uncertainty. It should also consider spares and replacement routes where a failed first delivery would otherwise halt the build.

Manage risk beyond the first-tier supplier

A second source reduces dependency only if it is technically and operationally usable. The alternative may require different interfaces, qualification work, tooling or acceptance evidence. Two suppliers dependent on the same lower-tier component may share the same disruption. Treat resilience as a product and process problem as well as a purchasing problem.

For the bought transmission, establish the consequences of a changed delivery date or discontinued variant. Can another configuration be used? What design work and test evidence would that require? Would the alternative affect controls, mountings, cooling or service equipment? A contingency that exists only as a supplier name cannot support a credible recovery schedule.

Inventory can absorb some disruption but also locks money into a configuration. Buying additional cooling connectors before a pending interface decision may create obsolete stock rather than resilience. Connect stock strategy with technical stability, physical identification, preservation requirements and likely future demand. Where shelf life or storage conditions matter, obtain and apply the relevant product information rather than assuming indefinite usability.

Track risk through observable actions: confirmation of capacity, accepted interface data, completion of qualification or establishment of a usable alternative. A supplier’s reassuring progress statement may be useful context, but significant commitments need evidence proportionate to their consequences. Where evidence cannot be obtained, expose the uncertainty in programme decisions rather than presenting confidence as a substitute.

Work through two different changes

The customer changes the required hot-climate operating conditions in DOORS. Engineering assesses cooling demand, HVAC performance, electrical demand, packaging and verification implications. Procurement asks suppliers for affected limits, alternative equipment, cost and lead-time consequences. These enquiries support disposition of the customer change; they do not themselves authorise revised requirements or purchase orders.

For Vehicle 01, establish the actual equipment already fitted and the work needed for any retrofit. For Vehicle 02, determine whether equipment is merely ordered, in manufacture or ready for shipment. For Vehicles 03 and 04, evaluate a changed sourcing package against the revised technical outcome. A blanket instruction to “use the new hot-climate equipment” would ignore these different states and could create unusable deliveries.

Separately, the cooling-module supplier proposes a connector change. Obtain the old and proposed interface definition, reason, affected supplier revisions, planned introduction and disposition of stock. Check the mating harness, electrical characteristics, routing, service information and assembly instructions. A connector that fits physically may still have incompatible pin allocation or other relevant characteristics. Do not infer interchangeability from appearance or supplier part-number similarity.

The decision may retain the existing connector for Vehicle 01, amend the Vehicle 02 order and introduce a new module/harness combination on Vehicles 03 and 04. That outcome requires explicit applicability, compatible mating definitions and controlled supply. Incoming inspection must distinguish the configurations, and stores must prevent unintended substitution. The customer hot-climate change and supplier connector change retain distinct causes, decisions and evidence even if their implementation is coordinated.

Connect procurement to controlled information

A part identity denotes a defined kind of item. A revision records a controlled state of its definition. An occurrence describes a use in a product context, while a physical instance is the actual supplied object. The cooling fan used on Vehicle 01 and the fan used on Vehicle 03 may share a part identity yet have different serial identities and possibly different applicable revisions. Procurement and receiving records must preserve the distinctions required for acceptance and later support.

The intended architecture uses Teamcenter for controlled product context and SAP for procurement and enterprise execution. NX and Capital contribute mechanical and electrical definition. The exchange must specify identifiers, revisions, units, applicability, approved alternatives and change status. Receipt of a new technical revision must not silently amend an existing commercial order, and a purchase-order amendment must not silently approve a new design.

Supplier portals, data exchange, inspection and execution capabilities depend on selected products and configurations. The operating model needs explicit acknowledgements and exception handling regardless of implementation. If an order references an obsolete package, identify who resolves the mismatch and prevent it becoming an unnoticed build instruction.

Scale the boundary management

For four vehicles, the same people may negotiate, review and inspect a supplier package. On major defence and infrastructure programmes, thousands of people may manage major supplier contracts over many years, with millions of product occurrences and several supplier tiers. Common identifiers, consistent change notification and delegated authority become essential to maintaining a coherent product.

Scale the depth of oversight to consequence, novelty and dependency. Central teams can govern critical interfaces and common supplier risks while local teams manage routine purchases within defined authority. The objective is a supply chain that can demonstrate what it has promised, what it has delivered and which configuration the business is entitled and able to use. The next chapter develops the technical and contractual controls that make those promises enforceable and operationally useful.