framework change impact analysis

Impact of Change

Change impact analysis touch points

Author: Ad Ghauri

5 Impact of Change Product changes managed end-to-end

Manage changes from

identification through field support

Process formality and rigor matched to business needs

Change process integrated with

PLM backbone

Schedule product build using

updated product data

Identify and manage non-

conformance corrective actions

Validate as-built product

Plan the implementation of the

authorized solution

Authorize the execution of the

plan

Update product data according

to the plan

Validate and release the resulting

items

End-to-End Process Change Implementation Change Incorporation

Adapted from Siemens PLM

Facilitate closed loop feedback by recognizing when strategic intent is at risk and

informing lifecycle stakeholders of this impending impact.

Teamcenter provides visibility to resources and schedules so you can see their

impact on current projects during the portfolio planning process.

End-to-End Process Change Implementation Change Incorporation

Manage changes from identification through field support

Plan the implementation of the authorized solution

Schedule product build using updated product data

Process formality and rigor matched to business needs

Authorize the execution of the plan Identify and manage non-conformance

corrective actions

Change process integrated with PLM backbone

Update product data according to the plan

Validate as-built product

Validate and release the resulting items End-to-end closed-loop product change management integrated with enterprise backbones

Design Changes Integration with ERP

Integration with

MES

Manufacturing Planning Changes

Other Changes

Provide and manage issue/problem identification, change definition, design change execution, manufacturing change incorporation, support and retrofit

Process formality and rigor matched to business needs – right-sizing process and cost to each specific change

Change Process integrated with PLM backbone provides seamless flow of work with the right data in the right place at the right time


5 Impact of Change Product changes managed end-to-end

5 Impact of Change End-to-End Change Management and PLM Integration

Order-to- Delivery Process

ERP

Inventory Mgmt

Procurement Order Mgmt

Finance

Resource Mgmt

Physical and Financial Assets

Intellectual Property / Assets

PLM and ERP Are Integrated, Distinct, Complementary Domains That Coexist

PLM

Change Request

Problem Report

Product Life WO ECO

Issue Report

TRB CRB CIB2 CIB1 Valid?

Design Review

Business Review

Design Impl. Review

Design Release

Mfg Impl. Review

Solve It?

Change Notice

As-Built Effectivity

Design Start As-Built

Shop Floor Build Order

As-Maintained

As-Designed

As-Planned

Valid?

Mfg Release

As-Planned Reconciliation

Design Change

Planning Change

As-Built Reconciliation


You can use Teamcenter to implement best practice workflows that enable cross-discipline teams to understand change impact, manage review/approval processes

and execute approved product changes



Teamcenter’s where-used/where-referenced and rollup, compare tools ensure that

design impact is fully understood before incorporation

../../WorkProduct_Templates/Change Management/ImpactChangeProcessERP.vsdx

Change Management Template Business Process

Des

ign

En

gin

eeri

ng

Man

ufa

ctu

rin

g En

gin

eeri

ng

MES

ERP

Ori

gin

ato

rO

rigi

nat

or

Ori

gin

ato

rA

dm

inis

trat

or

An

alys

tA

dm

inis

trat

or

An

alys

tC

RB

(C

han

ge

Rev

iew

Bo

ard

)TR

B (

Tech

nic

al

Rev

iew

Bo

ard

)A

dm

inis

trat

or

An

alys

tC

IB (

Ch

ange

Im

ple

men

tati

on

B

oar

d)

Co

st E

stim

ato

rC

han

ge R

esu

lts

Rev

iew

erP

ub

licat

ion

sP

acka

gin

gIn

itia

tive

Rev

iew

B

oar

dIn

cid

ent

Rev

iew

B

oar

dQ

ual

ity

Co

ntr

ol

Ori

gin

ato

rW

aive

r R

evie

w

Bo

ard

Dev

iati

on

R

evie

w B

oar

d

Change Solution Definition and Analysis Closed-Loop ValidationChange Driver VettingChange Driver Documentation Change Solution AuthorizationChange Solution Initiation Change Implementation Planning Change IncorporationChange Implementation

Update Design

Validate Change Results

Validate Change Results

Update Planning

