collaborative systems engineering, peter gerber prostep ivip … · 2020. 9. 29. · microservices...
TRANSCRIPT
© prostep ivip e.V. 23 September 2020 Collaborative Systems Engineering, Peter Gerber – prostep ivip Symposium 2020 1
© prostep ivip e.V. 23 September 2020 Collaborative Systems Engineering, Peter Gerber – prostep ivip Symposium 2020 2
Collaborative Systems Engineering
Peter Gerber (Schaeffler Technologies)
© prostep ivip e.V. 23 September 2020 Collaborative Systems Engineering, Peter Gerber – prostep ivip Symposium 2020 3Thema: Lore Ipsum
Develop a
Product
Develop a
Smart Product
or ServiceChallenge
Smart Products for Tomorrow
Yesterday Today Tomorrow
source: Daimler
Product & Technique Emotions & Function Mobility & Services
source: Daimlersource: Daimler source: Daimler
© prostep ivip e.V. 23 September 2020 Collaborative Systems Engineering, Peter Gerber – prostep ivip Symposium 2020 4Thema: Lore Ipsum
Masterplan for Co Action
Soccer: Industry: Integrated Architecture
Improves:
• Transparency
• Collaboration
• Efficiency
• Smart Functionality
• Increased Speed
• Traceability
• Complexity Management
© prostep ivip e.V. 23 September 2020 Collaborative Systems Engineering, Peter Gerber – prostep ivip Symposium 2020 6
SysML as central structure of the smart product
SysML Workflow Forum
© prostep ivip e.V. 23 September 2020 Collaborative Systems Engineering, Peter Gerber – prostep ivip Symposium 2020 7
Specification
and
Requirements
Input/Output
Parameter
SysML as central Element of the Product Architecture
Engineering
PartnerCustomer High Level Model
Detailed Model
SysML WF Forum: Establish Seamless Industrial-Level Collaboration using
model-based Systems Engineering to support handling of Complexity
Product Model
source: Daimler
source:Schaeffler
Functions & Interfaces
Decomposition
Detailing
© prostep ivip e.V. 23 September 2020 Collaborative Systems Engineering, Peter Gerber – prostep ivip Symposium 2020 8
Company
Focus on High Prioritised Use CasesIncluding internal and external Collaboration
SysML Authoring
Requirements
Management/
-Engineering
Test
Management„SysML – V&V“„SysML - RQM“
Partner SysML Authoring
„Model Exchange“
„SysML - RQM“
Requirements
Management/
-Engineering
„SysML - RQM“
Test
Management„SysML – V&V“
„SysML – V&V“
© prostep ivip e.V. 23 September 2020 Collaborative Systems Engineering, Peter Gerber – prostep ivip Symposium 2020 9
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. 23 September 2020 Collaborative Systems Engineering, Peter Gerber – prostep ivip Symposium 2020 10
Reference Process / Workflow:
Requirements Management supported by SysMLUse Cases and Requirements regarding technical solutions (Result of WP6)
Linking- and exchange process
In collaboration with
In Work
• Description of Minimal Set of
Information for Model- and Link
Exchange
• Configuration and Release
Management
© prostep ivip e.V. 23 September 2020 Collaborative Systems Engineering, Peter Gerber – prostep ivip Symposium 2020 11
SysML Models and Verification & ValidationRequirements 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. 23 September 2020 Collaborative Systems Engineering, Peter Gerber – prostep ivip Symposium 2020 12
From Documentation to PractiseEstablish SysML Implementor Forum January 2021
SysML WF SysML IF
Processual
interoperabilityTool
interoperability
WFIF
Chair (Industry Rep.)
Collaboration
Definition of reference process,
requirements and test cases
Evaluation of alternative solutions
implementation of a demonstrator
Chair (Industry Rep.)Requirements
Backlog
Solutions &
Demonstrators
© prostep ivip e.V. 23 September 2020 Collaborative Systems Engineering, Peter Gerber – prostep ivip Symposium 2020 13
Mastery of a distributed product structure
Interdisciplinary Collaboration Framework Forum
© prostep ivip e.V. 23 September 2020 Collaborative Systems Engineering, Peter Gerber – prostep ivip Symposium 2020 14
Distributed 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. 23 September 2020 Collaborative Systems Engineering, Peter Gerber – prostep ivip Symposium 2020 15
Interdisciplinary MBSE Collaboration Frameworkprostep ivip project: 2020-2023
WP1Methods, Use cases &
Requirements
WP3
Technologies
WP4Proof Of Concept / Vendors
Demonstrators
WP5Synthesis & Communication
WP2
DatamodelProduct Model
Domain Collaboration Tool
Domain
Domain
Domain
Framework Methods + Capabilities + Data Architecture + IT
Sub - System
Traces
© prostep ivip e.V. 23 September 2020 Collaborative Systems Engineering, Peter Gerber – prostep ivip Symposium 2020 16
Interdisciplinary Collaboration Framework Approach
Principles / Capabilities / Enablers
List for Technologies and Standards
Domain / Topics Sub Topic Name Short Description Member of Commission ICF Expert Source Alternative Type (Technology/ Standard/…) Relation Relevance Review
Ontology
Web Ontology Language OWL 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.
https://www.w3.org/OWL/
Eclipse Modeling Framework EMF Davy https://www.eclipse.org/modeling/emf/
Meta Object Facility MOF Davy https://www.omg.org/mof/
Knowlage Graph DesignSpace 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.
Davy DesignSpace
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
SysML SST
Damun, Davy https://sysml.org/ Standard
(Data Exchange Formats) / Representation
Open Data Protocol OData Related to these the OData (Open Data Protocol) is an ISO/IEC approved, OASIS standard that defines a set
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.
https://www.odata.org REST
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
between two nodes, like "<human> has exactly one <mother>") ("What XSD is for XML, SHACL is for RDF.")
https://www.w3.org/TR/shacl/
uniform resource identifier URI https://www.iana.org/assignments/uri-
schemes/uri-schemes.xhtml ;
https://www.w3.org/TR/uri-clarification/
UNICODE
ArangoDB Query Language AQL https://www.arangodb.com/docs/stable/aql/
Structured Query Language SQL SQL is a query language used for relational databases. Rene
Graph DataGraphQL GraphQL GraphQL is a query language used for graph-data developed by Facebook and published as open source
(no W3C standard and not compatible with SPARQL).
https://graphql.org/
Resource Description Framework RDF RDF is a language to express links between information. Each link in RDF is a triple which contains a
subject, a predicate and an object. Hereby the subject and the object represent the information
(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").
Rene https://www.w3.org/RDF/ Is better as LPG?;
OWL
Labeled-Property Graph LPG Labeled-Property Graphs are another way to describe linked data besides RDF. While in RDF a node or link
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.
Rene
Open Services for Lifecycle Collaboration OSLC The Acronym OSLC stands for Open Services for Lifecycle Collaboration (OSLC) which is an open
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.
https://open-services.net/resources/oslc-primer/ Standard
Representational State Transfer REST The REST (Representational State Transfer) technology is software architectural style that defines a set of
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)
Technology
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
data
STEP https://www.prostep.org/projekte/step-
benchmark/
Standard
Jupiter Tessellation JT https://www.prostep.org/projekte/jt-workflow-
forum/
Standard
Intermediate Data Format IDF www.simplifiedsolutionsinc.com
https://www.simplifiedsolutionsinc.com/images/
idf_v40_spec.pdf
Internet Data Exchange IDX www.prostep.org ??
<More from DDP>
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 Standards
Semantics Analytics / Semantic Search
Runtime / Realtime Data
Linking Data
Graph daten base
Mechanics Data
Electronics Data
Visualization
Available Technologies
Use cases Scenarios
Requirements
ArtifactProcess
ArtifactCapability
Artifact
is related to
Harmonized Artifact-/Informationmodel
Strategy
OntologyUser Guideline Modelling Guideline
SysML
Methods
Demonstrator
© prostep ivip e.V. 23 September 2020 Collaborative Systems Engineering, Peter Gerber – prostep ivip Symposium 2020 17
Conclusion
© prostep ivip e.V. 23 September 2020 Collaborative Systems Engineering, Peter Gerber – prostep ivip Symposium 2020 18
Strong through Collaboration in every aspect
Join us!
Interdisciplinary Collaboration FrameworkInterdisciplinary collaboration
SysML Workflow & Implementer ForumModel-based cross-company collaboration
Digital Data PackageTool/format independent cross-company exchange
ReqIF Workflow ForumRequirements exchange for collaboration
OEM
Tier 1
Etc.
Smart Collaboration enables Smart Products and Services
© prostep ivip e.V. 23 September 2020 Collaborative Systems Engineering, Peter Gerber – prostep ivip Symposium 2020 19
Collaborative Systems Engineering
Peter Gerber (Schaeffler Technologies)
© prostep ivip e.V. 23 September 2020 Collaborative Systems Engineering, Peter Gerber – prostep ivip Symposium 2020 20
Q&A (1)
You mentioned several prostep ivip project groups, how do you ensure, that the different projects are working towards a common goal?
On the Project Management level we have common meetings regarding Goals, Archtitecture and Content. Beside that we have several Members that are engaged in different project groups.
In our MBE project using NX tool, tested the neutral formats STEP and JT with PMI having atleast one section view. We faced some issues with data loss of PMIs particularly related to cylindrical geometry, hole callouts, Radial dimensions, GD&T data and special symbols. Any best practices?
I would like to address this Question to the specialists of the JT WF Forum and the Digital Data Package with their Focus on neutral Formats and Data exchange.
What was meant by a "German Requirement Book" for the collaboration with GfSE?
We collect our Requirements and Expectations regarding SysML Tool support and Industrial Usage. Most of these are addressed to our Implementor Forum. But some of them (Focus on Collaboration, Configuration-Release and Change Management) should be considered at INCOSE and OMG. So we are in close Collaboration with GfSE to harmonize our Requirements and to address them to INCOSE and OMG.
The whitepaper/recommendation is also available for participants of this meeting? (I am no IVIP member)
Yes! After the final release and layout the recommendation will be published on the ProSTEP IVIP internet sites for free.
© prostep ivip e.V. 23 September 2020 Collaborative Systems Engineering, Peter Gerber – prostep ivip Symposium 2020 21
Q&A (2)
Is the mentioned tool chain (PTC, Contact, Aras etc) planned to be cloud ready e.g. Microsoft Azure? Do
you plan to consider SW DevOps as well?
The existing demonstrators of the federated architecture were built in cloud systems and so the links connected different cloud solutions from different vendors, and it works.
SW DevOPS is one part of our considered principles at the ICF.
How do you work together with your partners in the model exchange. Do they use a collaboration
platform, or do they use their own tools and exchange different data files in your collaboration
framework?
Today the exchange of models with our partners follows project and company specific formats and ways of Exchange. This heterogenous Exchange is our motivator to engage in the ProSTEP IVIP Project groups
What is the status of the distributed product structure today ? is this vendor specific or are any standards in play ?
A vendor specific approach makes no sense from my point of view. The big advantage of a federated architecture is to use for each discipline the best in class tool for each Discipline. So its important to focus on the technologies and principles to enable a flexible vendor independent Tool architecture. Identify and describie the Rail guards and prerequisites is exactly our focus at the ICF but we have just started.