UH-60M Technology Readiness Level Assessment Methodology.

Slides:



Advertisements
Similar presentations
2010 HPRCT Presentation – Optimized Human Error Evaluation June 23 rd, 2010 Presenter: Terry J. Herrmann, P.E. Associate, Structural Integrity Associates.
Advertisements

Project Management Concepts
Chapter 7: Key Process Areas for Level 2: Repeatable - Arvind Kabir Yateesh.
More CMM Part Two : Details.
©2001 Plan B Systems Inc. PBSi Quantitative Cost/Schedule Risk Analysis.
Project Scope Management
“Common Process for Developing Briefings for Major Decision Points” INSTRUCTIONS Provide Feedback via to: Lois Harper PEO C4I and Space
Chapter 5: Project Scope Management
Engineering Design Development. Turner College and Career High School.
Chapter 5: Project Scope Management J. S. Chou, P.E., PhD.
Program Management Satisfy requirements of all individual projects with minimal resources Human resource is the most expensive Leadership Methods of documenting.
Defining the Activities. Documents  Goal Statement defines why helps manage expectations  Statement of Work what gets delivered defines scope  Software.
Gantt Chart Engineering Design Development. Turner College and Career High School.
What are MRLs ? Alfred W. Clark Dawnbreaker, Inc.
The program work breakdown structure (WBS) establishes the essential
Project Management Software Tools Cheryl A. Wilhelmsen Lee Ostrom.
ERT461 BIOSYSTEMS ENGINEERING DESIGN 1 ERT424 BIOPROCESS PLANT DESIGN 1.
LSU 07/07/2004Communication1 Communication & Documentation Project Management Unit – Lecture 8.
1 RPS Critical Planning Preparation & Delivery of Critical Parts Goodrich Aerostructures Group.
Session 3.11 Risk Identification Presented By: RTI, JAIPUR.
Org Name Org Site CMM Assessment Kick-off Meeting Dates of assessment.
Capability Maturity Model Part One - Overview. History Effort started by SEI and MITRE Corporation  assess capability of DoD contractors First.
BSBPMG503A Manage Project Time Manage Project Time Unit Guide Diploma of Project Management Qualification Code BSB51507 Unit Code BSBPMG503A.
© Grant Thornton | | | | | Guidance on Monitoring Internal Control Systems COSO Monitoring Project Update FEI - CFIT Meeting September 25, 2008.
August 2 and 3, 2010 Project Cost, Schedule, Risk and Contingency Jay Elias.
Chapter 6 : Software Metrics
Software Testing Course Shmuel Ur
Service Transition & Planning Service Validation & Testing
Copyright 2003 Northrop Grumman Corporation 0 To PIID or Not to PIID: Lessons Learned in SCAMPI Evidence Preparation To PIID or Not to PIID: Lessons Learned.
SacProNet An Overview of Project Management Techniques.
BSBPMG505A Manage Project Quality Manage Project Quality Project Quality Processes Diploma of Project Management Qualification Code BSB51507 Unit.
James W. Bilbro JB Consulting International Huntsville, AL Using the Advancement Degree of Difficulty (AD 2 ) as an input to Risk Management Multi-dimensional.
5-1 Copyright © 2013 McGraw-Hill Education (Australia) Pty Ltd Pearson, Larson, Gray, Project Management in Practice, 1e CHAPTER 5 Defining the Scope of.
The Center for Space Research Programs CSRP Technology Readiness Level.
Assessing the influence on processes when evolving the software architecture By Larsson S, Wall A, Wallin P Parul Patel.
Chapter 10 Analysis and Design Discipline. 2 Purpose The purpose is to translate the requirements into a specification that describes how to implement.
1 Advanced Project Management Project Plan Templates Ghazala Amin.
Project Management Processes for a Project
Pre-Project Components
THE PROJECT LIFE CYCLE PROJECT MANAGEMENT LIFE CYCLE LSU 01/18/2005 PROJECT LIFE CYCLE 1.
McGraw-Hill/Irwin © 2003 The McGraw-Hill Companies, Inc., All Rights Reserved. 6-1 Chapter 6 CHAPTER 6 INTERNAL CONTROL IN A FINANCIAL STATEMENT AUDIT.
Better Prepared And Ready to Help Emergency Preparedness Mission Nepal February 2011 From Contingency planning to readiness WFP’s Emergency Preparedness.
XLIX Engineering Design Firm © 2010 ENGR/ETGR Definition of Project 1 A project is “…a combination of human and non-human resources pulled together.
5 - 1 The Cost Modeling Process Chapter Introduction What makes a good cost model? – Good Statistics – Quality Data – Relevant Data – Analogous.
BSBPMG501A Manage Application of Project Integrative Processes Manage Project Integrative Processes Unit Guide Diploma of Project Management Qualification.
ISO Registration Common Areas of Nonconformances.
Module 1: Writing Your Functional Competency Assessment East Carolina University Department of Human Resources Classification and Compensation.
SRR and PDR Charter & Review Team Linda Pacini (GSFC) Review Chair.
Statement of Auditing Standard No. 94 The Effect of Information Technology on the Auditor’s Consideration of Internal Control in a Financial Statement.
1 Project Management C13PM Session 2 Project Initiation & Definition Russell Taylor Business Department Staff Workroom
1 Lecture 2.4a: SEF SE Planning and the SEP (SEF Ch 16) Dr. John MacCarthy UMBC CMSC 615 Fall, 2006.
1 11/2004 – N.Campanis for MPUG Western NY Chapter Working Session Nick Campanis Presented to MPUG – Western NY Chapter Working Session November 10, 2004.
SwCDR (Peer) Review 1 UCB MAVEN Particles and Fields Flight Software Critical Design Review Peter R. Harvey.
GAO’s Cost and Schedule Assessment Guides U.S. Government Accountability Office Applied Research and Methods Cost Engineering Sciences Jason T Lee, Assistant.
Copyright 2015 John Wiley & Sons, Inc. Project Planning Part II.
LECTURE 5 Nangwonvuma M/ Byansi D. Components, interfaces and integration Infrastructure, Middleware and Platforms Techniques – Data warehouses, extending.
Software Engineering Process - II 7.1 Unit 7: Quality Management Software Engineering Process - II.
Coupling and Cohesion Schach, S, R. Object-Oriented and Classical Software Engineering. McGraw-Hill, 2002.
Creating a Work Breakdown Structure with Microsoft Project.
Dr. Thomas D. Fiorino November 2002
Supportability Design Considerations
Technology Readiness Assessment (TRA)
Software and Systems Integration
UH-60M Technology Readiness Level Assessment Methodology.
ISA 201 Intermediate Information Systems Acquisition
Defining the Activities
Project Management Process Groups
Statement of Auditing Standard No. 94
Project management Learning Unit 5.
Presentation transcript:

UH-60M Technology Readiness Level Assessment Methodology

TRL Considerations Is system new or recap/upgrade with legacy documentation? Does Work Breakdown Structure (WBS) exist? If not, how will critical technologies be determined? What does “CRITICAL” technology mean to the system? Is the objective of the system understood by key players including OSD representatives? How do TRL definitions apply to specifics of system development?

UH-60M TRL Process 1 - Define “CRITICAL” technology. - Those vehicle technologies, components, or subsystems whose success or failure most significantly affect the ability of a fully integrated UH-60M to meet Block 1 key performance parameters (KPPs) as identified by the ORD and System Performance Specification, AVNS-PRF-10002. 2 - Using WBS, identify critical technologies for UH-60M. - Based on objectives of UH-60M Recap/Upgrade program, components of the WBS were selected as critical given improvements will be required in currently fielded UH-60 aircraft.

UH-60M TRL Process (cont.) 3 - Define TRL levels in relation to objectives of UH-60M. 7 Assigned to components which are currently undergoing qualification testing for an Army rotorcraft program but have not been fielded on the UH-60 platform except for qualification and testing. 8 Assigned to qualified components of other fielded UH-60 systems (UH-60Q). 9 Assigned to components currently fielded on UH-60L platform. 4 - Perform Assessment.

UH-60M TRL Process (cont.) 5 - Document results thoroughly. - Detailed information is necessary. - Focus on Spreadsheet which contains all relevant data. - Use one item as example and obtain all documentation. Element Level Standard Report Agency Date Results

Manpower Requirements UH-60M TRL Manpower Requirements The UH-60M Recap/Upgrade program consists of massive amounts of legacy documentation, which may be 20 years old and difficult to locate. Given this, the UH-60M TRL required: One Engineer - 8 Weeks Develop, track, coordinate, brief Two Engineers - 2 Weeks Track data for UH-60 Other Programs - 1 Week Contact for info/data File Clerk - 2 Weeks Locate, Copy Data TOTAL: 520 HR Engineering 80 HR Clerk

UH-60M TRL Lessons Learned DOD 5000.2 contains minimal guidance and definition of TRL Assessment requirements. Establish POCs for involvement in process. Need coordination early to establish requirements for TRL Assessment. POCs must understand program objectives to achieve common results. Do not underestimate time or manpower required. TRL Assessment must be performed independently from Risk Assessment (required MS document) to capture essence of TRL Assessment.

ACAT1D program 5000 changed in between – TRL now a requirement A lot of the components are legacy components, TRL didn’t make a lot of sense Integrated master schedule Process of mapping to WBS 1500 lines Assigned govt person for each activity on that line Likelihood versus consequences Software built for high, moderage Cost, schedule, perform 40 risk abatement plans (sekorsky) Pull down menu identifies into abatement plan