FIP detection zones and zone plans: getting them right for DFES DBA compliance in WA
Fire indicator panel zoning and zone plans are among the most common areas where DBA connection submissions fall short in WA. Here is what DFES requires and where contractors get caught out.
A contractor submits a DBA connection request for a completed commercial building. DFES reviews the zone plan and finds that several Manual Call Points are grouped into multi-device zones on the Fire Indicator Panel (FIP), making it impossible for attending personnel to identify which device activated. The submission goes back. The project is delayed. The fix is a panel reprogramming and a redrawn zone plan work that should have been scoped correctly from the start.
FIP zoning and zone plans are not an afterthought in the DBA connection process. They are among the first things DFES DBA reviewers look at, and they must be right before a connection is granted.
How FIP zoning works in practice
A Fire Indicator Panel the central control and indicating equipment for a building's fire detection system displays alarm events by zone. A detection zone is a defined area of the building that maps to a single zone indicator on the FIP. When a detector activates, the FIP shows which zone the event came from. That information is what DFES uses when responding to an alarm: it tells attending personnel where to go.
The DFES DBA Connection Code requires that zone plans accompany every FIP both detection zone plans and evacuation zone plans. These are the physical documents displayed at the FIP that allow anyone attending the building to cross-reference a zone indication with a location. Zone plans are a mandatory element of the DBA connection, not optional documentation.
Where Manual Call Points (MCPs) are installed, the requirements are specific. Each individual MCP shall be identified on the FIP and zone plan as an individual alarm zone for prompt and easier identification and location. Grouping MCPs into shared zones is not acceptable under DFES requirements. Each call point needs its own zone, which in turn needs its own line on the zone plan. This is one of the most consistent sources of non-compliance in DBA submissions involving older buildings or systems designed to a lower standard.
Smoke and fire door detection
The DBA Connection Code also addresses smoke and fire door detection as a distinct requirement. Smoke doors and fire doors that are held open or released by the fire detection system need to be integrated in a way that DFES can verify and monitor. The detection associated with those doors forms part of the zone structure and must appear correctly on the zone plan.
This requirement is relevant to buildings with extensive door-hold and door-release systems aged care facilities, hospitals, multi-tenancy commercial buildings with security-controlled areas, and buildings where the fire strategy relies on compartmentalisation. The integration between the detection system and the door control functions must be clear in the documentation provided to DFES, not assumed to be covered by the panel's internal logic.
What catches contractors in carparks
Carpark smoke detection is one of the most common areas where fire system designs for DBA-connected buildings fall short of DFES requirements. The DBA Connection Code addresses smoke detection in carparks as a specific topic, separate from the general detection requirements that apply to the rest of the building. Carparks present a different challenge because vehicle exhaust, dust, and the open nature of the space create false alarm risks that standard detection layouts do not account for well.
The specific requirements for carpark smoke detection must be considered at the design stage, not resolved during commissioning. A carpark that is zoned or detected in the same way as an occupied office floor is likely to either generate excessive false alarms or fail to detect a real event effectively. Either outcome creates a problem with DFES false alarms lead to review and potentially to alarm delay restrictions being imposed; inadequate detection raises compliance issues at the connection stage.
The compliance process
DFES requires the C8 form to be submitted for review prior to all works being initiated on any detection or warning system connected as a DBA. This includes modifications as well as new connections. If works are completed and the zone plan or zoning is found to be non-compliant, the submission process requires rework before the connection is granted. In the interim, the system is not connected to the DBA network, which means the building does not have monitored brigade alarm coverage.
All FIPs connected to the DBA network must comply with AS 1670.1. There are no exceptions to this unless DFES grants written approval. The zone plans, zoning structure, and detection layout must all reflect that compliance not just the panel hardware, but the way the system is configured and documented.
If you are involved in a commercial project in WA that requires DBA connection and want to make sure the FIP zoning and zone plans are set up correctly from the start, get in touch and we can work through the requirements with you.
