(WS14) Goran Đoreski - Važnost stakla, bakra i čelika
Fer Presentation Hr
1.
2. Ciljevi : - Upravljanje zgradama - Upravljanje prostorom - Upravljanje poslovanjem Ciljevi : - Smanjenje utjecaja na okolinu - Efikasno korištenje resursa - Ekološka prihvatljivost - Osiguranje zdrave okoline I nformacijske T ehnologije O drživost - Životni ciklus zgrade - Efikasni sustav u zgradi - Efikasno upravljanje & korištenje - Integracija I nteligentni G radovi I nteligentne Zgrade (IB) Zelene Zgrade (GB) Pravi presjek je efikasnost!
3. Vlasnici & Društveni zahtjevi Uredska op. Inicijalna cijena Godišnja cijena TCO Grijenje Rasvjeta Hlađenje Vršna opterečenja Hlađenja Vršna opterečenja hlađenja Chiller veličina Energija , Vršne potrebe , oblikovanje opterećenja Proizvodnja energije na lokaciji Centralna proizvodnja energije
4. Što su u stvari izazovi? Večina zgrada postoji ! Te hnologija postoji ! Znanje i sposobnost rješavanja problematike također postoji ! ROI Komfor Životni vijek DESIGN Energija Održavanje Održivost
5.
6.
7.
8.
9.
10. Što doista očekujemo od BrightCore? Separaciju “ što ” je isporučeno servisom od “ kako ” je isporučeno . Primjer : ATM - Automatic Teller Machines • tisuće različitih tipova, lokacija, veličina, itd... Jedan osnovni servis : Izdavanje gotovine . Jedan osnovni standard : Bankovna kartica . • Korisnik nezna i ne zanima ga kako ATM radi , dok god kad stavi karticu u njega dobiju gotovinu. Primjena ove jednostavane ideje na naše aplikacije. • ATM = Software Aplikacija ( Isporučilac servisa ) • Gotovina = Podaci • Kartica = Transakcijski protokol • Korisnik = Druga softverska aplikacija ( Korisnik Servisa )
13. Multi Building Servisno orijentirana infrastruktura
14.
15. Rezultati dialoga – kako upravljati zgradom!! Gospodarske ekonomske mogućnosti povezane s kontrolom energije, energetskom efikasnošću, ubrzati će održivost te samim time i rast. t end t start P t P t t max Q=P max *t max Q= P (t) dt t end t start
16.
17. Jasna slika - BrightCore Klienti Upravljački data center Objekt Objekt
18. Potpuno asinkrona mrežna struktura ObjectCore BrightNode BrightNode BrightNode BrightNode Building 1 Building 2 Building 3 Building 4 FMS BrightLet ERP BrightLet ICT ICT ICT ICT ICT ICT BrightLet
20. Nije postrednička komunikacija s Lo kalnom K ontrol nom Mrežom BrightNode je jednaki par član k ontrol ne Mreže Zgrada 1 Core
21. Povijest LonWorks – Vrijeme adaptacije Market Adoption 1990 ... 2010 More than 100 million installed products Standards Adoption EU – Buildings, Gas Stations, Home Appliances NA – Homes, Buildings, Trains, Freight Trains Semiconductor Manufacturing Asia – Buildings, Controls, Homes Standardized as ANSI/CEA-709.1-B Became more commonly known as LON® technology or simply LON LonMark International The LonWorks® Platform
22. “ Multivendor Lo c al Operating Network ” Control Infrastructure –Globalna prisutnost 2% Liftovi 9% Rasvjeta 4% Sistem Integratori 14% Vatrodojava 16% Procesna automatika 7% Uredska automacija 2% Potršačka roba 6% Benzinske pumpe 41% HVAC 8% Elektrane 6% Promet 2% Zdravlje 6% Edukacija 2% Telekom
24. Oslobađanje infrastru k ture od kaveza signal a , variabl i , proto k ol a .... Rasvjeta HVAC Domain Expertiza Kontrol Domain Expertiza I C T Domain Expertiza
Good afternoon my name is Nino Kurtalj, I am the president of Elma Kurtalj Company, I will present you today our BrightCore product family. Basically it is a story from Silos to open system!!!
Some where by the end of 90, I start to understand that the automation technology in buildings will follow the way what we have been seeing in ICT industries, those days !!! Generally this is a picture which emerge from all information available in beginning years of this century. When we really look on this picture we see that real intersection is efficiency !! If we go out from the building system we find ourselves in the area Intelligent city!
W e found ourselves in front of general request: - How to reach with building TCO structure model similar to ICT equipment model . How to be able to escape from Vendor Lock ( as much as possible) Generally how to take control!!! How to clarify hidden expenses ??
Therefore, we ask ourselves a question!!! What are the real issues ? Why it is so complicate to reach ICT scenarios with BA? Everything is here! We should be able to easy establish: - Life cycle expenses control, as well a s - T otal image of the building from the user and society stand point!
From stand point of Decision Makers we understood What they do not won't to know, and what they would like to know !! They are not interested in “DATA ”
They are not interested in “Information flow processes ” It is not something what the care of f ! This is technology, why should we know how it works???
Technical analyses, solutions to the problems; this is operations!!! This is not Decision Makers ground too!
Keeping thing working; This is again operations; We do not know that ether!!!
But total financial behavior of the system in time: - metrics, NPV, IRR These kind of data we would like to know!!! So, that is the BrightCore should simply open application to infrastructure dialog !
Then we ask ourselves how product should behave ! How, users should handle the product as well applications! We understood from experience , the system has to behave as ATM machine. User should have standard services for there needs . Simple and easy communication with the system !
Open application to infrastructure dialog? This is opening possibility to similarly threat building processes as we treat business processes!!! WOW, Complete different controllability! Precise financial tracking of the event!! Real time financial monitoring of event in maintenance and energy!!! All that fit into essence of real estate business!!
BUP Simply ! W e should create an open service oriented architecture , which will connects from one side networks (BA languages ) with on the another side application and services .
Furthermore, we understood the need for multi building service oriented architecture . Why?? Simply , because of efficiency in servicing, billing, upgrading,
During the establishment of the BrightCore framework, we tried to answer to three Critical questions: What we will bring to asset owners? – Clear total cost of ownership, as well manageability of infrastructure What will be the value to industry? – device & protocol level interchangeability What is the value to society? – easiness in creating integrated infrastructure
The dialog will show us up how to really drive the building!!! How to efficiently manage usage of our energy !!! How to control all other aspects of building behavior !!!
Therefore , we believe that BrightCore will bring you into interchangeability of - not just devices !!! I t will open possibility to move whole networks segments from one protocol to another !!! F or example from Modbus to Lonworks , It will open possibility to exchange horizontal and vertical applications connected to the building infrastructure!!! It will help owners to get fair price for product s in whole segment – from the device to application!!!
So , what really Brightcore does? Gives you ability to observe every building as separate network and still be in same “mage network ” Every network could be commissioned by different contractor Gives you ability to establish management data center which will take care about all your data from your buildings!!! Gives you ability to have enormous number of interactive clients ( software applications ) Through the SDK tools any vertical and horizontal application with open SDK could be connected to the infrastructure!!
How it looks like?? Every networks has the node which absolutely behave as any other device from that network (commissioning, integration, testing) Only difference is that the node (BrightNode) talk to ObjectCore In essence ObjectCore contains “world description” and ability to : - know all about interactions between nodes in separate networks ( what are the links between nodes , how they are operating , ..) - take care about interaction s between nodes in different networks - take care about interaction s between nodes and BrightLet - take care about interaction s between different BrightLet Truly we can talk about pure asynchronous network structure !!!!
In case of Lonworks we stay in native environment , using native tools If we have for example few geographically distributed buildings. E very building could be commissioned by different contractor !!! Every building could be maintained by different contractor!!!!
BrightNode is not simple gateway! From the ObjectCore perspective through BrightNode we are seeing all traffic at the native network; since we are there!!!! It is just on administrator of the network to establish what will go out and in native network. (which data ) And this is changeable in time remotely!!!
Just few reminds on Lonworks technologies! - Strong technology - Widely deployed - Lot of manufacturers - Well standardized
This is quite old slide, little bit refreshed; Present distribution of Lonworks technology Lonworks is quite widely outspread through different industries
On this slide is missing ISO standard , since Lon is ISO standard too. ( ISO/IEC 14908, Parts 1, 2, 3, and 4 ) We can see how big coverage has this protocol!!!
At the and general idea of the BrightCore is to unleash infrastructure from cage of signals, variables, protocols, ... It opens a way to look on the building as vivid object database with whom we are interacting constantly in real time , but just observing and manipulating with data which are interesting from our point of view. We all are not seeing things with the same eyes!!! In a same time lot of users humans or machine could interact with the building actively and passively. So, this is pure network speeded from tiny small devices in your room to the servers which are talking care about your business!!!
Thank you for your time If you are interested to see how it works I am outside in the lobby – BrightCore Booth !!
