Smoke Control Technical Bulletin - Viking Controls

Metasys Network Technical Manual 636Smoke Control Section

Technical BulletinIssue Date 1000

© 2000 Johnson Controls, Inc. 1Code No. LIT-636330 www.johnsoncontrols.com

Introduction Page 3

• Overview 3

• References 3

• Technical Manuals 4

• Application Notes 4

Smoke Control Requirements 7

• Agency Requirements 7

• Smoke Control System Requirements per UL 864 UUKL *8

• DX-9100/9120 Applications *11

• Fire Fighter’s Smoke Control Station (FSCS) *12

Smoke Control Restrictions 13

• Smoke Control System Restrictions per UL 864 UUKL 13

• DX-9100/9120 Applications 14

• Fire Operator Workstation (Fire OWS) 14

Design Considerations 15

• Smoke Movement 15

• Smoke Control Application Examples *16

Building HVAC Systems Used in Smoke Control 21

• Central Systems 21

• Dedicated vs. Non-dedicated Smoke Control Systems 21

• Individual Floor Fan Units 22

Smoke Control

*Indicates those sections where changes have occurred since the last printing.

2 Smoke Control—Smoke Control

• Fan Coil Units/Water Source Heat Pumps Page 22

• Induction Units 22

• Variable Air Volume (VAV) Systems 22

• Smoke Dampers 22

Smoke Control Strategies 23

• Manual Initiating Devices (Pull Stations) 23

• End-to-End Verification *24

• Fan Relay Supervision 24

• Response Time 24

Applying the Metasys Network as a Smoke Control System 25

• Network Control Module (NU-NCM300/350-2/-8) 25

• N1 ARCNET Card (NU-ARC101-0) 27

• N1 ARCNET Settings 27

• DX-9120 Card (NU-NET201-0) 29

• Initiating Devices 31

• Air Moving Equipment in a Smoke Control Sequence 33

• Fire Operator Workstation (Fire OWS) 34

• Fire Fighter’s Smoke Control Station (FSCS) 34

• Visual and Audible Indicating Devices *34

• Fire Alarm Control Third-Party Panels *34

System Programming Guidelines for Smoke Control 35

• Online Generation and DDL Programming Guidelines 35

• GPL Programming Guidelines 35

UL Listed Devices for Smoke Control 37

*Indicates those sections where changes have occurred since the last printing.

Smoke Control—Smoke Control 3

Introduction

This document provides sales engineers, project engineers, applicationengineers, and system representatives with the information necessary tohelp sell, engineer, install, and commission a smoke control system thatcomplies with the Metasys® UL® (Underwriters Laboratories, Inc.)864 UUKL Smoke Control Listing. To comply with the Listing, therequirements and restrictions placed on the Metasys components used andassembled must be followed as detailed in this and other Metasysdocumentation applying to the UL 864 UUKL Listing.

The design objectives of a smoke control system are to:

• maintain a safe and smoke free environment in emergency exit routesand areas of refuge during the evacuation of a facility

• contain the smoke within the fire area and minimize its migration toother areas of the facility

• provide for conditions outside the fire area that are conducive to theperformance of emergency operations such as evacuation, fire controland rescue

• protect life and minimize property loss

When designing your smoke control system, you must read and becomefamiliar with the following documents, codes, and standards:

• NFPA 92A Recommended Practice for Smoke Control Systems• American Society of Heating, Refrigerating, and Air Conditioning

Engineers (ASHRAE) publication entitled Design of Smoke ControlSystems for Buildings

• NFPA 72 National Fire Alarm Code• NFPA 101 Life Safety Code• NFPA 90A Air Conditioning Systems• NFPA 92B Smoke Management Systems in Malls, Atria, and Large

Areas• BOCA (Building Officials and Code Administrators International)

model code• ICBO (International Conference of Building Officials) model code• SBCCI (Southern Building Code Congress International) regulations

Overview

DesignObjectives

References


For Canadian applications, you must read and become familiar with thefollowing documents, codes, and standards:

• NFPA 92A Recommended Practice for Smoke Control Systems

• ASHRAE publication entitled Design of Smoke Control Systems forBuildings

• NFPA 92B Smoke Management Systems in Malls, Atria, and LargeAreas

• National Building Code

• Provincial Building Codes

• Supplement to the National Building Code

The following smoke control technical bulletins are currently available:

• Smoke Control (LIT-636330), this technical bulletin

• Metasys Smoke Control Wiring (LIT-636331)

• Smoke Control UL 864 UUKL Compliance Checklist (LIT-636333)

• How to Use the Metasys Smoke Control Library (LIT-636332)

The following list names the smoke control application notes that arecurrently available:

• Fire Fighter’s Smoke Control Station (FSCS) (LIT-6363351)

• Local Sonalert Logic (LIT-6363352)

• Single Story Enclosed Shopping Mall (LIT-6363353)

• Single Story Enclosed Shopping Mall; Independent Manual Override(LIT-6363354)

• Multi-Story Building Floor Above/Floor Below Pressurization andExhaust Logic (LIT-6363355)

• Multi-Story Building Floor Above/Floor Below Pressurization andExhaust Logic Independent Manual Override (LIT-6363356)

• Warehouse Smoke Exhaust and Reset Logic for a Rooftop Unit(LIT-6363357)

• Warehouse Smoke Exhaust and Reset Logic for a Rooftop Unit;Independent Manual Override (LIT-6363358)

• Weekly Testing of Dedicated Stairwell Pressurization Fans(LIT-6363359)

TechnicalManuals

ApplicationNotes

GPLApplications


• DX-9100/9120 Local Sonalert Logic (LIT-63633520)

• DX-9100/9120 Single Story Enclosed Shopping Mall (LIT-63633521)

• DX-9100/9120 Multi-Story Building Floor Above/Floor BelowPressurization and Exhaust Logic (LIT-63633522)

• DX-9100/9120 Warehouse Smoke Exhaust and Reset Logic for aRooftop Unit (LIT-63633523)

• DX-9100/9120 Weekly Testing of Dedicated Stairwell PressurizationFans (LIT-63633524)

DX-9100/9120Applications



Smoke Control Requirements

This section contains the Metasys configuration requirements for a UL 864UUKL Listed Smoke Control system. These must be followed in order tocomply with the UL Listing. (Assume any reference to UL Listing to meanUL 864 UUKL Listing, unless otherwise stated.)

Note: The Smoke Control Listing prescribed here is valid only with otherSmoke Control Listed Metasys system components. For example,the NU-NCM300/350-2/-8 is Smoke Control System EquipmentListed (UUKL) but with a complementary Energy ManagementEquipment Listing (PAZX). If any non-UL 864 UUKL Listedcomponent is connected to the Network Control Module (NCM)used for smoke control (see left side of Figure 1), the system nolonger complies with the UUKL Listing but can comply with thePAZX Listing. To comply with the UUKL Listing, all non-UUKLListed equipment should be installed as shown on the right side ofthe NU-ARCHUB as shown in Figures 1 or 4.

