OpenSAP Plm1-1 Week 6 All Slides

You might also like

Download as pdf or txt
Download as pdf or txt
You are on page 1of 85

Week 6: Get Started and Technical Foundation

Unit 1: SAP PLM and SAP Enterprise Product


Development Architecture
SAP PLM and SAP Enterprise Product Development architecture
Introduction – Solution portfolio and architecture considerations

PLM in ERP and SAP Enterprise Product SAP Teamcenter by Siemens


SAP S/4HANA as the system Development (EPD) as the system or other partner solutions
of record and downstream of differentiation and innovation for to extend and complement
business process integration. product development as native the SAP PLM portfolio.
Including SAP ECTR and PLM cloud PLM.
system integration(s).

ERP,
Cloud-Native SAP S/4HANA Modular Cloud Closed-Loop New
Architecture and Services Processes Technologies
Integrations

© 2023 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 2


SAP PLM and SAP Enterprise Product Development architecture
Solution overview

SAP Enterprise Product Development Projects


Documents
Systems Engineering EPD Foundation – Intelligent Handover
PLM Core Objects ….
Connected Products Configuration
PLM Product Version Management
Partner Solutions
Collaboration Specification
PLM BOM Version Management
Visual Enterprise ….
Baseline
Product Cockpit
Specification

… SAP HANA Cloud
Identity Authentication
Possible Authoring
Service
Systems EPD Integration Connectivity Service**
Service Launchpad
CAD CAD Open UI5 and SAP Fiori
BAPI / RFC/ Public OData APIs for S/4
ECTR CAD
Client
BOM Manufacturing/
Document PEO
Management
Change Variant
Management Configuration
Equipment/ & Others in Future …
Asset

External PLM PLM Domain PLM System …
systems* Model Integration(s) PLM and related objects

* for example Siemens Teamcenter ERP, SAP S/4HANA On-Premise, SAP S/4HANA Cloud SAP Cloud Solutions

© 2023 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC ** SAP Connectivity service helps to connect SAP BTP applications to other Internet resources or to on-premise 3
systems running in isolated networks
SAP PLM and SAP Enterprise Product Development architecture
Connecting distributed landscapes – PLM system integration(s) (PLMSI) and SAP ECTR

1. PLM system integration(s) for external PLM systems SAP Enterprise Product Development

CAD CAD
▪ This is implemented in an add-on component and relevant EPD Integration Service
2
for ERP and SAP S/4HANA integrations. ECTR CAD
▪ External PLM system integration(s) (inbound and Client
3
outbound)
− PLMSI uses a common meta domain model to integrate 1
External PLM PLM Domain PLM System
SAP with external PLM systems. The existing integration PLM Objects
systems Model Integration(s)
is with Siemens Teamcenter. This is achieved by enabling
REST services across the products.
ERP, SAP S/4HANA on-premise, cloud

2. PLM systems integration(s) for EPD applications (inbound)* 3. SAP Engineering Control Center (ECTR)*

▪ This is achieved by a set of OData APIs which are internal ▪ SAP ECTR is SAP’s strategic platform to integrate authoring tools like mechanical CAD
to PLM applications and help to exchange required data or electrical CAD systems.
across to EPD applications. ▪ The client can connect to CAD systems and transfer enterprise-relevant data to SAP and
▪ These services are ABAP-based OData APIs reading and also hold a reference to the data.
writing (planned) PLM objects in ERP and SAP S/4HANA. ▪ Objects like documents, material master, or bill of material could be replicated using the
▪ Objects like product, bill of material, or documents could be client.
exchanged.

* For more information see


▪ openSAP PLM 1-1 course, week 3 unit 6: “End-to-End Processes with PLM System Integration(s)”
▪ openSAP PLM 1-1 course, week 3 unit 4: “Manage and Design Products with SAP Engineering Control Center”
© 2023 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 4
SAP PLM and SAP Enterprise Product Development architecture
Connecting distributed landscapes – EPD integration service and SAP S/4HANA offerings
SAP Enterprise Product Development
SAP Business Technology Platform (BTP)
EPD Applications
BTP Applications
R
R

EPD Integration Service Queue

R R
Public APIs on API Hub R

ERP / SAP S/4HANA On-Premise & Cloud SAP S/4HANA On-Premise & Cloud RAP Events

PLM System Integration(s) Service PLM Objects


Bill of Change Change
R «
Material Master Record
PLM Objects
(SAP ERP / SAP S/4HANA On-Premise /
SAP S/4HANA Cloud planned)

EPD Integration Service SAP S/4HANA Offerings


▪ The EPD integration service acts as an integration component for data ▪ SAP S/4HANA inbound
exchange from ERP or SAP S/4HANA to EPD. − This should in general use published OData APIs. Additionally the PLM
▪ The service understands the domain of the EPD entities and help to system integration(s) component would assist for EPD-specific data
exchange ERP or SAP S/4HANA data towards EPD applications. exchanges.
▪ All EPD applications are expected to rely on this service for business and ▪ SAP S/4HANA outbound
data integrity of the core entities during data exchange with ERP or SAP − The preferred channel for integration is via published business events
S/4HANA . or RAP events depending on the release on which they are available.
▪ The APIs are a set of OData APIs acting as an integration component for − This preference also helps in the loose coupling of APIs and prevents
internal communications within SAP landscapes. maintenance across SAP S/4HANA releases.
− Outbound channels via DRF enabled for objects like bill of material.

© 2023 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 5


SAP PLM and SAP Enterprise Product Development architecture
Primary frameworks in use

SAP Cloud Application Programming Model ABAP RESTful Application Programming Model

Abbreviations in use:
▪ A2X: Application to “unspecified client” service, a stateless synchronous service for UI consumption
▪ CDS: Core Data Services, a preferred data exposure artifact with possibilities to model metadata information.
▪ SDK: Software Development Kit
© 2023 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 6
SAP PLM and SAP Enterprise Product Development architecture
Key takeaways

Summary
▪ The overall SAP PLM solution architecture is designed for optimal process
support and bridging of public cloud, private cloud and on-prem solution
components to protect customers’ IT investments
▪ SAP connects different landscapes with each other and ensures a smooth
data exchange
▪ To connect SAP EPD to SAP S/4HANA or ECC 6.0 backend, no extra
middleware is needed, the integration is done via EPD integration service /
OData API calls
▪ SAP ECTR enables customers to connect to a multitude of CAD systems while
SAP PLMSI is the integration enabler to external 3rd party PLM systems

