ETM 5131 – Capstone II Re-Development of New Component Implementation Process – Results By Scott Moeller.

Slides:



Advertisements
Similar presentations
COMPANY MAINTENANCE MANUAL
Advertisements

Course Material Overview of Process Safety Compliance with Standards
Configuration Management
Quality Assurance/Quality Control Plan Evaluation February 16, 2005.
Radiopharmaceutical Production
System Development Life Cycle (SDLC)
Configuration Management
CIP Cyber Security – Security Management Controls
What is a Feasibility Study (FS) and an Alternative Evaluation Report (AER)? ENVIRONMENTAL UPDATE MEETING NOVEMBER 20, 2014 HEATHER MCCOLEMAN OES MAJOR.
Ensure Vendor/Engineer of Choice Product Quality
SEP1 - 1 Introduction to Software Engineering Processes SWENET SEP1 Module Developed with support from the National Science Foundation.
How to Document A Business Management System
Chapter 3 Project Initiation
Network Design and Implementation
CSCU 411 Software Engineering Chapter 2 Introduction to Software Engineering Management.
Testing Without Executing the Code Pavlina Koleva Junior QA Engineer WinCore Telerik QA Academy Telerik QA Academy.
Project Plans CSCI102 - Systems ITCS905 - Systems MCS Systems.
Architecture is More Than Just Meeting Requirements Ron Olaski SE510 Fall 2003.
Final Report Document. Format Title Page Executive Summary Table of Contents Introduction Mission Statement Main PDS items Brief justification of the.
2. Discussion question It has been suggested that more ethical mistakes result from failure of imagination than from failure of moral principle. If you.
SE 555 Software Requirements & Specification Requirements Validation.
Computers: Tools for an Information Age
System Development Life Cycle (SDLC)
Pertemuan Matakuliah: A0214/Audit Sistem Informasi Tahun: 2007.
Chapter 4 After Green Light. After the Green Light Contractual Agreement Marketing Requirements Document (MRD) Project DefinitionBudget Project Approval.
Chapter 3 Project Initiation. The stages of a project  Project concept  Project proposal request  Project proposal  Project green light  Project.
Software Documentation Written By: Ian Sommerville Presentation By: Stephen Lopez-Couto.
Welcome to CMPE003 Personal Computer Concepts: Hardware and Software Winter 2003 UC Santa Cruz Instructor: Guy Cox.
Change Request Management
Data Structures and Programming.  John Edgar2.
Project Life Cycle Introduction and Overview © Ed Green Penn State University All Rights Reserved.
Module 9 Session 9.2 Visual 1 Module 9 Designing Control and Reporting Systems (Time, Cost, Resources and Scope (Performance and Quality)) Session 9.2Managing.
Copyright © 2003 by Prentice Hall Computers: Tools for an Information Age Chapter 14 Systems Analysis and Design: The Big Picture.
Systems Analysis and Design: The Big Picture
Basic Principles of GMP
CHAPTER 5 Infrastructure Components PART I. 2 ESGD5125 SEM II 2009/2010 Dr. Samy Abu Naser 2 Learning Objectives: To discuss: The need for SQA procedures.
Review of Draft AC 021 – Maintenance Contracting Draft AC 022 – Task and Shift Handovers Nie Junjian Airworthiness Inspector COSCAP-NA.
VALIDATION METHODOLOGY
Commissioning of Fire Protection and Life Safety Systems Presented by: Charles Kilfoil Bechtel National Waste Treatment Plant Richland WA.
Copyright 2002 Prentice-Hall, Inc. Chapter 1 The Systems Development Environment 1.1 Modern Systems Analysis and Design.
Evaluation and Recommendation of a Flow Computer For Replacing Chart Recorders ETM 5121 Project Proposal Submitted By Toby O’Brien.
Certification and Accreditation CS Phase-1: Definition Atif Sultanuddin Raja Chawat Raja Chawat.
1 Project Management Introduction. 2 Chap 1 What is the impact? 1994: 16% of IT projects completed “On-Time” 2004 : 29% of IT projects “On- Time” 53%
Chapter 101 The Design Process Chapter 10 Achieving Quality Through Continual Improvement Claude W. Burrill / Johannes Ledolter Published by John Wiley.
Software Testing and Quality Assurance Software Quality Assurance 1.
SYSTEMS ANALYSIS AND DESIGN LIFE CYCLE
Applied Software Project Management
1 Presentation Template: Instructor Comments u The following template presents a guideline for preparing a Six Sigma presentation. An effective presentation.
Paul Hardiman and Rob Brown SMMT IF Planning and organising an audit.
The Long Tail Why the future of business is selling less of more ▫ISBN = ▫Chris Anderson Low Distribution and Inventory costs allow companies.
 2001 Prentice Hall Business Publishing, Accounting Information Systems, 8/E, Bodnar/Hopwood Systems Implementation, Operation, and Control Chapter.
Configuration Management and Change Control Change is inevitable! So it has to be planned for and managed.
1 Getting Started : Purposes of IS Strategic Planning.
1. 1.To examine the information included in business reports. 2.To understand how to organize documents in order to ensure clear communication. 3.To analyze.
Software Engineering Process - II 7.1 Unit 7: Quality Management Software Engineering Process - II.
USDA 2016 Financial Management Training Transforming Shared Services Change Management Presented by Ron Gros.
Change Request Management
Office 365 Security Assessment Workshop
System Development Life Cycle (SDLC)
Software Documentation
System Development Life Cycle (SDLC)
Description of Revision
Engineering Processes
CLINICAL INFORMATION SYSTEM
Systems Analysis and Design
System Development Life Cycle (SDLC)
Engineering Processes
Software Reviews.
Radiopharmaceutical Production
Presentation transcript:

ETM 5131 – Capstone II Re-Development of New Component Implementation Process – Results By Scott Moeller

2 Table of Contents Title Slide Number Introduction………………………………… 3 Problem Summary/Statement …………… 4 Alternatives Listed………..……………….. 7 Alternative #1 Summary/Findings………… 9 Alternative #2 Summary/Findings/Conclusions..11 Alternative #3 Summary/Findings/Conclusions..13 Alternative #1 Results………………………14 Conclusions and Recommendations…....19

3 Introduction American Airlines modifies existing aircraft by installing new components for a various reasons

4 Problem Summary/Statement Modifications have numerous problems Major Issues – Maintenance problems with ease of installation and removal of new components still exist (Product Improvements Identified) – New components do not physically fit the actual aircraft without some minor re-work (Late Finds Discovered)

5 Problem Summary/Statement - Continued Minor Issues Technical data not readily available for mechanic’s use Piece-parts are found missing, breaking, or not stocked at key locations

6 Problem Statement/Summary Problem Statement: Lack of role definition during the implementation process of a new component installation contributes to miscommunication, ultimately costing the company additional money for re-work costs Typically a 5% budget over run is experience (parts problems only, not labor)

7 Alternatives Listed Alternative #1: Modify existing process to incorporate a best practices process learned from other companies partaking in similar situations Alternative #2: Keep existing process in place, unchanged, yet highly publish the process so as that role definition is clearly identified Alternative #3: Supplement existing process with one that contains better role definition

8 Alternative #1: Summary/Findings/Conclusions Several companies contacted: PCS, Jacobs Engineering, Caterpillar, US Gypsum, Chevron- Texaco, and Monsanto-Enviro Chem Caterpillar (CAT) and US Gypsum (USG) found to have similar situations: Spec-out new equipment manufactured by outside vendors, either off-the-shelf, or customized. CAT and USG yielded no known budget over run, no after-the-fact Product Improvements, and no Late Finds

9 Alternative #1: Summary/Findings/Conclusions - Continued CAT – Sumter, SC – Formally documented process – Engineering creates specifications – Production provides a dedicated representative – Engineering and Production can object to anything in the Spec, or any design feature, but Engineering has final decision – Constant communication exists between Engineering and Production (close physical proximity, also)

10 Alternative #1: Summary/Findings/Conclusions - Continued USG – Fairview, OK – No formally documented process, but protocol well-known – Engineering creates specifications – Production provides a dedicated representative – Engineering and Production can object to anything in the Spec, or any design feature – Final decision rests with either Engineering or Production depending on the project phase – Constant communication exists between Engineering and Production – Team members selected based on expertise and availability

11 Alternative #2: Summary/Findings/Conclusions – Three (3) parts: Two page initial planning checklist Planning Flow chart Engineering checklist

12 Alternative #2: Summary/Findings - Continued – Initial Planning Checklist: Provides basic information, but does not provide role definition for the design and implementation phases – Planning Flowchart: Provides approval process and stops when the implementation (and design) begins – Engineering Checklist: Only one step listed for coordinating with Production left extremely vague – Conclusion: Simply publishing the existing process will not solve the problem, as lack of role definition is still not addressed

13 Alternative #3: Summary/Findings/Conclusions Supplementing existing planning process with one that contains better role definition This has been determined as one of the best practices found in Alternative #1 Conclusion: Testing Alternative #1 will incorporate Alternative #3

14 Alternative #1 - Results Alternative #1 (Best Practices) Tested on MD80 Sliding Carpet project Following best practices were incorporated – Assigned dedicated Production representative – Assigned dedicated Engineering representative – Both Engineering and Production agreed upon the priority of the project – It was understood who had final decision authority (Production)

15 Alternative #1 – Results (Continued) Following best practices were incorporated – continued – Written concurrence on design features was given, prior to initial installation, by both Engineering and Production – Engineering and Production representatives selected based on their technical experience – Production and Engineering attended all design reviews

16 Alternative #1 – Results (Continued) Following best practices were incorporated – continued – Production and Engineering witnessed installation on another carrier – Production representative ensured supporting technical documents released and readily available prior to first installation – Outside vendor representative on-site for initial installation

17 Alternative #1 – Results (Continued) Following best practices were incorporated – continued – Inventory Control previously stocked anticipated spares prior to initial installation – Production representative verified spares availability prior to initial installation

18 Alternative #1 – Results (Continued) MD80 Sliding Carpet Project was successful – Initial installation completed with no budget over run, no after-the-fact Product Improvements Identified, no Late Finds Discovered – Can be attributed to clear communication and role responsibility between Engineering and Production

19 Conclusions and Recommendations Conclusions: – Production and Engineering both need to be included in the project from the very start (get the right people on the bus) – There needs to be a dedicated representative from both Engineering and Production – Production shall give written concurrence on the Engineering Specifications – End Result: Roles were amply defined, and it paid off with a successful project

20 Conclusions and Recommendations (Continued) Recommendations: – “Best practices” as tested on the MD80 Sliding Carpet project shall be incorporated into each project – These “best practices” shall be listed in both the General Procedures Manual (GPM) and Engineering Procedures Manual (EPM) for purposes of consistency

21 Q&A Session ?????????????????????????