The National Fire Protection Association (NFPA) and UL have publisheddocuments, which include provisions for the control of smoke. Thesedocuments are as follows:

• NFPA 92A Recommended Practice for Smoke Control Systems

• NFPA 90A Air Conditioning Systems

• UL 864 Control Units for Fire Protective Signaling Systems

• UL 555S Standard for Leakage Rated Dampers for Use in SmokeControl Systems

• NFPA 72 National Fire Alarm Code

• NFPA 70 National Electrical Code

• NFPA 101 Life Safety Code

In Canada, refer to the following documents:

• National Building Code• Supplement to the National Building Code• Provincial Building Codes• ULC/ORD-C100-1992 Smoke Control System Equipment• CAN/ULC-S112.1-M90 Standard for Leakage-Rated Dampers for Use

in Smoke Control Systems

AgencyRequirements

Current versions ofNFPA documentscan be purchasedby calling theNational FireProtectionAssociation at(800) 344-3555.

Current versions ofUL documents canbe purchased bycalling UL at(847) 272-8800.


As with other types of systems designed and installed to protect life andproperty, the responsibility for approving equipment, installations andprocedures lies with the local Authority Having Jurisdiction (AHJ). Thephrase “Authority Having Jurisdiction” refers to the agency or individualresponsible for approving equipment, an installation, or a procedure andgiving permission to occupy a building. In most municipalities, thatresponsibility lies with the fire chief, fire marshal, electrical inspector,insurance carrier, or others having statutory authority. Become familiarwith the building codes of your community as their requirements maydiffer from those of the NFPA.

The following requirements must be followed in configuring andassembling a Metasys Network in order to comply with theUL 864 UUKL Smoke Control Listing:

• All field wiring must be done in compliance with Johnson ControlsMetasys Smoke Control Wiring Technical Bulletin (LIT-636331).

• A UL 864 UUKL Listed active hub (NU-ARCHUB-0 available directlyfrom Johnson Controls) must be used to isolate allnon-UL 864 UUKL Listed devices (e.g., non-Listed NCMs andnon-Listed Operator Workstations) from all Listed devices on theN1 Local Area Network (LAN). The N1 segment connecting all of theListed devices must be isolated by the Listed active hub from the N1segment connecting all non-Listed devices.

• The ARCNET card to use for connecting the Fire OperatorWorkstation and the NU-NCM300/350 to the N1 LAN must be theNU-ARC101-0 (available directly from Johnson Controls).

• When required, a UL 864 UUKL Listed FSCS must be used to providemanual control of smoke control systems. A UL Listed annunciatorpanel, such as the one made by Automation Displays, Inc., may be usedas the FSCS. As an alternative, the UL Listed Fire OperatorWorkstation (Fire OWS) with graphics can be used. However, manyfire departments prefer a custom graphical annunciator to displaysmoke control system status and for manual override control, and theywill not use a computer terminal for smoke control.

• Each binary output (BO) object, used for pressurization and exhaustcontrol outputs, must be configured with its own feedback binary inputwhich monitors the associated controlled equipment status. For smokecontrol dampers, provide a pair of feedback binary inputs for thetwo damper end switches. For fans used for smoke control, providepositive indication of air flow with either a flow switch or current senseto determine the On/Off status of the fan.

Smoke ControlSystemRequirementsperUL 864 UUKL


• Positive indication on the FSCS of the operation of all smoke controlequipment must be provided, such as both the open and the closeddamper end switches for each smoke damper, air flow measurement, orstatic pressure measurement for each smoke control fan, and both thefan on and off status.

• When any smoke control equipment does not respond to automatic ormanual commands, this trouble condition must be visibly and audiblyindicated on the FSCS.

• The Local Sonalert Logic application must be used on the FSCS for allsmoke control systems.

• The Weekly Testing of Dedicated Stairwell Pressurization Fansapplication must be used on all dedicated smoke control systems.(See the Dedicated vs. Non-dedicated Smoke Control Systems section todetermine whether you have a dedicated system.)

• If the Fire OWS is not being used, the UL Listed PRN Series printermust be connected directly to at least one UL ListedNU-NCM200/201-0 or NU-NCM300/350-2/-8 that is running thesmoke control algorithm, and if connected to the N1 segment that isconfigured in compliance with the UUKL Listing (see left side ofFigures 1 or 4), then the NCM must be configured as NetworkController (NC) Direct. You must configure the PRN Series printer torecord all smoke control system alarm and trouble messages. If thesystem has a Fire OWS, this printer can be connected to it.

• The status of all smoke control systems must be displayedsimultaneously on the override device (FSCS). Once a system has beenaccessed, you must display on the override device all control points(fans, dampers, etc.) in that system simultaneously.

• Duct smoke detectors are often located in the return duct of a Heating,Ventilating, and Air Conditioning (HVAC) fan and connected to stopthe fan when smoke is detected (which is in compliance with NFPA90A). However, if the fan is used for smoke control, and the smokecontrol strategy is such that the return duct will be configured toexhaust smoke from the building during the smoke control systemoperation, then the duct detector should be prevented from stopping thefan, once the smoke control system has been activated.

• Automatic activation of any smoke control sequence of operation musthave priority over any automatic environmental control strategy andover any non-smoke control manual commands. When an automaticsmoke control sequence is initiated, you must bypass the followingoperational overrides:

- High and Low Temperature Protection Devices (i.e., A-11 andA-25 series Temperature Protection Devices)

- Return and Exhaust Air Duct Smoke Detectors


Note: Indication of an alarm condition from any air duct smoke detectorshould be available to FSCS operators so that they can makeinformed decisions concerning their override actions if smoke isdetected elsewhere, especially in the supply air. This can be in theform of annunciation on the fire alarm system control panel or aremote annunciator controlled by the fire alarm system.

• Manual activation or deactivation of any predefined smoke controlstrategy from the manual override station must have priority over anyautomatic smoke or environmental sequence of operation. The FSCSserves as the manual override station.

After an alarm has been received and acted upon by the smoke controlsystem, additional alarms will not cause the smoke control system totake automatic secondary actions. However, the system will executeany manual commands from the FSCS.

• All communication links between buildings must be fiber optic cable orcopper cable buried in a conduit that is separate from power wiring.

• Response time for individual smoke control components to achievetheir desired state of operational mode, exclusive of control systemresponse, should not exceed the following time periods: 60 seconds forfan operation at the desired state plus 90 seconds to annunciate;75 seconds for completion of damper travel plus 90 seconds toannunciate. In the case of fan start after damper close, these times areadditive. If the damper must be closed before the fan starts, the totalresponse time could be up to 135 seconds for operation, 75 seconds fordamper to close plus 60 seconds for fan to start. Time to annunciatewould be added to this time. (Control system response is the time fromautomatic detection of a smoke condition to the issuing of anappropriate command to the equipment.)