Further Information
▪ Architecture overview in the SAP EPD Administration Guide here
▪ See also “API Documentation” section in https://help.sap.com/docs/PLM_EPD
or https://api.sap.com/package/SAPEnterpriseProductDevelopmentAPIs/all

© 2023 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 7


Thank you.
Contact information:

open@sap.com
Follow all of SAP

www.sap.com/contactsap

© 2023 SAP SE or an SAP affiliate company. All rights reserved.


No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of
SAP SE or an SAP affiliate company.
The information contained herein may be changed without prior notice. Some software products marketed by SAP SE and its
distributors contain proprietary software components of other software vendors. National product specifications may vary.
These materials are provided by SAP SE or an SAP affiliate company for informational purposes only, without representation or
warranty of any kind, and SAP or its affiliated companies shall not be liable for errors or omissions with respect to the materials.
The only warranties for SAP or SAP affiliate company products and services are those that are set forth in the express warranty
statements accompanying such products and services, if any. Nothing herein should be construed as constituting an additional
warranty.
In particular, SAP SE or its affiliated companies have no obligation to pursue any course of business outlined in this document or
any related presentation, or to develop or release any functionality mentioned therein. This document, or any related presentation,
and SAP SE’s or its affiliated companies’ strategy and possible future developments, products, and/or platforms, directions, and
functionality are all subject to change and may be changed by SAP SE or its affiliated companies at any time for any reason
without notice. The information in this document is not a commitment, promise, or legal obligation to deliver any material, code, or
functionality. All forward-looking statements are subject to various risks and uncertainties that could cause actual results to differ
materially from expectations. Readers are cautioned not to place undue reliance on these forward-looking statements, and they
should not be relied upon in making purchasing decisions.
SAP and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered
trademarks of SAP SE (or an SAP affiliate company) in Germany and other countries. All other product and service names
mentioned are the trademarks of their respective companies.
See www.sap.com/trademark for additional trademark information and notices.
Week 6: Get Started and Technical Foundation
Unit 2: SAP Enterprise Product Development:
Identity and User Management
SAP Enterprise Product Development: identity and user management
Introduction

Target of the session:


▪ Get a basic understanding of the SAP Enterprise
Product Development authorization concept
▪ Understand the relation between user groups,
SAP BTP role collections, and collaboration for SAP
Enterprise Product Development
▪ Learn how the Manage Teams app can help to
manage SAP Enterprise Product Development user
assignments

© 2023 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 2


SAP Enterprise Product Development: identity and user management
Disclaimer and general considerations

▪ This session shows general possibilities on how to


manage access for the collaboration scenario in
SAP Enterprise Product Development.
▪ This presentation shows a general perspective and
possibilities only. It does not include all details
required for the setup of the same. It is highly
recommended to refer to the official SAP
documentation for the respective SAP products.
▪ Furthermore, it is recommended to have a detailed
planning session with a specific security consultant
to discuss the outlined possibilities in the context of
your organizational boundaries.

© 2023 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 3


SAP Enterprise Product Development: identity and user management
Clarifying some generic terms

Identity Provider (IdP) – a system or entity which manages digital identity information and is used
to provide or remove privileges. Organizations or companies typically use an IdP to allow their
employees and users to connect to different resources and applications.

SAP Cloud Identity Services, Identity Authentication is a public cloud service for secure
authentication and single sign-on for SAP cloud and on-premise applications. It can act as an
identity provider itself or be used as a proxy to integrate with an existing single sign-on
Infrastructure of a customer.

SAP BTP Role Collection – You can maintain application roles and role collections, which can be
used in user management. Role collections enable you to group together the roles you create using
the SAP BTP cockpit. The role collections you define can be assigned to user groups containing
users logging on with SAML 2.0 assertions.

© 2023 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 4


SAP Enterprise Product Development: identity and user management
SAP Enterprise Product Development authorization concept – Overview
SAP Business Technology Platform
▪ An identity provider that has a Corporate IDP Identity Authentication Sub Account
custom trust configuration in Service
SAP BTP. Security
Role Collection
▪ The identity provider provides
Role
the user groups using SAML User User CollaboriationAdminRC
Collection CollaborationUserInternalRC
assertion attributes. Group Group Mapping CollaborationUserExternalRC
CollaborationDPPAdmin
▪ It is required to map user * *
groups to role collections in
SAP BTP. Role collections
need to be set up/mapped as a SAP Enterprise Product
* * Development
one time effort.
(Shadow) Collaboration
▪ The role collection as a User trust
User
reusable element contains the Participants
authorizations that are
Application
necessary for this user group. User Group
trust
▪ Role collections on the other
hand are available within SAP Email
EPD for the collaboration
scenario as application user
groups. Document
Management Service
Disclaimer: this slide shows an illustrative view. It might not contain all details and
is based on current information available and EPD release 2211. Some future
innovations are based on roadmap items, which are subject to change.

© 2023 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 5


SAP Enterprise Product Development: identity and user management
Example usage of user groups

Security Enterprise Product Development


IdP / SAP IAS
Collaboration – CORP-ALL
User Groups Role Collection Mapping Role Collection
Participants
CORP From To EpdAdminRC
EPD-ADM EpdAdminRC EpdUserIntRC Collaboration
CORP-A EpdUserExtRC
EpdDPPAdmin
User Groups
CORP-B EPD-USR-INT EpdUserIntRC
CORP CORP
EPD-ADM EPD-USR-EXT EpdUserExtRC CORP-A
EPD-DPP-ADM EpdDPPAdmin CORP-B
EPD-USR-INT EPD-ADM
EPD-USR-EXT
Collaboration – CORP-P1
EPD-DPP-ADM
Participants

Users Collaboration
User Groups
user1
CORP-A
user2

SAP Business Technology Platform


Collaboration – CORP-P2

Participants

Collaboration
User Groups
Disclaimer: this slide shows only an illustrative CORP-B
view and might not contain all details. It is based on
current information available and SAP EPD release
2211.

© 2023 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 6


SAP Enterprise Product Development: identity and user management
Manage Teams app

▪ A team is a group of users that is created for different use cases


and works as a unit for user management.
▪ You can customize different teams of users, add or remove users
from the teams, and manage capability rules.
▪ Data created in Manage Teams will automatically synchronize with
Security in SAP BTP.
i.e Teams in Manage Teams = Role Collection in SAP BTP Security.
▪ In the Manage Teams app, the Teams table lists all the created
teams. Use the filters on the top of the page to set search criteria.
Choose the Settings button in the top-right corner of the table to
adjust the table display settings.
▪ As part of the process of creating a role collection, you should
consider a proper role collection structure fitting organizational
requirements. Using Manage Capability Rules, conditions can be
used to limit the available role collections as group assignments on
collaboration level in SAP Enterprise Product Development.
© 2023 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 7
SAP Enterprise Product Development: identity and user management
Manage Teams app

