Project Management Central
|
Please login or join to subscribe to this thread
|
||||
|
||||
Reva, did you receive any ideas/suggestions for this? I have just started an O&M project and am looking for ideas/suggestions on scheduling.
Network:638
With large complex systems, the testing and verification phase often involves a lot of operations for verification credit, and maintenance of the system up until final delivery. Integrated master schedules are used extensively to tie in the many moving elements of the plan. The rationale for how and why the IMS exists in a developmental environment can absolutely be applied post-delivery as well.
While post-delivery operations and maintenance is somewhat different than PD, if you have logical milestones that set target dates for completion of major activities and multiple detail level plans supporting that, then you can and should build a top level schedule to align them. Maintenance is often required at set operational intervals so operational planning can drive major milestones for the timing of maintenance activities. Complex maintenance activities require detailed lower level plans to complete within the down-time window so you not only can, but should have an integrated master schedule to tie the various sub-tier plans together.
I would not overly rely on your programs having the same activities. The real purpose of a master schedule is to manage your enterprise resources, allowing you to spot those who are over- and under-allocated.
Yes, loosely-defined activities will make it difficult to get the true usage of your resources. Take it as an opportunity to go back to the program and work on making the activities clear and straightforward. |
||||
Please login or join to reply
ADVERTISEMENTS
|
"If you work on a lobster boat, sneaking up behind people and pinching them is probably a joke that gets old real fast." - Jack Handey |
