Presentation is loading. Please wait.

Presentation is loading. Please wait.

Presented to: Right Sizing Team By: Ken Hamm, AJP-6830 Aviation Weather Office Date: July 14, 2010 v0.1 Federal Aviation Administration Aviation Weather.

Similar presentations


Presentation on theme: "Presented to: Right Sizing Team By: Ken Hamm, AJP-6830 Aviation Weather Office Date: July 14, 2010 v0.1 Federal Aviation Administration Aviation Weather."— Presentation transcript:

1 Presented to: Right Sizing Team By: Ken Hamm, AJP-6830 Aviation Weather Office Date: July 14, 2010 v0.1 Federal Aviation Administration Aviation Weather Right Sizing 7/14/10 Bi-weekly

2 2 Federal Aviation Administration Right Sizing Bi-Weekly – v0.1 July 14, 2010 Agenda Introduction to FAA AMS Requirements for SA phase  CRDR Requirements for CRD phase  IARD Application of ASWON and WSDS Deliverables: –ESRL –Indiana U. –MIT/Lincoln Lab –NCAR –NSSL –U. of Oklahoma

3 3 Federal Aviation Administration Right Sizing Bi-Weekly – v0.1 July 14, 2010 Templates Used Type of ProductAppendix Preliminary ACAT Determination Request A CRD PlanB Shortfall Analysis ReportC Service Analysis Approval MatrixH CRD Approval MatrixI Concept of OperationsK Concept of UseL

4 4 Federal Aviation Administration Right Sizing Bi-Weekly – v0.1 July 14, 2010 Acronyms Used AcronymFull Name ACATAcquisition Category AMSAcquisition Management System CONOPSConcept of Operations CONUSEConcept of Use CRDConcept and Requirements Definition CRDRConcept and Requirements Definition Readiness Decision EAEnterprise Architecture IARDInvestment Analysis Readiness Decision pPRpreliminary Program Requirements

5 5 Federal Aviation Administration Right Sizing Bi-Weekly – v0.1 July 14, 2010 Acquisition Management System Fig. 3: p. 4 of 79

6 6 Federal Aviation Administration Right Sizing Bi-Weekly – v0.1 July 14, 2010 Motivation All FAA investment initiatives must go through a Service Analysis (SA) and CRD process. During SA and CRD, the service organization must build a legitimate and compelling case that shows how a proposed initiative fulfills an FAA service need In both SA and CRD, a set of products will be developed by the service organization that act as both milestones for progressing through the AMS lifecycle and as building blocks for creating a sound acquisition case. from p. 2 of 79

7 7 Federal Aviation Administration Right Sizing Bi-Weekly – v0.1 July 14, 2010 Service Analysis Phase Fig. 4: p. 5 of 79

8 8 Federal Aviation Administration Right Sizing Bi-Weekly – v0.1 July 14, 2010 Requirements: Service Analysis Inclusion in EA Roadmap –The roadmap effort is currently in progress. Concept of Operations (CONOPS) –CONOPS is both a stand-alone document and a sub-section within the Shortfall Analysis Report. Shortfall Analysis Report (App. C) –This report re-states the problem being addressed by the initiative, identifies the severity of the problem, and explains the methods used to generate the shortfall estimate. Preliminary ACAT Determination Request (App. A) –Acquisition Category (ACAT) classifies project based on dollar thresholds and appropriate qualitative factors. –The assigned ACAT Level determines the future governance of the program. Approved CRD Plan (App. B) –The CRD plan outlines the approach the service organization will employ to complete the CRD phase of AMS.

9 9 Federal Aviation Administration Right Sizing Bi-Weekly – v0.1 July 14, 2010 Service Analysis: Concept of Operations The CONOPS document includes the following sections (App. K): –Executive Summary –Description of Operational Need –Service or System Justification (Description of Desired Change) –Proposed Service or System –Operational Scenarios –Impacts –References –Appendices

