NIR Item PLM Change MGT Final

1.1.
PLM – Change
Management
This presentation is intended to outline our general product direction. It is intended for information purposes only, and may not be incorporated into
1-1 any contract. It is not a commitment to deliver any material, code, or functionality, and should not be relied upon in making a purchasing decision.
Scenario
The Engineering group has now been tasked to
automate the Change Management Process. They
Need to define different processes for Ideas, Issues,
Change Requests, New Item Requests and Change
Orders.
Each type of change may need different routings
based on the business needs and they want that
routing to be automatic.
In some cases, they want to ensure specific steps
have been completed prior to moving the change to
the next step.
They want to be able to track the origin or the
genealogy of changes.
Change Management Foundation thought
Process
• Gather information on • Research the data that
all of the changes used may be required for
at a high level and each level of change
categorize them • Define if there are
• With in each change, are specified values that
there different types of must be used.
changes that may need • Research the routing
to be processed that is required for each
differently for what ever change.
business reason. • Understand what
• Within each of these processes must be
types, will I need this to completed prior to
be an item change or moving on to the next
not. step in the routing
Process
• Within each change, are specified values that
types, define if this is completed prior to
going to be item related. moving on to the next
step in the routing
Different Changes, Different types of
changes and Item inclusions
Safety
Issue
Issues
Eng
Quality
Item Data Change Item Data
Issue
Order
Change
Order
MFG Change Attributes

Eng Change
Change Item Data Order Change Document
Request
Change
Request
MFG
Change Item Data
Request
Process
be an item / product moving on to the next
change or not. step in the routing
Adding Required Data Elements and
Specific Values
EstimatedUnit
Up to 5M
Cost Difference
Cost
Impact Estimated 5m-10m
Implementation Dollar
NewItem ENG Cost Value
Request NIR 10m-50m
Process
be an item / product moving on to the next
change or not. step in the routing
Routing and Business Rules
Estimated Unit
Up to 5M
Cost Difference
Cost
Impact Estimated 5m-10m
Implementation Dollar
New Item ENG Cost Value
Request NIR 10m-50m
Step 15 Step 20
Step 10 Status
Status Status
Approval Completed
Open Approval
Approval
Criteria Criteria
ACTION
ACTION
Role Role
Assignment Assignment
Isn’t this overkill?
• Can one person or group effectively handle all

change groups such as Issues, Ideas, Change
Request or Change Order?
• Do all change groups require the same data for
processing?
• Can one process effectively handle a companies
business needs?
Oracle Solution
B usiness D ata C hange
A ttributes V alues
C hange
A ttribute E stim ated U nit
C hange U p to 5M
G roup C ost D ifference
C atalog
V alue S et
C ategory C ost
C hange
Type Im pact E stim ated 5m -10m
Im plem entation D ollar
N ew Item ENG C ost V alue
R equest N IR 10m -50m
S tep 15 S tep 20
S tep 10 S tatus
S tatus S tatus
A pproval C om pleted
W orkflow O pen
A pproval A pproval
S teps
C riteria C riteria
A C TIO N
A C TIO N
W orkflow
Tem plates
R ole R ole
A ssignm ent A ssignm ent
P rocess D ata /
R ules
Scenario I
New Item Request
Scenario
• Vision Engines wants a new item request process

in place. They want the process to be workflow
enabled and they want to be able to track specific
data elements about the change.
Demo
New Item Request
Process
Workflow Directs to Product Manager

Design Engineer will request new part
Who will review and approve as well
And provide a certain amount
as implement
Of data
Create New Engineering Item
Create Engineering Item > ADS Diesel Engines Components ICC > Continue
Update Item Descriptions
Provide Item Description > Next
Do not update Attributes now – will later
Next Button
Update New Item Request Attributes
ADS Cost Impact Sub Tab Update the Estimated Unit & Implementation Costs
Submit
Add to Favorites and note NIR #
New Item request created
Review notifications
Home Page > Select “NIR Requires item attribute values” Notification
Drill Down to the New Item Request Details
New Item Request Hyper Text
Update the Attribute Groups
Click on Attribute Group Notification hyperlink
Update Item Attributes
Your now in the Item Workbench. Update the two attributes > Apply
Get Back to the Change Request from Item
Workbench
Change Management Tab > Search > New Item Request > ADS > Go
New Item Request Search Returns / Select
NIR
Select New Item Request Hyperlink on your New Item Request Number
Get to the Item Definition Notification
Select Item Definition Notification Hyperlink
Close the Task
Close Button
Log in as Product Manager
Review Notification
Drill to New Item Request Details
Click on New Item Request Details Hyperlink
Review the Item Details
Review the Cost Impact of the New Item Request
Review the Item Details
Click on the Item From the New Item Request form

