MaryLouFrancis さんのグループアクティビティ

Change Management

Tom Semeraro — Fri, 12 Jun 2020 19:09:12 GMT

with Aras Innovator Version 12

Description

Aras Innovator provides both industry-standard and adapted approaches to Change Management, enabling your organization to incorporate a process that matches your requirements in complexity, control, and efficiency.

Topics

Prerequisites

https://youtu.be/Bsfhzm6hkxg

Note
The exercises in this online course assume you are working with the Innovator 12 training database, which is pre-populated with data and items for practice. While many of the procedures are the same in any environment, you will see varying results working with different data in a different environment.

Express ECO Workflow Overview

Rennie-Renee Warren — Mon, 22 Jun 2020 16:58:39 GMT

The Express ECO workflow process changes the status (lifecycle state) of the ECO. It also changes the status of the affected parts on the ECO and assigns activities to appropriate identities.

Express ECO Roles

The ECO workflow process assigns the following CM identities to each activity on the workflow map.

Creator
Team Manager
Team Member(s)
Change Control Board (CCB)

In addition, the lifecycle state of the Express ECO changes based on the selected Vote from the previous activity to select the path for the current activity (shown in red italics).

Express ECO Process

Submit ECO

When the ECO form is initially saved to the database, an assignment is sent to the Creator of the ECO to review before submittal to the Product Team.

Planning

Once Submitted, the Product Team Manager is responsible for performing an impact analysis and ensuring that each change item Action is set in the matrix. No item may be left in Review under the Item Action column on affected items or the ECO cannot continue to the next activity of the process.

The Team Manager can either vote to Start Work, activating the next activity (Draft Changes), or, if required, Submit to Plan Review by a Team Member.

Plan Review

The Product Team member can vote to Rework Plan, returning the ECO to the Team Manager, or Approve Plan, activating the next activity (Draft Changes).

Draft Changes

The Product Team Member can begin the activity of revising affected parts and BOMs on the ECO. After finishing the work, the ECO can be closed, finalizing all changes and set to Released state, or Submitted to Review to all members of the Change Control Board who perform the final review and either Approve to close the ECO or send back to the Product Team Member for rework.

Change Review

All members of the Change Control Board (CCB) identity are required to approve and close the ECO or send it back to Draft Changes activity for further work.

Close Change

The ECO is complete, and the process ends. The ECO is set to a released state and all affected items are versioned according to the Item Action selected.

Note: Some fast-track activity votes require you to enter your password to confirm your vote. An Aras Innovator Administrator can add this capability to any workflow activity path if necessary.

Results

Parts / Documents will be released
Parts / Documents will be revised
Parts / Documents will be superseded

Learn about the Engineering Document Review (EDR) process.

ECN Workflow Overview

Rennie-Renee Warren — Mon, 22 Jun 2020 16:30:01 GMT

ECN Roles

Creator as a member of CM Group
Owner (Assigned Creator)
Change Specialist II
Change Specialist III

Only members of the Configuration Management Identity group can create an ECN.

ECN Process

Typically, a member of the CM (Change Management) identity initiates an ECN. As each activity is processed, the status (lifecycle state) of the ECN changes to reflect its progress (in italics on the map).

The activities of the ECN workflow process are described below:

Submit ECN

After saving the ECN to the database, the Creator of the ECN receives an assignment to submit the ECN to planning. The Creator is responsible for completing the required information on the ECN form, and attaching any ECRs or files (if necessary) to help corroborate the change.

ECN Planning

During the ECN Planning activity, the CSII reviews the information and makes decisions about the propagation of the change regarding the parts assembly line. For example, every company has its own rules dealing with the conditions under which a part receives a new revision or maybe an entirely new part number. Also, the parent parts, or the containing assemblies, may require a change of revision or part number. The CSII considers all these changes and makes decisions and recommendations. The CSII also selects an Assigned Creator (Owner) for this ECN, who is the engineer or the technical person responsible for the technical implications of the change and its ramifications. The ECN is then transferred to the Owner during the Update Documents activity.

Update Documents

The Assigned Creator (Owner) is responsible for updating the BOMs, specifications, drawings, and any other specified documents affected by this change. The affected parts requiring the change of documents may not be only the parts being changed directly, but also the parent parts or the containing assemblies.

Review Documents

The ECN is then transferred back to the CSII who reviews the documents during the Review Documents activity. The CSII can then either reject or approve the ECN. If the CSII chooses to reject it, the assigned creator must update documents again. If the CSII votes to Approve it, the next assignment is routed to the Change Specialist III for an ECN Audit.

