Revision Handling and Management from a Manager’s Perspective
Today I want to talk to you about ROI and one of the methods of improving this – through effective revision handling in the electrical design process. This is not going to be a technical overview, instead I’m going to take more of a manager’s perspective on the issue – focusing on the economics of the engineering opportunity.
Back in my youth (erm not that I’m old) I studied economics and learned a lot about the importance of added value, economy of scales and scope and return on investment (ROI).
How can we compare a technical engineering tool with economy?
– From my point of view that’s quite easy, because there is always an economical impact on technical issues.
Managing Revisions in the Electrical Design Environment
Managing releases and revisions can involve a lot of time consuming effort involved in tracking of all changes, ensuring data consistency, while delivering against time pressures. You also need to ensure that only valid changes are distributed from the correct source models to the consuming applications that require them, thus preventing invalid or incomplete changes from being deployed.
You know as well as I do, that during an engineering process consistency of engineering data is very important. An engineer starts with a base design which will be delivered to the factory for the groundwork. During this groundwork the engineer is finishing the first release of the detail engineering. Unfortunately today we are all under time pressure, because of that the factory needs the information as soon as possible to build up the connections in the cabinets. At the same time the engineers revise the circuit diagram. At the end the produced cabinet is not on the same revision as the engineering. But only the differences are important to finish the cabinet in the factory.
If the factory is in house, that’s easy to handle most of the time, but what if the engineering is based in Switzerland and the factory is in China? Then you have to consider not just time differences, but a whole lot of other issues. So my point is that re-traceability is very important in achieving a good ROI.
To complete the workflow some information has to be written into an ERP System, along with the specific changes. All these processes cost a lot of money if they are not integrated. But time and cost are the things which we all want reduce. So that is why we introduced E³.Revision Management, to integrate all this and help engineering managers decrease their costs. To find out more visit the product web page here.
So now it’s time to go back to the frosty weather (-5°) here in Switzerland.
I wish you all a great week.
Greets from Switzerland