ANSI/EIA - 748 - A - 1998 EIA STANDARD Earned Value Management Systems Overview May 2, 2006 NDIA Program Management Systems Committee Walt Berkey, Lockheed.

Slides:



Advertisements
Similar presentations
1 Budgets and Budgetary Control Prepared and Presented By Gladstone K. Hlalakuhle.
Advertisements

ISO 9001:2000 Documentation Requirements
1 ANSI/EIA A STANDARD Earned Value Management Systems Proposed Changes Discussion January 31, 2007 NDIA Program Management Systems Committee.
Information Risk Management Key Component for HIPAA Security Compliance Ann Geyer Tunitas Group
Chapter 7: Key Process Areas for Level 2: Repeatable - Arvind Kabir Yateesh.
1 NDIA Earned Value Management Application Guide Status Report May 3, 2005.
How to Document A Business Management System
Blues Chapter CSEP 1 Earned Value Management System (EVMS) Ron Fradenburg Blues Chapter President 19 March 2013 For more information visit:
Page 1 National Defense Industrial Association (NDIA) Program Management Systems Committee (PMSC). NDIA Earned Value Management Systems Intent Guide Overview.
National Aeronautics and Space Administration ANSI/EIA-748-B Earned Value Management Systems (EVMS) 32 Guidelines ANSI/EIA-748-B Earned Value.
Project Management Session 7
Chapter 5: Project Scope Management
Configuration Management
ANSI/EIA -748 EVMS 32 Guidelines National Aeronautics and Space Administration.
Quality Manual for Interoperability Testing Morten Bruun-Rasmussen Presented by Jos Devlies, Eurorec.
Prepared by Long Island Quality Associates, Inc. ISO 9001:2000 Documentation Requirements Based on ISO/TC 176/SC 2 March 2001.
OHT 2.1 Galin, SQA from theory to implementation © Pearson Education Limited 2004 Software Quality assurance (SQA) SWE 333 Dr Khalid Alnafjan
Quality Management Systems P.Suriya Prakash Final Mech Vcet
Degree and Graduation Seminar Project Management Processes
The Key Process Areas for Level 2: Repeatable Ralph Covington David Wang.
Chapter 4 Interpreting the CMM. Group (3) Fahmi Alkhalifi Pam Page Pardha Mugunda.
Introduction to Software Quality Assurance (SQA)
Standards and Standardization. Standard Levels Standards preside according to the level. Their effect, image and their scope of work change from one level.
Copyright © 2009 NDIA PMSC Robert Loop August 2009 NDIA PMSC Guides Working Group Status.
OSF/ISD Project Portfolio Management Framework January 17, 2011.
OHT 23.1 Galin, SQA from theory to implementation © Pearson Education Limited 2004 The benefits of use of standards The organizations involved in standards.
1 ANSI/EIA A EIA STANDARD Earned Value Management Systems Potential Changes Discussion August 15, 2006 NDIA Program Management Systems Committee.
ISO 9000 & TOTAL QUALITY ISO 9000 refers to a group of quality assurance standards established by the International Organization for Standardization.This.
Cost Principles – 2 CFR Part 200 Subpart E U.S. Department of Education.
Soft Tech Development Inc. 1 Software Project Tracking A CMM Level 2 Key Process Area Soft Tech Development Inc.
1 Program Management Systems Committee Joint Industry/Government Meeting May 21, 2009 EVM for Service Contracts Working Group.
Centro de Estudos e Sistemas Avançados do Recife PMBOK - Chapter 4 Project Integration Management.
Certification and Accreditation CS Phase-1: Definition Atif Sultanuddin Raja Chawat Raja Chawat.
1.  Describe an overall framework for project integration management ◦ RelatIion to the other project management knowledge areas and the project life.
© MCR, LLC MCR Proprietary - Distribution Limited Earned Value Management Application, Guidance, and Education Neil F. Albert President/CEO MCR, LLC
Georgia Institute of Technology CS 4320 Fall 2003.
NDIA Program Management Systems Committee APM Reciprocity Agreement GEIA Engineering Bulletin Progress Report August 21, 2004 Walt Berkey, Lockheed Martin.
Lab-Wide Earned Value Management System Project Core Team Kickoff Meeting April 16, 2008 Dean A. Hoffer.
Office of Management and Budget NDIA Program Management Systems Committee May 3, 2005 EVMS Compliance Requirements David Muzio.
1 NDIA Earned Value Management Application Guide Status Report August 16-17, 2005 Wayne Abba Walt Berkey David Muzio David Treacy NDIA EVM Application.
QUALITY MANAGEMENT STATEMENT
Michael Campe U.S. Army Aviation and Missile Command NDIA TID Technical Information Division Symposium Royal Sonesta Hotel, New Orleans, LA August 2003.
PU-PPPL Earned Value Management System Overview Thomas Egebo October 4-6, 2011 Princeton University Plasma Physics Laboratory EVMS Certification Review.
APPLICATION GUIDE January 27, 2006 Overview May 2, 2006 NDIA Program Management Systems Committee Walt Berkey, Lockheed Martin Telephone ;
1 EMS Fundamentals An Introduction to the EMS Process Roadmap AASHTO EMS Workshop.
Evaluate Phase Pertemuan Matakuliah: A0774/Information Technology Capital Budgeting Tahun: 2009.
The Project Plan Plan Your Work, then Work Your Plan
~ pertemuan 4 ~ Oleh: Ir. Abdul Hayat, MTI 20-Mar-2009 [Abdul Hayat, [4]Project Integration Management, Semester Genap 2008/2009] 1 PROJECT INTEGRATION.
Presented to: NDIA By: Keith Kratzert Date: February 1, 2006 Federal Aviation Administration Improving Program Performance at FAA.
1 Chapter 11 Planning. 2 Project Planning “establishing a predetermined course of action within a forecasted environment” “establishing a predetermined.
SE513 Software Quality Assurance Lecture12: Software Reliability and Quality Management Standards.
1 The Voice of the Industrial Base 1 IBR Guide NDIA PMSC Working Group NDIA PMSC Meeting August 7, 2007 Prepared by; NDIA IBR Working Group August 2007.
Company LOGO. Company LOGO PE, PMP, PgMP, PME, MCT, PRINCE2 Practitioner.
1 The Voice of the Industrial Base 1 IBR Guide NDIA PMSC Working Group NDIA PMSC Meeting April 24, 2007 Prepared by; NDIA IBR Working Group April 15, 2007.
Organizations of all types and sizes face a range of risks that can affect the achievement of their objectives. Organization's activities Strategic initiatives.
0 Earned Value Management. 1  What is it?  Where did it come from?  What’s so special about it?  How do you do it?  What is an EVMS?
LECTURE 5 Nangwonvuma M/ Byansi D. Components, interfaces and integration Infrastructure, Middleware and Platforms Techniques – Data warehouses, extending.
Security Methods and Practice Principles of Information Security, Fourth Edition CET4884 Planning for Security Ch5 Part I.
S TANDARDS, CERTIFICATION AND ASSESSMENT C HAPTER 23 Dr. Ahmad F. Shubita.
AUDIT STAFF TRAINING WORKSHOP 13 TH – 14 TH NOVEMBER 2014, HILTON HOTEL NAIROBI AUDIT PLANNING 1.
Introduction for the Implementation of Software Configuration Management I thought I knew it all !
ANSI/EIA-748-B Earned Value Management Systems (EVMS)
Software Quality Control and Quality Assurance: Introduction
TechStambha PMP Certification Training
Earned Value Management
(Additional materials)
EVM 202—Lesson 3 EVMS Guidelines and Compliance
Quality management standards
Project Management Process Groups
Managing Project Work, Scope, Schedules, and Cost
Presentation transcript:

ANSI/EIA A EIA STANDARD Earned Value Management Systems Overview May 2, 2006 NDIA Program Management Systems Committee Walt Berkey, Lockheed Martin Telephone ; NDIA ANSI-EIA-748 Overview

AGENDA Cover Page NOTICE Foreword 1. INTRODUCTION 2. EVMS GUIDELINES 3. EVMS PROCESS DISCUSSION 4. SYSTEM DOCUMENTATION 5. SYSTEM EVALUATION

Cover Page EIA STANDARD Electronics Industries Alliance Government Electronics and Information Technology Association ANSI/EIA-748-A-1998 Approved: May 19, 1998 Reaffirmed: August 28, 2002

NOTICE EIA Engineering Standards and Publications are designed to serve the public interest through eliminating misunderstandings between manufacturers and purchasers, facilitating interchangeability and improvement of products, and assisting the purchaser in selecting and obtaining with minimum delay the proper product for his particular need. Standards and Publications are adopted by EIA in accordance with the American National Standards Institute (ANSI) patent policy. Formulated under the cognizance of the ADPA/NSIA (now NDIA) Management Systems Subcommittee with association support from the ASA, EIA, PMA and SCA. With authorization from the GEIA SSTC (Systems Standards & Technology Council) This document was reaffirmed by the American National Standards Institute on August 28, 2002 and by the EIA