After review Click on the
New Item Request Hyperlink to get back to the New Item Request
Start Approval Steps
Workflow Tab > Approve / Reject Hyperlink
Approve New Item Request
Approve Button
Setup
New Item Request
Setup Required – New Item Request
• Existing Data • New Setup Required

– Item Catalog Category – Change Type
– Roles and Role – Change Statuses
Mapping – Change Codes
– Change Category – Change Workflows
– Attribute Groups Steps
– Change Codes – Change Workflows
– Assign New Item
Request to Item
Catalog Category
Oracle Solution
A ttributes V alues
C hange
C hange U p to 5M
C atalog
V alue S et
C ategory C ost
C hange
S tep 15 S tep 20
S tep 10 A pproval
O pen C om pleted
W orkflow
A pproval A pproval
S teps
C riteria C riteria
A C TIO N
A C TIO N
W orkflow
Tem plates
R ole R ole
P rocess D ata /
R ules
Change Categories
• Change categories enable you to capture and

implement different categories of changes
throughout your enterprise
– Many pre seeded Change Categories
Change Order New Item Request
Change Request Issues
• User defined Change Categories created by
copying seeded Change Categories
– Exception is the New Item Request which cannot be
copied
Change Categories
Setup Workbench > Change Management Tab > Categories

For Review as we will use the seeded Category New Item Request
Oracle Solution
A ttributes V alues
C hange
C hange U p to 5M
C atalog
V alue S et
C ategory C ost
C hange
S tatus S tatus
S tatus A pproval
O pen C om pleted
W orkflow
A pproval A pproval
S tatus
C riteria C riteria
A C TIO N
A C TIO N
W orkflow
Tem plates
R ole R ole
P rocess D ata /
R ules
Change Types
• Within Change Categories you can have different

change types
– This allows different requirements and processes
for different change types within a category
Category = New Item Requests
Change Types = MFG New Part Request
Engineering New Part
Request
Marketing Collateral New Part
Number Request
Change Types
New Item Request

Category – Sub tab
Types
Sub Tab Types - under Category New Item Request > Create
Create New Item Request
Don’t
Forget
Complete and Apply
LOOK FAMILIAR????!!!!!
Change Type Created

Oracle Solution
Business Data Change
Attributes Values
Change
Attribute Estim ated Unit
Change Up to 5M
G roup Cost Difference
Catalog
Value Set
Category Cost
Change
Type Im pact Estim ated 5m -10m
Im plem entation Dollar
New Item ENG Cost Value
Request NIR 10m -50m
Status Status
Status Approval
O pen Com pleted
W orkflow
Approval Approval
Status
Criteria Criteria
ACTIO N
ACTIO N
W orkflow
Tem plates
Role Role
Assignm ent Assignm ent
Process Data /
Rules
Add Attribute Groups
• Change Management Attribute groups are used

only on the Change Management Document. This
adds a great deal of flexibility to the product.
• Adding attribute groups is exactly like it was in the
Item Catalog Category portion.
Hyper Text Attribute Groups > Add Attribute Groups
Select Attribute Group
Select Attribute Cost Impact > Apply
Add Pages to the Change Management
Type
• Creating and adding pages is exactly like it was in
the Item Catalog Category presentation. Pages
created here will only be seen on Change
Management Pages of the type you are creating.
• In our example – you will only see this page in the
New Product Request Change Category and the
Change Type of ADS NPR.
• You will place the attribute group you have
selected to be used in this Change Type on this
Change management page.
Create Change Management Page
Hypertext > Pages > Create Page
Create Change Management Pages II
1, Enter Basic Information

2. Click Add Another Row to add Cost Impact
New Terms Change Codes
• Available for all Change Categories

• User Definable – No System Processing
• Two codes used now
– Priorities
– Reasons
• This data will be available for tracking purposes.
Add Change Codes
Click on Codes Hypertext and Move All for both priorities and reasons
Configure the Change Management Type
• The configuration of the type will allow you to

