Engineering Change Notice Engineer training

Transcription

1 Engineering Change Notice Engineer training

2 Rules(1/2) No phone calls in the training room I know you are busy, if the phone call is urgent, take it and I will cover what you missed at the end if necessary No s

3 Rules (2/2) Questions I will try my best to answer any of your question If I can t during the training session, I will sent you the answer by if you so desire. Michel.jacques-ext@faurecia.com Speak to low Speak to fast Let me know as soon as possible so I don t waste your time.

4 Outline Part I: Engineering Change Management: FIS Process Engineering change management process: an overview ECN lifecycle Part II: The New ECN Application Creating an ECN Assigning task and deadlines Reviewing the work Approval Validation of Change

5 Change management Purpose: Consistent performance improvement Better KPI reporting Pinpoint areas of concern (Lessons Learned) Note differences between successful and failed changes Facilitate communication and track changes Cost control Preventing duplicate efforts Quality control Prevent corrective efforts Deadlines and Timing: Controlling the Rush

6 Change Management at FIS (1/6) How to we change our product: ECR ECO ECN MCO MMR PDW

7 Change Management at FIS (2/6) Engineering Change Request : ECR ECO MCO ECN MMR PDW Anyone can initiate an ECR in Galileo Encompasses Change Analysis and Assessment How change is implemented Costs Plants affected are involved in these assessments Weekly Change Meetings Change Coordinator and Plant Change Coordinator If approved by Program Manager an ECO will be created

8 Change Management at FIS (3/6) Engineering Change Order : ECR ECO MCO An ECO is generated in Galileo Linked to originating ECR Product Engineer and PDM BOM analyst alter BOM and validate changes At the end of this process, the BOM is ready to be transferred to FCS ECN MMR PDW

9 Change Management at FIS (4/6) Manufacturing Change Order : ECR ECO MCO ECN MMR An MCO is created for each plant affected by the change defined in the ECR and ECO. MCO makes the transfer from Galileo (PLM) to FCS (ERP) The transfer of a BOM into FCS does not automatically update all purchasing, sales, and tooling views: the MMR is created for these updates. PDW

10 Change Management at FIS (5/6) Material Master Request : Part Data Worksheet: ECN ECR ECO MCO MMR This document acts as a checklist for those responsible for views in SAP (FCS Production) Tooling Purchasing Sales Typically at R&D site Not a Plant responsibility PDW

11 Change Management at FIS (6/6) Engineering Change Notice : ECR ECO MCO ECN MMR PDW Document for Plant use Implementing the Change at the Plant level Should occur after the ECO Dependent on timing Task list Plant Change Coordinator Responsible for document Coordinates change implementation

12 Who are the key actors? Product Engineer/Manufacturing Engineer Plant Engineering Change Coordinator (PECC) Plant Quality Manager Plant Engineering Director/Manager Task Responsible

13 The ECN process (1/8) Lifecycle Overview (As supported by the Application)

14 The ECN process (2/8) Create Responsible: Activities: Product engineer or; Manufacturing engineer. ECN Creation Giving the most details about the change

15 The ECN process (3/8) Plant ECC Responsible: Activities: Plant Engineering Change Coordinator (PECC) Assessment of each task based on the nature of this change If a task is required, an responsible must be name and a due date given

16 The ECN process (4/8) Evaluate Responsible: Activities: Task Responsible PECC Performing the physical task Notifying the PECC by: Uploading evidence Mark the task as complete (Signature)

17 The ECN process (5/8) ECC Review Responsible: Activities: PECC Reviewing each evidence Deciding if the task was done as per standard Refused task will be sent back to its responsible Accepted task will be locked down

18 The ECN process (6/8) Approval Responsible: Activities: Engineering Manager Plant Quality Manager Review the ECN Each gives its approval Both approvals required If refused, sent back to the PECC

19 The ECN process (7/8) Validation of Change Responsible: Activities: Plant Quality Manager Answer Did the change have the intended result? User for traceability and follow up

20 The ECN process (8/8) Closed Responsible: Activities: None None

21 The Software Designed for Internet Explorer Designed by the EIT Team based on User Input Faster More intuitive and easier to use Evolving Engineer Password: abcd

22 The remaining part of the training is a live demonstration Supporting documentation can be found under the help section

23 The End