The following are important considerations to keep in mind durring the planning phase of an integration project using S4 Open products to integrate legacy building automation systems to open standards. If you need assistance with planning your project, drop by the forum and post a question. We'd be happy to help!
|
|
There are two options for dealing with legacy N2 devices in an integration. Both represent long-term strategies that each have their benefits, present both options to the facility manager and select the option that works best for them.
Phase Out Legacy N2 Field Devices
-
Benefit: Cost of upgrading can be distributed over any length of time
-
Replace HMI with BACnet or OPC based solution
-
Gradually replace Legacy equipment with new solution
-
Transitioning to new equipment is seamless
-
Unplug N2 Router when upgrade is complete
Salvage Legacy N2 Field Devices
-
Benefit: Leverage existing infrastructure
-
Replace HMI with BACnet or OPC based solution
-
Merge legacy buses if desired
-
Manage new and existing equipment from one interface
|
|
The legacy supervisory controller can be removed completely if the new head end can perform the following: - Occupied / Unoccupied schedules. The N2 field devices normally do not include a time clock so they completely rely on the head end for scheduling activities.
- Trending and logging activities.
- Global Variable support. For example, an outside air temperature sensor on one N2 device may be shared with other N2 devices on the same N2 bus or with N2 devices on other Metasys networks.
- Custom logic coded into the NCM or other supervisory controllers with GPL, JC Basic, or other languages.
If the new head end meets the above criteria and the legacy supervisory controller is removed the S4 Open appliance will act as bus master. |
|
|
|
|
|
Loading Poll...
Products 
