VIDEO: OpenBOM Collaboration ECO Approval Workflow and Notifications

Oleg Shilovitsky
Oleg Shilovitsky
23 February, 2022 | 2 min for reading
VIDEO: OpenBOM Collaboration ECO Approval Workflow and Notifications

Efficient and timely approvals are critical to the success of any manufacturing organization. To that end, OpenBOM has developed a unique collaborative workflow approval mechanism. If you didn’t check it yet, please navigate here to learn more – OpenBOM Collaborative Approval Workflow in 90 sec.

An important element of approval workflow is the notification mechanism. The uniqueness of the OpenBOM approval process is to be able to streamline the communication of change orders (eg. ECO, MCO, etc.) in the engineering department, and also between companies and contractors, to help ensure that everyone is aware of modifications to the product design and orders. In this article, we’ll take a closer look at how the OpenBOM Collaboration Approval Workflow notification mechanism works. We’ll also explain how you can configure notifications for your team. 

Role-Based Configuration and Notifications 

In OpenBOM you can define 4 levels of approval settings: 1- Notification; 2- Optional; 3- Mandatory; 4- Approve All.

Each of them allows you to set people’s roles in a way that will help them to perform their work either by observing change processes or taking an active part in them. Approval All is a super powerful role that allows the person to override everyone else and make things move forward. 

In addition to defining roles for approval, you can also see a small [x] notification sign, which defines who will be getting notifications about the changes. 

How Notifications Mechanism Works? 

OpenBOM notifications mechanism sends email notifications to every person in the list notifications (hint – when the [x] notification checkbox is switched on). This simple and powerful mechanism helps everyone involved know about changes that are done in the product. 

Here is an example of the email message notification. 

Video: Configuring Notification Mechanism 

Please watch a demo video of how to configure and use the notification mechanism. 

Conclusion

OpenBOM provides a universal approval workflow mechanism, which allows you to bring people from different departments as well as from multiple companies together to make an approval process easy and collaborative. OpenBOM increases the visibility of the process by making it transparent and easy to access and approve by everyone. The team members involved in an approval process are not getting a narrow view of their own “approval” task, but getting broad visibility. It is really important for management because they can prevent bottlenecks for the process in such a collaborative “bird view”. 

At the same time, OpenBOM also supports the mechanism of notifications, which works via email and allows you to be notified about changes even when you’re not getting into the OpenBOM web application. 

Check out what OpenBOM can do for you – REGISTER FOR FREE and start a 14-days trial to explore all premium features. 

Best, Oleg

Related Posts

Also on OpenBOM

4 6
10 April, 2026

Every time an engineer opens a product data management system, they face a small but real cognitive task before any...

10 April, 2026

OpenBOM will be presenting at Threaded in Miami, the startup gathering space hosted by Aras ACE 2026 at the Hilton...

9 April, 2026

I’m coming to Share PLM Summit 2026, taking place on May 19–20 in Jerez de la Frontera, Spain. It the...

8 April, 2026

For many SOLIDWORKS teams, the challenge was never the design work itself. It was everything that came after: configuring tools,...

2 April, 2026

A SolidWorks model is essential. A BOM is essential. Drawings, PDFs, STEP files, and DXFs are essential too. Many teams...

2 April, 2026

In the previous article, I wrote that engineering teams usually do not lose control because CAD design is wrong. The...

2 April, 2026

In my experience, manufacturing companies that rush a new product introduction process usually pay for it later. They see production...

1 April, 2026

How file-based workflows, disconnected BOMs, and the limits of PDM combine to create a product data problem most engineering teams...

31 March, 2026

Last week I wrote about where product lifecycle knowledge gets lost, and I also published a longer piece on Beyond...

To the top