Watch the overview
74 seconds. A narrated explainer; the transcript is below. The written guide includes additional detail.
Read the video text
- 0:00A summary can contain plausible counts and
- 0:02still have the wrong number of bins.
- 0:05The key question is which completed header
- 0:08defines that summary record. The mixed-file parser
- 0:11tracks header blocks. Definitions collected between H
- 0:14zero and H nine become active when
- 0:17the header closes, and the next completed
- 0:19header can change the context. For a
- 0:21type twenty example, the implemented check expects
- 0:24the configured bin count plus ten fields.
- 0:27Three configured bins therefore require thirteen fields;
- 0:31twelve fields produce a count mismatch. Summary
- 0:34configuration checks also inspect the applicable class
- 0:37or bin definitions. These checks address the
- 0:40record structure and configuration, not an assurance
- 0:43that the traffic counts are physically correct.
- 0:46Separate checks examine timestamp order and daily
- 0:48coverage in the mixed-file route. A complete-looking
- 0:51row is not enough to prove a
- 0:53complete observation period. Use the complete source
- 0:56file when reviewing header-dependent findings. A standalone
- 1:00summary lacks the active-header evidence needed for
- 1:03this comparison. Correct the relevant definition or
- 1:06record and rerun, retaining the original context.
Which header describes this summary?
A summary can contain plausible counts and still have the wrong number of bins. The key question is which completed header defines that summary record.
The mixed-file parser tracks header blocks. Definitions collected between H zero and H nine become active when the header closes, and the next completed header can change the context.
Compare bins with physical fields
For a type twenty example, the implemented check expects the configured bin count plus ten fields. Three configured bins therefore require thirteen fields; twelve fields produce a count mismatch.
Summary configuration checks also inspect the applicable class or bin definitions. These checks address the record structure and configuration, not an assurance that the traffic counts are physically correct.
Count fields against the completed header
In the implemented type-20 example, three configured bins require thirteen fields: the configured bin count plus ten. A twelve-field summary is short even if all its visible counts look plausible. Establish which completed header is active before changing the summary or its configuration.
Inspect subsequent header changes as well as the first block. Keep count, timestamp-order and daily-coverage findings separate so that fixing one structural fault is not mistaken for a complete observation period. Missing traffic must not be manufactured by padding the record with zeroes.
Keep time and coverage distinct
Separate checks examine timestamp order and daily coverage in the mixed-file route. A complete-looking row is not enough to prove a complete observation period.
Use the complete source file when reviewing header-dependent findings. A standalone summary lacks the active-header evidence needed for this comparison. Correct the relevant definition or record and rerun, retaining the original context.
Sources and scope
This guide describes the platform workflow; it does not establish a requirement of a TMH manual. Platform review and certification are described in the product documentation.
Put it into practice
Review check templatesSign-in and the relevant account permissions are required.