# Presentation: 805591

## NAS ArchitectureServices View 

- January 10, 2000

## NAS Architecture Objectives

- “Living” representation of the FAA’s strategic plan for NAS Modernization
- Promotes FAA/Industry collaboration and communication
- Supports the FAA Acquisition Management System
- Supports the FAA Annual Budget Decision Process

**Notes:**
The NAS Architecture represents a 15 year strategic projection of the types of enabling mechanisms that are necessary to meet the needs of the aviation community. This projection is based primarily on the need to sustain existing NAS Services and then to provide incremental enhancements to those services.
The NAS Architecture is not an end-state, but a “living” representation of an integrated and evolutionary approach to NAS modernization, and builds upon continuing collaboration with aviation system users.
 NAS Services are accomplished through the interaction of people and support activities with systems. The definition of these enabling mechanisms (people, support activities, and systems) over time, form the basis of the NAS Architecture. The NAS Architecture includes all mechanisms (both inside and outside the FAA) that are necessary to provide NAS Services.

## NAS Architecture Views

**Notes:**
The NAS Architecture data is divided into programmatic (i.e. cost and schedule) and technical (i.e. concepts, services, capabilities, implementation steps, requirements, and enabling mechanisms) components that are combined to define the enabling mechanisms necessary to meet the FAA mission and to deliver desired aviation services to the aviation community and aviation service providers.
Elements of the NAS Version 4.0 logical architecture have already been entered into a database containing definitions, schedules, and costs.  Information from the Technical Architecture will expand the database and provide additional information needed for full system implementation including system operators and support activities.  As the Technical Architecture is developed, information stored in the database will be used to define the concepts, technical characteristics, and interfaces for services and capabilities.

## Programs Buy Mechanisms

**Segments**

**...****that buy specific...**

**...that are managed by FAA organizations, that are composed of...**

**...****that are implemented into the...**

**Programs**

**...that are Reported to Congress, are composed of...**

**Programs Buy Mechanisms**

**Notes:**
Programmatic data consists of Programs, Projects, and Segments. Programs (and their lower level components) are the funding elements of the NAS Architecture. They provide the fiscal resources that procure the enabling mechanisms that combine to produce NAS Services.

## Mechanisms Deliver Services

**...****is composed of interactive...**

**...****that are requested by the Aviation Community**

**...****that combined, provide...**

**...that deliver...**

**Mechanisms Deliver Services**

**Capabilities**

**...that provide...**

**Implementation Steps**

**Services**

**Notes:**
Technical data consists of the information necessary to define the NAS Services and the enabling mechanisms necessary to accomplish them. 
NAS Services are high level activities performed by the FAA for the aviation community that contribute to the safe and efficient flow of aircraft throughout the NAS. Services are composed of Capabilities which are, in turn, composed of specific implementation steps that evolve over time. 
The definition of NAS Services through its various implementation steps over time provide the operational context for the interaction (and interdependencies) of the enabling mechanisms of the NAS.

## Architecture Data Base consists of...

**Capability**

- People
- Systems (HW, SW, Facilities)
- Support Activities
- Airspace Design
- Adaptation
- Certification
- AT and AF Procedures
- AT and AF Training
- Support Services

- Dollars
- FAA
- User
- DoD
- NASA
- Schedule

**Architecture Data Base consists of...**

**Program**

**Project**

- Segment

- The building blocks of the NAS Architecture Data Base are UNIQUE Segment-Mechanism pairs

- PROGRAMMATIC

- TECHNICAL

**SEGMENT**** - ****MECHANISM**** Pairs**

**Implementation Step**

**Mechanism**

**Notes:**
Each mechanism in the NAS Architecture database has a corresponding program segment(s) that defines the fiscal resources necessary to enable and/or sustain that mechanism. The combination of a program segment with its corresponding mechanism forms a unique segment-mechanism pair.
Note that programmatic data is also included in the NAS Architecture database for non-FAA costs to Users, DoD, NASA etc.

## Capability and Architecture Tool Suite (CATS)

**Capability and Architecture Tool Suite (CATS)**

**Notes:**

CATS consists of a suite of integrated commercial, off-the-shelf software products configured with custom applications to provide decision and systems engineering support necessary to document the NAS Architecture.  It is the electronic repository of NAS Architecture data. CATS provides user access to the logical (programmatic, cost, and schedule) and technical (technical definitions and requirements) architecture data. Users can input and review data, perform a variety of automated analysis functions, and generate reports and documents. 

## CATS Supports these processes

