SAP Engineering Record Process Presentation

SAP PLM Pre-Sales Meeting
Process Layer based on PLM 7 Engineering Record

Eudes Canuto, SAP PLM Consulting
February, 2013
Agenda
 PLM Reference Architecture

 Engineering Record Overview
 Demo scenario for Engineering Change Management
 Overview of Process Layer Functionalities
 Q&A
© 2012 SAP AG. All rights reserved. 2

Agenda

 Q&A

Overview: Integrated Product Development
Reference Architecture
Product
Sales Concept engineering Detail engineering Production preparation Production
Project
Concept engineering Detail engineering
Define product variance Procurement of tools
Define concept Validation by prototype
Release for production
Release ECR
EBOM (Variants) MBOM (Variants)
synchronize
Bill of Docs EBOM (Assembly) MBOM (Assembly)
synchronize

Overview: Integrated Product Development
Reference Architecture
Product
Project
Release ECR
synchronize
synchronize

Introduction of the solution
Seamless integration to the Reference Architecture for IPD
Sales
Product
Reference Architecture Service
Manager
  Logistic
Project Manager
Accelerate your business

processes based on
SAP PLM 7 functionality for
engineering record (ER)
Production
Engineering
Procurement

Agenda

 Q&A

PLM 7 Engineering Record
Engineering Change
Management
 Holistic Change
management support for
PLM objects
 Support ECR / ECO and
other process
 Embedded Ad-Hoc workflow
functionality
 Integration to BCV
Process Control for Product Data Management

Business Needs and Solution Requirements
One solution for different processes – Flexibility and Usability are the key
Typical processes
 Engineering Change Request
 Engineering Change Order
 Product release & forbid process
 Material creation process
 Product Change Notification
 Investment approval process
…
Business Needs
 Accelerate the processes

 Reduce the effort
 Ensure the process reliability & traceability
 A flexible solution with high usability

Business Needs and Solution Requirements
Typical Requirement from our customers
 Integrate People from different area‘s (engineering, manufacturing, sales, …)

 task & role specific user interface and service functions
 Process Reliability & Traceability but still very flexible

 predefine process (configuration) vs. Ad-Hoc (runtime)
 Process with loops, events, decision, branches based on background and dialog task
 the agent should be found automatically
 aligned authority management & agent determiniation
 Masterdata and process specific data must be managed

 Handle master data like material, documents, BOM,... from different systems
 Easily attach documents & ensure the process reliablity (mandatory doc‘s and templates)
 Control the change & display of data by status, role & value
 Authority management, Change Log
Agenda

 Q&A

Change Process: Roles and Functions
Change Coordinator / Product Manager
• Coordinates change requests

• Control communication flows
Change Initiator / Plant Manager

Technical Analysis / Engineering
• Initiates Engineering Changes
• Apply the changes in plant BOM • Analyzes and evaluates
the changes regarding
Based on Best Practices: technical feasibility
VDA 4965
CMII
Change Control Board (CCB) ProSTEP iViP

• Decides the execution and
scheduling of the change Business Analysis / Controlling
based on technical feasibility,
costs and other factors.
• Analyzes and evaluates the
changes regarding costs

Process Flow: ECR/ECO (Simplified)
Create Document
ECR ECR
Change
Initiator
Add Create
Close
Review Affected Review Change
Record
Objects Number
Change
Coordinator
Add technical Execute

feasibility changes
Engineering
Add business Execute

analysis changes
Controlling
Execution of
decision
CCB

Create Document
ECR ECR
Change
Initiator
Add Create
Close
Record
Objects Number
Change
Coordinator
ECR ECO
feasibility changes
Engineering

analysis changes
Controlling
Execution of
decision
CCB

Create Document
ECR ECR
Change
Initiator
Add Create
Close
Record
Objects Number
Change
Coordinator

feasibility changes
Engineering

analysis changes
Controlling
Execution of
decision
CCB

Change Initiator creates the Change Request
Creation of
the ECR
Document
the ECR
Review
Add Affected
Objects

Change Initiator documents the Change Request
Creation of
the ECR
Document
the ECR
Review
Add
Material
Affected
wird
angezeigt
Objects

Enter Header
Creation of Information
the ECR
Document
the ECR
Review
Add
Material
Affected
wird
angezeigt
Objects

Creation of
the ECR
Document Notes can be added

the ECR to describe the
request for change
Review
Add
Material
Affected
wird
angezeigt
Objects

