Thursday 24 March 2011

KNX/EIBnet IP.


KNX/EIBnet IP.

In home and building electronic systems the KNX/EIB bus as well as IP networks are some of
the most important standards for the future. The definition of the EIBnet/IP standard was a
major step in the integration of both protocols into one system.

In the standard solution, an IP network connects several KNX/IP gateways to access the KNX
subsystems, enabling communication between different KNX lines via the IP backbone. But
all senders and receivers of KNX telegrams are still connected to the KNX media.

Today many devices have an Ethernet connection but cannot be controlled via KNX. To integrate
such a device into the KNX world it would not make sense to add an additional hardware
interface to the KNX/EIB bus. It would be much more convenient to establish the KNX
communication via the IP link, providing a KNX device without a connection to the KNX
medium. It may be called a virtual KNX/EIB device.
what about the configuration of such a device?
To obtain full integration into the
KNX/EIB world, the device should be programmed using the ETS software, permitting the
setting of group addresses and parameters in a closed environment.
Today many buildings are equipped with an IP network which is used mostly as a network for
personal computers. On the other hand IP networks are increasingly able to serve automation
systems. So it is obvious that this technology is an interesting solution especially for building
automation. Existing systems like the KNX/EIB bus can be linked to an IP network for use as
a fast backbone.
          
Figure 1 shows an installation with two KNX/EIB lines connected via the IP network. To link
a KNX/EIB line to the IP network a KNX/IP-Router is needed. It converts the KNX/EIB telegrams
into IP frames and vice-versa according the EIBnet/IP standard. Besides, it filters the
telegrams to keep the bus load low. An EIBnet/IP client can access any KNX subsystem via
the IP network. Due to the routing capabilities of the EIBnet/IP servers, direct exchange of the
telegrams between two servers is possible.

        
Figure 2: Virtual KNX/EIB device

Figure 2 shows the theme of this paper: We replace one line consisting of the EIBnet/IP gateway
and one KNX end device with a single component, obtaining a new device which may be
called a KNX/EIB device for IP media. The former KNX/EIB device is now only present as
a virtual device. It is visible in the complete network as a standard KNX/EIB device although
it has no conventional connection to the KNX/EIB bus.

Instead it is linked to the KNX/EIB network via the Ethernet connection and the EIBnet/IP
features of the device. When programming the virtual KNX/EIB device using the ETS, the IP
network is invisible.

Software
This chapter describes the software architecture for KNX/EIB devices for IP media. It consists
mainly of an UDP/IP stack, which handles the communication between the network and
the virtual KNX/EIB device.
Click Here to Download to Full PDF: Download Link.

HVAC Sequence of Operations


Air handling unit sequence of operations

Unlike the terminal sequence of operations, the air handling unit (AHU) sequence of operations consists of several
subsequences, so the AHU sequence of operations could be split over several controllers. The AHU sequence of operations has as attributes an airflow control subsequence and a temperature control subsequence. In addition, there is an optional filter monitoring subsequence which has Digital attributes representing differential pressure switch status and filter condition status as well as optional attributes representing filter alarm delay time and filter run time.

The airflow control subsequence has supply fan control, return fan control (optional) and minimum outdoor airflow control (optional) attributes. The minimum outdoor airflow control entity has attributes representing the minimum outdoor airflow rate, the minimum outdoor airflow setpoint, and the minimum outdoor damper control signal. The supply fan control entity, a subtype of the flow moving control subsequence, may be further classified as variable air volume (VAV). The VAV supply fan control subtype, which is also a subtype of the feedback control loop, adds the analog attributes of supply air static pressure setpoint, supply fan control signal, and a set of supply air static pressure reset requests (optional).The VAV supply fan subtype is further classified as either single or dual duct. If it is single duct, then an Analog attribute representing the supply air static pressure sensor is added. If it is dual duct, two Analog attributes representing hot and cold deck supply air static pressure sensors are added. The set of supply air static pressure reset requests is provided so that they may each be linked to the supply air static pressure reset request attribute of a terminal unit sequence of operations.
Also illustrates the return fan control, which is also a subtype of the flow moving device control sequence. The return fan control sequence may also be further classified as VAV. The VAV return fan subtype, which is also a subtype of the feedback control loop, is further classified into five subtypes as the return fan control signal is modulated to maintain the process variable listed below at a setpoint value:

• Building static pressure
• The difference between supply fan speed and return fan speed
• The ratio of return fan speed to supply fan speed
• The difference between supply air flow rate and return air flow rate
• The ratio of return air flow rate to supply air flow rate.

