INDUSTRY FIELD GUIDE
Meter and counting-device data for AI counter interpretation
NIST publishes measurement guidance.
NAICS 334514 · Totalizing Fluid Meter and Counting Device Manufacturing
NIST publishes measurement guidance. A totalizing-meter manufacturer can define an original task that distinguishes a cumulative reading from a quantity measured over a stated interval. NIST measurement context
Create fictional meter identifiers, counter definitions and timestamped readings. Record a counter replacement between two observations. Ask the assistant which interval calculation is supported by the supplied rule. Include a rate field beside a total field and an observation whose reset history is absent. The key should identify the missing continuity rather than subtract across an unsupported boundary.
Annotate meter, counter, event time, reset or replacement, property and unit. Hold out a new log layout for evaluation. Score rate values used as totals, subtraction across an unrecorded reset and wrong-meter joins independently. Include a complete interval with all inputs so the model can demonstrate a supported calculation.
Use original records and invented values without connecting to a live utility or process. Customer consumption information, licensed interfaces and proprietary firmware data need appropriate authority. Describe the counter-and-event task and independently checked examples in the licensing brief. Confirm buyer scope before preparing a larger archive or authorized capture.
Discuss this original manufacturing sample with Fiund
Original Fiund exercise
A reset breaks the cumulative subtraction
A fictional meter export uses abstract counter units and an explicit reset event.
| Record | Source | What it records |
|---|---|---|
| 1 | Reading at 08:00 | M7 total 95 units. |
| 2 | Reset log | 09:00 reset; pre-reset total 100 and post-reset total 0. |
| 3 | Reading at 10:00 | M7 total 7 units. |
Question for the model
How many units accrued in the interval?
Show the reference answer and checks
The interval contains 5 units before reset (100 − 95) and 7 after reset (7 − 0), totaling 12. Records 1–3 supply both reset boundary values. Directly subtracting 95 from 7 would compare counters from different epochs.
- Treating a reset as negative consumption
- Ignoring the pre-reset subtotal
Fields to preserve
- counter_epoch
- Separates totals across resets
- reset_boundary_readings
- Support the two interval segments
- interval_delta
- Stores increment rather than cumulative value
Test another case
Omit the pre-reset value; report the known post-reset increment and flag the whole interval incomplete.
No actual utility accounts, meters, billing advice or customer usage data.
Discuss a contribution
Describe the sources you control, the task they could support and what has already been checked. Use the existing-data assessment for an archive or the collection brief for a new recording project. The contributor agreement defines Fiund’s licensing authority and compensation. A guide or fictional exercise does not establish an accepted collection or a sale.