This webinar focuses on two important components that support the operation of fire and smoke control systems: fire and smoke curtains and standby generators.
Participants will gain an understanding of the purpose and operation of fire and smoke curtains, their role in smoke containment and occupant safety, and the key inspection, testing and servicing activities required to maintain compliance and reliability.
The session will also examine standby generators and their role in providing emergency power to essential fire safety systems. Technicians will learn how standby generators interact with fire protection systems and the importance of verifying their operation during routine testing activities.
A key focus will be System Interface Testing (SIT), including how these systems work together during emergency conditions and the responsibilities of maintenance personnel in supporting ongoing system performance and compliance.
Ideal for fire protection technicians, maintenance personnel, facility managers and building operators, this webinar will provide practical knowledge to assist with the inspection, testing and servicing of fire and smoke control systems.
Fire & smoke curtains
Purpose & design requirements
The standby generator
The role it plays in the SIT (System Interface Test)
Register now and secure your spot!
Event details
| Date: |
Thursday, 13 August 2026 |
Time:
|
3.00pm - 5.00pm (AEST) |
| Location: |
Online, BigMarker |
Cost:
|
.jpg)
Non members - $100 per webinar or $600 for full 7 part series
|
| CPD: |
2 CPD hours |
| RSVP: |
Thursday 13, August at 12.30pm |
Tech Talks: Mechanical Services Series
Part 1: An introduction to Fire & Smoke Control and Mechanical Services
Part 2: Fire, Smoke and Combination Dampers & Sub-Ducts
Part 2.1: Fire & Smoke Curtains and Standby Generators in System Interface Testing continued (part 2)
Part 3: No two buildings are the same
Part 4: Your role & responsibilities onsite
Part 5: Pre-testing, Commissioning & Documentation requirements
Part 6: Routine servicing & system interface testing requirements
Part 7: Case studies & lessons learned