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
UH-60M Technology Readiness Level Assessment Methodology.
“Common Process for Developing Briefings for Major Decision Points” INSTRUCTIONS Provide Feedback via to: Lois Harper PEO C4I and Space
Program Management Satisfy requirements of all individual projects with minimal resources Human resource is the most expensive Leadership Methods of documenting.
Capability Maturity Model Part One - Overview. History Effort started by SEI and MITRE Corporation  assess capability of DoD contractors First.
Preceptor Orientation
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.
James W. Bilbro JB Consulting International Huntsville, AL Using the Advancement Degree of Difficulty (AD 2 ) as an input to Risk Management Multi-dimensional.
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.
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.
BSBPMG501A Manage Application of Project Integrative Processes Manage Project Integrative Processes Unit Guide Diploma of Project Management Qualification.
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.
GAO’s Cost and Schedule Assessment Guides U.S. Government Accountability Office Applied Research and Methods Cost Engineering Sciences Jason T Lee, Assistant.
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.
ON “SOFTWARE ENGINEERING” SUBJECT TOPIC “RISK ANALYSIS AND MANAGEMENT” MASTER OF COMPUTER APPLICATION (5th Semester) Presented by: ANOOP GANGWAR SRMSCET,
Coupling and Cohesion Schach, S, R. Object-Oriented and Classical Software Engineering. McGraw-Hill, 2002.
Cost and Schedule Paul Weinman Pacific Northwest National Laboratory.
CHAPTER10 Project Human Resource Management
Dr. Thomas D. Fiorino November 2002
James W. Bilbro JB Consulting International Huntsville, AL
Chapter 11 Project Management.
Camera PDR/CD1 Planning 19 September 2008
Project Management Business Management.
Supportability Design Considerations
Restoration and Regulation Discussion
Configuration Management
Technology Readiness Assessment (TRA)
Project Management BBA & MBA
Overview of Project Planning
Restoration and Regulation Discussion
CS4311 Spring 2011 Process Improvement Dr
Credit Arrangements – Independent Assessments
Software and Systems Integration
Configuration Management
Project Management and Information Security
ISA 201 Intermediate Information Systems Acquisition
ISA 201 Intermediate Information Systems Acquisition
Session 5b Dr. Dan C. Surber, ESEP
IBR Documentation Review
SBS FMEA Database FMEA Background SBS Database Features and Benefits
ITPD ISSUE MANAGEMENT PROCESS SEPTEMBER 5, 2008
Defining the Activities
Our new quality framework and methodology:
Risk Management Process (Revised)
Project Management Process Groups
Assessment Workshop Title of the Project (date)
Software Engineering Furqan Rustam.
Statement of Auditing Standard No. 94
Software Engineering Lecture 16.
Project management Learning Unit 5.
Capability Maturity Model
Software Engineering Lecture #3
DOD’S PHASED SYSTEM DEVELOPMENT PROCESS
Capability Maturity Model
Restoration and Regulation Discussion
ISSUE MANAGEMENT PROCESS MONTH DAY, YEAR
DOE Review of the LCLS Project 7-9 February 2006
KEC Dhapakhel Lalitpur
Conducting a Business Impact Analysis (BIA)
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