Foreword The processes include integration of program scope, schedule, and cost objectives, establishment of a baseline plan for accomplishment of program objectives, and use of earned value techniques for performance measurement during the execution of a program. The system provides a sound basis for problem identification, corrective actions, and management replanning as may be required. The guidelines in this document are purposely high level and goal oriented as they are intended to state the qualities and operational considerations of an integrated management system using earned value analysis methods without mandating detail system characteristics. Different companies must have the flexibility to establish and apply a management system that suits their management style and business environment. The system must, first and foremost, meet company needs and good business practices.

INTRODUCTION The principles of an EVMS are:  Plan all work scope for the program to completion.  Break down the program work scope into finite pieces that can be assigned to a responsible person or organization for control of technical, schedule and cost objectives.  Integrate program work scope, schedule, and cost objectives into a performance measurement baseline plan against which accomplishments may be measured. Control changes to the baseline.  Use actual costs incurred and recorded in accomplishing the work performed.  Objectively assess accomplishments at the work performance level.  Analyze significant variances from the plan, forecast impacts, and prepare an estimate at completion based on performance to date and work to be performed.  Use EVMS information in the company’s management processes.

INTRODUCTION The intent is to provide management information using existing company resources and a scaled EVMS application that achieves the program requirements and is compliant with the EVMS principles. EVMS scalability is viewed as spectrum employing the principles of EVMS as fundamental to all programs and the EVMS guidelines (Section 2) as applicable to large complex and/or high risk programs allowing any program regardless of size and complexity to realize the benefits of earned value management.

EVMS GUIDELINES This section provides basic guidelines for companies to use in establishing and applying an integrated Earned Value Management System (EVMS). These guidelines are expressed in fundamental terms and provide flexibility for each company to optimize its system and be fully accountable for the effectiveness of its usage. The guidelines are grouped in five major categories as documented below. Organization – 5 Guidelines Planning, Scheduling, and Budgeting – 10 Guidelines Accounting Considerations – 6 Guidelines Analysis and Management Reports – 6 Guidelines Revisions and Data Maintenance – 5 Guidelines

EVMS PROCESS DISCUSSION This section provides additional information relative to the EVMS guidelines in Section 2. This information is provided as an aid in understanding and applying earned value management methods. Statement of Work Work Breakdown Structure Program Organization Program Schedule Budget Allocation and Resource Planning Accounting Considerations Earned Value Methodology Performance Measurement Estimates at Completion Revisions and Data Maintenance

SYSTEM DOCUMENTATION EVMS documentation should be established in the standard form or forms used by the affected company for systems documentation and communication of policies and procedures. This EVMS standard does not require or suggest a company should create a descriptive document that is outside of normal company requirements or restricts a company’s ability to effectively implement desired system changes. At the same time, it is duly noted that it is good business practice to provide adequate policies and procedures where the subject processes are expected to be implemented and applied effectively enterprise wide. Government contracts may include a requirement for the contractor to provide a system description document. If a company does not maintain this type of document, a brief general description with a road map to the internal documents that are used is acceptable.

SYSTEM EVALUATION A company will normally evaluate the utility of internal management systems in accordance with standing policies and good business practice. For some purposes a visible and documented process of system evaluation may be needed when a company must attest to the capabilities and usage of its program management system. Assurance of conformity with EVMS guidelines may be contractually required on selected contracts for certain customers such as U.S. or other military customers, NASA, or other government agencies. This requirement may be applied in conjunction with performance measurement reporting on programs of significant size and nature as determined by contractual agreement with the customer. Evaluation Process - The company is responsible for the evaluation of its system. Prior C/SCSC Acceptance - For government contracts, if a company has an appropriate prior system acceptance, the company may elect to cite that acceptance in lieu of providing a statement of EVMS compliance. System Surveillance - Surveillance of the management system will be accomplished in accordance with company policies to ensure continued compliance with EVMS guidelines.