• In smoke control applications, you must reserve Priority 2 commandsfor BOs used for smoke control functions, such as fan and dampercontrol. All other non-smoke control logic should use lower commandpriorities.

• To design a smoke control system that sends commands across theN1 LAN, you must use the NU-NCM200/201-0 orNU-NCM300/350-2/-8 to interface all input and output smoke controlpoints. The NU-NCM300/311-0 and NU-NCM 300/311/350/361-1 arenot approved nor are they UL Listed for smoke control use. TheNU-NCM101-1 is UL Listed for smoke control use but may not be usedfor performing smoke control across the N1 LAN.


The following requirements apply to DX-9100/9120 applications:

• A DX base with transient protection devices [Metal Oxide Varistors(MOVs)] must be used. The Johnson Controls product code number forthe DX base with MOVs is DX9100-8990F.

• All alarm input Digital Inputs (DIs) are monitored and report criticalalarms at the Fire OWS when they close (turn On), such as a fire alarmcontrol panel smoke detector alarm point.

• You must monitor the fuse on the DI circuit of each DX-9100/9120when the DI is used for smoke control. To do this, connect a jumperwire across one spare DI, so that it will always indicate an Oncondition. If the fuse fails, this point will go off, indicating a fusefailure. Map this point to the Fire OWS (or to the required PRN seriesprinter directly connected to the NC) as a critical alarm with a normalstate of Closed (On).

• Any time that you use Analog Outputs (AOs) in your configuration forsmoke control, you must monitor the fuse on the AO. To do this, setone AO for voltage and define an Analog Input (AI) for voltage.Connect Analog Constants (ACs) set for 50.0 to the AO that is rangedfor 0–100. This gives the AO a 50 percent signal or a 5 volt output.This output is hardwired back to the AI defined for voltage with a rangeof 0–100 and a low limit of 20. If the AO fuse blows, the voltage willgo to 0 and the AI will go into low alarm. This alarm must bemonitored as a critical alarm.

• Any DX-9100/9120 used in a smoke application must have a Metasyspoll priority of 1 or 2.

• All fans controlled by the DX-9100/9120 must have an air flow statusswitch. Any mismatch of command and status of the fans must report acritical alarm at the FSCS.

• If you are using a fire alarm control panel connected to aDX-9100/9120, you must use a contact interface.

Note: The IFC-1010/2020 may be connected directly to the MetasysNetwork via the N2 Bus or the Metasys Intelligent Fire Network(MIFN), and therefore would not need to interface through theDX-9100/9120. All other fire alarm systems used to initiate thesmoke control system actions would have to use theDX-9100/9120 interface.



Requirements of a FSCS include the following:

• The FSCS must have full monitoring and manual control capabilityover all smoke control systems and equipment.

• The FSCS must have the capability to override (partially or in full) anyoperation in progress, including programmed actions, non-smokecontrol manual overrides, and non-smoke control bypasses.

• The FSCS must have highest priority over all smoke control systemsand equipment.

• The FSCS requires a building diagram clearly indicating the type andlocation of all smoke control equipment.

• The FSCS must have indication of the actual status (not the commandstatus) of systems and equipment used for smoke control. This includesboth the full open status and the full closed status of each smokecontrol damper, the status of each fan used for smoke control, and theair flow status of every fan.

• The FSCS must activate an audible signal if the operation proof sensor(binary feedback point) failed to provide positive feedback that itscommand was executed.

• If you choose to use an annunciator panel as your FSCS, two sources ofUL Listed display panels are:

Automation Displays, Inc.(ADI)3533 N. White AvenueEau Claire, WI 54703(715) 834-9595

CorporateCustomer Service(call for manufacturing location)(309) 797-0200

• There may be only one FSCS on a Metasys Network used for smokecontrol applications, unless multiple FSCSs are approved by the AHJ.

• A custom annunciator-type FSCS can be connected to any UL ListedNU-NCM200/201-0 or NU-NCM300/350-2/-8 in the network. Formore information on the FSCS, refer to the Fire Fighter’s SmokeControl Station (FSCS) Application Note (LIT-6363351) in this manual.

• As an option, the Fire OWS with graphics could be used as an FSCS,but only if the AHJ and/or fire department approves.

• All hardware supervision alarms, such as binary feedback alarms onfans and dampers, as well as the system alarm points, must turn on theFSCS alarm horn.

Fire Fighter’sSmoke ControlStation (FSCS)


Smoke Control Restrictions

The following are smoke control system restrictions per UL 864 UUKL:

• Do not use the fire alarm system manual pull stations to initiateautomatic smoke control sequences.

• Do not use a smoke detector to initiate a smoke control strategy exceptas detailed in the Smoke Control Strategies section of this document.

• Do not use the Intelligent Lighting Controller (ILC) to monitor orcontrol smoke control equipment. Also, do not use the IntelligentAccess Controller (IAC-600), any third-party lighting controller, anythird-party access controller, or any other subsystem equipment notUL 864 UUKL Listed.

• You cannot use a standard, non-UL 864 UUKL Listed OWS as theFSCS.

• Manual operations occurring from a non-UL Listed OWS isolated fromthe Fire Network (FN) must not have priority over automatic smokecontrol sequences or those initiated manually from the manual overridestation.

• You cannot use the Operator Terminal on a Metasys Network used forsmoke control.

• You may use the Network Terminal (NT) on a Metasys Network usedfor smoke control but cannot use the NT for smoke control functions.

• Do not override the following operational safeties during automaticsmoke control operation:

- Electrical Disconnects

- Overloads

- Duct Static Pressure Limits

- Supply Air Duct Smoke Detectors

Smoke ControlSystemRestrictionsperUL 864 UUKL


The following are smoke control system restrictions per UL 864 UUKLfor the DX-9100/9120 applications:

• The buttons on the face of the DX-9100/9120 cannot be used tooverride smoke control points. Any DX-9100 used for smoke controlmust be locked in an enclosure (e.g., EN-EWC25-0 or FSCS enclosure)to prevent unauthorized access to the DX-9100/9120.

• Any field or communication wires connected to the XP9102 cannotleave the room in which the XP9102 is mounted in unless transientprotection is provided. See Metasys Smoke Control Wiring TechnicalBulletin (LIT-636331) for more information.

The following are smoke control system restrictions per UL 864 UUKLfor Fire OWS applications:

• If the Fire OWS has been approved by the AHJ as the FSCS, it may beused for Metasys operation only. Other applications, such as for wordprocessing and spreadsheets, cannot be active.

• If the Fire OWS is used as the FSCS, a watchdog timer is required atthe Fire OWS (WD-TIMER-FIRE). For watchdog timer installation,refer to the Fire Operator Workstation (Fire OWS) Technical Bulletin(LIT-636014).

