2. Sermantics2015
Outline
2
• The company
• Industry 4.0
• „Semantic technologies as key enabler“
• Influence for documentation processes
• Use case
• Starting position
• Requirements
• Solution
• Summary / Lessons learned
4. Sermantics2015
Products in the age of industry 4.0
4
• More versions of the same product
• Lot size 1
• Cyber-Physical systems
• Semantic product memory
• Semantic technolgies as key
technology for the approach
• Semantic layers to connect product
properties with business and
manufacturing processes
5. Sermantics2015
Documentation in the age of industry 4.0
5
• Individual products need individual
documentations
• Eventually documentation moves from
hierarchical structures to topic oriented
models.
• Metadata can not only be used for the
publication process
• Topic oriented documentation models lilke
DITA are supported by XML-Editors like
Oxygen
6. Sermantics2015
Processes in the age of industry 4.0
6
• „Actionable“ semantic models
• Integration is only half way
• Integration level „knows“ what has to
happen if changes occur
• Service descriptions for
orchestration of individual product
demands
• Vocabulary has to be controlled in
all systems
10. Sermantics2015
Starting position
10
• Increased version diversity
• Many systems involved
during development of
new products
• Requirement engineering
• Source-Code repositories
• PDM-systems
• FrameMaker, LaTex, Word…
• File systems
• No support for
• Reuse
• Change-Management
• Traceability
11. Sermantics2015
Project goals
• Reuse of information
• In all systems
• Usable for engineer and end user documentation
• Traceability and visualization of dependencies
• Consequences of change
• Cockpit for project status and progress
• Simulation of changes in late phase of the project
• State of the project
• Many different users and roles for the system
• Detailed access rights model is necessary
12. Sermantics2015
Basic decisions
• Every documentation has to move to structured XML
• DITA
• Integration of the data is not enough
• Changes, versions and workflows have to be implemented
• Existing systems will not be changed or replaced
• A semantic layer providing access rights and workflow
support ist needed
• Formalize the process of development and documentation
• Harmonize the vocabulary
19. Sermantics2015
Lessons learned
19
• Industry 4.0 scenarios have already arrived in the daily business of
companies
• Semantic models are the (only) way to integrate the structure of different
systems
• Systems involved in the product design, development and
documentation process are able to provide their data at least in
XML (ReqIf, DITA)
• Technical integration is „easy“
• What does „approved“ mean?, What is a version?
• Genereric model allows easy reuse