How to determine if a project requires configuration managemnt
How to determine if a project requires configuration managemnt
(OP)
In my business every project is a one of a kind system with a unique configuration of electro-mechanical hardware and custom software. Most projects are small that cost under $100K and last less than 3 months. We do apply traditional project management techniques to our projects, but struggle with configuration management.
Specifically knowing when configuration management applies and when it does not.
Thanks in advance for feedback !
Specifically knowing when configuration management applies and when it does not.
Thanks in advance for feedback !





RE: How to determine if a project requires configuration managemnt
Configuration management is a system and process that can best be summed up as "A change in form, fit, or function of a part requires a new definition of the part, not just a revision. Configurations are not controlled by revision."
Another way to put it for commercial products is that if you sell a system to a customer, then you can not make a change to the definition of that system or when the customer has a problem, you will not have a record as to what EXACTLY they have. That doesn't mean you can make improvements on the system; you just have to redefine it somehow. The easiest way for machined components is to add a dash number to each part.
For example, drawing 12345 would depict part 12345-1. You can revise 12345-1 so long as you do not affect form, fit, or function. Once you do, you then revise drawing 12345 by adding a 12345-3 configuration (even numbers are reserved for opposite hand). Personally, since adding configuration 12345-3 also affects all upper level assemblies containing 12345-1 -- they now must also show 12345-3 by adding new dash numbers to each assembly -- I prefer to just use a different base number.
Back in manual days, part numbers were sacred. Now they are cheap.
--Scott
For some pleasure reading, try FAQ731-376
RE: How to determine if a project requires configuration managemnt
People should not forget that ALL the documentation should come under CM, as this should change THEN the product!
You don't need a CM engineer if the project is small and on a limited buget (aren't they all) but someone should take on the role