Fire Safety Data Production Framework | Wanlin Fire

Industry framework briefing · Updated

The First Step Toward a Capability Index: Data Production for OEM and ODM partners

In one sentence: A capability score is only as good as the fields beneath it - the shared data layer that lets buildings, platforms and assessors speak one language about fire safety.

At a glance

Collection scope
16 building-profile fields, 13 building fire-prevention indicators, 7 fire-protection systems, 5 management duties
Data sources
Three declared source types: manual entry after site checks, IoT devices reporting live status, AI-assisted recognition
Granularity anchor
GB/T 41020-2021 (fire risk assessment guideline for building property insurance) is the declared minimum granularity
Rule of the game
Third parties submit raw fields under fixed field names; compliance judgement and scoring are computed, not self-declared

Why a shared data language comes first

Platform scores diverge for one reason: the inputs are not the same. A shared collection framework makes the inputs identical, so any compliant platform computing the same fields reaches comparable results.

Four data groups, forty-one fields

The reference framework fixes the collection scope before any scoring is discussed. Each row below is a family of fields with a declared primary source; profiles feed every later judgement, including whether a protection system is even required.

The four collection groups
GroupSizeCoversPrimary source
Common - building profile16 fieldsType, nature, height, storeys above and below grade, total and footprint area, volume, largest single floor, hazard class, seat and bed counts, central air conditioning, fire-resistance level, construction date, use typeManual
Building fire prevention13 itemsExternal environment, fire lanes, separation distances, fire resistance, height and storey type, building age, compartments, egress, layout, occupant density, interior linings, insulation, electrical equipmentManual / AI
Fire protection systems7 systemsOutdoor and indoor hydrants, automatic alarm, automatic sprinklers, smoke control and exhaust, extinguishers and other means, maintenance regimeManual / IoT
Fire safety management5 dutiesSafety policy and archives, emergency and evacuation plans, training and drills, daily and periodic inspection, on-site response capabilityManual

Three sources, one record

Every field carries a declared source type, and the mix matters: data completeness, value density and the manual / IoT / AI ratio are themselves evaluation dimensions in the downstream program.

Manual

Field-verified facts entered after site checks and document review: profiles, external environment, separation distances, policies, plans, training, inspections and response staffing.

IoT devices

Live facility status reported by connected sensors: electrical load and detection results, hydrant pressure, alarm and sprinkler health, online status and long-unresolved faults.

AI assisted

Image and video recognition where it is reliable: lane and egress obstruction monitoring, reading combustion-performance grades of linings and insulation, with human review of results.

What the system computes versus what people submit

The boundary is explicit: people submit raw fields; judgement is computed. This is what keeps two platforms from reaching two different truths from the same building.

Computed by the system - nobody submits these

  • Separation-distance compliance and its five-band grading
  • Storey type (single / multi-storey) from profile fields
  • Building age computed from construction date
  • Compartment compliance and count
  • Occupant density from peak and off-peak flow entries
  • Electrical load ratio from design and measured load
  • Whether a protection system is required at all, judged from the profile

Submitted by people after site checks

  • Site-verified profile fields and hazard class
  • External environment and adjacent-building facts
  • Compartment layout and egress details
  • Management records: policy, plans, training, inspections
  • Extinguisher configuration grading (five-band choice)

Shared enumeration dictionaries

Answers draw on one shared dictionary so values compare across platforms and years. Samples:

Enumeration samples
EnumerationValues
Structure typeReinforced concrete / frame / steel structure / temporary
Fire-resistance levelLevel 1 / Level 2 / Level 3 / Level 4 / below Level 4
Combustion performanceA / B1 / B2 / B3
Fire hazard classClass A / B / C / D / E (Jia-Yi-Bing-Ding-Wu)
Storey typeSingle-storey / multi-storey / high-rise / underground

How monitoring hardware feeds the framework

The IoT-sourced fields are only as real as the devices behind them. The mappings below show published Wanlin device families against the framework fields they feed; model selection always follows the site survey.

Framework fields to device families
Framework fieldDevice familyWhat it proves
Protection-system status (hydrant, sprinkler, tank)WANLIN-770 4G pressure gauges, WANLIN-780 4G level gaugesMains pressure and tank levels reported live instead of graded from an annual reading
Electrical load and detection (indicator 1.13)Smart electricity set: host 705 with breakers 710 / 711Design versus measured load and electrical fault detection at distribution boxes
Alarm system networking (indicator 2.3)WANLIN-921 user information transmissionNetworks an existing fire alarm panel; online and linkage status supervised (GB 26875.3)
Detection coverage in corridors, sheds and homesWANLIN-307 / 309 / 310 smoke, WANLIN-340 heatBattery-powered points whose installed-and-online state is itself verifiable data
Maintenance evidence (indicator 2.7)Cloud maintenance tickets and patrol recordsFaults, repairs and monthly upkeep leave timestamped records rather than claims

Frequently asked questions

Why are interfaces keyed by field name?

Collections are submitted against fixed field names (for example build_height, fire_resistance_level), so any compliant platform can consume the same inputs and produce comparable outputs.

How fresh are the data?

Static records such as profiles and archives are manually re-verified on a published cycle (90 days in the reference design); IoT-sourced status refreshes in minutes and triggers alarms in real time.

Does this replace a formal fire-risk assessment?

No. The framework standardizes the data layer that assessments and platform scoring consume; formal conclusions still follow the applicable regulations and qualified assessors.

What exactly is being collected?

Four groups: 16 building-profile fields (type, height, storeys, areas, hazard class, fire-resistance level, construction date), 13 building fire-prevention items (lanes, separation, compartments, egress, occupant density, linings, electrical), 7 fire-protection systems (hydrants indoors and out, alarm, sprinkler, smoke control, extinguishers, maintenance) and 5 management duties (policy, plans, training, inspection, response capability).

Do third parties have to judge compliance themselves?

No. Third parties submit raw fields; system-computed items - separation-distance grading, storey type, building age, compartment compliance, occupant density, load ratio, and whether a system is required at all - are calculated by the model.

Next step

Data production is unglamorous and decisive: a building whose forty-one fields are current can be scored by anyone; a building with a folder of PDFs cannot. Start with the field list, not the dashboard.

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

Why are interfaces keyed by field name?

Collections are submitted against fixed field names (for example build_height, fire_resistance_level), so any compliant platform can consume the same inputs and produce comparable outputs.

How fresh are the data?

Static records such as profiles and archives are manually re-verified on a published cycle (90 days in the reference design); IoT-sourced status refreshes in minutes and triggers alarms in real time.

Does this replace a formal fire-risk assessment?

No. The framework standardizes the data layer that assessments and platform scoring consume; formal conclusions still follow the applicable regulations and qualified assessors.

Also on this site: SDOS / SPP Data Asset Management · 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