Default Lists for Engineering Change

The engineering change process uses member lists and route templates for reviews, approvals, and notifications. This reflects changes in CR and CO policies as of version V6R2009.

This page discusses:

Distribution List

A distribution list is a member list used for notifications. The CR and CO processes use distribution lists as a means to notify users of process changes. The distribution list is assigned on create of the CR or CO and can be edited from the Edit forms.

When a CR with a route-based policy is promoted from the Review to Plan CO state, all members of all attached distribution lists are automatically notified that the CR is being promoted. No duplicate notifications are sent if a person is a member of multiple lists and no notification is sent to the user who promotes the CR.

Note: The distribution list is not seen or used by a CR with an old (signature-based) policy since the old product line's change board members are used for notifications.

When a CO with a route-based policy is promoted from the Review to Release state, all members of all attached distribution lists are automatically notified that the CO is being promoted. No duplicate notifications are sent if a person is a member of multiple lists and no notification is sent to the user who promotes the CO.

Note: The distribution list is not seen or used by a CO with an old (signature-based) policy.

For details, see Member Lists.

Reviewer List

A reviewer list is a route template with a base purpose of Review that defines the list of people who should review the CR or CO before it is promoted to a specified state. The route template, which will be used for creating the reviewer route, is connected to the CR or CO. The reviewer list can be assigned when the CR or CO is created and can be edited from the Edit forms.

When a CR with a route-based policy is promoted from the Evaluate to Review state, a route is created using the reviewer list route template. This route is placed between the Review and Plan CO states and is a state-blocking route, which means that all tasks must be completed before the CR can be promoted to Plan CO. The route template that is used here must have a Route Base Purpose of "Review," but the route that is created from the template must have a Route Base Purpose of "Standard." This allows the tasks to have an action of either Approve or Reject, among others. The route must also have a Route Completion Action of "Promote Connected Object." When the last signature is approved, the CR is promoted to the Plan CO state.

Note: To release a configured structure with an unconfigured child part that is connected to same CO:
  1. Change the generated approval Route Completion Action from "Promote connected objects" to "Notify Route Owner".
  2. Complete the related CO

When a CO with a route-based policy is promoted from the Define Components to Design Work state, a route is created using the reviewer list route template. This route is placed between the Design Work and Review states and is a state-blocking route, which means that all tasks must be completed before the CO can be promoted to Review. The route template that is used here must have a Route Base Purpose of "Review," but the route that is created from the template must have a Route Base Purpose of "Standard." This allows the tasks to have an action Notify Route Owner of either Approve or Reject, among others. The route must also have a Route Completion Action of "Notify Route Owner."

Note: The Reviewer List is not seen or used by a CR or CO with an old (signature-based) policy since signatures are used for reviews.

For details, see Route Templates.

Default Reviewer Route Templates

The table below describes recommended default reviewer route templates for CRs and COs.

Template Name

Route Instructions

Route Base Purpose

Task Edit Setting

Description

CO Review

The CO needs review

Review

Extend Task List

This Route Template is used to create the Route placed between the Define Work and Review states on the CO.

CR Review

The CR needs review

Review

Extend Task List

This Route Template is used to create the Route placed between the Review and Plan CO states on the CR.

The template should have Enterprise Availability and be connected to Company "Company Name." The scope of the template is the Change Responsibility organization. The "Route Base Purpose" is "Review." The default route template should have a "Task Edit Setting" of "Extend Task List" so that mandatory tasks cannot be removed, but additional ones can be added.

The CO Review template should have the following role-based task.

Task Name

Route Task User

Approvers Responsibility

Comments

Instructions

Route Action

Seq

RT-SDE

role_SeniorDesignEngineer

Engineering

This change requires your approval.

Need your approval.

Comment

1

The CR Review template should have the following role-based tasks.

Task Name

Route Task User

Approvers Responsibility

Comments

Instructions

Route Action

Seq

RT-SDE

role_SeniorDesignEngineer

Engineering

This change requires your approval.

Need your approval.

Comment

1

RT-SME

role_SeniorManufacturingEngineer

Manufacturing

This change requires your approval.

Need your approval.

Comment

1

RT-Chairman

role_CRChairman

Engineering

This change requires your approval.

Need your approval.

Comment

2

Approval List

An approval list is a route template with a base purpose of Approve that defines the list of people that must sign or approve a CR or CO before it is promoted to a specified state. The approval list can be assigned when the CR or CO is created and can be edited from the Edit forms.

When a CO with a route-based policy is promoted from the Define Components to the Design Work state, a route is created using the approval list route template with a Route Base State of "Design Work." This route is placed between the Design Work and Review states and is a state-blocking route, which means that all tasks must be completed before the CO can be promoted to Review.

When the CO is promoted from the Design Work to Review state, a created using the approval list route template with a Route Base State of "Review." This route is placed between the Review and Release states and is a state-blocking route, which means that all tasks must be completed before the CO can be promoted to Release. The route templates that are used here must have a Route Base Purpose value of "Approve," but the routes that are created from the templates have a Route Base Purpose value of "Standard." This allows added tasks to have more choices for the task action.

Note: The approval list is not seen or used by a CR or CO with an old (signature-based) policy since signatures are used for approvals. action. The

For details, see Route Templates.

Default Approval Route Template

The table below describes the recommended Approval Route Template.

Template Name

Route Instructions

Route Base Purpose

Task Edit Setting

Description

CO Approval

The CO needs approval

Approve

Extend Task List

This Route Template is used to create the Route placed between the Review and Release states on the CO.

The template should have Enterprise Availability and be connected to Company "Company Name." The scope of the Template is the Change Responsibility organization. The "Route Base Purpose" is "Approve." The default route template should have a "Task Edit Setting" of "Extend Task List" so that the mandatory tasks cannot be removed, but additional ones can be added.

The CO Approval template should have the following role based tasks.

Task Name

Route Task User

Approvers Responsibility

Comments

Instructions

Route Action

Seq

RT-SME

role_SeniorManufacturingEngineer

Manufacturing

This change requires your approval.

Need your approval.

Approve

1