Manufacturing Change Order (MCO) Created

New MBOM Rev. Created - linked to

MCO

Plan (BOP)Affected?

New Plan (BOP) Rev. Created- linked to MCO

Yes

WIP Affected? Shop Order

Maintenance - linked to MCO

Yes MCO State Changed to Complete

&

No

No

Non-Conformance Identified

Stop SO Work

Create Non-Conformance

SO Materials Installed &

Operation Tasks Complete

SO Closed – As Built BOM

Created

As Built Records Transferred

As Built BOM received from

MES/ERP

Validate As Built Configuration

As-Built Not Validated


As-Built Validated

New Part Revision Created

New BOM Revision Created with Effectivity

New Routing Revision Created

Shop Order Released and/or

Updated with New Routing & BOM Revisions

Shop Order Material Issues &

Operations Closures


Created

As Built Records Transferred

Stop Work

Develop Short-Term Resolution


Create Change Solution Collector

Create Change Solution Collector

Make Business Decision

Make Business Decision

Planning Complete / Standard Track

Close the Change Item


Change Solution DisapprovedRework Change

Solution Per Comments

Rework Change Solution Per Comments

Create Change Implementation

Collector

Create Change Implementation

Collector

Make Implementation Decision

Make Implementation Decision

Execute the Implementation Plan

Execute the Implementation Plan

Manage Results Validation and

Release

Manage Results Validation and

Release

Audit the ChangeAudit the Change Close the Change

Item


Planning Complete/ Standard Track

Implementation Plan Execution Completed

Approved

Audit passed

Rework Change Implementation Per Comments

Rework Change Implementation Per Comments

Change Implementation Plan Approved

Change Implementation Plan Disapproved

Route Results to Downstream

Processes

Create Incident Report


Reproduce Incident

Reproduce Incident Analyze Root-

Causes

Analyze Root-Causes Resolve the

Incident

Resolve the Incident

Do Not Resolve Incident



Update Incident Report

Update Incident Report

Withdraw Incident

Need More Info

Resolve Incident without

Managed Change

Rework Incident Analysis

Resolve Incident with Managed Change

Change Solution Approved / Implement the Change

Resolve with Informal Change Implementation

Planning Complete / Fast Track

Planning Complete / Fast Track

Create New BOM Item Revisionwith Effectivity in ERP(Resulting BOM Item)

Disposition Failed As-Built Validation

Disposition Failed As-Built Validation

Revise Change Solution

Create new Change Implementation Collector

Create new Implementation Plan for same Change Implementation Collector

Create new Implementation Plan for same Change Implementation Collector

Restart Shop Order

Restart SO Work

Restart Work



Analyze the Change

Analyze the Change Propose Solutions

Propose Solutions

Manage Cost Estimation

Manage Cost Estimation

Technical ReviewTechnical Review

Solution Is Recommended

Change Solution Planning

Complete?

Change Solution Planning

Complete?

Plan the Implementation

Plan the Implementation

Change Implementation

Planning Complete?


Planning Complete?

Implementation Planning Complete

Approved

Planning Not Complete

Rework Change Implementation Plan

Rejected

Audit Failed

Rework Change Solution or AnalysisDefine / Rework Solutions

Re-Analyze

Incident

Update Change Effectivity on Change

Implementation Collector



Planning Not Complete

Estimate CostsEstimate Costs

Update Effectivity on BOM Revision in ERP

Effectivity Updated on BOM

Revision

&





Approved

&

Effectivity Trigger

Update Publications

Update Packages & Labels

Make Incident Decision

Make Incident Decision

Cancel Shop Order

Shop Order Cancelled

Cancel Shop Order

Stop Shop Order


&

Does this belong?

EquivalentIncident Report

Exists

EquivalentChange Solution Collector

Exists

EquivalentChange Implementation Collector

Exists

Incident Report

Incident Impact Analysis

Design Impact Analysis

Change Solution

Definition & Authorization

Validation

and Release

Manufacturing

Impact Analysis

For eg BOP needs updating

Manufacturing

Incorporation

Change

Implementation



Teamcenter’s unique context management capability enables engineers to create,

