DDC Online direct digital controls
Solidyne - IZAC Control and Monitoring System  [Archived]

System Architecture

Date Last Saved: 6/24/2004 7:31:22 AM

This section distinguishes between Operator Interfaces and Field Interfaces to the BAS. The Operator Interface refers to the main 'front-end' method for accessing and operating the BAS. The Field Interfaces typically access the BAS from the controller-level and have limited functionality, and may include HID, LDP, and ZBI as described below. This section describes the devices only; OI functionality is generally covered in the Software, while Field Interface functionality is detailed further in the individual Controllers
Operator Interfaces (OI)
Dedicated Operator Workstation (OWS)
Dedicated PC(s) with proprietary workstation software
PC with ICMS software
"Thin" Client Browser Internet Explorer or Netscape Navigator
"Thick" Client Browser
Product Application(s): N.A.
Handheld Interface Devices (HID)
PDA-Based Any browser-capable device
Proprietary Handheld version of Local Display Panel. Two-line display. Powered by the controller it is attached to.
Local Display Panel (LDP) Optional. Zone-mounted version of the Handheld Interface Device. Two-line display. Powered by the controller it is attached to.
Zone Based Interfaces (ZBI)
Thermostat with communication port to access local controller/network Available. See individual controllers for more information
Other thermostat types available (without communication ports)
Zone sensor
Zone sensor w/ occupant override
Zone sensor w/ setpoint adjustment
Zone sensor w/ occupancy sensor
Interface to BAS Networks Possible with interface hardware. The I3 (server/gateway) permits a PC (running ICMS software) or a thin-client (browser) to interface with the proprietary IZAC primary network.
Compatible with the building's IT network? Yes - through I3
Protocol(s) Proprietary
Cabling and Speeds RS-485 (shielded 3-wire) @ 1200-9600 bps (selectable)
Expansion Capability Each primary controller LAN can accommodate up to 1000 controllers. Repeater required for every 50 controllers. An unlimited number of LANS are possible limited only by OWS hard disk capacity.
Additional Information
Peer-to-Peer or Polling? None - No secondary network
Protocol(s) None - No secondary network
Cabling and Speeds None - No secondary network
Expansion Capability None - No secondary network
Additional Information
Includes a listing of available Gateways, Routers and other devices that provide additional communications flexibility into and out of the BAS. Repeaters, bridges, standard modems and the like are typically not included here. Note: If in use by the BAS, the Internet/building IT Network is extremely open and non-proprietary. If a vendor uses the IT Network, CI devices such as IP routers and hubs can be purchased from third parties.
Model (Device) Application
Model (Device) I3 (Intelligent Internet Innovation)
Application Communication interface device between networked IZAC controllers and an OWS (running ICMS software), thin-client, and/or 3rd party systems. Also stores/routes alarms.
Classification Server/Gateway
Proprietary IZAC network (EIA-485)
Additional Information Ports: (1) Internet, (2) EIA-485, (3) EIA-232, (2) Selectable. BACnet, LonWorks, Modbus, ARCNET, others.
Model (Device) Application
Model (Device) M202A (Master Interface Module)
Application Permits a PC (running ICMS software) to interface with the IZAC primary network. Communication interface device between networked IZAC controllers and a local PC, remote PC (via modem), or an alpha/numeric pager at up to 19.2 kbps. Also stores/routes alarms.
Classification Gateway/Router
Proprietary IZAC network
Additional Information 2 EIA-232 ports. Supports auto-answer/auto-dial
Model (Device) Application
Model (Device) M-203 (LANLink)
Application Required for every 50 controllers/nodes beyond the first 50 controllers/nodes. Also required for wire lengths exceeding 5000 feet.
Classification Repeater
Proprietary IZAC network (EIA-485)
Proprietary IZAC network (EIA-485)
Additional Information