Why BOM Control Matters in Long-Lifecycle Industrial Platforms
A qualified configuration is only reproducible for as long as its bill of materials is controlled. This note describes what BOM control covers, what a component change may invalidate and how change is managed during a programme.
Engineering Context
A commercial part number identifies a product against its published specification. It does not necessarily identify a fixed internal component combination. In consumer supply chains, controller, memory die or firmware revision may change during the product life while the specification and the part number remain unchanged.
For an industrial platform, the qualified configuration is the object under control. Where the internal composition changes without notification, the configuration recorded at qualification and the configuration in the field are no longer demonstrably the same.
What BOM Control Covers
A controlled bill of materials records the component combination associated with a qualified configuration and defines the procedure by which that combination may be changed.
- Component identification. The memory or storage components, controller where applicable and firmware revision associated with the qualified configuration.
- Configuration record. The capacity, organization, rated operating point and module marking under which the configuration was approved.
- Change procedure. The route by which a proposed change is reviewed, documented and, where required, requalified before it reaches production material.
Configuration control does not mean that no component may change during a programme. It means that a change is agreed in advance under a defined procedure rather than identified after delivery.
What a Component Change May Affect
| Item | Assessment |
|---|---|
| Platform compatibility | Whether the existing qualification record remains applicable to the revised configuration |
| Documentation | Whether product documentation and configuration records require revision |
| Installed base | Whether the change introduces more than one qualified configuration across deployed units |
| Requalification | Whether the scope of the change requires renewed platform validation |
The assessment output determines the applicable action. A change confined to a component with equivalent electrical and functional characteristics may require documentation revision only; a change affecting organization, firmware or operating point normally requires renewed evaluation.
Programme Considerations
- Programme period. The expected production and service period determines how long the configuration must remain reproducible.
- Spare units. Maintenance and spare requirements may extend beyond the initial production period and are considered when the configuration is defined.
- Generation transitions. Component availability changes over a multi-year programme; transition planning is reviewed against the expected lifecycle.
- Second sources. Where an alternative is approved, it is qualified as a defined configuration rather than treated as an equivalent substitution.
Applicable Limitations
Configuration control applies within the agreed programme scope and period. It does not constitute a guarantee of indefinite component availability, and it does not remove the need to plan for generation transitions within the expected lifecycle.
Categories of Change
Not every change carries the same qualification consequence. Separating changes by category makes the review proportionate and avoids treating a documentation update in the same way as a change of module organization.
- Documentation change. Product documentation is revised while the configuration itself is unchanged. Records are updated and the qualification result remains applicable.
- Equivalent component change. A component with equivalent electrical and functional characteristics is introduced. Compatibility review determines whether renewed validation is required.
- Configuration change. Organization, declared operating point or firmware behaviour changes. Renewed platform validation is normally required before the change reaches production.
- Generation transition. The programme moves to a different memory or storage generation. This is planned as a new qualification rather than as a substitution.
Records That Support Configuration Control
Configuration control depends on records that can be checked later. The minimum useful set identifies the approved configuration, the qualification result associated with it and the change history applied during the programme.
Where a supplier and a customer hold separate records, both should reference the same configuration identifier, so that a question raised years later can be resolved without reconstructing the history from delivery documents.
A Programme Timeline View
Configuration control is easier to reason about when mapped onto the programme timeline. Different questions arise at each stage, and the record required at each point is different.
- Design-in. The configuration is selected and the qualification scope is defined.
- Qualification. The configuration is evaluated and approved for the programme.
- Production. Material is verified against the approved configuration, and any proposed change is assessed before it reaches production.
- Service and spares. Replacement material is supplied against the same configuration, and generation transitions are planned rather than absorbed reactively.
Points to Confirm With a Supplier
The questions below are the practical form of configuration control. They are worth resolving during supplier selection rather than after the first change has occurred.
- How is a proposed change communicated, and at what point? A change identified in advance can be assessed; a change identified after delivery has to be investigated.
- Can the same part number ship with a different internal configuration? A clear answer matters more than which answer it is.
- Can the approved configuration be confirmed in writing for the programme? This is the record a later review will refer back to.
Engineering Summary
Configuration control is not a performance characteristic. Its function is to keep the configuration behind an existing qualification record reproducible for the agreed period, so that a change is assessed before it reaches production rather than identified afterwards in the field.
Related SIMORCHIP Resources
Related Technical Insights
Production Verification vs Platform Qualification
Production verification confirms module-level manufacturing and functional requirements. Platform qualification evaluates compatibility and stability against the target system configuration. These processes serve different purposes and should not be treated as interchangeable.
Read Technical Note →Sample Verification, Validation and Failure Analysis in Design-In
Design-in verification, platform validation and failure analysis address different questions at different stages of a programme. This note describes the objective of each activity and the point at which it applies.
Read Technical Note →Why Platform Compatibility Cannot Be Determined by DDR Generation Alone
Identical DDR generation and nominal data rate do not, by themselves, establish compatibility with a target platform. Module organization, memory-controller behaviour, firmware implementation and board configuration may all affect the qualification result.
Read Technical Note →Project Enquiries
Provide the target platform, required memory or storage configuration, operating conditions and expected programme lifecycle. SIMORCHIP engineering will review the applicable product configuration and qualification scope.