Forum Topic
IEC 61508 Change management/control
You need to be logged in to get access to the forums. You can do so here
|
Functional safety forum
|
Previous topic
| Next topic
|
|
|
Author
|
Message
|
|
|
håkan landsberg
|
Friday 14 December 2007 3:44:43 pm
IEC 61508 Change management/control
Is it specified anywhere in the standard at which point in the development life cycle a formal change procedure is needed (change request, impact analysis etc.) It is clear that all this is needed for changes in a released version of a product, but what about changes during development?
|
|
Michel Houtermans
|
Thursday 20 December 2007 9:34:11 pm
Re: IEC 61508 Change management/control
Change management is an important topic in IEC 61508. There are two kind of changes, one is called a change, the other is called a modification. Changes are those changes that take place during or within a lifecycle phase. They are the kind of change that do not effect the work done in other lifecycle phases. Changes in a lifecycle phase that do effect the work done in other lifecycles are called modifications. Modifications need to be formally managed by MOC procedure including impact analysis.
Basically MOC is part of your management of functional safety. In other words you need to have that procedure ready before the project starts....
|
|
Janne Peltonen
|
Sunday 16 March 2008 7:30:43 pm
Re: IEC 61508 Change management/control
In my opinion the question WHEN to start change management is crucial when thinking about costs of the project.
As a rule of thumb I think that management of change is needed when you have finished your work phase and have released the first version (draft or final) as output of your work for someone else working in the same project. The idea of management of change is simply to guarantee that all parties who have done their work before you agree with those changes you want to make.
E.g. if you have made a software and tested that it works correctly, you are quite sure that you can do no more with it and release the software for testing. After the testing has started, you have to manage all changes after that to be sure that nothing goes wrong during those changes.
Funny thing is that you can actually save lots of money when you apply the management of change procedure early enough. But not too early, if you're not nearly finished on your own, my advice is that don't start it yet.
|
Industry News