- Outreach to the Aviation Community
- Provide Response to Aviation Community on the Plans to Implement their Desires
- NAS Modernization
- Provide NAS Level Context for Acquisitions
- Support Executive Investment Decisions, Queries
- Financial Planning for the Annual  Budget
- Forecast new program starts and cost
- Impact Assessments for Annual Budget baseline changes
- Architecture Administration and Maintenance
- Provide care and feeding for the architecture data

- The Capability and Architecture Tool Suite (CATS) is Repository of Architecture Data
- FAA Server address is http://204.108.3.49/CATS/

## The Many Views of Architecture Data

- Services

- Programmatic

- System
- (Predominant View of Version 4.0)

- Location

- Organizational

- Domain

- Phase of Flight

- Support Activity

- Emphasis of Future Architecture Versions

**Notes:**
The segment-mechanism pairs that make up the NAS Architecture can be combined and viewed in many different ways. How you view the NAS Architecture depends on the information you are looking for.
The view provided in the NAS Architecture Version 4.0 document was primarily a system oriented view of the NAS. In the future, the emphasis of architecture versions will be a service view. 
Each view presents a collapsible / expandable tree that you can use to explore the hierarchical structure of the data or if you're not certain or know specifically what data you're looking for you can use the “search" function. 

## Technical Architecture Objectives

- Develop technical details that will:
- Support architectural assessments for Mission Analysis and Investment Analysis
- Provide basis to develop requirements, procedures, interfaces, and plans needed by IPTs
- Ensure NAS products are implemented using a consistent set of standards
- Develop NAS-Level Requirements

**Notes:**
The Technical Architecture provides important information to FAA, the aviation community, and Congress.  For the FAA, it provides an opportunity for better planning.  The Technical Architecture implements the strategic plan for modernizing the NAS, supports investment analysis tradeoffs, and presents a comprehensive design of NAS service groups, showing their capabilities, interfaces, and information flows.  Having a documented architecture, complete with traceable requirements, as the foundation for the NAS will provide a complete picture to help FAA plan future enhancements.  
A unique feature of the Technical Architecture is that mechanisms (people, systems, and support activities) are linked to programmatic segments of cost and schedules from the logical architecture.  This linkage supports the FAA’s acquisition of NAS programs by providing programmatic and technical information to make informed acquisition decisions.

## Technical Architecture Approach

- Perform System of Systems Engineering rather than “box” approach for FAA acquisitions
- Focus on defining and delivering services
- Decompose services into capabilities
- Define capabilities in terms of capability implementation steps
- Present and future
- Define capability implementation steps in terms of mechanisms (People, Systems, and Support Activities) required
- Use this data to populate the Architecture Data Base

**Notes:**
All of the technical activities necessary to deliver a service are described in the Implementation Step diagrams and facing page text.  This systems engineering approach defines the people, systems and support activities necessary for the Implementation Step, not just the delivery of hardware or software to the field.  
Support activities include airspace design, adaptation, certification, AT and AF procedures, AF and AT training, spectrum engineering, and rule making.

## NAS Services

**NAS Services**

- Air Traffic
- Services

- Airport Mgmt
- Services

- Security
- Services

- Safety
- Services

- Certification
- Services

- NAS
- Services

- Flight Planning
- Separation Assurance
- Advisory
- Traffic Mgmt - Synchronization_ _
- Traffic Mgmt -Strategic Flow
- Emergency
- Navigation_	__ _
- Airspace Management
- Infrastructure/Info Management

- Aircraft Ground Ops
- Aircraft Support
- Airport Ops
- Passenger Support

- Facilities
- Communications
- Passengers

- Operations
- Facilities

- Aircraft Certification
- Flight Standards
- Rulemaking
- Accident Investigation
- Aviation Medicine

- Business
- Management
- Services

- System Acquisition
- Regional Administration
- Depot
- Training

- NAS

- Service Groups

- Services

**Notes:**
The Technical Architecture is organized by FAA services provided to aviation system users. The service groups (Air Traffic, Airport Management, Security, Safety, Business Management, and Certification) have been categorized by the Architecture and System Engineering organization (ASD-100). 
 However, the detailed definition and technical decomposition for each of these groups must be coordinated with FAA organizations that are responsible for that service.  The Technical Architecture development cannot proceed until such consensus has been reached.
The Technical Architecture activity to date has focused on the Air Traffic Service Group as it is a prime driver for NAS modernization.
Note there are many ways to structure and define the NAS services.  From a systems engineering perspective, the important thing is that there is a “home” for every NAS service and that people use the same structure, terminology, and definitions.

## Air Traffic Services

- Flight
-  Planning

- ATC-Separation Assurance

- TM-Strategic
- Flow