Teams Management Manage Capability Rules User Group Assignment


▪ The Manage Teams app is used to ▪ In this example only user groups ▪ Based on Manage Capability Rules,
customize different teams of users, starting with “DL” or “SAP” and available role collections are limited as
add or remove users from the teams, ending with “GROUP” shall be group assignments on collaboration
and manage capability rules. available for collaboration level in SAP EPD.
assignment

© 2023 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 8


SAP Enterprise Product Development: identity and user management
Demo – Role collections and collaborations in SAP Enterprise Product Development

© 2023 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 9


SAP Enterprise Product Development: identity and user management
Key takeaways

Summary
▪ An identity provider (IdP) is used to provide user and user
group assignments which have to be mapped on SAP BTP
level to role collections for SAP EPD usage
▪ Role collections are available as user groups for
collaboration assignments inside SAP EPD. Manage
Capability Rules can be used to restrict user group
availability on collaboration level
▪ Consider structuring user group / role collections for
collaboration use
▪ Manage Teams app to manage role collection in SAP BTP
and user assignments. Also capability rules to restrict user
group (role collections) accessible inside each SAP EPD
capability
▪ SAP provides flexibility for customers to work with an
existing identity provider (e.g. from cloud hyperscalers) or
with SAP’s own identity provider
© 2023 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 10
Thank you.
Contact information:

open@sap.com
Follow all of SAP

www.sap.com/contactsap

© 2023 SAP SE or an SAP affiliate company. All rights reserved.


No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of
SAP SE or an SAP affiliate company.
The information contained herein may be changed without prior notice. Some software products marketed by SAP SE and its
distributors contain proprietary software components of other software vendors. National product specifications may vary.
These materials are provided by SAP SE or an SAP affiliate company for informational purposes only, without representation or
warranty of any kind, and SAP or its affiliated companies shall not be liable for errors or omissions with respect to the materials.
The only warranties for SAP or SAP affiliate company products and services are those that are set forth in the express warranty
statements accompanying such products and services, if any. Nothing herein should be construed as constituting an additional
warranty.
In particular, SAP SE or its affiliated companies have no obligation to pursue any course of business outlined in this document or
any related presentation, or to develop or release any functionality mentioned therein. This document, or any related presentation,
and SAP SE’s or its affiliated companies’ strategy and possible future developments, products, and/or platforms, directions, and
functionality are all subject to change and may be changed by SAP SE or its affiliated companies at any time for any reason
without notice. The information in this document is not a commitment, promise, or legal obligation to deliver any material, code, or
functionality. All forward-looking statements are subject to various risks and uncertainties that could cause actual results to differ
materially from expectations. Readers are cautioned not to place undue reliance on these forward-looking statements, and they
should not be relied upon in making purchasing decisions.
SAP and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered
trademarks of SAP SE (or an SAP affiliate company) in Germany and other countries. All other product and service names
mentioned are the trademarks of their respective companies.
See www.sap.com/trademark for additional trademark information and notices.
Week 6: Get Started and Technical Foundation
Unit 3: SAP Enterprise Product Development:
Onboarding Process
SAP Enterprise Product Development: onboarding process
Introduction

Getting started with SAP Enterprise Product


Development as a public cloud system
1. Welcome Email Overview (5 min)
2. Onboarding Overview (10 min)

© 2023 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 2


SAP Enterprise Product Development: onboarding process
Welcome to SAP Enterprise Product Development

Welcome & Introduction


► Start with understanding access information
in the welcome email – the account What comes next
administrator will receive this email after
SAP Enterprise Product Development is
available for the account.

Learn more

How to get help

Influence the product roadmap

© 2023 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 3


SAP Enterprise Product Development: onboarding process
Onboarding overview

Personas Steps
“As a system administrator, I want to set up the required
configurations on my subaccount on SAP Business System Administrator sets up basic SAP Business
Technology Platform to start implementing SAP Enterprise Technology Platform configurations.
Product Development.”
System Administrator sets up role configurations for
SAP Enterprise Product Development.

System Administrator sets up trust configurations


for identity provider (IdP) and SAP Business
Technology Platform configurations.

Business Administrator sets up connectivity


configurations on SAP Business Technology Platform.

Business Administrator sets up custom


configurations as per business requirements.

“As a business administrator, I want to define Administrators set up integrations to other


business rules and configurations to enable sharing of applications and systems.
product data with suppliers and contract manufacturers.”

© 2023 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 4


SAP Enterprise Product Development: onboarding process
Onboarding overview

Steps Overview

Subscribing to SAP Connectivity


User Management IdP Business Other Integration &
Enterprise Product Configuration
Setup Configuration Configuration Extensibility
Development Setup

Start End

I want to set up my I want to set up I want to set up I want to set up I want to configure I want to integrate
global account in users and roles for trust configuration connectivity Enterprise Product Enterprise
BTP and activate Enterprise Product for Enterprise configurations for Development based Product
Enterprise Product Development Product Enterprise Product on my business Development with
Development on Development Development requirements other applications
my subaccount capabilities and systems

Legend: SAP Business Technology Platform, Identity Provider and SAP Enterprise Product Development

© 2023 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 5


SAP Enterprise Product Development: onboarding process
Find out more…

More Information
▪ https://www.youtube.com/watch?v=iCGmBi_Kk58
Watch this YouTube video to learn how to subscribe to SAP Enterprise Product Development applications
▪ Getting Started with SAP Enterprise Product Development
Technical article blog from SAP Enterprise Product Development expert
▪ Considerations for Administrators Implementing SAP Enterprise Product Development
Technical article blog from SAP Enterprise Product Development expert
▪ SAP Enterprise Product Development Product Page
Get acquainted with the software and familiarize yourself with its capabilities, pricing, and use cases
▪ SAP Enterprise Product Development Help Portal
Find official product documentation, user guide, release notes, and more
▪ SAP Enterprise Product Development Continuous Influence
Suggest improvements to cloud solutions from SAP and most recent technologies directly to the development teams
▪ SAP Enterprise Product Development Community
Learn about new blog posts, featured information, news, releases, and learning opportunities
▪ SAP Note 3109501
Getting Started with SAP Enterprise Product Development – FAQ