Documents can be
Creation of
the ECR added to describe the
request for change
Document
the ECR
Review
Add
Material
Affected
wird
angezeigt
Objects

Create Document
ECR ECR
Change
Initiator
Add Create
Close
Record
Objects Number
Change
Coordinator

feasibility changes
Engineering

analysis changes
Controlling
Execution of
decision
CCB

Product Manager is informed to start a review
Via Email
Creation of
the ECR
Document
the ECR
Review
Add Affected
Objects

Product Manager is informed to start a review
Creation of
the ECR
Workflow Inbox
Document
the ECR
Review
Add Affected
Objects

Product Manager reviews the ECR
Creation of
the ECR
Document
the ECR
Review
Add Affected
Objects

Product Manager add affected objects
Creation of
the ECR
Document
the ECR
Review
Add
Affected
Objects

Product Manager completes the task
Creation of
the ECR
Document
the ECR
Review
Add
Affected
Objects

Create Document
ECR ECR
Change
Initiator
Add Create
Close
Record
Objects Number
Change
Coordinator
Add
Add technical
technical Execute
feasibility
feasibility changes
Engineering
Add
Add business
business Execute
analysis
analysis changes
Controlling
Execution of
decision
CCB

Work item is sent to Engineering and Controlling
Agents are
automatically
assigned

Engineering and Controlling add documents
• Open Work item

Change Record
• Adds the documents
• Update Costs
• Executes Decision
Change Record

Create Document
ECR ECR
Change
Initiator
Add Create
Close
Record
Objects Number
Change
Coordinator

feasibility changes
Engineering

analysis changes
Controlling
Execution of
decision
CCB

Change Control Board (CCB) decides if the
change will be performed

Create Document
ECR ECR
Change
Initiator
Add Create
Create
Close
Change
Record
Objects Number
Number
Change
Coordinator

feasibility changes
Engineering

analysis changes
Controlling
Execution of
decision
CCB

Create Document
ECR ECR
Change
Initiator
Add Create
Close
Record
Objects Number
Change
Coordinator

Execute
feasibility changes
changes
Engineering

Execute
analysis changes
changes
Controlling
Execution of
decision
CCB

Perform Changes (Engineering)

Perform Changes (Controlling)
 Department will execute the steps to

update the costs and milestones.

Create Document
ECR ECR
Change
Initiator
Add Create
Close
Close
Record
Record
Objects Number
Change
Coordinator

feasibility changes
Engineering

analysis changes
Controlling
Execution of
decision
CCB

Change Record is closed
 Change Process is finished

 Notification to interested parties (via Email)

Agenda

 Q&A

Integrated Product Development based on PPM 5.0 & PLM 7
Product
Project
Release ECR
synchronize
synchronize

Process Layer - Solution Components
Product
Project
Procurement of tools Process Layer
Define product variance
Define concept Validation by prototype 1 Actual Release: R2.2
Release ECR
synchronise

cPLM – Role specific Workspace
2 Actual Release: R1.0
synchronise cPLM – Cross Function

Process Layer - Solution Components (I)
• ER Process Control
• Predefined Process based on Process Route & Status Control (available)
• Protocol Functionality for process route (available)
• Process Configuration application (available)
• Task related edit mode (available)
• Task Function: (available)
• Decision (available)
• Agent Determination by:
• Context and role (available)
• Service Functions (available)
• Escalation Functions (Reminder, Due Date) (available)
• Background Service Functions (available)
• Task Description & Subject as Parameter (available)
• Task related dialog functions (available)
• Events (available)
• Info-Tasks (available)
• Control PR route selection also by previous status (available)
• Process Versions & Transport (available)
• Digital Signature (available)
• Checklist Integration (Release 2.4)
• Decision: Notes update based on configured category (Release 2.4)
• Process Preview (Release 2.3)
• Different mode for Process Route - Business and Expert user (Release 2.4)
• Enhancement to define the Workitem and Subject text also with data from ER (Release 2.4)

Predefined Processes / Task related Edit-mode / Protocol Functionality /
Background Functions
2 User can make a decision

(based on a decision profile)
1 User knows what is the task

3 A reason for the decision
can be entered. The field can
be a mandatory field.

ER Process Control – Process Configuration

Agent determination mechanisms
 SAP User
 By Service Function
 ACM Context & Role
 ACM Parameter Role
 Position
 Org. Unit

