Closing the PdM-Execution Gap With a Reliable 4–6 Week T-4 Schedule Model

Most plants now own the tools of modern condition monitoring: vibration routes, infrared cameras, oil analysis kits, maybe even a cloud dashboard full of “traffic light” health scores. Yet many of those same organizations still spend most of their week firefighting.

The problem isn’t that condition monitoring “doesn’t work.” It’s that the insights are rarely wired into how work is actually planned and scheduled.

In a robust work management process, you don’t discover bad bearings, hot terminations, or thinning pipe in isolation. Those findings flow into a rolling, capacity-based schedule that looks four or more weeks ahead. Many utilities and heavy-industrial sites use a “T-4” model: at roughly four weeks before execution (T-4), the work window for a given week begins to take shape; as you move through T-3, T-2, T-1, and finally T-0, the schedule becomes more detailed and more protected.

The real shift happens when findings stop floating in reports and start shaping next month’s work.

That T-4 concept is not just for power plants. Any plant that wants to use condition monitoring to reduce risk and cost can benefit from a similar 4–6 week rolling schedule.

This article connects three elements:

• Four planning and scheduling maturity levels commonly seen in industry.
• A robust condition-monitoring strategy that includes multiple technologies.
• A T-4-style rolling schedule, adapted for general industry rather than one sector.

We will look at how these pieces fit together, how to measure progress using SMRP-aligned metrics such as planned work, schedule compliance, reactive work, and PM/PdM completion, and how a fictional plant moves from chronic reactivity to genuine best practice.

The goal is simple: help you turn raw condition data into reliably executed work in the right week, before failure, with minimal drama.

The Challenge: Great PdM, Weak Work Management

Walk into “typical” plants and you will often see this pattern:

• A vibration vendor or in-house analyst generates monthly reports.
• Thermography is done annually, sometimes biannually, “when there’s time.”
• Oil samples are sent to a lab; red-flag results show up in someone’s inbox.
• Operators do rounds with a mobile app and capture alerts, photos, and notes.

Individually, these tools are valuable. Collectively, they often have no disciplined path into the plan/schedule. Condition reports sit in email, shared drives, or vendor portals. When something finally fails, everyone asks, “Didn’t we have data on this?”

To unpack why this happens, it helps to look at four practical maturity levels for planning and scheduling:

Level 1 – Chaotic Reactive

• Work is driven by alarms, phone calls, and emergencies.
• Almost no job planning. Stores are bypassed; parts are grabbed ad hoc.
• The weekly “schedule” is whatever the crew can get to between fires.
• Condition monitoring, if it exists, is mostly forensic (“told us what we already knew was broken”).

Level 2 – Fragmented Planning

• Some jobs are planned, usually bigger ones or recurring PMs.
• A weekly schedule exists, but it’s essentially a wish list: more work than capacity, little enforcement.
• Condition findings may generate work orders but do not systematically feed a forward-looking schedule.

Level 3 – Structured but Fragile

• Planning is formalized; most work has job plans and parts kitted.
• A rough 3–4 week view of known work exists, but priorities are fluid and easily displaced.
• Condition monitoring generates higher-quality work requests, yet reactive break-ins still blow up the week.
• SMRP metrics like Percent Planned Work and Schedule Compliance are tracked, but results are inconsistent.

Level 4 – Best Practice, Rolling Horizon

• The plant operates a rolling 4–6 week schedule anchored by capacity, priorities, and risk.
• There is a clear gating point (T-4) where candidate work is evaluated and slotted into a specific week.
• Condition monitoring is a primary source of proactive work, not an afterthought.
• Planned work routinely exceeds 80–90%, reactive work is low, and schedule compliance is stable in the 80–90+% range.

The uncomfortable reality is that many organizations sit in Level 2 or early Level 3. They have invested in tools and people for condition monitoring but have not invested equivalent discipline in how that information is converted into planned, scheduled work.

Symptoms include:

• Lots of overdue PdM recommendations in the CMMS.
• PM/PdM completion rates well below 90%.
• 30–40% or more of craft hours consumed by emergency or urgent work.
• A “good week” defined as “nothing really big broke,” not “we executed the plan.”

The missing link is a process connection: a standard way for condition data to feed a forward-looking, T-4-style schedule that the organization actually respects.

How Condition Monitoring Feeds a T-4 Rolling Schedule

The Solution: Wiring Condition Monitoring into a Rolling T-4 Schedule

At a high level, the solution has three pillars:

1. Design a robust, risk-based condition-monitoring strategy.
2. Connect PdM outputs to planning and prioritization.
3. Drive those prioritized jobs into a T-4 rolling schedule that protects proactive work.