© 2023 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 6


SAP Enterprise Product Development: onboarding process
Key takeaways

Summary
▪ Welcome email of SAP Enterprise Product
Development has the details required by an
administrator to set up and get started with the
solution
▪ SAP Enterprise Product Development is a
powerful and highly customizable public cloud
solution hosted and managed via SAP Business
Technology Platform (SAP BTP), and requires
the organization to implement customizations
and integrations according to their business
needs

© 2023 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 7


Thank you.
Contact information:

open@sap.com
Follow all of SAP

www.sap.com/contactsap

© 2023 SAP SE or an SAP affiliate company. All rights reserved.


No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of
SAP SE or an SAP affiliate company.
The information contained herein may be changed without prior notice. Some software products marketed by SAP SE and its
distributors contain proprietary software components of other software vendors. National product specifications may vary.
These materials are provided by SAP SE or an SAP affiliate company for informational purposes only, without representation or
warranty of any kind, and SAP or its affiliated companies shall not be liable for errors or omissions with respect to the materials.
The only warranties for SAP or SAP affiliate company products and services are those that are set forth in the express warranty
statements accompanying such products and services, if any. Nothing herein should be construed as constituting an additional
warranty.
In particular, SAP SE or its affiliated companies have no obligation to pursue any course of business outlined in this document or
any related presentation, or to develop or release any functionality mentioned therein. This document, or any related presentation,
and SAP SE’s or its affiliated companies’ strategy and possible future developments, products, and/or platforms, directions, and
functionality are all subject to change and may be changed by SAP SE or its affiliated companies at any time for any reason
without notice. The information in this document is not a commitment, promise, or legal obligation to deliver any material, code, or
functionality. All forward-looking statements are subject to various risks and uncertainties that could cause actual results to differ
materially from expectations. Readers are cautioned not to place undue reliance on these forward-looking statements, and they
should not be relied upon in making purchasing decisions.
SAP and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered
trademarks of SAP SE (or an SAP affiliate company) in Germany and other countries. All other product and service names
mentioned are the trademarks of their respective companies.
See www.sap.com/trademark for additional trademark information and notices.
Week 6: Get Started and Technical Foundation
Unit 4: SAP Enterprise Product Development:
Backend Integration – Part 1
SAP Enterprise Product Development: backend integration – Part 1
Integration overview

Integration Scenarios

Define Develop Deliver

Integration with Qualtrics to identify


Integration with SAP S/4HANA PLM for Integration with SAP Commerce Cloud for
experience gaps and prioritize
discrete industries (BOMs, 2D & 3D) visual spares & services
needs.

Integration with SAP Enterprise Integration with SAP S/4HANA PLM for Integration with SAP Subscription Billing
Portfolio and Project Management process industries (specifications, to create product-as-a-service business
for collaborative project execution recipe) models
Integration with SAP Ariba Sourcing to Integration with SAP Predictive Asset
exchange product data in RFx process Insights for predictive engineering insights
across the extended enterprise. and maintenance.

Integration with SAP Integrated Business


Integration with SAP Engineering
Planning for Supply Chain for product
Control Center for collaborative design
visualization

Integration with SAP Responsible


Integration with SAP Transportation
Design and Production for legal
Management for 3D visuals
reporting on packaging (planned)

For further information, see also openSAP PLM session “SAP Enterprise Product Development: backend integration – Part 2”

© 2023 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 2


SAP Enterprise Product Development: backend integration – Part 1
Integration with SAP S/4HANA Document Management

Exchange document info record and original (documents) directly from


SAP S/4HANA Document Management into collaboration in EPD

Overview:
▪ Document Management contains document info records and their
originals.
▪ These can be replicated or pushed into collaboration in EPD, and
synchronized back to Document Management.

The integration with SAP DMS enables companies to:


▪ Leverage the DMS integration to collaboration to push all the
relevant documents for the engineering process into collaboration
▪ Bring the original and its related information to the collaboration
(e.g. DIR number, classification data, etc.)
▪ Perform changes to a documents through collaborative reviews
▪ Create or trigger workflows to assign review tasks Product Engineering with Co-Man

▪ Document Management provides the possibility to both push and


pull documents to and from a collaboration

© 2023 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 3


SAP Enterprise Product Development: backend integration – Part 1
Functionalities in DMS while working with SAP Enterprise Product Development

You can perform the following processes in DMS while


working with SAP Enterprise Product Development:
▪ Upload documents from DMS to a collaboration:
– Upload documents and document structures to a
collaboration
– Upload specific file types to a collaboration
– Upload documents immediately or as a background job
▪ Synchronize back the documents from a collaboration to
DMS:
– Create, update, and view documents and document
structures in DMS
– Create document versions in DMS

© 2023 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 4


SAP Enterprise Product Development: backend integration – Part 1
Mandatory configurations in DMS

You need to configure the following:


▪ Define a Profile
– Add an entry each for Determine definitions for
applications per storage category and Assign
groups/user to the profile
▪ Create a Destination
– RFC (SM59) destination to connect to EPD system
▪ Create an OAuth Client Profile
– Set it up to connect to EPD system
– Generate token for authorization code option
– Client credential option is not available for EHP
systems
▪ Maintain the Destination for User Groups
– In Customizing table IPDC_CUST for user, profile,
and destination mapping
© 2023 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 5
SAP Enterprise Product Development: backend integration – Part 1
Integration with SAP Engineering Control Center

Exchange product design and related data directly from


CAD authoring tools for collaborative design

Overview:
▪ SAP Engineering Control Center (ECTR) supports sharing
and exchanging of data such as CAD drawings and
document info records (DIR) between the control center and
collaboration

The integration with SAP Engineering Control


Center enables companies to:
▪ Seamlessly exchange product design files between a CAD
authoring tool to a collaboration in EPD
▪ Perform changes to a product through collaborative design
reviews
▪ Create or trigger workflows to assign design review tasks
▪ Perform redlining markups on 3D visuals in the inbuilt 3D
viewer
© 2023 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 6
SAP Enterprise Product Development: backend integration – Part 1
Functionalities in ECTR while working with SAP Enterprise Product Development