ER Process Control – Digital Signature

ER Process Control – BRF+ Functions

ER Process Control – Process Preview

ER Process Control – Escalation Functions
1 Tasks are defined in design

time with a duration date 2 At Runtime, when the workflow
starts the user receives the task
and has N days to execute it

3 If the user doesnt complete the
task till the reminder date, he
receives a warning via
Email and has till the duration
date to conclude the task.
4 If the user doesnt complete the

task till the reminder date, he
receives a warning via
Email and has till the duration
date to conclude the task.
5 If the user doesnt complete the 

Task till the duration date the
project manager (attr of the
header), receives an email
(Example)

Process Layer - Solution Components (II)
• ER General
• Automatic Update of Header Attributes (available)
• Button to start workflow (available)
• Service Function for Object list (available)
• External Objects (available)
• Semantic relationships of Objects (Release 3.0)
• ER Integration
• PSM, ER, PPM-Item (available)
• cProjects Integration (Release 2.4)
• Other objects on request
• DMS Easy Document Handling

• Direct attachment of DIR (available)
• Status related template management (available)
• Display document by one click (available)
• Direct delete of documents (available)

Process Layer – Automatic update of header Attributes
Header Attributes (source)

1 Are set
Header Attributes (target)

2 are updated

Process Layer – Service Functions & External Objects Integration
User selects the additional

1 Function to search material in
External systems
User selects the Object from

2 The external system
Framework ‚Additional Functions‘

Inclusion of additional functions, i.e. Use of
Material in Bill of Materials in external systems,
use of a material in material in Bill of materials.
Object is added to the Objects

3 list

Process Layer – ER Integration
Integration with PSM Structures
Integration with ER

Process Layer – Easy Document Handling
• Documents are
created automatically
based on predefined
Saved in context of the
conditions (status 2 Engineering Record.
change)
• Documents are
created from
templates predefined
in customizing
• Documents are saved
in context of the ER
Documents will be added

1 automatically after status change

Process Layer – Easy Document Handling
Predefined documents can be

1 added with one-click
• Add predefined
documents with one-
click on „Create
Document“
• Manage documents:
• Change Status
• Create New Version
• Add Original with
browse-function 2 Manage documents:
status, version, original

Role Specific Workspace - Solution Components
Product
Project
Procurement of tools cPLM – Process Layer
Release ECR
synchronise

Role specific Workspace
synchronise cPLM – Cross Function

Role Specific Workspace - Solution Components (I)
• Agent parameter based context assignment based on ACM for ER

• Parameter based context assignment (available – R1.0)
• Display Context's, roles & user at business object (available – R1.0)
• Display Context validity parameter in object navigator (available – R1.0)
• Interface to connect central authority management system for role request (available – R1.0)
• Automatic Context assignment for other business object (Release 2.0)

• Framework for automatic heredity of context parameter (Release 2.0)
• Workspace related Cockpit with BCV related reports (Release 2.0)
• Comment:
• Minor enhancement in Release cPLM – ACM 1.0 are possible. New functions will be delivered as minor changes if there is a
need to support the agent determination for ER based on customer demand
• Additional functionality for authority management will be delivered in Release cPLM – ACM 2.xxx

Context Assignment Concept
PFCG Rollen Pipp

ER
Ulrich
1 Prod.Plant Logistic
Header
5
Hauser
…
Berechtigung
GB BU Kunde EZKL …. 3
Updat
matic
Auto
CS:
e..
6
014_Eklasse 1 012_Erzeugnis 2
Context Hierachie
001_BU3 007_Kunde 1
014_Eklasse 1 Process Route (Runtime)
2 002_BU2 008_Kunde 2
7
015_EKlasse 2
Context By: Owning
003_BU1 009_Kunde 3
Kunde Context: 012_Erzeugnis 2
GB 016_EKlasse 3
DS EZKL Role: Prod. Plant Logistic
010_Kunde 4
011_Erzeugnis 1
004_Werk 3
012_Erzeugnis 2 Process Route (Design Time)

005_Werk 2
Prod.Plant Logistic
Ulrich
4
Hauser Context By: Service Function
Context Service: get_by_lead_plant
013_Erzeugnis 3
Role: Prod. Plant Logistic
006_Werk 1
014_Erzeugnis 3

Solution Components – ACM Context Assignment
Parameter at Context Parameter and assigned Context at ER

