26 — Maintainability and through-life support

Delivery transfers a product into an operating life in which parts wear, equipment fails, requirements evolve and suppliers discontinue support. Engineering must make that life possible. Maintainability concerns the ability to perform necessary maintenance under the intended conditions. Support includes people, information, spares, facilities, tools, diagnostics, supplier arrangements and configuration control. A vehicle that can be assembled once in a factory is not necessarily a vehicle that can be repaired in service.

Support therefore begins while architecture and packaging remain changeable. A cooling-module mounting decision affects access; a connector choice affects tools and spares; a bought engine contract affects access to diagnostic information and replacement calibrations. Waiting until delivery converts these design choices into expensive constraints.

Define the support concept upstream

Establish who will operate and maintain the vehicles, where work will occur, what competence and equipment will be available, and how unavailable vehicles affect the customer's activity. These inputs shape repair boundaries and access requirements. Do not assume a field workshop has the lifting equipment, information access or supplier permissions available in the factory.

Decide which items are repaired, replaced as modules, returned to a supplier or discarded. A manufacturing module need not be the service replacement unit. The cooling assembly may be installed as one module but serviced through separate fan, hose or radiator replacements. Each service boundary needs compatible spares, removal and installation instructions, checks and an identification method that works on the actual vehicle.

The support engineer develops these arrangements with design, manufacturing, operators, maintainers, quality and procurement. The technical authority accepts design implications; commercial authority secures the necessary supply and information rights. The customer agrees its responsibilities through the applicable arrangements. A convenient internal assumption about customer workshop capability must become an explicit, tested agreement before delivery depends on it.

Design tasks as well as components

Maintainability assessment follows a task through the real installation. How does a maintainer identify the faulty item? Can adjacent equipment be protected? Can the cooling module be isolated and accessed? Are fluid and electrical connections distinguishable and reachable? What must be restored and checked before operation resumes? Answering these questions can expose a packaging problem that a geometric fit review misses.

Use NX geometry to investigate access and removal paths where appropriate, and Capital information to understand electrical connections and diagnostic relationships. These models contribute evidence; they do not establish that a person can perform the complete task under service conditions. Trial maintenance activities, competent reviews and representative demonstrations should address important uncertainties before access becomes fixed.

A repair task needs controlled inputs: applicable configuration, required competence, tools, replacement items, consumables, precautions, sequence and acceptance checks. Its output includes the restored product and evidence of what changed. Maintenance planning should also identify tasks that require specialist authority rather than inviting an improvised local repair. Where technical limits are required, obtain them from the responsible engineering definition or supplier documentation; do not invent them in the publication process.

Diagnostics should help distinguish causes that require different actions. Replacing a fan because a symptom points to cooling may leave a harness or control problem unresolved. Record observed symptoms, diagnostic steps and findings separately from the final repair. This preserves useful feedback and prevents a replaced part from automatically becoming the recorded cause of failure.

Publications are configuration-dependent instructions

Technical publications translate controlled engineering definition into information that a maintainer can use. They include identification, operating restrictions, inspection, troubleshooting, removal, installation and return-to-service instructions as appropriate. Their applicability must be tied to the supported configuration, including authorised departures and modifications.

A publication revision is not proof that every vehicle has received the corresponding modification. The maintainer must be able to select the instruction suitable for the installed connector, harness, engine and software state. Where several combinations remain permitted, the publication must make the selection conditions clear. A generic instruction that assumes the latest design can be hazardous for an earlier accepted vehicle.

Control the relationship between engineering changes and publication changes. The change assessment asks which tasks, illustrations, parts lists and diagnostic instructions are affected. Release timing matters: issuing replacement parts before the matching instructions or tools are available creates an avoidable support gap. Conversely, publishing a future instruction without clear applicability can cause premature implementation.

Supplier manuals require review for integration relevance. The engine supplier may describe bench access that does not exist in the installed vehicle. The HVAC supplier may omit vehicle-specific isolation or access steps. Preserve supplier authority over its equipment while providing the integrated instructions needed at the vehicle boundary. Contract for updates, usage rights and continued access rather than assuming delivery of an initial manual solves support indefinitely.

Spares and compatibility

A spare is useful when it can restore an intended configuration within the available support arrangements. Stock quantity alone does not establish this. Purchasing needs approved identities, permitted substitutions, storage and preservation requirements, lead-time exposure and the supporting information needed at issue. Service needs compatibility with the actual installation and evidence of any required modification.

Interchangeability may be conditional or directional. A later assembly might replace an earlier assembly only with a matching harness, bracket or calibration. Record the conditions explicitly and provide the corresponding kit or work package. Do not infer interchangeability from similar descriptions, supplier supersession notices or physical fit alone.

The bought engine and transmission deserve particular attention because replacement can introduce hardware and software differences together. Define which supplier configurations are acceptable, how their identities are obtained, and what vehicle-level checks follow replacement. Repairable items also need status control: serviceable, unserviceable, awaiting assessment and released after repair represent different permissions for use. A returned item should not re-enter available stock merely because it has arrived at the warehouse.

Connector change from factory to service

Vehicle 01 is in build, Vehicle 02 has major equipment ordered and Vehicles 03–04 remain in planning when the cooling-module supplier proposes a connector change. The engineering assessment covers the two mating sides; the support assessment asks what happens when either side later requires replacement. A factory solution that leaves an unsupported combination in service is incomplete.

