intellignet buildings

7/29/2019 Intellignet Buildings

1/70

Communication protocols EIBUS Anexample

Intelligent Buildings Technology


2/70

Communication protocols EIBUS Main networks The Installation Bus is designed to provide distributed technical control for

management and surveillance of buildings.

Therefore it provides a serial data transmission between the devices connectedto the bus. It also operates as a compatible, flexible low-cost system supportingthe above applications.



3/70

Communication protocols EIBUS Main networks The Installation Bus is designed to provide distributed technical control for

management and surveillance of buildings.

Therefore it provides a serial data transmission between the devicesconnected to the bus. It also operates as a compatible, flexible low-costsystem supporting the above applications.

DecentralizedCentralized



4/70

Communication protocols EIBUS



5/70

Communication protocols EIBUS Topology The EIB installation bus is a twisted-pair that is laid parallel to the

mains power supply network. The Bus Line interconnects allsensors and actuators of an installation together.

Sensors are command initiators such as switches and

pushbuttons. Other types of sensors include temperature sensors,brightness sensors etc. Actuators are command receivers such asluminaries, blinds, heating, door openers etc.

On each Bus Line up to 64 devices can be operated. Up to 12such Bus Lines can be joined together with a Line Coupler to formone Bus Area. Up to 15 such Bus Areas can in turn be connectedby means of an Area Coupler.



6/70

Communication protocols EIBUS Topology EIB is a fully peer-to-peer network, which accommodates up to

65536 devices.

The logical topology allows 256 devices on one line.

Lines may be grouped together with a main line into an area.

15 areas together with a backbone line form an entire domain.

On open media, nearby domains are logically separated with a 16-bitSystemID.

Without the addresses reserved for couplers, (255 x 16) x 15 + 255 =61.455 end devices may be joined by an EIB network.

Installation restrictions may depend on implementation (medium,transceiver types, power supply capacity) and environmental(electromagnetic noise) factors. Installation and product guidelinesshould be taken into account..



7/70

Communication protocols EIBUS Topology



8/70

Communication protocols EIBUS Topology



9/70

Communication protocols EIBUS Media Several media, like Twisted Pair, Powerline, Radio Frequency and

Infrared, today support the EIB protocol. It is of course always possible toconnect gateways to other media.

On EIB TP (Twisted Pair), bit-level collision detection with dominant logical0 ensures that in case of collision, the transmission always succeeds for

one of the communication partners. The resulting elimination of re-transmissions further enhances the performance of EIB TP. Together withEIB's powerful group addressing, EIB TP1 Collision Avoidance caters forextreme efficiency with reaction times 100 ms for two simultaneoustransmissions. Fast polling allows up to 14 devices to be polled for 1 bytestatus-information within 50 ms. A physical TP segment may be up to1000 m long.

The electrical segments can have an arbitrary topology (i.e. linear, star,tree, loop or combinations of them) consisting of individual wiring sectionsas long as the electrical requirements (resistive and capacitive length) arenot exceeded. Examples of such topologies of electrical segments areshown in Figure.



10/70

Communication protocols EIBUS Transmission The communication between a sensor (e.g. a switch) and an actuator

(e.g. a lamp) is a sequence of operations (see Fig. 3.12). In the caseof the EIB protocol, a switch - being uniquely defined by its physicaladdress - can communicate to lamps using group addressing.

The group addressing is based on the exchange of data coded withcommon rules between communication objects (mailboxes). Acommunication object is only able to transmit telegram on a singlegroup address. On the opposite side, a communication object can besubscriber to several group addresses, allowing it to receive telegramfrom different emitters. That means all EIB Bus devices subscribers tothe right group address (i.e. our lamp) will receive the commandmessage from the switch.



11/70

Communication protocols EIBUSTransmission



12/70

APPLICATION

PRESENTATION

SESSION

TRANSPORT

NETWORK

DATA LINK

PHYSICAL

APPLICATION

----

----

TRANSPORT

NETWORK

DATA LINK

PHYSICAL

Communication protocols EIBUSOSI



13/70

Communication protocols EIBUSProtocol The information exchange between two devices is

achieved by transmission of data packets.

Each data packet must be acknowledged. For every

medium, the message frame is similar to:

Message frame



14/70

Communication protocols EIBUSProtocol Some media will precede or follow this message by some

medium specific sequences, characteristic for themedium's access control or error correction mechanisms.The data packet contains the following fields:

control field. source address field.

destination address field.

length.

LSDU (Link Service Data Unit), i.e. info to betransferred.

check byte. Data packet



15/70


Data management and addressing To manage network resources (e.g. when configuring an installation), EIB uses a combination

of broadcast and point-to-point communication. Via broadcast (optionally using a device'sunique serial number), each device in the installation is assigned a unique Physical Address,which is used from then on for further point-to-point communication.

A connection (optionally with access authorization) may be built up, for example to downloadthe complete 'applet' binary image of an application program.

Management of EIB Bus devices connected to the Installation Bus can be addressed usingtwo modes:

Physical addressing (system operation)

Group addressing (normal operation).



16/70


Data management and addressingPhysical

Group



17/70

Communication protocols EIBUSConfiguration

Configuration of the bus system is achieved using the EIBTool Software developed by the EIBA.

The location and physical address of each bus device isentered in the architectural drawings.

When an installation is complete, a serial interface from apersonal computer configures the EIB system.



18/70

Communication protocols EIBUSRehabiliation

The EIB bus is well suited to exploitation in the rehabilitation field

for the following reasons:

Availability of commercial products.

Technology is open to third parties for exploitation.

Development kits are available.

Established network of training centres.

The major drawback of the EIB bus is that the technology has so

far only been applied in great measure to the twisted pair medium.This implies that if an existing home is to receive an EIB bus, a

certain amount of re-wiring will need to take place. However, the

technology can be applied to other media and products do exist

for Infrared and Power Line media. The EIBA is also carrying out

development for the coaxial cable, optical fiber and radio

frequency mediums.



19/70

Communication protocols EIBUSInternetworking

The EIB protocol does not communicate to communicate.

The aim of communication is the interworking between sensors and

actuators.

The interworking pyramid, defines the different interworking degrees.

It starts with the data format used and ends with the application

functionality.

It can be compared to a mail exchange where the communication

object is the mailbox and the functionality the complete written order.



20/70

Communication protocols EIBUS ComponentsEIB devices are divided into three types according to their use:

Basic components, such as power supply unit (PSU), choke,signal filter.

System components, which support the basic operation of thesystem such as Bus Coupling Unit (BCU), Line Coupler (LC),Phase Coupler, Repeater

EIB devices that are dedicated to applications such as sensors,actuators, IR-decoders, display panels. A Bus Coupling Unit orsimilar interface connects these types of devices to EIB.



21/70

Communication protocols EIBUSComponents



22/70

Communication protocols EIBUSComponents

The definition of the various parts are:

Power Supply Unit (PSU): Provides power for feeding of EIB Bus devices (Safety

Extra Low Voltage (SELV), 30 V DC nominal). Choke: Provides the coupling of the Power Supply Unit to the data bus line.

Data rail: Mounted support with four tracks to distribute the bus onto DIN rail.

Data rail connector: Provides the connection between the bus cable and the datarail.



23/70

Communication protocols Lonworks Local Operating Network Technology is a universal, open standard

networking platform created by Echelon Corporation for networks control.

A LonWorks control network is any group of devices working together tomonitor sensors, control actuators, communicate reliably using an openprotocol, manage network operation, and provide local and remote access

to network data. In some ways, a LonWorks control network resembles a data network,such as a LAN (local area network).

Data networks consist of computers attached to various communicationsmedia, connected by routers, which communicate to one another using acommon protocol.

Network management software allows administrators to configure and

maintain their computer systems. Control networks contain similar pieces optimized for cost, performance,

size, and response characteristics of control.

They allow networked systems to extend into a class of applications thatdata networking technology cannot reach.



24/70

Communication protocols Lonworks Like the computer industry, the control industry was, and in many cases is, creatingcentralized control solutions based on point-to-point wiring and hierarchical logicsystems.

This meant that there is a "master" controller, like a computer or programmable logiccontroller, physically wired to individual control, monitoring and sensing points, or"slaves."

The net result worked, but was expensive and difficult to maintain, expand, andservice.

It was also very expensive to install especially for retrofitting.

Before LonWorks control networks, most control systems required thousands of feet- even miles - of expensive wiring to connect dumb components to a custom-programmed central controller.

Expansion required costly rewiring and custom programming. The systems werevulnerable to failure of the central controllers.

LonWorks control networks improve this scenario. They allow simple expansion bymerely plugging in new interoperable devices that work together, regardless of themanufacturer. The devices communicate using an open protocol, the LonTalkprotocol. By distributing processing among all of the control devices, the centralpoint of failure is eliminated. By allowing for free flow of information betweendevices, control is improved and new applications are enabled.



25/70

Communication protocols Lonworks LonWorks technology nowadays provides a solution to the many

problems of designing, building, installing, and maintaining controlnetworks: networks that can range in size from two to 32,000devices and can be used in everything from supermarkets topetroleum plants, from aircraft to railway cars, from fusion lasers toslot machines, from single family homes to skyscrapers.

In almost every industry today, there is a trend away from proprietarycontrol schemes and centralized systems. Manufacturers are usingopen, off-the-shelf chips, operating systems, and parts to buildproducts that feature improved reliability, flexibility, system cost, andperformance.

LonWorks technology is accelerating the trend away from proprietarycontrol schemes and centralized systems by providinginteroperability, robust technology, faster development, and scaleeconomies.



26/70

Communication protocols Lonworks network A LonWorks network consists of a number of nodes communicating

over a number of media using a common protocol. The main parts ofthe network are :

The nodes, which are intelligent devices, that "talk" via the communicationprotocol assuring their interoperation and interaction.

Network equipment (Router, Repeater, Gateway and PC cards, Router/Modem). Transceivers (TP, Power lines, IR, RF, FO). PC or microprocessor communications software (DDE or MIP). Configuration, management, supervision and maintenance software.



27/70

Communication protocols Lonworks network



28/70

Communication protocols Lonworks network



29/70

Communication protocols Lonworks networkThe main advantages of the LonWorks network are:

It is a distributed control network.

Easier integration of different devices (sensors, actuators, controllers, etc.) fromvarious manufacturers is achieved.

Higher performance due to peer-to-peer communications is ensured. Reduced costs of installation and reconfiguration due to its distributed

characteristics.



30/70

Communication protocols Lonworks protocol The LonWorks protocol, also known as the LonTalk protocol and the

ANSI/EIA 709.1 Control Networking Standard, is the heart of the LonWorkssystem.

The protocol provides a set of communication services that allow the

application program in a device to send and receive messages from otherdevices over the network without needing to know the topology of thenetwork or the names, addresses, or functions of other devices.

The LonWorks protocol can optionally provide end-to-end acknowledgementof messages, authentication of messages, and priority delivery to providebounded transaction times.

Support for network management services allow for remote network

management tools to interact with devices over the network, includingreconfiguration of network addresses and parameters, downloading ofapplication programs, reporting of network problems, and start/stop/reset ofdevice application programs.



31/70

Communication protocols Lonworks protocol



32/70

Communication protocols Lonworks protocol OSI

The LonWorks protocol is a layered, packetbased, peer-to-peercommunications protocol. Like the related Ethernet and Internetprotocols, it is a published standard and adheres to the layered

architectural guidelines of the International Standards Organization (ISO)Open Systems Interconnect (ISO OSI) reference model.

The LonWorks protocol, however, is designed for the specificrequirements of control systems, rather than data processing systems. Toensure that these requirements are met with a reliable and robustcommunications standard, the LonWorks protocol is layered asrecommended by the International Standards Organization.

By tailoring the protocol for control at each of the OSI layers, theLonWorks protocol provides a control-specific solution that provides thereliability, performance, and robust communications required for controlapplications.



33/70

Communication protocols Lonworks protocol Channel

A channel is a specific physical communication medium (such as twistedpair or power line) to which a group of LonWorks devices are attachedby transceivers specific to that channel.

Each type of channel has different characteristics in terms of maximumnumber of attached devices, communication bit rate, and physicaldistance limits.



34/70

Communication protocols Lonworks protocolAddressing

The addressing algorithm defines how packets are routed from a sourcedevice to one or more destination devices.

Packets can be addressed to a single device, to any group of devices, or

to all devices. To support networks with two devices to tens of thousands of devices, the

LonWorks protocol supports several types of addresses, from simplephysical addresses to addresses that designate collections of manydevices.



35/70

Communication protocols Lonworksprotocol Addressing Physical Address. Every LonWorks device includes a unique 48-bit

identifier called the Neuron ID. The Neuron ID is typically assignedwhen as device is manufactured, and does not change during thelifetime of the device.

Device Address. A LonWorks device is assigned a device addresswhen it is installed into a particular network. Device addresses areused instead of physical addresses because they support moreefficient routing of messages, and they simplify replacing faileddevices. A network installation tool that maintains a database of thedevice addresses for the network assigns the device addresses.Device addresses consist of three components: a domain ID, subnetID, and node ID. Devices must be in the same domain to exchangepackets. There may be up to 32,385 devices in a domain. Thesubnet ID identifies a collection of up to 127 devices that are on asingle channel, or a set of channels connected by repeaters. SubnetIDs are used to support efficient routing of packets in large networks.There may be up to 255 subnets in a domain. The node ID identifiesan individual device within a subnet.



36/70

Communication protocols Lonworksprotocol Addressing Group Address. A group is a logical collection of devices within a

domain. Unlike a subnet, however, devices are grouped togetherwithout regard for their physical location in the domain. There maybe any number of devices in a group when unacknowledgedmessaging is used; groups are limited to 64 devices if acknowledgedmessaging is used. Groups are an efficient way to optimize networkbandwidth for packets addressed to multiple devices. There may beup to 256 groups in a domain.

Broadcast Address. A broadcast address identifies all devices with asubnet, or all devices within a domain. Broadcast addresses are anefficient method to communicate with many devices, and aresometimes used instead of group addresses to conserve the limitednumber of available group addresses.



37/70

Communication protocols Lonworks protocolDelivering

The LonWorks protocol offers three basic types of message delivery service and alsosupports authenticated messages. An optimized network will often use all of these services.These services allow tradeoffs between reliability, efficiency, and security, and are listedbelow:

Acknowledged Messaging. Provides for end-to-end acknowledgement. When using

acknowledged messaging, a message is sent to a device or group of up to 64 devices andindividual acknowledgements are expected from each receiver. If acknowledgements are notreceived, the sender times out and retries the transaction. The number of retries and thetimeout are both configurable.

Repeated Messaging. Causes a message to be sent to a device or group of any number ofdevices multiple times. This service is typically used instead of acknowledged messagingbecause it does not incur the overhead and delay of waiting for acknowledgements. This isespecially important when broadcasting information to a large group of devices, as anacknowledged message would cause all the receiving devices to try to transmit a response

at the same time.Unacknowledged Messaging. Causes each message to be sent once to a device or groupof any number of devices and no response is expected. This messaging service has thelowest overhead and is the most typically used service.

Authenticated Service.Allows the receiver of a message to determine if the sender isauthorized to send that message. Thus, authentication prevents unauthorized access todevices and is implemented by distributing 48-bit keys to the devices at installation time.



38/70

Communication protocols Lonworks protocol Variables

The LonWorks protocol implements the innovative concept of networkvariables.

Network variables greatly simplify the tasks of designing LonWorksapplication programs for interoperability with multiple vendors' products

and facilitating the design of information-based, rather than command-based, control systems.

A network variable is any data item (temperature, a switch value, or anactuator position setting) that a particular device application programexpects to get from other devices on the network (an input networkvariable) or expects to make available to other devices on the network(an output network variable).

The application program in a device does not need to know anythingabout where input network variables come from or where output networkvariables go.



39/70


When the application program has a changed value for an output networkvariable it simply passes the new value to the device firmware.

Via a process that takes place during network design and installationcalled binding, the device firmware is configured to know the logical

address of the other devices or group of devices in the network expectingthat network variable, and it assembles and sends the appropriatepackets to these devices.

Similarly, when the device firmware receives an updated value for aninput network variable required by its application program, it passes thedata to the application program.

The binding process thus creates logical connections between an outputnetwork variable in one device and an input network variable in anotherdevice or group of devices.

Connections may be thought of as "virtual wires." If one device contains aphysical switch, with a corresponding output network variable calledswitch on/off, and another device drives a light bulb with a correspondinginput network variable called lamp on/off, creating a connection by bindingthese two network variables has the same functional effect as connectinga physical wire from the switch to the light bulb.



40/70


Every network variable has a type that defines the units, scaling, and structure ofthe data contained within the network variable. Network variables must be thesame type to be connected. This prevents common installation errors fromoccurring such as a pressure output being connected to a temperature input.

Type translators are available to convert network variables of one type to anothertype. A set of standard network variable types (SNVTs) is defined for commonlyused types. Alternatively, manufacturers may define their own userdefined networkvariable types (UNVTs).

Network variables make possible information-based control systems, rather thanold-style command-based control systems. This means that in a LonWorkssystem, each device application makes its own control decisions, based oninformation it collects from other devices about what is going on in the system.

In a command-based system, devices issue control commands to other devices,so a command-issuing device, that is typically a centralized controller, must becustom programmed to know a lot about the system function and topology.

This makes it very difficult for multiple vendors to design standard control devicesthat can easily be integrated. Network variables make it easy for manufacturers todesign devices that systems integrators can readily incorporate into interoperable,information-based control systems.



41/70

Communication protocols Lonworksprotocol Devices



42/70

Communication protocols Lonworks protocolDevice

The basis of every LonWorks device is the Neuron Chip as it contains theentire required device hardware and software. The Neuron Chip containsthree identical 8-bit central processing units (CPUs) that are dedicated to thefollowing functions:

1. CPU-1 is the media access control, which drives thecommunication subsystem hardware and executes the media accessalgorithm. CPU-1 communicates with CPU-2 using network bufferslocated in shared memory. CPU-1 handles layers 3 to 6.

2. CPU-2 is the network CPU that implements layers 3 through 6 ofthe LonTalk protocol. It handles network variable processing,addressing, transaction processing, authentication and network

management.3. CPU-3 is the application CPU that runs code written by the usertogether with the operating systems services called by the applicationcode.



43/70

Communication protocols Lonworksprotocol Device



44/70

Communication protocols Lonworksprotocol Device

Neuron

Chip



45/70

Communication protocols Lonworksprotocol LonPoint

The Lon Point system is the result of such a systems approachproviding the low cost of an open system architecture, the multiusercapabilities of the LNS Network Operating System, the distributedprocessing capabilities of the Neuron Chip and Lon-Works platform

and the wiring flexibility of free topology communications. The system consists of the LonPoint Interface, Router and Scheduler

Modules, Lon-Point Application Programs, LNS-based LonMaker forWindows Integration Tool, and the LonPoint Software Plug-In. Thevarious I/O modules of the LonPoint system are described next.



46/70

Communication protocols Lonworksprotocol LonPoint



47/70

Communication protocols Lonworks protocolLonPoint



48/70

Communication protocols Lonworks protocolLonMark objects

The LonMark Association is an organization aiming at enabling the easyintegration of multi-vendor systems based on LonWorks networks andproviding an open forum for member companies to work together on

marketing and technical programs to promote the availability of openinteroperable control devices. The Association is focusing on:

Promoting benefits of interoperable LonMark products.

Providing collaborative marketing programs for companies developing Lon-Mark products.

Providing a forum to define application-specific design requirements.

Products that have been verified to conform to LonMark interoperabilityguidelines are eligible to carry the LonMark logo. The LonMark logo is anindicator that a product has completed the conformance tests and has beendesigned to interoperate across a LonWorks network.



49/70

Communication protocols Lonworks protocolLonMark objects As mentioned above the LonTalk protocol employs a data oriented

application layer that supports the data communication rather thancommands between nodes. By this approach application data such astemperatures, pressures, etc can be sent to multiple nodes, each of which

may have a different application for that datum. The data in the LonTalkprotocol are called the network variables and configuration properties.Standard Network Variable Types (SNVTs) and Standard ConfigurationParameter Types (SCPTs) provide a common platform for representing awide range of data by specifying units, range and resolution.

At the application layer, interoperability between LonWorks technology-based products is facilitated through the use of application-specific LonMarkObjects and SNVTs. LonMark Objects build upon network variables andprovide a concise application layer interface that incorporates semanticmeaning about the information being communicated.



50/70

Communication protocols Lonworks protocolLonMark objectsThere are three types of LonMark Objects:

The Node Object, the Sensor Object and the Actuators Object.

The Sensor Object is a generic object that can be used with any form of sensor, such asanalog pressure, temperature or humidity sensor or even a digital switch. The Sensor

Object can supply data directly to an Actuator Object or to control loop located within aController Object. There are two versions of the Sensor Object: one with no feedbacknamed the 'Open Loop Sensor Object' and the other with feedback named the 'ClosedLoop Sensor Object'.

The Open Loop Sensor Object is suitable for use with sensing devices that reportabsolute rather than relative values and for use with devices that do not requirefeedback information for correct operation.

The Closed Loop Sensor Object includes a feedback feature that makes it suitable for

use in applications where multiple sensors can be combined in arbitrary combinationswith multiple actuators devices. The purpose of the closed loop sensor object is toenable multiple sensors to control a common actuator or a single sensor to controlmultiple actuators while retaining synchronization between the actual and desired statesof objects in both the sensors and actuators.



51/70




52/70




53/70

Intelligent Buildings

Technology

Smart Buildings Evaluation

Tool


54/70

Intelligent Building - Typical buildingsenergy usage



55/70

Steps for an effective indoor environment andenergy management program:

Obtain total management commitment. Obtain employee cooperation. Conduct an energy survey. This is the "Building Audit" which identifies

building characteristics, energy uses in the building, and how much energyis consumed.

Identify problems and solutions. Use information gathered in the audit aswell as your knowledge of building conditions, and check the appropriateEnergy Conservation Opportunities.

Set conservation goals. Establish a goal in terms of percent reduction Keep consumption and indoor comfort records.

Implement changes.Monitor results.

Make appropriate adjustments. Based on monitored results, takeappropriate steps to implement any necessary adjustments required bychanging conditions.



56/70

Evaluating Intelligent Buildings Matrix ToolThis matrix tool takes into account the following three

elements (criteria):

The built environment should be productive, safe, healthy,thermally, aurally and visually comfortable.

The building has potential to serve future generations:

sustainability, or adaptability over the life cycle of the

building and safeguarding the earth and environmentresources.

Financial aspect: the building can be built within some

cost constraints whilst retaining market value.



57/70

Evaluating Intelligent Buildings Matrix Tool -PIs

The performance indicators selected are:

Built Environment

Responsiveness

Functionality

Economic issues Suitability



58/70

Evaluating Intelligent Buildings Matrix Tool -PIs Built Environment which consists of the following sub-

performance indicators: Comfort and productivity: at what level that the building creates a

comfort environment for the occupants

Individual control of local environment: can individual occupant changethe set-point of their terminal devices such as fan-coil unit or solarshedding devices

Health and safety: is it safe and health for people to stay in or aroundthe building

Energy consumption and environmental impacts: is there anorganisational policy on the operation of the built environment and theassociated environmental impacts

Integration with the surrounding ecological systems: how are decisionmade during the design phase regarding to macro-climatic design,

building integrated renewable energy sources and rainwater/wastewaterutilisation.



59/70

Evaluating Intelligent Buildings Matrix Tool -PIs Responsiveness

Awareness: how well the relevant people understand theirrelationship with the building

Automatic response to changes in the surroundings: is thereany measures that allow the building appropriately respondsto the changes in the surroundings, utility supply, servicessystems and usage of the buildings.

Performance under emergencies: what level ofemergencies can be handled within and around the building

Decision-making: the ability of building operators to makedecisions in responding to changes

Flexible usage: is it flexible to alter the partitions, layouts

and services systems for different usage.



60/70

Evaluating Intelligent Buildings Matrix Tool -PIs Functionality

Reporting system: how well the information associated withthe efficient management and operation of the building is

communicated to the relevant parties. Building Management System (BMS): is there a BMS

installed and how is it being used.

Maintenance: how the building, including architectural

features, BMS (if any), and services systems, is maintained. Facility Management (FM): is there a facility manager or

management team and how technically competent are they.

Easy-to-use through design: how the issues related to the

ease of use is considered in the design phase.



61/70

Evaluating Intelligent Buildings Matrix Tool -PIs Economic issues

Investment: are the intelligent building technologies arevalued by the relevant decision makers

Energy supply: how easy (or difficulty) is it to change thesupply of energy

Resources (water, waste treatment, etc): how energy audit,monitoring of water usage, and waste treatment are carried

out Costs: how the operating cost associated with energy and

other utilities are paid by tenants

Budget: what procedure is employed to determine the ratioof the initial construction cost to the lifecycle cost



62/70

Evaluating Intelligent Buildings Matrix Tool -PIs Suitability

Special use: does the building provide features to satisfy special needsof some individuals such as the disabled or elderly.

IT connectivity: does the building have access to specialist servicesproviders through IT network.

Location: is the building located such that the activities within thebuilding have easy access to the relevant sources

Organisation: is there an appropriate communication between differentdivisions of an organisations that allow effective dissemination of

information associated with efficient operation of the building Internal flow and operational planning: what process or method are

employed in the design phase to make decisions associated with thelocation of interacting divisions in the building and the movements ofstaff and information.



63/70

Evaluating Intelligent Buildings Matrix Tool -FactorsThese performance indicators are influenced by a number of factors. This Matrix Tool

only consider the five factors, as follows:

1. People Do they feel comfort and are they productive in the building

How well do they understand their relationship with the building

Do they have a role in the energy management

Investment decision-makers: do they understand the benefit of intelligent buildingtechnologies and are they willing to investigate the feasibility of relevant investment

People with special needs (such as the disabled and elderly): can the building satisfy theirspecial needs

2. Building systems Does the system provide facilities for individuals to change the set-point of local devices

according to their desire

Are the building and its systems well integrated with the surroundings Is the building controlled and managed by a Building Management System (BMS)

Is it technically feasible to change the suppliers of utilities when considered beneficial

Does the building have good access to the internet.



64/70

Evaluating Intelligent Buildings Matrix Tool -Factors3. Critical

What measures are there to ensure the safety and health of people staying in and around the building

Facilities equipped to handle emergencies

Maintenance and services of the facilities equipped to handle emergencies

Treatment of the waste and use of renewable energy sources

The factors associated with the location of the building that affect the performance of the building under

emergencies4. Process

The process of adapting energy management policies within the organisations

The technical competence of the building operators in dealing with any relevant change

The technical competence of the facility managers

Facilities for individual tenants to control and meter their utilities

Organisational regime of dealing with energy related issues

5.

Design Design considerations and decisions on the integration of the building and its systems with thesurroundings

Design considerations and decisions on possible change of partitions, layout and services systemsrequired by the change of usage

The use, operation and maintenance of building systems

Decision on the initial and lifecycle costs

Urban and building internal planning



65/70

Evaluating Intelligent Buildings Matrix Tool


Special Needsof Users

Connectibility(C.I.B.)

Location OrganisationInterior

Operations(Flows)

SUITABILITY

InvestmentPower Supply

&

Fuel Options

OverallResource

Management

Cost

Centres

Construction/Rent

Cost

ECONOMIC

ReportingBuilding

ManagementSystem

MaintenanceFacilitiesManager

Easeof Use

FUNCTIONALITY

AwarenessAutomated

ComponentsEmergency

DevolvedDecisionMaking

Spacial RESPONSIVENESS

ComfortLocal

InterfaceHealth Policy Sustainability

BUILTENVIRONMENT

PEOPLE SYSTEMS CRITICAL PROCESS DESIGN


66/70

Evaluating Intelligent Buildings Matrix Tool Each of the performance indicators has a value ranging from 0 to 5, with 5 indicatingthe best and 0 indicating the worst. Once these individual performance indicators areassessed against the relevant building features, the overall performance iscomputed as below:

where:

are the value of individual performance indicators: Built Environment,Responsiveness, Functionality, Economic and Suitability respectively.

are respectively the weighting factors for individual performanceindicators .

And:

The value of IQ specifies the intelligence of a building under the Matool. The

maximum value of IQ is 125. The rating of the intelligent building is accordinglyspecified as follows: Bad:


67/70

Evaluating Intelligent Buildings Matrix Tool -AssessmentThe assessment comprises three stages:

Stage 1 : to determine the

weighting factors

Stage 2 : to assess all relevant

individual performance indicators

Stage 3 : to compute the overall

performance based on the weighting scheme determinedin stage 1 and the value of individual performance

indicators determined in stage 2.


I lli B ildi T h l


68/70

Evaluating Intelligent Buildings Matrix Tool -Assessment


Built Environment (PE)

Responsiveness (PR)

Functionality (PF)

Economic (PE)

Suitability (PS)

(gE)

(gR)

(gF)

(gE)

(gS)

Weighting Factors for individual PI Weighting Factors for Overall PI

Stage 1: Assessment scheme

Stage 2: Individual PI Stage 3: Overallassessment

Overall

Intelligence of

thebuilding

(IQ)

I t lli t B ildi T h l



69/70



0.0

1.0

2.0

3.0

4.0

5.0

6.0

Built Environment

Responsiveness

FunctionalityEconomy

Suitability

People

SystemCritical

Process

Design




70/70

BuiltEnvironment

Responsiveness

Functionality

Economy

Suitability

People

System

Critical

Process

Design

4.0-5.0

3.0-4.0

2.0-3.0

1.0-2.0

0.0-1.0



intellignet buildings

Documents