You can perform the following processes in ECTR while working with SAP EPD:
▪ Selection
– In SAP Engineering Control Center, it is possible to select documents for export, which means that individual documents
can be assigned.
– Use the dedicated ‘collaboration workspace’ – a connection to SAP EPD is established and the collaboration workspace
of the current user is determined.
– The user then selects a collaboration workspace or a folder in a collaboration workspace as the export target.
– The assignment is made by selecting the source and target using drag and drop.
▪ Data Export
– The actual export takes place after the source and target have been selected as described above (drag and drop).
– The export functionality explodes the document structure according to the active loading rule and determines the
originals.
– The folders (DIRs) are created as folders and originals are created as files in the SAP EPD collaboration workspace.
– In collaboration, a PDF file is created for assemblies/document structures that reflects the document structure from the
SAP system. The file provides external engineers with information about the assembly structure.
▪ Import
– Re-import documents from a collaborative workspace easily and intuitively.
© 2023 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 7
SAP Enterprise Product Development: backend integration – Part 1
Mandatory configurations in SAP Engineering Control Center

You need to configure the following:


▪ Create a collaboration instance in SAP BTP cockpit
▪ Create a service key for the newly created
collaboration instance in SAP BTP
▪ Update the SAP ECTR configuration from the
service key information in the ECTR environment:
– connection.description
– connection.oauth.url
– connection.oauth.client.id
– connection.oauth.client.secret
– connection.epd.url

© 2023 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 8


SAP Enterprise Product Development: backend integration – Part 1
Introduction to product data collaboration (BOM and order BOM)

Exchange structured product data across the extended enterprise

Overview:
▪ Collaborate on product data such as bills of material (BOM)
and order BOMs, and enable internal and external
stakeholders to propose changes using redlining.

Integration with bill of material enables companies


to:
▪ Retrieve bills of material (BOM) and order BOMs from the
source system
▪ Exchange

© 2023 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 9


SAP Enterprise Product Development: backend integration – Part 1
Functionalities in collaborations for BOM and order BOM

The integration supports the following actions:


▪ Add (Import) Product Data
▪ Reimport Product Data
▪ Remove Product Data
▪ Download Product Data
▪ View Product Data
– Viewing product data in the source system
▪ Add Comments
▪ Set Processing Status
– Setting the processing status of product data records
▪ Perform Redlining (create, edit and delete)
▪ Linking files and folders to shared product data

© 2023 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 10


SAP Enterprise Product Development: backend integration – Part 1
Mandatory configurations

You need to configure the following:


▪ Prerequisites for configuring product data
▪ A system in SAP BTP
▪ An object type in SAP EPD
▪ URL definitions in SAP EPD

© 2023 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 11


SAP Enterprise Product Development: backend integration – Part 1
Key takeaways

This session shows the required configuration for the integration with:
DMS:
▪ The integration with SAP DMS enables companies to:
– Upload required documents from SAP S/4HANA DMS into collaboration
– Communicate efficiently using process-oriented workflows in collaboration
– Perform a safe and secure cloud-based collaborative change management where you
can involve your partners, suppliers, customers, other LoBs
– Synchronize back the revised documents into SAP S/4HANA DMS from collaboration
ECTR:
▪ The integration with SAP Engineering Control Center enables companies to:
– Exchange design data, such as native CAD data or drawings, for external engineers.
Once the external processor has finished processing the design data, the data can be
imported back into SAP Engineering Control Center
– Communicate efficiently using different communication methods in a collaboration such
as commenting, exchanging product data, and redlining markups
– Share accurate product data directly from the product design source
BOM:
▪ This enables companies to exchange BOMs in collaborations with their contract
manufactures

© 2023 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 12


Thank you.
Contact information:

open@sap.com
Follow all of SAP

www.sap.com/contactsap

© 2023 SAP SE or an SAP affiliate company. All rights reserved.


No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of
SAP SE or an SAP affiliate company.
The information contained herein may be changed without prior notice. Some software products marketed by SAP SE and its
distributors contain proprietary software components of other software vendors. National product specifications may vary.
These materials are provided by SAP SE or an SAP affiliate company for informational purposes only, without representation or
warranty of any kind, and SAP or its affiliated companies shall not be liable for errors or omissions with respect to the materials.
The only warranties for SAP or SAP affiliate company products and services are those that are set forth in the express warranty
statements accompanying such products and services, if any. Nothing herein should be construed as constituting an additional
warranty.
In particular, SAP SE or its affiliated companies have no obligation to pursue any course of business outlined in this document or
any related presentation, or to develop or release any functionality mentioned therein. This document, or any related presentation,
and SAP SE’s or its affiliated companies’ strategy and possible future developments, products, and/or platforms, directions, and
functionality are all subject to change and may be changed by SAP SE or its affiliated companies at any time for any reason
without notice. The information in this document is not a commitment, promise, or legal obligation to deliver any material, code, or
functionality. All forward-looking statements are subject to various risks and uncertainties that could cause actual results to differ
materially from expectations. Readers are cautioned not to place undue reliance on these forward-looking statements, and they
should not be relied upon in making purchasing decisions.
SAP and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered
trademarks of SAP SE (or an SAP affiliate company) in Germany and other countries. All other product and service names
mentioned are the trademarks of their respective companies.
See www.sap.com/trademark for additional trademark information and notices.
Week 6: Get Started and Technical Foundation
Unit 5: SAP Enterprise Product Development:
Backend Integration – Part 2
SAP Enterprise Product Development: backend integration – Part 2
Integration overview

Integration Scenarios

Define Develop Deliver

Integration with Qualtrics to identify


Integration with SAP S/4HANA PLM for Integration with SAP Commerce Cloud for
experience gaps and prioritize
Discrete Industries (BOMs, 2D & 3D) visual spares & services
needs.

Integration with SAP Enterprise Integration with SAP S/4HANA PLM for Integration with SAP Subscription Billing
Portfolio and Project Management Process Industries (specifications, to create Product-as-a-Service business
for collaborative project execution recipe) models
Integration with SAP Ariba Sourcing to Integration with SAP Predictive Asset
exchange product data in RFx process Insights for predictive engineering insights
across the extended enterprise. and maintenance

Integration with SAP Integrated Business


Integration with SAP Engineering
Planning for Supply Chain for product
Control Center for collaborative design
visualization

Integration with SAP Responsible


Integration with SAP Transportation
Design and Production for legal
Management for 3D visuals
reporting on packaging (planned)

For further information, see also openSAP PLM session “SAP Enterprise Product Development: backend integration – Part 1”

© 2023 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 2


SAP Enterprise Product Development: backend integration – Part 2
Integration with SAP Enterprise Portfolio and Project Management and collaboration in EPD

Exchange project development plan and objects across the extended enterprise through collaboration

