Parable City · Integration-led deployment

Identity and accountability for connected infrastructure.

Associate devices and properties with their owners. Define visibility, record administrative actions and connect authorised device records to city systems through FIWARE NGSI-LD.

Discuss an integration Open city dashboard

For: Infrastructure and integration teams
Interface: API and role-specific dashboards
Integration: FIWARE / NGSI-LD

Capabilities

Connect the asset, its owner and its operational record.

Device and property identity

Register identities, enrol devices under an owner and associate properties with their records. Owners and city operators have distinct views.

Visibility and city policy

Set device visibility and maintain city policy records. The city inventory exposes a reduced device view, including coarse location where supplied.

Incident approval records

Request bounded, expiring incident access and collect the required signatures, including the owner’s approval. Review the request and its audit history.

FIWARE integration

Map device records to NGSI-LD entities for a configured Orion-LD broker. Accept authenticated subscription notifications and record their payload commitments.

Example use case

A building owner and a city operations team.

A building owner registers a meter and chooses its visibility. An integration publishes the permitted device record to an Orion-LD broker. City operators review inventory and policy records, while recorded actions provide an audit trail for later inspection.

Deployment notes

Requirements and current scope

Provisioned identities: Registered owner and device identities, and a city-role identity for city operations. Opening the dashboard alone does not provision these roles.
Integration configuration: A configured City service and device onboarding process. FIWARE connectivity additionally requires an Orion-LD broker and authenticated callback configuration.
Current implementation: Device and property APIs, owner and city dashboards, policy records, incident approval workflows and a FIWARE bridge are implemented. Deployment is integration-led and requires validation against the target devices and operating environment.
Operational boundary: Recording an approval does not by itself actuate hardware or deliver sensor data. Device enforcement, telemetry transport and hardware attestation depend on the deployed integration.