Change Propagation in Technical Information

Changes Throughout a Project

Managing changes is an integral part of any industrial project. Components, requirements, design solutions or client input may change as the work progresses, and each change must be reflected in the relevant deliverables while maintaining consistency with what has already been developed. Even a relatively minor change, such as updating a component code or revising a standard detail used for a specific weld or assembly method, may therefore affect a wider part of the project documentation.

Complexity increases when the same information appears in multiple parts of the project. In these situations, the affected deliverables must be identified and updated, and the information must remain consistent in documents intended for manufacturing or assembly. Change management therefore involves both the technical assessment of the change and the control of change propagation throughout the documentation.

This dynamic makes it useful to treat information management as part of the engineering process. The way technical information is organised depends on the complexity of the project, the number of relationships between deliverables and the consequences that inconsistencies may have on later project phases.

Change Propagation

In a traditional project workflow, changes may pass through several stages before all affected deliverables are updated. The project manager receives new input from the client and passes it on to the engineering team, who must interpret the change, assess its implications and identify the documents that need to be revised. When the number of deliverables is limited and the relationships between pieces of information are easy to identify, this process can be managed by direct checking.

As the project grows, however, the number of dependencies to be considered also increases. A component code may appear in several deliverables, while a standard detail for a weld or assembly may be referenced in different parts of the documentation. Managing the change then requires both an understanding of the new technical content and the ability to trace every location where the original information has been used.

A significant part of this activity depends on the knowledge built up by the people working on the project. Designers must recognise the relationships between deliverables, identify where information has been replicated and verify that the required updates have been completed. This approach can be appropriate when the number of documents and dependencies remains limited, but it becomes increasingly demanding as the project structure grows more complex and the amount of shared information increases.

The Risk of Inconsistency

When the same information is present in several deliverables, multiple points have to stay consistent as the project evolves. Each revision therefore requires control over both the modified content and its distribution throughout the documentation. As the number of affected deliverables increases, a document may be unintentionally left out of the update, particularly when the effects of a change reach parts of the project that are not immediately apparent.

The path the information follows before it is implemented adds a further difficulty. A change may pass through several people and require clarification, additional information or further corrections along the way. It therefore becomes necessary to keep the current version of the information clearly identifiable and to know which deliverables have already been updated on that basis.

Internal reviews can identify many inconsistencies before documents are released, provided there is enough time and the conditions allow a thorough check. When inconsistencies reach manufacturing or assembly, their impact becomes tangible: an outdated component code or a construction detail that does not match the rest of the documentation can affect work carried out from those deliverables. Information consistency therefore contributes to the quality of the process through which engineering decisions are carried through to implementation.

The Role of Documentation

Drawings, specifications and other technical deliverables play an essential role in industrial projects because they formalise engineering decisions and convey the information required for subsequent activities. Data-centric approaches and dedicated information management systems provide additional ways of organising this content, while documentation remains an integral part of the overall process.

Information contained in a single document can be managed within that document with relative ease. When the same information is reproduced manually in several locations, however, each revision requires all occurrences to be kept aligned and checked, so that none remains tied to a previous version.

The informational complexity of a project therefore also depends on the relationships between its documents. Two projects with a similar amount of documentation may require different management approaches when one of them repeatedly reuses the same data across multiple engineering deliverables. In these situations, data-centric approaches can provide a more structured way of managing shared information and, where appropriate, reduce the need to update the same content manually in several locations.

Critical Information

Determining which information requires a more structured approach begins with understanding the role it plays within the project. Some information is used locally and remains tied to a specific deliverable, while other information runs through several parts of the design and may affect documents used for manufacturing, assembly or subsequent activities. The latter requires greater attention because a change can have effects in several places.

A component code used in several deliverables, a recurring standard detail or technical information shared across multiple documents are examples of data for which consistency becomes particularly important. Their criticality can be assessed by considering how many deliverables use the information, the likelihood that it will change during project development, the consequences of a potential inconsistency and the difficulty of manually tracing every location in which it appears.

This assessment helps focus control on the information that has the greatest influence on the project and helps determine the level of structure appropriate for managing it.

The Level of Structure

PDM and PLM systems provide ways of organising information, documents and revisions in environments where the volume of data and relationships makes predominantly manual management increasingly demanding. For organisations developing complex projects, these systems can therefore be an important part of the infrastructure used to keep engineering information under control.

Their use also requires procedures, classification criteria and shared methods for creating, storing and updating information, together with system configuration and user training. The appropriate level of structure must therefore be evaluated in relation to the characteristics of the organisation and the projects it manages. In a large industrial organisation, these requirements may be proportionate to the amount of information to be controlled, while in a project of limited scope they may impose a management burden that exceeds what the project actually requires.

Even a highly structured environment requires clear organisational criteria. Duplicate documents, similar content stored in different locations or difficulty in finding material that already exists may occur even when advanced systems are in place. Such tools support information control, but their effectiveness also depends on the rules used to organise and manage data and documents.

A Scalable Approach

For organisations that work with a wide range of companies and projects, the level of structure can be adapted to each project. A small assignment involving a limited number of deliverables has different information management requirements from a multidisciplinary project in which a large amount of information is shared across documents, people and stages of work. An initial assessment of project complexity therefore makes it possible to determine which information requires greater control and what kind of organisation suits it.

The process begins by identifying critical information, then assessing how widely it is distributed throughout the documentation and considering the consequences of potential inconsistencies before selecting the appropriate tools. For simpler projects, orderly document management combined with clear revision control may be sufficient. In intermediate cases, recurring information can be concentrated in dedicated sources, reducing the number of copies that need to be maintained manually. In more complex environments, PDM or PLM systems can provide suitable tools for managing a larger volume of data and relationships.

The resulting level of structure therefore follows from the actual requirements of the project. This approach makes it possible to adapt the method to the scale of the assignment and to the organisation involved, while keeping the management effort proportionate.

Managing Information

Change management makes the information relationships built up throughout a project particularly visible. When a piece of information changes, it becomes necessary to understand which deliverables depend on it, which subsequent activities may be affected and which version should be considered current. Making these relationships more explicit makes updates easier to control and reduces the need to reconstruct dependencies each time by relying mainly on the memory of the people involved.

The knowledge and responsibility of the designer remain central, because interpreting a change, assessing its implications and verifying its implementation are inherently engineering activities. An appropriate information structure supports this work by making the relationships between deliverables easier to identify and by making it easier to maintain their consistency throughout successive revisions.

Information management can therefore develop gradually as the project evolves, while keeping the transfer of engineering decisions from design to manufacturing and assembly consistent.