Cross Functions - Solution Components
Product
Project
Procurement of tools cPLM – Process Layer
Release ECR
synchronise

cPLM – Role specific Workspace
synchronise Cross Functions

Cross Functions - Solution Components (I)
• Change Log Tracking

• For ER (available)
• Others on request
• BRF+ based field control for PLM7

• For ER (Release 2.4)
• BRF+ based view control example: Tabs

• For ER (Release 2.4)

Cross Functions – Change Log Tracking

Benefits
Most important benefits
• Extensive features to support different types of processes

• Process can be managed completely based on process routes. This can be easily adapted.
Workflow development is not needed anymore
• Higher usability by functions like role specific UI control, easy document handling, task related
edit mode
• Business Logic can be changed easily by BRF+
• Short implementation cycle by low risk

• Functionality must not be developed customer specific
• ...but if necessary customer specific enhancement can be done based on the framework
• Best practice knowledge is available
• Reuse of solution component in other application of PLM 7, PPM

• Role and value based UI Configuration
• Easy document management
• Authority control with minimized effort - Automatic Context assignement by parameter
• Configuration by IT (central) and Business (decentral)

• Predined process routes (IT) vs. Business rule (business)
• Authority management by (IT) vs. Groups Easy document management(business)

Thank you
Contact information:
Eudes Canuto
SAP PLM Consultant
Eudes.canuto@sap.com

SAP Engineering Record Process Presentation

Загружено:

Сведения о документе

Оригинальное название

Авторское право

Доступные форматы

Поделиться этим документом

Поделиться или встроить документ

Параметры публикации

Этот документ был вам полезен?

Это неприемлемый материал?

Авторское право:

Доступные форматы

SAP Engineering Record Process Presentation

Загружено:

Авторское право:

Доступные форматы

SAP PLM Pre-Sales Meeting

Process Layer based on PLM 7 Engineering Record

 PLM Reference Architecture

© 2012 SAP AG. All rights reserved. 2

 PLM Reference Architecture

© 2012 SAP AG. All rights reserved. 3

EBOM (Variants) MBOM (Variants)

Bill of Docs EBOM (Assembly) MBOM (Assembly)

© 2012 SAP AG. All rights reserved. 4

EBOM (Variants) MBOM (Variants)

Bill of Docs EBOM (Assembly) MBOM (Assembly)

© 2012 SAP AG. All rights reserved. 5

Accelerate your business

© 2012 SAP AG. All rights reserved. 6

 PLM Reference Architecture

© 2012 SAP AG. All rights reserved. 7

Process Control for Product Data Management

 Accelerate the processes

© 2012 SAP AG. All rights reserved. 9

 Integrate People from different area‘s (engineering, manufacturing, sales, …)

 Process Reliability & Traceability but still very flexible

 Masterdata and process specific data must be managed

 PLM Reference Architecture

© 2012 SAP AG. All rights reserved. 11

Change Coordinator / Product Manager

• Coordinates change requests

Change Initiator / Plant Manager

Change Control Board (CCB) ProSTEP iViP

© 2012 SAP AG. All rights reserved. 12

Add technical Execute

Add business Execute

© 2012 SAP AG. All rights reserved. 13

Add business Execute

© 2012 SAP AG. All rights reserved. 14

Add technical Execute

Add business Execute

© 2012 SAP AG. All rights reserved. 15

© 2012 SAP AG. All rights reserved. 16

© 2012 SAP AG. All rights reserved. 17

© 2012 SAP AG. All rights reserved. 18

Document Notes can be added

© 2012 SAP AG. All rights reserved. 19

© 2012 SAP AG. All rights reserved. 20

Add technical Execute

Add business Execute

© 2012 SAP AG. All rights reserved. 21

© 2012 SAP AG. All rights reserved. 22

© 2012 SAP AG. All rights reserved. 23

© 2012 SAP AG. All rights reserved. 24

© 2012 SAP AG. All rights reserved. 25

© 2012 SAP AG. All rights reserved. 26

© 2012 SAP AG. All rights reserved. 27

© 2012 SAP AG. All rights reserved. 28

• Open Work item

© 2012 SAP AG. All rights reserved. 29

Add technical Execute

Add business Execute

© 2012 SAP AG. All rights reserved. 30

© 2012 SAP AG. All rights reserved. 31

Add technical Execute

Add business Execute

© 2012 SAP AG. All rights reserved. 32

Add technical Execute