IoT / Foundation
Use properties, events, and actions to connect device semantics with product definitions, data interpretation, control parameters, and business interfaces.
THE CUSTOMER PROBLEM
Two vendors may both report temperature while using different field names, units, precision, and read/write behavior. Carrying those differences into every page and statistic creates repeated integration work. A thing model gives these agreements a reusable home.
MECHANISM / REASON / TRADE-OFF
Common, category, product, and device levels serve different reuse scopes. A product model groups properties, events, and actions; configure device-specific differences through the supported model mechanisms.
Properties describe state and values, events record occurrences, and actions describe callable capabilities. Identifiers, types, units, and access constraints form the device contract.
Message parsing, parameter validation, historical data, and visualization bindings work around model definitions. Business tools still use real interfaces to read or control devices.
A CONCRETE EXAMPLE / MECHANISM EXAMPLE
A field-mapping example, not measured device data. Map the source field, standard identifier, data type, and display unit explicitly.
READY TO INTEGRATE
CONTINUE WITH THE FOUNDATION
