ARTICLE COMPANION

Reopened-order test card

Case: REOPEN-015
Prepared: 13 November 2026
Status: invented worked example; proposed and unexecuted

No CMMS, reporting application or AI service has been tested with this card. Expected values below are calculated from supplied fictional events. No actual human process-owner acceptance, observed output or operational sign-off is recorded.

What this case asks

Can the report show the status-based backlog contribution of 1 order at each selected historical cut-off, including a period after reopening? Do the earlier answers remain the same when rerun with the full history after final completion?

This checks the status history and reporting rule. It does not assess schedule attainment, physical-completion performance or why the order reopened.

Worked inputs

Order: WO-T015. Population: this order alone, with no additional orders or filters. Counting unit: distinct work-order identifier. All event, cut-off and extraction times below are Europe/London, GMT (+00:00), in November 2026.

Event ID Effective and recorded time Status
T015-01 2 November 2026, 09:00 Open
T015-02 3 November 2026, 15:00 Complete
T015-03 4 November 2026, 10:00 Reopened
T015-04 5 November 2026, 16:00 Complete

For this invented case, Reopened means work in the original scope remains. No reason for reopening is supplied. These are the complete events; each is entered immediately and becomes effective at entry time. There are no tied timestamps, backdated entries, later corrections, deletions or missing events.

Rule: at a cut-off, select the latest event effective at or before that instant. Open or Reopened contributes 1; Complete contributes 0. Before creation the contribution is 0. Each change applies at its effective instant, including an equal cut-off.

Human agreement before a real run

Keep these fields blank until a real person supplies the agreement. A prepared example, draft or production QA pass does not supply operational acceptance.

Required agreement Record for the real run
Maintenance process owner, role and date ______________________________
Status meanings accepted for this measure ______________________________
Original-scope meaning of Reopened accepted ______________________________
Population, counting unit and time basis accepted ______________________________
Expected counts and applicable events accepted before execution ______________________________
Approved test environment and scope ______________________________
Analyst checking arithmetic and source lineage ______________________________
Tester recording actual output ______________________________

If local meanings or inputs differ, write and accept a revised expectation before running that separate case. Do not silently apply this example to a different KPI.

Expected results and blank execution record

Report/build/version: ______________________________
Run date/time and tester: ______________________________
Input/history version and approved evidence path: ______________________________

Cut-off, GMT Expected status Expected count Applicable event Actual count and membership Actual event detail and evidence path
2 November 2026, 12:00 Open 1 T015-01, 2 November 09:00 __________________ __________________
3 November 2026, 17:00 Complete 0 T015-02, 3 November 15:00 __________________ __________________
4 November 2026, 12:00 Reopened 1 T015-03, 4 November 10:00 __________________ __________________
5 November 2026, 17:00 Complete 0 T015-04, 5 November 16:00 __________________ __________________

When included, WO-T015 must appear once. When its contribution is 0, it must not count in the backlog population. Detail must let the tester trace each answer to the applicable event, including the Complete events that exclude it. A matching total alone is insufficient.

After final completion, rerun the earlier cut-offs using the full history. Record the observed outputs and evidence separately:

Rerun check Expected Actual and evidence path
2 November 12:00 1; WO-T015 once; T015-01 applies ______________________________
3 November 17:00 0; T015-02 applies ______________________________
4 November 12:00 1; WO-T015 once; T015-03 applies ______________________________

Rerun date/time, input version and tester: ______________________________

Check what the reporting input actually retains

The invented current-only export is extracted on 6 November 2026 at 09:00 GMT. It contains exactly 1 row:

Order ID Created Current status Latest completion
WO-T015 2 November 2026, 09:00 Complete 5 November 2026, 16:00

It contains no first completion event, reopening event, prior statuses or prior effective times. Under the stipulated rule, this row supports a current contribution of 0 at extraction. By itself, it cannot establish all 4 historical answers.

Actual input type, fields retained and accessible history: ______________________________
Missing events or unavailable evidence: ______________________________
Approved internal evidence path: ______________________________

If only the current-only row is available, record historical reporting not demonstrated. Do not infer the missing events, record a pass or treat a plausible historical number as established evidence. The next decision is what historical evidence the reporting design must retain or retrieve.

Record the outcome after execution

  • Proposed pass conditions: the 4 counts are 1, 0, 1, 0; distinct membership is correct; detail identifies each applicable event; and the earlier results persist on rerun with full history after final completion.
  • A disagreement in count, membership or applicable event fails the reporting check. Record the discrepancy and evidence. Duplicate counting, today's status applied to every date or unsupported history presented as established does not pass.
  • Missing history or unavailable output evidence leaves the affected historical checks not demonstrated. Record the limit separately from any specific defect that has actually been observed.

Observed discrepancies and evidence: ______________________________
Outcome: pass / fail / not demonstrated / mixed, with affected checks identified: ______________________________
Analyst's calculation and source-lineage check, name/date: ______________________________
Maintenance process owner's operational acceptance or rejection, name/date: ______________________________
Required action, owner and recheck date: ______________________________

Use and handling

Keep real orders, exports, screenshots and test evidence in the organisation's approved environment. Use approved internal evidence pointers on a real test card. The public worked example and site repository should contain synthetic data only.

AI could propose checks or flag contradictions from the events, rule and export contract. The analyst must check those suggestions. Human status agreement and operational acceptance remain the process owner's decisions. This card contains no actual AI-service output or executed integration.