Production and Maintenance Capacity Planning With Real-Time Asset Health

By James Smith on October 24, 2026

production-maintenance-capacity-planning-asset-health

Production plans are usually written as if every machine will be ready, and maintenance plans as if every window will be free. The two collide on the shop floor, where a tired machine either misses its output or loses its service slot. A shared view of asset health lets both teams plan against the same picture of what each machine can really deliver this week. Plants building that view can ask iFactory AI how asset health feeds the production plan.

Production Planning

Production and Maintenance Capacity Planning With Real-Time Asset Health

Turn asset health into hours: how many each machine can run, how many each crew can service and where the plan will break. iFactory AI keeps both plans in step as conditions change.

80 to 90%
planned maintenance share that world-class teams aim for, according to the vendor Tractian
50 to 70%
typical range for manufacturing on the same source, so most plants have room to improve
1 to 100
the usual scale of an asset health index, where 100 means optimal health, as a Bentley Systems article describes

Two Plans, One Set of Machines

Production and maintenance draw on the same scarce resource: machine hours. Each team tends to plan its own calendar, and the conflicts show up late. Seeing both side by side is the first step.

Production asks

How many hours can I count on?

It needs machine hours to meet orders, with as few surprises as possible and enough warning to move work.

Maintenance asks

When can I take the machine?

It needs windows long enough to do the job, parts on hand and a crew free at that time.

Result 1

Skipped service

Production wins the argument, work is deferred and risk quietly builds up.

Result 2

Missed output

Maintenance wins, the plan loses hours and orders slip.

Better result

Shared hours

Both plans use the same health data and agree trade-offs early, with the numbers in plain view.

The aim is not to remove the conflict but to see it early enough to choose. Walk through a joint production and maintenance view on sample data in a short session.

Asset Health Index: One Number per Machine

An asset health index sums up condition and risk in one score. Bentley Systems describes a scale of 1 to 100, where 100 is optimal, calculated for each asset class from inputs such as age, maintenance history, load and condition tests. The bars below show an illustrative set of machines.

Press 1

92
Packer 5

81
Filler 2

78
Mixer 3

61
Conveyor 4

44
InputWhat It Tells YouTypical SourceWeight Idea
Condition readingsVibration, temperature, current trendsSensors and roundsHigh
Failure and repair historyHow often and how badly it failsWork ordersHigh
Age and run hoursWear accumulatedAsset and counter recordsMedium
Load and dutyHow hard it is workedProduction dataMedium
CriticalityWhat a failure would costRisk rankingUsed for priority, not for health

Keep health and criticality apart. Health says how likely the machine is to fail. Criticality says how much it would hurt. Planning needs both, but mixing them into one number hides the reason a machine is ranked high.

The source article is vendor marketing and gives no formula, so build and test your own weights. Ask support how health scores are built for different asset classes.

From Health Score to Usable Hours

A health score is only useful to planners when it turns into hours. Map each score band to an expected loss of scheduled time. The factors below are illustrative, so calibrate them against your own history.

Health BandScoreExpected Unplanned LossPlanning Stance
A, strong85 to 1003% of scheduled hoursPlan at full rate
B, good70 to 847%Plan with a small buffer
C, watch50 to 6915%Derate and plan an intervention
D, at riskBelow 5030%Protect output and repair soon

Calibrate with history

Compare each band with the unplanned downtime it actually produced over the last year, and adjust the percentages.

Reflect the trend

A score of 70 falling fast is riskier than a steady 70. Add a trend flag beside the band.

Keep it simple

Four bands are enough. More detail rarely improves a weekly plan.

Bands make health easy to use in the planning meeting. Calibrate health bands against your downtime history with the iFactory AI team.

See Your Capacity With Health Built In

Book a 30-minute session and iFactory AI will show how asset health, production demand and maintenance windows combine into one weekly capacity view.

The Weekly Capacity Ledger

Now combine demand, health and maintenance. For each machine, start with 120 scheduled hours, subtract planned maintenance and the expected unplanned loss from its health band, and compare the remainder with demand.

