Manual
Field-verified facts entered after site checks and document review: profiles, external environment, separation distances, policies, plans, training, inspections and response staffing.
Industry framework briefing · Updated
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
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.
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.
| Group | Size | Covers | Primary source |
|---|---|---|---|
| Common - building profile | 16 fields | Type, 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 type | Manual |
| Building fire prevention | 13 items | External environment, fire lanes, separation distances, fire resistance, height and storey type, building age, compartments, egress, layout, occupant density, interior linings, insulation, electrical equipment | Manual / AI |
| Fire protection systems | 7 systems | Outdoor and indoor hydrants, automatic alarm, automatic sprinklers, smoke control and exhaust, extinguishers and other means, maintenance regime | Manual / IoT |
| Fire safety management | 5 duties | Safety policy and archives, emergency and evacuation plans, training and drills, daily and periodic inspection, on-site response capability | Manual |
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.
Field-verified facts entered after site checks and document review: profiles, external environment, separation distances, policies, plans, training, inspections and response staffing.
Live facility status reported by connected sensors: electrical load and detection results, hydrant pressure, alarm and sprinkler health, online status and long-unresolved faults.
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.
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.
Answers draw on one shared dictionary so values compare across platforms and years. Samples:
| Enumeration | Values |
|---|---|
| Structure type | Reinforced concrete / frame / steel structure / temporary |
| Fire-resistance level | Level 1 / Level 2 / Level 3 / Level 4 / below Level 4 |
| Combustion performance | A / B1 / B2 / B3 |
| Fire hazard class | Class A / B / C / D / E (Jia-Yi-Bing-Ding-Wu) |
| Storey type | Single-storey / multi-storey / high-rise / underground |
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 field | Device family | What it proves |
|---|---|---|
| Protection-system status (hydrant, sprinkler, tank) | WANLIN-770 4G pressure gauges, WANLIN-780 4G level gauges | Mains 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 / 711 | Design versus measured load and electrical fault detection at distribution boxes |
| Alarm system networking (indicator 2.3) | WANLIN-921 user information transmission | Networks an existing fire alarm panel; online and linkage status supervised (GB 26875.3) |
| Detection coverage in corridors, sheds and homes | WANLIN-307 / 309 / 310 smoke, WANLIN-340 heat | Battery-powered points whose installed-and-online state is itself verifiable data |
| Maintenance evidence (indicator 2.7) | Cloud maintenance tickets and patrol records | Faults, repairs and monthly upkeep leave timestamped records rather than claims |
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.
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.
No. The framework standardizes the data layer that assessments and platform scoring consume; formal conclusions still follow the applicable regulations and qualified assessors.
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).
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.
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.
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.
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.
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