• Going from the Metasys software to Program Manager must berestricted to operators with high level password access to prevent thenormal operator from exiting Metasys operation. The Fire OWS cannotprevent an operator from exiting the Metasys system, so it is thesupervisor’s responsibility to ensure that this does not occur.


Fire OperatorWorkstation(Fire OWS)


Design Considerations

This section outlines the design criteria to be considered whenimplementing a smoke control strategy.

In general, the movement of smoke will follow the same pattern as theoverall air movement within a building. The major influences causingsmoke movement include stack effect, air/smoke buoyancy, air/smokeexpansion, wind, pressure, and the operating HVAC system. In a firesituation, a combination of these influences usually causes smokemovement. An accepted way of containing smoke within a compartmentor an area is to create pressure differences across partitions that separatethe affected area from the surrounding areas. This is accomplished bycreating higher pressure in the adjacent space than is in the smoke zone.The pressure differential should be sufficient to overcome the effects ofwind pressure, the stack effect, and the buoyancy of hot gases, yet permitdoors leading to emergency exit routes to be opened.

In addition, the movement of smoke through openings such as doors canbe minimized with air flow. For example, a stairwell may be pressurized,thereby minimizing the migration of smoke into it. Should one of thestairwell doors open, the movement of smoke will be reduced by the flowof fresh air from the stairwell into the affected area.

Note: Elevator shafts should be treated like stairwells and be positivelypressurized to prevent vertical migration of smoke through thebuilding. Inter-floor and inter-area duct work not being used foractive smoke control may be closed at the appropriate locations, asdetailed in the documents listed in the References section of thisdocument.

SmokeMovement


To help you in designing your smoke control system, this section showsseveral approved smoke control examples, which comply withUL Listings. Keep in mind that these are only examples. The mixture ofcomponents in your system will probably differ. Just be sure that yoursystem complies with all device and communication requirements andrestrictions.

Fire OWS(See Notes.)

NU-NCM300-FIRE

IFC Panel

)

IN TE LL IG EN T FI RE D ET EC T ION A N D A L AR M SY ST E M

Fire OWS and Metasys IntelligentFire Network (FN) Applications

IFC Panel

)


)


Metasys Fire

Network(loop)

OWS

N1 LAN

NU-NCM300/350-2/-8 (Smoke)

UL 916 Application Not Using Smoke Control

VAV

UL ListedActive Hub

(NU-ARCHUB-0isolates N1 segments.)

App1

*Must be installed in UL Listed enclosure or FSCS enclosure.

N1 LAN

NU-NCM 300/311-0NU-NCM 300/350/-1

DX-9100

ASCs are used for smoke control.**

DX-9100*

An FSCS may be used instead of the Fire OWS. For an example of an FSCS application, refer to Figure 3.

Notes:

N2 Bus

N2 Bus

Any UUKLListed N2Device

**The ASC on this N2 may be used for function other than smoke control, but all ASCs on this N2 must be UL 864 UUKL Listed.

IntelligentFire Controller

(IFC) Panel

Unitary(UNT)

Controller

Figure 1: UL Listed Active Hub Isolating Smoke Control System fromNon-Smoke Control System

Smoke ControlApplicationExamples


NU-NCM350-8

IFC Panel

)


Smoke Control Using MetasysSecondary Reporting Configuration

M E TA S Y S

IFC Panel

)


App1a

N1 LAN

An FSCS must be used with this configuration instead of the Fire OWS. For an example of an FSCS application, refer to Figure 4.

Note:

UL ListedActive Hub

(NU-ARCHUB-0Isolates N1 segments.)

Metasys Fire Network (loop)

Figure 2: Smoke Control System Using Metasys SecondaryReporting Fire Network Configuration


App2

N1 LAN

NU-NCM300/350-2/-8 (Smoke)

Fire OWS(See Note.)

N1 LAN

Smoke Control Using Third-PartyFire Alarm Control Panel

NU-NCM300/350-2/-8 (Smoke) NU-NCM300/350-2/-8 (Smoke)

Smoke Control Using IFC Panel

Fire Alarm Control Panel(Third-Party)

DX-9100**

I N T E L L I G E N T F I R E D E T E C T I O N A N D A L A R M S Y S T E M

DryContacts

DX-9100**

N2 Bus

IFC Panel

)

IN TELLIGEN T FIR E DETECTI ON AND ALARM SYSTEM

N2 Bus

UNT

I N T E L L I G E N T F I R E D E T E C T I O N A N D A L A R M S Y S T E M

Fire Alarm Control Panel(Third-Party)

ASCs are used for smoke control.***Any UUKLListed N2Device

MIG*

UL ListedActive Hub

(NU-ARCHUB-0isolates N1 segments.)

UL ListedActive Hub

(NU-ARCHUB-0isolates N1segments.)

VAV

** Must be installed in UL Listed enclosure or FSCS enclosure.

Notes:

* Metasys Integrator Gateway

*** The ASC on this N2 may be used for function other than smoke control,but all ASCs on this N2 must be UL 864 UUKL Listed.

N2 Bus

An FSCS may be used instead of the Fire OWS. For an example of an FSCS application, refer to Figure 3.

Figure 3: IFC and Fire Alarm Control Panel Smoke Control Applications


App3

N1 LAN

NU-NCM300/350-2/-8 (Smoke)

Smoke Control Using FSCS Annunciator Panel

UNT Air Handling Unit(AHU)

XT

XP

XT

XP

FSCSAnnunciatorPanel

XP XP

NU-NCM300/350-2/-8 (Smoke)

FSCS Enclosure

N2 Bus

Standard OWS

UL ListedActive Hub

(NU-ARCHUB-0isolates

N1 segments.)

DX-9100*

* Must be installed in UL Listed enclosure or FSCS enclosure.

NU-NCM350-2/-8

Ethernet

N2 Bus Any UUKLListed N2Device

Figure 4: Smoke Control Using FSCS


NU-NCM300-2/-8 (Smoke)

Fire OWS and Metasys Intelligent

Fire Network (FN) Applications

N1 LAN

UL 916 Application Not Using

Smoke Control

VAV

App4

N1 LAN

NU-NCM200

DX-9100*

N2 Bus


* Must be installed in UL Listed enclosure or FSCS enclosure.

UL ListedActive Hub

(NU-ARCHUB-0isolates

N1 segments.)

UL Listed Inputand Output Devicesfor Smoke Control

To standard OWSand other UL 916 Non-SmokeControl Equipment(as shown in Figure 1).

VAVDX-9100*


N2 Bus

***

UNT UNT

Any UUKL Listed N2 Device Any UUKL

Listed N2 Device

Transient protection must be appliedas shown in

as necessary to comply with UL Listing.

Metasys Smoke ControlWiring Technical Bulletin (LIT-636331)

***

