OpenBOM Change Management Demo – Change Order and Change Request

OpenBOM is a cloud-based PLM platform designed to streamline the product development process. One of the critical features of OpenBOM is its Change Management functionality, which allows users to efficiently handle any changes to their product definition throughout the product development cycle. In my previous articles, I provided an overview of change management and also demonstrated revision control.

Check these articles before moving forward:

• Change Management in OpenBOM – Revision, Change Request, and Change Orders
• OpenBOM Change Management Demo – Revisions

This article will provide an overview of OpenBOM’s Change Management feature, focusing on Change Requests and Change Orders.

In this demo, I will show how a single person can approve CO and CRs. In my next article and video, I will speak about how multiple people can collaborate and be engaged with the CO and CR reviews and approvals. 

Change Requests (CR)

A Change Request (CR) is a candidate for a revision that can be created for any item in OpenBOM. CR captures the changes of the item (eg. any attribute change or file attachment) and waits to be approved by a single person or list of people. 

Change Order (CO)

Once created, the CR can be attached to the Change Order (CO), which can hold multiple change requests (CRs). During the review process, all CRs will be reviewed by the team of assigned reviewers and approvers before they will be approved.

Once all CRs are approved, a revision for all items will be created and technically change is completed. The history of the change orders holds all COs ( open, approved, and rejected). If rejected, nothing happens and no revisions will be made. 

OpenBOM’s COs are tightly integrated with the rest of the platform, making it easy to manage changes across multiple BOMs and projects. For example, a CO for a part change in one project may require updates to multiple related projects, ensuring consistency and accuracy across the board.

Video Demo

To demonstrate OpenBOM’s Change Management feature, let’s consider a simple example of an assembly in a complex device that will require cost reduction change by replacing components with a new cost. You can see how CRs will be created by both items (to reduce cost) and then a CR will be created to capture changes of both components in a single BOM 

Watch the video online. 

Conclusion

OpenBOM’s Change Management feature is a robust and configurable tool that helps teams manage changes to their product designs with ease and efficiency. By using CRs and COs, teams can ensure that changes are properly documented, reviewed, and approved before implementation. With a configurable workflow, detailed tracking and reporting, and real-time updates and notifications, OpenBOM’s Change Management feature is an essential component of any product development process.

REGISTER FOR FREE and check how OpenBOM can help you today. 

Best, Oleg