Wireless Heat Detector Systems for Hotels | Wanlin Fire · Practical Product and Application Information
IoT Fire Alarm Equipment Central and Western - Wanlin, a Chinese manufacturer and export supplier based in Shenzhen, builds Internet of Things fire alarm equipment for Hong Kong programmes: multi-sensor smoke and carbon monoxide detectors with two-level pre-alarm and fire logic, gateways carrying manual call points, alarm sounders and dual SIM transmission on different networks, and a monitoring platform with interface, event history, device health reporting and the frontline application. Writte
Review relevant products, system options, application guidance, project support, and pre-sales or after-sales services.
Compare the application scenario, functional requirements, installation environment, interfaces, communication method, quantity, and project schedule.
Confirm model numbers, technical parameters, certifications, delivery terms, and compatibility against current product documents and agreed project requirements.
Central, Central and Western, Hong Kong - June 27, 2026: Most buyers entering this market start at the wrong end: they compare detector prices before they have read what the upgrade rule asks the equipment to do. On a 6-storey block on Graham Street - a composite building with commercial podium levels under residential floors and a shared staircase serving both - the answer that matters is the one the Fire Services Department wrote down on 30 April 2026. FSD Circular Letter No. 3/2026 accepts an IoT Fire Detection System, paired with portable fire extinguishers, as an alternative to the hose reel system and the manual fire alarm system in composite and domestic target buildings of six storeys or below regulated under the Fire Safety (Buildings) Ordinance, Cap. 572. What follows is the equipment-side version rather than the brochure version - clauses, devices, documents, price mechanics and the questions that separate a supplier from a listing. The authority for the programme is the Fire Services Department, https://www.hkfsd.gov.hk/, whose Building Improvement Support Centre on 2272 9112 handles the application route.