save and re-use the same context repeatedly as they evaluate design impacts.

Change Management Template Business Process

Des

ign

En

gin

eeri

ng

Man

ufa

ctu

rin

g En

gin

eeri

ng

MES

ERP

Ori

gin

ato

rO

rigi

nat

or

An

alys

tA

dm

inis

trat

or

An

alys

tO

rigi

nat

or

Wai

ver

Rev

iew

B

oar

d

Change Solution Definition and Analysis Closed-Loop ValidationChange Driver Documentation Change Solution AuthorizationChange Solution Initiation Change Implementation Planning Change IncorporationChange Implementation

Update Design

73

Update Planning

75

Manufacturing Change Order

(MCO) Created

56

New MBOM Rev. Created

- linked to MCO

59

Plan (BOP)Affected?

Plan (BOP)Affected?

New Plan (BOP) Rev. Created- linked to

MCO

61

Yes WIP Affected?

WIP Affected?

Shop Order Maintenance

- linked to MCO

67

YesMCO State Changed to Complete

57

&

No

No

Non-Conformance

Identified

63

Stop SO Work

72


81

SO Materials Installed & Operation

Tasks Complete

71


Created

70

As Built Records

Transferred

49

As Built BOM received

from MES/ERP

48

Validate As Built

Configuration

50


As-Built Validated

New Part Revision Created

60

New BOM Revision

Created with Effectivity

58

New Routing Revision Created

62

Shop Order Released and/or

Updated with New Routing

& BOM Revisions

69

Shop Order Material Issues &

Operations Closures

68


Created

70

As Built Records

Transferred

49

Stop Work


18

Investigate Long-Term Resolution

Create Change


11

Execute the Implementation

Plan

27

Manage Results

Validation and Release

34Close the

Change Item

10


14

Resolve with Informal Change Implementation

Create New BOM Item Revisionwith Effectivity in ERP(Resulting BOM Item)

Restart Shop Order

Restart SO Work

64

Restart Work


Effectivity Updated on

BOM Revision

53

&

Update Change Effectivity on


Collector

45

Approved

&

Effectivity Trigger

52

Cancel Shop Order

51

Shop Order Cancelled

66

Cancel Shop Order

Stop Shop Order

Create Waiver

16

Initiate Waiver

Make Waiver Decision

55


Create Deviation

13

Initiate Deviation

Restart Shop Order

&

Non-Conformance

Impact analysis of issue

For eg bad Pump Or

manufacturer recall

where else is it used

Change Notice As-Built

Validation

MES

ERP

5 Impact of Change Change Incorporation Integration Points


Teamcenter’s end-to-end solutions enable you to better understand the impact of

change and automate common functional processes across your lifecycle.

5 Impact of Change Impact Analysis enabled in Change Management Impact Analysis Laggards In Between Leaders

PLM Capabilities Design Release Management

Engineering Change Management

Enterprise Change Management

CAD Data Management

Release of Engineering Part Engineering Part Data

Engineering Bill of Material Engineering Documentation

Impact Analysis fully enabled in Enterprise Change Management

Visualization

Change Management

BOM Management

Document Management

Integrations

Manufacturing Process

Release of Enterprise Part Program Data

Plant Data Customer Data Supplier Data

Cost Data

Supplier Relationship

Cost Management

Program Management

Advanced Engineering

Quality Management

Impact Analysis Impact of Change is not fully

known in early stages Impact of change is limited to Design and Engineering Data

Impact of Change is Well Known in early stages

Change Implementation Only Design Change can be

implemented

Change Process that manages the release of Engineering

Data

Implementation of Change is stable at Enterprise level


5 Impact of Change Design Release Management

Release Process for CAD at different milestones using one of the following methods

Quick Release Process

Simple Design Release Process

Complex Design Request Process

CAD Impacts CAD Readiness Release CAD

Single step process that

locks down CAD

Few step process that includes reviews and

approval of CAD

More formal process that allows Engineer to communicate his CAD

requirements

Reuse of localized Design Data

Reuse of Local Engineering Information

Reuse of Engineering discipline Knowledge


5 Impact of Change Impact Analysis enabled by Enterprise Part


