How can you support RIDM/CRM/RM through the use of Risk Analysis
|
|
|
- Erick Horn
- 9 years ago
- Views:
Transcription
1 How can you support RIDM/CRM/RM through the use of Risk Analysis Supply Chain Conference 2011 Panel Session NASA s Approach to Integrated Risk Management Tony DiVenti Reliability and Risk Analysis Branch Code 322 [email protected] (301)
2 Agenda What does Risk Analysis mean in the context of RIDM & CRM NASA s newest PRA requirements How does GSFC flow down PRA requirements Two Approaches In-House PRA Development Out-of-House PRA Development GSFC s Standard Mission Assurance Requirements (MAR) Document Discussion 2
3 Relationship between RM and Risk Analysis s Diagram taken from Source 7 3
4 What is PRA? Definition: Probabilistic Risk Assessment (PRA) is one of the key RIDM tools. It is a scenario-based methodology (e.g., Event Trees, Fault Trees, Quantification) aimed at identifying and assessing Safety and Technical Performance risks in complex technological systems. PRA characterizes: 1) What can go wrong? 2) How likely is it? 3) What are the consequences Triplet Concept: Scenario, Likelihood, Impact 4
5 What is PRA? PRA Scenario Concept: Taken from Source 7 5
6 What is PRA? What makes PRA appealing is its ability to integrate several sources of information together that may contribute to Risk. Taken from Source 5 6
7 What is PRA? The integrated risk scenario model allows for a robust and ordered ranking of the risk contributors that may lead to the undesired states of interest Taken from Source 5 7
8 Two-Sets of Requirements governing PRA activity at GSFC Applicable requirements pulled from: NPR A PRA Procedures for NASA Programs and Projects (2010) NPR C NASA General Safety Program Requirements (2012) 8
9 Some of the Significant Changes to NPR made in conjunction with RIDM Removed language addressing Full, Simplified, and Limited Scope PRA. Greater emphasis on PRA Planning/PRA Plan Documentation - Formal PRA Plan shall be developed by PRA Lead and approved by Program/Project Manager to: - Identify specific end-states (undesirable consequences, performance measures, figures of merit) of interest consistent with PRA objectives - Define quantitative performance measures and numerical criteria that are to be evaluated by the PRA consistent with objectives - Develop a PRA schedule compatible with objectives, applications, and life cycle phases approved by the Program/Project manager - Greater tie-in with Program/Project characterization of NPR NASA Space Flight Program and Project Management Requirements - Use of Category 1 (i.e., LCC greater than 1 Billion dollars, Nuclear Payloads, Human Spaceflight) 9
10 New NPR Requirements for GSFC Formal submittal of PRA Decisions Cat I and Cat II, Class A or Class B. Formal submittal of PRA plans, including scope and rationale Requires Program Manager approval (note: PRA decision/scope determination is the primary responsibility of the Project subject to OSMA/Center SMA Concurrence) Formal coordination of Independent PRA Review with OSMA. 10
11 How is GSFC Flowing Down PRA Requirements to Developers/Suppliers GSFC s Mission Assurance Requirements (MAR) PROBABILISTIC RISK ANALYSIS (PRA) AND RELIABILITY Tailoring note: The PRA and reliability engineering section requires tailoring per the classification requirements of NPR , NPR , and project-specific requirements. RELIABILITY PROGRAM PLAN Tailoring note: If PRA is being invoked in section 4.2, change section 4.1to read from...implement a Reliability Program Plan (RPP) to... implement a Reliability Program Plan, including the developer s approach to PRA requirements in section 4.2,.. The developer shall document and implement a Reliability Program Plan (RPP) using both qualitative and quantitative techniques to support decisions regarding mission success and safety throughout system development. The RPP shall include a detailed approach to the analysis of hardware and software for their contributions to system reliability and mission success. The developer shall present the implementation of these plans and related activities at milestone reviews beginning with the System Requirements Review (DID 4-1). PROBABILISTIC RISK ASSESSMENT Tailoring notes: See paragraph 2.2.1a of NPR for criteria regarding the requirement to perform a PRA. If a PRA is not required, delete this section and the related DIDs. If a PRA will be performed, delete the non-applicable paragraph and related DID. The developer shall perform a Probabilistic Risk Assessment in accordance with NPR , Probabilistic Risk Assessment (PRA) Technical Procedures for Safety and Mission Success for NASA Programs and Projects (DID 4-2). The developer shall provide the information for a Probabilistic Risk Assessment per NPR , Probabilistic Risk Assessment (PRA) Technical Procedures for Safety and Mission Success for NASA Programs and Projects (DID 4-2). 11
12 How is GSFC Flowing Down PRA Requirements to Developers/Suppliers MAR Data Items Description (DID 4-1) Title: Reliability Program Plan DID No.: 4-1 MAR Paragraph: 4.1 Use: Planning and implementation of Probabilistic Risk Assessment (PRA) and reliability activities. Reference Documents: - NPD , NASA Reliability and Maintainability (R&M) Program Policy - NASA-STD , Planning, Developing and Managing an Effective Reliability and Maintainability (R&M) Program. - NPR Risk Classification for NASA Payloads - NPR PRA Procedures for NASA Programs and Projects Place/Time/Purpose of Delivery: - Deliver draft plan to the Project Office sixty (60) days after contract award for review. - Deliver final plan to the Project Office thirty (30) days prior to the Systems Requirements Review for approval. - Deliver activity reports related to implementation of the plan at milestone reviews beginning with the Systems Requirements Review for review. Preparation Information: The Reliability Program Plan shall include: - A discussion of how the developer intends to implement and comply with Reliability program requirements. - Charts and statements describing organizational responsibilities and functions conducting each task to be performed as part of the Program. - A summary (matrix or other brief form) that indicates for each requirement, the organization responsible for implementing and generating the necessary documents. - Identify the approval, oversight, or review authority for each task. - Narrative descriptions, time or milestone schedules, and supporting documents describing the execution and management plan for each task. - Documentation, methods, procedures, and reporting specific to each task in the plan. 12
13 How is GSFC Flowing Down PRA Requirements to Developers/Suppliers MAR DID 4-1 use this DID if the developer is performing the PRA Title: Probabilistic Risk Assessment DID No.: 4-2 MAR Paragraph: 4.2 Use: To provide a structured and disciplined approach to: analyzing system risk; supporting management decisions; improving safety, operations, performing maintenance and upgrades; improving performance; reducing costs. Reference Documents: - NPR Risk Classification for NASA Payloads - NPR Technical Probabilistic Risk Assessment (PRA) Procedures for Safety and Mission Success for NASA Programs and Projects - NPR NASA General Safety Program Requirements - PRA Procedures Guide for NASA Managers and Practitioners ( Place/Time/Purpose of Delivery: - Deliver a PRA plan to the Project office sixty (60) days after contract award for review (Note: PRA may be stand-alone document or included as part of the Reliability Program Plan (RPP), Risk Management Plan (RMP), etc. The PRA Plan shall meet requirements delineated in DID 4-1.). - Deliver interim PRA to the Project Office thirty (30) days prior to PDR for review. - Deliver updated interim PRA to the Project Office thirty (30) days prior to CDR for review. - Deliver updated interim PRA to the Project Office thirty (30) days prior to MOR for review. - Deliver final PRA to the Project Office thirty (30) days prior to FOR for approval. Preparation Information: The PRA shall be performed in accordance with NPR and include the following: - The objective and scope of the PRA - End-states-of-interest to the decision-maker, - Definition of the mission phases and success criteria, - Initiating event categories, - Top level scenarios, - Initiating and pivotal event models (e.g., fault trees and phenomenological event models), including assessments of common cause failure modes - Data development for probability calculations, - Integrated model and quantification to obtain risk estimates, - Assessment of uncertainties, - Summary of results and conclusions, including a ranking of the lead contributors to risk. 13
14 How is GSFC Flowing Down PRA Requirements to Developers/Suppliers MAR DID 4-2 use this DID if the GSFC is performing the PRA Title: Information for the Probabilistic Risk Assessment (PRA) DID No.: 4-2 MAR Paragraph: 4-2 Use: To provide a structured and disciplined approach to: analyzing system risk; supporting management decisions; address safety, operations, maintenance, and upgrades; manage performance; manage costs. Reference: - NPR Risk Classification for NASA Payloads - NPR Technical Probabilistic Risk Assessment (PRA) Procedures for Safety and Mission Success for NASA Programs and Projects - NPR NASA General Safety Program Requirements - PRA Procedures Guide for NASA Managers and Practitioners ( Related Documents None Place/Time/Purpose of Delivery: - Deliver preliminary heritage information, including the percent applicable, to the Project Office sixty (60) days after contract award for information. - Deliver updated heritage information, including the percent applicable heritage to the subject mission, to the Project Office thirty (30) days to prior major milestone reviews beginning with the SRR for information. - Deliver product information and process information for elements within the scope of the Mission PRA to the Project Office thirty (90) days prior to the PDR and thirty (30) days prior to subsequent major milestone reviews for information. Preparation Information: The government will provide a notification to the developer of the scope and/or area of inputs needed to support the risk assessment 30 days prior to needing information in preparation of the PRA. Types of information needed may include heritage information (e.g., current flight history, current operating hours, operational and storage environments, TRLs, etc.), product information (e.g., hardware and/or software configurations, parts lists, schematics), interim analysis (e.g, working-level copies of fault tree analysis, failure modes and effects analysis, reliability predictions, etc) and/or process information (e.g., design documents, manufacturing documents, parts program documents,etc) germane to the element(s) being evaluated within the scope of Mission PRA and Instrument development. The developer and their collaborators will provide access to the information necessary to support the scope of the Mission PRA. 14
15 Lessons Learned It is important that a clear scope, set of objectives, and milestones be established upfront with the project team to help ensure that needed questions will be answered in a timely manner. PRA and other models rely heavily on the degree and fidelity to which they match what will happen in reality. Such modeling requires close coordination with the design team, and a sound system understanding from the modeler. Need to establish a framework for developing basic event likelihood distributions upfront. Need to clearly communicate results
16 Discussion Comments Questions 16
Continuous Risk Management at NASA
Continuous Risk Management at NASA Ted Hammer GSFC NASA 301-286-7123 [email protected] Control Identify Track Dr. Linda Rosenberg SATC NASA 301-286-0087 [email protected] Communicate
SOFTWARE ASSURANCE STANDARD
NOT MEASUREMENT SENSITIVE National Aeronautics and NASA-STD-8739.8 w/change 1 Space Administration July 28, 2004 SOFTWARE ASSURANCE STANDARD NASA TECHNICAL STANDARD REPLACES NASA-STD-2201-93 DATED NOVEMBER
Criteria for Flight Project Critical Milestone Reviews
Criteria for Flight Project Critical Milestone Reviews GSFC-STD-1001 Baseline Release February 2005 Approved By: Original signed by Date: 2/19/05 Richard M. Day Director, Independent Technical Authority
Goddard Procedures and Guidelines
Goddard Procedures and Guidelines DIRECTIVE NO. APPROVED BY Signature: Original signed by NAME: A. V. Diaz TITLE: Director Responsible Office: Title: Code 300 / Office of Systems Safety and Mission Assurance,
SOFTWARE SAFETY STANDARD
NOT MEASUREMENT SENSITIVE National Aeronautics and NASA-STD-8719.13B w/change 1 Space Administration July 8, 2004 SOFTWARE SAFETY STANDARD NASA TECHNICAL STANDARD REPLACES NASA-STD-8719.13A DATED SEPTEMBER
<Project Name> Software Quality Assurance (SQA) Plan. <Document Control Number>
Software Quality Assurance (SQA) Plan Date: CHECK THE AT< WEBSITE Address> TO VERIFY THAT THIS IS THE CORRECT VERSION PRIOR TO USE. General Tailoring Guidelines This
NASA/SP-2011-3422 Version 1.0 November 2011. NASA Risk Management Handbook
NASA/SP-2011-3422 Version 1.0 November 2011 NASA Risk Management Handbook NASA/SP-2011-3422 Version 1.0 NASA Risk Management Handbook National Aeronautics and Space Administration NASA Headquarters Washington,
NODIS Library Program Formulation(7000s) Search
NODIS Library Program Formulation(7000s) Search NASA Procedural Requirements This Document Is Uncontrolled When Printed. Check the NASA Online Directives Information System (NODIS) Library to verify that
Risk Management Tools
Risk Management Tools Langley Research Center May 2, 2000 Michael A. Greenfield Deputy Associate Administrator Office of Safety and Mission Assurance 1 Recent Reviews Focusing on NASA Failures Mars Climate
NASA TECHNICAL STANDARD SOFTWARE SAFETY STANDARD
NASA TECHNICAL STANDARD NASA-STD-8719.13C National Aeronautics and Space Administration Approved: 05-07-2013 Washington, DC 20546-0001 Superseding NASA-STD-8719.13B SOFTWARE SAFETY STANDARD MEASUREMENT
NASA Procedural Requirements NM 7120-81, NRW 7120-27 NPR 7120.5D NID for NPR 7120.5D Effective Date: Expiration Date:
NASA Procedural Requirements NM 7120-81, NRW 7120-27 NPR 7120.5D NID for NPR 7120.5D Effective Date: Expiration Date: COMPLIANCE IS MANDATORY Standing Review Board Handbook Responsible Office: Office of
Project Zeus. Risk Management Plan
Project Zeus Risk Management Plan 1 Baselined: 5/7/1998 Last Modified: N/A Owner: David Jones/Zeus Project Manager Page Section 1. Introduction 3 1.1 Assumptions, Constraints, and Policies 3 1.2 Related
Geostationary Operational Environmental Satellite (GOES)
Effective Date: date of last signature Expiration Date: Five years for date of last signature Version: 2.0 Geostationary Operational Environmental Satellite (GOES) GOES-R Series Risk Management Plan August
Controlling Risks Risk Assessment
Controlling Risks Risk Assessment Hazard/Risk Assessment Having identified the hazards, one must assess the risks by considering the severity and likelihood of bad outcomes. If the risks are not sufficiently
AP1000 European 18. Human Factors Engineering Design Control Document
18.2 Human Factors Engineering Program Management The purpose of this section is to describe the goals of the AP1000 human factors engineering program, the technical program to accomplish these goals,
NASA Risk-Informed Decision Making Handbook
NASA/SP-2010-576 Version 1.0 April 2010 NASA Risk-Informed Decision Making Handbook Office of Safety and Mission Assurance NASA Headquarters THIS HANDBOOK HAS NOT BEEN REVIEWED FOR EXPORT CONTROL RESTRICTIONS;
Department of Defense MANUAL
Department of Defense MANUAL NUMBER 5000.69 July 30, 2014 USD(AT&L) SUBJECT: Joint Services Weapon Safety Review (JSWSR) Process References: See Enclosure 1 1. PURPOSE. In accordance with the authority
Commercial Crew Transportation System Certification Requirements for NASA Low Earth Orbit Missions
National Aeronautics and Space Administration CCTS Certification Requirements Commercial Crew Transportation System Certification Requirements for NASA Low Earth Orbit Missions ESMD-CCTSCR-12.10 Revision-Basic
Appendix V Risk Management Plan Template
Appendix V Risk Management Plan Template Version 2 March 7, 2005 This page is intentionally left blank. Version 2 March 7, 2005 Title Page Document Control Panel Table of Contents List of Acronyms Definitions
SOFTWARE CONFIGURATION MANAGEMENT GUIDEBOOK
Office of Safety and Mission Assurance NASA-GB-9503 SOFTWARE CONFIGURATION MANAGEMENT GUIDEBOOK AUGUST 1995 National Aeronautics and Space Administration Washington, D.C. 20546 PREFACE The growth in cost
Appendix E Program Management Plan Template
Appendix E Program Management Plan Template Version 2 March 7, 2005 This page is intentionally left blank. Version 2 March 7, 2005 Title Page Document Control Panel Table of Contents List of Acronyms Definitions
Reliability Analysis A Tool Set for. Aron Brall
Reliability Analysis A Tool Set for Improving Business Processes Aron Brall ManTech International 1 Introduction Outline Defining Business Process Reliability Quantifying Business Process Reliability Business
Measuring the Maturity of Robotic Planetary Mission Concepts II
SpaceOps 2010 ConferenceDelivering on the DreamHosted by NASA Mars 25-30 April 2010, Huntsville, Alabama AIAA 2010-2034 Measuring the Maturity of Robotic Planetary Mission Concepts
3.0 Risk Assessment and Analysis Techniques and Tools
3.0 Risk Assessment and Analysis Techniques and Tools Risks are determined in terms of the likelihood that an uncontrolled event will occur and the consequences of that event occurring. Risk = Likelihood
Space project management
ECSS-M-ST-80C Space project management Risk management ECSS Secretariat ESA-ESTEC Requirements & Standards Division Noordwijk, The Netherlands Foreword This Standard is one of the series of ECSS Standards
(S&MA) Paradigm. Roy W. Malone, Jr., Director Safety & Mission Assurance, MSFC. Fayssal M. Safie, Ph. D. NASA Safety Center Tech.
Changing g the Safety and Mission Assurance (S&MA) Paradigm Roy W. Malone, Jr., Director Safety & Mission Assurance, MSFC Fayssal M. Safie, Ph. D. NASA Safety Center Tech. Fellow PM Challenge 2010 7th
FERC Engineering Guidelines Risk-Informed Decision Making
FERC Engineering Guidelines Risk-Informed Decision Making Chapter R1 Introduction to Risk-Informed Decision Making Chapter R1, Risk-Informed Decision Making Table of Contents Chapter R1 Introduction to
An Introduction to the ECSS Software Standards
An Introduction to the ECSS Software Standards Abstract This introduces the background, context, and rationale for the creation of the ECSS standards system presented in this course. Addresses the concept
Mission Operation Ground. Assurance @ ESA. Mario Merri GSAW, Los Angeles, USA 2 Mar 2011 ESA UNCLASSIFIED
Mission Operation Ground Software Systems Product Assurance @ ESA Mario Merri GSAW, Los Angeles, USA 2 Mar 2011 The European Cooperation for Space Standardisation (ECSS) Established: in 1993 Goal: coherent,
Managing Commercial-Off-the- Shelf (COTS) Integration for High Integrity Systems: How Far Have We Come? Problems and Solutions in 2003
GSAW 2003 Managing Integration Breakout Session Summary Managing Commercial-Off-the- Shelf () Integration for High Integrity Systems: How Far Have We Come? Problems and Solutions in 2003 Karen Owens, Suellen
Mission Assurance Manager (MAM) Life Cycle Risk Management Best Practices David Pinkley Ball Aerospace MA Chief Engineer September 23, 2014
Mission Assurance Manager (MAM) Life Cycle Risk Management Best Practices David Pinkley Ball Aerospace MA Chief Engineer September 23, 2014 Challenges in Risk Management Program Risk Lexicon Independent
Maximizing the Utility of Your Tool Set for Project Support
2013 NASA Cost Analysis Symposium Maximizing the Utility of Your Tool Set for Project Support Bob Sefcik, Glenn Research Center Tom Parkey, Glenn Research Center August 28, 2013 www.nasa.gov Glenn Research
Table of Contents PERFORMANCE REVIEWS STRATEGIC REVIEWS
SECTION 270 PERFORMANCE AND STRATEGIC REVIEWS Table of Contents 270.1 To which agencies does this section apply? 270.2 What is the purpose of this section? PERFORMANCE REVIEWS 270.3 What is the purpose
Technical Baseline Management
Technical Baseline Management September 30, 2003 Pat Hascall LAT System Engineering 1 Technical Baseline Management We are required to manage the configuration of our technical baseline What is configuration
STATEMENT OF WORK FOR SUPPORT SERVICES FOR THE OFFICE OF HUMAN CAPITAL MANAGEMENT AT THE GODDARD SPACE FLIGHT CENTER DECEMBER 2012
Contract # NNG13VB30B Attachment #1: Office of Human Capital Management Statement of Work for Support 1 STATEMENT OF WORK FOR SUPPORT SERVICES FOR THE OFFICE OF HUMAN CAPITAL MANAGEMENT AT THE GODDARD
SOFTWARE DEVELOPMENT PLAN
SOFTWARE DEVELOPMENT PLAN This document outline is based on the IEEE Standard 1058.1-1987 for Software Project Management Plans. This is the controlling document for managing a software project, and it
NASA Risk Management for IT Security
NASA Risk Management for IT Security NASA Risk Management Conference V October 26-29, 2004 Tom Siu, RS Information Systems GRC Network Security Team [email protected] Objectives The Progression of NASA
REVIEW OF NASA S LESSONS LEARNED INFORMATION SYSTEM
MARCH 6, 2012 AUDIT REPORT OFFICE OF AUDITS REVIEW OF NASA S LESSONS LEARNED INFORMATION SYSTEM OFFICE OF INSPECTOR GENERAL National Aeronautics and Space Administration REPORT NO. IG-12-012 (ASSIGNMENT
The Software Development Life Cycle: An Overview. Last Time. Session 8: Security and Evaluation. Information Systems Security Engineering
The Software Development Life Cycle: An Overview Presented by Maxwell Drew and Dan Kaiser Southwest State University Computer Science Program Last Time Brief review of the testing process Dynamic Testing
Draft Copy. Change Management. Release Date: March 18, 2012. Prepared by: Thomas Bronack
Draft Copy Change Management Release Date: March 18, 2012 Prepared by: Thomas Bronack Section Table of Contents 10. CHANGE MANAGEMENT... 5 10.1. INTRODUCTION TO CHANGE MANAGEMENT... 5 10.1.1. PURPOSE OF
Information Technology Project Oversight Framework
i This Page Intentionally Left Blank i Table of Contents SECTION 1: INTRODUCTION AND OVERVIEW...1 SECTION 2: PROJECT CLASSIFICATION FOR OVERSIGHT...7 SECTION 3: DEPARTMENT PROJECT MANAGEMENT REQUIREMENTS...11
PIVOTAL FOR GRANT MANAGEMENT
PIVOTAL FOR GRANT MANAGEMENT DATA SHEET Granting requires you to have robust processes to manage and assess eligibility of applicants and their applications, and balancing this off against demands for
NASA System Safety Handbook
NASA/SP-2010-580 Version 1.0 November 2011 NASA System Safety Handbook Volume 1, System Safety Framework and Concepts for Implementation NASA/SP-2010-580 Version 1.0 NASA System Safety Handbook Volume
Palisade Risk Conference, 2014
Advanced Risk Management to Improve Cost and Schedule Performance on EPC Projects Risk-Management Best Practices from Nuclear Experience Palisade Risk Conference, 2014 Sola Talabi PhD MBA MSc BSc RMP Project
PROJECT CHARTER GUIDE
Treasury Board of Canada Secretariat Secrétariat du Conseil du Trésor du Canada Enhanced Management Framework for Information Technology PROJECT CHARTER GUIDE February 1999 Chief Information Officer Branch
SUCCESSFUL INTERFACE RISK MANAGEMENT FROM BLAME CULTURE TO JOINT ACTION
SUCCESSFUL INTERFACE RISK MANAGEMENT FROM BLAME CULTURE TO JOINT ACTION SUMMARY Axel Kappeler, Principal James Catmur, Director Interfaces are important because they are everywhere. However, interfaces
SPACE LAUNCH SYSTEM PROGRAM (SLSP) INTEGRATED LOGISTICS SUPPORT PLAN (ILSP)
SLS-PLAN-025 VERSION 1 National Aeronautics and Space Administration RELEASE DATE: APRIL 15, 2013 SPACE LAUNCH SYSTEM PROGRAM (SLSP) INTEGRATED LOGISTICS SUPPORT PLAN (ILSP) Release Date: April 15, 2013
Science Mission Directorate Policy. Policy and Requirements for the Education and Public Outreach Programs of SMD Missions. SMD Policy Document SPD-18
Science Mission Directorate Policy Policy and Requirements for the Education and Public Outreach Programs of SMD Missions SMD Policy Document SPD-18 Recommended by SMD Science Management Council, January
PROJECT MANAGEMENT PLAN <PROJECT NAME>
PROJECT MANAGEMENT PLAN TEMPLATE This Project Management Plan Template is free for you to copy and use on your project and within your organization. We hope that you find this template useful and welcome
Program Lifecycle Methodology Version 1.7
Version 1.7 March 30, 2011 REVISION HISTORY VERSION NO. DATE DESCRIPTION AUTHOR 1.0 Initial Draft Hkelley 1.2 10/22/08 Updated with feedback Hkelley 1.3 1/7/2009 Copy edited Kevans 1.4 4/22/2010 Updated
Biometrics Enterprise Architecture Project Management Plan (BMEA PMP)
Biometrics Enterprise Architecture Project Management Plan (BMEA PMP) Version 1.0 Prepared by: Date: November 24, 2008 Revision History Purpose Revision Date Level 11/17/2009 First Draft 1.0 Responsible
8. Master Test Plan (MTP)
8. Master Test Plan (MTP) The purpose of the Master Test Plan (MTP) is to provide an overall test planning and test management document for multiple levels of test (either within one project or across
Department of Administration Portfolio Management System 1.3 June 30, 2010
E 06/ 30/ 2010 EX AM PL 1. 3 06/ 28/ 2010 06/ 24/ 2010 06/ 23/ 2010 06/ 15/ 2010 06/ 18/ 2010 Portfolio System 1.3 June 30, 2010 Contents Section 1. Project Overview... 1 1.1 Project Description... 1 1.2
Appendix B: Work Breakdown Structure (WBS)
: Work Breakdown Structure (WBS) B.1. Introduction The WBS and WBS dictionary are effective management processes for planning, organizing, and administering NASA programs and projects. In accordance with
Negative Risk. Risk Can Be Positive. The Importance of Project Risk Management
The Importance of Project Risk Management Project risk management is the art and science of identifying, analyzing, and responding to risk throughout the life of a project and in the best interests t of
Program/Project Management Series Work Breakdown Structure Reference Guide
Program/Project Management Series Work Breakdown Structure Reference Guide National Aeronautics and Space Administration May 1994 2 Work Breakdown Structure Reference Guide May 1994 Table of Contents Chapter
Assessment of NCTD Program Management Framework for Positive Train Control Program
Assessment of NCTD Program Management Framework for Positive Train Control Program Subtask 2: Analysis Gap Analysis Prepared for: Brad Hansen, M.S., PMP Director, PMO Capital Projects May 2013 0 icfi.com/transportation
TD Bank N.A. s Enterprise-Wide PMO Monitors Projects and Maintains Focus on Strategic Goals
WHITE PAPER TD Bank N.A. s Enterprise-Wide PMO Monitors Projects and Maintains Focus on Strategic Goals AT A GLANCE TDBNA first began using a project management office (PMO) to support its privatization
Commercial Crew Program Status
National Aeronautics and Space Administration Commercial Crew Program Status for the NAC Presenter Title Date Philip McAlister of Presentation Acting Director, Commercial Spaceflight Development NASA HQ
Quality Risk Management Tools Quality Risk Management Tool Selection When to Select FMEA: QRM Tool Selection Matrix
Quality Risk Management Tools Quality Risk Management Tool Selection When to Select FMEA: QRM Tool Selection Matrix 26 Quality Risk Management Tools The ICH Q9 guideline, Quality Risk Management, provides
Integrated Risk Management:
Integrated Risk Management: A Framework for Fraser Health For further information contact: Integrated Risk Management Fraser Health Corporate Office 300, 10334 152A Street Surrey, BC V3R 8T4 Phone: (604)
A COMPARISON OF FIVE APPROACHES TO SOFTWARE DEVELOPMENT. David J. Schultz. January 21, 2000
A COMPARISON OF FIVE APPROACHES TO SOFTWARE DEVELOPMENT David J. Schultz January 21, 2000 1. Introduction This white paper addresses five approaches, or methodologies, for software engineering (SWE): The
System- Level Reliability Analysis for Conceptual Design of Electrical Power Systems
System- Level Reliability Analysis for Conceptual Design of Electrical Power Systems Ying Zhang and Tolga Kurtoglu Palo Alto Research Center Palo Alto, CA, 94304 {yzhang, kurtoglu}@parc.com Irem Y. Tumer
System Engineering Data Repository
System Data Repository 09:00 data in the MBSE life-cycle 09:20 EGS-CC in the system context 09:40 Conceptual Modelling and ECSS 10:00 ecascade 10:20 A snapshot of systems engineering data management in
For Articulation Purpose Only.
E328 Project Management (4 Modular Credits) This document addresses the content related abilities, with reference to the module. Abilities of thinking, learning, problem solving, team work, communication,
Gilead Clinical Operations Risk Management Program
Gilead Clinical Operations Risk Management Program Brian J Nugent, Associate Director 1 Agenda Risk Management Risk Management Background, Benefits, Framework Risk Management Training and Culture Change
NPR 7120.5, NASA Space Flight Program and Project Management Handbook. February 2010
NPR 7120.5, NASA Space Flight Program and Project Management Handbook February 2010 Preface NASA accomplishes its strategic goals through human and robotic missions, which are conducted through programs
CHARACTERISTICS OF SUCCESSFUL MEGAPROJECTS
Chapter Six CHARACTERISTICS OF SUCCESSFUL MEGAPROJECTS Bibliographic Information: Committee to Assess the Policies and Practices of the Department of Energy to Design, Manage, and Procure Environmental
U.S. DEPARTMENT OF ENERGY PROJECT REVIEW GUIDE FOR CAPITAL ASSET PROJECTS
NOT MEASUREMENT SENSITIVE U.S. DEPARTMENT OF ENERGY PROJECT REVIEW GUIDE FOR CAPITAL ASSET PROJECTS DOE G 413.3-9 [This Guide describes suggested non-mandatory approaches for meeting requirements. Guides
PROJECT MANAGEMENT ROADMAP, 2013-2014. Executive Summary
Review by the Office of Program Evaluation and Government Accountability (OPEGA) Response from the Office of Information Technology (OIT) March 1, 2013 PROJECT MANAGEMENT ROADMAP, 2013-2014 Executive Summary
AABInternational POLICIES AND PROCEDURES MANUAL. Form 225. Rev. 9-8-15 AVIATION ACCREDITATION BOARD INTERNATIONAL
AABInternational POLICIES AND PROCEDURES MANUAL Form 225 Rev. 9-8-15 AVIATION ACCREDITATION BOARD INTERNATIONAL 3410 SKYWAY DRIVE AUBURN, ALABAMA36830 TABLE OF CONTENTS 1.0 The Aviation Accreditation Board
VCE PRODUCT LIFE CYCLE END OF LIFE POLICY OVERVIEW
VCE PRODUCT LIFE CYCLE END OF LIFE POLICY OVERVIEW Document Version 3.0 December 2015 Revision history Revision History Date Document version Description of changes July 2013 1.0 Initial publication September
REGULATORY GUIDE OFFICE OF NUCLEAR REGULATORY RESEARCH. REGULATORY GUIDE 1.174 (Draft was issued as DG-1226, dated August 2009)
U.S. NUCLEAR REGULATORY COMMISSION May 2011 Revision 2 REGULATORY GUIDE OFFICE OF NUCLEAR REGULATORY RESEARCH REGULATORY GUIDE 1.174 (Draft was issued as DG-1226, dated August 2009) AN APPROACH FOR USING
Launch Services Program (LSP) Advisory Services Plan
National Aeronautics and Space Administration John F. Kennedy Space Center, Florida Launch Services Program LSP-PLN-326.01 Launch Services Program (LSP) Advisory Services Plan EXECUTIVE SUMMARY: This Advisory
U.S. Nuclear Regulatory Commission
U.S. Nuclear Regulatory Commission 2011 Data Center Consolidation Plan and Progress Report Version 2.0 September 30, 2011 Enclosure Contents 1 Introduction... 2 2 Agency Goals for Data Center Consolidation...
How to successfully manage your mega-project
How to successfully manage your mega-project Part I Early planning and organizing for success kpmg.com 2 Building, Construction & Real Estate How to successfully manage your mega-project A three-part series
Best Practices Statement Project Management. Best Practices for Managing State Information Technology Projects
State of Arkansas Office of Information Technology 124 W. Capitol Ave. Suite 990 Little Rock, AR 72201 501.682.4300 Voice 501.682.4020 Fax http://www.cio.arkansas.gov/techarch Best Practices Statement
The Need for a Systems Engineering Approach For Measuring and Predicting the Degradation of Aging Systems And How It Can Be Achieved
The Need for a Systems Engineering Approach For Measuring and Predicting the Degradation of Aging Systems And How It Can Be Achieved William Robinson Gisele Welch Gary O Neill Georgia Tech Research Institute
PHASE 3: PLANNING PHASE
PHASE 3: PLANNING PHASE The ning Phase focuses principally on required project planning work. Proper comprehensive project planning is essential to a successful IT project, and incomplete project planning
Introducing ECSS Software-Engineering Standards within ESA
r bulletin 111 august 2002 Introducing ECSS Software-Engineering Standards within ESA Practical approaches for space- and ground-segment software M. Jones & E. Gomez Ground Segment Engineering Department
Project Management Plan Template
Abstract: This is the project management plan document for . This is a controlled document and should be maintained in a configuration environment. Project Management Plan Template Contents REVISION
Change Management Best Practices
General Change Management Best Practices Practice Area Best Practice Criteria Organization Change management policy, procedures, and standards are integrated with and communicated to IT and business management
Future Multi-Mission Satellite Operations Centers Based on an Open System Architecture and Compatible Framework
Future Multi-Mission Satellite Operations Centers Based on an Open System Architecture and Compatible Framework GSAW 2014 Thomas J. Sullivan, Aerospace Ground Systems Lab Rico Espindola, MMSOC Flight Operations
TREASURY INSPECTOR GENERAL FOR TAX ADMINISTRATION
TREASURY INSPECTOR GENERAL FOR TAX ADMINISTRATION The Customer Account Data Engine 2 Systems Development Guidelines; However, Process Improvements Are Needed to Address Inconsistencies September 30, Year
DESIGN AND INTEGRATION OF EQUIPMENT. (B) Process Flow Guideline
LLE INSTRUCTION 7700H LLEINST 7700H SUBJECT: APPENDIX: DESIGN AND INTEGRATION OF EQUIPMENT (A) List of Acronyms (B) Process Flow Guideline ENCLOSURES: 1. Equipment Qualification Checklist (EQC) 2. Project
A Characterization Taxonomy for Integrated Management of Modeling and Simulation Tools
A Characterization Taxonomy for Integrated Management of Modeling and Simulation Tools Bobby Hartway AEgis Technologies Group 631 Discovery Drive Huntsville, AL 35806 256-922-0802 [email protected]