ECN Audit

The CSIII then makes the final decision to complete and close the ECN.

ECN Released

After the audit is completed, the ECN is released, which also automatically updates the life cycle state of the affected Parts or Documents.

Results

Parts / Documents will be released
Parts / Documents will be revised
Parts / Documents will be superseded

A running ECN process cannot be canceled, but will always end up released.

Next steps

Engineering Change Notice (ECN)

Rennie-Renee Warren — Mon, 22 Jun 2020 16:28:04 GMT

Description

After PR and ECR an ECN is required to adopt the change process. The ECN controls the process by which change is implemented within an organization. Use an ECN to release new parts and documents, and/or change or obsolete previously Released Part or Document items.

Most organizations that conform to CM2 principles would have one or more problem reports created to substantiate the desired modification. To respond to the problem reports, or as a result of proactive thinking, they initiate an engineering change request (ECR). Upon review of the ECR’s, a member of the configuration management team then creates an ECN to begin the process of making the actual changes.

Life Cycle

Workflow

Next steps

Change Management Identities

Rennie-Renee Warren — Mon, 22 Jun 2020 16:12:51 GMT

A set of groups have been defined to work within the change management process. Your Aras Innovator administrator will assign various personnel to these roles based on their responsibility in the process. The following roles have been defined:

Group	Description
Configuration Management (CM)	Configuration Management group consists of the CSI, CSII, and CSIII groups.
Change Specialist I (CSI)	Drive the change process in the organization.
Change Specialist II (CSII)	Complete the change process in the organization.
Change Specialist III (CSIII)	Implement the change in the production process of the affected part.
Change Review Board (CRB)	Responsible for several steps in the ECR process. When an ECR has wide or complex implications, the CRB is called to review the change and provide input into the process.
Assigned Creator	Owner of the part or document being changed. Usually an engineer or technical person responsible for technical implications and ramifications of change to each affected item. The Assigned Creator is responsible for updating the BOMs, specifications, drawings, and any other specified documents affected by this change.
Designated User	Responsible for managing, using, and reviewing the part.
Originator	The person who is responsible to initiate the change order. They may not be the creator of the ECO, but their identity was chosen on the ECO form as the Originator. This user does not receive any assignments unless they belong to a Change Specialist or CCB role.
Change Analyst	The person who is responsible for making assignments and processing the change order to completion. Set to Change Specialist I (CSI) by default. The CSI considers all change options to make decisions and recommendations. The CSI also confirms that correct Assigned Creators are set for each Affected Item in the ECO.
Change Control Board (CCB)	Group responsible for a full review of the change for approval (if required). All members of the CCB receive an assignment in their InBasket at the Change Review activity and all members must complete the activity to release the ECO.
Creator (Express ECO)	The creator is always the user who initially saves an ECO item. They can edit the ECO form filling in relevant fields, supply affected items, and are assigned the Submit the ECO to the Planning activity when they want it to proceed.
Change Coordinator (Express ECO)	This role is selected by the creator. This person does not receive any activity assignments from the ECO. However, they do have elevated privileges to be able to edit the ECO, change activity assignments, and cancel an ECO in progress.
Aras PLM	The Aras PLM group represents the change management workflow process and does not contain any individuals.

Team Identities and Roles

A team is defined as a group of one or more identities in Aras Innovator that are assigned a role as part of the membership. Teams can be used for adding permissions or workflow assignments and consists of the following standard roles:

Team Manager
Team Member
Team Guest
Team

Three teams are defined in the training database: Product, Tech Docs and CAD. The Product team is the default Team identity for an Express ECO and DCO. The team roles receive the activity assignments when using the Express ECO and DCO release processes. In the student database, PE Student belongs to all Team roles.

Note: For more information about creating and administering teams, see the Aras Innovator Documentation or attend the Aras Innovator Configuring Solutions course.

CM2 Change Management

DonnaS — Mon, 22 Jun 2020 16:07:55 GMT

Configuration management (CM) focuses on establishing and maintaining consistency of requirements, design, and operational information throughout a product or system's life cycle. It uses a set of prescribed rules to determine how, when and if an item can be changed. To learn more about Configuration Management and CM Principles go to www.cmpic.com

The CM2 Process was developed by the Institute of Configuration Management. The process stresses the importance of requirements and standardized change methods. This is the most complex form of change management implemented in Aras Innovator. Learn more about CM2 methodology at www.icmhq.com.

Aras Innovator follows many of the principles defined in CM2 to effectively manage enterprise change for parts and documents.