select what data you would like to see on the
change when it is sent out.
• The Sections will appear as portions on the
Change Type with expansion capability
• The Primary Attributes will appear on the New
Change in the overview section
Configure the Change Management Type
Click on Configuration and select all sections and for primary attributes
All except Names
Oracle Solution
A ttributes V alues
C hange
C hange U p to 5M
C atalog
V alue S et
C ategory C ost
C hange
S tatus S tatus
S tatus A pproval
O pen C om pleted
W orkflow
A pproval A pproval
S tatus
C riteria C riteria
A C TIO N
A C TIO N
W orkflow
Tem plates
R ole R ole
P rocess D ata /
R ules
Exercise I
New Item Request
Exercise 1 (cont)
Create the Data Elements for a New Item
Request Change
Use your initials in place of XXX:
• Create a new New Item Request TYPE named
“XXX New Item Request” Sequence Generated,
Prefix=XXXNIR, Next Number=1
• Add Attribute Group=Cost Impact
• Create a Page to display the attribute group Cost
Impact
• Assign all codes
• Configure the Change
– Sections available=(move all)
– Primary attributes=(move all but “NAME”)
Oracle Solution
A ttributes V alues
C hange
C hange U p to 5M
C atalog
V alue S et
C ategory C ost
C hange
S tatus S tatus
S tatus A pproval
O pen C om pleted
W orkflow
A pproval A pproval
S tatus
C riteria C riteria
A C TIO N
A C TIO N
W orkflow
Tem plates
R ole R ole
P rocess D ata /
R ules
Create the Workflow Statuses
• A change will go through a series of statuses

during it’s life. Open, Approval, Closed etc.
• Create the statuses first.
• You are only creating headers at this point
• Each status can have it’s own workflow that you
will define.
Add Workflow Status
Click on Workflow Hyperlink > Add Another Row
Update Workflow Status
#15 > Type Approval > Apply
Oracle Solution
A ttributes V alues
C hange
C hange U p to 5M
C atalog
V alue S et
C ategory C ost
C hange
S tatus S tatus
S tatus A pproval
O pen C om pleted
W orkflow
A pproval A pproval
S tatus
C riteria C riteria
A C TIO N
A C TIO N
W orkflow
Tem plates
R ole R ole
P rocess D ata /
R ules
Create the actual workflow assignments
• Each one of the statuses in the workflow, Open,
Approval, and Completed can have their own
workflow assigned. In our case we are going to
make this very simple. Your Design Engineer is
the creator and will be asked to complete some of
the attributes for the New Part request. This will be
in the open portion.
• We will be leaving the Change Management
Creation area and move into the Creation of
Workflows
• We will then come back and assign the actual
workflows to the steps / status we have created
Creating Workflow Templates
Setup Workbench > Change Management Tab > Workflow Sub Tab> Create
Create Definition Workflow for Status
Open
Make Sure Type = Definition & then Add Step
Add the Action & Assignee
Click on add Step and then Add Assignee add the

ADS Design Engineer you created
What did we just do…
• For the first workflow status of Open – we have

created a workflow that will use the item roles you
have defined earlier in the class. In this case, you
have asked the person who you created as a
Design Engineer to complete the attributes that
will be requested as well as the cost impact
statement from the change document.
• Lets add the next workflow template for the
approval process.
Oracle Solution
A ttributes V alues
C hange
C hange U p to 5M
C atalog
V alue S et
C ategory C ost
C hange
S tatus S tatus
S tatus A pproval
O pen C om pleted
W orkflow
A pproval A pproval
S tatus
C riteria C riteria
A C TIO N
A C TIO N
W orkflow
Tem plates
R ole R ole
P rocess D ata /
R ules
Navigate to create new workflow template
To get back to the workflow template, you have to click on the Workflow Subtab
or Apply Button
Create Approval Workflow template for the
Approval Status
Add Step
Add the Action & Assignee
Add Assignee > add the ADS Product Manager you created
What have we done….
• For Status Open – we created a workflow that will

use the item roles you have defined earlier in the
class. In this case, you have asked the person
who you created as an Design Engineer to
complete the attributes that will be requested as
well as the cost impact statement from the change
document.
• For Status Approval - we have created a workflow
that basically asks the Product Manager you
created to review and approve.
• We now have to link these workflow templates to
the actual workflow statuses.
Oracle Solution
A ttributes V alues
C hange
C hange U p to 5M
C atalog
V alue S et
C ategory C ost
C hange
S tatus S tatus
S tatus A pproval
O pen C om pleted
W orkflow
A pproval A pproval
S tatus
C riteria C riteria
A C TIO N
A C TIO N
W orkflow
Tem plates
R ole R ole
P rocess D ata /
R ules
Configure the Workflow Statuses and link
the Workflow templates to the Workflow
Statuses
• We have created workflow statuses
• We have created new workflow templates
• Each workflow Status can have it’s own template
• We now need to configure the workflow steps
• We need to add the templates to the workflow
steps
Configure Workflow Status Open and add
Workflow Template
Change Management Categories > Your New Item Request > Workflow > Status Open>
Update Properties
Configure Workflow Step 10 / Status Open
and add Workflow Template (cont)
Add Workflow for definition – allow updates and auto promote to approval
Configure Workflow Status Approval and
Add Template
Click on Status Approval and Update Properties

