01 · Purpose and boundaries
Purpose and boundaries
Total Productive Maintenance coordinates people and functions to improve equipment effectiveness throughout its life. It includes restoring basic conditions, planned maintenance, operator involvement, training, and focused removal of losses. It is broader than asking operators to clean machines, and broader than optimizing a maintenance department's schedule.
Start with the equipment's required function and acceptable operating conditions. A warehouse conveyor must transport the correct loads safely and consistently, not merely run. Establish equipment boundaries, ownership, maintenance history, spare-part needs, and authorized task limits. Operators can observe conditions and perform approved care; work involving hazardous energy, specialized repairs, or regulated competence remains with appropriately qualified personnel.
02 · How the method works
How the method works
Identify losses using explicit categories and consistent definitions. Downtime, changeovers, minor stops, reduced speed, defects, and rework can all reduce useful output. Separate the symptom from the cause; repeated jams may arise from packaging variability, damaged rollers, or inappropriate settings.
Restore basic conditions before introducing elaborate predictive methods. Clean and inspect safely, identify leaks or wear, restore lubrication and fastening conditions, and tag abnormalities with an owner and response. Define approved autonomous-care tasks and teach how to recognize abnormal conditions. Plan maintenance from failure mechanisms, manufacturer guidance, operating conditions, and evidence—not merely a calendar copied from another machine.
Measure the result with appropriate equipment and system measures. Overall equipment effectiveness combines availability, performance, and quality, but its inputs require carefully defined time and ideal-rate boundaries. Use it to reveal losses rather than reward a single percentage. Link maintenance timing and spare availability to customer service and the equipment's system role.
03 · Worked logistics example
Worked logistics example
Fictional PineDock runs a sorter for 450 planned production minutes each day. Stops consume 45 minutes, leaving 405 operating minutes. Its ideal rate is 40 parcels per minute. It processes 14,580 parcels, of which 14,434 are correctly sorted first time.
Availability is 405/450 = 90%. Performance is 14,580/(405 × 40) = 90%. Quality is 14,434/14,580, approximately 99%. OEE is about 0.90 × 0.90 × 0.99 = 80.2%. These are illustrative definitions; the team must ensure the ideal rate and planned-time exclusions are legitimate.
Inspection finds recurring belt tracking issues and dust-covered sensors. Approved cleaning, scheduled belt alignment, and spare sensor availability reduce stop time to 25 minutes. Operating time becomes 425 minutes. If performance remains 90% and quality 99%, estimated good output becomes 425 × 40 × 0.90 × 0.99 = 15,147 parcels, roughly 713 more than baseline. The team verifies this estimate through actual operating records.
04 · Interpretation and decisions
Interpretation and decisions
Availability improvement matters only in the context of demand and the system constraint. If outbound dock capacity is lower, extra sorter output may create congestion. Use released volume, late shipments, recovery time, and maintenance workload alongside OEE.
A rise in performance accompanied by lower quality may reflect excessive speed. A rise in availability after removing maintenance from the planned schedule may simply change the denominator and increase future failure risk. Keep definitions stable and inspect the individual loss components. Decide maintenance priority from consequence, probability, detectability, and recovery capability rather than treating every asset as equally critical.
05 · Common misapplications
Common misapplications
TPM is often reduced to a cleaning checklist or an OEE target. Both can miss the reliability system. An equipment utilization incentive may encourage producing unnecessary parcels or operating beyond safe limits. Do not transfer repairs to operators without competence, authorization, safe procedures, and support.
Avoid using an assumed universal “world-class” percentage as the improvement target. Equipment types, product mixes, and measurement boundaries differ. Do not replace preventive work with predictive technology before establishing trustworthy data. A sensor generates information; people and processes still need to interpret it, plan intervention, and restore equipment.
06 · Advanced adaptation
Advanced adaptation
JIPM describes TPM through an eight-pillar framework, with emphasis and additional management elements adapted to the organization. Common areas include focused improvement, autonomous maintenance, planned maintenance, quality-related maintenance, education, safety and environment, early equipment management, and administrative processes. Their names and implementation arrangements should follow the selected framework rather than an invented universal checklist.
Advanced adaptation uses failure-mode analysis and condition monitoring on critical assets, connecting signals to intervention windows and spare strategy. Early equipment management feeds operating lessons into new equipment specifications: accessible inspection points, maintainable components, diagnosable faults, and safe recovery. Reliability engineering and daily operator observation should reinforce one another.
For a shared warehouse asset, include recovery arrangements: an approved manual route, available spare capacity, trained coverage, and a clear decision about which customer commitments receive priority during restoration.
07 · Implementing and sustaining the change
Implementing and sustaining the change
Introduce total productive maintenance (tpm) within a clearly named operating boundary. Identify the product family, shift, equipment, and handoffs affected; record what happens immediately before and after that boundary. A change that improves one task while exporting its delay to another department has not established an improvement. Agree who can stop the trial, who handles exceptions, and which customer commitment takes priority when the normal rule cannot be followed.
Establish a baseline from actual work rather than a single demonstration. Include normal variation in order mix, replenishment timing, staffing, and workload. Keep the denominator visible: minutes per order, defects per shipment, or completed lines per available hour answer different questions. Record the workload and conditions alongside each observation so that a quiet trial period cannot masquerade as better performance. Observe the process with the people who do it; their explanation of interruptions often changes the proposed design.
Start with a reversible pilot large enough to expose handoff problems. Explain the expected mechanism before launch: which action changes, which delay or failure it removes, and which result should respond. Train all affected shifts and support roles using the same operating definition. During the pilot, capture exceptions as information about the design. Do not conceal them through unofficial stock, unrecorded overtime, or a specialist who quietly repairs every failure.
Review customer service, safety, quality, work content, and inventory together. A faster average with more severe late orders may be unacceptable; a lower inventory level with repeated emergency deliveries may have displaced the cost. Investigate variation before declaring success. If the expected mechanism does not appear, revise the design or return to the baseline rather than defending the idea. A promising observation is a reason to test more conditions, not proof that every operating context will behave identically.
After a successful trial, make the new rule part of daily work. Give an accountable owner responsibility for the operating standard, change control, training, and periodic review. Specify the abnormal condition that requires escalation and the person who responds. Check whether the improvement remains effective when a trained colleague is absent or demand changes. Sustain the mechanism through routine management and learning; documentation is useful only when it describes the process people actually follow.
Connections
Related methods and phase use
Placed under Improve because of the outcome it supports. Use the method in other phases when its purpose and assumptions fit the work; the phase list is a guide to selection, not a compulsory sequence.
Sources
Professional foundations and further reading
The explanation and fictional teaching examples are written for LeanTrainingLab. Linked primary sources provide professional foundations; example values and local conventions are stated in the guide. The accepted toolset draws on Six Sigma+Lean Toolset, second edition (Lunau, editor; Springer, 2013). No book text or examples are reproduced here.