Align Teamcenter-driven sourcing data with the BOM to provide insight into supplier

cost impact on the final product

5 Impact of Change Manufacturing Impact Analysis


5 Impact of Change Plant Specific Manufacturing Impacts


To support the Implementation of a change at multiple Manufacturing facilities

typically the ECN is broken into plant specific MCN’s.

The MCN process is used to incorporate updates to a Plant Specific BOM, BOP

and push to ERP. These MCN’s conduct Local Impact

Analysis to meet local requirements

5 Impact of Change Impact Analysis with Alternates

Anytime there are design constraints or design parameters restrictions, impact analysis can be done with combination of where-used and Alternates/Substitutes features

If there is a part that’s causing recalls or returns, it can be replaced by Alternates by

searching where-used

5 Impact of Change Overseers of Impact of change

Requestor Analyst Change

specialists Change Review

Board Change implementation

board

Creates a change object or is delegated a change object by another requestor. The requestor is responsible for elaborating

the definition of a change and for providing as much detail as possible to

define the problem or request at hand. A requestor may perform the elaboration,

or a change specialist may delegate responsibility for elaborating a change to

another user (an analyst or requestor). When you create a change object, you are its requestor. If responsibility is delegated

to another user, that user becomes the current requestor and you are no longer

the requestor.

Assesses the technical feasibility of a change

or the technical feasibility of

implementing the low-level details of a

change. An analyst elaborates the details

of a change by providing a technical

recommendation, performing an impact analysis, and planning

the implementation

Facilitate and manage the movement of a change or deviation

through the appropriate processes

at a site. Change specialists also work to continuously improve

the change process itself. They have an understanding of

product definitions and a site’s change

process.

Reviews, approves, and authorizes enterprise change requests and

deviation requests. The review board makes a

business decision about whether a change or

deviation request should proceed. Review board members are generally senior individuals from various functional areas

within a site or individuals who have expertise in

some aspect of a change or deviation

Reviews, approves, and authorizes change notices. This group reviews

the detailed implementation plan for an enterprise change notice and makes a technical decision about

whether to implement the planned change. The group also makes an

implementation plan and decides the . The membership of the

implementation board generally includes both people with technical

knowledge and managers with control of resources and schedules.

Membership may vary depending on the complexity, cost, and other

characteristics of a change

Change Management Tracks changes to a product throughout its life cycle.

You propose a change to a product and then manage the entire cycle of review, approval, and implementation of the change.

You can articulate the work required to Implement a change.

Assess its impact on any managed business items, such as parts or documents. Notify life cycle participants about proposed and authorized changes.

Track progress and completion of work. Compare before and after product configurations

Three Key Change States

Closure Maturity Disposition

Defines the status of the change object.

Change objects start with an open status

and remain there until the change is complete unless a

decision is made to defer or cancel the

change

Defines the degree of completion of the open change object. The elaborating state is the planning phase. The reviewing state can be informal where one user approves the change, or formal where a review board must approve. Reviewers can decide

the change is not ready and send it back to the planning phase or approve the change. Once

approved, the change moves to the executing state and the changes begin. Finally, the change is

considered complete

Represents a technical, business, or implementation decision by a person or review board about a change

object's approval. Prior to review, there is no disposition assigned. If the reviewers approve the

change, the ECN process is initiated. Approved ECNs proceed to execution. If the reviewers reject the

change, it is closed. If the reviewers defer the change, it is placed on hold. If the reviewers think the change is not ready, it returns for more planning. At any time in

the process, the change can be cancelled.

Open Closed

On hold Cancelled

Elaborating Reviewing Executing Complete

None Investigate Approved

Disapproved Deferred

5 Impact of Change TC States in context of Analyzing Impact

5 Impact of Change SDG Use Case Goals

Use Case #

Use Case Description

Current State - Situation Goal # Future State Goals

5.1.1

Must provide impact of

change where used including analysis, work instructions,

WIP

Impact Analysis

A design engineer initiates a change request to a solid model or other

managed object in the PLM. As part of the business process for change, the PLM application generates a list of items related to the object that could be impacted by this change.

Examples include:

work in process, drawing, analysis, work instructions, fixtures, CMM and

