Webinar: The Vorto project proposal for Eclipse Internet of Things (IoT)

Eclipse Webinar | INST / TST | 15/10/2014 | © Bosch Software Innovations GmbH 2014. All rights reserved, also regarding any disposal, exploitation, reproduction, editing, distribution, as well as in the event of applications for industrial property rights.

Bosch Software Innovations

1

The Vorto project proposal Eclipse Webinar



Bosch Key Figures 2013

Bosch Group 46,4 billion EUR in sales

281 400 associates 225 manufacturing sites

Americas

Asia Pacific 2

Europe 55 % share of sales 174 400 associates 140 manufacturing sites

2 Including other regions

21 % share of sales 33 500 associates 33 manufacturing sites

24 % share of sales 73 500 associates 52 manufacturing sites

Automotive Technology

66 % share of sales Industrial Technology

15 % share of sales Energy and Building Technology

9 % share of sales Consumer Goods

10 % share of sales

2

The Vorto project proposal



3

Bosch Strategy: Networking our Technology


http://youtu.be/TXvjBw8AGwc

http://youtu.be/TXvjBw8AGwc�



4

Bosch Software and Systems House

• Locations: Berlin, Immenstaad, Stuttgart, Chicago, Palo Alto, Singapur, and Shanghai

• Employees: ~ 500 worldwide

Overview Bosch Software Innovations

Industry Focus Mobility, Energy, Industry, City & Building

Bosch IoT Suite BPM , BRM , M2M

Professional Services Planning, Implementation,

Training and Operation of Solutions, based on our Software Suite




M2M BRM BPM Bosch IoT Suite

Smart Energy Smart Metering VPP (Virtual Power Plant)

Connected Industry Service Portal

Smart Mobility Fleet Management eMobility Solutions

Bosch Software Innovations: The Systems and Software House for Internet of Things Solutions

Smart Home Intelligent Solutions

5




Bosch IoT Platform Strategy Overall goal:

Business Success for Bosch Group in IoT with Products and Services in the Verticals Mobility, Industry, Energy, Building

Interconnections and Interoperability of Devices/Services (therefore Bosch should “back on the right (platform) horse”)

Assumption:

2-5 major IoTS platforms (in next 5-7 years) At least one of them will be Open Source Bosch not able to develop one of these proprietary platforms alone

and customers/partners would not accept it No risk/dependency on proprietary 3rd party platform

Conclusion

Open Platform strategy with OSS

6




There are four scenarios that shall be addressed by the Vorto approach

7 7


Vendors of IoT platforms want to integrate as much as devices as possible into their ecosystem without major effort.

Vendors of IoT devices want to increase the number of ecosystems where their devices can be integrated.

Consumers want to use a large variety of devices in their ecosystem and don‘t want to be limited to using devices of one specific vendor. 1

Flexibility, Ease of use

Increase sales

Increase sales, become standard

2

3

Application developers want to support a broad range of devices without a need to develop vendor specific code. 4

Increase sales, reduction of complexity



Scenario 1: Consumer

8 8


Bosch M2M

ThingWorx

Qivicon

Device 1

Device 2

Device 3

Device 4



Scenario 2: Device vendor

9 9


Bosch M2M

ThingWorx

Qivicon

Device 1



Scenario 3 and 4: Platform vendor / Application developer

10 10


Bosch M2M

ThingWorx

Qivicon

Device 2 Device 3

Device 1

Device 4

Device 5



An approach that covers the requirements of all 4 scenarios:

11 11


Bosch M2M

ThingWorx

Qivicon

Device 2 Device 3

Device 1

Device 4

Device 5



Camera

Display

Bosch VSC-1516

SAMSUNG UE55

Abs

tract

Rea

l

12 12

Info model Samsung UE55

Info model Bosch VSC-1516


An information model is an abstract representation of the functionalities, properties, and status of a real object



Components - Tuner - Display - Speakers - Motion Detector

13 13

Information model


An information model is an abstract representation of the functionalities, properties, and status of a real object

Functionblock: Tuner

Functionblock: Display

Functionblock: Speaker

Device specific information

Functionblock: Motion Detector



Bosch M2M

Bosch Driver

ThingWorx ThingWorx Driver

Qivicon

14 14


Idea: Creation of a flexible meta information model and code generators for generating specific representations

Qivicon Driver

Meta Model

Information Model of Device i

Qivicon Code Generator

Device i

Bosch Code Generator

ThingWorx Code Generator

Instance of

