1. SYSTEM-OF-SYSTEMS THAT ACT LOCALLY FOR OPTIMIZING GLOBALLY EU FP7 - SMALL/MEDIUM-SCALE FOCUSED RESEARCH PROJECT (STREP) FP7-ICT-2013.3.4: ADVANCED COMPUTING, EMBEDDED AND CONTROL SYSTEMS D) FROM ANALYZING TO CONTROLLING BEHAVIOUR OF SYSTEM OF SYSTEMS (SOS) Consortium Meeting WP7.2: Business Model, Standardization & Exploitation Itziar Alonso & Eduardo Gilabert (IK4-Tekniker) 9 February 2016 Technische Universitaet Muenchen (TUM), Germany

2. Project Acronym: Local4Global Project Number: 611538 Project Start Date: October 2013 Duration: 3 Years Funded by: EU FP7 Program Name: EU FP7 - SMALL/MEDIUM-SCALE FOCUSED RESEARCH PROJECT (STREP) FP7-ICT-2013.3.4: ADVANCED COMPUTING, EMBEDDED AND CONTROL SYSTEMS D) FROM ANALYZING TO CONTROLLING BEHAVIOUR OF SYSTEM OF SYSTEMS (SOS) Local Global Contact Information For information regarding this Project: Check the Project Web-Site: http://local4global-fp7.euhttp://local4global-fp7.eu Participants 1CERTH - Centre for Research and Technology 2ETHZ – Eidgenössische Technische Hochschule Zürich 3RWTH – RWTH Aachen University 4IK4 – IK4 TEKNIKER 5TRV – TRANSVER GmbH 6TUC – Technical University of Crete 7TUM – Technische Universtität Muenchen 4

3. WP7 Task 2 Task 7.2: Business Model, Standardization & Exploitation (Task Leader IK4) Aspects relative to explotation and commercialisation of the project results and the overall economic viability of the initiative in the mid-term. It will describe how the consortium members intend to take forward the work of Local4Global project. Deliverables: D.7.4 - Initial Exploitation Plan (M9) D.7.5.1 - L4G Business Models and Update of Exploitation Plan ( 1 st version) (M18) D.7.5.2 - L4G Business Models and Update of Exploitation Plan ( final version) (M36) D.7.6 - Overview of Potential Standards for TSoS Control (M18) D.7.7 - Standards for TSoS Control (M36)

4. Standardization

5. WP7 Task 2 Standardization L4G project provides contribution to the European effort for standardization. L4G requires the use of standards and systems that render the interfacing and connection of different embedded software systems. D.7.6. “Overview of Potential Standards for TSoS”: selected set of standards and their implementation in Local4Global Integrated Software System. Different areas in Local4Global system: software development services interoperability data interoperability building/domotic standards The final version after finishing the development of the Local4Global system, on month 36 will include further updates and the implementation of the standards in Local4Global system. Standardization is key for guaranteeing exploitation of Local4Global results

6. WP7 Task 2 Standardization TypeStandards 1 Software Development UML, SOA 2 Services Interoperability HTTP, FTP, TSL/SSL UMTS, WSDL, SOAP, UDDI REST, BPEL 3 Data interoperability XML, OWL, SensorML 4 Building/ domotic BacNet, LonWorks, EIB, KNX,OPC ModBus, M-Bus, MP-Bus

