Maintenance project planning (free template for Philippine plants)

Maintenance project versus routine PM

The most common Philippine plant mistake is treating a 2-week turnaround as a long list of PMs. PMs do not have critical-path dependencies, do not need contractor coordination, and do not need handback. Projects have all three. Use the right tool for the work.

The 6 reasons projects blow over budget

Six causes account for most budget overruns on maintenance projects, and they recur often enough to be worth planning against by name:

1. Scope creep after freeze. Production adds a "while you have it open" job 2 weeks before the project. The 30-minute add takes 6 hours and shifts the critical path. Hard freeze at 90 days is the rule; only true emergencies add after that, and every emergency add gets a documented justification.
2. Discovery work. The team opens an asset and finds worse damage than expected (corrosion under insulation, cracked housing, contaminated oil, undocumented modifications). Plan 15 to 20 percent contingency time and budget for discovery. Plants that plan zero contingency are surprised every time.
3. Contractor delays. The third-party crew arrives 2 days late, or arrives with fewer people than contracted, or arrives without the right tools. Mitigation: contractual penalties, pre-arrival kit verification, backup contractor on call.
4. Late parts. Imported parts have 60 to 120-day lead times. A single late delivery on a critical-path job extends the whole project. Order long-lead-time parts 120 days out; have backup suppliers identified for everything Tier 1 critical.
5. Safety incidents triggering stand-down. A near-miss or actual incident triggers DOLE-required investigation and a plant-wide safety pause. Plan that this will happen approximately once per major project; build a 1-day stand-down into the contingency budget.
6. Weather. The Philippine rainy season (June to October) affects outdoor work, scaffolding, hot work, and crane lifts. Schedule weather-sensitive work for early shifts; have indoor-only fallback jobs ready for rain days.

The 6-step project planning workflow

Step 1: Freeze the scope 90 days out

One workshop with production, maintenance, engineering, and plant manager. Every proposed job goes on the wall. Each job gets a written justification, an asset reference (from Asset Hub), and an estimated duration. Plant manager signs the frozen scope. After the freeze, only documented emergencies add.

Step 2: Build the schedule with critical path

Sequence every job. Identify dependencies (you cannot reassemble before alignment; you cannot align before bearing install; you cannot bearing install before bearing arrival). The longest dependency chain is the critical path. Total project duration equals critical path duration; non-critical jobs have slack.

Compression options:

• Parallelise non-dependent work (two crews on different assets simultaneously)
• Pre-fabricate off-line (assemble the spare pump skid before the outage starts)
• Add shifts (24-hour coverage on the longest critical-path jobs)
• Add resources (split a 3-day crew of 2 into 2 days of 3 if the work is parallelisable)

Step 3: Allocate resources by skill matrix

Match every job to the people and equipment needed. Cross-check against the Skill Matrix to confirm Level 3+ coverage on every critical-path job on every shift. Surface single-point-of-failure people (only one technician can do X) and pre-arrange backup or train a second.

Step 4: Identify risks and assign mitigations

Top-10 risk workshop with the project team. Each risk gets:

• Probability (Low / Medium / High)
• Impact (cost or schedule)
• Named owner
• Documented mitigation
• Trigger condition for activating the mitigation

Step 5: Cost the project to the asset, not the project code

Every peso spent gets allocated to the asset that benefited (rebuild cost on Pump P-101A, not "Turnaround 2026 Q3"). Three years later when you decide replace versus refurbish, you have the data; plants that lump everything under one project code lose this forever. Note that this one is a discipline you keep in your finance system, not something WorkHive does for you: a project carries a budget figure and links to the assets it touched, but there is no per-asset cost rollup to read back, so the ledger that answers "what has this pump cost us" is still yours to keep.

Step 6: Execute with daily standups and handback discipline

15-minute daily standup at start of shift. Standing agenda: yesterday completed, today planned, blockers, risk status. Contractors attend alongside in-house leads.

Per-asset handback: PM schedule updated, Logbook entry of the work, parts consumed, photos in Asset Hub, supervisor and operations sign-off. No asset returns to operations until handback complete.

Critical path explained for plant projects

Critical path is the longest dependency chain through your schedule. Its duration sets the minimum total project duration. Example for a pump overhaul:

Job A: Drain and isolate pump          (4 hr)
Job B: Disassemble                    (6 hr, after A)
Job C: Inspect and clean              (8 hr, after B)
Job D: New bearings install           (4 hr, after C, needs bearings on hand)
Job E: Alignment                      (4 hr, after D)
Job F: Reassemble                     (6 hr, after E)
Job G: Commissioning test             (4 hr, after F)