MachineBandDemand hPlanned Maint. hExpected Loss hAvailable hSurplus or Gap h
Press 1A10043.6112.4+12.4
Packer 5B9868.4105.6+7.6
Filler 2B10468.4105.6+1.6
Mixer 3C961018.092.0-4.0
Conveyor 4D901436.070.0-20.0
Total4884074.4485.6-2.4

The total looks nearly balanced, with a gap of only 2.4 hours. The detail tells a different story. Conveyor 4 is 20 hours short, while Press 1 and Packer 5 have spare time. A plan built on the total would miss the problem, and one built on the machine hours finds it in time to act.

Shift work

Move orders from the short machine to those with surplus, if routings and tooling allow.

Fix the weak asset

A repair that lifts Conveyor 4 from band D to band B removes most of its expected loss.

Reset the promise

If neither is possible, tell sales early which orders move, and by how much.

All figures are illustrative and meant to show the method. Ask support how the ledger is built from live data in the platform.

Maintenance Crew Capacity: The Other Half

Machine hours are only one constraint. Maintenance also has a limited number of technician hours, and the plan must fit inside them. The bar shows an illustrative week for a crew of six.





Planned preventive work, 70 hours
Condition-triggered jobs, 44 hours
Reserve for breakdowns, 40 hours
Backlog and improvement work, 62 hours
Crew capacity, one week, illustrative
Technicians6
Productive hours each, after travel, meetings and leave36
Crew hours available216
Planned and condition-based work, including backlog176
Planned share, 176 of 216 hours81.5%

Tractian defines planned maintenance percentage as planned hours divided by total maintenance hours. At 81.5 percent this crew sits inside its quoted 80 to 90 percent world-class aim, well above the 50 to 70 percent it reports as typical for manufacturing. The reserve of 40 hours is what keeps breakdowns from consuming planned work.

Crew hours are a constraint just like machine hours. See crew capacity and planned share on a live dashboard in a working session.

Finding the Right Maintenance Window

The best time to service a machine is when production loses least. Different windows suit different jobs.

Window TypeTypical LengthSuitsWatch For
Changeover gapUnder an hourInspections, lubrication, quick adjustmentsDelaying the next run
Idle shiftSeveral hoursComponent swaps and calibrationParts and crew ready in time
Weekend stopOne to two daysLarger repairs and overhaulsOvertime cost and contractor access
Planned shutdownDays to weeksMajor projects and statutory checksLong preparation and many trades
Match job to window
Do not start a ten-hour job in a two-hour gap. Plan from the work to the window.
Pre-stage parts
A window is wasted waiting for a part. Kit and check before the stop begins.
Protect the window
Agree with production that planned windows are not given away without a trade-off.
Use health to move it
If a machine's health falls, pull its job forward. If it holds, the slot can move back.
Windows are scarce, so choose them with data. Ask support how maintenance windows are proposed from the production plan.

Real-Time Triggers: When Health Changes the Plan

Health scores move during the week. Agree in advance which changes should reopen the plan and who is told, so replanning is calm and quick.

Watch
Score falls by 10 points in a week, or enters band C
Action: add to the weekly review, check parts and draft a job for the next window.
Plan
Score falls below 60, or a condition alarm persists
Action: book the earliest suitable window, reserve parts and derate the machine in the plan.
Act
Score below 50 on a critical machine, or a sudden fall
Action: move production off the machine, repair at the next safe stop and inform sales.

These limits are examples. Set them from past failures, and use tighter limits for machines that constrain the whole line.

Clear triggers turn health scores into decisions. See health triggers reopening a plan on a live board during a demo.

A Worked Decision: Fix Conveyor 4 Now or Later

Conveyor 4 is at 44 and 20 hours short. The plan has two options, and the cost of each can be set out plainly. Figures are illustrative.