7. WP7 Task 2 Standardization StandardRationaleImplementation UMLUML is one of the most visual ways of expressing the data model that will be used. Every partner has previous experience with it. Tools like Visual Paradigm even include functionalities to transform UML into source code. Used in the design phase for the Local4Global software. This includes data models, flow diagrams, sequence diagrams, and component diagram SOA/OSGiThe Service Oriented Architecture offers greater adaptability and scalability, splitting the functionalities in services. The OSGi approach could be considered similar, as it encapsulates different functionalities in completely functional components called bundles. This allows to easily deploy new functionalities without the need of modifying the existent solution. The Local4Global software will follow the SOA/OSGi approach. A core service/bundle will offer the generic functionalities (data and configuration management, control logic and optimization algorithms) while different communication drivers/bundles will be downloaded and deployed to meet the use case requirements HTTP/FTPHTTP and FTP are two of the most extended protocols for long distance communications between machines. Most existing development libraries make use of these protocols Used for communications between the different components of the traffic use case. Web/online communication drivers will use HTTP/FTP as their base protocol. TSL/SSLTSL and SSL are used along with HTTP and FTP to provide a security layer in the communications. It’s a well extended standard and known to every partner in the project. Web communication drivers will support the use of TSL/SSL along with HTTP/FTP. UMTSUMTS provides inexpensive wireless long distance communication. It is used in the existing infrastructure of the traffic use case Different components of the traffic use case use this technology: -Junction control units communicate with the road Administration through UMTS -The Apps deployed in the smartphones will use the UMTS to communicate with the services in TUM

8. WP7 Task 2 Standardization StandardRationaleImplementation WSDL/SOAPWSDL and SOAP are widely applied in Web Services, WSDL for defining the web service and SOAP as message format. In the traffic use, the Local4Global algorithm will be deployed as a service in IK4-Tekniker premises, along with other functionalities. These web services will use SOAP and WSDL for the communications. RESTREST offers a very extended more lightweight alternative to the WSDL services, using HTML commands (GET, PUT...) as functions. Local4Global services use WSDL/SOAP, but REST could be used for exposing the services as an alternative. Specific communication drivers could use REST services as data sources. XMLXML is a well know and extended standard for structured data exchange. SOAP messages are XML messages will specific tags. The web services used in the traffic use case services will use SOAP or plain XML to exchange measurement data and control strategies. OPCOPC’s use is very extended standard in industrial and building environments. This standard is used in the pre-existing infrastructure for the building use case. Is used in the building use case infrastructure, in order to make data available to the BMS. An OPC-UA communication driver will be developed in Local4Global. BACnetThis standard is used in the pre-existing infrastructure for the building use case. Used in the building use case infrastructure, connects the different control units and sensors with the OPC server and the BMS. MP-BusThis standard is used in the pre-existing infrastructure for the building use case. Used in the building use case infrastructure as a field bus protocol for the sensors. LonWorks EIB KNX ModBus M-Bus Tekniker has developed the communication drivers using the openMUC framework as guideline, which includes working communication drivers for many of these standards. Support for the different existing communication protocols is desired in order to have greater interoperability. openMUC framework[17] has already working driver implementation of these standard and they could be easily be adapted in order to be used in the Local4Global software system. They are not used in any of the proposed use cases, but will be taken into account for the supporting the final product.

9. Exploitation

10. Task 7.2. Framework Initial Activities Business Models & Exploitation Strategy Update WP7.2 L4G Final Business Models & Exploitation Strategy & Market Awareness Identification of Project Exploitable Results Definition of Partners Exploitation Strategy Annex 1. Standards Annex 2. IPR Management D.7.4. Month 9 D.7.4 Standards & IPR Management L4G Use Cases L4G Stakeholders Validation Best practice models INPUTS D.7.5.1 Month 18 D.7.5.2 Month 36 Strategic Definition Product and Services Analysis Market Analysis Implementation Plan Management Issues Financial Plan Business Models: Partners Exploitation Plan Updated Standards TSoS D.7.5.2 Early Version Month 24

11. An initial version of D7.5.2 was requested at M24. The “ technical” part of the deliverable contained: Stakeholder analysis, First draft of a business case, including financials, Prioritization of products and Analysis of obstacles on the way to commercialization, such as certification etc.. Deliverable 7.5.2. Early Version

12. DEFINITION: L4G Business Models & Update on Exploitation Plans (m 36): “Based on D7.5.1 (m18) + D.7.5.2 e.v. it will be further updated and elaborated by embedding the experience/results from the Local4Global Use Cases” Exploitation Plan for L4G products & per partner Business Models Deliverable 7.5.2. Definition & Content

13. Thank you for your attention Eduardo Gilabert & Itziar Alonso (IK4-Tekniker)