10 10 Federal Aviation Administration Right Sizing Bi-Weekly – v0.1 July 14, 2010 Service Analysis: Shortfall Analysis Report This report re-states the problem being addressed by the initiative, identifies the severity of the problem, and explains the methods used to generate the shortfall estimate. It contains, but is not limited to, the following products. Required ProductDescription Needed Service or CapabilityIdentifies the new or updated capability required to meet FAA strategic objectives Legacy Case DefinitionIdentifies existing operational and technical environment and planned near-term capability Preliminary ShortfallDetailed description of shortfall Concept of OperationsDescribes what initiative will do from a physical or operational perspective

11 11 Federal Aviation Administration Right Sizing Bi-Weekly – v0.1 July 14, 2010 Service Analysis: Preliminary ACAT Determination Request

12 12 Federal Aviation Administration Right Sizing Bi-Weekly – v0.1 July 14, 2010 Service Analysis: Preliminary ACAT Determination Request (cont’d)

13 13 Federal Aviation Administration Right Sizing Bi-Weekly – v0.1 July 14, 2010 Service Analysis: CRD Plan The CRD Plan is the document that outlines the approach the service organization will employ to complete the CRD phase. Its purposes are: –Ensure agreement among all organizations providing CRD resources –Define products to be completed during the CRD phase –Establish a milestone schedule for the CRD effort

14 14 Federal Aviation Administration Right Sizing Bi-Weekly – v0.1 July 14, 2010 Service Analysis: CRD Plan Deliverable Activity Responsible Agent Reviewing Agents Review Period Target Date Develop Concept(s) of Use Develop Functional Analysis Quantify Shortfall Develop EA Products and Amendments

15 15 Federal Aviation Administration Right Sizing Bi-Weekly – v0.1 July 14, 2010 CRD Plan: Other Deliverable Activities Conduct Safety Risk Management Develop Preliminary Requirements (pPR) Develop Range of Alternatives Estimate Costs and Benefits Create Investment Analysis Plan (IAP) Finalize ACAT Designation Request Prepare for Investment Analysis Readiness Decision (IARD)

16 16 Federal Aviation Administration Right Sizing Bi-Weekly – v0.1 July 14, 2010 Service Analysis and CRD Products

17 17 Federal Aviation Administration Right Sizing Bi-Weekly – v0.1 July 14, 2010 CRD Process

18 18 Federal Aviation Administration Right Sizing Bi-Weekly – v0.1 July 14, 2010 CRD Phase: Concept of Use (CONUSE) The CONUSE document is an expansion of the CONOPS: –Focus is on the user (i.e. user’s language, needs, expectations, etc.) –It describes specifically how users will employ the proposed capabilities and how they will function in the operating environment (secondary focus) –The CONUSE will be used as a foundation for performing the functional analysis and, in turn, developing the preliminary Program Requirements.

19 19 Federal Aviation Administration Right Sizing Bi-Weekly – v0.1 July 14, 2010 CRD Phase: Concept of Use The CONUSE document includes the following sections (App. L): –Background Information (including References) –Description of Operational Need –Service or System Justification –Proposed Service or System –Operational Scenarios –Description of Impacts –Appendices

20 20 Federal Aviation Administration Right Sizing Bi-Weekly – v0.1 July 14, 2010 CRD Phase: Functional Analysis The Functional Analysis product takes stakeholder needs and translates them into the functions required to satisfy the need. Higher-level functions are decomposed into sequentially lower-level sub-functions. –A function is defined as a characteristic action or activity that needs to be performed to achieve the desired service. –Stakeholder needs are derived from the Needed Services product, the Preliminary Shortfall product, the CONOPS, and the NAS System Requirements document (SR-1000). During Functional Analysis, focus is on what the new service will do, not how the service will be performed.

