ARTICLE COMPANION

Three-check export card

Static worksheet proposal, with a fictional completed example. This card records an agreed interpretation of a particular export. It does not certify all the data in a CMMS.

Blank card

Prompt Record your answer
Question and intended decision
Export filename/version, extraction time and time zone
Site, equipment and period scope; filters used during export
Coverage evidence: does this contain every qualifying record for a site total, or only selected rows? Reconcile against a suitable source population.
1. Row grain: What does one row describe? What makes an event/order unique?
Confirmed duplicate rule, retained source rows and evidence
2. Equipment: Which field identifies a position, physical item or assembly? Is site/source part of the key?
Register/mapping version, installation dates where needed, unresolved references
3. Status/date: Current state or dated event? What does the chosen status mean? Which date and boundaries apply?
Treatment of later status changes and repeated eligible events
Reconciled result, included/excluded record IDs and limitations
Export supplier: row-grain evidence accepted by / date
CMMS process owner: equipment/status/date interpretation accepted by / date
Recheck trigger and next owner

Leave an interpretation unresolved if the evidence is missing. Retain the source export; keep transformations and exclusions traceable. Recheck when the query, source system, mapping, status rules or reporting question changes.

Completed fictional example

Prompt Example
Question Distinct North Quay orders represented in this extract that entered Complete in October 2026, even if their status later changed.
Extraction Selected status history and current-status fields as at 5 November 2026; extraction clock time/time zone not supplied in the teaching extract. A real handover needs both.
Grain and duplicate Intended one row per site + WO + event ID. Ravi, fictional export supplier, checks source event E11 and confirms the second identical row is an exported copy. He accepts that grain interpretation. Original retained. E12 is a separate event and stays.
Coverage No confirmation that the export includes every qualifying October event/order. A site total requires Ravi to check export filters and reconcile coverage against the source population.
Equipment Register check establishes NQ/P-07 and SQ/P-07 are distinct duty positions. Lena, fictional CMMS process owner, accepts site + tag for this extract; no physical-item mapping supplied.
Status/date Lena checks E11/E13 in the source orders and accepts Complete as the event status for this question. Current status is as at extraction. Site-local event dates: 1 October inclusive to 1 November exclusive. Count each site + WO once.
Result Within the supplied rows: 4 raw October Complete rows; 3 distinct represented orders across both sites after the E11 copy is set aside; 2 North Quay orders (701, 702). Filtering these North Quay rows to current Complete gives 0 and does not answer the agreed event question.
Limits Selected history only; site-wide October coverage unverified, so no site total established. No historical backlog, failure count or work-quality conclusion. Cause of 702's current Open status is not supplied.
Acceptance All checks and people above are invented for the article. No actual operational export has been approved.

Companion-artifact specification

  • Audience: Reporting analyst with the export supplier and a named CMMS process owner.
  • Inputs: A preserved export and its query/filter details; coverage reconciliation against a suitable source population for site totals; field definitions; equipment register/mappings; small source-order/history checks; intended reporting question.
  • Outputs: One card beside the export, a reproducible inclusion/duplicate rule, reconciled record counts with explicit population/coverage limits, unresolved items and named acceptance owners.
  • Assumptions: Relevant source records and responsible people are available. Keys and dates must be checked for the actual system. A card for one extract does not establish fitness for another question.
  • Human acceptance: Export supplier accepts grain/query interpretation. Process owner accepts equipment identity, status and date meaning. Analyst reconciles the result and records limitations before report use.
  • Data handling: Keep real exports and cards in the organisation's approved storage. This package contains invented records only. An AI profile is optional, subject to authorised access, and requires row-level evidence and human checking.
  • Status and smallest useful version: Static worksheet delivered here. No interactive tool, live connection or working AI integration is claimed. A printable version could be scoped later if useful.