Will populate statuses available
Configure Workflow Status Approval and
Add Template
Add Approval Template > Auto Promote and Auto Demote steps
Add the New Item Request Change Type to
the Item Catalog Category
• We now will apply this change type we have
created to the Item Catalog Category we want to
enforce this particular workflow against.
• In our case – it will be the ADS Diesel Engine
Components.
Adding to Item Catalog Category
Items Tab > Hypertext New Item Request

Add New Item Request to Item Catalog
Category
Update
Add the Attribute Group from the Item
Catalog Category that needs updating
• Only user defined attribute groups will be

available – operational attribute groups will be
able to be under change management control in
future release.
• This can be as many user defined attribute groups
as required for this New Item Request.
Add the Attribute Group
Add Attribute Group to the New Item
Request
Exercise 2
New Item Request
Exercise 2 (cont)
New Item Request
• Add new Status “15” of status type Approval
• Create Workflow Template for Status Open Status
– Name & Description=ADS NIR Definition
– Type=Definition
– Add Step
Step=10
Workflow Process=Definition
Assignee=Derived
Response Required=One Assignee
Days to respond=1
– Add Assignee
Item Role=ADS Design Engineer
Exercise 2 (cont)
New Item Request
• Create Workflow Template for Status Approval (15)
– Name & Description=ADS IR Approval
– Type=Approval
– Add Step
Step=10
Workflow Process=Approval
Assignee=Derived
Response Required=One Assignee
Days to respond=1
– Add Assignee
Item Role=ADS Product Manager
Exercise 2 (cont)
New Item Request
• Update Open Status
– Status for Promotion=Approval
– Workflow Template=ADS IR Definition
– Allow Updates=<check>
– Auto Promote=<Approval>
• Update Approval Status
– Status for Promotion=Completed
– Status for Demotion=Open
– Workflow Template=ADS NIR Approval
– Allow Updates=<check>
– Auto Promote=<Completed>
– Auto Demod=<Open>
Exercise 2 (cont)
New Item Request
• Add NIR to ADS Diesel Engine Components
• Add Attribute Group ADS Diesel Engine Component
Specifications to be updated
Recap New Item Request
• Your prospect has many different product lines

and the new item request process is different
among each line. What steps would you need to
perform in order to show a demo?
• Common Issues
– What did you run into
Workflow Variables
Objects Impacting Page Driven Workflow
Creation
• Change Catalog Categories
• Change Status Types
• Workflow Template Types
• Workflow Processes
Change Categories
Change Categories
New Item Request – All Others
Change Type Statuses
Status Types
Open
Approval
Review
Released
Scheduled
Implemented
Setup Workbench > Change Management Tab > Statuses
Change Management Workflow Steps
Setup Rules
• Has to be at least two Statuses with each Change
Header Type
– First may be any Status Type
– Will Default two Open and Implemented
– Last Must be Status Type Implemented
• Status Type of Scheduled Must be followed by
Status Type of Implemented
Workflow Template Types
Types
Approval
Definition
Definition and Approval
Generic
Workflow Processes
Workflow Processes
Request Approval
Request Comments
FYI
Definition
Definition and Approval
New Item Request
N ew P roduct Introduction
M atrix
R eview , R eleased,
S tatus T ypes OPEN A pproval S cheduled and Im plem ented
& Approval
& Approval
& Approval
Definition
Definition
Definition
Generic
Definition
Definition
Definition
Approval
Approval
Approval
Generic
Generic
W o rkflo w T yp e
Availab le YES YES YES YES YES
W o rkflow
P rocesses
YES
R eq u es t Ap p rova l
R eq u es t C om m e n t YES YES YES YES YES
FYI YES YES YES YES YES
D efin itio n YES
D efin itio n a nd
Ap p ro va l YES
All Others
All O ther Change Type
W orkflow M atrix
R eview, R eleased,
Status Types O PEN Approval Scheduled and Im plem ented
& Approval
& Approval
& Approval
Definition
Definition
Definition
Generic
Definition
Definition
Definition
Approval
Approval
Approval
Generic
Generic
W orkflow Type
Available YES YES YES
W orkflow
Processes
Request YES
Approval
R equest YES YES YES

C om m ent
FYI YES YES YES
D efinition
Definition and
Approval
How Extravagant do you want to get?
Change Management Scenario II
Engineering Change Request to
Engineering Change Order
Design Engineer Submits Change Request Product Manager reviews and

To Product Manager Creates a Change Order
Scenario
Vision Engines wants to see what the origin of change

are. For example, if there is a Change Request that is
turned into a Change Order, Vision Engines wants to
be able to see that relationship.
New Concepts
• Change Management Line Types
– If you want an item to be populated when creating a
Change Order from other Change types - you have
to have a change line.
– Create line types for any change type except
Change Orders – these are system defined.
– Line Attributes
• Linking or relating Change Management Type to
one another.
– Issue to Change Request
– Change Request to Change Order
– Idea to Issue to Request to Order
• Item Selection Criteria
– Will limit the item selection to the criteria you have
defined – in our case – Item Catalog Category
Demo