We will stay at the process level and walk through each.

1. A robust condition-monitoring strategy (but practical)

For general industry, a pragmatic condition-monitoring program typically uses a mix of technologies, aligned with asset criticality:

• Vibration analysis for rotating equipment (motors, pumps, fans, gearboxes).
• Infrared thermography for electrical connections, MCCs, bus ducts, refractory, and insulation.
• Lubricant analysis for gearboxes, large bearings, hydraulic systems.
• Ultrasound for compressed air leaks, steam traps, valves, and some bearing faults.
• Online process data (flows, pressures, currents, temperature trends) to detect pattern changes.
• Operator rounds capturing observations, smells, noises, minor leaks, and housekeeping issues.

The specific technologies matter less than having:

• Standard task packages (routes, frequencies, methods).
• Clear acceptance criteria (what is “normal,” “warning,” and “alarm”).
• A single intake path from findings into the CMMS as work requests.

Without that intake path defined, no scheduling model will fix the disconnect.

2. From condition finding to risk-ranked job

The real leverage appears when each condition finding follows a standard, rapid path:

1. Detection: A condition task identifies an abnormal condition (e.g., bearing defect, overheated cable lug, abnormal gear wear particle).
2. Initial assessment: The analyst assigns a severity and estimates risk-of-failure window (e.g., “Action required within 3–4 weeks to avoid unplanned downtime”).
3. Work identification: A work request is created with:

• Specific asset and location
• Clear problem description (symptom, not assumed cause)
• Recommended corrective task (replace bearing, reterminate cable, flush gearbox, etc.)
• Suggested required-by date or risk window

4. Planning: The planner develops a job plan:

• Scope, steps, and safety considerations
• Craft mix and hours
• Parts and materials (and lead times)
• Special tools, access requirements, permits, and coordination needs

5. Risk-based prioritization: At least weekly, a cross-functional review (maintenance, operations, reliability/PdM) reviews new and existing work, focusing on:

• Consequence of failure (safety, environment, production, cost)
• Probability and timing (from the condition assessment)
• Opportunities to bundle work (e.g., outages, product changeovers, shared scaffolding or crane access)

This is where SMRP-aligned metrics start to show impact:

• Planned Work (%): As more condition-driven findings are converted to fully planned jobs, the share of planned hours rises toward the 85–90% range seen in best-in-class operations.
• Reactive Work (%): As those risks are addressed before failure, the fraction of hours spent on emergencies drops below 10–15%.

But planning alone is not enough. Without a time-based frame like T-4, planned PdM work will still be displaced by “urgent” requests.

3. The T-4 rolling schedule: where condition monitoring earns its keep

Think of the T-4 model as a rolling weekly playbook:

• T-4 (four weeks before execution week):
  • Candidate work for that future week is identified and reviewed.
  • This includes condition-driven work, PMs due in that window, and known corrective jobs.
  • The team balances priority and risk against available crew capacity and major production events.
  • Jobs are assigned to a specific week (not just “sometime soon”).
• T-3 and T-2:
  • Planners and supervisors refine the package: confirm parts arrival, lock in permits, coordinate with operations.
  • Some adjustments happen, but changes are controlled and justified (e.g., a higher-risk condition finding displaces a lower-risk job).
• T-1:
  • The weekly schedule is effectively frozen.
  • Changes are handled through a visible “break-in work” or “emergency work” process, tracked as reactive.
  • Daily allocations are prepared from the frozen weekly schedule.
• T-0 (execution week):
  • Supervisors allocate jobs to people and shifts, with daily huddles to adjust within the weekly plan.
  • Actual hours are captured against the work orders for feedback and metric calculation.

Within this model, a robust condition-monitoring program plays a critical role in two ways:

1. Feeding the T-4 decision point with high-quality future work. For example, a vibration alert on a critical pump today may indicate a 3–5 week risk window. That immediately makes it a candidate for the T-4 review for Week W+3 or W+4, not “we’ll get to it when we can.”
2. Protecting proactive work at T-1 and T-0. When everyone agrees that the schedule is built on risk-based priorities—including condition-based risks—it becomes easier for leaders to say “no” or “not this week” to non-urgent break-ins. That’s how Schedule Compliance stabilizes in the 80–90%+ range: because the schedule represents disciplined decisions, not wishful thinking.

Over time, three patterns usually emerge:

