How to get a view of all of the artifacts impacted by an engineering change request, faster
AndyGurd 270001QKDH Visits (1383)
Talking to clients, who are engineering products and systems, one of the biggest challenges I hear is that of responding to engineering change requests. And by responding, I don’t just mean the time taken to implement the change, but all of the process that should come before that to determine whether the change should be implemented now/later/never and what’s the impact of implementing the change on cost, schedule and resources. Engineering change requests need to be evaluated intelligently, not blindly. The extent of the impact of a change request on a specification, design, test plan, subsystem, component, part, source code file, etc. will need to determined by the experts on those elements of the product/system, but how do you even know where to start? How do you know what is potentially impacted by the change request? Watch this short animation on the challenge of building a comprehensive impact analysis view and a new solution with the potential to greatly reduce the time and effort to do so.
So what do you think? How much time and effort do you or your engineering teams spend on compiling a list of artifacts that are potentially impacted by an engineering change request? If you could automatically generate an impact analysis view built from data in multiple tools from multiple vendors, across multiple engineering teams and disciplines, would that be of value to you and your organization?