08 — Design engineering and analysis

From required behaviour to a manufacturable definition

The engineering question is whether a particular design can deliver the required behaviour and be manufactured, assembled, inspected and supported. A geometrically complete cooling module can still lack an adequate airflow path, an accessible hose connection or a justified mounting arrangement. Detailed engineering therefore includes calculations, material selection, tolerances, supplier assessment and test planning as well as computer-aided design (CAD).

Manufacture overlaps design, so each commitment needs a defined technical basis and accountable authority. The discipline lead owns technical adequacy; the system authority owns compatibility with vehicle requirements and interfaces; manufacturing engineering confirms process feasibility; quality identifies necessary inspection evidence. Programme and commercial authorities accept schedule and purchasing exposure. A designer cannot transfer those decisions simply by releasing geometry.

Customer requirements remain in DOORS. Engineers record the requirement baseline used for each assessment and any derived constraints. A proposed hot-climate change is an input to impact assessment before it becomes an authorised design obligation. The assessment identifies which operating conditions, vehicle configurations and acceptance criteria change. Unclear duty cycles require customer clarification or an explicit bounded assumption, with an owner and a date for resolution.

Alternatives and analytical claims

A trade study compares feasible ways of satisfying a need against declared criteria. For the cooling module, alternatives might change radiator packaging, fan capability, airflow management or control strategy. The comparison includes electrical demand, service access, mass, supplier availability, installation sequence and verification effort. It records rejected alternatives and the conditions under which a rejected alternative could become preferable. Numerical scoring cannot replace judgement when the underlying estimates have different uncertainty or safety consequences.

An analysis model is a deliberately simplified representation used to answer a question. Its record should identify the question, product configuration, input sources, units, boundary conditions, material properties, simplifications, solver or calculation method, results and limitations. These fields describe the information needed to assess the result; storage depends on the analysis environment. A bracket stress result using a rigid mounting assumption cannot automatically justify a flexible chassis installation. A thermal calculation using clean airflow cannot establish performance under a different obstruction condition.

Model verification asks whether the model and calculation have been implemented and solved adequately for the intended task. Engineers examine equations, units, mesh or discretisation sensitivity where relevant, convergence, boundary conditions and comparisons with independent calculations. Model validation asks whether the representation is sufficiently faithful to the physical behaviour for its intended use. Suitable test comparisons and uncertainty assessment support that judgement. Neither label establishes that every vehicle requirement has been verified or that the delivered vehicle is valid for its intended operation.

The analysis lead proposes the method and its domain of use. A competent checker examines assumptions and results with independence proportionate to consequence. The design authority accepts the engineering conclusion, including limitations. Where evidence is insufficient, the output is a restricted decision: for example, proceed with a representative prototype while withholding production approval for the altered bracket. An attractive simulation plot is not an approval record.

Reassess the assumptions before reusing the result

Consider a cooling assessment based on the original ambient conditions, a particular fan characteristic and an assumed airflow restriction. The customer requests hotter conditions. The analyst compares the requested case with the recorded domain of the earlier assessment. Outside that domain, the favourable result cannot establish compliance merely because the radiator geometry is unchanged. The model may remain useful, but needs justified new inputs and a new conclusion.

If the method and relevant test comparisons cover the revised range, updated calculations may support part of the argument. If airflow or fan behaviour is unsupported in that range, further supplier evidence or testing is needed before relying on the prediction. Conservatism must have an understood direction: an assumption conservative for bracket loading need not be conservative for thermal performance.

The independent supplier connector change poses a different question. Thermal evidence may remain applicable if fan behaviour and installation remain demonstrably unchanged. Changed electrical losses, control signals or routing could undermine that judgement. Record which inputs are affected and why the remaining evidence can be reused. For Vehicle 02, permission to order equipment before this work is complete must remain distinguishable from acceptance of its final performance.

Margins and product definition

A margin expresses the relationship between an assessed capability and an applicable demand or limit. Its meaning depends on the quantity, uncertainty, operating envelope and governing method. The programme should define the calculation and acceptance basis rather than apply one unsupported percentage to all disciplines. Tolerance, degradation, variability and modelling uncertainty may affect the assessment differently; counting the same uncertainty twice can distort a decision just as omitting it can.

The payload change illustrates why a local calculation is insufficient. Increased payload can change structural loading, suspension behaviour, braking demand, powertrain duty and thermal performance. The system authority coordinates assessments and their assumptions. The bracket designer receives an approved load envelope rather than inventing one from a desired payload figure. If that envelope remains provisional, any manufacturing commitment identifies the reserved capacity, possible rework and authority accepting exposure.

Product definition states what must be made and accepted. Analysis explains why that definition is expected to work. Keeping them linked but distinct allows a calculation to be corrected without silently altering a manufacturing requirement. It also prevents a test team from treating an analytical assumption as a specified characteristic.

NX supports adding product and manufacturing information (PMI) to CAD models for model-based definition; that capability does not establish completeness or downstream interpretability. Siemens describes the NX PMI workflow. The policy is to identify the authoritative geometry, dimensions, tolerances, material and process specifications, applicable notes and inspection characteristics as one controlled definition package. Where drawings remain necessary, the package declares their authority and precedence. Manufacturing and inspection must receive a representation they can use and whose interpretation has been checked.

BS 8888 concerns technical product specification and documentation. BSI identifies a 2025 edition; detailed application must use the edition selected for the programme and its relevant referenced standards. This chapter does not reproduce its provisions or assert conformance. BSI's edition listing supports the scope and edition identification, not a particular tolerance prescription. Geometrical specification does not itself validate thermal performance, approve a manufacturing process or establish lifecycle governance.

Release while other work continues

Vehicle 01 is in build, Vehicle 02 has major equipment ordered and Vehicles 03–04 are being planned. Suppose the hot-climate assessment requires a different fan and a revised mounting bracket. The team identifies the affected module occurrence, both mounting interfaces, electrical connection, airflow envelope and service removal path. It checks whether the existing bracket can remain, whether supplier equipment already ordered can be modified and which evidence must be repeated.

The bracket may be released for manufacture before the entire vehicle is complete if its loads, interfaces, material, acceptance characteristics and permitted use are sufficiently established. The release record identifies the definition revision, intended units, supporting analyses, unresolved dependencies and authorised limitations. If fan selection still affects loads or clearances, the bracket commitment either reserves a justified envelope or remains restricted. Programme urgency does not make an unresolved interface stable.

Design checking includes fit and interference, tolerance accumulation, fastening and connection access, material compatibility, environmental exposure, installation sequence and maintainability. The checker follows the relevant failure mechanisms rather than merely checking that each drawing field is filled in. A cooling connection needs defined endpoints, sealing intent and assembly constraints; manufacturing planning later turns these into operations, and execution records establish what was actually completed.

At major defence or infrastructure scale, millions of occurrences cannot each be checked through informal recollection. Reusable analysis methods, controlled input libraries, configuration-specific queries and automated checks help identify affected populations. Thousands of people working over years require preserved assumptions and reproducible evidence because the original analyst may no longer be available. Automation still requires accountable method ownership and exception handling.

The system mapping places mechanical definition in NX, lifecycle-controlled identities and release relationships in Teamcenter, customer requirements in DOORS, and procurement and production commitments in SAP. Analysis authoring and simulation management remain implementation choices. Links must preserve the assessed configuration and input versions; an editable URL to the latest model is insufficient evidence. Integration mechanisms and licensed modules require validation against the selected deployment.

This chapter establishes engineering decision content. Electrical integration develops the neighbouring discipline, and configuration control explains how the resulting definitions apply to particular units.