In Aras Innovator, the full scope of managed change is handled via PRs, ECRs, ECNs

	Problem Report (PR)	PRs capture pertinent data about an issue that may lead to an ECR.
	Engineering Change Request (ECR)	ECRs are initiated to request a change to a part or a document.
	Engineering Change Notice (ECN)	ECNs control changes to affected parts and notify appropriate individuals about the change.

Note: Depending on your configuration, an administrator may need to set the CM options to CM2 in order for you to have access to the CM2 item types.

Supplying Basic Part Information

ConnieBurke — Tue, 09 Jun 2020 19:31:07 GMT

The part item form contains the fields to define a new part, including the part number, name and description.

Required fields display a shaded background.
The Revision and State fields are automatically set by the system.
Item fields feature Type Ahead – the form field autocompletes as you begin typing a valid entry.

Type

You can classify a part in one of several categories. The specified classification determines the options available on the form as well as the life cycle of the part. The Aras Innovator System Administrator defines classifications as needed for business use.

Assigned Creator and Designated User

The Assigned Creator and Designated User properties are user-assigned values that dictate permissions and task assignments in workflows.

Property	System property name	Description
Assigned Creator	owned_by_id	Identifies the individual or group responsible for the design or content of the actual item, as well as the Owner of the item. The assigned creator of the actual item is not always the same person who creates the item in the Aras Innovator database.
Designated User	managed_by_id	Identifies the individual or group responsible for managing and reviewing the item.

Create a New Part Item

Login as PE Student.
From the TOC Open the Design category.
Click Parts.
In the Parts Panel click Create a New Part.
Define the new part item using the information provided below.

Part Number	P404-0011
Name	Pickup Roller
Type	Component
Assigned Creator	Component Engineering
Designated User	Component Engineering
Make or Buy	Buy
Long Description	Compatible Paper Pickup Roller
Effective Date	Choose a date one month from the current date.

Note: Item fields in the part form feature Type Ahead – the form field autocompletes as you begin typing a valid entry. As you start to type, the list option matching your text appears. Either press Enter or click to make the selection.

www.aras.com/.../8176.plm_2D00_e_5F00_03_5F00_part_2D00_pickuproller.mp4

Click Save to save your changes.

Next steps

Product Engineering

DonnaS — Tue, 09 Jun 2020 12:45:04 GMT

with Aras Innovator Version 12

Description

Product engineering encompasses the entire product life cycle from design and testing to release and deployment. The Product Engineering training topics give you hands on exercises using Aras Innovator to create parts, track suppliers and manage bills of materials (BOMs).

Prerequisites

Aras Innovator Fundamentals

Note
The exercises in this online course assume you are working with the Aras Innovator 12 training database, which is pre-populated with data and items for practice. While many of the procedures are the same in any environment, you will see varying results working with different data in a different environment.

Manually Promoting Individual Items

John Pilla — Mon, 22 Jun 2020 15:51:11 GMT

You can perform manual changes on individual items from the item view or from the search grid.

Note: To manually release or review items, all the prerequisites for manual promotion must be met.

Manually Promote Items

Release from the Part Item View

Open to view the part you wish to release.
From the More menu, select Manual Release.

The State field updates from Preliminary to Released.

Promote from the Part Item View

Open to view the part you wish to release.
Click the Promote button.
In the Promote window, select the appropriate state and click the green checkmark to complete the promotion.

The State field updates to the selected state.

Promote from Search Grid

Search for the part(s) you wish to promote.
From the main search grid, right-click the part and select Promote.
In the Promote window, double-click the desired state to Promote the item.
The item state updates to Released.

Manually Create New Revisions

If all prerequisites have been met for a manual revision, the New Revision button displays to the right of the Revision field on the item form.

Create a new revision from the Part Item View

Open to view a released part you would like to revise. If you are using the Training environment, find number 9170-1687, Ferrite core.
Click the New Revision button.
Click OK when prompted to create a new revision.
The Revision updates incrementally and the State updates to Preliminary.

Create a new revision from the More menu

Open to view a released part you would like to revise.
From the More menu, select Create New Revision. The Revision updates incrementally and the State updates to Preliminary.
Close the Part tab.

Note: Affected items on a formal release process (ECO) cannot be manually released or revised. The associated permissions allow edits to each part at the new major revision level of B.

Next steps

Learn to manually promote multiple items

Prerequisites for Manual Promotion

John Pilla — Mon, 22 Jun 2020 15:42:05 GMT

Requirements for manually releasing parts or documents

The document and part life cycles allow for the manual promotion of an item from Preliminary to Released without a formal review process.