• PM/PdM completion rates exceed 90%. Condition routes and inspections are no longer routinely skipped, because they are in the plan, not “nice to have.”
• Ready backlog becomes healthy. The plant maintains 2–4 weeks of fully planned work, ready to drop into future T-weeks as capacity and risk dictate.
• Production trust increases. Operations knows that when they support outages and windows, the work being done actually reduces future risk—not just “uses up” maintenance labor.

Leadership and culture matter here—but often in very specific ways: setting rules about emergency work, enforcing schedule freeze points, and insisting that condition data be used to drive those decisions.

Fictional Case Study: Midwest Polymers Connects PdM to T-4

Midwest Polymers Inc. is a mid-sized plastics plant with extrusion lines, pelletizers, cooling towers, air compressors, and a mix of utility systems. They have about 40 maintenance craftspeople across mechanics, electricians, and instrumentation.

Three years ago, Midwest invested in:

• Vibration routes on critical rotating assets.
• Infrared thermography on main switchgear and bus ducts.
• Lubricant analysis for gearboxes and large bearings.
• An ultrasound program for steam and compressed air.

On paper, their condition-monitoring program looked impressive. In practice, they were stuck around Level 2–3 on the maturity scale:

• Planned work hovered around 55–60%.
• Reactive work (emergency + urgent) consumed roughly 35% of labor hours.
• Schedule compliance bounced between 50–70%.
• PM/PdM completion usually sat in the 75–80% range.
• Ready backlog oscillated wildly, from a few days to more than six weeks.

A reliability engineer summarized it bluntly:

“We are great at finding problems and terrible at turning them into work done before failure.”

Step 1: Standardize the PdM-to-workflow

The first change was surprisingly basic: Midwest created a single workflow for condition findings:

• All PdM vendors and internal analysts were required to log findings into a Condition Review log within the CMMS, not just email reports.
• Each finding had to include:
  • Asset, location, and tag
  • Technology used (vibration, IR, oil, ultrasound)
  • Severity (A–D) and recommended action window (e.g., “act within 4 weeks”)
  • A proposed corrective task

A weekly Condition Review Meeting was added to the calendar. Participants:

• Reliability engineer (chair)
• Maintenance planner
• Production representative for the affected area
• PdM technicians or vendors (as needed)

Every new finding was either:

• Rejected (with justification),
• Converted into a planned work order, or
• Flagged as “monitor closely” with a defined follow-up date.

Within three months, nearly all significant condition findings were being converted into well-defined work orders in less than one week.

Step 2: Introduce a T-4-style rolling schedule

Midwest then launched a rolling 4-week schedule, explicitly labeled T-4 to T-1, with the current week as T-0:

• At T-4, the maintenance manager led a weekly Scheduling Conference:
  • Reviewed crew capacity and major production constraints for Week W+4.
  • Selected candidate work from the ready backlog, emphasizing:
    • High-risk condition-driven jobs
    • Overdue PM/PdM tasks
    • Corrective work tied to chronic production losses
  • At T-3 and T-2, planners confirmed parts, access, permits, and bundling opportunities. Jobs that could not be ready in time were swapped with other ready work.
  • At T-1, the weekly schedule was frozen:
    • Any work added after the freeze was tagged as break-in (reactive).
    • Supervisors were expected to protect scheduled proactive work unless safety or critical production risk demanded a change.

Initially, this was uncomfortable. Production supervisors wanted flexibility; maintenance supervisors worried about looking bad on schedule compliance. Leadership addressed this by:

• Defining clear emergency work criteria (safety, environmental, or very high production risk).
• Agreeing that breaking the schedule for anything else required manager-level approval.
• Committing to track Reactive Work (%) and Schedule Compliance (%) as joint KPIs, not “maintenance-only” numbers.

Step 3: Results over 12–18 months

Within six months, Midwest saw notable shifts:

• Planned Work (%) rose from ~60% to 78%.
• Reactive Work (%) dropped from ~35% to 18%.
• Schedule Compliance (%) for the frozen weekly schedule stabilized around 82–85%.
• PM/PdM completion climbed above 90% and stayed there.

After 18 months, they were operating firmly at Level 4 – Best Practice:

• Planned work fluctuated between 85–90%.
• Reactive work held below 12% for four consecutive quarters.
• Ready backlog consistently stayed around 3 weeks of planned work—enough flexibility to reshuffle around major outages, but not so large that priorities went stale.

More importantly, several high-risk findings (for example, an overheating main breaker, critical fan bearing defects, and progressing gearbox wear on a key extruder) were addressed in planned outages instead of becoming plant-wide events.

When asked what made the difference, the maintenance manager didn’t mention sensors or analytics:

“We didn’t buy new PdM tools. We changed how we decide what gets into the week. T-4 made condition monitoring real for our schedulers and supervisors.”