Assume the disposition permits the earlier combination on Vehicle 01 and introduces a revised combination on later vehicles. Support must preserve identification and instructions for both, establish whether the earlier spare remains available, and define any approved conversion route. If a conversion requires the harness and fan connection to change together, the kit and work package must express that dependency. A stock substitution instruction must not bypass it.

The supplier HVAC and harness arrangements may introduce different repair boundaries. Determine who may alter a termination, who supplies repair instructions and what inspection establishes completion. Where local repair is prohibited or unsupported, replacement planning must account for the resulting downtime and equipment availability. These consequences belong in the technical and commercial decision before the supplier change is accepted.

Vehicle 01's maintenance record starts from its accepted delivery state. A later conversion records removal of the earlier item, installation of the replacement, connection work, any software or calibration change and required verification. Vehicle 02's order amendment does not prove that it received the revised configuration. Its delivery evidence establishes the starting point for support. Vehicles 03–04 enter service with their own actual histories even if they share the same planned definition.

Customer changes and controlled modifications

Changed payload and hot-climate requirements in DOORS are separate from the supplier connector proposal. In service they may become a modification programme, a restricted-use decision or another technically justified disposition. Assess structure, suspension, brakes and powertrain implications for payload, and cooling, HVAC, electrical demand and verification implications for hot-climate use. No single predetermined hardware solution follows automatically.

A modification package identifies the applicable units and configurations, authorised target state, required parts, instructions, software and calibration releases, checks and completion evidence. Commercial agreement addresses responsibility and cost; technical authority approves the engineering solution. The operator's access to the vehicle and ability to schedule work are necessary implementation inputs, not administrative details.

Retain a per-unit implementation status. “Kit delivered”, “work started”, “installed”, “verified” and “returned to service” represent different facts. An incomplete installation must remain visible, particularly if work is interrupted or access to the central system is lost. Change closure follows the required evidence and disposition of exceptions. This carries change control through the operating life of each vehicle.

If an action is deferred from delivery into service, transfer it to an accepting owner with the affected units, completion criteria, due event and required return evidence identified. An authorised connector conversion may be due before a specified use or maintenance event; any delivery restriction remains applicable until its release conditions are met. Closing the administrative transfer records the handover, not physical completion. Keep the implementation obligation open in the service record and return completion evidence to the change and configuration records.

Feedback that changes engineering

Field reports should identify the unit, installed configuration, operating context, observed symptom, maintenance action and evidence. Separate observation from diagnosis and suspected cause. A report stating “fan failed” may mean only that cooling was inadequate and replacing the fan appeared to help. Investigation determines whether the cause lies in the fan, connector, installation, control logic, calibration or use conditions.

Route significant findings to engineering, quality, suppliers and assurance according to consequence. Compare affected and unaffected configurations before generalising to the fleet. Repeated maintenance can reveal an access or diagnostic weakness even when every replaced component meets its specification. Support data therefore informs design improvement as well as warranty administration.

Feedback becomes controlled change when an authorised decision alters requirements, definition, maintenance policy or operating restrictions. Record the affected population and the evidence required to verify improvement. A publication correction may be sufficient for one finding; another may require containment and physical modification. Preserve the connection to the original report so that closure can be assessed against the problem actually observed.

Obsolescence, life extension and retirement

Support horizons can exceed supplier product lives. Monitor discontinuance notices, information access, specialist tools, repair capability and software dependencies as well as physical stock. Assess options such as continued procurement, qualified alternatives, redesign or revised support arrangements. Each has compatibility, assurance, storage, contractual and future-maintenance consequences. A last-time purchase delays one problem but may create preservation and ageing risks that require assessment.

Life extension is a new commitment based on actual condition, usage, configuration and supportability. An original design claim cannot simply be stretched to cover changed duty or prolonged service. Establish what must be reassessed and what evidence supports continued use. Keep limitations and required inspections connected to the individual units or applicable population.

Retirement also requires planning. Determine withdrawal authority, equipment disposition, hazardous-material handling obligations, data retention, supplier notifications and termination of support access. Specific legal and environmental requirements depend on the actual product and jurisdiction and must be established for the programme. Record completion of required actions and distinguish retired equipment from serviceable spares. Preserve enough configuration and provenance information for later investigation or contractual obligations while applying the authorised retention and disposal arrangements.

Responsibilities and scale

At major defence or infrastructure scale, millions of occurrences, years of manufacture and thousands of people produce a mixed fleet with many simultaneous states. Support structures must reflect replaceable units and service tasks without erasing their relationships to engineering and manufacturing structures. Fleet campaigns require configuration queries, accountable work packages and per-unit closure. Expensive supplier contracts must secure the information, notification, repair and continuity arrangements on which that model depends.

The reference architecture keeps customer requirements in DOORS, mechanical and electrical definition in the NX and Capital authoring environments, controlled lifecycle relationships in the Teamcenter role, and commercial and material transactions in the SAP role. Service execution, technical publications, diagnostics and software lifecycle control need explicit implementation choices. None becomes automatic because the four core platforms are present, and SAP need not own every as-maintained event.

Assign a record owner for installed state and maintenance history, define how approved definition reaches service and how actual events return, and reconcile delayed or conflicting updates. The enduring engineering objective is a supportable product whose current configuration, applicable instructions and outstanding obligations can be established when a real intervention is needed.