|
The primary change form used for implementation is the Enterprise Change Notification (ECN). The purpose of the ECN is to establish a work plan to implement the approved ECR. The ECN has a line item for each modified part and document that is assigned to specific data Creators for processing. For example, a drawing document would be assigned to a designer as the Creator. The resulting work for each line item is also checked by a User, or consumer, of that information. For example, the Creator of a drawing is a designer and the User is a manufacturing engineer.
Change Administrator II (CAII) creates the ECN and the table of parts and documents that must be modified to implement the ECR. The planning process includes assigning people to each required data modification. It may be necessary for CAII to delegate planning activities to another technical resource; however, CAII remains responsible for the total plan. It is also CAII’s responsibility to set the effectivity for each new or revised part version. Once the plan is complete (for full track), it is sent to the Change Implementation Board (CIB) for approval prior to implementation. If the CIB believes that the plan is incomplete or inaccurate, the plan may be sent back to the CAII for further planning. The ECR/ECN package may also be sent back to the CAI for further review of the ECR if details of the implementation plan cause the cost or impact of the change to increase. The ECN creation and implementation planning activities are performed in the highlighted section of the change process shown below.
CMII Closed-loop Change Process -- ECN Creation and Implementation |
CAII is the chairperson for the Change Implementation Board (CIB). It is his or her job to schedule the meeting, set the agenda, and conduct the review. The CIB is made up of a cross-functional team of people who are empowered to review the ECN and determine if the plan is complete. The ECNs are rejected, approved, or sent back to CAII for further planning. If rework is required, the ECN remains in the Under Review state until it returns to the CIB. If the ECN is accepted, it moves to the execution phase. The ECN may also be rejected if, for any reason, the company decides the change should not proceed. If the ECN is rejected, its state is set to Cancelled. The ECR and any PRs are also set to the Resolved state.
The Implement Changes process step pictured in the diagram is performed by individual Creators and Reviewers assigned to a implementation task activity in the ECN. The Creator updates the document, making the necessary modifications per the instructions from the ECN. The Reviewer validates the changes as clear, concise and valid. If the modifications are not acceptable, they are routed back to the implementer for further update. If they are acceptable, the User approves the change and it waits for ECN audit. During this sequence of actions, the changeable data remains in the In Work state. |
