Device Sensor & Computing Hardware

Findings

Catalogue-native findings must describe the information grouped by each layer. This legacy version does not declare them separately.

Questions & artifacts

Questions, artifact requirements and serial naming rules are required by Vercy vNext; they remain unassigned in this reference version.

Dimension & namespace

• EXTEND `world.physicalItem` (M2): a device is an item; identity, custody and location semantics are inherited.
• REFERENCE `world.equipment` (M6): machines are host assets for monitoring devices; the machine's condition data arrives through streams bound here.
• REFERENCE `world.vehicle` (M7): telematics units mount on vehicles as host assets.
• REFERENCE the digital cluster (D): the telemetry stream content itself is a digital-cluster object; this model keeps only the binding reference.
• imports: w3c-ssn-sosa (ALIGN): sensor, observation and observed-property semantics.
• imports: w3c-wot-thing-description (ALIGN): capability and interface description of the unit.

Canon, patches & standards

• EXTEND `world.physicalItem` (M2): a device is an item; identity, custody and location semantics are inherited.
• REFERENCE `world.equipment` (M6): machines are host assets for monitoring devices; the machine's condition data arrives through streams bound here.
• REFERENCE `world.vehicle` (M7): telematics units mount on vehicles as host assets.
• REFERENCE the digital cluster (D): the telemetry stream content itself is a digital-cluster object; this model keeps only the binding reference.
• imports: w3c-ssn-sosa (ALIGN): sensor, observation and observed-property semantics.
• imports: w3c-wot-thing-description (ALIGN): capability and interface description of the unit.

Artifact formats & serial data

Format-independent core. Concrete artifact formats and naming prefixes are not declared in this legacy version.

Policies & accepted processes

• `telemetryAccess`: owner-granted subscription to streams bound to named sensors, scoped by property and period.
• `deviceAttestation`: query contract by which a party verifies the unit's identity, firmware integrity and calibration standing.
• `maintenanceAccess`: grant allowing a service party to read operation state and apply firmware or configuration changes.

Read / add / edit / delete

CRUD procedures and interface bindings are not declared in this legacy version.

Ownership, roles & access

Each device record is stewarded by the device's owner per the catalogue's S1 ownership model; telemetry subscriptions, attestation queries and maintenance access exist only as S1/S2 grants from that owner, with operation-state changes traceable via S4 audit.

Objects

• `device`: one hardware unit; key attributes: serial reference, model reference, lifecycle status, owner reference.
• `deviceModel`: the class of the unit; key attributes: maker reference, model code, capability baseline.
• `sensorUnit`: a sensor hosted by the device; key attributes: sensor kind, position, calibration state.
• `observedPropertySpec`: what a sensor measures; key attributes: property, unit, range, accuracy.
• `telemetryStreamRef`: a reference to the stream carrying readings; key attributes: stream identifier, cadence, retention hint.
• `firmwareVersion`: an installed or installable firmware state; key attributes: version, release reference, integrity hash.
• `configurationProfile`: a named set of applied settings; key attributes: profile identifier, parameters, applied date.
• `networkEndpoint`: how the device is reached; key attributes: address kind, address, protocol, reachability status.
• `hostAssetRef`: the asset the device is mounted on; key attributes: target model, target identifier, mount role.

Relationships

• `device` -> instanceOf -> `deviceModel` (many-to-one): the unit inherits its model's capability baseline.
• `device` -> hosts -> `sensorUnit` (0..*): a device may carry zero or many sensors.
• `sensorUnit` -> observes -> `observedPropertySpec` (1..*): each sensor measures at least one property.
• `sensorUnit` -> emitsTo -> `telemetryStreamRef` (0..*): readings are bound to streams, not stored here.
• `device` -> runs -> `firmwareVersion` (1 current, 0..* historical): exactly one firmware state is current.
• `device` -> configuredBy -> `configurationProfile` (0..1 current): the profile in force, with history via events.
• `device` -> reachableAt -> `networkEndpoint` (0..*): endpoints may coexist across networks.
• `device` -> mountedOn -> `hostAssetRef` (0..1): the machine, vehicle, place or item the device serves.

Events

• `deviceProvisioned`: the unit was set up, identified and bound to an owner.
• `firmwareUpdated`: a new firmware version became the current one.
• `sensorCalibrated`: a hosted sensor's calibration was performed and recorded.
• `connectivityLost`: the device stopped being reachable at its endpoints.
• `connectivityRestored`: reachability resumed after an outage.
• `configurationChanged`: a different configuration profile or setting set took effect.
• `deviceCompromiseReported`: a security compromise or vulnerability affecting the unit was reported.
• `deviceDecommissioned`: the unit was retired and its bindings closed.

Projections

• `inventoryView`: identity, model, host asset and lifecycle status across a holding; omits streams and settings.
• `observabilityView`: sensors, observed properties and stream bindings; omits network addresses and security data.
• `securityAuditView`: firmware history, configuration changes and compromise reports; omits measurement semantics.