SDOS / SPP Data Asset Management | Wanlin Fire

Industry framework briefing · Updated

Data Governance for Fire Safety: First Steps for OEM and ODM partners

In one sentence: Two platforms carry the data layer of building fire safety: SDOS aggregates and meters IoT data from third-party platforms; SPP turns services such as patrols and maintenance into traceable records - the shared data layer that lets buildings, platforms and assessors speak one language about fire safety.

At a glance

Roles
Data owner (the building owner, first collector and beneficiary), data provider (registered platform pushing unit, device and dynamic data), data consumer (authorized caller within a granted unit scope)
Access control
Authorization is granted per unit list and validity period; consumers call interfaces with a token bound to that scope
Service records
SPP records each service - patrol, maintenance, inspection, assessment - against the building, via manual entry, Excel import or API
Value ladder
Digitalization, data-fication, asset-ization, capital-ization, monetization: each level makes safety records more accountable and more valuable

Three roles, one authorization chain

Services you cannot see, you cannot buy with confidence. Service records are what make fire-safety work comparable and auditable.

Data consumer

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.

Data owner

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.

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.

The nine-step path from registration to data call

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.

Registration to authorized calls
#StepWhat happens
1RegisterAn organization self-registers online: identity, contact, business licence, and a declared provider or consumer role.
2Qualification reviewThe platform reviews the application; approved accounts are activated, rejected ones return with reasons.
3Provider registrationApproved providers register as data producers, maintaining the owner-unit list and facility-device archives they serve.
4Data uploadProviders push unit and device archives plus dynamic monitoring data per the interface specification.
5Consumption applicationA consumer applies, declaring the data types and the owner-unit scope it needs to serve.
6Authorization reviewThe platform or provider reviews and confirms the grant, aligning it with the owner’s authorization.
7Unit-scope allocationAccessible owner units are allocated one by one; anything not on the list is invisible to the consumer.
8Token issuanceThe platform issues an access token bound to the approved unit list and a validity period.
9Authorized callsThe consumer calls interfaces with the token; the platform validates scope on every request and refuses anything beyond it.

SPP: services that leave shapes

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.

Service products

Traceable, comparable service records raise the certainty of buying and delivering services - the precondition for services to become products.

Service traces

Every service - patrol, inspection, maintenance, assessment, drill - is recorded against the building as it happens: who did what, when, with what result.

Service shapes

Invisible work becomes visible, checkable and comparable data; managers and clients can both see the shape of the service.

Ways in: manual, Excel, or API

Service-data capture paths
PathTypical use
Manual entryOn-site staff record service results directly in the platform.
Excel importBatch import of existing ledgers and checklists.
API integrationExisting property or fire-service tools connect through open interfaces and keep serving the unit alongside platform tools.

Who consumes, and what they get

Consumer types and value
ConsumerValue
Government regionsArea risk pictures and targeted governance from aggregated, authorized data.
Service organizationsProof of delivered work and a marketable service record.
Social unitsVisible services and one data base per building they can audit.
Industry associationsA comparable basis for self-regulation, evaluation and training.

The five-level data ladder

  1. Asset-ization. Governed, metered data with explicit ownership becomes a balanceable asset.
  2. Capital-ization. Provable data assets support financing and valuation.
  3. Monetization. Authorized products and services are paid for; data can be traded under governance.
  4. Digitalization. Devices and workflows go online; events become records.
  5. Data-fication. Records are structured under shared fields and dictionaries.

Where Wanlin fits

Frequently asked questions

What does metering mean here?

Every upload and every call is accounted against the declared scope, so data provision and consumption are measurable and chargeable rather than informal.

Does data asset-ization mean selling safety data freely?

No. It means records gain governed value: ownership explicit, access authorized, use metered. No data leaves an owner’s control without explicit authorization.

What is SDOS?

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.

How does a data consumer get access?

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.

Do we have to replace our current software?

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.

Next step

Nine steps, one principle: nothing moves without the owner’s authorization, and every movement is metered. That is the whole contract in one sentence.

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.

Evidence and references to request

What does metering mean here?

Every upload and every call is accounted against the declared scope, so data provision and consumption are measurable and chargeable rather than informal.

Does data asset-ization mean selling safety data freely?

No. It means records gain governed value: ownership explicit, access authorized, use metered. No data leaves an owner’s control without explicit authorization.

What is SDOS?

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.

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