Overview:
▪ SAP Enterprise Portfolio and Project Management contains projects
and portfolios.
▪ This integration helps to link collaboration to project elements as
object links.

Integration with SAP Enterprise Portfolio and Project


Management enables companies to:
▪ Link project elements from project management to one or more
collaborations using object links
▪ Access linked collaborations from the project element
▪ Create single work items or entire workflows in the collaboration
▪ Assign work items to responsible team members with/without access
to project management
▪ Share related documents and exchange comments in the
collaboration
▪ Monitor the completion of work items in the collaboration
© 2023 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 3
SAP Enterprise Product Development: backend integration – Part 2
Functionalities in SAP PPM while working with collaboration in SAP EPD

Use the object type Collaboration to create an object link


to collaboration in SAP Enterprise Product Development.
This object type supports the following features:
▪ Create one or more collaborations from portfolio objects and
project elements
▪ Assign an existing collaboration to portfolio objects and
project elements
▪ Display header data of linked collaborations in either portfolio
or project element
▪ Navigate and access linked collaborations from portfolio
objects and project elements
▪ Delete linked collaborations from portfolio objects and project
elements
▪ Delete portfolio objects and project elements that have linked
collaborations
© 2023 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 4
SAP Enterprise Product Development: backend integration – Part 2
Working with SAP PPM-related collaborations

While working on collaborations, you can use all the


functionality of the collaboration capability in SAP
Enterprise Product Development. For example:
▪ You can create single work items or entire workflows in
the collaboration.
▪ You can assign work items to the responsible team
members, including external team members with no
access to SAP Portfolio and Project Management.
▪ The portfolio and project manager and team members
can share related documents and exchange comments
in the collaboration.
▪ Team members can complete work items in the My
Inbox app of SAP Enterprise Product Development.
▪ The portfolio and project manager can monitor the
completion of work items in the collaboration.

© 2023 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 5


SAP Enterprise Product Development: backend integration – Part 2
Mandatory configurations in PPM and collaboration

You need to configure the following:


▪ SAP Notes: SAP Portfolio and Project Management:
Configuration Content.
▪ The web server address for the collaboration service
URL and the collaboration UI URL
▪ The OAuth 2.0 client
▪ Maintain the e-mail address for the SAP S/4HANA
user
▪ Configure the EPD systems:
– Create a custom status profile
– Create a custom collaboration type
– Create a reference object

© 2023 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 6


SAP Enterprise Product Development: backend integration – Part 2
Integration with SAP Enterprise Portfolio and Project Management & requirements management

Exchange requirements across the extended enterprise

Overview:
▪ SAP Enterprise Product Development lets you link requirements,
blocks, models and requirement models to SAP Portfolio and
Project Management objects such as portfolio items, project
management project, and project management tasks.

Integration with SAP Enterprise Portfolio and Project


Management enables companies to:
▪ Assign requirements, blocks, models, and requirement models
from portfolio objects and project elements
▪ View the metadata of item, project, and project tasks in
requirements management and systems modeling
▪ For example, if you navigate from a project management project
header, you can view the project name and project number

© 2023 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 7


SAP Enterprise Product Development: backend integration – Part 2
Mandatory configurations in PPM and requirements management

You need to configure the following:


▪ Set up the integration of portfolio objects and
project elements with requirements in SAP EPD
▪ Configuration Guide for SAP Portfolio and Project
Management in SAP Note 3077647

© 2023 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 8


SAP Enterprise Product Development: backend integration – Part 2
Integration with SAP Ariba Sourcing

Share comprehensive product data in RFx processes across the extended enterprise

Overview:
▪ By integrating with SAP Ariba Sourcing, you can enable your
suppliers to access collaborations where you have shared content
related to sourcing objects or RFx (request for quotation, proposal, or
information)
Integration with SAP Ariba Sourcing:
▪ Suppliers can access the shared content related to sourcing objects
or RFx (request for quotation, proposal, or information)
▪ Suppliers can respond to sourcing projects with higher accuracy
▪ Suppliers can reduce the response time for an RFx event (request for
quotation, proposal, or information)
▪ Supports collaborative as well as competitive supplier scenarios
▪ SAP Enterprise Product Development (EPD) complements SAP Ariba
Sourcing for accomplishing a successful RFx project
▪ It is offered as a standard integration option

© 2023 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 9


SAP Enterprise Product Development: backend integration – Part 2
Functionalities in SAP Ariba Sourcing while working with collaboration in SAP EPD

The collaboration is linked to a sourcing project.


This supports the following features:
▪ Suppliers can access the RFx events with the EPD
collaboration link containing the relevant artifacts
▪ Collaboration supports a wide range of artifacts, from
structured data (like – BOM, specification) to
unstructured data, (like – CAD models, pdf) to serve
various kinds of sourcing projects.
▪ You can link relevant collaborations to the SAP Ariba
sourcing project by clicking the standard button
Retrieve Document URLs

© 2023 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 10


SAP Enterprise Product Development: backend integration – Part 2
Mandatory configurations in SAP Ariba Sourcing and collaboration

You need to configure the following:


▪ The destination configured in your subaccount in
SAP BTP
▪ Collaboration type configurations in SAP EPD
▪ Endpoint configuration in SAP Ariba
▪ Integration configuration in SAP Ariba
▪ Authentication mechanism

© 2023 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 11


SAP Enterprise Product Development: backend integration – Part 2
Key takeaways

SAP EPPM and collaboration


▪ The integration with SAP EPPM and collaboration enables companies to:
– Improve the collaboration process and give faster access by linking the project and
collaboration world
– Perform a safe and secure cloud-based collaborative change management where you
can involve your partners, suppliers, customers, other LoBs, for completing and tracking
their part of the task in a project
– Communicate efficiently using process-oriented workflows in collaboration

SAP EPPM and requirements management


▪ The integration with SAP EPPM and requirements management enables companies to:
– Assign requirements, blocks, models, and requirement models from portfolio objects
and project elements

SAP Ariba Sourcing


▪ The integration with SAP EPPM enables companies to:
– Create a collaboration room and invite suppliers managed in SAP Ariba Supplier
Lifecycle and Performance
– Allow suppliers to access collaborations with shared content related to sourcing events
and RFx
© 2023 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 12
Thank you.
Contact information:

open@sap.com
Follow all of SAP

www.sap.com/contactsap

© 2023 SAP SE or an SAP affiliate company. All rights reserved.