uses

uses

uses

generates

generates

generates



Vorto Project Vorto

Project

Vorto Project

Information Meta Model

IoT Tool Set

Code Generators Repository

15 15


The goal of the Vorto project is to enable a global standardization

Create representations for different eco-systems

Standardize the structure of information models

Manage and provide information models

Create information models



Camera

Display

16 16

Info model Display

Info model Camera


Information models are standardized by means of a flexible and sustainable meta information model

Eclipse EMF based Meta Information Model

Instance of

Instance of

Meta Information Model

Specifies the structure of derived information models



Camera

Display

17 17


Info model Display

Info model Camera

Information models that conform to the meta information model can be authored using the IoT Tool Set

Eclipse Platform based IoT Tool Set

Created using

Created using



18 18


The initial version of the IoT Tool Set is realized as an Eclipse plugin and provides a textual DSL editor

The grammar of the DSL corresponds to the meta information model

Auto completion and syntax highlighting allow for comfortably creating information models

A graphical environment for creating information models shall be added

The Tool Set shall allow for connecting to the information model repository

Part of the initial contribution

In scope of the project



XML Representation

19 19


The IoT Tool Set allows for creating information model based implementations using Code Generator plugins

IoT Tool Set

XML Code Generator

OSGi DAL Code Generator

OSGi DAL Representation

Info model Display

The code generator extension point of the IoT Tool Set allows developers to create additional (domain specific) code generators.



20 20


The central Information Model Repository allows for managing and providing existing information models

Information Model Repository

Info model Camera

Info model Display

Governance

When version 1.0 of the repository is released it shall be hosted by Eclipse to promote a worldwide standardization of information models

IoT Tool Set



Repository


The components of the Vorto project in combination at a glance

IoT Tool Set

OSGi DAL Code Generator

Code Generator Extension Points

XMI

Governance

Import

OSGi oneM2M HGi …

OSGi oneM2M HGi …




Use Case: A device vendor creates a new smoke detector and an openHab community member wants to integrate it

Vendor A creates an information model for his new Z-Wave smoke detector using the IoT Toolset

After Vendor A has finished his work he publishes his new information model into the repository.

openHab community member would like to include it into his/ her environment.

openHab community member browses the repository and finds the corresponding information model and downloads it.

openHab Community member uses an openHab code generator in combination with the IoT Tool set to create the related items.

(openHab community member adds specific Z-Wave information to the generated items.)

The smoke detector is supported by openHab.




Use Case: A platform vendor releases a new platform and provides a related code generator for allowing others to easily integrate their devices

Platform Vendor P releases a new IoT platform and wants to allow potential consumers to integrate their devices.

Vendor P creates a P-specific code generator in the context of the Vorto project and makes it available to potential consumers via the IoT Tool Set update page.

Device Vendor A notices that there is a new platform but the information models which are related to his products are technology agnostic and thus are still valid. There is nothing to do.

Developer installes the IoT Tool Set. Developer gets

code generator via Tool Set update page.

Developer downloads corresponding information models.

Developer generates code for the new platform.



The Meta Information Model


Technical Aspects:

The IoT Tool Set

• Is based on Ecore (part of the Eclipse Modeling Framework). • Attributes and Capabilities which are described in the information meta model are

realized as Ecore compliant Java interfaces and implementation classes. • The meta information model contains also technical validation functionalities for

meta model instances.

• The DSL editor is based on the Eclipse XText framework. • The grammar of the DSL is based on the meta information model. • The code assistance, and the syntax highlighting information is an additional part

of the DSL grammar. • The editor provides a textual standard formatting of information models which

allows for comfortably comparing different (versions of) information models. • Allows for serializing the meta information model instances as user readable DSL

text file and machine readable XMI file. • The Tool Set provides an code generation extension point consisting of an

interface Java class and an extension schema.




The Repository

Repository

• TBD

The Code Generators

• Must implement the „information model generator“ interface which is part of the code generator extension point

• Code generators are based on the information meta model • Input for the code generators are specific instances of the information meta model • Can be based for example on Eclipse XPand or JET… • Code generators can be integrated into the tool set by registering the code

generator as an extension of the given extension point.

Technical Aspects:



26

Contact Details Olaf Weinmann [email protected]

Predictive Maintenance

@BoschSI

Bosch ConnectedWorld Blog

www.blog.bosch-si.com

Date post:	01-Dec-2014
Category:	Internet
Upload:	stefferber
View:	1,960 times
Download:	0 times