** The ASC on this N2 may be used for function other than smoke control, but all ASCs on this N2 must be UL 864 UUKL Listed.

Notes:

Figure 5: Addition of the NCM200 Configured to Complywith UL 864 UUKL Listing


Building HVAC Systems Usedin Smoke Control

Central air handling unit systems are frequently employed in smokecontrol designs. The designer should ensure that the system’s capacity issufficient to supply the quantity of outdoor air necessary to pressurize theareas adjacent to any fire area. The designer should also make sure that thefan systems can handle situations where a fire may expand to other areas,requiring more areas to be positively pressurized. In addition, the installermust install smoke dampers at the duct risers of each floor’s supply andreturn takeoffs as required by NFPA 92A. Pressure controls should also beemployed in order to avoid rupturing or collapsing the ductwork.

Smoke control systems generally fall into two categories: dedicated andnon-dedicated.

Dedicated smoke control systems are fan, damper, and duct systemsdesigned for the sole purpose of controlling smoke within a building. Theyform a system of air movement that is separate and distinct from thebuilding’s HVAC system and only operate to control the flow of smoke.With their function being dedicated to the performance of smoke control,they are more immune to faults in the building’s HVAC system. They are,however, more costly than non-dedicated systems, and because they arenot in continuous use, faults may go undetected.

Note: To assure full performance and maintain UL compliance, applyperiodic testing to all dedicated systems, including dedicatedelevator shaft fans, dampers used exclusively for smoke control,and the like. Refer to the Weekly Testing of Dedicated StairwellPressurization Fans Application Note (LIT-6363359) in thismanual for details on how to perform the necessary tests.

Non-dedicated smoke control systems share components with other airmoving equipment normally used for building environmentalcontrol.When the smoke control mode is activated, the operating mode ofthe building’s HVAC equipment changes in order to accomplish theobjectives of the smoke control design. Non-dedicated systems tend to beless costly and occupy less of the building’s space. However, from anoperational standpoint, the control strategy may become elaborate. Thismay expand the number of control and monitoring points connected to aFacility Management System (FMS) and increases the complexity of thesequence of operation of the air moving equipment.

CentralSystems

Dedicated vs.Non-dedicatedSmoke ControlSystems


If sufficient outdoor air is available and the system has the capability toexhaust an area, individual or floor-by-floor fan units can be used insmoke control applications.

These types of units are generally located on the perimeters of buildingsand only draw enough outdoor air to fulfill the fresh air requirements ofthe spaces they serve. They are often used in conjunction with centralsystems, which deliver fresh air and exhaust recirculated air in largerquantities. When the fan coil unit is not located in the smoke zone, it isacceptable to exclude it from the smoke control sequence. When the unitserves the smoke zone in a design that calls for the area to be negativelypressurized, its outdoor air damper should be closed, and the unit shouldbe de-energized.

During a smoke control mode, induction units that serve the smoke zoneshould be shut down, or their primary air source should be closed off.

The Variable Air Volume (VAV) system, when employed as part of asmoke control strategy, is a subset of the general central system categorydescribed above. Employ control strategies that ensure adequate quantitiesof air pass through the terminal units to permit floor pressurization in theareas adjacent to the smoke zone. This may include overriding the airvolume control to provide maximum deliverable air to the areas adjacentto the fire area. If fan powered terminal units are used and installed in thesmoke zone, shut off their fans. If bypass dampers fulfill the volumecontrol, close the damper during smoke control mode.

All dampers used as barriers in smoke partitions or as safety dampers in asmoke control system should be UL Listed and Classified for use in thatapplication. (Refer to UL 555S Standard for Leakage Rated Dampers forUse in Smoke Control Systems.) In Canada, smoke dampers should beULC or CUL Listed and Classified for use in that application. (Refer toCAN/ULC-S112.1-M90 Standard for Leakage-Rated Dampers for Use inSmoke Control Systems.)

Individual FloorFan Units

Fan CoilUnits/WaterSource HeatPumps

Induction Units

Variable AirVolume (VAV)Systems

SmokeDampers


Smoke Control Strategies

The smoke alarm initiation of an automatic smoke detection device, suchas an area-type smoke detector located in one of the facility’s smokezones, generally activates the smoke control system. This activationinitiates a control strategy for the air moving equipment to create higherpressures in the areas surrounding the smoke zone than are present in thesmoke zone. This may include positively pressurizing areas adjacent to thesmoke zone and/or negatively pressurizing the smoke zone and exhaustingair from that area. Subsequent alarms in other zones must be preventedfrom automatically changing the initial smoke control sequence. Keep inmind the guidelines provided in this section when planning your smokecontrol strategy.

Notes: Do not use duct type smoke detectors exclusively to activate smokecontrol. This is for three reasons:

1. The dilution of air in the duct system will likely result in aslow response time.

2. The supply air duct detector, when exposed to outside air inthe HVAC supply air duct, may report a false alarm.

3. The duct system may move smoke from the smoke zone andthis will cause the duct detector in the return/exhaust duct ofthe non-dedicated fan system to register an alarm.

However, it may be acceptable to use a duct smoke detector if it isnot exposed to outside air, the duct detector’s coverage area isequal to the area covered by a spot type area smoke detector(typically 900 square feet or less), and/or the application has beenapproved by the AHJ.

Manual initiating devices (pull stations) must not be used to initiate asmoke control sequence, since there is no certainty that manual deviceswill be activated in the area of involvement. However, you can use manualpull stations to initiate global operations, such as energizing stairwell andelevator shaft pressurization fans.

ManualInitiatingDevices(Pull Stations)


End-to-end verification is required to ensure that the smoke controlsequence of operation has been implemented. Verification must beaccomplished by using damper position indicators and air flow switches.Any failure that results in command not equaling condition must generatean audible and visual alarm at the FSCS. For smoke dampers, there mustbe a positive indication of the damper’s fully opened position and its fullyclosed position for purposes of display on the FSCS and alarm reporting ifthe damper position does not agree with the commanded position. For apermanent record of alarms, including situations where the commandedsmoke control sequence does not equal condition, use the UL ListedPRN Series printer.

Fan relay supervision is required if the project must meet Life SafetyCode, NFPA 101 requirements. The auxiliary relay used to control themotor starter on the HVAC system fan must be located within three feet ofthe motor starter and the wiring between the fan shutdown controller andthe shutdown relay must be monitored for integrity (supervised). This canbe accomplished by using electronic supervision or continuously poweredshutdown relays that will turn the fan off if power is lost to the relaycircuit. In addition, proof of fan operation (e.g., an air flow switch) isrequired.

Response time for individual components to achieve their desired state ofoperational mode, exclusive of control system response, should not exceedthe following time periods: 60 seconds for fan operation at the desiredstate plus 90 seconds to annunciate; 75 seconds for completion of dampertravel plus 90 seconds to annunciate. In the case of fan start after damperclose, these times are additive. If the damper must be closed before the fanstarts, the total response time could be up to 135 seconds for operation,75 seconds for damper to close plus 60 seconds for fan to start. Time toannunciate would be added to this time. (Control system response is thetime from automatic detection of a smoke condition to the issuing of anappropriate command to the equipment.)

