building automation systems from internet of · pdf filebuilding automation systems from...
TRANSCRIPT
Building Automation Systems from Internet of Things
ProfessorJerkerDelsingEISLAB
LuleåUniversityofTechnology
IoT Product Segments
Conveyor (Tier2) Components and Parts (Tier3) Drive Heads LTU & Winches Belt Structure Belting Pulleys Feeder Breakers Components (a.u. idlers, motors, etc.)
Suppliers of these Products are: Potential partners, and; Future Service Providers
Onecustomer,KGHM,onecomponent• 120kmconveyers• 720.000idlerbearings
The automation challenge
Annual growths more than 10% and over 500 billion connected devices are expected worldwide by 2025. - Cisco 2013
Massive automation systems not possible with current technologies
Not enough many engineers on the globe to do the job with current technology
Benefits to the production industry - Spire
• Be>erop@miza@onandcoordina@onofsingleprocessesorprocesschainsandofcompleteplantsandsites,
• Significantlyimprovedresourceefficiency.• Be>ercoordinatedcontrolloopsinoneprocessstepandimprovedcollabora@onofcontrolsystemsofdifferentprocessesalongaprocesschaingivehigherprocessyieldswhichresultsinbe>ermaterialefficiency,wastereduc@on,lessenergyuseandreduc@onofpollu@on.
• Improvedproductqualitythroughbe>erprocesscontrolandsmartqualitycontrol• Higheru@liza@onofequipment• Newcollabora@vesolu@onswithintegratedinforma@onmanagementoffernewpossibili@esforsupplychainmanagementincludingprice-basedcoordina@onorop@misedmarketmechanisms
• Saferopera@onofplantsduetoimprovedcontrolandshut-downprocedures.• Possibili@estointegratemul@pleprocesses.• Shorterdelivery@mesandlowerproduc@oncost.
www.arrowhead.eu
5
Arrowhead Process and energy system automation
4 years project 68M€79 partnersCoordinated by
an ARTEMIS CoIE
www.arrowhead.eu - [email protected]
ARTEMIS Industry Association The association for R&D actors in embedded systems
www.arrowhead.eu
6
ISA-95systemsintothecloud?The
7
ArrowheadapproachesTCP/IPeverywhere,middlewarenowhere.
InternetofThings-IoT
Systemofsystems-SoS
TheIntegratingapproach
ServiceOrientedArchitectures-SOA
8
Theglobalcloudapproach
A Survey of Commercial Frameworks for the Internet of Things. Hasan Derhamy, Jens Eliasson, Jerker Delsing, and Peter Priller, SOCNE workshop at ETFA 2015, Luxemburg
9
Collaborativeautomationinthecloud
Automationislocal-requirementson:RealtimeSecurityandsafetyContinuousengineeringScalability
Localcloudsarebeneficialto:Latency-realtimeSecurity-supportingsafetyLessengineeringdependencies
Intercloudserviceexchangeenablesscalability
10
ClassicalautomationsystemcharacteristicsCentralisedcontrollers,DCS,SCADA,PLC,Pullbased-timeslottedstreamingofalldata
Hardrealtime
Designtimebindings
SeamstohaveanupperboundofX*105I/O’s
11
CloudbasedautomationsystemsChoiceofcentralisedordistributedcontrolanddatatoinformationcomputationsPushoneventorpull
Latebinding-runtimebinding
Hardrealtime?
www.arrowhead.eu
12Howtobuildlocalcloud?Fundamentalconceptualoverview
all of its users to work in a common and unified approach – leading towards high levels of interoperability.
A. Overview of Arrowhead Framework The Arrowhead Framework includes principles on how to
design SOA-based systems, guidelines for its documentation and a software framework capable of supporting its implementations.
The design guidelines provide generic “black box” design patterns on how to implement application systems to be Arrowhead Framework compliant. Furthermore, these guidelines allow making legacy systems Arrowhead Framework compliant.
The documentation guidelines include templates for service, system and, system-of-systems descriptions (to be detailed in the following sections of this paper). Due to its complexity there is also a “Cookbook” for hands-on instructions on how to use the framework.
The software framework (Fig. 2) includes a set of Core Services which are capable of supporting the interaction between Application Services. The Core Services handle the support functionality within the Arrowhead Framework to enable Application Services to exchange information. Examples are services for Discovery, Authorization, Orchestration, and System Status. An Application Service handles the data exchange between specialized devices (those that the system is special at). Examples are services for sensor reading, billing, energy consumption, weather forecasts, etc.
The Core Services (Fig. 2) are further divided into three different groups: i) Information Infrastructure (II); ii) Systems Management (SM); and, iii) Information Assurance (IA).
The II services are the set of core services and systems in charge of providing information about the services and how to connect to them. This includes services like Service Discovery, Application Installation and Setup, Service Metadata, etc. The SM services are the set of core services and systems providing support for late binding and solving system-of-systems composition. The SM provides logging, monitoring and status functionality. It also addresses orchestration, software distribution, Quality of Service (QoS), configuration and policy. Finally, such a software framework can only operate if the system is able provide adequate security and safety levels. Those functions are assured by the IA services, supporting secure information exchange. Example services include those for authorization, authentication, certificate distribution, security logging and service intrusion.
The software framework also addresses the design and prototype implementations of gateways/mediators for making legacy systems Arrowhead compliant.
Finally, the Arrowhead Framework provides a set of rules and principles to: i) address technical property requirements; ii) Arrowhead conformity requirements and, iii) a set of tool(s) for conformity test and verification.
Fig. 2. Arrowhead Framework core and application services
B. The Arrowhead Framework documentation approach The Arrowhead Framework states a common approach of
how to document SOA-based systems. The documents structure is built on three levels, namely: System-of-Systems, System and Service level. These are depicted in Fig. 3, showing the links between documents, as well.
Fig. 3. The Arrowhead Framework documentation relationships
The approach is to apply the terms “black box” and “white box” only to the System level since it is well known what it means. However, these concepts are not used at the Service level, where such division is rather meant to be about technology independence/dependence.
At the System-of-Systems (SoS) level, a concrete “System-of-Systems type” is defined in the System-of-Systems Description (SoSD) document. Thus, the particular “system type” needed to fulfill our SoS goals can be implemented. The correct way of working is assured thanks to the “black box” representation of all Systems in the System Description (SysD). Therefore, each “system type” can talk to each other or identify the gateways/mediators’ needs.
In the System-of-Systems Design Description (SoSDD) a SoSD instance can be created. All the participating “white box” Systems (SysDD) must be enumerated and the entire setup must be explained, including infrastructure description (network configuration, VPNs, etc.), domain structure, startup behavior etc. This is a deployment description and it describes the SOA installations.
www.arrowhead.eu
13
CoreFunctionalities-System-of-Systemsinalocalcloud
ARROWHEAD FRAMEWORK
LOCAL CLOUD
Orchestration system
Authorisation system
Service Registry & discovery
system
Applicationsystem
Applicationsystem
Applicationsystem
App
lication
system
Applicationsystem
14
ArrowheadcoresystemsPlantdescriptionsystemConfigurationsystem
Gatekeeperservice-interclouddiscovery,orchestrationandsecurity
Eventhandlersystem
Historiansystem-dataloggingandinterclouddatapathsupport
Metaserviceregistrysystem-Userregistrysystem
QualityofServicesystem
Translationservice-protocolandsemantics
15WhataboutserviceprotocolinteroperabilityIsitpossibletomakemachineassistedtranslationlike
CoAP -> XMPPCoAP -> MQTTCoAP -> OPC-UAOPC-UA -> CoAPOPC-UA -> MQTTNecessary semantics translationNecessary data structure translationsService integrity over protocols, data structures, semantics etc.
Hasan Derhamy, Pal Varga, Jens Eliasson, Jerker Delsing and Pablo Punal Pereira Translation Error Handling for Multi-Protocol SOA Systems, ETFA 2015, Luxembourg
16
HardrealtimeIoTcloudHard real time dependent on underlaying communication capabilities
Local hard real time cloud to prescribe communication technology e.g. Industrial ethernet, TTTech, time slotted 802.15.4
SOA overhead eats bandwidth Use compression EXI
EXIP: A Framework for Embedded Web DevelopmentKyusakov, R., Punal, P., Eliasson, J. & Delsing, J. Oct 2014 In : ACM Transactions on the Web. 8, 4, 29 p.23
www.arrowhead.eu
17
Real@melocalcloudautoma@on &intercloudautoma@on
RealtimeLocalcloud#1
IASM
II
Applicationsystem
Applicationsystem
Applicationsystem
App
lication
system
Applicationsystem
Applicationsystem
RealtimeLocalcloud#2
IASM
II
Applicationsystem
Applicationsystem
Applicationsystem
App
lication
system
Applicationsystem
Applicationsystem
RealtimeLocalcloud#3
IA SMII
Applicationsystem
Applicationsystem
Applicationsystem
App
lication
system
Applicationsystem
Applicationsystem
18NecessarytechnologyforlargeautomationsystemsinthecloudRobustcommunication,wiredorwirelessIoTsensors,actuators,PLC:s,etc.
DCSandSCADAfunctionality’
MESandERPfunctionality
CloudintegrationtechnologyEngineeringtoolsforcloudautomationsystems
Testtoolsandsimulatorsfordebugging
Migrationofcloudautomationintolegacyproductionsystem
Suitablesecurity
19
CanwebuildArrowheadautomationsystemstoday?RobustcommunicationIoTsensors,actuators,PLC:s,etc.
DCSandSCADAfunctionality
MESandERPfunctionality
Cloudintegrationtechnology
EngineeringtoolscloudautomationTesttoolsandsimulators
Migrationtocloudautomation
Suitablesecurity
➡Productsonthemarket➡Someproductsonthemarket
➡Firstproductsonthemarket
➡Demonstratedinindustrialenv.➡Someproductsonthemarket➡Demonstratedinindustrialenv.➡Firstproductsonthemarket
➡Demonstratedinindustrialenv.
➡Firstproductsonthemarket
20
AutomationengineeringtimeAutomationisaservicebasedonproducts
Simplicityofautomationserviceengineeringismarketkey
ArrowheadFrameworkreducesengineeringtime
From5-6days->6-8hours(Abelko)From4-5weeks->1week(BnearIT)
www.arrowhead.eu
21
Renewable-PVatbuildingroofRecoveryfromliftoperationGridsupplyUseof3sharedservices:energytariffs,prediction,energyplanningEnergysavingsupto65%
Liftmicrogrids
www.arrowhead.eu
22
UseofpredictionserviceenablesflexibilityinenergydemandEnergysavings15%
Waterdistributiongrid
www.arrowhead.eu
23
Loadbalancing-LuleåSwedenAdaptivecontrolcurveservice
Loadbalancingofindividualbuildingpeekenergydemandsservice
MultisiteoptimisationserviceInteractingwithloadbalancingandtheadaptivecontrolcurve
Stena(housingcompany)claims5%savingsinenergyusage.
MARSUR (EDA) 1/4
EU Maritime Surveillance
Network (incl DMZ)
Member State protected network
Data transfer Whiteboard
Phone
Mail Chat
Video stream
Maritime Surveillance
System (MSS)
MARSUR Exchange System
(MEXS)
MARSUR (EDA) 2/4
EUMaritimeSurveillanceNetwork
DirectConnection
National MSS
SWEDEN
Database
National MSS
ITALY
MSS_APIDirect
Connection
National MSS
SPAIN
DirectConnection
(?)
National MSS
FINLAND
MSS_API
National MSS
UNITED KINGDOM
Database ?MSS_API ? Direct Conn.
?National
MSS
FRANCE
Services: Data Transfer Mail Chat (?)
Services: Data Transfer Mail ChatWhiteboardVoIP Video
Services: Data Transfer Mail ChatWhiteboardVoIP Video
Services: Data Transfer Mail ChatVideo
Services: Data Transfer Mail ChatWhiteboardVoIP
Services: Data Transfer Mail ChatWhiteboardVoIP Video
MARSUR (EDA) 3/4
MARS
URExchan
geSystem(M
EXS)
Mem
ber S
tate
DM
Z
National MSS
EU Maritime Surveillance Network
Data Transfer
(Proprietary)
Data Repositor
y (PostgreSQ
L)
(Postfix, Dovecot,
Squirrelmail)
VoIP
(Asterisk)
User Registry
(OpenLDAP)
National Private Network
Mail client,
Webmail Vide
oC
amer
a
Video
(VLC)
MEXS-MSS API
Spark
ChatWhiteboard
(OpenFire)
VoIP Client
UserRegistryClientTool/
Viewer
Vide
oC
lient
MEXS-MEXS API
MEXS-MEXS API
MEXS 1.0 TIDE 2.xMEXS-MEXS API
Con
figur
e
MARSUR (EDA) 4/4• EU; 18 länder, marina system
• Säkerhet, x509 manuellt utbyte, ssl/tls, dmz, ad/inloggning
• Integration, 2-3 dagar
• Skarp operationell drift sedan 2009
• Nod för grundfunktionalitet, 3 L:en.
28
ArrowheadFrameworkPublicbyMarch2016
Documentation
Cookbook
Supportwiki
Coresystemcode
Tools-OpensourceandcommercialSampleautomationservices-code
29
ArrowheadFrameworkPublic(March)Wikihttps://forge.soa4d.org/plugins/mediawiki/wiki/arrowhead-f/index.php/Main_Page
30
Nyaprojectförslag-ArrowheadXXXProductintheloopCustomerintheloop
Productionintheloop
Automationstate
Nanobusinesstransactions
..
..
www.arrowhead.eu
Arrowhead.euanArtemisandProcessIT.EUproject
31