Equipment data
Equipment inspection uses EntityPreview, DescriptionList, and OperationalStatus. The application supplies the equipment vocabulary, engineering values, and state decisions. These conventions describe how to keep those facts readable and distinct.
State has several meanings
| Fact | Example | What the application supplies |
|---|---|---|
| Requested state | Running | The requested target and its request identity |
| Observed state | Stopped | What the latest observation actually reported |
| Condition | Inspection required | The equipment assessment, independently of its operating state |
| Communication | Connected | Connection state; a connection can carry stale observations |
| Data quality | Stale | Whether the displayed evidence is current, stale, partial, unavailable, or unknown |
| Command result | Accepted | The authoritative outcome for that request; acceptance does not establish that the target state was reached |
| Alarm priority | High | The caller's alarm policy and priority, independently of acknowledgment and equipment condition |
Use the same shared detail rows for these facts. Use a text Badge where semantic emphasis helps, with a visible label. Keep repeated statuses free of boxes and indicators. Use ActionStatus when an action needs progress, feedback, or recovery controls. A snapshot can show its supplied command result as a plain detail row.
Alarm priorities, thresholds, suppression rules, equipment interlocks, and permitted commands belong to the application. Incident response and handover will demonstrate their lifecycle. The design system does not derive them from an icon, a color, or a measurement.
Measurements and limits
- Keep value and unit together. Preserve supplied precision:
0.000 kPadiffers from an unknown or unavailable reading. Counts should say what they count. - Name missing values. Use Unknown when no value was supplied; use Unavailable when the source explicitly cannot provide one. Show the supplied reason.
- Preserve the original. When the application converts or scales a reading, retain its raw value and unit and name the conversion. The UI displays the supplied result without recalculating it.
- Show the applicable range and its source. A bound may be one-sided. Keep the engineering unit explicit. Separate equipment limits from the plot's axis range.
- Use supplied assessments. Show Above maximum, Below minimum, Within limits, or Not evaluated in text. Applications own inclusivity, hysteresis, tolerances, validity checks, and any relationship between limits and alarms.
- Keep conversions consistent. A unit preference must convert the value and all associated bounds together. Never relabel an unchanged number. Incompatible units or absent bounds cannot support a Within limits assessment.
Range sources identify the applicable procedure, configuration, or revision. Unknown source information remains explicit. Stale evidence should say “Last reported above maximum”, rather than presenting a historical assessment as a current reading.
Source and time
Keep the source, observation timestamp, and data quality next to the readings. UTC is the example's display convention; a host can present an explicit timezone while preserving the original instant. A connection, command acknowledgment, or page refresh must not advance observation time.
The Facility Monitoring example groups readings from one coherent observation under a shared source and timestamp. If fields come from different sources or observation times, show that evidence per field or split the observations. Do not flatten unrelated readings under a single Current label.
Apply these conventions
The Facility Monitoring recipe maps equipment reports into EntityPreviewRecord while coordinating camera, pressure history and event evidence at a shared review time. It keeps explicit zero pressure, missing observations, stale evidence and unavailable cameras distinct.
Adapt the application data model to your equipment. The core presentation does not select operating limits, convert engineering units, infer freshness or issue machine commands. Consumers own these decisions and supply their outcomes alongside the readings.