- Airspace
- Management

- ATC-Advisory

- Emergency & Alerting

- Flight Plan Support
- Flight Plan Processing

- Aircraft - Aircraft
- Aircraft - Terrain / Obstacles
- Aircraft - Airspace
- Surface Separation

- Long-Term Planning
- Flight Day Management
- Performance Assessment

- Airborne
- Surface

- Weather Advisories
- Traffic Advisories
- NAS Status Advisories

- Monitoring & Maintenance
- Spectrum Management
- Government / Agency Support

- Air Traffic
- Services

**Air Traffic Services**

- Service Group

- Services

- Capabilities

- TM-Synchronization

- Airspace Design
- Airspace for Special Use

- Navigation

- Infrastructure /Information
- Management

- Airborne Guidance
- Surface Guidance

- Emergency Assistance
- Alerting Support

**Notes:**
The Air Traffic services and capabilities descriptions were developed by a joint team of ATS, ASD, SETA, and JTA personnel.  The Air Traffic service and capability descriptions were submitted to ATS on April 1999.  The Technical Architecture is proceeding in the Air Traffic area.
Using a refined process based on lessons learned during the Pathfinder activity, the follow-on Technical Architecture activity will focus on three additional capabilities of Air Traffic Services including Separation Assurance, Flight Planning, and Navigation.  Other NAS services will be added at a later date.

## TM Synchronization Service 1 of 2

- TM-Synchronization
- Service
- 104

- Capability

- Implementation
- Steps

**Airborne**
- 1041

**TM Synchronization Service ****1 of 2**

- Air Traffic Service

**Notes:**

The Pathfinder activity selected the Traffic Management - Synchronization Service to test the concept and validate the Technical Architecture process, products, and tools. This Air Traffic Service was selected as it involves many of the Free Flight Phase 1 (FFP1) programs and supports the ongoing follow-on to FFP1 work with RTCA.
The pathfinder products include the following:
Draft implementation steps for Traffic Management - Synchronization completed, Lessons Learned developed and DOORS portion of CATS established to support Technical Architecture

## TM Synchronization Service 2 of 2

- TM-Synchronization
- Service
- 104

- Implementation
- Steps

**Surface**
- 1042

**TM Synchronization Service ****2 of 2**

- Air Traffic Service

- Capability

**Notes:**
There are two capabilities for the TM-Synchronization Service.  This chart shows the Implementation Steps defined for surface synchronization while the preceding chart showed the Implementation steps for airborne synchronization.

## NAS Architecture Definitions

**Architecture** - The structure of NAS components, their interrelationships, and the principles and guidelines governing their design and evolution over time
**Service** - High Level activities performed by the FAA for the aviation community that contribute to the safe and efficient flow of aircraft throughout the NAS
**Capability** - NAS architecture component consisting of a set of functions or related activities that enables or supports the delivery of a service
**Implementation Step** - NAS architecture component consisting of operational scenarios and the mechanisms necessary to enable delivery of a capability
**Operational Scenario** - Narrative description of the interaction of mechanisms necessary to perform a specific portion of a capability
**Mechanism** - The people, systems, or support activities used to accomplish the delivery of an implementation step, capability or service

**Notes:**
The definitions of the technical components of the NAS Architecture are included to provide a better understanding of the architecture terms used. 

## NAS Architecture Definitions (con’t)

**Segment** - The lowest level programmatic component of the architecture. Segments are the financial building blocks of the architecture and provide the RE&D, F&E, and operational resources to procure one or more mechanisms.

**NAS Architecture Definitions (con’t)**

**Notes:**
The programmatic definitions of the for the NAS Architecture are also included to provide a common basis for understanding of the architecture terms used. 

## Technical Architecture Process Document

- Provides vision of Technical Architecture
- Describes process and products
- Includes example products
- Incorporates Pathfinder Lessons Learned
- Organized as reference for teams
- 1.0 Introduction
- 2.0 Technical Architecture Overview
- 3.0 Infrastructure
- 4.0 Technical Architecture Development Environment
- 5.0 Requirements Development
- Appendices

**Notes:**
The TA Process Document describes the process, products and tools used for performing the Technical Architecture.  The Technical Architecture provides the basis for defining NAS-level requirements and other technical details to support FAA’s Acquisition Management System.

The first three sections of the document give an overview of how the Technical Architecture fits into the existing NAS and its documentation.  Section 4 provides guidelines for developing diagrams and text with existing tools.  Section 5 indicates how the requirements will be defined.  The appendices present detailed information (e.g., templates, reference material, a Technical Architecture example, report types, suggestions for database fields, etc.)  to be used as reference.