Data provider
A registered organization - typically an IoT platform operator - reviewed by the platform, pushing unit archives, device records and dynamic monitoring data per the interface specification, with its grantable scope configured.
Industry framework briefing · Updated
In one sentence: Who may read a building’s smoke-alarm heartbeat? Under the published model for community service operators, only whoever the owner authorized, through a token bound to a unit list and validity period - the shared data layer that lets buildings, platforms and assessors speak one language about fire safety.
At a glance
The question every building owner eventually asks - "who else can see my devices’ data?" - has a structural answer in this model, not a contractual one.
A registered organization - typically an IoT platform operator - reviewed by the platform, pushing unit archives, device records and dynamic monitoring data per the interface specification, with its grantable scope configured.
An organization that needs the data: it applies, states the data types and unit scope it needs, receives a token bound to the approved list and validity period, and calls only within that scope.
The building owner is the first collector and user of IoT data from the premises, and the beneficiary of its use. Aggregation and every later call are organized around the owner’s authorization.
The published flow is linear and auditable. Nothing moves until steps 6-7 have explicitly granted a unit scope, and every later call is validated against it.
| # | Step | What happens |
|---|---|---|
| 1 | Register | An organization self-registers online: identity, contact, business licence, and a declared provider or consumer role. |
| 2 | Qualification review | The platform reviews the application; approved accounts are activated, rejected ones return with reasons. |
| 3 | Provider registration | Approved providers register as data producers, maintaining the owner-unit list and facility-device archives they serve. |
| 4 | Data upload | Providers push unit and device archives plus dynamic monitoring data per the interface specification. |
| 5 | Consumption application | A consumer applies, declaring the data types and the owner-unit scope it needs to serve. |
| 6 | Authorization review | The platform or provider reviews and confirms the grant, aligning it with the owner’s authorization. |
| 7 | Unit-scope allocation | Accessible owner units are allocated one by one; anything not on the list is invisible to the consumer. |
| 8 | Token issuance | The platform issues an access token bound to the approved unit list and a validity period. |
| 9 | Authorized calls | The consumer calls interfaces with the token; the platform validates scope on every request and refuses anything beyond it. |
On the service side, the framework’s answer to invisible work is the record: every patrol, inspection, maintenance visit and assessment is captured against the building as it happens.
Invisible work becomes visible, checkable and comparable data; managers and clients can both see the shape of the service.
Traceable, comparable service records raise the certainty of buying and delivering services - the precondition for services to become products.
Every service - patrol, inspection, maintenance, assessment, drill - is recorded against the building as it happens: who did what, when, with what result.
| Path | Typical use |
|---|---|
| Manual entry | On-site staff record service results directly in the platform. |
| Excel import | Batch import of existing ledgers and checklists. |
| API integration | Existing property or fire-service tools connect through open interfaces and keep serving the unit alongside platform tools. |
| Consumer | Value |
|---|---|
| Government regions | Area risk pictures and targeted governance from aggregated, authorized data. |
| Service organizations | Proof of delivered work and a marketable service record. |
| Social units | Visible services and one data base per building they can audit. |
| Industry associations | A comparable basis for self-regulation, evaluation and training. |
The aggregation, management and metering layer for social-unit IoT data: third-party platforms register and are reviewed, push unit and device archives plus dynamic data, and consumers retrieve data only within authorized unit scopes.
It applies declaring the data types and owner-unit scope needed; after authorization review the platform issues a token bound to the approved unit list and validity period; requests beyond the scope are rejected.
No. Existing property-management or fire-service tools can connect through open interfaces and keep serving the unit; platform tools and existing tools operate side by side.
Every upload and every call is accounted against the declared scope, so data provision and consumption are measurable and chargeable rather than informal.
No. It means records gain governed value: ownership explicit, access authorized, use metered. No data leaves an owner’s control without explicit authorization.
Start where the leverage is: device archives and dynamic data through one aggregation layer, service traces through one record layer. Two integrations, one governed data base per building.
Scope disclosure: this page explains a published industry data framework in plain terms for fire-safety practitioners; it is educational and does not assert any participation status, designation or certification for Wanlin products. Program participation, assessments and certificate scope must be confirmed through the organizing bodies and, for devices, against the exact model and configuration. To discuss how your building data could meet the framework, contact wanlinfirecontrol@163.com or 4006-016-119 / +86 132 6167 7119.
The aggregation, management and metering layer for social-unit IoT data: third-party platforms register and are reviewed, push unit and device archives plus dynamic data, and consumers retrieve data only within authorized unit scopes.
It applies declaring the data types and owner-unit scope needed; after authorization review the platform issues a token bound to the approved unit list and validity period; requests beyond the scope are rejected.
No. Existing property-management or fire-service tools can connect through open interfaces and keep serving the unit; platform tools and existing tools operate side by side.
Also on this site: Fire Safety Data Production Framework · Fire Prevention Capability Index · Fire Industry Internet Demonstration Site, the aging-community renovation program, the product center for datasheets, and the site FAQ section., and the topic guides index