The plant runs 24/7 with morning and evening 12 hour shifts, and there are multiple projects and preventive maintenance to schedule. Would creating a master project file and adding sub-projects for the projects and the maintenance be the best choice, also could one project calendar be used or would multiple calendars be needed? Saving Changes...
Sort By:
Stéphane ParentSelf Employed / Semi-retired| Leader MakerPrince Edward Island, Canada
You ask good questions, Evette. Unfortunately, we would need a lot more background information to properly answer them.
My first question is whether the shutdown is a one time thing or will it be repeated?
I presume the sub-projects you are mentioning are those that would be affected by the shutdown. My suggestion would be to keep your shutdown schedule separate from the subj-projects and simply have them include external milestones, as necessary.
The need for multiple calendars will be driven by your resources' calendars.
Some of the things you will need to consider: * a good communication plan * multiple checkpoints or gates * a fallback plan Saving Changes...
The plant has two shutdowns per year for preventive maintenance and repairs. One shutdown is during the Spring and the other one is in the Fall. The sub-projects are capital projects that have been approved to be completed during the shutdown. Initially, my thought was to create a master file and add sub-projects to it, so that everything for the shutdown would be captured in a master schedule. This is my first time handling a schedule of this size, so I post the question to get advice to help me formulate my approach. Saving Changes...