You must be the Assigned Creator (Owner).
The Item cannot be claimed.
The Item cannot be an affected item on an existing change control process, such as any type of ECO, ECN, or DCO.

Requirements for manually revising items

You can create a new major revision of a part or document without following a formal change process.

You must be the Assigned Creator (Owner).
The Item cannot be an affected item on an existing change control process.

Assigning Ownership: The Assigned Creator is designated as the Owner identity of the part, CAD document, or document item. In order to manually revise or release a part or document, a user must be a member of the Identity selected as the Assigned Creator.

Next steps

Creating an Express DCO

John Pilla — Mon, 22 Jun 2020 16:52:49 GMT

The Express DCO form contains the following fields to define the change order:

DCO Number	Server assigned.
State	Current status of the DCO, server-generated after Save.
Priority	High, Medium, or Low
Release Date	Server generated date that DCO is approved, closed, and released.
Title	Title of the change order.
Change Reason	Why change is being made.
Change Coordinator	The Owner of the DCO responsible for moving the DCO through the process.
Team	Represents a set of roles that have assigned identities. Team Roles are used to define assignments in the Workflow. The DCO Workflow assigns work to a Team Manager and Team Members. An administrator is responsible for creating and assigning identities to Teams.
Change Description	Details about the change.

An Express DCO can be created from the Change Management category of the TOC, the Document (or CAD Document) item search grid or the More button on a Document item tab.

Releasing a New Document

To promote a new Document from the Preliminary lifecycle state to Released, you select the Add Action on the Affected Items tab and search to find the document under the New Number column.

Revising a Document

Once a Document has been released, changes are not allowed to the Document. However, you can issue an Express DCO to revise the document incrementing it to the next revision level and resetting the lifecycle back to the preliminary state, allowing modifications. By using an Express DCO, you control who and when someone can make edits to a new revision of a Document item. Select Interchangeable if the Document Revision uses the same Document Number. If a new Document Number needs to be established, leave the Interchangeable box unchecked and select a new Document item in the New Number… column.

Obsolete a Document

You can also move a Document from the Released lifecycle state to Superseded by using the DCO Delete Action.

A Superseded Document is considered no longer in use in the system either because it has been replaced with a newer version or the information contained in the Document is no longer relevant. Select the Delete Action on the affected item(s) tab. The Interchangeable and New Number columns are irrelevant.

Note: Don’t confuse the DCO Delete Action with physically deleting a Document from the database. The DCO document change Action does not modify the contents of the Document or the attached files, it flags the user community that the document should no longer be used.

Try it … Create an Express ECO to Release a New Document

From the TOC, select DCOs > Create New DCO
Fill in the fields in the form with appropriate information.
From the Affected Items tab, select the New Affected Item button to add a new empty row to the relationship grid and choose Add from the Action column drop down menu.
Click in the New Number column and select the Document item to be released. For this example, select any document in the student database.

Note: At least one affected item must be attached as a relationship before the user can complete the first SignOff.

Click save to save the data and have the server generate the DCO number, the state, and initiate the workflow process.

Express DCO Workflow Overview

John Pilla — Mon, 22 Jun 2020 16:52:02 GMT

An Express DCO has been designed to manage change for Document (and CAD Document) items. The identities shown are assigned activities and the lifecycle states of the DCO change as shown on the map in italics. Learn more about Team Identities.

Express DCO Roles

The Express DCO workflow process assigns the following CM identities to each activity on the workflow map.

Creator
Team Manager
Team Member
Change Control Board (CCB)

In addition, the lifecycle state of the Express DCO changes based on the selected Vote from the previous activity to select the path for the current activity (shown in italics).

Express DCO Process

Start

As soon as the creator fills in a Title, selects the appropriate Team, and saves the DCO, it is created with a state of New and the first assignment, Planning, becomes active.

Planning

Once a DCO has been created, it is assigned to the Team Manager of the selected Team on the DCO form. The Team Manager then decides if the Document will be submitted to authors for any changes or the DCO can be canceled closing the process.

Cancel Change

If the Team Manager votes to cancel the DCO, the process ends and the DCO is canceled.

Draft Changes

Team Member(s) of the selected Team then signal by voting when changes are complete on the Document and the DCO is assigned to the Team Manager for Initial Review.

Initial Review

The Team Manager then decides if a Full Review is necessary for the Document change, which sends an assignment to the member(s) of the Change Control Board Identity. The Team Manager can also bypass the CCB and opt for a Fast Approve which closes the DCO. (A sign-in password is required from the Team Manager to make the final approval.).

Final Review