ItemOption A: Repair at the WeekendOption B: Run On and Hope
Repair timingPlanned 6-hour weekend windowFailure expected within weeks
Repair cost2,5004,000, with rushed parts
Production lostNone in the weekend window12 hours of stoppage at 1,500 margin an hour, 18,000
Extra overtime to shift work1,200Not planned
Total3,70022,000

The planned repair costs about 18,300 less in this illustration. The point is not the exact figure, but that the comparison can be made in minutes when health, capacity and cost sit in the same view.

Decisions like this are easier when both teams see the same numbers. Ask support how repair-or-run decisions are supported in the platform.

KPIs That Show Whether the Joint Plan Works

A few numbers tell you if the two plans are working together. Review them in one meeting that production and maintenance both attend.

KPIWhat It ShowsGood DirectionWarning Sign
Planned maintenance percentageShare of hours spent on planned workRising toward 80 percentFalling as breakdowns grow
Schedule compliancePlanned jobs finished in their windowHigh and steadyWindows repeatedly overrun
Capacity coverAvailable machine hours over demand hoursOne or higherBelow one on key machines
Health trendMovement of scores by bandFewer machines in C and DMachines sliding down each month
Backlog weeksOpen work divided by weekly crew hoursStable or shrinkingGrowing backlog
Unplanned downtime hoursHours lost to breakdownsFallingRising with no cause found
Pair a production number with a maintenance number in every review. See joint planning KPIs on one dashboard with the iFactory AI team.

Common Planning Mistakes

Most breakdowns in planning come from habits. Each has a plain fix.

1
MistakePlanning on nominal capacity
FixDerate each machine by its health band.
2
MistakeLooking only at plant totals
FixCheck capacity machine by machine.
3
MistakeTwo separate calendars
FixShare one plan view with windows and orders.
4
MistakeNo breakdown reserve
FixHold crew hours back for the unexpected.
5
MistakeHealth scores nobody trusts
FixBack-test bands against past failures and share the results.
6
MistakeReplanning without notice
FixUse trigger rules and tell the affected teams at once.
Small habits make the joint plan stick. Ask support for a joint planning checklist tailored to your plant.

A 90-Day Path to Joint Planning

iFactory AI is built as a turnkey server that racks in, plugs in and goes live in roughly 6 to 12 weeks, so a joint planning pilot fits inside a quarter.

Days 1 to 30
Choose one area, build health scores for its key machines and agree the four bands.
Days 31 to 60
Build the weekly ledger for machine and crew hours and run it beside the current plan.
Days 61 to 90
Switch to the joint plan, set trigger rules and hold a weekly meeting with both teams.
One area first proves the method before it spreads. Plan a joint planning pilot with our team.

What iFactory AI Adds

iFactory AI is smart manufacturing and industrial software. It brings asset condition, production plans and maintenance work into one view.

Live asset health
Scores and bands follow condition data and maintenance history.
Capacity ledger
Demand, health losses and maintenance hours are netted per machine.
Window proposals
Suitable gaps are suggested for each job, with parts and crew checks.
Trigger alerts
Health changes reopen the plan and notify the owners.
Data sources and planning systems differ by plant, so confirm scope early. Ask support which production and maintenance systems can be connected in your case.

What Data You Need Before You Start

A joint plan does not need perfect data. It needs a short list of fields that are reasonably complete and agreed by both teams. Check each one before the pilot begins, and note who owns it.

Data ItemOwnerMinimum StandardCommon Gap
Asset list with hierarchyMaintenanceEvery planned machine has one record and a lineDuplicates and retired assets still listed
Failure and repair historyMaintenanceA year of work orders with cause codesFree-text causes that cannot be grouped
Condition readingsReliabilityRegular readings for critical machinesGaps when sensors are offline
Production schedulePlanningOrders by machine and weekMachine not recorded on the order
Rated speed and run hoursOperationsStandard rate per machine and productRates out of date after upgrades
Crew rosterMaintenanceTechnicians, skills and leave by weekSkills not recorded

Start with the machines that constrain the line. Their data matters most, and a small, clean set is easier to trust than a large, patchy one.

