Enobase Internet of Things · Productivity
Give a device reading a business context.
A useful reading needs more than a number.
Identify the source
Name the device, the measurement and its unit before designing the ingestion.
A useful reading needs more than a number.
Name the device, the measurement and its unit before designing the ingestion.
The details that make the record useful.
Choose the fields that explain the work and the next decision.
A named device
Keep the device identity separate from its latest measurement.
An explicit unit
Record what is measured and how its value is expressed.
A timestamp
Keep the measurement time so an old reading is not mistaken for a current one.
A business relationship
Identify the equipment, lot or check the reading belongs to.
The same starting point, shaped for different teams.
These illustrative configurations show how the unit of work changes with the operation.
A food team records a cold-room reading
The record needs the sensor, temperature unit and measurement time. Operational thresholds and alerting require explicit validation.
A workshop records a dimension
The record needs the instrument, millimetres and work-order reference. The measurement belongs to a specific quality check.
Define the record before connecting the device.
Model the source, timestamp, unit and business relationship in your workspace. Device compatibility and ingestion are part of the integration scope.
Keep the hand-offs explicit.
Start from the records on each side, then agree which actions belong in the configured process.
Prepare the quality record
Define how a measurement will support a quality check.
Prepare the quality recordKeep equipment context
Associate the device data with the equipment being followed.
Keep equipment contextQuestions about Internet of Things
Start with a defined process and its required records. Agree the configuration and connected actions before extending it to other teams.