No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of
SAP SE or an SAP affiliate company.
The information contained herein may be changed without prior notice. Some software products marketed by SAP SE and its
distributors contain proprietary software components of other software vendors. National product specifications may vary.
These materials are provided by SAP SE or an SAP affiliate company for informational purposes only, without representation or
warranty of any kind, and SAP or its affiliated companies shall not be liable for errors or omissions with respect to the materials.
The only warranties for SAP or SAP affiliate company products and services are those that are set forth in the express warranty
statements accompanying such products and services, if any. Nothing herein should be construed as constituting an additional
warranty.
In particular, SAP SE or its affiliated companies have no obligation to pursue any course of business outlined in this document or
any related presentation, or to develop or release any functionality mentioned therein. This document, or any related presentation,
and SAP SE’s or its affiliated companies’ strategy and possible future developments, products, and/or platforms, directions, and
functionality are all subject to change and may be changed by SAP SE or its affiliated companies at any time for any reason
without notice. The information in this document is not a commitment, promise, or legal obligation to deliver any material, code, or
functionality. All forward-looking statements are subject to various risks and uncertainties that could cause actual results to differ
materially from expectations. Readers are cautioned not to place undue reliance on these forward-looking statements, and they
should not be relied upon in making purchasing decisions.
SAP and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered
trademarks of SAP SE (or an SAP affiliate company) in Germany and other countries. All other product and service names
mentioned are the trademarks of their respective companies.
See www.sap.com/trademark for additional trademark information and notices.
Week 6: Get Started and Technical Foundation
Unit 6: SAP Enterprise Product Development:
Adapting the User Interface
SAP Enterprise Product Development: adapting the user interface
Introduction

Customize and adapt the user interface (UI) in the My Collaborations app

Overview – UI5 flexibility:


▪ Users with the UI5 flexibility role can customize user
interface controls using Adapt UI in the user profile
and manage views (public variant) in the My
Collaborations app
▪ Users can change the user interface of your
applications in an upgrade-safe and modification-
free way

© 2023 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 2


SAP Enterprise Product Development: adapting the user interface
Working with key users’ UI5 flexibility

Users with the UI5 flexibility role can customize the user
interface (UI) under My Collaborations app:
▪ A key user can make UI changes and publish on behalf of end users
– Adapt the UI
– Manage views (variants)
– Save UI changes as drafts
– Manage versions
▪ On releasing the adapted version of the application, the changes are
available for all the end users
▪ UI changes could be:
– Renaming a text on the UI controls, like buttons, labels etc.
– Adding or hiding fields
– Rearranging fields: dragging and dropping UI elements to
rearrange them
– Embedding content to header or section: embed content from
external applications or web sites to your app, e.g. external videos
or maps
© 2023 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 3
SAP Enterprise Product Development: adapting the user interface
Demo

© 2023 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 4


SAP Enterprise Product Development: adapting the user interface
Key takeaways

Summary
▪ A key user can make UI changes and publish on behalf
of end users – Users with the UI5 flexibility role can
customize the user interface (UI) with the My
Collaborations app
▪ Possible things to adapt in the user interface (UI)
– From embedding a map to renaming a button text, etc.
▪ What if you delete something important or even break
the app?
– No worries. Key user adaptation comes with a built-in
safety net.
– It informs you whenever you’re about to do something
that’s worth double-checking: for example, removing
mandatory fields from the UI.
– You can also undo your changes and even discard
them all and reset the UI to the default app.
© 2023 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 5
Thank you.
Contact information:

open@sap.com
Follow all of SAP

www.sap.com/contactsap

© 2023 SAP SE or an SAP affiliate company. All rights reserved.


No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of
SAP SE or an SAP affiliate company.
The information contained herein may be changed without prior notice. Some software products marketed by SAP SE and its
distributors contain proprietary software components of other software vendors. National product specifications may vary.
These materials are provided by SAP SE or an SAP affiliate company for informational purposes only, without representation or
warranty of any kind, and SAP or its affiliated companies shall not be liable for errors or omissions with respect to the materials.
The only warranties for SAP or SAP affiliate company products and services are those that are set forth in the express warranty
statements accompanying such products and services, if any. Nothing herein should be construed as constituting an additional
warranty.
In particular, SAP SE or its affiliated companies have no obligation to pursue any course of business outlined in this document or
any related presentation, or to develop or release any functionality mentioned therein. This document, or any related presentation,
and SAP SE’s or its affiliated companies’ strategy and possible future developments, products, and/or platforms, directions, and
functionality are all subject to change and may be changed by SAP SE or its affiliated companies at any time for any reason
without notice. The information in this document is not a commitment, promise, or legal obligation to deliver any material, code, or
functionality. All forward-looking statements are subject to various risks and uncertainties that could cause actual results to differ
materially from expectations. Readers are cautioned not to place undue reliance on these forward-looking statements, and they
should not be relied upon in making purchasing decisions.
SAP and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered
trademarks of SAP SE (or an SAP affiliate company) in Germany and other countries. All other product and service names
mentioned are the trademarks of their respective companies.
See www.sap.com/trademark for additional trademark information and notices.
Week 6: Get Started and Technical Foundation
Unit 7: Technical Considerations for Connected
Products/Digital Twins
Technical considerations for connected products/digital twins
Introduction

Connected products in SAP Enterprise Product Development, EPD-CP, is a physics-based digital


twin solution that uses streaming IoT data from sensors and control and supervisory systems as
input to produce online and real-time condition data and direct insight into the system state and
behavior.

Creating various engineering simulation models:

[Example] [Example]
Physical Equipment Engineering simulation models Calculated Damage
Parameter
ANSYS System simulations
Physics-based models FEDEM FEA

Open Modellica CFD

Python Statistics
Data-driven
Scikit learn Trend/Forecast
models
Failure detection
TensorFlow

© 2023 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 2


Technical considerations for connected products/digital twins
Connected products – Master data

Templates
Compiles a set of indicators/
indicator groups (e.g. sensors/
channels) into a common
template
Models
Model is an abstract representation
based on a template with additional Indicators for
information about an object
measured values
Grouped in
Equipment indicator groups
Equipment is a physical Indicators for
instance of a model calculated values
© 2023 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 3
Technical considerations for connected products/digital twins
Connected products – Overview

Early Warnings Instances


Bind the simulation
View alerts and
model to equipment
situation replays

Product Monitoring
Templates
Monitor result plots
Deploy engineering
simulation models
© 2023 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 4
Technical considerations for connected products/digital twins
Connected products – Templates
adding simulation model takes in INPUT dataframe
(indicator group)

input
template indicators
name

