A green square on a dashboard can settle an argument too quickly. The machine is running, the display says. But running a program, cutting a production part and proving a changed operation are different claims. Which one does the square support?
That question belongs at the machine before it becomes a question about the chart. A useful integration preserves the difference between an observed signal and an interpretation of the work. The operator can help explain that difference without being asked to design the entire information system.
The examples below follow one hypothetical CNC milling job: a small batch of brackets with a revised hole pattern. They are teaching examples, not reports from an employer or installation. The local labels are illustrative; they are not proposed replacements for a machine builder's definitions or an integration standard.
Lesson 1: Identify what "active" actually observes
Field example. The bracket program has started. The machine performs preliminary instructions and a tool change before the first cut. A display shows the same green "Running" label throughout. Someone reading the chart later calls the whole interval cutting time.
The label may faithfully represent the signal it receives while still supporting an inaccurate conclusion. MTConnect's Execution definition illustrates the distinction: ACTIVE describes a component executing an instruction. That definition does not, by itself, say that a tool is removing material from an acceptable production part.
Concrete checks. Ask the integrator to identify the source observation behind the label, including the component or path concerned. Write down the transformation between that observation and the dashboard wording. Walk through an ordinary, approved cycle with the operator and compare the displayed transitions with the work being performed. Record any interval that the display combines even though the team needs to distinguish it.
Do this through observation and documentation, following the site's normal operating arrangements. Changing a program to create convenient test signals is a separate task requiring its own review.
Lesson 2: Separate cutting from the purpose of the cut
Field example. Material is being removed from a trial bracket while the revised operation is checked. The program is active and the tool is cutting, but the team has not released the job for routine production. A daily summary counts the interval alongside established production work.
The missing information is the purpose of the operation. Motion and material removal do not establish whether the work is a trial, an approved production operation or a planned demonstration. The same physical activity can serve different purposes.
Concrete checks. Agree who identifies prove-out work and where that context is recorded. Check whether the production report needs a distinct category or an annotation linked to the interval. Define when that context ends, including who is authorized to release the operation under the site's existing procedures. Avoid assuming that a change from one machine state to another supplies that authorization.
Keep the additional reporting proportionate. The aim is a useful distinction, not a long list of reasons that operators cannot apply consistently. An explicit "purpose not recorded" entry is more honest than silently assigning every cutting interval to production.
Lesson 3: Give a necessary check its own context
Field example. The first revised bracket is waiting for a required dimensional check. The machine is not cutting. The operator has followed the agreed process, yet a report groups the interval with unexplained downtime.
A machine observation alone may not identify why work is waiting. The reason could be a planned check, missing information, an equipment problem or something else. Treating all of those as the same event makes the next conversation less precise.
Concrete checks. Identify what record establishes that a check is required and what record establishes its completion. Agree who supplies the waiting reason and when it should be entered. Decide how a correction will be made if the initial reason proves inaccurate. Check that the report keeps the observed state separate from the explanation attached to it.
The dashboard must not become permission to skip the check. It should help the team see the wait and understand it. If the goal is to improve the process, the useful question may be whether the required information or inspection resource was available when needed.
Lesson 4: Do not turn cycle completion into acceptance
Field example. The program reaches its end and the bracket is removed. A counter increases. Later inspection identifies a feature requiring further attention. A summary has already treated the increment as one finished, accepted part.
Several events have been collapsed into one: program completion, physical part removal, completion of all required operations and acceptance against requirements. A shop may connect those events through an established process, but the connection needs to be known rather than assumed.
Concrete checks. Ask what causes the counter to increase and whether the increment represents a cycle, a component or another defined unit. Check how multiple components, repeat operations and trials are handled where relevant. Identify the authoritative record for acceptance and determine whether the dashboard receives it. Keep the original event available when a later status changes.
A display can usefully report completed cycles without claiming to report accepted parts. Naming that limit makes the number more useful. It also gives the receiving team a clear question to resolve if the two totals differ.
Lesson 5: Keep the meaning of the label with the data
Field example. The team improves the bracket dashboard so that prove-out and check-wait intervals are visible. The following month, a comparison appears to show a change in performance. Part of the difference comes from the new categories, but the earlier definition was not retained.
A clearer vocabulary is progress. Comparing records made under different definitions requires context, however. Otherwise, an improvement in description can look like a change in the work itself.
Concrete checks. Keep a short state dictionary with the report: the source observation, the displayed wording, the interpretation permitted, the interpretation excluded and the owner of the definition. Record when a mapping changes. Include what the display does when an observation is missing or stale; lack of current information should remain distinguishable from a confirmed machine state. Revisit the dictionary with an operator when a new type of job exposes a gap.
The best question is not whether the dashboard contains every possible detail. It is whether a reader can tell what each claim rests on. That makes a disagreement easier to investigate and a useful observation harder to misuse.
Reference
MTConnect Standard, Part 3: Observation Information Model, version 2.5.0, January 5, 2026, section 5.2.48, Execution: https://docs.mtconnect.org/MBSD_MTConnect_Part_3_2-5-0.pdf