The Internet of System Engineering INCOSE-IL Seminar, Herzliya, Israel

15 September, 2011

Software Platform for Integration

of Engineering and Things ICT-2009.1.3 Project Number: 257909

www.sprint-iot.eu

Internet of Systems Engineering Architecture U. Shani (IBM)

• Goals of the SPRINT Architecture

• Components

• Related Standards – RDF and OSLC

• The Platform – Rational Jazz and Design Manager

• Distributed Collaboration

• Data and control flow

Table of Contents

2

Components

3

Internet of

Designers

Internet of Physical

Devices

Internet of Model

Elements

Internet of System

Engineering Designers-to-

Physical Device

Connectivity

T

1

T

2

T

n

A1 A2 Am

SII – SPRINT Information Bus

. . . . .

. . .

SSI – Semantic Services Integration

SSI – Semantic Services Integration

S

D

1

T

C1

Internet

C

D

1

Architecture Components

Architecture Components

• Tools

• Applications

• SII – Semantic Interoperability Integration

• SSI – Semantic Service Integraton

• Devices

• Device platforms

Relationship Hub (RH)

Protocols and Data formats

• Data is coded in RDF – Resource description Framework

• Communicating in OSLC – Open Services for Lifecycle Collaboration

• Platform is Jazz – supporting OSLC and RDF with security and reliability

TCP/IP – Transmission Control Protocol / Internet Protocol

HTTP – Hypertext Transfer Protocol

RESTful – Representational State Transfer

RDF – Resource Description Framework

OSLC – Open Services for Lifecycle Collaboration

genid:ARP40722

foaf:Person

rdf:type

“shani” foaf:nick

“Uri Shani”

foaf:name

“2971b1c2fd1d4f0e8f99c167cd85d522a614b07b “

foaf:mbox_sha1sum

rdf:SeeAlso

genid:me

foaf:knows

http://www.iamshani.com/foaf.xml

OSLC Servers and Clients

• Clients may have no repository

• Clients cannot respond to queries

• Clients are not servers

• BUT: Clients can participate in OSLC

OSLC Client

OSLC ToolA Repository

A

OSLC ToolB Repository B

T

n

SII

Partner A

Partner B

Partner C

Collaborative Environment

DSII

T

n

SIIB

SIIA

SIIC

Partner A

Partner B

Partner C

Distributed Collaboration

DSII

Partner A

Partner B

Partner C

SIIB

SIIA SIIC

SIID SIIE

A

m

Partner E Partner D

Multi-project Distributed Colalboration

Ja

zz s

erv

er

EADS RZ EADS YZ

Inte

rne

t GZ

IAI RZ IAI YZ

DOORS 9.2

SA 11.3

DOORS 9.2

SA 11.3

HP QC

IAI tools

Clie

nts

Clie

nts

9443.9444

9443.9444

Ja

zz s

erv

er

IAI web br.

EADS web br.

EADS

SII

IAI

SII

Concrete Example

SII RDF Repository

R1

T1 T2

R2

A1 A2

Ra1 Ra2

OSLC SII - 1 SII RDF

Repository

R3

T3 T4

R4

A3 A4

Ra3 Ra4

OSLC SII - 2

Data flow from tool

to application via

local SII node and

repository

Two-way data flow

between 2 tools on

separate SII nodes

and 2 repositories via

SII collaboration.

Abstraction of Distributed Model Sharing

Jazz Integration Architecture Over the Jazz Foundation Server

SII – SPRINT Information Bus

HRC lite

Tool

domain

Plugin

R

SII RDF Repository

Proprietary Tool

format

RDF format of

Proprietary Tool

structure

One of intermediary

OSLC domain

structures

Intermediary

OSLC format step

1

Intermediary OSLC

format step 2

OSLC Lite-HRC

structure

RDF format Proprietary

format

OSLC structure Proprietary structure

Domain

Interm 1

Plugin

Interm1

Interm 2

Plugin

Interm 2

common

Plugin

SSI – Semantic Services Integration Data processing path T

OSLC

RDF

OSLC

RDF SII Repository

Example: IBM Rational Rhapsody SysML

RDF

SPRINT Data and Control Flow

Step 2:

Plain RDF Model

Step 3:

OSLC RDF Model

Step 4:

Common Model

SII

SSI

RDF

OSLC RDF

OSLC RDF

HRC lite

SII Repository

IBM Rational Rhapsody SysML Step 1:

SysML Model CAx-Tool provides the translation

into plain RDF.

CAx-Tool sends RDF to SII

-Using DM or RIO

SII takes care about OSLC

transformation.

NOTE: In this step there are may

different versions of the RDF

representation (*.nt, *.rdf)

NOTE: In this step there just the

OSLC Domain specific versions

remain.

Translation the OSLC RDF into a

common model using the HRC lite

meta-model by the SSI

NOTE: After this step just one

model can be exists.

Physical adding of the common

model as RDF file into the

repository. Step 5:

Common Model in

relation to other

common model

elements

SPRINT Data and Control Flow

RioStore

RDF Repository

RioResource RioBaseService

HttpService

SII_MM_Resource

SII_Tool_Resource

SII_Tool_Service

SSI_Mediation_Service

Uses Uses

Uses

Uses Uses

Uses

Client Tool

Exporter

1

2

4

3

5

6

SII_Service

SPRINT Data and Control Flow

Implementation

Andreas Keis

Engineering & Architecture

Manager Software Engineering

EADS Innovation Works

Quadrant Campus, Newport NP10 8FZ

United Kingdom

Tel: +44 (0) 1633 71 4760

Fax: +44 (0) 1633 71 3300

Mobile: +44 (0) 7970381972

Email: andreas.keis@eads.com

Linkedin: http://www.linkedin.com/in/andreaskeis

Contact

18