OpenBOM - Revisions and Change Management

Change Management is an essential part of lifecycle control.

In OpenBOM there is a mechanism to help you manage the lifecycle

Change history
Revision
Change request and approval.

OpeBOM automatically saves the data and captures the history of changes. You don’t need to worry about it. You can always navigate to the history command and see the list of changes in reverse chronological order including the information about who made the changes and when they happened.

In the Bill of Materials, changes are made in the so-called “Latest State”. This is the state you can edit. When you approach a specific maturity state, you can use the Save Revision command, which saves the snapshot of the latest state and will be preserved as an immutable record with the revision number and additional comment.

You can create multiple revisions and always see the history, navigate back and create revision comparison reports.

To create a formal change process, OpenBOM provides a change request and approval mechanism. This mechanism includes the list of people with change approval rights. In this case, the Save Revision command is replaced with Change Request, and once the change is approved the new revision is created.

OpenBOM has a mechanism to manage revisions in structures. It includes a bottom-up and top-down revision change process. Read more in our online documentation on how to manage revisions and change management processes.