Guide CN→AU R14 Fire Alarm Zone Map
Verdict for procurement and compliance leads: A fire-alarm zone map shipped China→Australia can be held current in 21 calendar days through a controlled 12-step maintenance cycle with a single named owner per step, one default annual revision, and explicit change-control for OEM drawing updates. The decision is go for any B2B partner that already holds an approved file and can nominate an Australian cert body (e.g., a CSIRO-ActivFire or SAI Global-listed laboratory) before the first review. Evidence date: 2026-09-22. Limitation: cost figures are not published on this page; only HS classification and duty verification blocks are sourced (see HS/Duty Block).
| Decision field | Value | Source row |
|---|---|---|
| Equipment scope | Notifier NIS-3001 fire-alarm control panel family (Notifier by Honeywell, China OEM) with attached addressable smoke/heat detectors and notification appliances | Notifier by Honeywell — Control Panels (AU product page) |
| Trade lane / location | China → Australia (CN→AU), importer-of-record lodged in AU | Australian Border Force (home) |
| Maintenance horizon | 21 calendar days per cycle, default 1-year revision, shorter on OEM drawing change | Timeline table, FAQ #3 |
| Standard framework | AS 1670.1:2018 (Fire detection, warning, control and intercom systems — System design, installation and commissioning, Part 1: General requirements) | Standards Australia publications portal |
| Cert body status | Cert body nomination pending per shipment (no generic placeholder) | FAQ #5 |
The table below defines the controlled maintenance process. Each step has a single named owner and a literal input/output document reference so it can be computed inside a quality-management system. The 12-step sequence is the canonical cycle used by TradVolt B2B partners; it is not an external regulatory requirement but a controlled workflow that maps to AS 1670.1:2018 documentation expectations.
| Step # | Action | Owner | Input doc | Output doc | Done-when |
|---|---|---|---|---|---|
| 1 | Receive the OEM master fire-alarm zone-map drawing for the Notifier NIS-3001 family from the Chinese manufacturer and confirm drawing revision letter. | Procurement Officer | R14_OEM_zone-map_master_RXXX.pdf | R14_zone-map_intake_log.xlsx | Intake log entry dated and saved. |
| 2 | Request bilingual zone-map cover sheet (CN/EN) for Australian reviewers. | Trade Documentation Clerk | R14_OEM_zone-map_master_RXXX.pdf | R14_zone-map_cover_CN-EN_v01.docx | Bilingual cover sheet signed by both parties. |
| 3 | Map device list and circuit IDs against AS 1670.1:2018 sub-clauses (zone definition, detector siting, notification appliance layout). | Compliance Engineer | R14_zone-map_cover_CN-EN_v01.docx | R14_AS1670_crosswalk.xlsx | Crosswalk sheet complete with no open gaps against AS 1670.1:2018 sub-clauses. |
| 4 | Submit documentation package to the nominated Australian certification body for review (cert body nominated per shipment — see FAQ #5). | Compliance Engineer | R14_AS1670_crosswalk.xlsx | R14_certbody_submission_cover_letter.pdf | Submission acknowledgement received in writing from the named cert body. |
| 5 | Track and resolve cert-body observations; re-submit revised artifacts as needed. | Compliance Engineer | R14_certbody_observations_log.xlsx | R14_certbody_resubmission_v##.zip | All observations closed in writing. |
| 6 | Receive cert-body approval (cert letter with cert body name + cert reference number) and update the controlled document register. | Compliance Engineer | R14_certbody_resubmission_v##.zip | R14_certbody_approval_letter.pdf | Approval letter stored in register; cert body name and cert number recorded. |
| 7 | Generate importer-of-record declaration pack referencing approved drawings. | Customs Broker | R14_certbody_approval_letter.pdf | R14_IOR_declaration_pack_v01.pdf | Declaration pack filed with broker file. |
| 8 | Lodge the Australian customs entry referencing the approved zone-map documentation. | Customs Broker | R14_IOR_declaration_pack_v01.pdf | R14_customs_entry_confirmation.json | Customs entry confirms release instructions. |
| 9 | Archive maintenance file and notify the facility-management team of the current revision. | Records Officer | R14_customs_entry_confirmation.json | R14_MAINT_archive_index.xlsx | Archive entry complete and FM team notified in writing. |
| 10 | Schedule the next revision review against the maintenance calendar. | Records Officer | R14_MAINT_archive_index.xlsx | R14_revision_calendar_entry.ics | Calendar entry created and acknowledged. |
| 11 | Issue change-control note if any OEM drawing revision arrives between cycles. | Procurement Officer | R14_revision_calendar_entry.ics | R14_change_control_note_v##.pdf | Note circulated and acknowledged by Compliance Engineer. |
| 12 | Close the maintenance cycle and reset the done-when counters in the QMS. | Quality Manager | R14_change_control_note_v##.pdf | R14_cycle_close_report_v##.pdf | Cycle-close report countersigned. |
Maintain the following files inside the R14 maintenance folder. The list below uses literal filenames so each controlled document can be located without ambiguity.
The timeline below describes realistic calendar windows for a single CN→AU corridor revision cycle. All durations are expressed in calendar days and are intended for planning, not contractual commitment. The 21-day total matches the totalTime: P21D value in the page schema.
| Phase | Activity | Window (calendar days) | Owner | Predecessor |
|---|---|---|---|---|
| 0 | OEM master receipt | Day 0 – Day 1 | Procurement Officer | — |
| 1 | Bilingual cover sheet | Day 1 – Day 4 | Trade Documentation Clerk | Phase 0 |
| 2 | AS 1670.1:2018 crosswalk | Day 4 – Day 8 | Compliance Engineer | Phase 1 |
| 3 | Cert-body review | Day 8 – Day 15 | Compliance Engineer | Phase 2 |
| 4 | Observation closure | Day 15 – Day 18 | Compliance Engineer | Phase 3 |
| 5 | IOR declaration pack | Day 18 – Day 19 | Customs Broker | Phase 4 |
| 6 | Customs lodging | Day 19 – Day 20 | Customs Broker | Phase 5 |
| 7 | Archive + close | Day 20 – Day 21 | Records Officer | Phase 6 |
The default 1-year maintenance cycle is an internal TradVolt editorial default for partners that hold a stable OEM drawing; it is not an external regulatory requirement. Source: Standards Australia publications portal (no specific AS 1670 clause defines an annual maintenance interval).
Use the button below to download the R14 maintenance checklist as a PDF for internal distribution. The download event is captured via the global dataLayer for analytics.
Download R14 Checklist (PDF) Request RFQ
The zone map is the controlled documentation that identifies detection and notification zones for a fire-alarm system (e.g., a Notifier NIS-3001 panel and its detectors). It is referenced by Australian certifiers during equipment review and by the importer-of-record during customs lodging.
This guide references AS 1670.1:2018 — Fire detection, warning, control and intercom systems — System design, installation and commissioning, Part 1: General requirements. Partners should confirm the exact sub-clause with their nominated cert body. Source: Standards Australia publications portal.
The maintenance calendar is set at cycle close. The default cycle is one year (TradVolt editorial default), but partners may schedule shorter cycles when OEM drawing revisions arrive between cycles.
The cert-body approval is not issued and the customs declaration cannot reference an approval letter. The maintenance cycle is paused at Step 5 until observations are closed in writing.
No. Steps 4 to 6 of the process table require a nominated Australian cert body. Cert body nomination is pending per shipment; typical Australian cert bodies for fire-alarm equipment include CSIRO-ActivFire (ActivFire scheme) or SAI Global-listed laboratories. Without a named cert body and its cert reference number recorded on the approval letter, the maintenance file cannot be closed. Source: Australian Border Force (home) for the importer-side reference framework.
© TradVolt Editorial. Trade lane: CN→AU. Slug: /guides/cn-au-fire-alarm-zone-map-r14/. Revision: R14. Evidence date: 2026-09-22.