The temperature control subsequence consists of setpoint logic, cooling control (optional), heating control (optional), and economizer control (optional). The setpoint logic has two subtypes: single-zone setpoint control for single-zone AHUs and supply air temperature (SAT) setpoint control for AHUs that serve multiple zones. The single-zone setpoint control entity has two Analog attributes: zone temperature and zone temperature setpoint, as well as an optional setpoint reset schedule based on return air temperature (RAT). The reset sequence has a RAT attribute along with minimum and maximum zone temperature setpoints. The SAT setpoint control is classified as being either single duct, with SAT and SAT setpoint attributes, or dual duct, with cold deck SAT, cold deck SAT setpoint, hot deck SAT, and hot deck SATsetpoint attributes. The SATsetpoint control entity also has an optional SAT setpoint reset attribute. The SAT setpoint reset is abstract but there are two subtypes, one based on RAT and the other on heating and cooling requests. The RAT reset entity (the same type as the single-zone temperature setpoint reset schedule) has a RAT attribute along with minimum and maximum SAT setpoints. The heating and cooling request reset entity has sets of heating and/or cooling requests along with minimum and maximum SATsetpoints. The set(s) of heating and/or cooling requests are provided so that the elements of the set(s) may each be linked to a heating or cooling request attribute of a terminal unit sequence of operations. The
dual duct SAT setpoint control type has two optional SAT setpoint reset attributes, one for the cold deck and one for the hot deck.

The abstract economizer control subsequence has attributes representing the economizer status, economizer
control signal, minimum position, and low temperature limit
(optional). The economizer is classified into four subtypes in with the following additional attributes:

• Absolute temperature-based: outdoor air temperature and changeover temperature
• Relative temperature-based: outdoor air temperature and return air temperature
• Absolute enthalpy-based: outdoor air temperature, outdoor air humidity, and changeover enthalpy
• Relative enthalpy-based: outdoor air temperature, outdoor air humidity, return air temperature, and return air humidity.
The cooling and heating control subsequences are classified as either hydronic (chilled water for a cooling coil or hot water for a heating coil) or staged (one or more stages of refrigeration for a cooling coil and one or more stages of either electric heat or combustion furnace for a heating coil). The hydronic coil entity has a valve control
signal attribute and an optional “central plant run request” attribute. The staged coil entity has a set of on/off stage command attributes.



Central plant sequence of operations.

Chiller and boiler manufacturers often package the controls with their products, but the BAS may perform plant-level control, for example, equipment sequencing/scheduling, alarming, and possibly setpoint reset. The central plant control sequence consists of a subsequence representing the supervisory control strategy, an optional set of pump control subsequences, and an optional set of energy conversion equipment control subsequences. The supervisory control subsequence has attributes of plant type (boiler or chiller), supply temperature, supply temperature setpoint, return temperature, lockout temperature, run enable (optional), and a set of run requests (optional). The run requests are provided so that they may be linked to a boiler or chiller run request attribute of an air handling unit or terminal unit sequence of operations. The pump control subsequence is a subtype of the flow moving device control subsequence. It may be further classified as a pump feedback control subsequence, which is a subtype of both the pump control and the feedback control subsequences.

In addition, the pump feedback control entity has supply pressure, supply pressure setpoint, and pump control signal attributes along with an optional set of supply pressure setpointreset requests.

The energy conversion control subsequence is for supervisory control over a boiler or chiller with packaged local controls. It consists of the device type (derived from the central plant type), run command, lead/lag status (optional), alarm (optional), supply temperature (optional), supply temperature setpoint (optional), control signal (optional), run time (optional), and energy consumption (optional).

Lighting Control System.


Lighting Control System

A lighting control system consists of a device that controls electric lighting and devices, alone or as part of a daylight harvesting system, for a public, commercial, or residential building or property, or the theater. Lighting control systems are used for working, aesthetic, and security illumination for interior, exterior, and landscape lighting, and theater stage lighting productions. They are often part of sustainable architecture and lighting design for integrated green building energy conservation programs.
Lighting control systems, with an embedded processor or industrial computer device, usually include one or more portable or mounted keypad or touch screen console interfaces, and can include mobile phone operation. These control interfaces allow users the ability to remotely toggle (on-off) power to individual or groups of lights (and ceiling fans and other devices), operate dimmers, and pre-program space lighting levels.

·  X10 (industry standard)
·  Digital Addressable Lighting Interface
·  DMX512
·  Lonworks
·  Dynalite
·  Modbus
·  C-Bus (protocol)
·  KNX (standard)
·  MIDI
·  INSTEON

BASIC SYSTEM
A.        Lighting Control System (LCS) system shall utilize DDC to control lighting relays, dimmable ballasts, and lighting contactors as specified in the sequence of operation and in the drawings for all systems.

B.        The control system shall be fully integrated and installed as a complete package of controls and instruments in a manor that provides maximum benefit to the end user.

C.        The system shall include all computer software and hardware, control unit hardware and software, operator input/output devices, sensors, control devices, and miscellaneous devices required for complete operation and future modifications.  Documentation for all software and hardware devices shall be provided.

D.        Provide engineering, installation, calibration, commissioning, acceptance testing assistance, software programming, and checkout for complete and fully operational LCS.