End-to-EndVerification

Fan RelaySupervision

Response Time


Applying the Metasys Networkas a Smoke Control System

In general, the equipment you use in an engineered smoke controlapplication is the same as that used in environmental control applications.However, there are some unique components, such as theNU-NCM200/201-0 and NU-NCM300/350-2/-8, the UL Listed active hub(NU-ARCHUB-0), and the FSCS, that must be used to comply with thecomponent performance requirements of the UL UUKL Listing. Also,there may be significant differences in the way the equipment is installedand the quantity and type of control and monitoring points that areconnected.

All devices used for smoke control applications must communicate withthe UL Listed Network Control Module (NU-NCM200/201-0 orNU-NCM300/350-2/-8). Be certain to account for any extra monitoring(feedback) and/or control points required because of the smoke controldesign. Refer to the Network Control Module 300 Series TechnicalBulletin (LIT-6360251) in this manual for information on how to properlyinstall the NU-NCM300-2/350-2/-8.

Note: All NU-NCM200/201-0 and NU-NCM300/350-2/-8 devices, theFire OWS (if used), and the N1 LAN that connects them must beisolated from other non-smoke control NCMs and standardOperator Workstations by a UL Listed active hub(NU-ARCHUB-0) as detailed in the Smoke Control SystemRequirements per UL 864 UUKL section of this document and asshown in Figure 1 or Figure 4.

NetworkControl Module(NU-NCM300/350-2/-8)


NCM 350 Ncm350

1 2 3 4 5 6 7 8

1 2 3 4 5 6 7 8

IN

OUT

RELO

AD7 8

POWER

ONCO

NFIG.

END OFLINE

a b D-RAM

-ATTENTION -PLEASE DISCONNEDT BATTERY

BEFORE INSTALLING MEMO RY

BATTERY

NEXT SERVICE DATE:

POWER

SUPPLY

DISCONNECT

POWER BEFORE

SERVICING

DANGER

LINE VOLTAGE

INS IDE

b

ISASLOTS

I

II

IV

COMM-PORTS

III

II

III

IV

I

RE

FN

2

-

N2

+

NCM 3

50

Figure 6: NU-NCM300/350-2/-8 Network Control Module(outside its enclosure)


If using the NU-NCM300/350-2/-8 the UL UUKL Listing requires thatyou use the NU-ARC101-0 ARCNET card for N1 LAN communication.See the next section for using the NU-NCM300/350-2/-8 with theNU-NET201-0 for Echelon communication. This card is installed in theNU-NCM300/350-2/-8 and the Fire Operator Workstations to allow thesecomponents to communicate over the N1 LAN.