Flow
• Design Engineer creates change request

– Change Request items limited to a specific set of
items
– Attributes at Header and Line Level
– Submit the Change
• Product Manager
– Log in as Product Manager
– Create Change Order From Change Request
– View the relationships
As Design Engineer – Create Change
Request
Home > Create Change Request > Select ADS ECR
Complete Change Header
Notice Item Number Limitations > Also Change Header Attributes
Add Change Line
Add the Change Line
Update Change Line (1)
Update Change Line & Apply > Save for Later

Change Line User Defined Attribute
• For User Defined Attributes at the Change Line

Level
– Not able to input values when creating Change
– Have to Apply and Save for Later
– You will be returned to the Change Page
You can now update the Change Line User
Defined Attribute
Select the line and select Update
Update Attributes
Back to Change Page and Submit
Actions > Submit > Go
Flow
• Design Engineer creates change request

– Change Request items limited to a specific set of
items
– Attributes at Header and Line Level
– Submit the Change
• Product Manager
– Log in as Product Manager
– Create Change Order From Change Request
– View the relationships
Log in as Product Manager
Select Notification
Change Request Details
Select Change Request Details
Add Change Request to Change Order
Actions > Add to Change Order
Update Change Order Info
Accept defaults for this portion of class

Continue Button
Submit Change Order
Update Change Order Name > Submit button
Newly Created Change Order
Click the View Relationships Tab
View Relationships
Setups

Setup Required – ECR to Change Order
• Existing Data • New Setup Required
– Item Catalog Category – Change Type
– Roles and Role – Line Type
Mapping – Line Attributes
– Change Category – New Workflow
– Attribute Groups
– Change Codes
– Change Statuses
– Change Codes
– Change Workflows
Statuses
– Change Workflows
Create New Change Type
• Create a new Change Type under the Change

Request Category
• You can copy from a different change type and
modify (MCR)
• We are adding the Item Selection Criteria as well
Creating New Change Request Type
Setup Workbench > Change Request Category > Type MCR > Duplicate
Creating New Change Type with Selection
Criteria
Subject Selection Criteria = Item Revision – Item Selection Criteria

= Catalog Category ADS Diesel Engine Components
Add the Attribute Groups for the New
Change Request Type
• We are creating a new change request type so we
will add a few new attribute groups and attributes.
• This is at the Change Type Header Level
– Add Affected Designs
– Add Strategic Impact
Add Change Type Header Attribute Groups
Add Attribute Groups and select affected Designs and Strategic Impact
Create Pages for New Change Type
Header
• Should be getting familiar!!!
Create Pages for New Change Type
Header
Create one page for both attribute groups or two pages one for
each attribute group
Create Line Attribute Group and Attribute
• Line attribute groups can be useful when you want

to capture data only about a specific line.
• We are going to be creating a new line type and
will need a line attribute group .
• We will first create a very simple line attribute
group and attribute.
Create Line Attribute Group
Change Management Tab > Line Attributes Sub Tab >

Apply and Add Attribute Button
Create Line Attributes
Apply
Completed Line Attributes
Create the Line Type
• We will now create the line type

• Line types will be available for all of the Change
Types under the Change Category.
• We will add the Item Search Criteria to the line
type
• We will add attribute groups
• We will create the pages
Create New ECR Line Type
Under Change Category ECR > Select Line Type Sub Tab > Create
Complete Line Creation
Item Revision Subject Selection - Item Selection Criteria = Catalog Category

ADS Diesel Engine Components
Add Attribute Groups to new Line Type
Attribute Group Link > Add Attribute Groups Button

Create Pages for new Line Type
Pages Link
Workflow Setups copied from MCR
• Codes will be copied over

• Configuration will be copied over
• Workflow Statuses will be copied over
• We will update the configuration
• We need to configure the approvals and workflow
statuses
Update Configuration
Change Management > Categories > Change Request Type

Select your change request
Click the Configuration hyperlink
Make the selections as showsn - remove Name from Primary Attributes Selected
Update Workflow
Change Management Tab > Categories > ADS ECR > Workflow hypertext
Select Status Open and Update
Update Properties
Complete Workflow Status Open
Enter Workflow Template
Complete Workflow Status Open
Why is this blank?
Create Generic Workflow Step
Workflow Sub Tab > Create > Add Step
Create Action for Generic workflow
Create FYI Process and add Design Engineer
Complete Setup Workflow Status Open
Workflow Hypertext > Update Step 10 > Add the workflow and updates > Apply
Update workflow Status Approval
Workflow Hypertext > Update Status Approval > Add the NIR Workflow > Apply
Exercise 3