ready if
successful

output
defined indicators
input and return OUTPUT
output in dataframe
the model (indicator group)
indicator groups asset central
taken from the model mapping template
between model
© 2023 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC and asset central 5
Technical considerations for connected products/digital twins
Connected products – Instances

instance
name

instance
status

download
logs

instance
status

selected template selected equipment


data mapping between model
© 2023 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 6
and asset central
Technical considerations for connected products/digital twins
Connected products – Product monitoring

equipment
name plot types

canvas add canvas

© 2023 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 7


equipment – indicator group – indicator
Technical considerations for connected products/digital twins
Connected products – Early warnings

situation
replay/
time series
filtering

alerts

replay
© 2023 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 8
Technical considerations for connected products/digital twins
Demo

© 2023 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 9


Technical considerations for connected products/digital twins
Key takeaways

Summary
▪ Connected products – allows deploying physics-based
digital twins;
▪ Model deployment:
– Create Equipment in asset central;
– Create Template that contains the engineering model;
– Create an Instance binding the model to the equipment;
– Monitor results in Product Monitoring;
– View alerts in Early Warnings;

© 2023 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 10


Thank you.
Contact information:

open@sap.com
Follow all of SAP

www.sap.com/contactsap

© 2023 SAP SE or an SAP affiliate company. All rights reserved.


No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of
SAP SE or an SAP affiliate company.
The information contained herein may be changed without prior notice. Some software products marketed by SAP SE and its
distributors contain proprietary software components of other software vendors. National product specifications may vary.
These materials are provided by SAP SE or an SAP affiliate company for informational purposes only, without representation or
warranty of any kind, and SAP or its affiliated companies shall not be liable for errors or omissions with respect to the materials.
The only warranties for SAP or SAP affiliate company products and services are those that are set forth in the express warranty
statements accompanying such products and services, if any. Nothing herein should be construed as constituting an additional
warranty.
In particular, SAP SE or its affiliated companies have no obligation to pursue any course of business outlined in this document or
any related presentation, or to develop or release any functionality mentioned therein. This document, or any related presentation,
and SAP SE’s or its affiliated companies’ strategy and possible future developments, products, and/or platforms, directions, and
functionality are all subject to change and may be changed by SAP SE or its affiliated companies at any time for any reason
without notice. The information in this document is not a commitment, promise, or legal obligation to deliver any material, code, or
functionality. All forward-looking statements are subject to various risks and uncertainties that could cause actual results to differ
materially from expectations. Readers are cautioned not to place undue reliance on these forward-looking statements, and they
should not be relied upon in making purchasing decisions.
SAP and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered
trademarks of SAP SE (or an SAP affiliate company) in Germany and other countries. All other product and service names
mentioned are the trademarks of their respective companies.
See www.sap.com/trademark for additional trademark information and notices.
Week 6: Get Started and Technical Foundation
Unit 8: Gain Insights into Product Data
Gain insights into product data
Extend the functional coverage to manage product data across the extended enterprise

Manage Product Data in SAP Enterprise Product Development

Define Develop Deliver

Manage Product Data

Product Specification Configuration Insights


Structure Management Management

Integration with SAP S/4HANA

BOM Change Product Data Product


Management Management CAD Compliance
Integration

© 2023 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 2


Gain insights into product data
Take the right actions based on information aggregated in dashboards, KPIs, and charts

Business Outcomes Use Case Highlights


“As a product manager I need to gain insights for my
product during development, production, sales, and
operations to make the right decision and take the
Observe & discover – Keep an overview on
right actions.”
product-related tasks, changes, requirements
and their fulfillment, customer feedback, and
other important KPIs and thresholds.

Analyze & decide – Aggregate, correlate,


and analyze product-related information from
various internal and external data sources to
make informed decisions.

© 2023 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 3


Gain insights into product data
Take the right actions based on information aggregated in dashboards, KPIs, and charts

Use Case Overview


Aggregate
View cumulated
Generate and Observe and information from
data as diagrams
view KPIs show trends internal and external
and charts
data sources

Data and information KPIs make processes If key figures or Product data is
from the product measurable and measured values show distributed over
lifecycle are prepared comparable and enable an inadequate trend, various internal and
in diagrams and charts, weak points to be intervention might be external sources. To
providing a identified. The necessary. Insights get a complete view,
management-oriented automated collection of supports the recognition all these sources need
overview and thus KPIs allows of these critical to be considered.
enabling the faster comprehensible situations.
compilation of findings. statements about
process performance.

© 2023 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 4


Gain insights into product data
Mockup

© 2023 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 5


Gain insights into product data
Key takeaways

Summary
▪ Observe & discover
– Keep an overview on product-related data and
information with specific dashboards
▪ Analyze & decide
– Aggregate, correlate, and analyze product-related
information from various internal and external data
sources to make informed decisions.

© 2023 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 6


Thank you.
Contact information:

open@sap.com
Follow all of SAP

www.sap.com/contactsap

© 2023 SAP SE or an SAP affiliate company. All rights reserved.


No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of
SAP SE or an SAP affiliate company.
The information contained herein may be changed without prior notice. Some software products marketed by SAP SE and its
distributors contain proprietary software components of other software vendors. National product specifications may vary.
These materials are provided by SAP SE or an SAP affiliate company for informational purposes only, without representation or
warranty of any kind, and SAP or its affiliated companies shall not be liable for errors or omissions with respect to the materials.
The only warranties for SAP or SAP affiliate company products and services are those that are set forth in the express warranty
statements accompanying such products and services, if any. Nothing herein should be construed as constituting an additional
warranty.
In particular, SAP SE or its affiliated companies have no obligation to pursue any course of business outlined in this document or
any related presentation, or to develop or release any functionality mentioned therein. This document, or any related presentation,
and SAP SE’s or its affiliated companies’ strategy and possible future developments, products, and/or platforms, directions, and
functionality are all subject to change and may be changed by SAP SE or its affiliated companies at any time for any reason
without notice. The information in this document is not a commitment, promise, or legal obligation to deliver any material, code, or
functionality. All forward-looking statements are subject to various risks and uncertainties that could cause actual results to differ
materially from expectations. Readers are cautioned not to place undue reliance on these forward-looking statements, and they
should not be relied upon in making purchasing decisions.
SAP and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered
trademarks of SAP SE (or an SAP affiliate company) in Germany and other countries. All other product and service names
mentioned are the trademarks of their respective companies.
See www.sap.com/trademark for additional trademark information and notices.

You might also like