Figure 7 shows the ARCNET card with its switch and jumper settings asrequired by the NU-NCM300/350-2/-8. (ARCNET card settings for theFire OWS are covered in Fire Operator Workstation (Fire OWS)Technical Bulletin (LIT-636014). Set the switches and jumpers as shown.Be sure that the node address you set on the card matches the node addressset in the Metasys software.

E4

EN

RO

M

IRQ15IRQ14IRQ12IRQ11IRQ10IRQ7IRQ6IRQ5IRQ4IRQ3IRQ2/9

BA

LEIO

CH

RD

YO

WS

ME

ME

N16

B

MS

0M

S1

MS

2M

S3

MS

4

IOS

0IO

S1

IOS

2

MS

0M

S1

MS

2M

S3

MS

4

IOS

0IO

S1

IOS

2

CCSIARCNET

CCSI ARCNET PCA66, 16-bit

Boot ROM(Not installed) Typically No

ConnectionsNodeID

MSB

Used for bus speedcompatibility settings.

12

34

56

78

Dual Light-EmittingDiode (LED)

Yellow=accessed Green=transmitting

Open=1Close=0

Bayonet-Neill-Concelman(BNC)(Not installed)

SMC COM90C66

Figure 7: N1 ARCNET Card Settings for NU-NCM300/350-2/-8

The N1 LAN ARCNET board comes factory installed with the settingsshown below.

Input/Output (I/O) BaseAddress

= 2E0H

Memory Base Address = COOOOH

Interrupt (IRQ) = 4

E4-Programmable Read-OnlyMemory (PROM) Enable

= OFF

N1 ARCNETCard(NU-ARC101-0)

N1 ARCNETSettings


I/O BASE ADDRESS = 2EOH

IOS0 IOSI IOS2 ON OFF ON

BASE MEMORY ADDRESS = COOOOH

MS0 MS1 MS2 MS3 MS4 ON ON ON ON ON

IRQ = 4

Notes: ON = Jumper installedOFF = Jumper removed

Figure 8: Jumper Settings on CCSI ARCNET PCA66-CXB

• BALE (Bus Address Latch Enable) has no jumper.

• IOCHRDY (IO Channel Ready) has no jumper.

• OWS (Zero Wait State) has no jumper.

• MEMEN16B (Enable 16 Bit Memory) has no jumper.

(There cannot be a jumper on both IOCHRDY and OWS at the sametime.)

If the Metasys Fire Network is used (as shown in Figure 1), you need to setthe node address of the Fire-Net NCM on the Fire-Net NCM N1 LANARCNET board. All network nodes connected to either the N1 LAN orthe FN must have a node address to identify it on either one or both of thenetworks. IFC panels, Intelligent Network Annunciators (INAs), Fire-NetNCMs, and Fire OWSs are all FN nodes. The IFC panels and INAs areonly connected to the FN, while the Fire-Net NCMs and Fire OWSs areconnected to both the N1 LAN and the FN.

Since they connect to two networks, certain restrictions apply to theFire-Net NCM and Fire OWS node address. The node address for theFire OWS and Fire-Net NCM must be:

• within the range specified below• the same number on both the N1 LAN and the FNNote: The Metasys Intelligent Board (MIB) does not have Dual Inline

Package (DIP) switches to set its node address. It assumes the sameaddress that is set on the N1 ARCNET card in the Fire OWS or theN1 ARCNET card on the Fire-Net NCM.

IMPORTANT: Fire OWS must have a network node address between150-159.

N1 Node IDSwitches


IMPORTANT: The Fire-Net NCM must have a network node addressbetween 70-79.

Only Fire-Net NCMs and Fire OWSs can have node addresses in thoseranges. None of the other standard Metasys Operator Workstations,IFC panels, standard NCMs, or INAs can use these node addresses.However, nodes that are exclusive to either the N1 LAN or the FNcan use the same node address as a standard NCM that is connected to theN1 LAN only.

If you already have network nodes that are within the designated ranges forthe Fire-Net NCM and Fire OWS, you must change their node addresses.Refer to the appropriate technical bulletin for how to change that node’saddress. For example, to change the node address of a standard OperatorWorkstation that has an address between 150-159, see the OperatorWorkstation Technical Bulletin (LIT-636013) located in the MetasysNetwork Technical Manual (FAN 636).

Set the node address on the switches located on the N1 ARCNET board.Refer to the manual that came with the N1 ARCNET board for specificson how to set the switches. Figure 9 shows an example of a node addresswithin the required range for a Fire-Net NCM.

OPEN=1 CLOSED=0

Nn152

MSB LSB

1

0

1 2 3 4 5 6 7 8

Figure 9: Switches with Fire-Net Node Number of 70

If using the NCM300/350-2/-8 on the N2 Bus, a LONWORKS card(NU-NET201-0) is required (Figure 8). This card is installed into Slot 2(right-hand slot) of the NCM300/350-2/-8. You may notice a coloredbutton on the top of the card. If this service button is pressed, the Neuronchip sends out a message over the network with its unique ID code. Thiscould be useful for configuring or examining the LONWORKS network,but has no use with the Metasys System. Pressing the button does notaffect the network or any Metasys component. Refer to LONWORKS N2EBus Technical Bulletin (LIT-6364100) for more details about installing theNU-NET201-0 card.

DX-9120 Card(NU-NET201-0)


N2lonbrd

Echelon LONWORKS Chip Echelon LONWORKS Firmware Chip

Service Buttonand LED

Screw Plug Terminal(For N2 Bus Connection)

9-pin D-type Connector (Not Used)

I/O Address Switches

LON - V1.0 Neuron3150 Chip

GND VDC

OFF OFF OFF OFF

ST1

Figure 10: DX-9120 Card Settings for NU-NET201-0


You can initiate an automatic operation of a smoke control sequence inone of three ways.

The first method responds to an automatic smoke detector change-of-statedetected at the IFC-1010/2020 Fire Alarm Controller connected to theMetasys System via the N2 Bus (Figure 3). From a hardware standpoint,configure the IFC-1010/2020 Fire Controller to meet the fire alarm systemrequirements of the facility. Use your local building codes and therequirements of the AHJ to define the exact requirements. Install theIFC-1010/2020 per the IFC-1010/2020 Technical Manual (FAN 448).Connect the IFC-1010/2020 to the Metasys N2 Bus as detailed in theConnecting the IFC-1010/2020 to Metasys Technical Bulletin(LIT-448162) of the IFC-1010/2020 Technical Manual (FAN 448).

Alarms detected by automatic devices within a smoke zone activate anIFC-1010/2020 defined zone and the associated Metasys zone object.A unique zone object must correspond to each smoke zone within thebuilding, and that zone object must not change its state as a result of theactivation of a manual pull station. However, the zone object may changestate as a result of a sprinkler system flow switch, as long as the area of thesprinkler coverage is identical to the smoke control zone.

The second method of automatic initiation uses a non-IFC-1010/2020,third-party fire alarm system to trigger the smoke control strategy(Figure 3). This method uses contacts furnished as part of the fire alarmsystem connected to binary input devices on the Metasys FMS. Alarmsdetected by the third-party fire alarm system’s automatic devices within asmoke zone actuate these contact devices. A unique contact mustcorrespond to each smoke zone within the building, and that contact mustnot change its state as a result of the activation of a manual pull station.Each contact is then connected to a separate binary input at the Metasysbinary input panel of choice (as listed in the UL Listed Devices for SmokeControl section of this document). Since the connection between the firealarm system contact closure and the multiplexing panel is not supervisedfor wiring faults, the fire alarm system contacts and the multiplexing panelmust be located in the same room and the wiring between them must beenclosed in a metallic raceway not exceeding 20 feet. Activation of thesmoke control sequence begins immediately upon receipt of an alarmcondition.

InitiatingDevices

InitiatingDevices Used forAutomaticInitiation


The third method of automatic operation uses a Metasys UL ListedFire Network (Figure 1). A custom annunciator panel serving as the FSCScan also be employed. This third method responds to a change-of-statedetected at the IFC-1010/2020 Fire Alarm Controller connected to theMetasys System via the Metasys Intelligent Fire Network (MIFN). From ahardware standpoint, the IFC-1010/2020 Fire Controller should beconfigured to meet the fire alarm system requirements of the facility. Useyour local building codes and the requirements of the AHJ to define theexact requirements. Install the IFC-1010/2020 per the IFC-1010/2020Technical Manual (FAN 448). Connect the IFC-1010/2020 to the FN asdetailed in the Metasys Intelligent Fire Network Technical Bulletin(LIT-448196). Alarms detected by automatic devices within a smoke zoneactivate an IFC-1010/2020 defined zone and the associated Metasys zoneobject. A unique zone object must correspond to each smoke zone withinthe building, and that zone object must not change its state as a result ofthe activation of a manual pull station.

Manual implementation of the smoke control strategy takes place at theFSCS. The FSCS must be capable of overriding, either partially or in full,any automatic activation that may be in progress. It must also be capableof manually controlling each control point (damper, HVAC fan, etc.) thatis used for smoke control in the facility.

Note: The Fire OWS may be used to manually override smoke controloperation, if it is the sole FSCS for the facility. However, youcannot use a standard, non-Fire OWS to perform such an override.

Interface devices (those that interface field points to the controller) havethe following restrictions:

• They must be used and installed according to Johnson Controlsliterature.

• They must result in fan operation at the desired state within 60 seconds(plus 90 seconds to annunciate) when commanded.

• They must result in completion of damper travel within 75 seconds(plus 90 seconds to annunciate) when commanded.

For more information, see the GPL Programming Guidelines in theSystem Programming Guidelines for Smoke Control section of thisdocument.

InitiatingDevices Used forManualImplementation


As with other Facility Management scenarios, use Application SpecificControllers (ASCs) as required to meet the needed sequence of operation.Use AHUs, VAVs, and Unitary (UNT) controllers in the HVAC scenariosfor which they were designed. Your controller selection should account forthe fact that operational overrides and safeties are sometimes bypassed andmore control outputs may be required. Since positive indication of controlaction via flow switches and damper end switches (proof sensors) isrequired, the quantity of input points will generally increase as well. SeeMetasys Smoke Control Wiring Technical Bulletin (LIT-636331) forrestrictions on field wiring. All electrical installations should meet therequirements of NFPA 70 National Electric Code. Refer to the controller’stechnical bulletin for more information. (In Canada, installations shouldmeet the requirements of the Canadian Electrical Code or the provincialelectrical code.)

Note: Do not use the ILC (Intelligent Lighting Controller) to monitor orcontrol air moving equipment to be used in a smoke control design.Also, do not use the Intelligent Access Controller (IAC-600), anythird-party lighting controller, or any third-party access controlleror any other subsystem equipment that is not UL 864 UUKL Listedto monitor or control smoke control operations.

In more sophisticated control scenarios, use the DX-9100/DX-9120 withan XT/XP. Just like the ASCs mentioned above, the quantity of input andoutput points required at the DX-9100/9120 is generally large. Inputwiring connected to these controllers’ I/O points does not need to beshielded or installed in metallic raceway as protection against transients.See Metasys Smoke Control Wiring Technical Bulletin (LIT-636331) forrestrictions on field wiring. All electrical installations should meet therequirements of NFPA 70 National Electric Code. Refer to the controller’stechnical bulletin for more information. (In Canada, installations shouldmeet the requirements of the Canadian Electrical Code or the provincialelectrical code.)

Air MovingEquipment in aSmoke ControlSequence

ApplicationSpecificControllers

DX-9100/DX-9120Controllers


When using the NU-NCM200/201 or NCM300/350-2/-8 to configure theMetasys FMS for smoke control, a UL 864 UUKL Listed Fire OperatorWorkstation (Fire OWS) can share the N1 LAN segment with the NCM.You may connect additional Fire OWSs over the same ARCNET LANsegment, as long as the maximum number of allowed nodes per segment isnot exceeded. For details on node maximums, refer to the N1 ARCNETLocal Area Network Technical Bulletin (LIT-636017) in this manual.

The FSCS must have full monitoring and manual control capability overall smoke control systems and equipment. It must have the capability tooverride (partially or in full) any operation in progress, includingprogrammed actions, non-smoke control manual overrides, and non-smokecontrol bypasses. You may have only one FSCS on a Metasys Networkused for smoke control applications unless multiple FSCSs are approvedby the AHJ. For more details, refer to the Smoke Control Requirementssection earlier in this document.

You must provide visual and audible indication to alert an operator in theevent that a programmed smoke control sequence did not occur. Thiscan be accomplished by using the FSCS or Fire OWS. Visual indicationonly can be provided by the printer. Use Model PRN series and connect itto the configured printer port at the NU-NCM200/201-0 orNU-NCM300/350-2/-8 that is running the smoke control algorithm. Installa PRN series printer in the same room as the NCM, but the cabling doesnot need to be installed in conduit.

Any UL Listed Fire Alarm Control Panel (FACP) manufactured by a third-party may be used in conjunction with the Metasys Smoke Control system.See Figures 1 through 5 for details on system connections.

Fire OperatorWorkstation(Fire OWS)

Fire Fighter’sSmoke ControlStation (FSCS)

Visual andAudibleIndicatingDevices

Fire AlarmControlThird-PartyPanels


System ProgrammingGuidelines for Smoke Control

When programming the system for smoke control applications, the systemmust conform to the guidelines outlined below.

You can create your Metasys database using online generation from anOperator Workstation or with Data Definition Language (DDL) using anASCII text editor. See your Operator Workstation User’s Manual(FAN 634), or DDL Programmer’s Manual (FAN 632), for moreinformation.

Follow these guidelines when defining systems and objects:

• Name all systems used for smoke control in a manner that makesidentification obvious. For example, the air-handling unit serving thewest wing on the third floor might be called “AHU3_W” and thestairwell pressurization system might be called “STR_PRES.”

• Name all objects within a system used for smoke control in a mannerthat makes identification obvious. For example, the outside air dampermight be called “OSA_DMPR” and the mixed air damper might becalled “MXA_DMPR.”

• Use engineering units that are appropriate to easily determine thecurrent status of a device.

• Use the 24 character expanded ID attribute in an object definitionwindow to provide information that is pertinent to an object’s type andlocation and is easily understood in an emergency situation.

Use Graphic Programming Language (GPL) to define “automatic” and“manual” smoke control logic via software and process (logic) objects. ForGPL programming details, see the Graphic Programming LanguageProgrammer’s Manual (FAN 631).

Manual override operations take precedence over any automatic smokecontrol sequence of operation. Assign all manual override processes aprocess priority of 1 and a command priority of 2, the highest priority inthe system from a process.

Use the GPL Smoke Control library of applications for examples ofautomatic smoke control sequences. For details, refer to the documentsunder the GPL Applications tab in the Smoke Control section of thismanual.

OnlineGeneration andDDLProgrammingGuidelines

GPLProgrammingGuidelines


You can use the smoke control applications as written, or modify them tomeet your requirements. For help on selecting these applications, refer tothe How to Use the Metasys Smoke Control Library Technical Bulletin(LIT-636332) document under the Smoke Control section of this manual.


UL Listed Devices for SmokeControl

The following lists Johnson Controls equipment that has received theUL Smoke Control Listing.

• AP-VMA Series

• AS-AHU Series

• AS-FMK Series

• AS-RLY Series

• AS-UNT Series

• AS-VAV Series

• AS-XFR Series

• DX Series

• EN-BSF Series

• EN-EWC Series

• EN-PLR Series

• EN-TBC Series

• EN-TBF Series

• EN-TBP Series

• EN-EWC Series

• EN-EXP101

• EN-WIN101

• FM-IAN101

• FM-IAP101

• FM-IBF101

• FM-IBN101

• FM-IDP Series

• FM-IDPB Series

• FM-IUN102

• FM-OAE101

• FM-OAI101

• FM-OAN101

• FM-OAP Series

• FM-OBE101

• FM-ORE101

• FM-ORL101

• FM-ORM101

• FM-OSV101

• FM-OTE101

• IO-NTU Series

• MIB-OWS Series

• NU-ARC101-0

• NU-ARCHUB-0

• NU-ARCCX-0

• NU-ARCFB-0

• NU-ARCCFB-0

• NU-BAT101

• NU-COM101

• NU-DCM Series

• NU-L2B101

• NU-MDM101

• NU-EOL201

• NU-N2B101

• NU-NCM101*

• NU-NCM102*


• NU-NCM200

• NU-NCM201

• NU-NCM300-2

• NU-NCM350-2

• NU-NCM350-8

• NU-NCM401

• NU-NCM300-FIRE***

• NU-NCMFIRE-1***

• NU-NET201-0

• NU-PWR101

• NU-XBN101

• NU-XRL Series

• NU-XRM Series

• FIREOWS-PC-01

• FIREOWS-PC-02

• FIREMON-17

• FIREMON-21

• XP9 Series

• XPx Series

• XTM Series

* Indicates devices that cannot be connected to an N1 network overwhich smoke control sequences are running.

** UL Listed as System Control Unit and used with smoke controlsystem.

*** UL Listed as System Control Unit Accessories and used with smokecontrol system.


Notes


Notes

Controls Group www.johnsoncontrols.com507 E. Michigan Street FAN 636P.O. Box 423 Metasys Network Technical ManualMilwaukee, WI 53201 Release 11.00

Printed in U.S.A.

Documents

Smoke Control Technical Bulletin - Viking Controls