Exercise 3 (cont)
1. Create a new change type under the change

category Engineering Change Request and copy
from the MCR change type
• Add item selection criteria to enforce ADS Diesel
Engine Catalog Category
• Add 2 header attribute groups
– Affected Designs
– Strategic Impact
• Create display pages for Affected Designs and
Strategic Impact
Exercise 3 (cont)
2. Create the Line Attributes called Line_Cost to be

added later to a new entity called Change Lines
– Add one attribute called Cost of Change Per Line
and use the value set called Dollar Value
3. Create the line type ADS ECR Line
– Subject Selection Criteria=Item Revision
– Item Selection Criteria=Catalog Category > ADS
Diesel Engine Components
– Add Attribute Group Cost of Line Impact to the
line type
– Create a display page for the line type
Exercise 3 (cont)
• Update Status “Open”

– Workflow Template=ADS ECR FYI
– Allow Updates
– Allow Auto Promote=Approval
• Update Status=“Approval”
– Status for Demotion=Open
– Workflow Template=ADS NIR Approval
– Allow Updates
– Allow Auto Promote=Approval
– Allow Auto Demote=Open
Recap
If Vision Engines wants to be able to track what started

a change, how would they do that? What steps would
you need to take to set this up?
If Vision Engines wants to be able to track different

types of data at the header level and at a change line
level, what would you show them? How would you go
about setting this up?
Change Management Business Scenario III
Change Management Communications
Rejecting Change Documents
Product Manager Rejects

Design Engineer Creates
Request asking for more
Change Request
Data
New Concepts
• Use of the Auto Promote and Demotion in the

workflow setups.
– We have seen the auto promotion working in the
first two cases
– We will now see how the auto demotion will work.
• Action Log
– User can request and post comments directly to
one another. These will create notifications.
• Restarting of the Workflow
– After responding to a condition, users may need to
restart the workflow.
• No new setups required!!!
Check the following to ensure the flow will
work
• You will be using the new Change Request you
have created
• Check the workflow steps and the actual workflow
to make sure you have Auto Promote and Auto
Demote selected for the Definition and Approval
workflow steps.
Check Change Request Type Workflow
Your New Change Request Type

Check workflow and auto promote for
Status Open
Check workflow, promote and Demote for
Step 20
Demo
Flow
• Log in as Design Engineer

– Create ECR
– Updated Attributes and Submit ECR
• Log in as Product Manager
– View Notifications
– Request Comments from Design Engineer
– Reject ECR
• Log in as Design Engineer and view notifications
– Make Changes to ECR
– Restart the workflow
– Reply to comments to advise
As Design Engineer – Create Change
Request
Home > Create Change Request > Select your new Change Request Type
Update Change Attributes
Make sure to add an Item and Rev - Update a few attributes and Submit
Submitted ECR
Work is done as Design Engineer – logout as Design Engineer
Flow
• Logged in as Design Engineer

– Created ECR
– Updated Attributes and Submitted ECR
• Log in as Product Manager
– View Notifications
– Request Comments from Design Engineer
– Reject ECR
Product Manager Reviews Notifications
Click on the notification for the ECR you just submitted
Scroll to the Change Request Details
View the change request details
Review Designs & Impacts
Review Designs and Impacts – Then select action Log
Request Comment
Request Comment from Design Engineer
Select Person and update Comments
Select Person and update comments - Apply
Reject ECR
Select the Overview Tab / then Approve Reject Hyper Text
Reject ECR
Done as the product Manager > Will be returned to the notification page. Log out
Flow
• Logged in as Design Engineer
– Created ECR
– Updated Attributes and Submitted ECR
• Logged in as Product Manager
– Viewed Notifications
– Requested Comments from Design Engineer
– Rejected ECR
Design Engineer views notifications
Click on Comment Notification
Review Comment and Look at ECR Details
Select Change Request Details
Update ECR
Update attributes and Apply
Resubmit workflow
Workflow Tab > Start Workflow Button
Back to Notifications
Click on Comment Notification
Reply to comment
Reply
Exercise 4

Exercise 4 (cont)
Vision Engines wants the Change Management
Process to be workflow driven as well as allow for auto
promotion and demotion based on acceptance or
rejection of the change.
They want the person rejecting the change to be able
to advise why the are rejecting the change and they
want to be able to direct the rejection to the correct
person. They also would like to be able to transfer the
workflow.
Once that issue is taken care of the person who
resolved the problem needs to be able to restart the
workflow to get to the next phase.
How can PLM solve this business issue?
Run through the solution to make sure it is working as
you thought it should
Recap
Vision Engines wants to be able to communicate with

