1 – shows silo systems. Typical of most systems installed.2 – shows a basic int. system, but still a half-way house; siloed systems with a single head-end probably represent the most expensive implementation. Still have the single-system delivery/engineering, but now with the additional integration element. This is what most integrated solution are and why integration is considered more expensive. Although it does provide a single front end, often represents limited capability, not very robust whilst relying on power of PC.3 – moving to common backbone – usually IP enabling a more robust functional int. – however still siloed in its implementation – represents most common form of int. today4 – lighting into BMS - see this more today with the KNX solutions5 – finally full int. by zone. Today’s systems capable but often only partly implemented due to procurement, standards & capability6 – examples of other systems that link at the management level – server to server. Usually only implemented when specific function required – not just for a common user interface.
1 – this is the typical siloed solution, with multiple individual front ends2 – single user front end across multiple systems3 – focus only on appropriate info – that can be quickly understood4 – since the data can come from anywhere – any system - the format of the user interface must be consistent – whether it is web interfaces or main workstations - fewer user interfaces reduces s/w costs, maintenance & training - improved understanding of the system – which leads to faster response to events - easier to manage multiple users and what restrictions they have
1 – here is a simple scenario – in the event of a fire detection, a number of reactions can automatically be effected - display on a dynamic graphic to locate the event - drive the cctv camera to set presets, record pre and post event, and display live view on a monitor - over ride HVAC plant – put extract air systems into fire mode – usually this is hardwired - open nominated doors automatically – save people from using breakglasses - set lighting to fire statusWithout an intelligent int. system it is not possible to achieve this sort of C&E in a cost effective manner, and certainly not possible to make changes to the functionality in the future easily.It also provides fast level of response – much can be automatedFast pinpointing of sourceImproved diagnosis – full audit trail of the event with video footageAnd obviously improved efficiency of operation – this is a real driver for int. in retail shopping centres
1 – shows levels of a BMS, as basically defined by the ISO standards - mgmt level – typically IP where enterprise servers and workstations reside - automation level – where nc/rc reside, and local wks - field level – typically field bus RS485 or similar – connects local controllers, field devices – drives, sensors, actuators2 – these are the different types of common open protocols these provide means of integration for intelligent functional solutions, but not one meets all needs - so BACnetrecognised as good for HVAC primary plant, although it functions across all layers - LON good for sophisticated life space control – temperature, lighting control - KNX good for basic life space control, especially focused on lighting control - Modbus good for any int. to electrical systems – power distribution etcWhere as OPC, XML & SOAP are all methods to int. at the mgmt levelSo a combination of open protocols is usually needed along with a capability to int. bespoke protocols (common in the security arena).
1 – don’t just ask for int. – its lazy and you will get an over expensive response – companies trying to manage risk2 – develop a spec that defines exactly what C&E you want3 – define a platform that is still going to be here tomorrow – many s/w solution out there that have no real future development and often limited in their real capability4 – don’t specify functionality that requires significant cost – just for the sake of wanting to be different5 – if it doesn’t meet cost constraints, the construction chain will soon spot it and take advantage6 – will be challenged if you specify against a certain product7 – getting best in class not easy – time consuming and can challenge program time – but is usually worth the investigation8 – open protocols do not ensure not being tied in. Selecting product with multiple channels does9 – don’t spec a protocol or integration method – it limits the potential solutions10 – the hidden cost. They normally want to keep the packages siloed – this ruins any chance of functional int. being achieved – most M&E contractors do not like the packages being combined as this gives critical mass to the specialist – the main contractor can then procure direct with the specialist
It integration for intelligent buildings
IT integration for intelligent buildings…. a vendors perspectiveSteve Harris: UK Sales Director, Buildings Business, Schneider ElectricDate: 29th November 2011Place: De Montfort University
Contents● The Evolution of Building Systems● The Building Lifecycle● Common User Interface● The Management Control Loop● The Power of Cause & Effects● Use of Open Standards● What are the Challenges?● How can an Intelligent Building be Achieved? 2
The Evolution of Building Systems Meeting Room Booking VoIP Personnel System Lighting BMS Controller Intruder Controller Access Controller CCTV A B C D E Panel Panel HVAC Lighting HVAC Access HVAC Access HVAC Access Access Intruder HVAC HVAC Intruder Access Lighting Lighting Zone 1 Zone 2 Zone 3 3
The Building LifecycleCAPEX PHASE OPEX PHASE •Reduce Equipment Costs •Improve Operations •Reduce Installation Costs •Improve response times •Reduce Installation Times •Improve efficiencies •Reduce Risk •Reduce Complaints 4
Common User InterfaceA B C D E OR A B C D EFocus is on ensuring the user has the most appropriate information in a format that is quicklyunderstandableData can be from anywhere – from any system ● Format is consistent ● Less different types of user interface = lower software, maintenance and training costs ● Improved comprehension = faster reaction to events ● Easy to manage users 5
The Power of Cause and Effects > Fast first level response > Fast pinpointing of source of alert > Improved diagnosis > Improved efficiency of operation 6
Use of Open Standards• Fundamental to an integrated solution• Allows differing systems from different manufacturers to communicate• Can be put out to competitive bidding• Makes upgrading and enhancements easier• Less reliance on third party technical support 7
What are the Challenges?> Determining what you really want> Developing a specification> Having a platform that is future proofed> Keeping it simple> Meeting cost constraints> Getting Best Value> Getting Best in Class> Not being “tied in” for future extensions and operational support> Not getting tied into details that compromise cost and functionality> Construction chain maximising their opportunity at your expense 8
How can an Intelligent Building beAchieved? Have a clear vision… • Understand legislative restrictions and opportunities • Determine a functional vision • Get buy-in from all parties Engage experienced expertise early… • Find partners who you can trust • Develop detail designs early to ensure viability • Establish true costs to deliver and run the project Stay engaged… • Through both Construction and Operational phases • Don’t let intermediaries compromise the vision • Get the right team involved 9
Make the most of your energySMwww.schneider-electric.com/uk 10