Conclusion and Call to Action

Condition monitoring by itself does not make a plant proactive. It simply moves the moment of awareness earlier. Whether that awareness turns into reliability gains depends on the maturity of your planning and scheduling process.

A T-4-style rolling schedule gives condition monitoring a place to land:

• Findings are not floating in reports; they are translated to planned jobs.
• Those jobs compete for a reserved spot in a specific week based on risk and capacity.
• Once scheduled and frozen at T-1, they are protected from everything except true emergencies.

The result, when done well, is visible in SMRP-aligned metrics:

• Planned Work (%) rises into the 80–90% range.
• Reactive Work (%) falls below 10–15%.
• Schedule Compliance (%) stabilizes above 80–90%.
• PM/PdM completion exceeds 90%, and ready backlog stays in the healthy 2–4 week window.

You do not need to copy any one industry’s version of T-4 exactly. What matters is having a disciplined, multi-week horizon with clear rules for how condition data turns into work and how that work moves through T-4, T-3, T-2, T-1, and T-0.

If you want to assess your own plant:

1. Map your current flow from PdM findings to work orders, to planning, to the weekly schedule.
2. Identify your maturity level (1 through 4) based on how planned, stable, and risk-based your weekly schedule truly is.
3. Select two or three SMRP-aligned metrics (e.g., Planned Work, Reactive Work, Schedule Compliance) and start trending them monthly.

The connection between condition monitoring and T-4 is not theoretical. As Midwest Polymers discovered, once you wire your data into a rolling schedule, the plant stops asking, “What did we miss?” and starts asking, “What risk did we deliberately remove this week?”

SMRP Metric Appendix

Note: Names and general definitions are aligned with SMRP Best Practices; “typical best-in-class targets” are based on published industry guidance and may vary by sector. The maturity levels and example targets discussed in this article are also informed by the Electric Power Research Institute’s Best Practice Guideline for Maintenance Planning and Scheduling (EPRI, Palo Alto, CA, 2000, Report 1000320), adapted here for general industrial use. For readers who want the original source, the report is available from the Electric Power Research Institute at www.epri.com by searching for “1000320” or the report title.

1. Planned Work (%) – SMRP 5.3.1

Definition (paraphrased):
The proportion of maintenance labor hours spent on jobs that were planned in advance (with defined scope, estimated hours, parts identified, and materials available) versus all maintenance labor hours in the period.

Formula:
Planned Work (%) = (Planned Maintenance Labor Hours ÷ Total Maintenance Labor Hours) × 100

Typical best-in-class target:
85–90% of total maintenance labor hours.

2. Reactive Work (%) – SMRP 5.4.1 (Reactive / Emergency Work)

Definition (paraphrased):
The proportion of maintenance labor hours spent on reactive (unplanned, emergency, or urgent) work relative to total maintenance labor hours.

Formula:
Reactive Work (%) = (Reactive Maintenance Labor Hours ÷ Total Maintenance Labor Hours) × 100

Typical best-in-class target:
Below 10–15% of total maintenance labor hours.

3. Schedule Compliance (%) – SMRP 5.4.3 (Hours)

Definition (paraphrased):
The degree to which the maintenance organization completes the labor hours that were included on the frozen schedule for a defined period (typically the weekly schedule).

Formula (hours-based):
Schedule Compliance (%) = (Actual Labor Hours Worked on Scheduled Jobs ÷ Total Labor Hours in the Frozen Schedule) × 100

Typical best-in-class target:
80–90%+ for a realistically loaded schedule; some references cite 90–100% for highly mature organizations.

4. PM and PdM Completion (%) – PM / PdM Compliance

Definition (paraphrased):
The percentage of preventive and condition-based maintenance tasks that are completed on or before their scheduled due date, within the defined grace period.

Formula:
PM/PdM Completion (%) = (Number of PM/PdM Tasks Completed on Time ÷ Number of PM/PdM Tasks Scheduled) × 100

Typical best-in-class target:
≥ 90% on-time completion for PM and PdM tasks.

5. Ready Backlog (Weeks of Work) – SMRP 5.4.9 (Ready Backlog)

Definition (paraphrased):
The total volume of fully planned and material-ready work in the backlog, expressed as the number of weeks it would take to complete using normal crew capacity.

Formula:
Ready Backlog (Weeks) = Ready Backlog Labor Hours ÷ (Average Weekly Available Maintenance Labor Hours)

Typical best-in-class target:
2–4 weeks of ready backlog; more than ~6 weeks often indicates excessive backlog and prioritization issues.