Maintenance records for AI licensing

Which question could the records answer?

Choose a possible task before counting work orders. A repair-reasoning task might need symptoms, diagnostic steps and the eventual finding. A maintenance-planning task would ask different questions about operating periods, interventions and later failures. These are possible uses to discuss, not evidence that a buyer needs your archive.

The UK Government Data Quality Framework treats quality as fitness for the intended purpose. It is public-sector guidance, not a commercial certification or a price benchmark. Our practical recommendation is to write the proposed question at the top of your internal review and assess the records against it.

Keep this separate from selling the physical equipment. Fairlode reviews descriptions of business records for potential data licensing; it does not provide machinery resale valuations.

Follow the repair, not just the job number

Within your own authorised systems, ask a maintenance colleague to trace a completed job from the first report to the final check. Record which links exist without copying the underlying notes into an enquiry.

• What was reported: a symptom, an alarm or a measured deviation?
• What was checked before an action was chosen?
• Which work was completed, and was it planned maintenance or a response to a fault?
• What evidence supports the recorded outcome?
• Can later visits be connected to the same issue?

Where several visits sit under separate job numbers, explain that structure. Do not count each visit as an independently resolved fault. Where a diagnosis was revised, preserve the distinction between the first suspicion and the eventual finding.

Check what closed and repaired mean

Ask who closes a work order and what the status confirms. It may record that an engineer has finished their paperwork, that a replacement part was fitted, or that a return-to-service check passed. Those meanings should not be merged into a stronger claim.

An illustrative example: a pump job is marked complete after a seal replacement, but there is no subsequent running test in the archive. Describe it as a recorded replacement with an unrecorded follow-up outcome. Do not turn it into a confirmed successful repair.

Keep a short list of ambiguous codes and the person or team able to explain them. Use the existing data dictionary guide for field definitions rather than creating a second set of meanings for an external discussion.

Describe the equipment and time coverage

Prepare an internal scope note covering equipment families, the period held and the systems involved. State whether an asset identifier remains stable when equipment moves site, is rebuilt or changes owner. If it does not, explain how histories could be confused.

Ask whether the archive includes ordinary operation as well as failures. An archive containing only call-outs cannot, by itself, describe everything that happened between them. Record whether usage hours, operating conditions or scheduled checks are available, unknown or outside the proposed collection.

Separate maintenance history from continuous measurements. If the opportunity depends on vibration, temperature or other readings, use the machine sensor data checklist to describe those streams and how they connect to interventions.

Keep permission questions separate from quality

List the teams and organisations involved in creating the records: your employees, service contractors, equipment suppliers and customers. Ask the appropriate adviser to check the relevant agreements before promising external use. Ownership of equipment is not a substitute for reviewing permissions relating to its records.

Keep engineer names, contact details, customer locations, credentials, photographs and confidential production information out of the first description. Do not describe a collection as anonymous merely because the asset number replaces a name. The anonymisation guide explains why that needs a separate assessment.

If the overview itself would disclose a sensitive fault pattern or process, stop and discuss confidentiality before sending it. There is no need to prove the archive is interesting by attaching real work orders.

Prepare a useful first outline

Use this structure for a non-confidential outline: broad equipment category; period covered; approximate number and definition of records; whether faults, actions and outcomes are linked; known missing stages; and who can authorise a review. Leave commercially sensitive quantities out if they cannot safely be disclosed.

Mark estimates as estimates. Add one clear limitation, such as inconsistent outcome checks in the older system, instead of claiming the whole archive is complete. An accurate limitation is more useful than a confident but unsupported description.

Read the Ireland and Northern Ireland sector guidance for local context. Then use the existing descriptions-only enquiry route. An initial review is not buyer acceptance, a machinery valuation or permission to hand over the underlying records.