Collaborative Systems Engineering - Peter Gerber (Schaeffler Technologies) - prostep ivip Symposium
←
→
Page content transcription
If your browser does not render page correctly, please read the page content below
Collaborative Systems Engineering
Peter Gerber (Schaeffler Technologies)
© prostep ivip e.V. 9 September 2020 Collaborative Systems Engineering, Peter Gerber – prostep ivip Symposium 2020 2
Smart Products for Tomorrow
Yesterday Today Tomorrow
Product & Technique Emotions & Function Mobility & Services
source: Daimler source: Daimler source: Daimler source: Daimler
Develop a
Develop a
Challenge Smart Product
Product
or Service
© prostep ivip e.V. 9 September 2020 Thema: Systems Engineering, Peter Gerber – prostep ivip Symposium 2020
Lore Ipsum
Collaborative 3
Masterplan for Co Action
Integrated Architecture Industry:
Improves:
• Transparency
• Collaboration
• Efficiency
• Smart Functionality
• Increased Speed
• Traceability
• Complexity Management
© prostep ivip e.V. 9 September 2020 Thema: Systems Engineering, Peter Gerber – prostep ivip Symposium 2020
Lore Ipsum
Collaborative 5
SysML as central structure of the smart product
SysML Workflow Forum
© prostep ivip e.V. 9 September 2020 Collaborative Systems Engineering, Peter Gerber – prostep ivip Symposium 2020 6
SysML as central Element of the Product Architecture
Detailing
Product Model Functions & Interfaces
Specification
Input/Output
and
Parameter
Requirements Decomposition
Customer High Level Model Engineering
Partner
Detailed Model
source: Daimler
source:Schaeffler
SysML WF Forum: Establish Seamless Industrial-Level Collaboration using
model-based Systems Engineering to support handling of Complexity
© prostep ivip e.V. 9 September 2020 Collaborative Systems Engineering, Peter Gerber – prostep ivip Symposium 2020 7
Focus on High Prioritised Use Cases
Including internal and external Collaboration
Requirements
Test
Company Management/ „SysML - RQM“ SysML Authoring
„SysML – V&V“ Management
-Engineering
„SysML - RQM“ „Model Exchange“ „SysML – V&V“
Requirements
Partner Test
Management/ SysML Authoring „SysML – V&V“
„SysML - RQM“ Management
-Engineering
© prostep ivip e.V. 9 September 2020 Collaborative Systems Engineering, Peter Gerber – prostep ivip Symposium 2020 8
Base: Model Exchange
Use Cases and Requirements regarding technical solutions (Results of WP4)
Reference Process / Workflow:
Exchange of real model data (Use Case):
Description of Minimal Set of Information:
Structural Content
© prostep ivip e.V. 9 September 2020 Collaborative Systems Engineering, Peter Gerber – prostep ivip Symposium 2020 9
Requirements Management supported by SysML
Use Cases and Requirements regarding technical solutions (Result of WP6)
Reference Process / Workflow: In collaboration with
Linking- and exchange process
In Work
• Description of Minimal Set of
Information for Model- and Link
Exchange
• Configuration and Release
Management
© prostep ivip e.V. 9 September 2020 Collaborative Systems Engineering, Peter Gerber – prostep ivip Symposium 2020 10
SysML Models and Verification & Validation
Requirements regarding technical solutions (Results of WP7)
Integrated Model and Exchange Workflow
Description of Minimal Set of Information
Config, Release and Change Management
© prostep ivip e.V. 9 September 2020 Collaborative Systems Engineering, Peter Gerber – prostep ivip Symposium 2020 11
From Documentation to Practise
Establish SysML Implementor Forum January 2021
Collaboration
SysML WF SysML IF
Chair (Industry Rep.) Requirements Chair (Industry Rep.)
Backlog
Processual Tool
interoperability interoperability
Solutions &
Demonstrators
IF WF
Definition of reference process, Evaluation of alternative solutions
requirements and test cases implementation of a demonstrator
© prostep ivip e.V. 9 September 2020 Collaborative Systems Engineering, Peter Gerber – prostep ivip Symposium 2020 12Mastery of a distributed product structure
Interdisciplinary Collaboration Framework Forum
© prostep ivip e.V. 9 September 2020 Collaborative Systems Engineering, Peter Gerber – prostep ivip Symposium 2020 13Distributed product structure and ALM-PLM Integration
Best practices for cross-disciplines collaboration (CDLC conclusion)
Process, Use Cases, Architecture (Requirements)
Implementation in Demonstrators
prostep IVIP
recommendation
available in October 2020
© prostep ivip e.V. 9 September 2020 Collaborative Systems Engineering, Peter Gerber – prostep ivip Symposium 2020 14Interdisciplinary MBSE Collaboration Framework
prostep ivip project: 2020-2023
Framework Methods + Capabilities + Data Architecture + IT WP1
Methods, Use cases &
Requirements
Domain Collaboration Tool Domain
WP2
Product Model Datamodel
WP3
Domain Domain Technologies
WP4
Proof Of Concept / Vendors
Demonstrators
Sub - System
WP5
Synthesis & Communication
Traces
© prostep ivip e.V. 9 September 2020 Collaborative Systems Engineering, Peter Gerber – prostep ivip Symposium 2020 15Interdisciplinary Collaboration Framework Approach
Available Technologies Principles / Capabilities / Enablers Harmonized Artifact-/
Informationmodel
List for Technologies and Standards
Domain / Topics
Ontology
Sub Topic Name
Web Ontology Language
Eclipse Modeling Framework
Meta Object Facility
Knowlage Graph
Short
OWL
EMF
MOF
DesignSpace
Description
The W3C Web Ontology Language (OWL) is a Semantic Web language designed to represent rich and
complex knowledge about things, groups of things, and relations between things.
DesignSpace provides a shared engineering infrastructure that lets you integrate any tools and connect
their data to detect irregularities across different tools and changes in data transfer.
Member of Commission ICF Expert
Davy
Davy
Davy
Source
https://www.w3.org/OWL/
https://www.eclipse.org/modeling/emf/
https://www.omg.org/mof/
DesignSpace
Alternative Type (Technology/ Standard/…) Relation Relevance Review
Process
is related to
Artifact
SysML
Semantic Network
Semantic Network Knowlage Graph
Modeling Languages / Data Modeling
Unified Modeling Language UML Davy https://www.omg.org/spec/UML/2.5 Standard
Systems Modeling Language SysML Damun M. TUK Member of Damun, Davy https://sysml.org/ Standard
(Data Exchange Formats) / Representation SysML SST
Open Data Protocol OData Related to these the OData (Open Data Protocol) is an ISO/IEC approved, OASIS standard that defines a set https://www.odata.org REST
of best practices for building and consuming RESTful APIs. OData helps focus on business logic while
building RESTful APIs without having to worry about the various approaches to define request and
response headers, status codes, HTTP methods, URL conventions, media types, payload formats, query
options, etc. OData also provides guidance for tracking changes, defining functions/actions for reusable
procedures, and sending asynchronous/batch requests. OData RESTful APIs are easy to consume. The
OData metadata, a machine-readable description of the data model of the APIs, enables the creation of
powerful generic client proxies and tools.
JavaScript Object Notation JSON Rene https://www.json.org/
JavaScript Object Notation for Linked Data JSON LD https://json-ld.org/
Extensible Markup Language XML Rene https://www.w3.org/XML/
Simple Object Access Protocol SOAP The SOAP-Interface, originally “Simple Object Access Protocol” is an international standard of the World
Wide Web Consortium (W3C). As a Webservice based Interface, SOAP is typically used with HTTP(s), but
other protocols are also possible. The SOAP Standard describes in detail how a SOAP message is
structured. Information in a client-server communication or from one system to another, is usually
transmitted via XML. In order to use SOAP web services, a detailed description is necessary. This is often
implemented using Web Service Description Language (WSDL).
Terse RDF Triple Language Turtle https://www.w3.org/TR/turtle/
Architecture
SPQRQL Protocal And RDF Query Language SPARQL SPARQL is a query language used for RDF (standardized by W3C). https://www.w3.org/TR/sparql11-overview/ Query Leng. for
RDF
Shapes Constraint Language SHACL SHACL is a language for validation of graph-based data (e.g. define the maximum amount of edges https://www.w3.org/TR/shacl/
between two nodes, like " has exactly one ") ("What XSD is for XML, SHACL is for RDF.")
Linking Data
Graph Data
uniform resource identifier
ArangoDB Query Language
Structured Query Language
GraphQL
URI
UNICODE
AQL
SQL
GraphQL
SQL is a query language used for relational databases.
GraphQL is a query language used for graph-data developed by Facebook and published as open source
Rene
https://www.iana.org/assignments/uri-
schemes/uri-schemes.xhtml ;
https://www.w3.org/TR/uri-clarification/
https://www.arangodb.com/docs/stable/aql/
https://graphql.org/
Capability
Artifact Artifact
(no W3C standard and not compatible with SPARQL).
Resource Description Framework RDF RDF is a language to express links between information. Each link in RDF is a triple which contains a Rene https://www.w3.org/RDF/ Is better as LPG?;
subject, a predicate and an object. Hereby the subject and the object represent the information OWL
(identified by URIs) and the predicate (also often identified by URI) describes, why and how those
information is linked together (e.g. "uri://car" "uri://has", "uri://wheels").
Graph daten base
Labeled-Property Graph LPG Labeled-Property Graphs are another way to describe linked data besides RDF. While in RDF a node or link Rene
cannot contain any attributes (those are modelled as new nodes and are then linked to the entity), LPGs
may have attributes for each node and link. Those are modelled as key-value-pairs.
Open Services for Lifecycle Collaboration OSLC The Acronym OSLC stands for Open Services for Lifecycle Collaboration (OSLC) which is an open https://open-services.net/resources/oslc-primer/ Standard
community, to define a set of specifications that enable integration of software development. It is a
uniform infrastructure for interfaces between different systems to evolve, such areas as Application
Lifecycle Management (ALM), Product lifecycle Management (PLM), IT Operations and more. The
intention of OSLC is to make life easier for tool users and tool vendors, to support collaboration, enable
traceability, reporting and automation, with the concept to link artifacts over the engineering lifecycle.
Artifacts (e.g. requirements, testcases, …) are presented as OSLC resources. Each resource can be
manipulated using HTTP methods and can be retrieved and displayed as an RDF representation. RDF/XML
is the most common representation, other formats like JSON or HTML are also used. It is a neutral
interface with advantages of flexibility, expandability, openness and free availability.
Representational State Transfer REST The REST (Representational State Transfer) technology is software architectural style that defines a set of Technology
constraints to be used for creating Web services. Web services that conform to the REST architectural
style, called RESTful Web services, provide interoperability between computer systems on the Internet.
RESTful Web services allow the requesting systems to access and manipulate textual representations of
Web resources by using a uniform and predefined set of stateless operations. Other kinds of Web
services, such as SOAP Web services, expose their own arbitrary sets of operations.
(https://en.wikipedia.org/wiki/Representational_state_transfer)
Standards for Eng. specific data exchange
Requirements Requirements Interchange Format ReqIF https://www.omg.org/spec/ReqIF/About-ReqIF/ Standard
STandard for the Exchange of Product model STEP https://www.prostep.org/projekte/step- Standard
data benchmark/
Mechanics Data
Jupiter Tessellation JT https://www.prostep.org/projekte/jt-workflow- Standard
forum/
Requirements
Intermediate Data Format IDF www.simplifiedsolutionsinc.com
https://www.simplifiedsolutionsinc.com/images/
Electronics Data
Methods
idf_v40_spec.pdf
Internet Data Exchange IDX www.prostep.org ??
Other Buzzwords / and Use Cases
Microservices is Architecture Syle
always based on REST
Microservices are an architectural pattern of information technology where are processes are decoupled
and doing individual Services. Each process communicates with each other with language-independent
programming interfaces. These enables an independent development and modular design of software
applications. Microservices can be implemented using different programming languages, databases,
hardware and software environment, depending on what fits best. They are organized around business
capabilities. The communication is often over a network to fulfil a goal using technology- agnostic
protocols such as HTTP. (https://de.wikipedia.org/wiki/Microservices)
Data analytics / (Big Data)
Digital Twin
IoT
Cloud Service
Open Source
Argument Reality
Visualization
Visualization Standards
Semantics Analytics / Semantic Search
Runtime / Realtime Data
Strategy
Scenarios Use cases
User Guideline Ontology Modelling Guideline
Demonstrator
© prostep ivip e.V. 9 September 2020 Collaborative Systems Engineering, Peter Gerber – prostep ivip Symposium 2020 16Conclusion © prostep ivip e.V. 9 September 2020 Collaborative Systems Engineering, Peter Gerber – prostep ivip Symposium 2020 17
Strong through Collaboration in every aspect
OEM
Join us!
Tier 1 SysML Workflow & Implementer Forum
Model-based cross-company collaboration
Interdisciplinary Collaboration Framework
Interdisciplinary collaboration
Digital Data Package
Tool/format independent cross-company exchange
Etc.
ReqIF Workflow Forum
Requirements exchange for collaboration
Smart Collaboration enables Smart Products and Services
© prostep ivip e.V. 9 September 2020 Collaborative Systems Engineering, Peter Gerber – prostep ivip Symposium 2020 18Collaborative Systems Engineering
Peter Gerber (Schaeffler Technologies)
© prostep ivip e.V. 9 September 2020 Collaborative Systems Engineering, Peter Gerber – prostep ivip Symposium 2020 19You can also read