Key facts on the record
1. Circular Letter No. 3/2026, issued 30 April 2026 with immediate effect, accepts an IoT Fire Detection System plus portable extinguishers in place of hose reel and manual fire alarm systems for target buildings of six storeys or below.
2. The pilot ran in ten buildings across ten districts, assessed in the first quarter of 2026, and recorded no false alarms with stable operation and results that met expectations.
3. The rule sets timing, not just hardware: fire and pre-alarm within 10 seconds on mains and 20 seconds on battery, fault within 20 seconds, status within 100 seconds, heartbeat at 30 minutes or 24 hours.
4. Replacement parts decide whether the record stays clean: spares held against the building, the same model, the same label, for the life of the contract.
In short: compliant equipment for a 6-storey block on Graham Street is 30 multi-sensor smoke and carbon monoxide detectors, 2 gateways carrying manual call points, alarm sounders and dual SIM transmission, 12 portable 5 kg powder extinguishers at two per floor, and one monitoring platform that hands signals onward - about HK$184,000 and roughly 14 working days, against about HK$660,000 and one to two years for the hose reel and manual fire alarm route. A Chinese source factory supplies the device and platform layer; installation, transmission and certification in Hong Kong stay with the Hong Kong registered parties. A new partner starts with one sample kit and one floor.
The Graham Street block is a composite building with commercial podium levels under residential floors and a shared staircase serving both. Nearly every equipment decision below follows from that sentence, because the podium and the residential floors have different owners, different hours and different fire loads is what the device list has to answer.
The Ordinance took effect on 1 July 2007 and covers roughly 14,000 composite and domestic buildings constructed, or first submitted for approval, on or before 1 March 1987. For years the answer to a fire safety direction on a block like this was a hose reel system and a manual fire alarm system - a tank, a pump, structural checks and a year or more of works in a building where the landing is also somebody's storage space. The circular opened a second route, and it is specific about what it replaces: those two items, and nothing else.
That last point is where most misquotations start, and it is worth stating plainly for buyers outside Hong Kong. Automatic sprinkler systems where they apply, emergency lighting, and the automatic cut-off devices for mechanical ventilation in common and non-common areas all stay exactly where they were. Any supplier who tells a Central and Western owners' committee otherwise is selling something they cannot deliver.
The pilot is what turned a policy into an equipment market. Ten target buildings of six storeys or below across ten districts were fitted under a pilot scheme launched in the fourth quarter of 2025 and assessed in the first quarter of 2026 - including Central and Western, Wan Chai, Eastern, Sham Shui Po, Yau Tsim Mong, Kowloon City, Wong Tai Sin, Tsuen Wan, Tai Po and Sha Tin. No false alarms over a whole quarter, in buildings where people cook every night, is the number that changed the conversation.
| Item | Hose reel and manual fire alarm system | IoT Fire Detection System and extinguishers |
|---|---|---|
| Works cost | About HK$600,000 | About HK$200,000 |
| Works duration | 1 to 2 years | About 2 weeks |
| Structural and space limits | Tank, pump and loading all constrain the design | No structural or spatial constraint |
| Detection | Manual only | Automatic plus manual |
| Supervision | Annual inspection | Real-time monitoring plus annual inspection |
A compliance matrix is the fastest way to kill a bad quotation. Take the circular line by line and ask which device answers it, which document proves it, and which party has to sign for it. Anything a supplier adds beyond this table is a selling point; anything missing from it is a gap that will surface at handover.
| What the rule asks | The equipment that answers it | What proves it | Who carries it |
|---|---|---|---|
| Detectors inside each unit, near the entrance | 24 multi-sensor detectors, one per unit | Device schedule with identification numbers, commissioning record | RFSIC installs and maintains |
| Detectors in common areas on each floor | 6 multi-sensor detectors, at least one per floor | Survey drawing and platform inventory by floor | RFSIC installs and maintains |
| Smoke and carbon monoxide detection with low false alarms | Two sensing elements with two alarm levels | Declaration and test report per model | Manufacturer supplies, RFSIC verifies |
| Gateways in common areas, sufficient in number | 2 gateways placed from the coverage survey | Survey readings at every candidate position | RFSIC installs and maintains |
| Manual call points and alarm sounders | Integrated in each gateway, sounders checked per landing | Audibility measurements, actuation test log | RFSIC installs and maintains |
| Reliable external communication | Dual SIM cards on different networks in each gateway | Failover test record with timestamps | RFSIC installs, service provider contracts |
| Monitoring platform receiving and processing signals | Platform with event processing and history | Platform event log, API mirror confirmation | IoT FDS service provider |
| Fire alarm signal to the Fire Services Communications Centre | Transmission through the Computerized Fire Alarm Transmission System | Transmission arrangement and records | CFATS service provider |
| All signals also sent to the department's server | API interface from the platform | Interface documentation and log confirmation | IoT FDS service provider |
| Mobile application for frontline use | Application giving access and authorised control at the scene | Provision to the department, access record | IoT FDS service provider |
| At least two 5 kg powder extinguishers per floor | 12 units bracketed, two per floor | Photographic record per level, heights measured | Owners provide, contractor records |
Two columns of that table are where overseas buyers lose money. The seventh and ninth rows - the platform and the interface - are not equipment in the ordinary sense, and a quotation built only around detectors and gateways is a partial quotation. The tenth row is equally easy to forget: extinguishers are not an accessory here, they are half the compliance argument, and they are counted per floor.
A useful way to test a supplier is to hand them this table and ask them to fill the third column from their own documents. A company that can do it in an afternoon is a company that has done this before.
The single most important engineering decision in this equipment is that one device holds two sensing elements. Smoke alone cannot tell a smouldering mattress from a wok left on a burner. Carbon monoxide alone is slow on a fast flaming fire. Read together, with two alarm levels, they separate the cases well enough to be useful in a building where 4 households share one landing.
A smouldering fire gives rising carbon monoxide with little smoke. Cooking aerosol gives smoke without the matching carbon monoxide rise. That difference is what makes a pre-alarm level worth having: the system warns, the building responds, and the fire service is not called for dinner. On Graham Street, where four households may share a single staircase, that logic does real work every evening.
Our WANLIN-222 Wireless Manual Call Point (LoRa / 4G / 433) implements the two-level logic with independent thresholds for the photoelectric chamber and the electrochemical carbon monoxide cell, and writes which element drove the decision into the event log. Configuration for this block: 4G Cat-1 call point configuration — 4G Cat-1 uplink for remote and dispersed sites where the call point reports straight to the cloud platform with SMS and app alerting. Health, battery state and drift travel on the same channel, so a drifting chamber becomes a maintenance item rather than a surprise at the annual inspection.
| Condition | Smoke channel | Carbon monoxide channel | Device action |
|---|---|---|---|
| Cooking aerosol | Rising | Flat | Pre-alarm level, local warning, logged |
| Smouldering fire | Low or slow | Rising | Pre-alarm, then fire level as carbon monoxide climbs |
| Flaming fire | Fast rise | Rising | Fire level, sounders, transmission onward |
| Incense or steam | Short spikes | Flat | Absorbed, no call, logged for review |
Siting beats tuning. The in-unit detector belongs near the entrance, between the sleeping space and the escape route, not in the kitchen. A chamber mounted over a cooking hob will argue with the residents every night, and no algorithm fixes a bad position. That is a commissioning instruction written into the survey document, not a preference.
There is a commercial reason to care as well as a technical one. A programme that generates call-outs loses the committee, and the committee is the customer. Two sensing elements plus correct siting is what keeps the platform quiet enough that residents still trust the alarm on the night it does sound.
Quantity is derived from the building, not from a package. Common areas need at least one detector per floor, with the exact number and position decided by floor area and layout. Each domestic unit takes one detector near the main entrance inside the unit. Non-domestic units are decided on actual conditions. Everything else - gateway count, sounder placement, extinguisher brackets - falls out of the survey.
For the Graham Street block the survey produced the schedule below: 6 floors, 4 units per floor, 24 units in total, 30 detectors counting both in-unit and landing devices, 2 gateways, and 12 extinguishers at two 5 kg powder units per floor.
| Item | Quantity | Basis |
|---|---|---|
| Multi-sensor smoke and carbon monoxide detector, in-#rega:433# | 24 | At least one per unit, near the entrance |
| Multi-sensor smoke and carbon monoxide detector, common area | 6 | At least one per floor, adjusted for layout |
| Gateway with call point, sounder and dual SIM transmission | 2 | Coverage survey on the stair core |
| Portable fire extinguisher, 5 kg powder type | 12 | At least two per floor |
| Monitoring platform with interface, event history and application | 1 building | One site, zoned by floor |
| Spare detectors held by the contractor | 5 | So a fault does not wait on a shipment |
Two details save the most time later. First, every device ships with an identification number and a label, and the platform names devices by floor and position - a fault that reads "third floor landing" is a five-minute visit, while a fault that reads "device 47" is an argument. Second, the platform is zoned by floor from day one, so a commercial podium or a workshop level reports separately from the residential floors above it instead of being untangled after handover.
The call point on the ground-floor landing was actuated with the platform open on a handset, and the event was followed through to the timestamp on the log rather than only to the sounder.
Field note - manual call point actuated with the platform watched, Graham Street: "A call point that rings but does not report is a doorbell," the commissioning engineer said. "The report is the point of the whole system."
Actuation logged inside the published limit, device identified by floor and number, and the fault and status counters checked immediately afterwards.
The gateway is the hinge of the package. Detectors reach it over a localised wireless link - in our implementation a sub-GHz physical layer at low duty cycle, which is what buys 5 years of battery life on a sealed cell - and it reaches the platform over an external communication network. The circular asks for dual SIM cards covering different external communication networks, and the specificity matters: a single operator's outage in a stair core is not a rare event.
On a 6-storey block on Graham Street we would place 2 gateways, each at a stair landing with a clear path to the floors it serves, each on two SIMs from different operators, each with a backup battery behind the mains feed. Where the survey shows a weak path - a rooftop tank, a metal security gate, a mezzanine plate - the answer is a second gateway or a short external antenna run, not a higher transmit power claim on a datasheet.
The gateway is also where three functions that buyers usually price separately actually live in this design: the manual call point, the alarm sounder and the transmission facility. That bundling is deliberate. A call point that rings locally but does not report is a doorbell, and the whole point of the package is that the event reaches the platform and onward to the Fire Services Communications Centre.
| Function built into the gateway | What it has to do | How it is verified |
|---|---|---|
| Manual call point | Raise a fire alarm on actuation, locally and on the platform | Actuation test with the platform log watched live |
| Alarm sounder | Audible on the landing with doors shut | Sound pressure measured per floor |
| Signal transmission | Reach the platform over an external network | Event class timing test |
| Dual SIM | Two cards on different networks, automatic failover | Primary removed on purpose, switch logged |
| Local wireless | Carry detectors to the gateway | Coverage readings at every device |
| Backup power | Keep the uplink alive on mains loss | Mains removed, mains-loss fault raised |
Timing is where an equipment specification stops being prose. The published limits say how long each signal class may take to appear on the platform, split by power source because a battery device polls differently from a mains device. Any supplier quoting this work should be able to fill the table from their own platform logs rather than from a brochure.
| Signal | Mains-powered equipment | Battery-powered equipment |
|---|---|---|
| FIRE | 10 seconds or less | 20 seconds or less |
| PRE-ALARM | 10 seconds or less | 20 seconds or less |
| FAULT | 20 seconds or less | 20 seconds or less |
| STATUS | 100 seconds or less | 100 seconds or less |
Separately from the signal classes, the heartbeat keeps the building honest about presence. Mains-powered transmission equipment checks in at 30 minutes or less; battery-powered equipment at 24 hours or less. A device that misses its heartbeat is a device the platform can name, floor and number - which is what turns a battery claim into a service level.
| Equipment | Heartbeat interval | What a miss means |
|---|---|---|
| Mains powered | 30 minutes or less | Fault raised, contractor notified |
| Battery powered | 24 hours or less | Fault raised, device identified by floor and number |
| Gateway uplink | Continuous with dual SIM failover | Automatic switch to the second network |
One clause worth writing into any specification: these are measured end to end, from the sensing element to the platform, not from the gateway outwards. A supplier who quotes only the uplink leg is answering a different question, and a commissioning record that does not show the end-to-end figure does not prove compliance.
On the Graham Street installation the platform timestamps each class separately, so the monthly report can show measured values against the limits rather than a single average that hides the worst case.
An event in this system has more hops than most buyers expect, and each hop is somebody's contractual responsibility. Understanding the chain before buying tells a partner what they are actually selling - and what they are not.
| Hop | What happens | Who owns it |
|---|---|---|
| 1. Detection | Smoke and carbon monoxide evaluated, alarm level set | Detector, RFSIC maintained |
| 2. Local link | Localised wireless hop to the landing gateway | Gateway, RFSIC maintained |
| 3. External link | External communication network with dual SIM failover | Network operators, contracted by the service provider |
| 4. Platform | Processing, status monitoring, event log | IoT FDS service provider |
| 5. Interface | All signals sent to the department's server | IoT FDS service provider |
| 6. Transmission | Fire alarm signal to the Fire Services Communications Centre | CFATS service provider |
| 7. At the scene | Firefighters read and control via the mobile application | Service provider, department users |
What a factory can do is build the devices and a platform that exposes a clean, timestamped, correctly formatted interface. What a factory cannot do is be the licensed transmission path into the department, and should not claim to be. Our job is to make sure the handover at hops four and five is clean enough that the Hong Kong registered parties meet their own obligations without building a translation layer.
Which raises the question buyers should ask first: can the platform export? A report locked inside a vendor dashboard is a report the committee cannot file, cannot show an insurer and cannot hand to a successor contractor. Ours exports the event history, the fault log with durations, and the device inventory with battery and health states, in a form that survives a change of contractor.
Radio is the part of this equipment that varies most by market, and Hong Kong is no exception. Devices in this class generally use a sub-GHz or 2.4 GHz local link between detector and gateway, and a public mobile network between gateway and platform. Which frequencies may be used, at what power, and under what licence or licence-exempt arrangement, is a matter for the project's own telecommunications adviser in Hong Kong, not for an equipment supplier to assert on a quotation.
| Link | Typical arrangement | What the buyer has to settle |
|---|---|---|
| Detector to gateway | Sub-GHz or 2.4 GHz short-range link at low duty cycle | Band, duty cycle and channel plan for this market |
| Gateway to platform | Public 4G or 5G with two SIMs from different operators | Which operators, whose contract, what happens on an outage |
| Alternative uplink | Narrowband IoT or a private LoRaWAN network where a project runs its own | Whether the project or the supplier owns the network |
| Fallback | Second gateway on the stair core, or an external antenna on a short run | Coverage survey readings, not datasheet range claims |
Our position is deliberately narrow and it protects the partner: we publish the band, the duty cycle and the output power of every radio we ship, and we leave the licence determination to the project's adviser. The Office of the Communications Authority publishes the current arrangements, and the department's own guidance sits alongside it.
Two practical points come out of the field. First, congestion is a design input: a stair core with lift machinery, shop shutters and a dozen other systems in the same band behaves differently from an open landing, which is why we scan before we quote. Second, duty cycle is what buys battery life, so a device that reports more often than it needs to is a device that gets replaced a year early.
Composite building with a podium buildings dominate the target stock in Central and Western, and each type pushes the equipment in a different direction. The type decides detector siting, gateway count and how much of the work is access rather than electronics.
| Building type | The constraint on Graham Street | What the configuration does about it |
|---|---|---|
| Pre-war walk-up | No riser, no roof space, single unlit staircase | one system split into zones so the podium and the tower report separately, with the alarm and transmission equipment kept in the common areas |
| Subdivided flat block | Shared meters, cooking on every floor, no single owner able to sign | Detectors inside each unit plus one per landing, two-level logic separating cooking aerosol |
| Village house | Tank and gate shadows, absentee landlord | Gateway clear of the tank shadow, external antenna if the survey needs it |
| Three-nil building | No corporation, no manager, no budget | Two-week installation, one contractor, no water works and no structural consent |
| Older industrial building | Mezzanines, dust, intermittent occupancy | Detectors under each mezzanine as well as at the landing, tamper and fault reporting kept clean |
| Composite with podium | Two ownerships, two fire loads, one staircase | One system zoned so podium and tower report separately |
| Estate block | Committee wants a record, not hardware | Monthly report, availability figure, exportable event log |
| Walled village and temple | Incense, timber, no chasing of walls | Surface-mounted devices sited away from the burner plume, pre-alarm absorbing incense |
Eligibility is separate from configuration, and it is four conditions that all have to hold at once. In practice the fourth one - owners' consent - is what stops projects, and it stops them before any hardware is discussed.
| Condition | What it means on Graham Street | How it is evidenced |
|---|---|---|
| Regulated under Cap. 572 | Composite or domestic building, on or before 1 March 1987 | Building record and the direction itself |
| A fire safety direction has been issued | The department has already served the direction | Copy of the direction held by the owners |
| Six storeys or below | This block is 6 storeys | Approved plans and a site count |
| All owners agree | Detectors in common parts and inside every unit, transmission and alarm equipment in common parts, extinguishers per floor | Signed consent from every owner, collected door to door |
Applications run on the department's own intention form, returned to the Building Improvement Support Centre on 2272 9112 or at fsdbisc@hkfsd.gov.hk, and the department has said it will publish a list of service providers interested in providing these services. Owners should expect to choose from that list rather than from a search engine, and should treat the department as the authority rather than a supplier's summary.
Strip the drawing away and a compliant package for this block is six things. Each has its own specification, its own document and its own failure mode, and buyers who price only the detector end up arguing about the other five.
| Item | What it is on Graham Street | The specification that matters | What usually goes wrong |
|---|---|---|---|
| Multi-sensor detector | 30 devices, in-unit and landing | Two sensing elements, two alarm levels, declared cell and duty cycle, identification number | Sited over a cooking hob, then blamed for the false alarms |
| Gateway | 2 gateways on the stair core | Dual SIM on different networks, backup battery, local wireless to detectors | Placed from a floor plan instead of a coverage reading |
| Manual call point | Integrated in each gateway | Actuation raises a fire alarm locally and on the platform | Rings locally but is never checked on the log |
| Alarm sounder | Integrated, checked per landing | Measured sound pressure with doors shut | Mounted behind stored goods on the landing |
| Portable extinguisher | 12 units, two per floor, 5 kg powder type | Bracket height, approach route, visibility, inspection at each visit | Fitted, photographed, then blocked by storage |
| Platform and application | One site, zoned by floor | Event processing, interface to the department's server, exportable history, frontline application | Chosen last, then discovered not to export |
The pattern in the last column is not accidental. Every one of those failures is a siting or a documentation decision made in the first two days, and every one of them surfaces months later as a complaint the equipment gets blamed for.
Two specification lines deserve more attention than they usually get. The cell: a declared cell part number with a declared duty cycle is the only honest form of a battery claim, because 5 years on paper means nothing in a stair core that reaches 25 degrees with 91 per cent relative humidity. And the identification number: without it a fault cannot be named, and an unnamed fault is what turns a five-minute visit into an afternoon.
Overseas buyers are handed a folder of PDFs and asked to be satisfied. The folder is worth reading properly, because three checks separate a real file from a decorative one, and none of them require a laboratory.
| Document | What to check | What a weak answer looks like |
|---|---|---|
| Declaration of conformity | Named standard, model number matching the carton, issuer named | A generic declaration with no model, or a model that is not the one shipped |
| Test report | Named laboratory, report number, date, model on the report | A report for a family name rather than for the model quoted |
| Model coverage | Which variants the report actually covers | Assumed coverage across a range that was never tested together |
| Radio declaration | Band, power, duty cycle as shipped | A band stated without power or duty cycle |
| Battery documentation | Cell part number, transport classification | A nominal year figure with no cell identified |
| Conformity files for the destination | CE and UKCA marking, RoHS, REACH, FCC as applicable | Markings shown without the files behind them |
Common references in this equipment class: smoke alarm devices against EN 14604, carbon monoxide alarm devices against EN 50291, and EN 54 series references where a component is supplied into a system context. Which of these apply to a given device is a question for the buyer's own market and the project's consultant - the discipline we hold to is that the declaration names the model on the carton and the test report exists behind it.
On documentation, a European distributor building a Hong Kong line: "We did not need another factory," the purchasing manager said. "We needed one that already knew what a Hong Kong handover file looks like, so our engineers could spend their time on the survey."
One practical habit saves a great deal of time: ask for the declaration pack with the quotation rather than after the shipment. A supplier who can produce it at quoting stage has it; a supplier who promises it later is often discovering, at the same moment as the buyer, whether it exists.
The path from a search query to a first container is more orderly than it looks from outside, and the buyers who move fastest are the ones who do the steps in this order rather than in parallel.
| Stage | What the buyer actually does | What decides whether it moves forward | Typical duration |
|---|---|---|---|
| Search and shortlist | Compares manufacturers, checks whether the supplier can name the applicable rule rather than only the product | Whether the first reply answers the compliance question or only the price question | Days |
| Technical enquiry | Sends building type, storey count, unit count, destination market | A configuration proposal with counts and a basis for them | 1 to 3 days |
| Documentation check | Asks for declarations, test reports and radio parameters | Named model coverage, not a family name | 1 to 5 days |
| Sample kit | Orders a small kit by air, surveys one floor, mounts a handful of devices | Whether the event stream and the coverage readings match the claim | 10 to 15 days to arrival |
| Factory qualification | Audits the line, the component sourcing and the traceability | Batch records, serial list, second-source plan | One visit or one audit day |
| Trial order | One building, packed to the device schedule | Whether the cartons, the labels and the platform inventory agree | One project |
| First container or programme | Volumes, private label artwork, consolidation, trade terms | MOQ, packing, inspection before loading | Per programme |
What slows this down is almost never the price. It is the fourth column of the second row: a supplier who answers a technical enquiry with a catalogue PDF instead of a configuration for the building in front of them. Buyers tell us the fastest way a manufacturer can differentiate is to propose a count with a stated basis - 24 units, 30 detectors, 2 gateways, 12 extinguishers, and why.
Two honest cautions for buyers, both of which we give in writing. Ask any supplier - Chinese or otherwise - whether they can carry the statutory installation and certification duties in the destination market; in Hong Kong they cannot, and a company that says otherwise is either working through registered local parties or overstating its scope. And treat a factory visit as the cheapest due diligence available: the test log and the component list tell a buyer more in an hour than a month of correspondence.
Private label in this category used to mean artwork. It no longer does, and buyers should know exactly which layer of the device they are asking to change, because the answer determines whether the declaration still covers it.
| Layer | What can change | What stays the same | Effect on the documentation |
|---|---|---|---|
| Appearance and labelling | Housing colour, device label, brand mark, carton artwork | Sensing elements and radio parameters | Declaration reissued under the partner's model reference with the same test basis |
| Documentation pack | Manual, quick start guide, warranty sheet in the partner's language | Technical content and safety instructions | Translated pack, bilingual where the market needs it |
| Configuration | Zone naming, report templates, escalation contacts, thresholds where the rule allows | Alarm logic boundaries set by the rule | Site configuration record per project |
| Platform | Branding, domain, user management, white label interface | Event schema and interface behaviour | Interface documentation unchanged |
| Sensing and radio | Not available for private label change in a regulated programme | Chamber, cell, band and duty cycle as declared | Declaration and test reports stay traceable to the same line |
The last row is the one worth dwelling on. A partner can change almost everything a customer can see, and should not change anything a regulator reads. Where a market needs a different band or a different threshold regime, that is a product decision with tests behind it, not an artwork decision - and it is cheaper to say so up front than to discover it during an audit.
Underneath all of it, traceability has to survive the rebrand. A partner answering an audit three years later needs the batch, the test log and the component list for the devices already on the wall, not for the devices currently on the line. We hold the production record rather than only the shipment record for exactly that reason.
Equipment for a Hong Kong programme is read by three audiences who do not overlap: the registered contractor who signs the certificate, the committee who files the documents, and the residents who read the card next to the detector. A pack that serves only the first of those fails the other two.
| Item | What it has to contain | Who reads it |
|---|---|---|
| Device label | Identification number, model, bilingual operation note | Residents, contractor, inspector |
| Quick start card | What to do when it sounds, in Traditional Chinese and English | Residents |
| Operation instruction | Position, testing, what not to do, bilingual | Committee and contractor |
| User manual and warranty | Operation, term, replaceable items | Committee and maintenance contractor |
| Carton label | Model, quantity, identification range, packing list reference | Freight forwarder, contractor |
| Packing list | Matches the device schedule for the building | Contractor, subsidy file |
Numbering is the part that pays for itself. Cartons packed to the device schedule, labels matching the platform inventory, and an identification range on each carton mean the installation team can walk the building in order instead of sorting. The drive from Shenzhen to Kwai Tsing is a few hours; what decides the delivery date is whether the paperwork and the cartons agree.
For private label partners the pack is rebuilt under their own brand - artwork, manuals, quick start guides and carton printing - with the underlying test reports traceable to the same production line. That is what lets a partner answer an audit without opening a negotiation with their own supplier.
Buyers ask for a unit price first, and it is the least useful number on the page. What moves the price on this equipment is the configuration, the documentation and the volume, and a quotation that separates those is the only one a buyer can compare.
| What moves the number | Direction | Why |
|---|---|---|
| Detector and gateway count | Direct | 30 devices and 2 gateways on this block, derived from the survey |
| Battery specification | Direct | A declared cell with a longer service life costs more than a generic one |
| Radio configuration | Direct | Band, uplink module and dual SIM arrangement for the destination market |
| Documentation scope | Direct | Declaration pack, test reports and translated manuals are deliverables, not favours |
| Private label and packaging | Set-up plus unit | Artwork, tooling for housing colour, carton printing |
| Order volume | Inverse | One building prices differently from a programme of blocks |
| Trade terms | Structural | FOB, CIF and EXW move who carries freight, insurance and risk |
What we will not do is quote a number detached from a configuration. A price for 30 detectors on a 6-storey walk-up in Central is not the same product as a price for a hundred units into a distributor's warehouse, and buyers are better served by a band with the assumptions written next to it than by a figure that survives contact with the survey for a week.
Terms are ordinary and stated up front: factory-direct pricing, private label and OEM from low volumes, sample kits by air inside ten to fifteen days, FOB, CIF and EXW terms, mixed containers consolidated at the Shenzhen factory, and a distributor or agent programme with territory discussion for partners who commit to annual volume.
Committees vote on one number; buyers need the breakdown. A single headline figure hides the two things that actually change between projects - how much of the spend is hardware and how much is access, commissioning and documents. On the Graham Street block, at the HK$184,000 the survey produced, the split looks like this.
| Line | Share | Amount | What moves it |
|---|---|---|---|
| Devices | About 46 per cent | HK$84,640 | Detector count, gateway count, spares held |
| Platform | About 17 per cent | HK$31,280 | Sites, users, interface and reporting requirements |
| Installation and commissioning | About 27 per cent | HK$49,680 | Access, floors, out-of-hours work, antenna runs |
| Documentation and testing | About 10 per cent | HK$18,400 | Declarations, commissioning records, survey report |
| Total, this block | 100 per cent | HK$184,000 | About 14 working days |
Two comparisons put that number in context. Against the traditional route on the same block - about HK$660,000 and twelve to twenty-four months - the difference is roughly HK$476,000 and most of two years of programme. Against the subsidy, the Fire Safety Improvement Works Subsidy Scheme covers this class of work at up to 60 per cent of eligible works and consultancy fees, or the cap for that class of building, whichever is lower: about HK$110,000 here, leaving roughly HK$74,000 for the owners, before any cap is applied.
The line overseas buyers underprice is installation and commissioning, because it is mostly access. 24 units across 6 floors, some tenanted, some locked, some owned by people who have not been to the building in years. We plan one floor per day and we do not start drilling before the consent sheet is complete.
Every failure below has the same shape: somebody assumed a line instead of measuring it, and the assumption surfaced after the drilling started. None of them are exotic, and all of them are cheaper to prevent at survey stage than to fix at commissioning.
| Failure mode | Where it comes from | What prevents it |
|---|---|---|
| Coverage assumed from a floor plan | A gateway count taken off a drawing rather than off a reading | A survey with readings at every candidate position, signed before the quote |
| Consent that is nearly complete | Tenanted units and absentee owners discovered during installation | Door-to-door consent closed before any plate is fixed; one floor per day afterwards |
| No lawful mains supply for the gateway | The only common-area circuit is switched, or has no spare way | A power note on the survey document, and a written answer before day one |
| A model substituted mid-project | A near-equivalent offered when stock runs short | Device schedule locking model and label, cartons packed to that schedule |
| A platform that cannot export | Discovered when the committee asks for the record | Export written into the contract: event history, fault log, inventory |
On site, a registered contractor's site foreman: "Access is the schedule," he said. "One floor a day, and not a single plate fixed before the consent sheet is complete."
The fifth one deserves a note because it is the only failure that does not show up in the first year. A system can commission cleanly, run quietly and still be a commercial trap if the building cannot take its own record elsewhere. We write the export into the order rather than into the brochure, and we generate the device schedule from the platform after commissioning so the numbers in the file are the numbers in the system.
On the Graham Street block, the two that would have bitten us were access and power: two of the 24 units were let to tenants who were not on the owners' list, and the only lighting circuit in the common area is switched at the meter rather than at the fitting. Both were caught on the survey morning, which is the only reason the programme is still 14 working days.
Sourcing detection equipment from China is not a leap of faith, it is an audit. The buyers who do this well ask the same nine questions in the same order, and they ask them before the first container rather than after the first failure.
| Question | Why it matters | What a real answer looks like |
|---|---|---|
| Which standards does the device hold, and who issued the report? | A declaration without a test report is paper | Named standard, named laboratory, report number, model on the report matching the model quoted |
| What is the battery, and how is the claim measured? | Nominal years mean nothing in a humid stair core | Cell part number, duty cycle, and a platform that reports measured state |
| Can the platform export its own data? | Lock-in is a commercial risk, not a technical one | Event history, fault log with durations, inventory with health states, in an open format |
| What is the radio, exactly? | Spectrum is regulated market by market | Band, power, duty cycle, and a written note that the licence decision is the buyer's adviser's |
| How are devices traced? | A recall without serial numbers is a guess | Serial numbers tied to batch test records and to the packing list |
| What is the second source plan? | Single-source components stop lines | Alternative approved for critical parts, lead time stated |
| What does the sample kit contain, and how fast does it fly? | One floor of data beats ten emails | Kit by air in ten to fifteen days, platform access included |
| How is the shipment packed? | Commissioning runs off the device schedule | Cartons packed to the schedule, labels matching the platform inventory |
| What happens three years from now? | Replacement parts decide whether the log stays clean | Spare holding, same model, same label, stated warranty term |
We publish answers to all nine in writing because it shortens the process for both sides. The two that buyers tell us matter most are the second and the third: a battery claim the platform can prove, and data the buyer can take elsewhere.
One caution worth repeating. No equipment supplier can carry the statutory installation, transmission or certification duties in Hong Kong. A factory that offers to "handle everything" is either working through registered local parties - in which case name them - or is telling a buyer what they want to hear. Ask which it is.
There is a serious case for the incumbent international lines, and a buyer who ignores it is not being served. They bring long certification histories, deep installed bases and local engineering support. There is also a serious case for a Chinese source factory, and it is not only price.
| Dimension | Incumbent international brands | Chinese source factory |
|---|---|---|
| Unit price | Highest, with channel margins stacked on top | Factory-direct, typically a fraction of the branded figure |
| Certification history | Longest, widest, best documented | Smoke and carbon monoxide declarations with conformity files; verify per model |
| Lead time and change | Catalogue product, slow to change | Private label, custom housing, custom labelling, faster to adapt |
| Retrofit fit | Designed for new-build wired systems | Battery and wireless designs built for occupied old buildings |
| Platform lock-in | Often closed, proprietary | Open interface and exportable event history should be a purchase condition |
| Spare parts and continuity | Strong local stock | Depends on the factory holding spares against the project; ask |
| Best fit | Large new-build projects with wired infrastructure | Old building retrofit, occupied sites, private label programmes |
Our own answer is unromantic. On a 6-storey walk-up on Graham Street with no riser, no roof space and residents who will not move out, a wired catalogue system designed for a new office tower is the wrong tool at any price. On a large new-build with a wired infrastructure budget and a consultant specifying by brand, our equipment is not the obvious first choice, and we would rather say so than lose a partner's second order.
Where we think the comparison is genuinely close, and where buyers should press hardest, is documentation and data. Ask any supplier - imported or Chinese - for the test report behind the declaration, the export format of the event log, and the serial traceability of a batch. The answers separate suppliers far more reliably than the logo does.
Nobody should price a Central block from a floor plan. The survey produces eight things, and each of them changes either the quantity or the risk.
| Survey item | What is measured | What it decides |
|---|---|---|
| Signal strength and coverage | Path from every unit and landing to each candidate gateway position | Gateway count and antenna work |
| Channel plan | Occupancy and noise floor around the stair core | Which channels the equipment is configured on |
| Transmission design | Operator coverage at the stair core, dual SIM plan | SIM operators and failover behaviour |
| Physical constraints and power | Mains availability in common areas, mounting surfaces, soffit condition | Mains routes and fixing method |
| Unit access | Occupancy, tenancy, locked units, absentee owners | Installation schedule, one floor per day |
| Fire load and false alarm sources | Kitchens on landings, incense, workshop dust, corridor windows | Detector siting and pre-alarm thresholds |
| Extinguisher positions | Bracket height, approach route, visibility | 12 units, two per floor, 5 kg powder type |
| Evacuation route | Staircase width, storage on the landing, door swing | Sounder placement and audibility |
On Graham Street the survey took one morning with two people and a handheld receiver. The finding that mattered was not radio: it was that two of the 24 units were let to tenants who were not on the owners' list, which moved the installation start by a week while consent was collected.
The survey also settles the question that comes up on every quotation: whether the gateway can be powered legally. A detector is a battery device and needs nothing from the building. A gateway needs mains, and in older blocks the only supply in the common area is often a lighting circuit that is switched off at night or has no spare way. Finding that out on day one costs a morning; finding it out on installation day costs a week.
We issue the survey as a document, not as a conversation: candidate gateway positions with readings, a marked-up floor plan, the device schedule, the power note and the access constraints. That document is what the contractor prices from and what the committee files.
Composite building with a podium buildings punish radio. A reinforced concrete floor slab takes a real bite out of a sub-GHz link, a metal security gate at the entrance takes another, and a rooftop water tank throws a shadow exactly where a gateway would otherwise go. On the Graham Street block the worst reading we logged was -107 dBm, taken from the top-floor landing to a ground-floor gateway position - workable, but with no margin left for a humid summer and a corridor full of stored goods.
The answer is redundancy rather than power. A second gateway on the stair core means one unit can fail without the building going dark, and a short external antenna run costs less than call-backs. Our WANLIN-222 family supports dual-gateway registration, so a detector that loses its primary path is re-homed automatically and the event is logged as a fault rather than silently absorbed.
Environment matters as much as structure. This block runs at about 25 degrees on the landing in summer with relative humidity around 91 per cent. Condensation and steam are false alarm sources, not detector failures, and they are handled by siting and by the two-level logic rather than by desensitising the chamber.
There is a third factor specific to Hong Kong that visiting engineers miss: the buildings change. A partition goes up, a mezzanine gets inserted, a shop unit changes hands and fills with stock, and the radio path that was fine at commissioning is no longer fine a year later. That is why the coverage survey is a document with readings rather than a verbal clearance, and why we recommend repeating it whenever a block changes use.
The service provider produces a monthly performance report for a fitted building, and it is the only document that tells a committee whether the equipment is still doing its job three years later. Buyers should ask to see a sample report before ordering, because the difference between a real one and a marketing one is visible in ten seconds.
| Line | What a healthy month shows | What a bad month looks like |
|---|---|---|
| System online rate | 100 per cent, or a named exception with a duration | A percentage with no denominator and no exception list |
| Component availability | Above 99.95 per cent, measured against the device inventory | A rounded figure with no device count behind it |
| Fault count and duration | Each fault named, opened and closed with dates | Faults summarised as a total with no closure dates |
| False alarm count | Zero, or each one attributed to a cause and a siting change | A number with no attribution, or no line at all |
| Missed heartbeats | None outstanding at month end | Devices listed as offline for longer than the repair clock |
| Battery and health states | Declared state per device, with replacements logged | A single average, which hides the worst device on the worst landing |
On reporting, an overseas buyer's quality manager: "I do not audit the showroom," she said. "I audit the test log, the serial list and the component source. A factory that can produce those three in an hour is a factory I can order from."
The line that gets argued about is the last one. Averaging battery state across 30 devices tells a committee nothing about the one device that matters, which is the one about to fail on the top floor in the wet season. We report per device and let the contractor sort the list, because the repair clock runs per device, not per average.
One more practical point for overseas partners: the report is also the marketing asset. A distributor who can hand a prospective client twelve months of clean monthly reports from an occupied block is selling evidence, and in this market evidence closes faster than a price list.
Zero false alarms over the pilot quarter is the result that made this policy possible, and it is worth being clear about how it was achieved: not by making detectors less sensitive, but by giving the device two sensing elements, two alarm levels and a siting plan that respects how people actually cook, burn incense and store things on a landing.
In a Central and Western walk-up the false alarm candidates are predictable. Cooking aerosol in a unit with the door open. Incense at a shrine on the landing. Steam from an open corridor window during the wet season. Workshop dust in an industrial unit. Each has a signature: smoke without a carbon monoxide rise, or a short spike that decays. The device absorbs them at the pre-alarm level and logs them, so the pattern can be reviewed instead of argued about.
The operational discipline matters as much as the electronics. Silent test mode lets a contractor prove the system without emptying the building; day and night modes let a hotel or a school keep a sane acoustic environment; and the drill record belongs in the committee's minutes, not only in the platform.
Seasonality is the part overseas buyers never ask about and Hong Kong contractors always do. Typhoon season brings open windows, wet corridors and condensation on cold surfaces; the wet months push landing humidity to 91 per cent and above. None of that causes a fire, but all of it causes complaints if the siting ignores it, and complaints are what get a system switched off - which is the only outcome worse than a false alarm.
One more honest note. No detection equipment removes the need for housekeeping. Storage on a landing blocks an evacuation route and it also blocks a sounder; a corridor window left open onto a light well brings steam into the detection zone. The device can absorb the aerosol, but the committee still owns the landing.
Power design in this equipment is deliberately boring. Detectors run on battery with a service life of three years or more - 5 years on the cells specified for this configuration - and report their own state on the heartbeat. Gateways run on the building's mains supply with a backup battery behind them, because the gateway is the one component that cannot go quiet.
The rule that concentrates minds is the 30-day one: the registered contractor has to complete a repair within 30 days or report the matter to the department. That makes fault reporting a commercial issue rather than a technical curiosity. A platform that surfaces a low battery, a removed detector or an offline gateway on the day it happens is the difference between a routine visit and a reported breach.
| Element | Power | Reporting | Failure behaviour |
|---|---|---|---|
| Multi-sensor detector | Battery, 5 year service life | Heartbeat at 24 hours or less, battery state and drift | Fault raised, device identified by floor and number |
| Gateway | Building mains plus backup battery | Heartbeat at 30 minutes or less, mains-loss fault | Dual SIM failover, backup battery carries the uplink |
| Alarm sounder | Fed from the gateway arrangement | Status and fault on the same channel | Fault raised within 20 seconds |
| Extinguishers | Not applicable | Visual inspection at each visit | Replacement at the next scheduled visit |
The practical failure mode is not a dead cell, it is an undocumented one. A detector that quietly drops out of the network and is not noticed until the annual inspection has left a floor unprotected for months, and under the reporting regime that is a reportable fault rather than a maintenance note. Hence the insistence on heartbeat reporting that names the device, and on a contractor who actually watches the platform rather than logging in once a quarter.
We also specify the cells rather than quoting a number. A three-year life on paper means nothing if the device sits in a humid stair core with a corridor window open; the honest answer is a declared cell, a declared duty cycle, and a platform that reports the measured state so the claim can be checked against the building.
The question that separates a supplier from a vendor is asked about three years after handover: when a detector fails on the fourth-floor landing, what arrives, how fast, and does it change the commissioning record? On the Graham Street block the honest answer has to be written down before the first carton ships, because 30 devices on one platform inventory is a small population and a single substituted model contaminates the file.
| Item | Held where | Typical arrangement | What to write into the contract |
|---|---|---|---|
| Multi-sensor detector | With the maintenance contractor on site | 5 units held against this building | Same model, same label, replacement logged to the same serial list |
| Gateway | With the contractor or the service provider | One spare per programme, not per building | Configuration restored from the site record, not re-engineered |
| Battery cells where replaceable | With the contractor | Declared cell part number, not a generic equivalent | Cell type named so the duty cycle claim still holds |
| Mounting plates and fixings | With the contractor | Consumables held as a kit | Replacement does not change the mounting position |
| Extinguishers | On the bracket, per floor | 12 units, inspected at each visit | Replacement at the next scheduled visit, recorded |
| Platform access and export | With the building | Event history and inventory retained for the contract term | Retention period, and a full export on termination |
Warranty terms in this category are ordinary and worth stating plainly rather than dressing up: a stated term against manufacturing defect, a stated response for a fault report, and a stated commitment that the model supplied at commissioning is the model supplied at replacement. Anything more creative than that is usually a way of avoiding one of the three.
For a private label partner the same logic applies under their own brand, which is why we hold the production record rather than only the shipment record. A partner answering an audit three years later needs the batch, the test log and the component list for the devices already on the wall - not for the devices currently on the line.
Two test gates decide whether a Central installation is signed off or argued about. Factory acceptance happens before anything ships; site acceptance happens after it is installed. Both produce records, and both are cheap compared with discovering the problem later.
| Gate | Check | What passes |
|---|---|---|
| Factory | Chamber response on both sensing elements | Response inside the declared band on every unit in the batch |
| Factory | Battery voltage under load | Cell batch within specification, voltage logged by serial number |
| Factory | Wireless join and rejoin | Device joins, loses, and re-homes without manual intervention |
| Factory | Tamper and burn-in run | Tamper raises a fault; burn-in completes without early failure |
| Site | Coverage readings at every device | Every device meets the margin recorded in the survey |
| Site | Event class timing | FIRE, PRE-ALARM, FAULT and STATUS inside the published limits |
| Site | Uplink failover | Second SIM takes over, event logged, platform notified |
| Site | Fault injection | Removed device and mains loss raise named faults inside 20 seconds |
| Site | Audibility per landing | Measured level with doors shut and windows as the building uses them |
| Site | Silent functional test then audible drill | Full function proven quietly, then an evacuation timed door to door |
The step that gets skipped under pressure is fault injection, and it is the one that proves the maintenance model. Removing a device and watching the platform raise a named fault inside twenty seconds tells the contractor whether the 30-day repair clock is workable in this building before it has to be. A system commissioned without that test is a system whose first fault will be its first surprise.
Handover is not the end of the job. The monthly performance report starts the following month, and the first quarter is when siting mistakes surface - a detector too close to a kitchen door, a corridor window onto a light well, a landing that accumulates storage. Our practice is to review the first quarter's event log with the contractor and adjust siting while the team is still on site.
The sequence below is what a 6-storey block on Graham Street actually looks like from the first visit to the drill. It is included because buyers price the wrong thing when they price only the hardware: the schedule is mostly access, testing and documentation.
| Stage | What happens | What it produces |
|---|---|---|
| Survey | Readings at candidate gateway positions, unit count, power check | Survey document and device schedule |
| Consent and access | Owners and tenants sign, floor-by-floor schedule agreed | Signed consent sheet |
| Delivery check | Cartons opened, serial numbers counted against the schedule | Receiving record |
| Fixing | Plates and brackets fixed, no devices mounted yet | Photographic record per level |
| Mounting and numbering | Devices mounted, labelled and registered to floor and position | Device inventory in the platform |
| Gateway and uplink | Mains supply, backup battery, both SIMs commissioned | Failover test record |
| Platform configuration | Zones by floor, thresholds, escalation contacts, report cadence | Site configuration record |
| Silent test | Full functional test with no audible output | Test log with timestamps |
| Fault injection | Device removed, mains removed, battery low simulated | Fault class and timing verification |
| Extinguisher round | 12 units bracketed, heights measured, plates fixed | Photographic record per level |
| Audible drill and handover | Evacuation timed, records filed, certificate issued by the RFSIC | Drill record and certificate |
Two administrative details decide whether the last stage is a formality or a delay. The device schedule has to match the platform inventory, because the certificate file and any subsidy claim both read from it. And the drill has to be recorded in the committee's own minutes, because that is the document the next contractor and the next committee will look for.
A fitted building generates four records, and the question of who can produce each one is a contract question rather than a technical one. It comes up twice: when a committee changes service provider, and when an insurer or a successor contractor asks for the history of a building they have never seen.
| Record | Who keeps it | What a buyer should require |
|---|---|---|
| Event history, fire and pre-alarm | Platform, mirrored to the department's server | Exportable with timestamps, per device, in an open format |
| Fault log with durations | Platform, surfaced to the contractor | Open and close dates, so the repair clock is provable |
| Device inventory with health and battery state | Platform, generated from commissioning | Matches the device schedule and the packing list |
| Survey, commissioning and drill records | Contractor, committee and subsidy file | Documents rather than emails, filed with the minutes |
Two clauses do most of the work. The first is a retention period written into the contract, so a committee knows how far back it can ask. The second is a termination clause that obliges the platform to hand over a complete export rather than a summary - without it, a building that changes provider loses its own history, and the new contractor starts blind on a system that has been running for years.
There is a commercial angle for overseas partners here as well. A distributor who can offer an exportable, well-structured record is offering something several incumbent platforms in this category do not, and it is the single cheapest differentiator available in a market where the hardware itself is increasingly comparable.
The reason one-stop supply wins here is organisational, not technical. A six-storey block in Central has nobody whose job is to integrate four vendors. The committee wants one contractor, one schedule and one phone number. That is why we supply the devices, the platform and the documentation as a single package, and why the partner programmes are built around who carries what.
The partner is a regional sourcing office qualifying a Chinese plant against its own audit: traceability, component sourcing, test records and a second-source plan before any volume is discussed. The commercial shape of that relationship: OEM and ODM programmes, traceability records, second-source planning.
Partner note - an overseas manufacturer's sourcing office: "We audit the line, not the brochure," the quality manager said. "Show me the test log and the component list and we can talk about volume."
| Cooperation model | How it works | What we supply |
|---|---|---|
| Distributor and importer | Hold stock in your own market, sell under our brand or yours, and open a territory discussion once annual volume is committed. | MOQ from a mixed starter order, sample kit by air, marketing files and training material |
| Private label and OEM | Your brand on the detector and the gateway, your artwork on the carton, your language on the quick start guide, your thresholds in the firmware where the rule allows it. | Private label from low volumes, custom housing colour, custom label and packaging artwork |
| Contractor and integrator supply | Equipment and platform supplied to your project, with the statutory installation and maintenance work staying with your own registered team. | Project pricing, commissioning records, interface and event history access, spare parts holding |
| Platform and technology partner | Take the devices onto your own platform through the interface, or run ours underneath yours. | Interface documentation, event schema, device health feed, joint support model |
| Trading company and sourcing office | Mixed containers consolidated at the factory, one document set, inspection before loading. | Mixed SKU consolidation, third-party inspection, FOB, CIF and EXW terms |
| Agent with territory commitment | Represent the line in a defined territory, bring the projects, and hold the commercial relationship with the end client. | Territory discussion, lead protection, joint quotation support, factory visit programme |
Terms are ordinary and stated up front: factory-direct pricing, private label and OEM from low volumes, sample kits by air inside ten to fifteen days so a partner can survey and test one floor before committing, FOB, CIF and EXW terms, mixed containers consolidated at the Shenzhen factory, and a distributor or agent programme with territory discussion for partners who commit to annual volume. Consignments for Hong Kong programmes cross from Shenzhen through Yantian or Shekou into Kwai Tsing, and onward export runs on the same consolidated schedule.
What we ask a new partner for is small: one building, one survey, one floor installed, one month of platform data. That is enough to prove the coverage, the timing and the reporting in the partner's own market, and it is a cheaper argument than any document we could send.
With immediate effect from 30 April 2026, FSD Circular Letter No. 3/2026 accepts an Internet of Things Fire Detection System together with portable fire extinguishers as an alternative solution to the statutory requirements for hose reel and manual fire alarm systems in composite and domestic target buildings of six storeys or below regulated under the Fire Safety (Buildings) Ordinance, Cap. 572. For the avoidance of doubt, all other applicable requirements under the Ordinance remain unchanged.
The multi-sensor detectors and the gateways are fire service installation and equipment components: they are installed, maintained, inspected and repaired by a registered fire service installation contractor, which issues the certificate. The monitoring platform and the mobile application are not fire service installations; they sit with the IoT FDS service provider. The extinguishers are portable equipment provided for occupants to operate.
Sufficient multi-sensor detectors near the entrance inside each unit and in the common areas on each floor; sufficient gateways in common areas, incorporating manual call points, alarm sounders and signal transmission facilities with dual SIM cards covering different external communication networks; and at least two 5 kg powder-type portable fire extinguishers on each floor. The exact counts come out of a survey, not a package.
Fire and pre-alarm signals have to appear on the platform within 10 seconds from mains-powered equipment and within 20 seconds from battery-powered equipment. Fault signals have to arrive within 20 seconds regardless of power source and status signals within 100 seconds. Heartbeat checks run at 30 minutes or less for mains equipment and 24 hours or less for battery equipment.
Smoke alone cannot separate a smouldering mattress from a wok left on a burner, and carbon monoxide alone is slow on a fast flaming fire. Read together, with two alarm levels, the two channels separate the cases: a smouldering fire gives rising carbon monoxide with little smoke, while cooking aerosol gives smoke without the matching carbon monoxide rise. That is what makes a pre-alarm level useful instead of noisy.
Ask per device and per model. Smoke alarm devices are commonly declared against EN 14604, carbon monoxide alarm devices against EN 50291, and system components may carry EN 54 series references where they are supplied into a system context. Conformity files such as CE and UKCA marking, RoHS, REACH and FCC apply by destination market. What matters is that the declaration names the model on the carton and that a test report from a named laboratory exists behind it.
Yes, for the device and platform layer, and that is how most private label programmes in this category run. What a factory cannot carry is the statutory installation, maintenance, transmission or certification duty in Hong Kong, which rests with the Hong Kong registered parties. A supplier that offers to handle everything is either working through registered local parties - in which case name them - or overstating its scope.
A sample kit by air inside ten to fifteen days, enough detectors and one or two gateways to survey one floor and mount a handful of devices, with platform access to watch the event stream for a month. After that, MOQ and packing are discussed against the device schedule for the building, and consolidation into mixed containers is available where the order allows.
Housing colour, the label on the device, the artwork on the carton, the manual and quick start guide in the partner's language, and configurable items such as zone naming, thresholds where the rule permits, and report templates. What does not change is the sensing element, the radio parameters as declared for the market, and the traceability of the batch to the same production line and test records.
Every device carries an identification number and a label, and the platform names devices by floor and position. Serial numbers are tied to batch test records and to the packing list, so a fault reads as "third floor landing" rather than as a device number nobody can locate. That traceability is also what lets a replacement three years later be the same model with the same label.
In practice yes for Hong Kong programmes: device labels, the operation instruction and the quick start card in Traditional Chinese and English, alongside the user manual and warranty sheet. A pack in a single language excludes residents who need to read the card next to the detector, and it is the first thing an inspection notices.
The registered contractor has to complete a repair within 30 days or report the matter to the department, so fault reporting is a commercial issue rather than a technical curiosity. Practically, that means spares held against the building, the same model supplied at replacement, and a platform that raises a named fault the day it happens rather than at the annual inspection.
The log should belong to the building, not to the supplier. Write three things into the contract before installation: the event history, the fault log with durations and the device inventory are exportable in an open format; the retention period and who may request a copy are stated; and on termination the platform hands over a complete export rather than a summary. A committee that cannot take its own record to a successor contractor has bought a subscription, not a system.
With one building. We ship a sample kit by air inside ten to fifteen days - enough detectors, one or two gateways and platform access to survey one floor, mount a handful of devices and watch the event stream for a month. Then we talk about MOQ, private label artwork, packing to the device schedule and consolidation into mixed containers.
Our read from the enquiries reaching the factory is consistent: the partners who win this work are the ones who can prove equipment rather than describe it - coverage readings, event timing, a declaration pack that matches the model on the carton, and an exportable log. That is what we build for.
Further reference for buyers checking the policy and the technical background: National Fire Protection Association, together with the Fire Services Department circular itself.
Wanlin - Internet of Things fire alarm equipment manufacturer and export supplier, Shenzhen, China, for Hong Kong programmes. Wanlin Manufacturing Group builds multi-sensor smoke and carbon monoxide detectors with two-level pre-alarm and fire logic, gateways carrying manual call points, alarm sounders and dual SIM transmission on different networks, and the monitoring platform with interface, event history, device health reporting and the frontline application - supplied factory-direct to registered contractors, service providers, platform companies, integrators, distributors and trading companies. Portable 5 kg powder-type extinguishers are supplied to the count the rule requires, two per floor. OEM, ODM and private label, bilingual Traditional Chinese and English labelling, declaration and test report documentation with CE, RoHS, REACH, FCC and UKCA files. Statutory installation, transmission and certification responsibilities in Hong Kong rest with the Hong Kong registered parties; we supply the device and platform layer behind them.