2026-09-29 4
Engineering changes may affect models, drawings, workmanship and inspection documents simultaneously. Updating only one of the files may easily cause inconsistencies in subsequent stages.
Models, drawings, processes, and inspection documents may have different numbers, but they must all refer to the same valid product state. This can be achieved through configuration lists or document association tables, thereby avoiding situations where different departments use seemingly the most up-to-date documents that do not match each other.
Changes can affect not only unmanufactured parts, but also purchased components, work-in-process items, and completed accessories. The review should clarify how each state will be handled, and whether it is necessary to notify relevant parties. Simply marking the effective date is often insufficient to address issues related to on-site boundaries.
The change review should clearly define the applicable scope, the time of effectiveness, and how work-in-process items will be handled. For critical interfaces, it is also necessary to check the related accessories simultaneously.
After the documents are released, it is important to ensure that the old versions are discontinued and that the new version can be actually implemented. When dealing with procedures, tools, or inspection lists, these should also be switched accordingly. On-site feedback can help identify situations where the documents have been updated, but the operating conditions are not yet ready.
Recording the reasons for the change, the impact analysis, and the approval conclusions helps to explain why the current plan was chosen later on. When new problems arise, this information can reduce the need for repeated investigations. The key to effective change management is ensuring that design intentions and product states remain consistent.
It is assumed that the drawings have been updated, but the on-site processing procedures and inspection lists still use the old version. Even if each person operates according to the documents they hold, inconsistencies can still occur in the end. When changes are implemented, it is necessary to list the affected items and confirm that the switch has been completed for each item. For parts that have already been manufactured, it is also important to specify the applicable scope to avoid mixing together different requirements.
Notifying people is just one step in the information transfer process. It is also necessary to ensure that the handling of documents, procedures, tools, and work-in-process items has been properly established. The execution status should be recorded as evidence of completion, rather than just assuming that a message has been sent as sufficient proof.
After the release is completed, it is important to ensure that the correct version is available on-site, and that necessary records of the changes are kept, allowing for subsequent tracking and review.
