IoT & smart cities | Modelled case study
Enroll unique identities for a citywide sensor fleet
Can each camera, meter, light, and environmental sensor be traced to an authorized manufacturing and enrollment event?
The modelled organisation
A recognisable problem reaches the operating agenda
This composite scenario follows the Smart City Platform · Device Operations · Procurement functions. It is grounded in the cited problem context but does not identify a real customer.
Operating environment
A city or IoT operator manages large fleets of constrained sensors, gateways, cloud ingestion, device enrollment, updates, support commitments, and multiple vendors.
What is at stake
A shared credential or abandoned update path can expose an entire fleet whose devices differ in hardware, connectivity, ownership, and remaining support life.
Situation
Mass procurement encourages shared bootstrap credentials and opaque vendor roots that undermine revocation and device attribution.
Event that forces action
New city platform, multi-vendor tender, or discovery of cloned device credentials.
Concrete system boundary
Systems this case study puts in scope
The model is specific about the operational surfaces that must be discovered, changed, or independently checked.
city sensor fleet
manufacturing and field enrollment
device identity registry
replacement and ownership transfer
Modelled case study walkthrough
How this organisation would use QNSI
The walkthrough connects the real-world problem to a bounded QNSI contribution and an independently reviewable result.
Recognise the operating condition
Mass procurement encourages shared bootstrap credentials and opaque vendor roots that undermine revocation and device attribution.
Frame the decision the owners must make
Can each camera, meter, light, and environmental sensor be traced to an authorized manufacturing and enrollment event?
Apply QNSI to the controlled boundary
Track device identity, manufacturing source, issuer, algorithm, owner, location, and enrollment evidence in QNSI.
Leave the team with a concrete result
A municipal device identity ledger with duplicate credentials, unapproved issuers, and enrollment confidence.
Prove the result in the organisation's environment
The city tests factory provisioning, anti-cloning, privacy, physical replacement, revocation, and supplier evidence.
What useful success looks like
A decision artifact plus proof from the real environment
The model stops at a target result. It becomes an actual case study only when a customer produces and independently validates this evidence in production.
Decision artifact
A municipal device identity ledger with duplicate credentials, unapproved issuers, and enrollment confidence.
Independent validation boundary
The city tests factory provisioning, anti-cloning, privacy, physical replacement, revocation, and supplier evidence.
Real-world problem grounding
Primary sources behind the model
These sources establish the external requirement, failure mode, or risk context used to model this case. They do not endorse HEOSSI or prove that QNSI completed the scenario.
Customer evidence status
This is modelled, not a customer claim
The organisation is a composite and the result is a target state. This page does not prove a deployment, customer outcome, certification, legal conclusion, regulator endorsement, or completed control.