What this is
What is a production impact record?
What is a production impact record?
A production impact record converts a breakdown into a cost: units not produced, product scrapped, orders run late, and the labour and overtime spent recovering. It is completed by production, not maintenance, because production holds the line rate and the order book that make the numbers real.
Why is this scored on cost rather than time?
Hours of downtime do not compete for capital. A dollar figure does. Scoring the record on cost impact, where high is bad, means the same record that documents the event also builds the business case for whatever permanent fix follows it.
How does this differ from an Equipment Failure Report?
The failure report says what broke and when the line stopped. This record says what that stoppage was worth: lost margin, scrap value, recovery labour, and any commercial fallout. One documents the fault, the other prices it.
Scope
When is a production impact record required?
This record prices an event that another template has already opened. Raising it as a stand-alone incident report, or skipping it because the line recovered quickly, both break the chain back to the original case.
Use this template when
- A breakdown, slowdown or quality hold has already been logged elsewhere and carries a Case ID
- Production has settled enough to know units lost, scrap volume and whether output was clawed back
- Finance or engineering needs a defensible number to weigh against the cost of a permanent fix
- A repeat failure or bad actor case needs a cost trail behind it to justify investigation depth
- A customer-facing consequence, a late order or a notified customer, needs to be on the record alongside the operational detail
Do not use it for
- Equipment Failure Report, which records that an asset failed and stopped or degraded production, without pricing it.
- Failure Mode Record, which records how the asset failed using standard failure mode codes rather than cost.
- Repair Record, which records what was physically done to fix the asset, parts and settings, not what the stoppage cost.
- Repeat Failure Review, which looks at pattern across multiple failures rather than pricing this one event.
- Bad Actor Report, which ranks assets by cumulative cost over time; this record supplies one of the inputs, it does not replace the ranking.
Compliance mapping
Which ISO 55001 cl.9.1 requirements does this satisfy?
ISO 55001 clause 9.1 asks an organisation to evaluate the performance of its assets, not just their condition. This record is the mechanism: it turns a maintenance event into an asset performance figure that clause 9.1's monitoring and evaluation requirement can actually use.
| Clause | Requirement | Where it lands |
|---|---|---|
| cl.9.1 Monitoring, measurement, analysis and evaluation | Asset performance and the effectiveness of the asset management system must be measured against defined criteria. | Cost |
| cl.9.1 Monitoring, measurement, analysis and evaluation | The organisation must determine what needs monitoring, including methods that produce valid, comparable results. | Production loss |
| cl.6.2.2 Planning to achieve asset management objectives | Financial and non-financial consequences of asset failure inform planning to meet objectives. | Recovery and knock on |
| cl.8.1 Operational planning and control | Criteria for operational processes must be established, including how deviations are controlled and their consequences captured. | Recovery and knock on |
| cl.7.5 Information requirements | Information generated by the asset management system must be traceable to the event and record that produced it. | Header |
| cl.10.1 Nonconformity and corrective action | The organisation evaluates the need for action to eliminate the cause of a nonconformity, weighed against its consequences. | Cost |
What it does not cover
- Total Cost Of Event, which is left as a single typed figure instead of the sum of Lost Margin, Scrap, Labour and Repair Cost that finance will expect to trace.
- Case ID, which is blank or invented, breaking the thread back to the Equipment Failure Report or Downtime record this cost belongs to.
- Output Recovered Later, which is marked Fully without Overtime Hours To Recover or Additional Shift Required being completed, hiding the labour cost of that recovery.
- Penalty Or Claim Risk, which is left as None on an event where Orders Late is greater than zero and Customer Notified is No.
- Downstream Lines Affected and Upstream Product Held Or Diverted, both marked No on an event large enough to have triggered a customer notification, which is inconsistent on any linked production line.
Global
Production Impact Record requirements by country
ISO 55001 is voluntary everywhere, but its practical force differs sharply by sector and geography: in some places it is embedded in economic regulation, in others it is a certification a customer asks for.
ISO 55001:2014, Asset management — Management systems — Requirements
The source standard itself, sitting alongside ISO 55000 (overview and terminology) and ISO 55002 (guidance on application).
Wherever this record is used, its cost fields exist to satisfy cl.9.1's performance evaluation requirement; that clause number is the one to defend if the record is ever audited.
Economic regulators' asset management expectations (Ofwat, ORR) built on the Institute of Asset Management's IAM framework
UK infrastructure regulators expect regulated utilities and rail operators to demonstrate ISO 55001-aligned asset management maturity, with cost-of-failure evidence a routine part of price control and investment submissions.
A production impact record with a reconciled Total Cost Of Event is the kind of evidence a regulatory submission needs; an unreconciled one is the kind that gets challenged.
IPWEA and utility asset management plans referencing AS ISO 55001
Local government and utility asset management plans in Australia and New Zealand are built around AS ISO 55001 and expect a documented cost-of-failure trail behind any renewal or replacement business case.
This record supplies the failure-cost evidence those asset management plans cite; without it, renewal business cases fall back on age or condition alone.
How to complete it
How to complete a production impact record, step by step
The fields are simple to fill in. The four calls below decide whether the total that comes out the other end survives contact with someone who did not witness the event.
Line Rate Per Hour should be the rate the line was actually running at before the stoppage, not its nameplate or theoretical maximum. Using nameplate rate on a line that was already running slow inflates Units Not Produced and every dollar figure built on it.
Output Recovered Later marked Fully does not mean the event was free. Overtime and an additional shift have a labour cost that belongs in the record even when the units eventually shipped; the loss moved from lost margin to recovery cost, it did not disappear.
Penalty Or Claim Risk and Customer Notified are judgement calls that often outlive the shift that completes this record. Marking a risk as None because the customer has not complained yet is a different statement from confirming commercial has closed it out, and the record should say which one is true.
Total Cost Of Event is a required field with four contributing numbers sitting above it. Before signature, the two figures should be checked against each other; a mismatch caught at completion is a five-minute fix, one caught by finance later is a credibility problem for every record that follows it.
What auditors find
Most common production impact record findings
Recurring gaps in completed production impact records, and what closes each one.
| Finding | Clause | What fixes it |
|---|---|---|
| Case ID left blank or filled with the asset ID instead of the originating record reference. | cl.7.5 Information requirements | Require the Case ID to match an existing Equipment Failure Report, near miss or nonconformance reference before the record can be marked Complete. |
| Total Cost Of Event does not equal the sum of Lost Margin, Scrap, Labour and Repair Cost. | cl.9.1 Monitoring, measurement, analysis and evaluation | Add a calculated check at submission that flags any total more than a small tolerance away from the sum of its components. |
| Downtime Hours recorded but Line Rate Per Hour and Units Not Produced left blank. | cl.9.1 Monitoring, measurement, analysis and evaluation | Make Line Rate Per Hour required whenever Downtime Hours is greater than zero, so the conversion to lost output cannot be skipped. |
| Additional Shift Required and Overtime Hours To Recover left blank on records marked Output Recovered Later: Fully. | cl.6.2.2 Planning to achieve asset management objectives | Show the recovery labour fields whenever Output Recovered Later is not No, and require at least one to carry a value. |
| Orders Late greater than zero with Penalty Or Claim Risk left at None and no note on customer notification. | cl.8.1 Operational planning and control | Route any record with Orders Late above zero to a commercial reviewer before the second signature, rather than letting production close it alone. |
| Scrap Record ID left blank despite Product Scrapped carrying a nonzero value. | cl.7.5 Information requirements | Require the linked Scrap Record ID whenever Product Scrapped is greater than zero, so the quality and cost records agree on volume. |
Case in point
Case in point: the number that finally got the bearing replaced
A packing line seal drive had failed twice in four months, each time logged as an Equipment Failure Report and repaired the same day. Neither repair record carried a cost line, so the two events read as routine maintenance rather than a pattern. The third failure, on a Friday afternoon shift, triggered a production impact record for the first time: four hours of downtime, a partially recovered order run on Saturday overtime, and one late shipment that avoided a penalty only because the customer was notified early.
The Total Cost Of Event, once labour, scrap and lost margin were added up, came to several times the quoted cost of the upgraded bearing housing that engineering had proposed and shelved twice. With that figure attached to a Case ID that also linked the two prior failures, the replacement was approved inside a week. The bearing itself had not changed between the second and third failure; the only thing that changed was that someone finally priced it.
The template
The template, field by field
The form exactly as it installs. Every field, option, score and conditional rule is editable, and the links to other templates come with it.
4 sections
- Reference
- MNT-018
- Archetype
- Record
- Record ID
- PI-2026-000
- Scoring
- Cost impact
- Direction
- High is bad
- Singleton
- No
- Basis
- ISO 55001 cl.9.1
- Links
- Links Case, Downtime
- Tags
- Maintenance, Cost
- Sections
- 4
- Fields
- 41
- Follow up fields
- 0
- Repeating sections
- 0
- Links out
- 3
Header
15 fieldsRecord ID*
Auto sequence. Format PI-2026-0000.
The record's own ID. Other templates point at this value.
Status*
Drives who this goes to next.
- Planned2 pts
- In progress2 pts
- Complete3 pts
- Deferred0 pts
- Open0 pts
- Closed3 pts
- Overdue0 pts
Date and Time*
Raised By*
Site*
Site ID*
Format SITE-000.
Links to FDN-001 Site ID
Area
The area within the site.
Exact Location
Drop a pin for anything hard to find.
Asset*
Asset ID*
Format AST-0000.
Links to FDN-002 Asset ID
Case ID*
The failure or downtime event this quantifies.
Thread key. Every record in this chain carries this value
Parent Type*
What kind of record this follows.
Parent ID*
The reference of that record.
Immediate predecessor record
Raised Date*
Speak Finance
Maintenance loses budget arguments because it reports hours and finance thinks in dollars. This record converts one into the other.
Production loss
8 fieldsDowntime Hours*
Line Rate Per Hour
Units Not Produced*
Product Scrapped
Scrap Record ID
Links to QUA-005 Scrap ID
Product Downgraded
Raw Material Lost
Packaging Lost
Recovery and knock on
8 fieldsOutput Recovered Later*
- Fully3 pts
- Partly1 pt
- No0 pts
Overtime Hours To Recover
Additional Shift Required
- No3 pts
- Yes0 pts
Orders Late
Customer Notified
- Yes3 pts
- Not required3 pts
- No0 pts
Penalty Or Claim Risk
- None3 pts
- Possible1 pt
- Likely0 pts
Downstream Lines Affected*
- No3 pts
- Yes0 pts
Upstream Product Held Or Diverted*
- No3 pts
- Yes0 pts
Cost
10 fieldsLost Margin Value
Scrap Value
Labour Cost
Repair Cost
Total Cost Of Event*
Cost Per Downtime Hour
The number that justifies preventive investment on this asset.
Production*
Signature*
Finance*
Second Signature*
MNT-018 · record IDs look like PI-2026-000 · Links Case, Downtime
Open in KnowellaRun it with agents
From a document you fill in to a programme that runs itself
The form is the easy part. Keeping the cost fields reconciled, chasing the finance sign-off and rolling the total into a bad-actor ranking is the work that actually slips.
Holds the production impact record against its Case ID, checks the cost fields reconcile before sign-off, and surfaces cost per downtime hour into the asset's own history.
Matches Product Scrapped and its linked Scrap Record ID against the quality module's own scrap ledger, so the two records never diverge on volume.
Watches Orders Late and Downstream Lines Affected against the live schedule, flagging any event that needs a commercial or customer-facing response before the record closes.
Rolls completed cost records into the bad-actor and capital-justification view, and holds every write for your approval before it touches a record.
This template lives in KnowMaintain — asset maintenance. Work orders, planned maintenance, calibration, reliability and shutdowns.
Meet KnowMaintain→Glossary
Production Impact Record definitions and key terms
- Cost impact scoring
- A scoring model where a high score signals a costly outcome rather than a good one, used on records that measure consequence rather than compliance.
- Case ID
- The thread key carried by every record in a chain of related events, letting a failure, its cost record and any resulting action be pulled together as one case.
- Lost margin
- The contribution margin the business would have earned on units that were never produced because the line was down, as distinct from their raw material or scrap value.
- Cost per downtime hour
- Total Cost Of Event divided by the hours the line was stopped; the figure typically carried into a capital or preventive maintenance business case.
- ISO 55001 clause 9.1
- The performance evaluation clause of the asset management standard, requiring measurement of asset and system performance against defined criteria.
FAQ
Frequently asked questions about production impact record
Who is supposed to complete a production impact record?+
Production, not maintenance. Production holds the line rate, the order book and the scrap and recovery detail the costing depends on; maintenance's contribution, the repair itself, is already captured in the Repair Record it links back to.
What sections does the production impact record contain?+
Four: Header, Production loss, Recovery and knock on, and Cost. Together they hold 41 fields, 22 of which are required, moving from what happened to what it cost.
Why does the record need a Case ID rather than standing alone?+
Because a cost figure without its originating event is unauditable. The Case ID threads this record back to the Equipment Failure Report, near miss or nonconformance that caused the loss, so the full chain can be reviewed together.
How is a production impact record scored?+
On cost impact, where a high score is bad. The scoring exists so the record can be triaged and trended like any other, rather than being read narratively every time.
Does output recovered later mean the event cost nothing?+
No. Recovering output through overtime or an extra shift has its own labour cost, and the record is built to capture that cost separately rather than letting a full recovery erase the loss.
Can the production impact record template be changed?+
Yes. Every field, option, score and conditional rule is editable, and the link back to Case and Downtime records comes with it. Most teams install it as it is, run it for a cycle, then adjust the cost fields to match their own finance categories.
Keep going
Related templates and programmes
Industries this is written for
Programmes this belongs to
Used together in Reliability and Predictive Maintenance
Root Cause Analysis
Finds out why something happened rather than who was involved
Equipment Failure Report
Records that an asset has failed and stopped or degraded production
Failure Mode Record
Records how an asset failed, using standard failure mode codes rather than free text
Repair Record
Records what was actually done to fix the asset, including parts replaced and settings changed
Temporary Repair Record
Records a repair that is not permanent, with an expiry date and a plan for the proper fix
Repeat Failure Review
Reviews an asset that has failed the same way more than once
More in Breakdowns
Equipment Failure Report
Records that an asset has failed and stopped or degraded production
Failure Mode Record
Records how an asset failed, using standard failure mode codes rather than free text
Repair Record
Records what was actually done to fix the asset, including parts replaced and settings changed
Temporary Repair Record
Records a repair that is not permanent, with an expiry date and a plan for the proper fix
Repeat Failure Review
Reviews an asset that has failed the same way more than once
Breakdown Debrief
A short review straight after a significant breakdown, capturing what happened and what would have helped
Written and reviewed by
Siddarth Singh
Founder & Chief Executive Officer, Knowella
Certified Safety Professional and industrial and systems engineer with more than a decade inside food supply chain, freight and manufacturing operations. This page was written against the current text of the standards it cites, not against secondary summaries of them.
- Certified Safety Professional (CSP), Board of Certified Safety Professionals
- MBA, University of Chicago Booth School of Business
- MS and BS, The Ohio State University, Industrial and Systems Engineering
- Six Sigma Black Belt
Sources and last review. Reviewed 16 August 2026 against:
- ISO 55001:2014 cl.9.1 — Monitoring, measurement, analysis and evaluation
- ISO 55001:2014 — Asset management, management systems, requirements
- ISO 55000:2014 — Asset management, overview, principles and terminology
This page is general guidance, not legal advice. Confirm requirements with your jurisdiction’s regulator.