Gaps are normal at the start and can be closed in stages. Ask support to review data readiness for your first area.

What-If: A Demand Surge Meets a Tired Line

The value of a joint view shows when demand changes. Suppose sales adds a promotion that raises weekly demand on the filling line by 15 percent. The question is where the extra hours can come from. Figures are illustrative.

Base demand

104 h
With surge

120 h
Available

106 h

The surge pushes demand to about 120 hours against 106 available, a gap of roughly 14 hours. Three levers are open, and each has a different cost and risk.

Lever 1

Defer a service job

Gains hours now but raises risk. Only sensible if the machine is in band A or B and the job can be placed after the promotion.

Lever 2

Add a weekend shift

Adds hours without touching the service plan, at the price of overtime and a tighter crew week.

Lever 3

Re-route to a sister line

Uses spare hours elsewhere, if the product and pack format can run there.

A health-aware view shows which lever is safe before anyone commits. Run a surge scenario on sample data in a short session.

Roles and Meeting Rhythm

Tools help, but the habit of meeting decides whether the joint plan survives. Keep the rhythm short, regular and tied to the same numbers each time.

Monday, 30 min
Review last week's compliance, then confirm this week's ledger, windows and any machines that changed band.
Midweek, 15 min
Check triggers and open gaps. Decide whether any job or order must move before the weekend.
Friday, 20 min
Close the week, confirm weekend windows with parts and crew, and note lessons for the bands.
Production planner

Owns demand and the order sequence

Brings the schedule, proposes moves and tells sales and customers what changes.

Maintenance planner

Owns windows, parts and crew

Brings health scores, the job list and the reserve, and flags where a window is at risk.

Name one person to make the call when the two sides disagree. A short, fast decision beats a long debate, and the data in front of everyone keeps it fair.

Clear roles keep the plan moving. Ask support for a role and meeting template you can adapt.

How to Judge Whether the Pilot Worked

After 90 days, compare the pilot area with its own baseline. Keep the test simple so the result is believed.

Fewer surprises
Count unplanned stops on pilot machines against the same weeks last year.
Better planned share
Track planned maintenance percentage monthly and look for a steady climb.
Honest promises
Check how often committed order dates held, before and after.
Trust in the numbers
Ask both teams whether they would keep using the shared view. Adoption is a result too.

If the pilot shows gains, extend to the next area. If not, look at the bands and data first, since a poorly calibrated score is the most common cause.

A fair test builds confidence for a wider rollout. Agree pilot success measures with the iFactory AI team.

Plain-Language Glossary

Shared words keep production and maintenance aligned.

Asset health index
A score, often 1 to 100, that sums up the condition and risk of a machine.
Planned maintenance percentage
Planned hours divided by total maintenance hours.
Capacity cover
Available hours divided by demand hours.
Derate
To plan a machine at less than its full rate because of its condition.
Maintenance window
A gap in production long enough to carry out a job.
Backlog
Approved work not yet done, often shown in weeks of crew time.

Frequently Asked Questions

What is capacity planning with asset health?

It means planning production hours and maintenance hours together, using each machine's condition to estimate how many hours it can really deliver.

How do we build a health score?

Combine condition readings, repair history, age and load for each asset class, then test the result against past failures. Ask support how scores are built for your equipment.

What planned maintenance percentage should we aim for?

One vendor source puts world-class at 80 to 90 percent and typical manufacturing at 50 to 70 percent. Treat 100 percent as unrealistic.

How often should the plan be reviewed?

Weekly for the ledger, with trigger rules reopening it sooner when a health score falls sharply.

Who should be in the planning meeting?

A production planner, the maintenance planner, a supervisor from each side and, when cost is discussed, a finance partner.

Plan Production Around the Health of Your Machines

iFactory AI turns asset health into hours, joins them to production demand and maintenance crews, and reopens the plan when conditions change. Book a walkthrough on your own plant data.


Share This Story, Choose Your Platform!