21 21 Federal Aviation Administration Right Sizing Bi-Weekly – v0.1 July 14, 2010 CRD Phase: Functional Analysis Through the process of decomposing and analyzing functions, a description of the system emerges and becomes the framework for developing requirements and physical architectures. Analysis of the operating environment is also required. –Changes to an environment or multiple operating environments may require defining additional functions. Required analysis tools: –N 2 Diagram –Functional Flow Block Diagram

22 22 Federal Aviation Administration Right Sizing Bi-Weekly – v0.1 July 14, 2010 Functional Analysis: Generic N 2 Diagram N is the number of entities Functional or physical entities are placed on the diagonal axis The remaining squares of N x N matrix represent the interface inputs and outputs Fig : System Engineering Manual

23 23 Federal Aviation Administration Right Sizing Bi-Weekly – v0.1 July 14, 2010 Functional Analysis: Example N 2 Diagram Blank square indicates no interface between respective functions An ‘X’ placed in square corresponding to Row I, Column J indicates data flow from function I to function J. Fig : System Engineering Manual

24 24 Federal Aviation Administration Right Sizing Bi-Weekly – v0.1 July 14, 2010 Functional Analysis: More Diagrams Fig : System Engineering Manual Fig : System Engineering Manual Diagram Showing Functional Decomposition Functional Flow Block Diagram

25 25 Federal Aviation Administration Right Sizing Bi-Weekly – v0.1 July 14, 2010 Backup Slides

26 26 Federal Aviation Administration Right Sizing Bi-Weekly – v0.1 July 14, 2010 Motivation (cont’d) Service Analysis Phase Identify and define future service needs Document service needs on approved EA roadmap Clearly describe the nature, urgency, and impact of the problem Ends with a CRDR, marking transition to CRD Phase CRD Phase Define and validate any shortfalls or service gaps Identify requirements on a functional level Ensure that the investment initiative aligns with FAA strategic goals and objectives Identify different viable alternatives Ends with an IARD, marking transition to Investment Analysis Phase

27 27 Federal Aviation Administration Right Sizing Bi-Weekly – v0.1 July 14, 2010 Supporting Activities Non FAA Sensors CY PIREPS NEXRAD Product Improvement & Dual Pol 49 NextGen RWI Solution Set Auto PIREP Entry ERAM 43 Weather Sensor Roadmap (1 of 2) TDWR NEXRAD ASR-WSP Wx Right Sizing study for NextGen Observing Capabilities (AJT & AJP) Evaluate Multi-Function Phased Array Radar Technology (MPAR) Develop Inter-Agency Requirements for Air Domain Surveillance Lightning Data NextGen Surveillance & Weather Radar Capability ASR-8/9 WX Channel 93 WSP TR1 TDWR SLEP 1 Wind Shear Det Svc Portfolio (with LIDAR & LLWAS) IID 443 ASR-WSP LLWAS TR FID 104 TDWR SLEP 2 TDWR SLEP 3 ASWON Portfolio FAA Sensors NextGen RWI Solution Set Wind Shear Service Surface Weather Observing Service SAWS, DASI, F420 Surface Weather Observing Solutions Wind Shear Solutions IARD 37 TDWR AWOS AWSS ASOS ASWON TR ISD 408 ASWON TR IID 445 IARD 407 IARD NextGen Surface Observing Capability ISD 447 IID 77 FID 444 ASR-11 WX Channel IARD 407 IID 77 ACFT Wx Sensors 93 Non-Fed AWOS IID 77 FID 104 IID 77 FID 104 FID WSP TR 2/3 IARD 407 X X X X X IARD 407 FID 104 FID 104 IID 77 IID 77 IARD 407 IARD 407 IARD 407 Alaskan Wx Cameras IARD 85 FID 446


Download ppt "Presented to: Right Sizing Team By: Ken Hamm, AJP-6830 Aviation Weather Office Date: July 14, 2010 v0.1 Federal Aviation Administration Aviation Weather."

Similar presentations


Ads by Google