EnergyProfessional
Mechanical
- Jan 20, 2010
- 1,279
I'm looking for a good way to track over the course of a project what decisions were made and why. for example: someone decided a year ago a pipe should be increased for future capacity. Next year this will be installed and in the field someone wonders if the pipe could be made smaller... then it would be good to know that and what the reason was to begin with. or to track that a specific item was required by a specific person.
Most my projects are just designed by myself (and a structural engineer, I'm MEP) and a smaller circle of stake holders. but I also wonder about solutions for larger projects. Some of my colleagues manage projects designed by outside consultants.
My McGyver way would be to start with a spreadsheet and write that down per CSI-division or so. that obviously would have its limitations. I asked some project managers, but didn't find a good solution.
What do you guys use or recommend?
Most my projects are just designed by myself (and a structural engineer, I'm MEP) and a smaller circle of stake holders. but I also wonder about solutions for larger projects. Some of my colleagues manage projects designed by outside consultants.
My McGyver way would be to start with a spreadsheet and write that down per CSI-division or so. that obviously would have its limitations. I asked some project managers, but didn't find a good solution.
What do you guys use or recommend?