Design data, configuration control and digital lifecycle models

A filename is not the complete history

A configuration identifies the particular set of product definitions and related information being considered. Configuration management keeps those identities, changes and statuses explicit. A baseline is an agreed reference description at a point in the work; it gives subsequent changes a defined starting point. The necessary scope and approval responsibilities depend on the project.

In our classroom example, geometry A is a particular model revision. Material dataset M2 contains the input values used, boundary case B1 defines the loading and support assumptions, and numerical setup N3 identifies the mesh and solver choices. Result R7 belongs to that combination. Its meaning cannot be reconstructed from a picture and “latest model” alone.

Follow the affected relationships

The dependency diagram says which inputs generated R7. If geometry B moves a hole, preserve geometry A and R7 while assessing affected quantities: local geometry, contacts, mesh, manufacturing definition, interfaces and relevant requirements. Some evidence may remain applicable with a justified rationale; other evidence may need updating. The decision should be explicit.

An approved change to a drawing does not automatically modify an already manufactured part. Record whether an item is as-designed, as-built or as-maintained and which differences are known. The digital definition and the physical object need a documented relationship. Their matching names do not establish that relationship.

A useful lifecycle model supports a question

For R7, retain the intended question, input versions and units, coordinate references, assumptions, method, numerical checks, output definition, review status and limitations. If a new calculation supersedes it, connect the records and explain why. Keep proposed, accepted and implemented changes distinguishable. A folder full of exports is not automatically an organised lifecycle record.

A digital representation may support design, manufacture, operation or maintenance by linking relevant information. Terms such as digital lifecycle model or digital twin need an explicit scope and updating mechanism. A static three-dimensional image alone does not establish a current, validated representation of a physical asset. Ask what is connected, how changes enter, how correspondence is checked and which decision the representation supports.

Read a version mismatch before accepting a result

Suppose R7 used geometry A with a 20 mm end margin. Geometry B changes that margin to 25 mm. A prototype record identifies an export of A, while its test report is labelled B. The first task is to establish what was actually built and tested; the label cannot resolve the mismatch.

If the prototype is confirmed as A, retain its observations as evidence about A under the recorded conditions. Assess relevance to B separately. Editing the report label would not make the physical test a test of B. A reliable record makes the discrepancy and its disposition visible.

Try the reasoning

1. Does a new drawing automatically update existing hardware?

   Show the answer and reasoning

   No. The design definition, actual item and modification status need explicit relationships.

2. Must every change force every test to be repeated?

   Show the answer and reasoning

   Not necessarily. Assess dependencies and applicability, document the rationale and perform the checks needed for the affected claims.

3. What is lost by replacing R7 without retaining its inputs?

   Show the answer and reasoning

   The ability to reconstruct the earlier result and identify which decisions relied on that configuration.

What to carry forward

Attach evidence to identified configurations and carry changes through the relationships they actually affect.