SYSTEM ARCHITECTURE OF BMS


 
The system shall be implemented as an integrated, open solution, which enables Service Center
connectivity through standard Building Operating System (BOS) interface.
The System Architecture shall consist of four levels:

- Service Level
- Management Level
- Control Level
- Field Level

The system shall be completely modular in structure and freely expandable at any stage. Each level of
the system shall operate independently of the next level up as specified in the system architecture. For
example, Control Level shall operate independently without support from Management Level.
The system shall be fully consistent with the latest industry standards. To enable efficient functional
system integration and to provide maximum flexibility and to respond to changes in the building use, the
system offered shall support the use of Lon Works, Modbus, M-bus, Ethernet TCP/IP and Internet
communication technologies.

Service Level:

Service Level shall allow the systems to be connected without additional software for providing centralized remote monitoring, alarm and fault detection of connected
building management and security systems
The Service Center shall be capable of accessing remotely the systems through a standard interface
through the BAS platform. The standard connectivity shall enable providing advanced maintenance and
security services, such as security alarm monitoring, maintenance alarm monitoring, remote diagnostics,
main user capability, remote control and optimization of all systems, energy optimization, trending and
reporting services.

Management Level

Management Level shall provide a uniform view to all systems through the open Building Operating
System (BOS) platform. All the systems - controls of cooling, ventilation and lighting, consumption
measurements, access controls, intruder alarms, fire alarms and NVR/DVR systems - shall be integrated
with the BOS using device drivers.
The BOS shall offer at least the following common services to be used by all connected systems:
o Alarms
o Historical trending
o Logs and reporting
o User profile and role management
The BOS shall collect trends from defined points, collect and forward alarms from the systems. The BOS
shall enable efficient management of user rights. The BOS shall be capable of forwarding alarms to
mobile phones using SMS & E-mai, local alarm printers or to Service Center. It shall be possible to browse the
alarm history for reporting and statistical purposes.

 Control Level

The Control Level shall consist of a distributed network of smart controllers, which communicate to each
other using a commonly known field bus as specified herein. Connectivity towards Management Level
shall utilize standard TCP/IP protocol.

The controllers shall include all the intelligence of the system. All communication shall be event based,
real-time peer-to-peer communication. All controllers shall be capable of operating autonomously
independently of Management Layer. For example, all systems react to alarms on the Control Layer
without interference from upper layers.
Security controllers shall utilize RS-485 connection
between the network controller and the interface panels.

Field Level

The Field Level shall consist of industry standard sensors and actuators, industry standard
card readers and IP cameras.

Wednesday 23 March 2011

BMS / Building Automation

Building Automation Systems (BAS) optimize the start-up and performance of the heating, ventilating and air conditioning (HVAC) equipment and alarm systems. BAS greatly increases
the interaction of mechanical subsystems within a building, improve occupant comfort, lower
energy use and allow off-site building control

BAS use computer-based monitoring to coordinate, organize and optimize building control
Fuction/ sub-systems such as security, fire/life safety, etc. Common applications include :
Speciality
1. Equipment scheduling (turning equipment off and on as required)
2. Optimum start/stop (turning heating and cooling equipment on in advance to ensure the
building is at the required temperature during occupancy)
3. Operator adjustment (accessing operator set-points that tune system to changing
conditions)
4. Monitoring (logging of temperature, energy use, equipment start times, operator logon, etc)
5. Alarm reporting (notifying the operator of failed equipment, out of limit temperature/pressure
conditions or need for maintenance.

The system is DDC (Direct Digital Control) based with functions distributed both physically and functionally over the field controllers. The DDC interface, with sensors, actuators and environmental control systems, carries out various functions of energy management, alarm detection, time/event/holiday/temporary scheduling, communication interface/control and building maintenance & report generation.

These controllers are capable of functioning on a stand-alone mode, even in case of loss of communication with the central control station. We work closely with the owners and architects to install software packages into the system that are customized for the project. Other integrated packages in the system include active graphics software, energy management software, alarm indication software, maintenance package and billing software.

BASIC OF INTEGRATED BUILDING MANAGEMENT SYSTEM.

INTEGRATED BUILDING MANAGEMENT SYSTEM.

Integrated Building Management System (IBMS) is a complete information delivery system that monitors and controls a variety of systems and functions at an optimal level of efficiency.
 The System provider shall furnish and install a fully integrated Building Management System (BMS),
incorporating distributed control techniques and standard open communication networks. The system
shall be implemented as an integrated, open solution, which enables Service Center connectivity through
standard Building Operating System (BOS) interface.
The integrated systems shall include controls and monitoring of the whole building (BMS and Security)
and each room/apartment whenever applicable.

Integrated Building Management and Security Systems shall include the following subsystems:
           - BMS / Building automation (cooling/heating control, ventilation control, pumps, etc.)
           - Lighting control
           - Access control system
           - Intruder alarm system
           - Video monitoring system
           - Fire alarm system
           - Central battery system.