All members of the CCB must then approve the change to close the DCO.

Close Change

The DCO process ends with this automatic activity and the release or change is complete. The related items on the Affected Items tab will also be promoted to a Released state.

Results

CAD Documents / Documents will be released
CAD Documents / Documents will be revised
CAD Documents / Documents will be superseded

Reviewing a Revised BOM

John Pilla — Thu, 02 Jul 2020 10:22:23 GMT

Once the Express ECO process is complete, the BOM changes are finished in the newly revised parent assembly. Any previous revision of the parent part assembly can be displayed by selecting Versions from the Navigate button’s pulldown menu.

Previously released versions of the parent assembly will now reflect a Superseded State.

Note: The Try it's on the Modifying BOM Relationships page must be completed to see the changes in the following Try it.

Try it … View Revised BOM using Redline View

Open the CP00011 part for viewing.
From the BOM tab in the Relationship grid, select Redline from the Display menu.
Notice the changes shown in red.
Note: You may need to expand columns to see the redlined change.

Completing the EDR and ECO Process

John Pilla — Thu, 02 Jul 2020 09:45:01 GMT

After an approval path has been selected on the EDR, the EDR workflow process ends and returns to the original control process of the parent Express ECO that spawned the EDRs.

EDR Status Changes

The EDR is set to a Pending Closure state, which is a temporary state, until the parent ECO is completed. All affected items remain at a state of In Review.

The parent Express ECO form indicates when the EDR status is Complete.

The Team Member with an active assignment of Draft Changes for the parent Express ECO must now vote to complete their current assignment. Once a vote is made to either Close the Change (fast track) or Approve the Change on the parent ECO, the ECO process ends and the EDR process officially closes at the same time.

The Express ECO and any spawned EDRs are set to a Released state. All affected items of both the ECO and the EDRs are also set to a Released state or incremented to a new revision level and released.

If an Item Action was set to Renumber or Revise for a previously released item, the previous version is now Superseded.

Any affected items that had an Item Action set to None are not changed.

Try it … Complete Activities for the Express ECO

Login as PE Student to complete the activities related to the express ECO.
Open the parent ECO. Note the form shows the EDR status as COMPLETE.
Confirm the state of the items in the Impact Matrix:
- All document and CAD documents are in the In Review state.
- All part items are in the Preliminary state.

Locate the Draft Changes assignment in your InBasket and Vote to Close Change. This is a fast track option so enter the password to complete.
Return to the parent ECO and confirm that it is now Released.
View the Impact Matrix and confirm that all affected items are in the Released state.

Viewing Signoffs

John Pilla — Thu, 02 Jul 2020 09:08:22 GMT

There are numerous ways to view the current process of the workflow and see who has signed off, including any comments that were entered.

You can use the Signoffs tab, available on the ECO, to review previous assignment decisions and to Vote if you are the active assignee for an activity.

Users can also navigate to the TOC and select My Innovator > My InBasket to see all their assignments and click the link under the Source Item column to display where they are in the ECO process. Clicking on the View Signoffs button (hand holding a pencil) will open the history report.

The Workflow History Report is also available from the ECO’s Navigation button’s pulldown menu by selecting Workflow and then clicking on the View Signoffs button. The report shows you how previous members voted.

Try it … Vote to Complete the Assignment

On the Express ECO from the previous exercise, select the Signoffs tab and click VOTE NOW on the active Planning Assignment to move the ECO along in the process.
In the Workflow Activity Completion window, vote to Start Work and click Complete. A new active assignment, Draft Changes, is generated for all Team members.
Before this can be completed, the two subflows from the EDRs spawned from the parent ECO must be completed.

Next steps

Review the EDRs

MaryLouFrancis さんの グループ アクティビティ

Change Management

Express ECO Workflow Overview

Express ECO Roles

Express ECO Process

ECN Workflow Overview

ECN Roles

ECN Process

Engineering Change Notice (ECN)

Change Management Identities

Team Identities and Roles

CM2 Change Management

Supplying Basic Part Information

Type

Assigned Creator and Designated User

Create a New Part Item

Product Engineering

Manually Promoting Individual Items

Manually Promote Items

Manually Create New Revisions

Prerequisites for Manual Promotion

Creating an Express DCO

Releasing a New Document

Revising a Document

Obsolete a Document

Try it … Create an Express ECO to Release a New Document

Express DCO Workflow Overview

Express DCO Roles

Express DCO Process

Reviewing a Revised BOM

Completing the EDR and ECO Process

EDR Status Changes

Viewing Signoffs

MaryLouFrancis さんのグループアクティビティ