Critical path: A → B → C → D → E → F → G = 36 hours

Non-critical: Job H "Touch up paint" (2 hr) can run any time after B
              has 30 hours of slack; do not lose sleep over it
      

The leverage: if Jobs D, E, or F slip 4 hours, the project finishes 4 hours late. If Job H slips, nobody cares. Knowing this directs the supervisor's attention. Plants without explicit critical path treat every job equally and miss the leverage.

Coordinating multiple contractors

Most major projects in Philippine plants involve 3 to 8 contractor crews working in parallel: mechanical, electrical, instrumentation, scaffolding, insulation, painting, lifting, civil. Without explicit coordination, they trip over each other: scaffolding crew leaves before electrical needs to access, insulation goes back before instrumentation has had time to check.

Three rules that work:

1. Single coordinator owns the master schedule. Contractors do not negotiate schedule with each other; they negotiate through the coordinator. The coordinator is usually a senior planner or project engineer, not a contractor.
2. Decide what system access each contractor gets: deliberately. WorkHive will not scope it for you: hive membership is worker or supervisor, and a member sees the hive's records. So either keep vendors out of the hive and have your own staff log their work against a contractor project, or accept that a vendor you add can read the plant's logbook. Whichever you choose, make status updates land in Project Manager rather than in WhatsApp groups, so the trail survives the project.
3. Daily standup includes contractor leads. Same 15-minute meeting, same agenda. Blockers surface immediately. Email handoffs and side-chat coordination kill projects.

Coexistence with SAP PS and Maximo Projects

WorkHive Project Manager does not replace SAP PS (Project System) or Maximo Project Management. Those handle the financial side:

• WBS structure for finance reporting
• Cost allocation to project codes and assets
• Vendor PO tracking and invoice matching
• Capitalisation rules and depreciation triggers

WorkHive Project Manager handles the operations side:

• Who does what when: a Gantt with the critical path computed
• Schedule risk by Monte Carlo simulation over the task durations, so the end date comes with a spread rather than a single optimistic number
• Resource overload flagged when the same people are booked twice
• Change orders raised against a project when scope moves
• Daily progress log with supervisor sign-off
• Scope items, and links to the asset, the logbook entries, PM completions, inventory items and engineering calculations the project touches
• Variance summary and lessons learned at the close

They meet at one point today, and it is worth knowing exactly where: when a worker closes a work order in the logbook, WorkHive pushes that completion out to your configured CMMS (computerized maintenance management system): the machine, who did it, actual hours and the close timestamp: translated into that system’s own status code rather than the literal word “closed”. See the CMMS integration guide for the setup. Nothing financial crosses in either direction: budgets, WBS structure, PO matching and capitalisation stay entirely in SAP or Maximo, and a cost figure you want in both places is entered in both places. Plants that use both well treat them as complementary; plants that try to make either do both end up with one half-used system.

Handback discipline: where most projects end badly

The pattern that ruins post-project credibility: the project hits its deadline, the assets restart, production celebrates, and 3 weeks later operations is still asking maintenance for the updated drawings, the new PM schedules, the as-built photos. The work happened; the documentation did not.

Handback discipline closes this gap. For every asset touched by the project, before it returns to operations:

• Asset Hub record updated with any spec changes
• PM schedule reviewed and any frequency changes captured
• Logbook entry of the work done with technician name
• Parts consumed entered in Inventory
• As-built photos attached
• Supervisor signs the handback; operations signs receipt

No signature, no handback. No handback, the asset stays project-owned and the project does not close.

Frequently asked questions

Sources

• Project Management Institute (PMI), PMBOK Guide, 7th Edition. Source for the project planning workflow adapted here for plant maintenance.
• Society for Maintenance and Reliability Professionals (SMRP), Best Practices, 5th Edition, 2017. Source for turnaround / shutdown planning benchmarks.
• Department of Labor and Employment (DOLE), Occupational Safety and Health Standards (OSHS) Rules 1010 and 1040 on hazardous workplace requirements and OSH committee. Source for safety planning in projects.
• WorkHive platform positioning, "Four Gaps One Hive" with Project Manager as the Execution accelerator. workhiveph.com
• Related WorkHive guides: CMMS Integration · Skill matrix · Asset register · Spare parts inventory