presented to: right sizing team by: ken hamm, ajp-6830 aviation weather office date: july 14, 2010...

Presented to: Right Sizing Team

By: Ken Hamm, AJP-6830

Aviation Weather Office

Date: July 14, 2010 v0.1

Federal AviationAdministrationAviation Weather

Right Sizing 7/14/10

Bi-weekly

2Federal AviationAdministration

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



July 14, 2010

Templates Used

Type of Product Appendix

Preliminary ACAT Determination Request

A

CRD Plan B

Shortfall Analysis Report C

Service Analysis Approval Matrix H

CRD Approval Matrix I

Concept of Operations K

Concept of Use L



July 14, 2010

Acronyms Used

Acronym Full Name

ACAT Acquisition Category

AMS Acquisition Management System

CONOPS Concept of Operations

CONUSE Concept of Use

CRD Concept and Requirements Definition

CRDR Concept and Requirements Definition Readiness Decision

EA Enterprise Architecture

IARD Investment Analysis Readiness Decision

pPR preliminary Program Requirements



July 14, 2010

Acquisition Management System

Fig. 3: p. 4 of 79



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



July 14, 2010

Service Analysis Phase

Fig. 4: p. 5 of 79



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.



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



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 Product DescriptionNeeded Service or Capability Identifies the new or updated capability

required to meet FAA strategic objectives

Legacy Case Definition Identifies existing operational and technical environment and planned near-term capability

Preliminary Shortfall Detailed description of shortfall

Concept of Operations Describes what initiative will do from a physical or operational perspective



July 14, 2010

Service Analysis: Preliminary ACAT Determination Request



July 14, 2010

Service Analysis: Preliminary ACAT Determination Request (cont’d)



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



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



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)



July 14, 2010

Service Analysis and CRD Products



July 14, 2010

CRD Process



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.



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



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.



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:– N2 Diagram

– Functional Flow Block Diagram



July 14, 2010

Functional Analysis: Generic N2 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 4.7-5 : System Engineering Manual



July 14, 2010

Functional Analysis: Example N2 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 4.7-6 : System Engineering Manual



July 14, 2010

Functional Analysis: More Diagrams

Fig 4.4-23 : System Engineering ManualFig 4.4-21 : System Engineering Manual

Diagram Showing Functional Decomposition Functional Flow Block Diagram



July 14, 2010

Backup Slides



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



July 14, 2010

Su

pp

ort

ing

A

ctiv

itie

s

No

n F

AA

S

enso

rs

CYCY 2009 2010 2012 2013 20142011 2015 2016 2017 2018 2019 2020 2021 2022 2023 2024 2025

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

LightningData

NextGen Surveillance & Weather Radar Capability

ASR-8/9WX Channel

93

WSP TR1

TDWR SLEP 1

Wind Shear Det SvcPortfolio

(with LIDAR & LLWAS)

IID443

ASR-WSP

LLWAS TR

FID104

TDWR SLEP 2 TDWR SLEP 3

ASWON Portfolio

FA

A S

enso

rs

NextGen RWI Solution Set

Win

d S

hea

r S

ervi

ce

Su

rfac

e W

eath

er

Ob

serv

ing

Ser

vice

SAWS, DASI, F420

Surface Weather Observing Solutions

Wind Shear Solutions

IARD37

TDWR

AWOSAWSS

ASOS ASWON TR

ISD408

ASWON TR

IID445

IARD407

IARD407

481

NextGen Surface Observing Capability

ISD447

IID77

FID444

ASR-11WX Channel

IARD407

IID77

ACFT WxSensors

93

Non-FedAWOS

IID77

FID104

IID77

FID104

FID104

26

WSP TR 2/3

IARD407

X

X

X

X

X

IARD407

FID104

FID104

IID77

IID77IARD

407

IARD407

IARD407

Alaskan Wx Cameras

IARD85

FID446

presented to: right sizing team by: ken hamm, ajp-6830 aviation weather office date: july 14, 2010...

Documents