all parties during the change process. They want to
make sure that all communication that is pertinent to
the change is captured and tracked. What would you
demo? What parts of the solution would you review to
make sure the flow was correct?
Change Management Business Scenario IV –
Enforce Standard Process for Change Orders
Business Scenario
The Engineering group does not feel they have enough

information to process many of the Change Request
they are seeing.
They don’t feel they have a comprehensive

understanding of the costs or how many different
designs will be impacted.
New Concepts
• Change Order Tasks Templates
• Change order tasks can ensure that mandatory
work is completed before the change order is
implemented or promoted to the next status
• Defined at the Org level allowing you to enforce
standard work procedures for managing change
orders
• Only for Change Orders
Demo
Create ECO
Create ECO
Complete Header Data
Review Change Order
Review Change Order, Click on Hypertext Change Number
Try to change / promote the Status of the
Change Order
Promote the Status from the Workflow Tab
Error Message
Cancel to get back

Go to Line Tab
Change Tasks are on the Line Tab, if there are lines or not
Access Change Tasks
1.
2.
3.
1. Lines Tab > Change Tasks Sub Tab

2. Click the Go Button
3. Update all Mandatory tasks with Status=Open
Update Mandatory Change Tasks
Change Task Status to Completed > Click Apply Button

Promote Change Status
Promote Button
Change Order Status updated
Setup
Setups Required
• Existing Data • New Setups Required

– Item Catalog Category – Create Task Template
– Change Category – Create and update
– Change Type new Change Type
– Line Type – Assign Task Template
– All attributes to Change Type
– All Values
– All workflows
Create Task Template
• Create an Task Template for an Organization

• Add Change Tasks to the Task Template
Specify whether the task is mandatory or
optional
Specify how to derive the default assignee
• Associate the Task Template to an
Organization
Specify between which phases of the change
order status the tasks are to be completed
Create Change Tasks
Setup workbench > Change Management Tab > Task Template Sub Tab > Create
Create Change Task Template
Create tasks as needed – assigned to either a person or a group
Create New Change Order Type
Change Management Tab > Categories Sub Tab > Change Order Category Selected
Types Sub tab> Select ECO Then Duplicate Button
Update New Change Order Type
Name ADS ECO > Sequence Generated > Apply
Attribute Groups Hypertext

Select Attribute Groups
Select Affected Designs and Cost Impact

Create Pages
Pages Hypertext
Configure Page
Add Attribute groups to page

Select Codes for new Change Type
Codes Hypertext > Move all codes to selected box.
Configure new Change Type
Configuration Tab > Move all Sections, move all primary attributes except Name
Update Workflow
We are not going to use this step and it may cause problems during your
demo with schedule dates and times..delete the Scheduled Step and apply
Add Change Tasks to Change Type
Organization Policies Hyper Text
Select Organization
Add Vision Operations
Add Task Template
Task Template Sub tab > Add your created task template start after status open
Complete before Status Released
Exercise 4

Exercise 4 (cont)
Vision Engines wants to ensure specific requirements

are met prior to an Engineering Change Order moving
to an approval stage.
They want every ECO to include an impact and cost

analysis.
Using PLM, how can you solve this business issue?
Once you have completed the setup, create an ECO

and make sure that the tasks are completed prior to
being able to move it to the approval step.
Recap
Vision Engines is having problems getting the amount

of data they would like to make informed decisions on
approving changes. What would you demo, and how
would set this up?
Business Scenario V
Engineering Change Order Propagation
Scenario
Vision Engines is considering rolling out a centralized

Change Management System. They want to be able to
push changes out to the different organizations that
are impacted.
New Concepts
• Organization Hierarchy
• Organization Propagation Policy
– If Item is not defined in receiving org – ECO will not
Propagate
– If the Bom is not defined in receiving org – Only
ECO header will propagate > no Line detail
– If the revisions of bom in sending org is different
then the revisions of bom in receiving org – ECO
will not Propagate
– The Receiving Org will have to implement the ECO
Business Scenario V
Demo
Create ECO
Create ECO
Must have Revised item > Use ADSDECOMP1
Review Change Order
Review Change Order, Click on Hypertext Change Number
Get to Line Tab
Change Tasks are on the Line Tab, if there are lines or not
Access Change Tasks
Lines Tab > Change Tasks Sub Tab > Go Button
Update Change Tasks
Change Task Status to Completed > Click Apply Button

Promote ECO Open to Released
The ECO you created > Workflow Tab > Promote Button from Open to Released
Promote – Released to Implemented
This kicks off concurrent request – and will take a minute or so
View of Implemented Change
Propagate ECO
Back to Overview Tab > Actions Drop Down > Propagate ECO > Go
Update Comments
Apply
View Propagation Results
The request will take some time. After completed > Organizations Tab
Select either Seattle or Boston> Propagation report Tab
Setup
Setups Required
• Existing Data • New Data