NC programs.

1 Provide the change initiator with all of the information necessary to manage a change as early in the change process as possible.

2 Show notifications and action(s) queued to be taken by effected stakeholders via workflow or other means.

3 Show the ability to store a “package” of the entire change for future reference.

4 Show the ability to group managed data or objects into a more encompassing change to reduce the quantity of individual change notices

5 Show the change form that holds all the metadata about the change.

6 Show a record of the dispositions, drivers and design intent of the change and effectivity.

6.1 Show how to communicate the status1 of the various hardware and product already produced or fielded, i.e.: units shipped, inventory, WIP, etc.

6.2

Show how to communicate the impact and effectivity of the change on the hardware next higher level of the assembly, or sub components based on the disposition of the change and the hardware’s state (where it exists), i.e.: 5 known states – units shipped, parts in stock, work in process (WIP), parts kitted, parts shipped in place, etc. Dispositions are: Use (with clarifying adjectives), parts must comply (with clarifying adjectives)

7 Demonstrate some key metrics around the change process and PLM in general.

7.1 Demonstrate what type of training is needed for users to develop desired metrics.

8

Demonstrate the ability to have unincorporated changes to a model recorded (IP lessons learned objects) to defer the cost of change to a point in the business process where that cost can be borne by active program.

5 Impact of Change Required Teamcenter Modules

Teamcenter Template or Interface or Custom

Interface Functional Capabilities

Technical details Supported versions,

and sunsetting, Sustaining, and other compatibility details

Integration 1 - Exists

2 - TC Module

0 - Doesn't Exist

TC Module Names

TC Module Versions

5.1.1

Must provide impact of change where used

including analysis, work instructions,

WIP

Impact Analysis

Requirements management Captures and traces software functionality, ensuring design teams are

implementing what your customers want. 2

Systems engineering and modeling

Enables your development teams to define the system and model’s functional behavior; improves quality and streamlines the development process by

providing all stakeholders with a system-level understanding of the product and how each of its components fits together.

2

Software configuration management

Leverages integration with third-party software configuration management solutions, enabling development teams to facilitate software change

management and elevate change management to the system level, hereby improving productivity across the software development lifecycle.

2

Configuration and calibration parameter management

Manages the structure and architecture of calibration and configuration parameters across multiple products and variants; helping to increase design re-

use and better determine the type and size of memory required.

2

Software dependency and compatibility management

Manages the interdependencies of multiple signals, binary-to-binary, binary-tohardware and hardware-to-hardware, thereby ensuring product quality.

2

Software design component management

Manages software design data embedded into system components; enabling the use of configuration and integrated change management applications, build

processes, software product lines (SPL), was well as options and variants.

2

Product configuration and variant management

Provides a holistic approach for controlling product changes at the system level; defines which software modules can or should be flashed onto processors for

various product configurations, thereby improving product re-use and ensuring product reliability.

2

Change management

Incorporates software into the overall change management process and verifies software changes in relation to the entire system, enabling your teams to analyze

change impact on the basis of product dependencies and thereby improve product reliability.

2

Product and process management

Allocates resources, defines schedules and hardware/software dependencies and monitors progress to enable your teams to meet product cost and delivery

schedule objectives.

2

Multi-site design collaboration

Manages both hardware and software product development projects on a 24/7 basis by sharing data across multiple sites.

2

5 Impact of Change Required Teamcenter Interfaces

Teamcenter Template or Interface or Custom

Interface Functional Capabilities

Technical details Supported

versions, and sunsetting,

Sustaining, and other

compatibility details

Integration 1 - Exists

2 - TC Module 0 - Doesn't

Exist

TC Module Names

TC Module Versions

Must provide impact of change where used including analysis,

work instructions, WIP

Impact Analysis

• Collaboratively performing rapid and full change management across your product lifecycle. Siemens PLM

• Systems Engineering: At Teamcenter's Core. CimData Corporation.

• History and Heritage of Civil Engineering. ASCE.

• Change Manager Guide. Siemens PLM

• PLM World and Siemens PLM Software 2015. Siemens PLM Conference Notes