– Item Catalog Category – Organization Hierarchy
– Change Category – Organization
– Change Type Propagation Policy
– Line Type
– All attributes
– All Values
– All workflows
Create New Org Hierarchy
• There are many already defined in the system and

you should be able to use them
• If you are going to create a new one – keep it
simple and remember to start with the org you will
be creating the ECO in as the parent. In our Case –
Vision Operations
• In the PLM Pages Organization Policies Tab, the
hierarchy will not be displayed in the LOV if you
are not in the org that is defined as the top level.
In our Case – Vision Operations
• This form is one of the ugliest working forms we
have – be patient
Name Org Hierarchy
Log in as MFG > Inventory > Setup > Organizations > Hierarchy
Enter Name > Save the record
Create Version
Create version > Save the Record

You will now have to query your new hierarchy
Add Top Level Org
In our Case – Vision Operations
In Organization Field – enter the parent org

In Our case Vision Operations
Add Child Orgs
Add Seattle Manufacturing, Save – then add Boston Manufacturing and Save
Add New Org Hierarchy to the
Organization Policy
Log in as the Design Engineer > Setup workbench > Change Management > Change Orders > Your
Change Type> Organization Policies hyper text > Propagation Rules Sub Tab >
Add Another Row > Status for Propagation is Implemented > Hierarchy is your new Hierarchy.
Exercise 5
Business Scenario V
Exercise 5 (cont)
Vision Engines wants to control changes for a couple

of their plants and push them out to the plants after
implementation. These plants are located in Seattle
and in Boston.
How would you define this solution?
After the solution is defined, create a change and

propagate the change to the child orgs.
Recap
What can a change order update?
• Change Order Capabilities

• Creating Structures from PLM (forms)
• Updating Item Attributes from Change Order
• Updating Item Attachments
• Updating AML
• Updating Routing (forms)

NIR Item PLM Change MGT Final

Hochgeladen von

Dokumentinformationen

Originaltitel

Copyright

Verfügbare Formate

Dieses Dokument teilen

Dokument teilen oder einbetten

Freigabeoptionen

Stufen Sie dieses Dokument als nützlich ein?

Sind diese Inhalte unangemessen?

Copyright:

Verfügbare Formate

NIR Item PLM Change MGT Final

Hochgeladen von

Copyright:

Verfügbare Formate

1.1.

MFG Change Attributes

• Can one person or group effectively handle all

• Vision Engines wants a new item request process

Workflow Directs to Product Manager

Provide Item Description > Next

New Item request created

New Item Request Hyper Text

Click on Attribute Group Notification hyperlink

Select Item Definition Notification Hyperlink

Click on New Item Request Details Hyperlink

Review the Cost Impact of the New Item Request

Click on the Item From the New Item Request form

Workflow Tab > Approve / Reject Hyperlink

• Existing Data • New Setup Required

• Change categories enable you to capture and

Setup Workbench > Change Management Tab > Categories

• Within Change Categories you can have different

New Item Request

Complete and Apply

Change Type Created

• Change Management Attribute groups are used

Hyper Text Attribute Groups > Add Attribute Groups

Select Attribute Cost Impact > Apply

Hypertext > Pages > Create Page

1, Enter Basic Information

• Available for all Change Categories

• The configuration of the type will allow you to

• A change will go through a series of statuses

Click on Workflow Hyperlink > Add Another Row

#15 > Type Approval > Apply

Make Sure Type = Definition & then Add Step

Click on add Step and then Add Assignee add the

• For the first workflow status of Open – we have

• For Status Open – we created a workflow that will

Click on Status Approval and Update Properties

Items Tab > Hypertext New Item Request

• Only user defined attribute groups will be

• Your prospect has many different product lines

Setup Workbench > Change Management Tab > Statuses

Availab le YES YES YES YES YES

R eq u es t C om m e n t YES YES YES YES YES

FYI YES YES YES YES YES

D efin itio n YES

Available YES YES YES

R equest YES YES YES

FYI YES YES YES

Design Engineer Submits Change Request Product Manager reviews and

Vision Engines wants to see what the origin of change

Design Engineer Submits Change Request Product Manager reviews and

• Design Engineer creates change request

Home > Create Change Request > Select ADS ECR

Notice Item Number Limitations > Also Change Header Attributes

Add the Change Line

Update Change Line & Apply > Save for Later

• For User Defined Attributes at the Change Line

Actions > Submit > Go

• Design Engineer creates change request

Select Change Request Details

Actions > Add to Change Order

Accept defaults for this portion of class

Update Change Order Name > Submit button

Click the View Relationships Tab