• What’s New in Change Management. SPLM 2014 Change Management New Release Round table

• Teamcenter Workflow Execution Best Practices. Overview by Lee Rowlands at Siemens PLM 2015

• Change Drivers and Solution Definition. SPLM 2015 Change Management User Forum Session.

5 Impact of Change Special thanks to References

Extra Slides

5 Impact of Change Plan and Implement Change

Authorized changes are implemented by updating the product data according to an

approved plan


Groups one or more authorized change solutions for implementation

Change Notice Change Order

Schedule Manager

Project Plan Spreadsheet

Carries the plans required to implement those solutions

Implementation Plan Assigned tasks, step-by-step, to achieve the approved solution

../../WorkProduct_Templates/Change Management/ChangeImplementation.vsdx

5 Impact of Change TC OOTB Change Implementation Processes

Create Change Implementation for Change Solution Relate a Deviation Implemented by this Change Implementation

Identify the Change Implementation Relate an Incident Report Implemented by this Change

Implementation

Describe the Change Implementation Delete Change Implementation

Set Target Release Level Assign Originator

Assign Analyst Assign Change Implementation Board

Assign Administrator Relate a Business Item that Must be Replaced

Initiate Change Implementation Process Relate an Item that Provides Useful Information about this

Change Item

Create Change Implementation Without Context Relate a Business Item that Must be Revised

Create Change Implementation for Incident Report Relate a Plan

Create Change Implementation for Deviation Delete Change Item

Create Change Implementation for Change Task Relate a Business Item that Resulted From Executing the Change

Implementation

Describe Special Instructions View Change Implementation Properties

Indicate if Customer Approval Required View Change Implementation Process Status

Describe the Status of Customer Approval View Change Implementation Relationships & Related Items

Set the Date of Customer Approval View Change Implementation Participants

Relate a Change Solution Implemented by this Change Implementation

View Business Item

Create ECR item – step 1 The Analyst derives the Change Request for the Problem Report (PR) Item created by the

Requestor for a problem item (the sample Engine item is the problem item here)

5 Impact of Change Create and approve Change Request (ECR) items

Create ECR item – step 2 The Analyst chooses the Change Request Item from the list


`


Create ECR item – step 3 The details regarding the change request item are filled in. Since the Id and Revision fields are left blank, these values are automatically generated. The Analyst could also

choose to fill in these values manually.


Create ECR item – step 4 The Change Request Item is now created. Please note that the “Problem Items” pseudo folder shows the Problem Item and the “Implements” pseudo folder shows the PR Item.

`


Approve ECR item – step 5 The Analyst initiates the Workflow to approve the ECR Item


Approve ECR item – step 6 The Change Review Board members review the ECR Item, analyze the complexity, constraints

and feasibility of the requested change. The approved ECR item shows the values Open, Approved and Reviewing for the attributes Closure, Disposition and Maturity respectively

`

`

5 Impact of Change Create and approve Change Notice (ECN) items

Create ECN item – step 1 The Change Review Board member derives the Change Notice (ECN) item for the ECR Item


Create ECN item – step 2 The Change Review Board member selects the Change Notice Type to create the ECN Item

`


Create ECN item – step 3 Details regarding the Notice are entered. Since the Id and Revision fields are left blank, these values are automatically generated. The member could also choose

to fill in these values manually.


Create ECN item – step 4 The ECN Item is created showing the Sample Engine item in the “Problem Items”

pseudo folder and the corresponding ECR item in the “Implements Folder”.

`


Approve ECN item – step 5 The Change Review Board member initiates the Workflow to approve the ECN item.


Approve ECN item – step 6 The Change Implementation board members review the ECN, come up with a detailed implementation plan and approve the ECN. The ECN item now has the values Closed, Approved and Complete for attributes Closure, Disposition and Maturity respectively.

`

`

5 Impact of Change View and Search Change Management Items

Viewing Change Management Objects The Change Manager application shows all the change objects created (PRs, ECRs and ECNs)

5 Impact of Change View and Search Change Management Items

Searching Change Management Objects The Change Management objects could be searched using the saved queries built for the

Change management objects (highlighted above)

`

`

`

framework change impact analysis

Documents