**Program Requirements**

**For**

**Alaska Flight Service Modernization (AFSM)**

January 2008

[(This Page Intentionally Left Blank)]{.smallcaps}.

DOCUMENT VERSION CONTROL

  --------------------------- ------------------------------------------------- ------------------------
  **[Version]{.smallcaps}**   **[Description of Change]{.smallcaps}**           **[Date]{.smallcaps}**

  Draft-01                    Initial Release to AFSM Program Office for review 12/20/2007

  Draft 02                    Release to AFSM Program Office for management     01/28/2008
                              review                                            

                                                                                

                                                                                

                                                                                

                                                                                

                                                                                

                                                                                

                                                                                

                                                                                

                                                                                

                                                                                

                                                                                

                                                                                
  --------------------------- ------------------------------------------------- ------------------------

[(This Page Intentionally Left Blank)]{.smallcaps}.

Table of Contents

[**1** **Background 1-1**](#background)

[1.1 Alaska Flight Service System Shortfalls
1-1](#alaska-flight-service-system-shortfalls)

[1.2 Proposed AFSM System Enhancements
1-2](#proposed-afsm-system-enhancements)

[2 Operational Concept 2-1](#operational-concept)

[2.1 Operations 2-1](#operations)

[2.2 Maintenance 2-2](#maintenance)

[2.3 Quantities and Location 2-3](#quantities-and-location)

[2.4 Schedule Constraints 2-3](#schedule-constraints)

[3 Technical Performance 3-5](#technical-performance)

[3.1 Operational and Functional Requirements
3-5](#operational-and-functional-requirements)

[3.2 Product Characteristics and Performance Requirements
3-22](#product-characteristics-and-performance-requirements)

[4 Physical Integration 4-1](#physical-integration)

[4.1 Real Property 4-1](#real-property)

[4.2 Grounding, Bonding, Shielding and Lightning Protection
4-1](#grounding-bonding-shielding-and-lightning-protection)

[4.3 Cables 4-2](#cables)

[4.4 Hazardous Materials 4-2](#hazardous-materials)

[4.5 Power Systems and Commercial Power
4-3](#power-systems-and-commercial-power)

[4.6 Telecommunications 4-3](#telecommunications)

[4.7 Special Considerations 4-3](#special-considerations)

[5 Functional Integration 5-1](#functional-integration)

[5.1 Integration with Other FAA Enterprise Architecture Elements
5-1](#integration-with-other-faa-enterprise-architecture-elements)

[5.2 Integration with Non-FAA Enterprise Architecture Elements
5-3](#integration-with-non-faa-enterprise-architecture-elements)

[5.3 Information Requirements - TBD
5-4](#information-requirements---tbd)

[5.4 Software Integration 5-4](#software-integration)

[5.5 Standardization 5-4](#standardization)

[6 HUMAN INTEGRATION 6-1](#human-integration)

[6.1 Human / Product Interface 6-1](#human-product-interface)

[6.2 Human Engineering Program 6-1](#human-engineering-program)

[6.3 Human Centered Design 6-1](#human-centered-design)

[6.4 Employee Safety and Health 6-2](#employee-safety-and-health)

[6.5 Specialized Skills and Capabilities
6-2](#specialized-skills-and-capabilities)

[7 SECURITY 7-1](#security)

[7.1 General Security 7-1](#general-security)

[7.2 Physical Security 7-1](#physical-security)

[7.3 Information system security 7-1](#information-system-security)

[7.4 Personnel Security 7-4](#personnel-security)

[7.5 Data management 7-4](#data-management-1)

[7.6 Internet access 7-5](#internet-access)

[7.7 Security Training 7-5](#security-training)

[8 Integrated Logistics 8-1](#integrated-logistics)

[8.1 Staffing 8-1](#staffing)

[8.2 Supply Support 8-1](#supply-support)

[8.3 Support Systems and Equipment 8-2](#support-systems-and-equipment)

[8.4 Technical data 8-2](#technical-data)

[8.5 Training 8-3](#training-1)

[8.6 Packaging, Handling, Storage and Transportation
8-3](#packaging-handling-storage-and-transportation)

[9 Test and Evaluation 9-1](#test-and-evaluation)

[9.1 Critical Operational Issues (COIs)
9-1](#critical-operational-issues-cois)

[9.2 Test and Evaluation requirements
9-2](#test-and-evaluation-requirements)

[10 Implementation and Transition 10-1](#implementation-and-transition)

[10.1 Site Surveys and Planning 10-1](#site-surveys-and-planning)

[10.2 Transition Plan 10-1](#transition-plan)

[10.3 Dual Operations 10-1](#dual-operations)

[10.4 Air Traffic Operations 10-1](#air-traffic-operations)

[10.5 Site Preparation Authority 10-1](#site-preparation-authority)

[10.6 Installation and Checkout (INCO)
10-1](#installation-and-checkout-inco)

[10.7 Field Familiarization 10-2](#field-familiarization)

[10.8 Power Compatibility 10-2](#power-compatibility)

[10.9 Site Authority 10-2](#site-authority)

[11 Quality Assurance 11-1](#quality-assurance)

[11.1 A Quality Assurance (QA) Program must be established and
implemented IAW FAA Order 7210.56, Air Traffic Quality Assurance and
Industry Best Practices.
11-1](#a-quality-assurance-qa-program-must-be-established-and-implemented-iaw-faa-order-7210.56-air-traffic-quality-assurance-and-industry-best-practices.)

[12 Configuration Management 12-1](#configuration-management)

[12.1 The AFSM system Configuration Management (CM) must be IAW FAA
Order 1800.66, NAS Configuration Management.
12-1](#the-afsm-system-configuration-management-cm-must-be-iaw-faa-order-1800.66-nas-configuration-management.)

[13 In-Service Management 13-1](#in-service-management)

[13.1 The NAS AFSM system In-Service Management (ISM) must be managed
IAW FAA Order 6000.30, National Airspace System Maintenance Policy.
13-1](#the-nas-afsm-system-in-service-management-ism-must-be-managed-iaw-faa-order-6000.30-national-airspace-system-maintenance-policy.)

[14 System Safety Management 14-1](#system-safety-management)

[14.1 The AFSM system must manage System Safety Management (SSM) IAW FAA
Order 8040.4, Safety Risk Management (SRM), the FAA Safety Management
System (SMS) Manual, the FAA System Safety Handbook (SSH), and
applicable sections of FAA Order 1800.66, NAS Configuration Management.
14-1](#the-afsm-system-must-manage-system-safety-management-ssm-iaw-faa-order-8040.4-safety-risk-management-srm-the-faa-safety-management-system-sms-manual-the-faa-system-safety-handbook-ssh-and-applicable-sections-of-faa-order-1800.66-nas-configuration-management.)

[Appendix 1: Mission Need Correlation Matrix
1](#appendix-1-mission-need-correlation-matrix)

[Appendix 2: Acronyms 1](#appendix-2-acronyms)

[Appendix 3: Reference documents 1](#appendix-3-reference-documents)

[Appendix 4: Glossary of Terms and Definitions
1](#appendix-4-glossary-of-terms-and-definitions)

[Appendix 5: AFSM Voice Switch Requirements
1](#appendix-5-afsm-voice-switch-requirements)

[Appendix 6: AFSM Telecommunications
1](#appendix-6-afsm-telecommunications)

[Appendix 7: Requirements Traceability Matrix (RTM)
2](#appendix-7-requirements-traceability-matrix-rtm)

List Of Figures

[Figure 1 - AFSM Program Functional Diagram
3-5](#__RefHeading___Toc185932248)

# Background

The Federal Aviation Administration (FAA) provides for the safe and
efficient use of the nation's airspace. FAA Flight Services contributes
to these objectives through weather briefing and flight planning
capabilities; with the primary role of Flight Service being to supply
weather information, aeronautical information, and flight planning
services to general aviation pilots and other users. In Alaska, these
services are provided from Automated Flight Service Stations (AFSSs) and
non-automated Flight Service Stations (FSSs) located throughout the
state. Alaska Flight Service currently operates three (3) AFSSs and
fourteen (14) FSSs. The AFSSs maintain a hub concept with the FSSs
reporting to 1 of the 3 AFSSs.

Alaska Flight Service customers include:

a)  airline transport, Government, commercial, private, student and
    recreational pilots,

b)  military, air taxi and on-demand charter Part 135 operators,

c)  domestic and international aviation interests, and

d)  public safety and law enforcement agencies.

Flight Service coordinates Search and Rescue (SAR) activities; performs
Visual Flight Rules (VFR) orientation services to lost aircraft;
maintains and provides continual weather broadcasts on selected
Navigation Aids (NAVAIDs); issues and cancels Notices-To-Airmen
(NOTAMs); relays clearances, and provides Airport Advisory service at
non-towered or part-time towered airports. Additional supporting
services include: development, translation, processing and coordination
of aeronautical, meteorological and aviation information; to advise,
notify and educate customers.

## Alaska Flight Service System Shortfalls

The Alaska Flight Service Modernization (AFSM) Program Mission Need
Decision, in accordance with the FAA Acquisition Management System (AMS)
policy, was approved and signed in September 2006. The report provided
an in-depth description of the shortfalls of the legacy Alaska Flight
Service system that the AFSM automation program will address.

The following are the Alaska Flight Service automation system
shortfalls.

a)  The Alaskan Flight Service legacy systems had exceeded their useful
    lifecycle, were difficult to support and, did not meet all
    operational requirements as defined in FAA Order 7110.10, Flight
    Services.

b)  There is a need to ensure business continuity by providing redundant
    capabilities for Flight Services facilities for nighttime
    "fallback", or in the event there is a catastrophic failure at the
    Flight Service hub in the Anchorage Air Route Traffic Control Center
    (ARTCC) (ZAN) or any Alaska Flight Service facility.

In May 2007 the FAA replaced the legacy systems with the Operational and
Supportability Implementation System (OASIS) as an interim solution.
OASIS relieved some of the identified shortfalls, but has certain
limitations of its own. The system does not meet unique Alaska
operational requirements; nor does it resolve the redundancy issues.
Additionally, the OASIS contract period of performance will end in
February 2010.

## Proposed AFSM System Enhancements

The primary objective of the AFSM Program is to improve the level of
service in Alaska. The AFSM automation system objectives include the
ability to:

a)  provide necessary capacity to meet growing air traffic technology /
    modernization demands;

b)  expand accessibility of service to Alaska aviation users;

c)  provide products efficiently;

d)  reduce operational costs while meeting performance goals;

e)  meet operational requirements of FAA orders and directives; and

f)  integrate various aeronautical and weather data sources for use in
    the Alaskan operational environment.

    ~~.~~

In addition to addressing the challenges of Alaska's unique flying
environment, implementation of the AFSM system is expected to result in
a Flight Service system that meets operational requirements of Alaska
Flight Services and FAA Order 7110.10, Flight Services.

The AFSM program is designed to also contribute positively to the FAA
Flight Plan Goal of increased safety. This would be accomplished by
decreasing the number of general aviation aircraft accidents in Alaska
from 130 accidents per year observed in FY2000--2002; to a goal of no
more than 99 per year observed in FY 2009**.** The modernized system's
planned deployment is the end of FY2009. Implementation of the AFSM
automation aspect may not occur in time to impact the FY 2009
statistics.

The AFSM automation system is expected to enhance the margin of safety
by:

a)  providing timely and accurate integrated textual and graphical
    products;

b)  increasing the number of calls for preflight briefings;

c)  reducing the number of unanswered or abandoned calls for preflight
    briefings;

d)  reducing the delay to answer calls;

e)  reducing system outages by increasing reliability and
    maintainability;

f)  providing information and services through a web portal and remote
    briefing stations.

The AFSM system will improve the General Aviation (GA) margin of safety
in Alaska through modernization of systems; by providing necessary
capacity to meet growing air traffic technology / modernization demands;
increased accessibility of services to Alaska aviation users; improved
efficiency and augmented capabilities. With improved maintainability and
reliability, the system will also reduce system operating costs while
improving availability and productivity.

\[This Page Intentionally Left Blank\]

# Operational Concept

## Operations

Alaska Flight Service delivers services to general aviation, military
and commercial pilots. The Flight Service Air Traffic Control Specialist
(ATCS) provides pilots with pertinent weather and aeronautical
information by translating, summarizing and interpreting weather
reports, forecasts, satellite images, weather camera pictures, weather
radar products, NOTAMs, and other information. The Flight Service ATCS
also provides Inflight emergency services for aircraft in distress,
search and rescue services through VFR flight plans, and IFR and VFR
flight planning services which include the ability to file, open, amend
or close flight plans.

### Operational Environment

Alaska Flight Service specialists provide services to pilots operating
in an environment that includes remote airports, uncharted landing
areas, difficult geography and extreme climates. Services are primarily
provided using air-ground remote communication outlets and telephones.
Future services will also be provided through a web portal and dedicated
FAA access terminals at local and remote locations. The use of GPS,
ADS-B, and other flight following and location technologies could
enhance search and rescue (SAR), lost aircraft orientation, and
in-flight aircraft services.

### Key System Capabilities

The primary capabilities and features of the new system are described as
follows:

a)  To integrate and accurately display textual and graphical weather
    and aeronautical products from various Government and industry
    sources.

b)  To share a master Flight Plan database that, can, per request,
    populate the Flight Plan as soon as the specialist enters the
    aircraft call sign or pilot's last name.

c)  To show the pilot's route, weather and other potential impacts to
    the flight and to generate alerts to the specialist (or user) for
    defined critical parameters that have changed since the last
    briefing or update

d)  To allow Enhanced Runway Incursion Displays, where runway safety
    information (NOTAMs) can be entered for dissemination by clicking a
    map of the area or airport. Visual indicators on maps are
    automatically updated and the system processes the information and
    records history and coordination information in the background.

e)  To provide Alaska aviation users, through an FAA-approved web
    portal, access to weather and aeronautical information, flight
    planning services, and limited database information to facilitate
    interactive briefings by Flight Service specialists.

f)  To interface with data link systems and broadcast systems to provide
    voice or data transmissions to pilots.

g)  To enable the voice switch, as implemented in the GFE
    telecommunications network, to provide "dynamic resectorization"
    which is defined as "being able to switch any frequency, radio,
    phone call, etc. to another location".

h)  To allow the voice switch network to transfer Flight Services to
    other facilities for business continuity with no more than one
    satellite hop in the end-to-end path, as network topology allows.

i)  To incorporate an Automated-Text-To-Voice (ATTV) capability designed
    to convert text to audible voice for transmission to pilots over
    Transcribed Weather Broadcasts (TWEB), telephone, Telephone
    Information Briefing System (TIBS), Internet, or
    ground/satellite-based data link, with specialist override
    capability.

j)  To mitigate loss of service and avoid single points of failure where
    sources of weather text, graphics, and flight planning data emanate
    from a single physical location.

    NOTE: AFSM Automation Operational Scenarios have been provided by
    the Alaska Flight Service Area Information Group (AFSAIG) to
    illustrate how capabilities will be translated into day-to-day
    utilization by Flight Service specialists and Alaska aviation users.

## Maintenance

The intended service life for the AFSM system is 20 years. The system
will be designed using an open source architecture, which allows greater
alternatives for expansion and adaptability to hardware advances and
software modifications. The system will meet the maintainability
requirements of FAA Order 6000.30, Policy for Maintenance of the NAS.
Nothing in the following paragraphs precludes the use of a contract
maintenance solution if it is in the best interest of the FAA. The
selected maintenance alternative will depend on the FAA Investment
Analysis Decision architecture.

### Hardware Maintenance

First-level maintenance will begin after each site achieves Initial
Operational Capability (IOC). Maintenance actions should be accomplished
using Technical Instruction Books and built-in-test (BIT) capability to
detect and isolate faults to the Lowest Replaceable Unit (LRU). The need
to use support equipment at the local level should be limited.
Maintenance actions at the first-level are:

a)  Periodic maintenance including performance checks and status
    monitoring, and routine maintenance;

b)  Corrective maintenance including restoration, troubleshooting,
    system reset and reconfiguration, repair and replacement, alignment
    and tuning and parameter setting; and

c)  Certification, if required, including initial, periodic and
    after-corrective maintenance and post accident/incident evaluation.

### Software Maintenance

Specific software maintenance requirements will be developed based on
the selected contractor's proposal. On-site software maintenance should
be limited to troubleshooting and minor software mitigations.
Second-level support will be responsible for Configuration Management
(CM) and life-cycle engineering support. The development contractor will
be responsible for configuration control of any development software
until after the product baseline is established. Once the product
baseline is established, the second-level support organization assumes
baseline control.

### Second-Level Support

Second-level maintenance support typically consists of troubleshooting
and analyzing hardware or software problems beyond that performed at
site level by first-level maintenance personnel. Second-level support
also includes: CM of system hardware, software and documentation, and
the development and testing of system modifications. Second-level
support may be performed by contractor or government personnel.

### Depot and Supply Support

Depot support activities consist of the repair and replenishment of
system components, spares and repair parts. Repaired components are
returned to the operational site or stored for future use. Component
reliability, failure rates and repair turnaround time are used to
calculate supply support and depot maintenance requirements.

Supply support [must]{.underline} ensure that sufficient spares and
repair parts to maintain system availability requirements are available.
Required spares and repair parts will be available to site maintenance
personnel on-site from the designated item manager. The government item
manager or designated contractor is responsible for ensuring that
sufficient spares and repair parts are available.

## Quantities and Location

AFSM systems will be deployed to the following locations:

a)  William J. Hughes Technical Center (WJHTC),

b)  second-level Engineering laboratory, as required,

c)  all operational Alaska AFSSs, as required,

d)  all operational Alaska FSSs, as required and,

e)  training facility

f)  other locations to be determined.

## Schedule Constraints

TBD

\[This Page Intentionally Left Blank\]

# Technical Performance

![](media/image1.wmf){width="6.604861111111111in"
height="3.6180555555555554in"}Figure 1, AFSM Program Functional Diagram
depicts a notional functional architecture. The expected functional and
operational capabilities are presented in a graphical manner to provide
a quick comprehensive overview of the AFSM system design.

[]{#__RefHeading___Toc185932248 .anchor}Figure 1 - AFSM Program
Functional Diagram

## Operational and Functional Requirements

### Weather Briefing

#### The AFSM system [must]{.underline} perform weather briefing functions in accordance with FAA Orders.

#### The AFSM system [must]{.underline} receive a weather briefing.

##### The AFSM system [must]{.underline} receive alphanumeric (A/N) weather data for use in providing a weather briefing.

##### The AFSM system [must]{.underline} receive weather graphics for use in providing a weather briefing.

##### The AFSM system [must]{.underline} receive aeronautical information for use in providing a weather briefing.

##### The AFSM system [must]{.underline} receive concurrently alphanumeric (A/N) weather data, weather graphics, and other aeronautical information for use in providing a weather briefing.

#### The AFSM system [must]{.underline} store a weather briefing.

##### The AFSM system [must]{.underline} store alphanumeric (A/N) weather data for use in providing a weather briefing.

##### The AFSM system [must]{.underline} store weather graphics for use in providing a weather briefing.

##### The AFSM system [must]{.underline} store aeronautical information for use in providing a weather briefing.

##### The AFSM system [must]{.underline} store simultaneously alphanumeric (A/N) weather data, weather graphics, and other aeronautical information for use in providing a weather briefing.

#### The AFSM system [must]{.underline} process a weather briefing.

##### The AFSM system [must]{.underline} process alphanumeric (A/N) weather data for use in providing a weather briefing.

##### The AFSM system [must]{.underline} process weather graphics for use in providing a weather briefing.

##### The AFSM system [must]{.underline} process aeronautical information for use in providing a weather briefing.

##### The AFSM system [must]{.underline} process simultaneously alphanumeric (A/N) weather data, weather graphics, and other aeronautical information for use in providing a weather briefing.

#### The AFSM system [must]{.underline} integrate alphanumeric (A/N) weather data, weather graphics, and aeronautical information for use in providing a weather briefing.

#### The AFSM system [must]{.underline} provide weather graphics and overlay capability for use in providing a weather briefing.

#### The AFSM system [must]{.underline} provide weather briefings with site adaptable parameters.

##### The AFSM system [must]{.underline} provide weather briefings with site adaptable parameters for Alaska.

##### The AFSM system [must]{.underline} provide weather briefings with site adaptable parameters for Canada.

##### The AFSM system [must]{.underline} provide weather briefings with site adaptable parameters for the continental United States (CONUS).

##### The AFSM system [must]{.underline} provide weather briefings with site adaptable parameters for Hawaii.

##### The AFSM system [must]{.underline} provide weather briefings with site adaptable parameters for Mexico.

##### The AFSM system [must]{.underline} provide weather briefings with site adaptable parameters for Europe.

##### The AFSM system [must]{.underline} provide weather briefings with site adaptable parameters for Russia.

##### The AFSM system [must]{.underline} provide weather briefings with site adaptable parameters for Japan.

##### The AFSM system [must]{.underline} provide weather briefings with site adaptable parameters for China.

##### The AFSM system [must]{.underline} provide weather briefings with site adaptable parameters for Korea.

#### The AFSM system [must]{.underline} display weather briefing products.

##### The AFSM system [must]{.underline} display A/N weather messages as a weather briefing product.

##### The AFSM system [must]{.underline} display weather graphics as a weather briefing product.

##### The AFSM system [must]{.underline} display weather camera images as a weather briefing product.

##### The AFSM system [must]{.underline} display NOTAMs as a weather briefing product.

##### The AFSM system [must]{.underline} display Air Traffic Control Center (ATCSCC) messages as a weather briefing product.

##### The AFSM system [must]{.underline} display Special Use Airspace (SUA) data as a weather briefing product.

##### The AFSM system [must]{.underline} display Law Enforcement (LE) alert messages as a weather briefing product.

#### The AFSM system [must]{.underline} provide distance measuring on weather graphics.

#### The AFSM system [must]{.underline} provide weather briefings in accordance with FAA-Order 7110.10.

##### The AFSM system [must]{.underline} provide Standard weather briefings in accordance with FAA-Order 7110.10.

##### The AFSM system [must]{.underline} provide Abbreviated weather briefings in accordance with FAA-Order 7110.10.

##### The AFSM system [must]{.underline} provide Outlook weather briefings in accordance with FAA-Order 7110.10.

#### The AFSM system [must]{.underline} provide Route Orient formatted weather briefings.

##### The AFSM system [must]{.underline} provide Route Orient formatted weather briefings that display A/N weather data.

##### The AFSM system [must]{.underline} provide Route Orient formatted weather briefings that display weather graphics with geopolitical boundaries.

##### The AFSM system [must]{.underline} provide Route Orient formatted weather briefings that display grid weather data.

#### The AFSM system [must]{.underline} adapt, scale and stratify the route corridor of a weather briefing.

#### The AFSM system [must]{.underline} provide Local Area formatted weather briefings.

##### The AFSM system [must]{.underline} provide Local Area formatted weather briefings using alphanumeric messages.

##### The AFSM system [must]{.underline} provide Local Area formatted weather briefings using weather graphic products.

##### The AFSM system [must]{.underline} provide Local Area formatted weather briefings using aeronautical data.

#### The AFSM system [must]{.underline} provide Selected Location formatted weather briefings.

##### The AFSM system [must]{.underline} provide Selected Location formatted weather briefings using alphanumeric messages.

##### The AFSM system [must]{.underline} provide Selected Location formatted weather briefings using weather graphic products.

##### The AFSM system [must]{.underline} provide Selected Location formatted weather briefings using aeronautical data.

#### The AFSM system [must]{.underline} provide Trend Weather Information through the display and integration of alphanumeric and graphic products.

#### The AFSM system [must]{.underline} allow customer access to the same weather briefing products available to the flight service specialists through an FAA-approved web portal.

#### The AFSM system [must]{.underline} provide Delta weather briefings.

### Flight Plan Processing

#### The AFSM system [must]{.underline} perform flight planning functions IAW FAA Order 7110.10, Flight Services.

#### Process Domestic flight plans

##### The AFSM system [must]{.underline} validate Domestic flight plans.

##### The AFSM system [must]{.underline} file Domestic flight plans.

##### The AFSM system [must]{.underline} activate Domestic flight plans.

##### The AFSM system [must]{.underline} amend Domestic flight plans.

##### The AFSM system [must]{.underline} close Domestic flight plans.

##### The AFSM system [must]{.underline} cancel Domestic flight plans.

#### Process International Civil Aviation Organization (ICAO) flight plans

##### The AFSM system [must]{.underline} validate ICAO flight plans.

##### The AFSM system [must]{.underline} file ICAO flight plans.

##### The AFSM system [must]{.underline} activate ICAO flight plans.

##### The AFSM system [must]{.underline} amend ICAO flight plans.

##### The AFSM system [must]{.underline} close ICAO flight plans.

##### The AFSM system [must]{.underline} cancel ICAO flight plans.

#### Process Military flight plans

##### The AFSM system [must]{.underline} validate Military flight plans.

##### The AFSM system [must]{.underline} file Military flight plans.

##### The AFSM system [must]{.underline} activate Military flight plans.

##### The AFSM system [must]{.underline} amend Military flight plans.

##### The AFSM system [must]{.underline} close Military flight plans.

##### The AFSM system [must]{.underline} cancel Military flight plans.

#### Process Stereo flight plans

##### The AFSM system [must]{.underline} validate Stereo flight plans.

##### The AFSM system [must]{.underline} file Stereo flight plans.

##### The AFSM system [must]{.underline} amend Stereo flight plans.

##### The AFSM system [must]{.underline} close Stereo flight plans.

##### The AFSM system [must]{.underline} cancel Stereo flight plans.

#### Process DVFR flight plans

##### The AFSM system [must]{.underline} validate DVFR flight plans.

##### The AFSM system [must]{.underline} file DVFR flight plans.

##### The AFSM system [must]{.underline} activate DVFR flight plans.

##### The AFSM system [must]{.underline} amend DVFR flight plans.

##### The AFSM system [must]{.underline} close DVFR flight plans.

##### The AFSM system [must]{.underline} cancel DVFR flight plans.

#### Process Special VFR (SVFR) flight plans

##### The AFSM system [must]{.underline} validate SVFR flight plans.

##### The AFSM system [must]{.underline} file SVFR flight plans.

##### The AFSM system [must]{.underline} activate SVFR flight plans.

##### The AFSM system [must]{.underline} amend SVFR flight plans.

##### The AFSM system [must]{.underline} close SVFR flight plans.

##### The AFSM system [must]{.underline} cancel SVFR flight plans.

#### The AFSM system [must]{.underline} insert preferential routes for IFR flight plans.

#### The AFSM system [must]{.underline} insert aircraft and pilot data into flight plan data fields.

#### The AFSM system [must]{.underline} automatically address flight plans for transmission to appropriate facilities.

#### The AFSM system [must]{.underline} allow manual override to flight plan data fields.

#### The AFSM system [must]{.underline} allow additions to flight plan data fields.

#### The AFSM system [must]{.underline} validate flight plan data fields for accuracy and format.

#### Process Aircraft Movement Messages

##### The AFSM system [must]{.underline} format aircraft movement messages for transmission.

##### The AFSM system [must]{.underline} validate aircraft movement messages for transmission.

##### The AFSM system [must]{.underline} validate aircraft movement messages from external systems.

#### Process Control Messages

##### The AFSM system [must]{.underline} format control messages for transmission.

##### The AFSM system [must]{.underline} validate control messages for transmission.

##### The AFSM system [must]{.underline} validate control messages from external systems.

#### The AFSM system [must]{.underline} convert ICAO flight plan data fields to domestic flight data format.

#### The AFSM system [must]{.underline} convert domestic flight plan data fields to ICAO flight data format.

#### The AFSM system [must]{.underline} display flight plan information history at any position.

#### The AFSM system [must]{.underline} allow flight plan information history import into a flight plan mask.

#### Display Current Flight Plan

##### The AFSM system [must]{.underline} display current flight plan information by aircraft call sign.

##### The AFSM system [must]{.underline} display current flight plan information by a wildcard search.

#### Display Flight Plan Lists

##### The AFSM system [must]{.underline} display prestored aircraft flight plan lists.

##### The AFSM system [must]{.underline} display partial aircraft flight plan lists.

##### The AFSM system [must]{.underline} display proposed aircraft flight plan lists.

##### The AFSM system [must]{.underline} display suspense aircraft flight plan lists.

##### The AFSM system [must]{.underline} display inbound aircraft flight plan lists.

##### The AFSM system [must]{.underline} display timed-out, closed, and cancelled flight plans in a single list.

#### The AFSM system [must]{.underline} display data entry error messages.

#### Process General Messages

##### The AFSM system [must]{.underline} format general messages for transmission.

##### The AFSM system [must]{.underline} validate general messages for transmission.

##### The AFSM system [must]{.underline} validate general messages from external systems.

#### The AFSM system [must]{.underline} display a traffic count database.

### In-Flight Processing

#### The AFSM system [must]{.underline} maintain multiple In-Flight work queues.

#### The AFSM system [must]{.underline} perform In-Flight functions in accordance with FAA Order 7110.10.

#### The AFSM system [must]{.underline} transfer retrieved flight plan information to In-Flight work queues.

#### The AFSM system [must]{.underline} provide a configurable electronic strip-bay.

#### The AFSM system [must]{.underline} provide a configurable airport advisory display that combines stored and real-time information.

##### The airport advisory display [must]{.underline} display stored and real-time weather information.

##### The airport advisory display [must]{.underline} display stored and real-time aeronautical information.

##### The airport advisory display [must]{.underline} display electronic strip-bay information.

#### The AFSM system [must]{.underline} provide ADS-B flight path deviation alerting.

#### The AFSM system [must]{.underline} display a contact list.

### Search and Rescue

#### The AFSM system [must]{.underline} validate SAR messages on receipt.

#### The AFSM system [must]{.underline} generate SAR alerts when SAR messages are received.

#### The AFSM system [must]{.underline} retrieve global SAR data.

#### Process SAR Messages

##### The AFSM system [must]{.underline} allow for the entry of SAR messages.

##### The AFSM system [must]{.underline} allow for the editing of SAR messages.

##### The AFSM system [must]{.underline} allow for the transmission of SAR messages.

##### The AFSM system [must]{.underline} format SAR messages for transmission.

##### The AFSM system [must]{.underline} validate SAR messages for transmission.

#### The AFSM system [must]{.underline} perform automatic flight plan tracking.

#### The AFSM system [must]{.underline} generate an alert when an aircraft has reached a configurable overdue state.

### Data Management

#### The AFSM system [must]{.underline} process aeronautical data.

#### The AFSM system [must]{.underline} process weather data.

#### The AFSM system [must]{.underline} maintain a database of pre-stored flight plans.

#### Alert queue(s) for improperly formatted messages

##### The AFSM system [must]{.underline} maintain alert queue(s) for improperly formatted messages.

##### The AFSM system [must]{.underline} allow editing of improperly formatted messages from alert queue(s).

##### The AFSM system [must]{.underline} allow storing of properly formatted messages from alert queue(s).

#### The AFSM system [must]{.underline} maintain a database of flight plans.

#### The AFSM system [must]{.underline} transmit flight related updates to aircraft equipped with data-link capable systems upon specialist approval.

#### The AFSM system [must]{.underline} automatically update Law Enforcement list(s) IAW FAA Order 7110.10.

#### The AFSM system [must]{.underline} maintain an A/N weather database.

#### The AFSM system [must]{.underline} maintain a graphical weather database.

#### The AFSM system [must]{.underline} maintain a NOTAM database.

#### The AFSM system [must]{.underline} allow the retrieval of flight plans by any flight plan field.

#### The AFSM system [must]{.underline} allow the editing of flight plans.

#### The AFSM system [must]{.underline} allow the re-transmittal of flight plans upon completion of editing.

#### The AFSM system [must]{.underline} maintain an active record of all completed flight data transactions for a configurable number of days.

#### The AFSM system [must]{.underline} update flight plan information received from external sources.

#### The AFSM system [must]{.underline} update flight plan information received from internal sources.

#### The AFSM system [must]{.underline} allow for internal messaging.

#### The AFSM system [must]{.underline} transmit traffic count information directly into the FAA national database.

#### The AFSM system [must]{.underline} allow the transmittal of data via e-mail link.

#### The AFSM system [must]{.underline} maintain a telephone database.

#### Integrated Facsimile Server

##### The AFSM system [must]{.underline} allow for transmission of documents via an integrated fax server.

##### The AFSM system [must]{.underline} allow for receipt of documents via an integrated fax server.

#### The AFSM system [must]{.underline} maintain a general message database.

#### The AFSM system [must]{.underline} maintain a master flight plan database.

#### The AFSM system [must]{.underline} maintain a radio contact database.

#### The AFSM system [must]{.underline} maintain a traffic count database.

#### The AFSM system [must]{.underline} maintain a view sequence database.

#### The AFSM system [must]{.underline} maintain an aeronautical information database.

#### The AFSM system [must]{.underline} maintain an aircraft hexadecimal database for ADS-B equipped aircraft.

#### Maintain Alerts for Delayed Products

##### The AFSM system [must]{.underline} maintain alerts for delayed A/N products.

##### The AFSM system [must]{.underline} maintain alerts for delayed graphical weather products.

#### Message Transmission Queues

##### The AFSM system [must]{.underline} monitor message transmission queue(s) for messages in queue for more than a configurable number of minutes.

##### The AFSM system [must]{.underline} signal alert for messages in queue for more than a configurable number of minutes.

#### Real-time System Updates

##### The AFSM system [must]{.underline} perform real-time 56-day updates.

##### The AFSM system [must]{.underline} perform real-time software releases.

### Weather Observation Processing

#### Weather Observations Processing (includes METARs & SPECIs)

##### The AFSM system [must]{.underline} allow for the entry of multiple weather observations.

##### The AFSM system [must]{.underline} allow for the editing of multiple weather observations.

##### The AFSM system [must]{.underline} allow for the transmission of multiple weather observations.

##### The AFSM system [must]{.underline} format weather observation messages for transmission IAW WMO-386.

##### The AFSM system [must]{.underline} validate weather observation messages for transmission IAW WMO-386.

#### Pilot Reports Processing (includes PIREPs and urgent PIREPs)

##### The AFSM system [must]{.underline} allow for the entry of multiple pilot reports.

##### The AFSM system [must]{.underline} allow for the editing of multiple pilot reports.

##### The AFSM system [must]{.underline} allow for the transmission of multiple pilot reports.

##### The AFSM system [must]{.underline} format pilot report messages for transmission IAW WMO-386.

##### The AFSM system [must]{.underline} validate pilot report messages for transmission IAW WMO-386.

#### The AFSM system [must]{.underline} display data entry error messages.

#### The AFSM system [must]{.underline} provide graphical weather observations.

### Notice-To-Airmen Processing

#### NOTAMs Processing

##### The AFSM system [must]{.underline} allow for the entry of multiple NOTAMs.

##### The AFSM system [must]{.underline} allow for the editing of multiple NOTAMs.

##### The AFSM system [must]{.underline} allow for the transmission of multiple NOTAMs.

##### The AFSM system [must]{.underline} allow for the entry of multiple NOTAM Cancellations.

##### The AFSM system [must]{.underline} allow for the editing of multiple NOTAM Cancellations.

##### The AFSM system [must]{.underline} allow for the transmission of multiple NOTAM Cancellations.

##### The AFSM system [must]{.underline} allow for the simultaneous entry of multiple NOTAMs and multiple NOTAM Cancellations.

##### The AFSM system [must]{.underline} allow for the simultaneous editing of multiple NOTAMs and multiple NOTAM Cancellations.

##### The AFSM system [must]{.underline} allow for the simultaneous transmission of multiple NOTAMs and multiple NOTAM Cancellations.

##### The AFSM system [must]{.underline} format NOTAM messages for transmission.

##### The AFSM system [must]{.underline} validate NOTAM messages for transmission.

#### The AFSM system [must]{.underline} display data entry error messages.

#### The AFSM system [must]{.underline} maintain a NOTAM log IAW FAA Order 7930.2.

#### The AFSM system [must]{.underline} provide for recording of NOTAM coordination activity.

#### The AFSM system [must]{.underline} provide templates/sample NOTAMs customized for individual locations/situations, to be maintained locally.

#### The AFSM system [must]{.underline} provide graphical NOTAMs.

#### The AFSM system [must]{.underline} record NOTAM entries into the traffic count database.

### Training Support Processing

#### Operational Training Modes

##### The AFSM system [must]{.underline} provide a scripted (data sent in a timed sequence) operational training mode.

##### The AFSM system [must]{.underline} provide an interactive (instructor generated message) operational training mode.

#### Configuration Training Modes

##### The AFSM system [must]{.underline} provide a scripted (data sent in a timed sequence) configuration training mode.

##### The AFSM system [must]{.underline} provide an interactive (instructor generated message) configuration training mode.

#### Capture Live Data for Training

##### The AFSM system [must]{.underline} capture live alphanumeric weather data.

##### The AFSM system [must]{.underline} capture live graphical weather data.

#### Store Live Data for Training

##### The AFSM system [must]{.underline} store live alphanumeric weather data.

##### The AFSM system [must]{.underline} store live graphical weather data.

#### Import of Weather Data

##### The AFSM system [must]{.underline} allow import of the stored alphanumeric weather data to other AFSM systems.

##### The AFSM system [must]{.underline} allow import of the stored graphical weather data to other AFSM systems.

#### Export of Weather Data

##### The AFSM system [must]{.underline} allow export of the stored alphanumeric weather data to other AFSM systems.

##### The AFSM system [must]{.underline} allow export of the stored graphical weather data to other AFSM systems.

#### The AFSM system [must]{.underline} allow edit and "replay" of the captured and stored weather data as specific weather scenarios in the operational scripted or interactive modes on selected terminals without operational impact.

##### The AFSM system [must]{.underline} allow for a "start" command within the scenario to begin replay.

##### The AFSM system [must]{.underline} allow for a "stop" command within the scenario during replay.

##### The AFSM system [must]{.underline} allow for a "resume" command within the scenario during replay.

##### The AFSM system [must]{.underline} allow for an instantaneous \"fast forward\" command to specific times within the scenario during replay.

##### The AFSM system [must]{.underline} allow an instantaneous \"rewind\" command to specific times within the scenario during replay.

##### The AFSM system [must]{.underline} record transaction entries during replay.

#### The AFSM system [must]{.underline} provide online Help.

#### The AFSM system [must]{.underline} provide multiple simultaneous training scenario capabilities.

### Supervisory / Administrative Processing

#### Local Activity Report

##### The AFSM system [must]{.underline} provide an exportable report on local activity.

#####  The AFSM system [must]{.underline} allow report parameters to be modifiable.

#### Monitor System

##### The AFSM system [must]{.underline} monitor local resource use.

##### The AFSM system [must]{.underline} monitor external interface status.

##### The AFSM system [must]{.underline} monitor system status.

##### The AFSM system [must]{.underline} monitor system alarms.

#### The AFSM system [must]{.underline} generate law enforcement alerts when an aircraft identification match is found in the law enforcement list(s).

#### Generate System ATCSCC Alerts

##### The AFSM system [must]{.underline} generate ATCSCC alerts when ATCSCC messages are received.

##### The AFSM system [must]{.underline} generate ATCSCC alerts when ATCSCC messages are cancelled.

#### The AFSM system workstations [must]{.underline} be configurable by operational function.

### Logical Display Manipulation

#### The AFSM system [must]{.underline} allow resizing of multiple logical displays within the physical display.

#### The AFSM system [must]{.underline} allow scrolling of multiple logical displays within the physical display.

#### The AFSM system [must]{.underline} allow relocation of multiple logical displays within the physical display.

#### The AFSM system [must]{.underline} allow configuration of displays.

#### The AFSM system [must]{.underline} provide the capability for logical displays on as many as two physical monitors.

#### The AFSM system [must]{.underline} provide the capability for drag and drop of information between multiple logical displays.

#### The AFSM system [must]{.underline} provide the capability to log a briefing from multiple logical displays.

### Continuous Data Recording

#### The AFSM system [must]{.underline} history record all input from internal sources.

#### The AFSM system [must]{.underline} history record all input from external sources.

#### The AFSM system [must]{.underline} history record all output data packets to internal sources.

#### The AFSM system [must]{.underline} history record all output data packets to external sources.

#### The AFSM system [must]{.underline} history record all data necessary to recreate system status.

#### The AFSM system [must]{.underline} history record all data necessary to recreate performance.

#### The AFSM system [must]{.underline} history record all data necessary to recreate system environment.

####  The AFSM system [must]{.underline} delete historical data after a configurable number of days.

#### The AFSM system, including the hardware configuration, [must]{.underline} record all operational data for a configurable number of days.

#### The AFSM system [must]{.underline} time stamp all recorded input data to a calibrated national time standard source in UTC format.

#### The AFSM system [must]{.underline} time stamp all recorded output data to a calibrated national time standard source in UTC format.

#### The AFSM system [must]{.underline} synchronize all recorded input data to a calibrated national time standard source in UTC format.

#### The AFSM system [must]{.underline} synchronize all recorded output data to a calibrated national time standard source in UTC format.

#### The AFSM system [must]{.underline} record all critical data required for recovery of the system to a serviceable state.

#### The AFSM system [must]{.underline} record all critical data required for return of the system to a serviceable state.

#### The AFSM system [must]{.underline} allow the critical recorded data required for operations to be accessible regardless of system status. 

#### The AFSM system [must]{.underline} allow historical data to be archived for further use.

### Event Reconstruction

#### The AFSM system [must]{.underline} automatically store time-stamped data for a configurable number of days, for archive purposes.

#### The AFSM system [must]{.underline} allow for data retrieval and reconstruction of time-stamped data, without interference with the live operational system.

#### The AFSM system [must]{.underline} generate a report on Flight Service user-defined operational information.

### Monitor and Control

#### The AFSM system Monitor and Control function [must]{.underline} monitor system health.

#### The AFSM system Monitor and Control function [must]{.underline} monitor system performance.

#### The AFSM system Monitor and Control function [must]{.underline} generate visual alarms.

##### The AFSM system Monitor and Control function [must]{.underline} generate visual alarms in case of system errors that affect system operation.

##### The AFSM system Monitor and Control function [must]{.underline} generate visual alarms in case of out of tolerance conditions that affect system operation.

##### The AFSM system Monitor and Control function [must]{.underline} generate visual alarms in case of recovery actions that affect system operation.

##### The AFSM system Monitor and Control function [must]{.underline} generate visual alarms in case of overloads that affect system operation.

##### The AFSM system Monitor and Control function [must]{.underline} generate visual alarms in case of failed LRUs that affect system operation.

##### The AFSM system Monitor and Control function [must]{.underline} generate visual alarms in case of other conditions that affect system operation.

#### The AFSM system Monitor and Control function [must]{.underline} generate audible alarms.

##### The AFSM system Monitor and Control function [must]{.underline} generate audible alarms in case of system errors that affect system operation.

##### The AFSM system Monitor and Control function [must]{.underline} generate audible alarms in case of out of tolerance conditions that affect system operation.

##### The AFSM system Monitor and Control function [must]{.underline} generate audible alarms in case of recovery actions that affect system operation.

##### The AFSM system Monitor and Control function [must]{.underline} generate audible alarms in case of overloads that affect system operation.

##### The AFSM system Monitor and Control function [must]{.underline} generate audible alarms in case of failed LRUs that affect system operation.

##### The AFSM system Monitor and Control function [must]{.underline} generate audible alarms in case of other conditions that affect system operation.

### AFSM Voice Switch 

#### See Appendix 5: AFSM Voice Switch Requirements

### Alternate Access

#### The AFSM system [must]{.underline} provide customer access through an FAA-approved web portal.

##### The AFSM web portal [must]{.underline} support a standard web browser for the user interface.

##### The AFSM web portal [must]{.underline} comply with US Government and FAA security requirements.

##### The AFSM web portal [must]{.underline} comply with US Government and FAA web content policies.

##### The AFSM web portal [must]{.underline} provide low bandwidth web pages for users who have low connection speed internet connections.

##### The AFSM web portal [must]{.underline} allow users to access current AFSM weather databases.

##### The AFSM web portal [must]{.underline} provide a glossary of aviation weather terms.

##### The AFSM web portal [must]{.underline} provide historical (trend) weather information.

##### The AFSM web portal [must]{.underline} provide 3 character to 4 character location identifier (LOCID) conversion.

##### The AFSM web portal [must]{.underline} provide 4 character to 3 character LOCID conversion.

#####  The AFSM web portal [must]{.underline} provide 3 character/4 character LOCID encode and decode.

#####  The AFSM web portal [must]{.underline} display current Alaskan Pilot Bulletins.

#####  The AFSM web portal [must]{.underline} allow pilots to file domestic VFR flight plans.

#####  The AFSM web portal [must]{.underline} allow pilots to file domestic IFR flight plans.

#####  The AFSM web portal [must]{.underline} allow pilots to file ICAO VFR flight plans.

#####  The AFSM web portal [must]{.underline} allow pilots to file ICAO IFR flight plan.

#####  The AFSM web portal [must]{.underline} allow pilots to file DVFR flight plans.

#####  The AFSM web portal [must]{.underline} have access to the Alaskan Master Flight Plan database.

#####  The AFSM web portal [must]{.underline} provide route briefings.

#####  The AFSM web portal [must]{.underline} provide area briefings.

#####  The AFSM web portal [must]{.underline} provide RAIM data in an understandable graphical form.

#####  The AFSM web portal [must]{.underline} support Personal Desktop Assistant (PDA) and small screen rendering devices (SSR).

#####  The AFSM web portal [must]{.underline} provide interactive weather briefings with a FSS specialist if requested by the user.

#####  The AFSM web portal [must]{.underline} support weather and aeronautical information from a FSS delivery via an e-mail messaging platform.

#####  The AFSM web portal [must]{.underline} support Pilot/Flight Service user forums.

#####  The AFSM web portal [must]{.underline} allow access to Alaskan Weather Cameras.

#####  The AFSM web portal [must]{.underline} allow pilots to cancel VFR flight plans.

#####  The AFSM web portal [must]{.underline} allow pilots to close VFR flight plans.

#####  The AFSM web portal [must]{.underline} allow pilots to amend VFR flight plans.

#####  The AFSM web portal [must]{.underline} provide a Plain Language option.

#####  The AFSM web portal [must]{.underline} provide access to flight planning functionality.

#####  The AFSM web portal [must]{.underline} provide access to flight planning resources.

#### The AFSM system [must]{.underline} provide access through a remote user access terminal.

#####  The AFSM system [must]{.underline} provide Flight Service Specialist remote user access to all of the AFSM system functionality and data through the remote user access terminal.

##### The AFSM system [must]{.underline} provide access through a remote user access terminal at remote locations.

##### The AFSM system [must]{.underline} provide access through a remote user access terminal with interaction between the user pilot and the Flight Service Specialist.

##### The AFSM system [must]{.underline} provide access through a remote user access terminal that is configurable for operations at temporary Flight Service Station locations.

#### The AFSM system [must]{.underline} provide exportable activity reports.

##### The AFSM system [must]{.underline} provide exportable web portal activity reports.

##### The AFSM system [must]{.underline} provide web portal activity reports with site adaptable parameters.

##### The AFSM system [must]{.underline} provide exportable activity reports.

##### The AFSM system [must]{.underline} provide activity reports with site adaptable parameters.

### Automated Text To Voice (ATTV) Processing

#### The AFSM system [must]{.underline} interface with the existing ATTV system. 

## Product Characteristics and Performance Requirements

### Service Levels

#### Reserved

### Availability

#### The AFSM system availability (A~o~) [must]{.underline} be greater than or equal to (≥) 0.999.

### Reliability

#### The AFSM system [must]{.underline} have a Mean-Time-Between-Failures (MTBF) of no less than 5000 hours over the full range of environmental conditions.

### Maintainability

#### The AFSM system Mean-Time-To-Repair (MTTR) for the system [must]{.underline} not exceed 0.5 hours. This period includes all time necessary to localize, repair, test and restore a failed system/unit to its established baseline performance once on-site repair activity has begun.

#### The AFSM system total time to complete all periodic tasks [must]{.underline} not exceed 12 staff hours annually; nor [must]{.underline} any periodic maintenance event require more than one person to accomplish the task.

#### The AFSM system [must]{.underline} have the capability to automatically diagnose the cause of system faults.

#### The AFSM [must]{.underline} have the capability to identify failures to Lowest Replaceable Unit (LRU).

#### The AFSM [must]{.underline} allow replacement of failed LRU without affecting functional operations.

### Recovery

#### The AFSM system [must]{.underline} restore itself in less than 15 minutes after restoration of electrical power to the normal operational mode in effect at the time of power loss.

### System Reserve

#### The AFSM system processing resource [must]{.underline} meet the following reserves:

##### Central Processing Unit (CPU) use. The AFSM system [must]{.underline} contain reserve processing capacity so that the mean use over any 5-minute interval is no more than 50 percent of the maximum processing capacity.

##### Memory Use. The AFSM system [must]{.underline} contain reserve memory capacity so that memory use does not exceed 50 percent of the maximum memory capacity.

##### Storage Use. The AFSM system [must]{.underline} contain on-line reserve storage capacity so that the storage use within the system does not exceed 50 percent of the maximum on-line storage capacity.

### Portability

#### The AFSM system software [must]{.underline} be portable to the extent that:

##### Porting AFSM system software to another implementation of the Operating System (OS) and programming language on the same hardware platform [must]{.underline} satisfy all functional and performance requirements and 98 percent of the code [must]{.underline} be portable without change.

##### Porting AFSM system software to another Portable Operating System Interface Standard (POSIX)-compliant hardware platform [must]{.underline} satisfy all the functional and performance requirements and 95 percent of the code [must]{.underline} be portable without change.

[]{.mark}

[]{.mark}

[]{.mark}

# Physical Integration

## Real Property

Procurement and requirements pertaining to Land, Space, Buildings, and
Heating, Ventilating, Air Conditioning (HVAC) in this section will not
be addressed as part of the AFSM Automation System Modernization.

### Land -- Not applicable.

### Space -- Not applicable

### Reserved

### Environmental

#### The AFSM system [must]{.underline} be in accordance with FAA Order 1050.10, Prevention, Control and Abatement of Environmental Pollution at FAA Facilities.

### Energy Conservation

#### The AFSM system [must]{.underline} be in accordance with FAA Order 1053.1, Energy and Water Management Program for FAA Buildings and Facilities.

### Heating, Ventilating, Air Conditioning (HVAC) -- Not applicable.

## Grounding, Bonding, Shielding and Lightning Protection

### Grounding, bonding, shielding and lightning protection of equipment [must]{.underline} be in accordance with the following:

1.  FAA-Standard-019, Lightning Protection, Grounding, Bonding and
    Shielding for Facilities;

2.  FAA-Standard-020, Transient Protection Grounding, Bonding, and
    Shielding Requirements for Equipment;

3.  NFPA 70 Standard, National Electrical Code®; and Institute of
    Electrical and Electronics Engineers Standard 1100-1999,

4.  Recommended Practice for Powering and Grounding for Sensitive
    Electric Equipment.(IEEE 1100-2005 also known as IEEE Emerald Book)

5.  Requirements for grounding, bonding, shielding and lightning
    protection [must]{.underline} be specified to comply with FAA-G-2100
    and associated standards.

## Cables

### The AFSM system cabling [must]{.underline} be in accordance with the NFPA 70 Standard, National Electrical Code®, and FAA-C-1217, Electrical Work, Interior.

### The AFSM system cable installation [must]{.underline} be in accordance with FAA-G-2100, Electronic Equipment, General Requirements.

## Hazardous Materials

### General Requirements.

#### The AFSM system [must]{.underline} be compliant with the applicable provisions of the following:

1.  FAA-G-2100, Electrical Requirements,

2.  FAA Order 4800.2, Utilization and Disposal of Excess and Surplus
    Personal Property.

3.  FAA Human Factors Design Standard (HFDS).

### Handling of Hazardous Materials.

#### The AFSM system handling of hazardous materials [must]{.underline} be in accordance with the following:

1.  29 Code of Federal Regulations (CFR Title 29, Part 1910),
    Occupational Safety and Health Standards; (www.osha.gov)

```{=html}
<!-- -->
```
4.  FAA Order 8040.4, Safety Risk Management;

5.  29 CFR 1910.1000, Air Contaminants;

6.  Code of Federal Regulations, Title 40, Protection of the
    Environment, subchapter I, Solid Waste (parts 260, 700, and 766).

### The Hazardous materials inherent in AFSM system technology [must]{.underline} be in accordance with FAA Order 1050.10, Prevention, Control and Abatement of Environmental Pollution at FAA Facilities.

### The AFSM system components [must]{.underline} be delivered free of asbestos, polychlorinated biphenyls (PCBs), lead, and class 1 ozone depleting substances except for the use of lead based solder on circuit boards in accordance with the following:

1.  FAA Order 1050.20, Airway Facilities Asbestos Control;

```{=html}
<!-- -->
```
7.  FAA Order 1050.14, Polychlorinated Biphenyls (PCBs) in the National
    Airspace Part 82 Protection of Stratospheric Ozone;

8.  Environmental Protection Agency (EPA), Listing of Global
    Ozone-Depleting Substances;
    ([www.epa.gov/Ozone/ods2.html](http://www.epa.gov/Ozone/ods2.html))

### The AFSM system equipment disposal plans [must]{.underline} address the identification, handling, storage, and disposal of hazardous materials, in accordance with the following: 

1.  FAA Order 1050.10, Prevention, Control and Abatement of
    Environmental Pollution at FAA Facilities;

```{=html}
<!-- -->
```
9.  40 CFR 260, 49 CFR Sub-chapter C, 40 CFR 260, 40 CFR 700 to 766.

## Power Systems and Commercial Power

### The AFSM system power requirements [must]{.underline} comply with applicable sections of the following: 

1.  FAA-G-2100, Electronic Equipment, General Requirements.

```{=html}
<!-- -->
```
10. NFPA 70 National Electrical Code®.

## Telecommunications

### The AFSM system telecommunications service requirements are provided in Appendix 6 (The Government will work with the selected vendor to define the requirements for GFE telecommunications following contract award.)

### The vendor [must]{.underline} provide analyses to describe an optimal telecommunications network for the implicit AFSM telecommunications.

## Special Considerations

### The AFSM system installation [must]{.underline} be in accordance with the following:

1.  Federal Emergency Management Administration (FEMA) Handbook 224,

```{=html}
<!-- -->
```
11. International Communication Satellite Systems Conference (ICSSC)
    RP-4;

12. Seismic safety -- FAA Application Handbook for FAA-G-2100G,
    Electronic Equipment, General Requirements;

13. Applicable Architectural Barriers Act Accessibility Standard (ABAAS)
    requirements.

### All contractors performing installation on an airport [must]{.underline} be in compliance with the following: FAA Advisory Circular No. 150/5370-2, Operational Safety on Airports during Construction.

# Functional Integration

This section defines functional integration requirements associated with
integrating the AFSM system into the operational environment. This
involves interfacing with the primary weather and aeronautical
information systems of the NAS. It also includes functional integration
with non-NAS elements, such as the NWS and the Flight Service for the
21^st^ Century (FS21) system.

## Integration with Other FAA Enterprise Architecture Elements

### General Interface Requirement

#### The AFSM system [must]{.underline} be integrated IAW applicable Interface Requirement Documents (IRDs) and Interface Control Documents (ICDs).

### Automatic Dependent Surveillance -- Broadcast (ADS-B)

#### The AFSM system [must]{.underline} be integrated with the Automatic Dependent Surveillance-Broadcast (ADS-B) system.

### Alaska Weather Cameras

#### The AFSM system [must]{.underline} be integrated with the Alaska Weather Camera system.

### Juneau Airport Wind System (JAWS)

#### The AFSM system [must]{.underline} be integrated with the Juneau Airport Wind System (JAWS).

### Advanced Technologies and Procedures (ATOP)

#### The AFSM system [must]{.underline} be integrated with the Advanced Technologies and Procedures (ATOP) system.

### Micro Enroute Automated Radar Tracking System (MEARTS)

#### The AFSM system [must]{.underline} be integrated with the Micro-Enroute Automated Radar Tracking System (MEARTS).

### NAS Aeronautical Information Management Enterprise System (NAIMES)

#### The AFSM system [must]{.underline} be integrated with the National Airspace System (NAS) Aeronautical Information Management Enterprise System (NAIMES) or its replacement.

### NADIN MSN Replacement (NMR)

#### The AFSM system [must]{.underline} be integrated with the National Air Space Data Interchange Network (NADIN) Message Switched Network (MSN) Replacement (NMR) system.

### Weather Message Switching Center Replacement (WMSCR) sustainment

#### The AFSM system [must]{.underline} be integrated with the Weather Message Switching Center Replacement (WMSCR) sustainment system.

### Operational and Supportability Implementation System (OASIS)

#### The AFSM system [must]{.underline} be integrated with the Operational and Supportability Implementation System (OASIS).

### Flight Data Processing (FDP) 2000

#### The AFSM system [must]{.underline} be integrated with the Flight Data Processing (FDP) 2000 system.

### EnRoute Automation Modernization (ERAM) System

#### The AFSM system [must]{.underline} be integrated with the EnRoute Automation Modernization (ERAM) System.

#### The AFSM system [must]{.underline} be integrated with the HOST system during a fallback scenario. 

### Aeronautical Information System Replacement (AISR)

#### The AFSM system [must]{.underline} be integrated with the Aeronautical Information System Replacement (AISR) system.

### Direct User Access Terminal System (DUATS)

#### The AFSM system [must]{.underline} be integrated with the Direct User Access Terminal Systems (DUATS).

### Automated Weather Observing Systems (AWOS)

#### The AFSM system [must]{.underline} be integrated with the Automated Weather Observing Systems (AWOS).

### Automated Surface Observing Systems (ASOS)

#### The AFSM system [must]{.underline} be integrated with the Automated Surface Observing Systems (ASOS).

## Integration with Non-FAA Enterprise Architecture Elements

### The AFSM system [must]{.underline} be integrated with non-NAS elements, as defined in the applicable IRD and ICD. 

### National Weather Service (NWS) Data

#### The AFSM system [must]{.underline} receive NWS data.

### Next Generation Weather Radar (NEXRAD)

#### The AFSM system [must]{.underline} receive NEXRAD data.

### NAV Canada

#### The AFSM system [must]{.underline} integrate with the NAV Canada system.

#### The AFSM system [must]{.underline} receive NAV Canada data.

##### The AFSM system [must]{.underline} receive NAV Canada textual products.

##### The AFSM system [must]{.underline} receive NAV Canada graphical products.

##### The AFSM system [must]{.underline} receive NAV Canada aeronautical products.

#### The AFSM system [must]{.underline} process NAV Canada data.

##### The AFSM system [must]{.underline} process NAV Canada textual products.

##### The AFSM system [must]{.underline} process NAV Canada graphical products.

##### The AFSM system [must]{.underline} process NAV Canada aeronautical products.

#### The AFSM system [must]{.underline} display NAV Canada products.

##### The AFSM system [must]{.underline} display NAV Canada textual products.

##### The AFSM system [must]{.underline} display NAV Canada graphical products.

##### The AFSM system [must]{.underline} display NAV Canada aeronautical products.

### United States Customs - Domestic Air Interdiction Coordination Center (DAICC)

#### The AFSM system [must]{.underline} be integrated with the Air Marine Operations Center (AMOC) system.

### Foreign Air Traffic Control interfaces

#### The AFSM system [must]{.underline} be integrated with Foreign Air Traffic Control (ATC) systems.

### El Paso Interdiction Center (EPIC)

#### The AFSM system [must]{.underline} be integrated with the El Paso Interdiction Center (EPIC) system.

### North American Aerospace Defense Command (NORAD)

#### The AFSM system [must]{.underline} be integrated with the North American Aerospace Defense (NORAD) Command system.

### Military Base Operations (MBO)

#### The AFSM system [must]{.underline} be integrated with Military Base Operations (MBO) systems.

### Flight Service for the 21st Century (FS21)

#### The AFSM system [must]{.underline} be integrated with the Flight Service for the 21^st^ Century (FS21) system.

### Automated Weather Sensor System (AWSS)

#### The AFSM system [must]{.underline} be integrated with the Automated Weather Sensor System (AWSS).

## Information Requirements - TBD

## Software Integration

### The AFSM system software integration, development, and documentation [must]{.underline} be in accordance with the following FAA Standard or an industry standard that is acceptable to the FAA:

#### FAA-STD-026, NAS Software Development,

#### FAA-STD-018, Computer Software Quality Program Requirements

## Standardization

### The AFSM system functional interface characteristics, protocols and data message formats of required information [must]{.underline} be IAW all applicable Interface Requirement Documents (IRD) and Interface Control Documents (ICD). 

### The AFSM system required functional integration interfaces will use existing FAA and non-FAA system IRDs where applicable.

### The AFSM system functional integration ICDs [must]{.underline} be developed IAW the following:

1.  FAA-STD-025, Preparation of Interface Documentation.

```{=html}
<!-- -->
```
14. Applicable FAA system IRDs.

15. Applicable non-FAA system IRDs.

[(This Page Intentionally Left Blank)]{.smallcaps}

# HUMAN INTEGRATION

The Alaska Flight Service Modernization system [must]{.underline} be
developed IAW the Human Factors Design Standard (HFDS) and
Computer-Human Interface (CHI) standards sanctioned by the FAA.

## Human / Product Interface

### The AFSM system design [must]{.underline} comply with requirements imposed by the following:

#### The Human Factors Design Standard (HFDS) For Acquisition of Commercial-Off-The-Shelf, Non-Developmental, and Developmental Systems;

#### FAA-G-2100, Electronic Equipment, General Requirements; and

#### FAA Order 9550.8, FAA Human Factors Policy.

## Human Engineering Program

### The AFSM system development contractor [must]{.underline} conduct a Human Factors Engineering Program as outlined in MIL-HDBK-46855A, Human Engineering (HE) Program Process and Procedures, Section 4 "Program Tasks"

### The AFSM system development contractor [must]{.underline} conduct a Human Factors Engineering Program as outlined in MIL-HDBK-46855A, Human Engineering (HE) Program Process and Procedures, Section 7, Program "HE Procedures for Contractors".

### The AFSM system development contractor [must]{.underline} perform a user-centered task analysis as outlined in MIL-HDBK-46855A, Human Engineering (HE) Program Process and Procedures Section 8 "HE Methods and Tools"

## Human Centered Design

The AFSM system human-to-system interfaces [must]{.underline} be IAW
human-centered design processes.

Note: These processes are described in the FAA Human Factors Awareness
tool, Usability section at the FAA Human Factors Home Page. They can
also be found within ISO 13404 (February 1996): Human-centered design
processes for interactive systems.

### Usability

#### The AFSM system human-system integration shall be IAW with the HFDS, Chapter 3.1 "General"**.**

####  The AFSM system human-system integration shall be IAW with the HFDS, Chapter 3.2 "Design and Evaluation"**[.]{.smallcaps}**

### Computer-Human Interface

#### The AFSM system interfaces [must]{.underline} be in accordance with the HFDS, Chapter 8 "Computer Human Interface".

### Design Simplicity

The AFSM system [must]{.underline} be designed for simplicity of use IAW
the HFDS, Chapter 2.2 "Simplicity".

Note: The metrics for design simplicity include (but not limited to) the
number of procedures, number of steps in a procedure, number of input
device activations, number of decision points, and entry redundancy.

### Communications and Teamwork

The AFSM system [must]{.underline} enable personnel communication and
information interchange IAW with the HFDS, Section 3.2.3 "Consider
Effects on Coordination".

Note: The design goal is to enable and facilitate inter-user
communications; for example, between the Flight Service Specialists,
Flight Service Specialists and pilots, maintainers and maintainers at
remote sites.

### Automation Guidelines

#### The AFSM system interfaces [must]{.underline} comply with the HFDS, Chapter 3 "Automation"

## Employee Safety and Health

### The AFSM system [must]{.underline} comply with relevant Occupational Safety and Health Administration (OSHA) mandates and other safety and health regulations and standards, as specified in the FAA HFDS Section 12, Personnel Safety, 

### The AFSM system [must]{.underline} comply with relevant Occupational Safety and Health Administration (OSHA) mandates and other safety and health regulations and standards, as specified in Section 13, "Environment". 

### The AFSM system [must]{.underline} conform to FAA Specification FAA-G-2100, Electronic Equipment, General Requirements section on Personnel Safety.

## Specialized Skills and Capabilities

### Anthropometry and Workplace Design

#### The AFSM system [must]{.underline} comply with human performance thresholds and criteria, as specified by the HFDS Section 14, "Anthropometry and Biomechanics". 

#### The AFSM system [must]{.underline} conform to site and system requirements, according to HFDS Section 10, "Workstation and Workplace Design".

### Human Performance Requirements

#### The AFSM system [must]{.underline} be operable and maintainable by the current workforce, as verified by a Task and Skills Analysis.

### Workload

#### The AFSM system operator and maintainer cognitive and physical workloads [must]{.underline} be in accordance with the HFDS, Section 3.1.11 "Avoid Extreme Workload Levels"

#### The AFSM system operator and maintainer cognitive and physical workloads [must]{.underline} be in accordance with the HFDS, Section 3.1.10 "Avoid Increasing Demands for Cognitive Resources".

### Training

#### The AFSM system [must]{.underline} be IAW the HFDS, Section 3.1.24 "Make Systems Easy to Learn".

#### The AFSM system [must]{.underline} be IAW the HFDS Section 3.10 "Training".

[(This Page Intentionally Left Blank)]{.smallcaps}

# SECURITY

## General Security

The AFSM system has inherent security risks and potentially introduces
increased security risks into the NAS.

### The AFSM system [must]{.underline} ensure that appropriate security requirements (technical, operational, and management controls) are taken to mitigate risks to the AFSM system and other NAS elements to an acceptable level based upon a security risk assessment.

### The AFSM system security controls [must]{.underline} be non-disruptive to ATC operations. 

### The AFSM system architecture [must]{.underline} adhere to the FAA Information System Security Architecture Version 6.

### The AFSM system security policies [must]{.underline} comply with the 44 United States Code (U.S.C.), Federal Information System Security Act.

### The AFSM system security policies [must]{.underline} comply with FAA Order 1370.82, Information System Security Program.

## Physical Security

### The AFSM system [must]{.underline} comply with FAA Order 1600.6, Facility Security Policy.

### The AFSM system [must]{.underline} comply with FAA Order 1600.69, FAA Facility Security Management Program.

### The AFSM system [must]{.underline} segregate interface equipment for encrypting data communications to computer equipment performing air traffic functions.

### The AFSM system [must]{.underline} remotely monitor and control access to unmanned facilities to prevent interruption of service, unauthorized access to computers, theft, and damage to government property.

### Physical Integrity Monitoring

#### The AFSM system [must]{.underline} monitor the physical integrity of the overall system to the maximum extent possible.

## Information system security

### System Integrity

#### The AFSM system [must]{.underline} be protected from threats to integrity.

### Availability

#### The AFSM system [must]{.underline} be protected from threats to availability.

#### The AFSM system [must]{.underline} protect assets from denial of service.

#### The AFSM system [must]{.underline} protect assets from unacceptable degradation of service.

### Confidentiality

#### The AFSM system [must]{.underline} provide for information system confidentiality based upon a risk assessment.

### Non-Repudiation

#### The AFSM system [must]{.underline} implement non-repudiation service.

### Access Control

#### The AFSM system [must]{.underline} provide for access control.

#### The AFSM system [must]{.underline} enforce separation of security domains.

#### The AFSM system [must]{.underline} enforce secure import of authorized and unauthorized information and export of authorized information outside its security domain.

### Identification and authentication

#### The AFSM system [must]{.underline} uniquely identify all authorized entities.

#### The AFSM system [must]{.underline} authenticate an authorized entity's identity.

### Malicious Activity

#### The AFSM system [must]{.underline} protect against malicious activity.

#### The AFSM system [must]{.underline} alert administrators when malicious activity is detected.

### Security Operation

#### The AFSM system [must]{.underline} protect access to assets during all operational states.

#### The AFSM system [must]{.underline} enforce system security rules during all operational states.

### Security Management

#### The AFSM system [must]{.underline} implement technical security management.

#### The AFSM system [must]{.underline} enforce established security rules and procedures.

#### The AFSM system [must]{.underline} establish criteria for determining who [must]{.underline} have access or clearances to information on a need-to-know basis.

#### The AFSM system [must]{.underline} provide centralized security incident reporting.

### Security Audit

#### The AFSM system [must]{.underline} record all system access attempts in a security audit log.

#### The AFSM system [must]{.underline} preserve the security audit log for a minimum of 90 days.

#### The AFSM system [must]{.underline} prevent modification of the events recorded in the security audit log.

#### The AFSM system [must]{.underline} record all detected malicious activity in the security audit log.

#### The AFSM system [must]{.underline} record all attempts to violate system security rules in the security audit log.

#### The AFSM system [must]{.underline} record all security administration activities in the security audit log.

#### The AFSM system [must]{.underline} implement security audit review mechanisms.

#### The AFSM system [must]{.underline} record the security audit log during all operational states.

#### Audit-Recording Tools

##### The AFSM system [must]{.underline} provide audit-recording tools to collect information for deterrence, detection, and damage assessment objectives without compromising system performance.

#####  The AFSM system [must]{.underline} provide audit-recording tools to collect information for deterrence, detection, and damage assessment objectives without compromising system capacity.

#####  The AFSM system [must]{.underline} provide audit-recording tools to analyze information for deterrence, detection, and damage assessment objectives without compromising system performance.

#####  The AFSM system [must]{.underline} provide audit-recording tools to analyze information for deterrence, detection, and damage assessment objectives without compromising system capacity. 

#### The AFSM system [must]{.underline} provide a notification capability of security events.

### Recovery

#### The AFSM system [must]{.underline} provide recovery measures from security incidents.

#### The AFSM system [must]{.underline} provide recovery features for survivability in the event of system compromise.

#### The AFSM systems [must]{.underline} ensure automated recovery of data after a system failure.

#### The AFSM system [must]{.underline} ensure that all security functions complete successfully.

#### The AFSM system [must]{.underline} ensure that all security functions recover.

##### The AFSM system [must]{.underline} ensure that all security functions recover to a consistent state.

##### The AFSM system [must]{.underline} ensure that all security functions recover to a secure state.

## Personnel Security

### The AFSM system [must]{.underline} comply with FAA Order 1600.1, Personnel Security Program.

### Contractor and Industrial personnel security control [must]{.underline} comply with FAA Order 1600.72, Contractor and Industrial Security Program.

## Data management

### The AFSM system [must]{.underline} provide for the management for data in accordance with the following:

#### The AFSM system [must]{.underline} provide for the management for data in accordance with FAA Order 1375.1, Data Management

#### The AFSM system [must]{.underline} provide for the management for data in accordance with FAA Order 1200.22, NAS Data and Interface Equipment Used by Outside Interest.

## Internet access

### The AFSM system [must]{.underline} protect any access to the internet in accordance with the following:

#### The AFSM system [must]{.underline} protect any access to the internet in accordance with FAA Order 1370.83, Internet Access Points 

#### The AFSM system [must]{.underline} protect any access to the internet in accordance with FAA Order 1370.84, Internet Services.

## Security Training

### The AFSM system [must]{.underline} provide security training.

#### The AFSM system [must]{.underline} provide security training for the technical controls implemented.

#### The AFSM system [must]{.underline} provide security training for the operational controls implemented.

#### The AFSM system [must]{.underline} provide security training for the management controls implemented.

\[This Page Intentionally Left Blank\]

# Integrated Logistics

An Integrated Logistics Support plan [must]{.underline} be prepared and
submitted to the FAA. The maintenance philosophy [must]{.underline}
concur with the system maintenance concept and ensure that
supportability requirements are incorporated into the design of the
equipment/system.

## Staffing

### Operations

#### The operations of the AFSM system [must]{.underline} utilize the existing FAA job categories.

#### The operations of the AFSM system [must]{.underline} utilize the existing FAA job skill classifications.

### Maintenance

The maintenance philosophy [must]{.underline} concur with the system
maintenance concept and ensure that supportability requirements are
incorporated into the design of the equipment/system.

#### The maintenance of the AFSM system [must]{.underline} be IAW FAA Order 1100.157. National Systems Engineering Divisions Maintenance or industry standard that is acceptable to the FAA. 

#### The maintenance of the AFSM system [must]{.underline} utilize the existing FAA job categories.

#### The maintenance of the AFSM system [must]{.underline} utilize the existing FAA skill classifications.

## Supply Support

### Hardware Barcode

#### The AFSM system hardware [must]{.underline} be bar-coded.

#### The AFSM system hardware bar-coded data [must]{.underline} be entered into a barcode system.

#### The AFSM system barcode system [must]{.underline} be transitioned to the FAA. 

### Maintenance Repair

#### Site Level Maintenance Repair

##### Site level maintenance repair for the AFSM system [must]{.underline} include removal of defective Lowest Replaceable Units (LRUs).

##### Site level maintenance repair for the AFSM system [must]{.underline} include replacement of defective Lowest Replaceable Units (LRUs).

##### Site level maintenance repair for the AFSM system [must]{.underline} include restoration of the system.

### Integrated Logistics Support Plan

#### An Integrated Logistics Support plan [must]{.underline} be prepared and submitted to the FAA.

### Field Level Maintenance Repair

#### Field level maintenance activities [must]{.underline} be performed on the AFSM system equipment installed in its operating environment.

#### Field level maintenance activities [must]{.underline} include preventative maintenance actions.

#### Field level maintenance activities [must]{.underline} include corrective maintenance actions.

### Depot Level Maintenance

#### Depot level maintenance [must]{.underline} be accomplished by repairing and/or replacing defective LRU's.

## Support Systems and Equipment

### The AFSM system support systems and equipment [must]{.underline} be provided for FAA Test and Evaluation.

### The AFSM system support systems and equipment [must]{.underline} be provided for FAA Second-level engineering maintenance.

## Technical data

### Manuals and Instructions

#### The AFSM system Operator Manuals [must]{.underline} be prepared and submitted to the FAA.

#### The AFSM system Operator Manuals [must]{.underline} be prepared IAW 6000.15 General maintenance Handbook for NAS Facilities, or industry standard that is acceptable to the FAA. 

#### The AFSM system Maintenance Manuals [must]{.underline} be prepared and submitted to the FAA.

#### The AFSM system Maintenance Manuals [must]{.underline} be prepared IAW FAA Order 6000.15 General Maintenance Handbook for NAS Facilities, or industry standard that is acceptable to the FAA. 

### Drawings and Specifications

#### The AFSM system technical data [must]{.underline} be provided to the FAA IAW FAA-STD-002F Standard Engineering Drawing Preparation and Support or industry standard that is acceptable to the FAA. 

#### The AFSM system drawings [must]{.underline} be provided to the FAA IAW FAA-STD-002 Standard Engineering Drawing Preparation and Support or industry standard that is acceptable to the FAA. 

### Development Software

#### The AFSM system developmental software [must]{.underline} be fully documented and commented IAW the current version of FAA-STD-026, Software Development for the National Airspace System or industry standard that is acceptable to the FAA.

## Training 

### The AFSM system Hardware Maintenance Training [must]{.underline} be developed and submitted to the FAA IAW FAA-STD-028, Contract Training Program or industry standard that is acceptable to the FAA. 

###  Instructional materials [must]{.underline} be created in the development phase based on the course design guide and the related Data Item Description (DID) delineated in FAA-STD-028 or industry standard that is acceptable to the FAA. 

### The AFSM system Air Traffic Control Specialist Training [must]{.underline} be developed and submitted to the FAA IAW FAA-STD-028, or industry standard that is acceptable to the FAA.

## Packaging, Handling, Storage and Transportation

### The AFSM system packaging, handling, storage and transportation [must]{.underline} be IAW American Society for Testing and Materials (ASTM)-D3951, Standard Practice for Commercial Packaging.

[\[This Page Intentionally Left Blank\]]{.smallcaps}

# Test and Evaluation

## Critical Operational Issues (COIs)

The operational requirements developed for the Alaska Flight Service
Modernization system [must]{.underline} be traceable to the identified
COIs. COIs are key operational effectiveness or suitability issues
expressed in the form of questions that reflect controversies and
uncertainties about system capabilities, practicability, environmental
effects, etc. COIs are examined in tests during the FAA Acquisition
Management System (AMS) solution implementation phase to determine a
product's capability to perform its mission. The following COIs have
been identified for the AFSM system.

### COI-1: Can the users (operators and maintainers) provide the necessary services and functions to provide safe and efficient operation of the NAS with equal to or better than the effectiveness of the current system?

### COI-2: Does the system interface and operate with existing equipment and systems (e.g. NWS, other ATC facilities and input systems) without degradation of system effectiveness?

### COI-3: Does failure of the system adversely impact any NAS system, subsystem, network or facility?

### COI-4: Does the system have the reliability, maintainability and availability to provide for essential services equivalent to the current system or consistent with approved changes?

### COI-5: Does the system design and site adaptation procedure allow the system to be transitioned and adapted safely and expeditiously for all sites to which it will be deployed?

### COI-6: Does the system provide the necessary hardware and software maintenance and necessary logistics services that allow Flight Services to operate without disruption?

### COI-7: Does the system and infrastructure provide the necessary redundancy so that no single failure of equipment, system, installation or facility causes loss of service? 

### COI-8: Does the system comply with the security requirements specified in FAA Order 1370.82, Information Systems Security Program.

## Test and Evaluation requirements

The AFSM system Test and Evaluation (T&E) [must]{.underline} be
conducted IAW FAA AMS T&E Policy and Guidance.

### Solution Implementation (SI) Test Requirements

The AFSM Solution Implementation testing [must]{.underline} address six
main components.

#### SI Developmental Test (DT) [must]{.underline} be conducted to demonstrate that all technical and performance requirements for the AFSM system and subsystem hardware and software specified in the contract have been met. DT [must]{.underline} be performed by the contractor and witnessed by the FAA at the contractor and/or William J Hughes Technical Center locations.

#### SI Operational Test (OT) [must]{.underline} be conducted to verify that the AFSM system is operationally effective and operationally suitable for use in the NAS and that the NAS infrastructure is ready to accept the system. OT [must]{.underline} be conducted at the William J. Hughes Technical Center under the direction of the FAA and [must]{.underline} be followed up by operational key site (or key sites) testing at a designated NAS facility.

#### SI Production Acceptance Test (PAT) [must]{.underline} be conducted on each AFSM system before it leaves the factory. The PAT [must]{.underline} verify that the vendor is producing units that meet the AFSM requirements and is defect free before shipment.

#### SI Site Acceptance Test (SAT) [must]{.underline} be conducted to verify that the AFSM system is installed and functioning properly and integrates with other site equipment, all in preparation for site acceptance. SAT [must]{.underline} be conducted by the vendor with oversight by the FAA.

#### SI Field Familiarization (FF) [must]{.underline} be conducted to verify readiness for integration of the AFSM system into the NAS. Field Familiarization is conducted by Air Traffic and Technical Operations field personnel at each site to which the AFSM system is delivered.

#### SI Independent Operational Test & Evaluation (IOT&E) [must]{.underline} be a full system-level evaluation conducted in an operational environment to confirm the operational readiness of the AFSM system to be part of the NAS. The FAA Chief Operating Officer, through the Vice President of Safety Services, designates investment programs on which to conduct IOT&E. The decision to designate a program for IOT&E is based on such factors as complexity, operational criticality, lifecycle cost, interoperability, and risk [must]{.underline} be defined during investment analysis.

### Test Transition Requirements

Joint Acceptance Inspection (JAI) [must]{.underline} be conducted IAW
FAA Order 6010.7, Joint Acceptance Inspection. It is intended that the
JAI will result in an Operational Readiness Date (ORD), commissioning of
the AFSM system and transition to the In Service Management life cycle
phase.

### In service Management (ISM) Test Requirements

The AFSM In Service Management testing [must]{.underline} address four
main components.

#### ISM Development Test [must]{.underline} be conducted to verify that modifications to the AFSM system meet specified requirements and interrelated functions are not adversely affected. Development Test [must]{.underline} be performed by the contractor and witnessed by the FAA at the contractor and/or William J Hughes Technical Center locations.

#### ISM System Test [must]{.underline} be conducted to ensure the modifications to the AFSM system are ready for use in the NAS. System Test [must]{.underline} be conducted at the William J. Hughes Technical Center under the direction of the FAA.

#### ISM Key Site Test [must]{.underline} be conducted to verify the modifications to the AFSM system meet the user needs. Key Site Test [must]{.underline} be conducted at an operational NAS facility.

#### ISM Field Familiarization [must]{.underline} be performed to validate the performance of the AFSM system prior to operational use.  Field Familiarization is conducted by Air Traffic and Technical Operations field personnel at each site to which the AFSM system modification is delivered.

[]{.mark}

[(This Page Intentionally Left Blank)]{.smallcaps}

# Implementation and Transition

## Site Surveys and Planning

### Site Surveys [must]{.underline} be conducted prior to equipment deployment.

### The implementation strategy [must]{.underline} cover all activities necessary to prepare the site, and deliver, install, integrate and commission the system into NAS operations.

## Transition Plan

These activities include installation, integration and equipment
acceptance testing with external facilities.

### A NAS Transition Plan [must]{.underline} be developed IAW the FAA's Implementation Planning Guidelines.

## Dual Operations

### If dual operations are necessary, then both the legacy and the AFSM system [must]{.underline} operate until JAI is signed.

Note: The determination for necessity to conduct dual operations will be
made by the FAA on a site-by-site basis.

## Air Traffic Operations

### The Installation and Checkout (INCO) of the AFSM system [must]{.underline} be performed without disrupting existing services.

## Site Preparation Authority

### Site preparation for the NAS [must]{.underline} be coordinated and overseen by the FAA.

## Installation and Checkout (INCO)

### The AFSM system INCO [must]{.underline} be performed by the installation contractor.

### The AFSM system INCO [must]{.underline} be coordinated between the installation contractor and the FAA.

### The AFSM system INCO [must]{.underline} be overseen by the FAA.

## Field Familiarization

### Technical Operations and Flight Service personnel will use the AFSM system in an operational environment to become familiar with the system operations and maintenance.

## Power Compatibility

### The AFSM system electrical equipment [must]{.underline} be tested for power compatibility prior to connection to FAA critical electrical power panels.

## Site Authority

### Local Air Traffic and Technical Operations personnel [must]{.underline} have consent authority over site-specific NAS integration.

# Quality Assurance

## A Quality Assurance (QA) Program [must]{.underline} be established and implemented IAW FAA Order 7210.56, Air Traffic Quality Assurance and Industry Best Practices.

[(This Page Intentionally Left Blank)]{.smallcaps}

# Configuration Management

## The AFSM system Configuration Management (CM) must be IAW FAA Order 1800.66, NAS Configuration Management.

[(This Page Intentionally Left Blank)]{.smallcaps}

# In-Service Management

## The NAS AFSM system In-Service Management (ISM) must be managed IAW FAA Order 6000.30, National Airspace System Maintenance Policy**[.]{.smallcaps}**

[(This Page Intentionally Left Blank)]{.smallcaps}

# System Safety Management

## The AFSM system must manage System Safety Management (SSM) IAW FAA Order 8040.4, Safety Risk Management (SRM), the FAA Safety Management System (SMS) Manual, the FAA System Safety Handbook (SSH), and applicable sections of FAA Order 1800.66, NAS Configuration Management.

[(This Page Intentionally Left Blank)]{.smallcaps}

# Appendix 1: Mission Need Correlation Matrix {#appendix-1-mission-need-correlation-matrix .Appendix-Style}

T B D

[(This Page Intentionally Left Blank)]{.smallcaps}

# Appendix 2: Acronyms {#appendix-2-acronyms .Appendix-Style}

The following acronyms with associated definitions were used in this
document.

**[Acronym Definition]{.smallcaps}**

AAWBS Alaska Aviation Weather Briefing System

ABAAS Architectural Barriers Act Accessibility Standard

ADA American's With Disabilities Act

ADS-B Automated Dependent Surveillance - Broadcast

ADTN Administrative Data Transmission Network

AFSAS Alaska Flight Service Automated System

AFSS Automated Flight Service Stations

AISR Aeronautical Information System Replacement

AOS NAS Operational Systems Field Support Service

ARTCC Air Route Traffic Control Center

AMS Acquisition Management System

A/N Alphanumeric

ANICS Alaskan NAS Interfacility Communication System

ANSI American National Standards Institute

ASHRAE American Society of Heating, Refrigerating, and Air-Conditioning
Engineers

ASP Acquisition Strategy Plan

ATC Air Traffic Control

ATCS Air Traffic Control Specialist (also referred to as a Flight
Service Specialist (FSS))

ATCSCC Air Traffic Control System Command Center

ATIS Automated Terminal Information Service

ATO Air Traffic Organization

ATOP Advanced Technologies and Procedures

ATS Air Traffic Service

ATSM American Society for Testing and Materials

ATTV Automated Text to Voice

AWP Aviation Weather Processor

BIT Built-in-test

BWM / FIRMNET Bandwidth Manager / FAA IP Router Network

CAI Contract Acceptance Inspection

CAM Camera

CBA Cost Benefit Analysis

CERAP Combined Center Radar Approach Control

CHI Computer-Human Interface

CIT Capital Investment Team

CM Configuration Management

COI Critical Operational Issue

CONUS Continental United States

COTS Commercial Off-The-Shelf

CPU Central Processing Unit

CRS Contractor Repair Service

CWA Center Weather Advisory

DAWN Digital Aviation Weather Network

DID Data Item Description

DR Discrepancy Report

DR&A Data Reduction and Analysis

DoD Department of Defense

DT Development Test

E-Mail Electronic messaging

EOR End of Repair

FAA Federal Aviation Administration

FAT Factory Acceptance Test(ing)

FCA Functional Configuration Audit

FEMA Federal Emergency Management Administration

FF Field Familiarization

FQT Functional Qualification Test(ing)

FTE Full Time Equivalent

FSS Flight Service Specialist

GA Government Acceptance

GFE Government Furnished Equipment

GFI Government Furnished Information

GFP Government Furnished Property

HF Human Factors

HWCI Hardware Configuration Item

I&I Installation and Integration

IBR Integrated Baseline Review

IOC Initial Operating Capability

ISD In-Service Decision

ISP Implementation Strategy and Planning

ITDP Integration and Test Development Plan

ITT Integrated Test Team

JRC Joint Resources Council

LRU Line Replaceable Unit

MOE Measure of Effectiveness

MOP Measure of Performance

MOS Measure of Suitability

NAATS National Association of Air Traffic Specialists

NAS National Airspace System

NATCA National Air Traffic Controllers Association

NCP NAS Change Proposal

NDI Non-Developmental Item

OCD Operational Capability Demonstration

OCT Operational Capability Test

OMB Office of Management and Budget

ORD Operational Readiness Demonstration

OT Operational Test(ing)

PASS Professional Airways System Specialists

PAT Production Acceptance Test

PCA Physical Configuration Audit

PTR Program Trouble Report

QA Quality Assurance

QRO Quality Reliability Officer

RD Requirements Document

RFO Request for Offer

RMA Reliability, Maintainability, and Availability

SAT Site Acceptance Test

SCAP Security Certification and Authorization Package

SEM System Engineering Manual

SIR Screening Information Request

SME Subject Matter Expert

SOW Statement of Work

SSM System Safety Management

T&E Test and Evaluation

TIM Technical Interchange Meeting

TRR Test Readiness Review

TWG Test Working Group

V&V Verification and Validation

VRTM Verification Requirements Traceability Matrix

WBS Work Breakdown Structure

WJHTC William J. Hughes Technical Center

[(This Page Intentionally Left Blank)]{.smallcaps}

# Appendix 3: Reference documents {#appendix-3-reference-documents .Appendix-Style}

Appendix 3 identifies documents which were referenced or used as
guidelines in the development of the AFSM system Requirements document.

**Federal Regulations**

-   29 Code of Federal Regulations (CFR Title 29, Part 1910),

```{=html}
<!-- -->
```
-   29 CFR 1910.1000, Air Contaminants;

-   40 CFR 260 to 40 CFR 700 to 40 CFR 766

-   40 CFR 260, 49 CFR Subchapter C, 40 CFR 260, 40 CFR 700 to 766.

**FAA Handbooks**

-   FAA-G-2100 Handbook, Electronic Equipment, General Requirements
    Application Handbook

**FAA Standards**

-   FAA-STD-002F Standard Engineering Drawing Preparation and Support or
    industry standard that is acceptable to the FAA

-   FAA-STD-018, Computer Software Quality Program Requirements

-   FAA-Standard-019, Lightning Protection, Grounding, Bonding and
    Shielding for Facilities;

-   FAA-Standard-020, Transient Protection Grounding, Bonding, and
    Shielding Requirements for Equipment;

-   FAA-STD-025, Preparation of Interface Documentation.

-   FAA-STD-026, Software Development for the National Airspace System
    or industry standard that is acceptable to the FAA.

-   FAA-STD-028C, Contract Training Program or industry standard that is
    acceptable to the FAA.

**FAA Orders**

-   FAA Order 1050.10C, Prevention, Control and Abatement of
    Environmental Pollution at FAA Facilities

-   FAA Order 1050.14, Polychlorinated Biphenyls (PCBs) in the National
    Airspace Part 82 Protection of Stratospheric Ozone

-   FAA Order 1050.19B, Environmental Due Diligence Audits in the
    Conduct of FAA Real Property Transactions

-   FAA Order 1050.20, Airway Facilities Asbestos Control

-   FAA Order 1053.1A, Energy and Water Management Program for FAA
    Buildings and Facilities

-   FAA Order 1100.157A. National Systems Engineering Divisions
    Maintenance

-   FAA Order 1200.22, NAS Data and Interface Equipment Used by Outside
    Interest

-   FAA Order 1370.82, Information System Security Program

-   FAA Order 1370.83, Internet Access Points

-   FAA Order 1370.84, Internet Services

-   FAA Order 1375.1, Data Management

-   FAA Order 1600.1, Personnel Security Program.

-   FAA Order 1600.6, Facility Security Policy

-   FAA Order 1600.69, FAA Facility Security Management Program.

-   FAA Order 1600.72, Contractor and Industrial Security Program

-   FAA Order 1800.66, NAS Configuration Management

-   FAA Order 4420.4, Space Acquisition

-   FAA Order 4800.2, Utilization and Disposal of Excess and Surplus
    Personal Property

-   FAA Order 6000.30, Policy for Maintenance of the NAS

-   FAA Order 6000.30, National Airspace System Maintenance Policy

-   FAA Order 6000.15 General Maintenance Handbook for NAS Facilities

-   FAA Order 6010.7, Joint Acceptance Inspection

-   FAA Order 7110.10, Flight Services

-   FAA Order 7210.56, Air Traffic Quality Assurance and Industry Best
    Practices

-   FAA Order 7930.2 Notices To Airmen (NOTAM)

-   FAA Order 8040.4, Safety Risk Management

-   FAA Order 9550.8, FAA Human Factors Policy

**Human Factors**

-   Human Factors Design Standard (HFDS) For Acquisition of
    Commercial-Off-The-Shelf, Non-Developmental, and Developmental
    Systems;

```{=html}
<!-- -->
```
-   HFDS, Chapter 2.2 "Simplicity"

-   HFDS, Chapter 3 "Automation"

-   HFDS, Section 3.1.10 "Avoid Increasing Demands for Cognitive
    Resources"

-   HFDS, Section 3.1.11 "Avoid Extreme Workload Levels"

-   HFDS, Section 3.1.24 "Make Systems Easy to Learn"

-   HFDS, Section 3.2.3 "Consider Effects on Coordination"

-   HFDS Section 3.10 "Training"

-   HFDS, Chapter 8 "Computer Human Interface"

-   HFDS Section 10, "Workstation and Workplace Design"

-   HFDS Section 14, "Anthropometry and Biomechanics"

**Military Standards**

-   MIL-HDBK-46855A, Human Engineering (HE) Program Process and
    Procedures, Section 4 "Program Tasks"

-   MIL-HDBK-46855A, Human Engineering (HE) Program Process and
    Procedures, Section 7, Program "HE Procedures for Contractors".

-   MIL-HDBK-46855A, Human Engineering (HE) Program Process and
    Procedures Section 8 "HE Methods and Tools"

**Other FAA Documents**

-   FAA Advisory Circular No. 150/5370-2, Operational Safety on Airports
    during Construction

-   FAA Information System Security Architecture Version 6

-   FAA Safety Management System (SMS) Manual

-   FAA System Safety Handbook (SSH)

**Miscellaneous**

-   44 United States Code (U.S.C.), Federal Information System Security
    Act.

-   American Society of Heating, Refrigerating, and Air Conditioning
    Engineers (ASHRAE)

-   American Society for Testing and Materials (ASTM)-D3951, Standard
    Practice for Commercial Packaging

-   Federal Emergency Management Administration (FEMA) Handbook 224

-   International Communication Satellite Systems Conference (ICSSC)
    RP-4

-   National Fire Protection Association (NFPA) 70 Standard

-   NFPA 70 Standard, National Electrical Code®; and Institute of
    Electrical and Electronics Engineers Standard 1100-1999, Recommended
    Practice for Powering and Grounding for Sensitive Electric
    Equipment.

-   NFPA 70 Standard, National Electrical Code®, and FAA-C-1217,
    Electrical Work, Interior

-   NFPA 70 National Electrical Code®

-   Standard/American National Standards Institute (ANSI) standards
    which include ANSI/ASHRAE 62-2001 - Ventilation for Acceptable
    Indoor Air Quality

**OSHA**

-   Occupational Safety and Health Administration (OSHA) mandates and
    other safety and health regulations and standards, as specified in
    the FAA HFDS Section 12, Personnel Safety

-   Occupational Safety and Health Administration (OSHA) mandates and
    other safety and health regulations and standards, as specified in
    Section 13, "Environment"

**Weather**

-   WMO-386: WORLD METEOROLOGICAL ORGANIZATION (WMO) - Manual on the
    Global Telecommunication System

# Appendix 4: Glossary of Terms and Definitions {#appendix-4-glossary-of-terms-and-definitions .Appendix-Style}

This glossary provides definitions of the terms used in the AFSM system
Requirements document.

AUTOMATIC FLIGHT PLAN TRACKING -- {Alaska unique -- definition TBD}

BROADCAST− Transmission of information for which an acknowledgement is
not expected.

BROADCAST \[ICAO\]− A transmission of information relating to air
navigation that is not addressed to a specific station or stations.

CONTACT LIST -- {TBD}

Delta Briefings -- a record of flight history, weather briefed, NOTAMs
provided, etc., which follows flights through the system. The system
alerts ATCS of new or changed information.

GRAPHICAL NOTAM -- {TBD}

STEREO ROUTE− A routinely used route of flight established by users and
ARTCCs identified by a coded name; e.g., ALPHA 2. These routes minimize
flight plan handling and communications.

STEREO FLIGHT PLAN -- A flight plan (civil aircraft or military
aircraft) using a stereo route.

TELEPHONE INFORMATION BRIEFING SERVICE− A continuous telephone recording
of meteorological and/or aeronautical information.

TRANSCRIBED WEATHER BROADCAST− A continuous recording of meteorological
and aeronautical information that is broadcast on L/MF and VOR
facilities for pilots.

VIEW SEQUENCE -- A view sequence is a capability providing display of a
combination of static text and/or dynamic weather and aeronautical data.

[(This Page Intentionally Left Blank)]{.smallcaps}

# Appendix 5: AFSM Voice Switch Requirements  {#appendix-5-afsm-voice-switch-requirements .Appendix-Style}

Note: This appendix identifies the AFSM Voice Switch Requirements.

[(This Page Intentionally Left Blank)]{.smallcaps}

# Appendix 6: AFSM Telecommunications {#appendix-6-afsm-telecommunications .Appendix-Style}

Note: AFSM system telecommunications will be government furnished.

\[This Page Intentionally Left Blank\]

# Appendix 7: Requirements Traceability Matrix (RTM) {#appendix-7-requirements-traceability-matrix-rtm .Appendix-Style}

This appendix contains the AFSM system Requirements Traceability Matrix.

**[The RTM currently includes only Section 3.]{.underline}**

+----------+---------------------------------------------------+------+
| **Req.   | **Requirement Definition**                        |      |
| ID**     |                                                   |      |
+==========+===================================================+======+
| 3.1      | **Operational and Functional Requirements**       |      |
+----------+---------------------------------------------------+------+
| 3.1.1    | Weather Briefing                                  |      |
+----------+---------------------------------------------------+------+
| 3.1.1.1  | The AFSM system [must]{.underline} perform        |      |
|          | weather briefing functions in accordance with FAA |      |
|          | Orders.                                           |      |
+----------+---------------------------------------------------+------+
| 3.1.1.2  | The AFSM system [must]{.underline} receive a      |      |
|          | weather briefing.                                 |      |
+----------+---------------------------------------------------+------+
| 3        | The AFSM system [must]{.underline} receive        |      |
| .1.1.2.1 | alphanumeric (A/N) weather data for use in        |      |
|          | providing a weather briefing.                     |      |
+----------+---------------------------------------------------+------+
| 3        | The AFSM system [must]{.underline} receive        |      |
| .1.1.2.2 | weather graphics for use in providing a weather   |      |
|          | briefing.                                         |      |
+----------+---------------------------------------------------+------+
| 3        | The AFSM system [must]{.underline} receive        |      |
| .1.1.2.3 | aeronautical information for use in providing a   |      |
|          | weather briefing.                                 |      |
+----------+---------------------------------------------------+------+
| 3        | The AFSM system [must]{.underline} receive        |      |
| .1.1.2.4 | concurrently alphanumeric (A/N) weather data,     |      |
|          | weather graphics, and other aeronautical          |      |
|          | information for use in providing a weather        |      |
|          | briefing.                                         |      |
+----------+---------------------------------------------------+------+
| 3.1.1.3  | The AFSM system [must]{.underline} store a        |      |
|          | weather briefing.                                 |      |
+----------+---------------------------------------------------+------+
| 3        | The AFSM system [must]{.underline} store          |      |
| .1.1.3.1 | alphanumeric (A/N) weather data for use in        |      |
|          | providing a weather briefing.                     |      |
+----------+---------------------------------------------------+------+
| 3        | The AFSM system [must]{.underline} store weather  |      |
| .1.1.3.2 | graphics for use in providing a weather briefing. |      |
+----------+---------------------------------------------------+------+
| 3        | The AFSM system [must]{.underline} store          |      |
| .1.1.3.3 | aeronautical information for use in providing a   |      |
|          | weather briefing.                                 |      |
+----------+---------------------------------------------------+------+
| 3        | The AFSM system [must]{.underline} store          |      |
| .1.1.3.4 | simultaneously alphanumeric (A/N) weather data,   |      |
|          | weather graphics, and other aeronautical          |      |
|          | information for use in providing a weather        |      |
|          | briefing.                                         |      |
+----------+---------------------------------------------------+------+
| 3.1.1.4  | The AFSM system [must]{.underline} process a      |      |
|          | weather briefing.                                 |      |
+----------+---------------------------------------------------+------+
| 3        | The AFSM system [must]{.underline} process        |      |
| .1.1.4.1 | alphanumeric (A/N) weather data for use in        |      |
|          | providing a weather briefing.                     |      |
+----------+---------------------------------------------------+------+
| 3        | The AFSM system [must]{.underline} process        |      |
| .1.1.4.2 | weather graphics for use in providing a weather   |      |
|          | briefing.                                         |      |
+----------+---------------------------------------------------+------+
| 3        | The AFSM system [must]{.underline} process        |      |
| .1.1.4.3 | aeronautical information for use in providing a   |      |
|          | weather briefing.                                 |      |
+----------+---------------------------------------------------+------+
| 3        | The AFSM system [must]{.underline} process        |      |
| .1.1.4.4 | simultaneously alphanumeric (A/N) weather data,   |      |
|          | weather graphics, and other aeronautical          |      |
|          | information for use in providing a weather        |      |
|          | briefing.                                         |      |
+----------+---------------------------------------------------+------+
| 3.1.1.5  | The AFSM system [must]{.underline} integrate      |      |
|          | alphanumeric (A/N) weather data, weather          |      |
|          | graphics, and aeronautical information for use in |      |
|          | providing a weather briefing.                     |      |
+----------+---------------------------------------------------+------+
| 3.1.1.6  | The AFSM system [must]{.underline} provide        |      |
|          | weather graphics and overlay capability for use   |      |
|          | in providing a weather briefing.                  |      |
+----------+---------------------------------------------------+------+
| 3.1.1.7  | The AFSM system [must]{.underline} provide        |      |
|          | weather briefings with site adaptable parameters. |      |
+----------+---------------------------------------------------+------+
| 3        | The AFSM system [must]{.underline} provide        |      |
| .1.1.7.1 | weather briefings with site adaptable parameters  |      |
|          | for Alaska.                                       |      |
+----------+---------------------------------------------------+------+
| 3        | The AFSM system [must]{.underline} provide        |      |
| .1.1.7.2 | weather briefings with site adaptable parameters  |      |
|          | for Canada.                                       |      |
+----------+---------------------------------------------------+------+
| 3        | The AFSM system [must]{.underline} provide        |      |
| .1.1.7.3 | weather briefings with site adaptable parameters  |      |
|          | for the continental United States (CONUS).        |      |
+----------+---------------------------------------------------+------+
| 3        | The AFSM system [must]{.underline} provide        |      |
| .1.1.7.4 | weather briefings with site adaptable parameters  |      |
|          | for Hawaii.                                       |      |
+----------+---------------------------------------------------+------+
| 3        | The AFSM system [must]{.underline} provide        |      |
| .1.1.7.5 | weather briefings with site adaptable parameters  |      |
|          | for Mexico.                                       |      |
+----------+---------------------------------------------------+------+
| 3        | The AFSM system [must]{.underline} provide        |      |
| .1.1.7.6 | weather briefings with site adaptable parameters  |      |
|          | for Europe.                                       |      |
+----------+---------------------------------------------------+------+
| 3        | The AFSM system [must]{.underline} provide        |      |
| .1.1.7.7 | weather briefings with site adaptable parameters  |      |
|          | for Russia.                                       |      |
+----------+---------------------------------------------------+------+
| 3        | The AFSM system [must]{.underline} provide        |      |
| .1.1.7.8 | weather briefings with site adaptable parameters  |      |
|          | for Japan.                                        |      |
+----------+---------------------------------------------------+------+
| 3        | The AFSM system [must]{.underline} provide        |      |
| .1.1.7.9 | weather briefings with site adaptable parameters  |      |
|          | for China.                                        |      |
+----------+---------------------------------------------------+------+
| 3.       | The AFSM system [must]{.underline} provide        |      |
| 1.1.7.10 | weather briefings with site adaptable parameters  |      |
|          | for Korea.                                        |      |
+----------+---------------------------------------------------+------+
| 3.1.1.8  | The AFSM system [must]{.underline} display        |      |
|          | weather briefing products.                        |      |
+----------+---------------------------------------------------+------+
| 3        | The AFSM system [must]{.underline} display A/N    |      |
| .1.1.8.1 | weather messages as a weather briefing product.   |      |
+----------+---------------------------------------------------+------+
| 3        | The AFSM system [must]{.underline} display        |      |
| .1.1.8.2 | weather graphics as a weather briefing product.   |      |
+----------+---------------------------------------------------+------+
| 3        | The AFSM system [must]{.underline} display        |      |
| .1.1.8.3 | weather camera images as a weather briefing       |      |
|          | product.                                          |      |
+----------+---------------------------------------------------+------+
| 3        | The AFSM system [must]{.underline} display NOTAMs |      |
| .1.1.8.4 | as a weather briefing product.                    |      |
+----------+---------------------------------------------------+------+
| 3        | The AFSM system [must]{.underline} display Air    |      |
| .1.1.8.5 | Traffic Control Center (ATCSCC) messages as a     |      |
|          | weather briefing product.                         |      |
+----------+---------------------------------------------------+------+
| 3        | The AFSM system [must]{.underline} display        |      |
| .1.1.8.6 | Special Use Airspace (SUA) data as a weather      |      |
|          | briefing product.                                 |      |
+----------+---------------------------------------------------+------+
| 3        | The AFSM system [must]{.underline} display Law    |      |
| .1.1.8.7 | Enforcement (LE) alert messages as a weather      |      |
|          | briefing product.                                 |      |
+----------+---------------------------------------------------+------+
| 3.1.1.9  | The AFSM system [must]{.underline} provide        |      |
|          | distance measuring on weather graphics.           |      |
+----------+---------------------------------------------------+------+
| 3.1.1.10 | The AFSM system [must]{.underline} provide        |      |
|          | weather briefings in accordance with FAA-Order    |      |
|          | 7110.10.                                          |      |
+----------+---------------------------------------------------+------+
| 3.       | The AFSM system [must]{.underline} provide        |      |
| 1.1.10.1 | Standard weather briefings in accordance with     |      |
|          | FAA-Order 7110.10.                                |      |
+----------+---------------------------------------------------+------+
| 3.       | The AFSM system [must]{.underline} provide        |      |
| 1.1.10.2 | Abbreviated weather briefings in accordance with  |      |
|          | FAA-Order 7110.10.                                |      |
+----------+---------------------------------------------------+------+
| 3.       | The AFSM system [must]{.underline} provide        |      |
| 1.1.10.3 | Outlook weather briefings in accordance with      |      |
|          | FAA-Order 7110.10.                                |      |
+----------+---------------------------------------------------+------+
| 3.1.1.11 | The AFSM system [must]{.underline} provide Route  |      |
|          | Orient formatted weather briefings.               |      |
+----------+---------------------------------------------------+------+
| 3.       | The AFSM system [must]{.underline} provide Route  |      |
| 1.1.11.1 | Orient formatted weather briefings that display   |      |
|          | A/N weather data.                                 |      |
+----------+---------------------------------------------------+------+
| 3.       | The AFSM system [must]{.underline} provide Route  |      |
| 1.1.11.2 | Orient formatted weather briefings that display   |      |
|          | weather graphics with geopolitical boundaries.    |      |
+----------+---------------------------------------------------+------+
| 3.       | The AFSM system [must]{.underline} provide Route  |      |
| 1.1.11.3 | Orient formatted weather briefings that display   |      |
|          | grid weather data.                                |      |
+----------+---------------------------------------------------+------+
| 3.1.1.12 | The AFSM system [must]{.underline} adapt, scale   |      |
|          | and stratify the route corridor of a weather      |      |
|          | briefing.                                         |      |
+----------+---------------------------------------------------+------+
| 3.1.1.13 | The AFSM system [must]{.underline} provide Local  |      |
|          | Area formatted weather briefings.                 |      |
+----------+---------------------------------------------------+------+
| 3.       | The AFSM system [must]{.underline} provide Local  |      |
| 1.1.13.1 | Area formatted weather briefings using            |      |
|          | alphanumeric messages.                            |      |
+----------+---------------------------------------------------+------+
| 3.       | The AFSM system [must]{.underline} provide Local  |      |
| 1.1.13.2 | Area formatted weather briefings using weather    |      |
|          | graphic products.                                 |      |
+----------+---------------------------------------------------+------+
| 3.       | The AFSM system [must]{.underline} provide Local  |      |
| 1.1.13.3 | Area formatted weather briefings using            |      |
|          | aeronautical data.                                |      |
+----------+---------------------------------------------------+------+
| 3.1.1.14 | The AFSM system [must]{.underline} provide        |      |
|          | Selected Location formatted weather briefings.    |      |
+----------+---------------------------------------------------+------+
| 3.       | The AFSM system [must]{.underline} provide        |      |
| 1.1.14.1 | Selected Location formatted weather briefings     |      |
|          | using alphanumeric messages.                      |      |
+----------+---------------------------------------------------+------+
| 3.       | The AFSM system [must]{.underline} provide        |      |
| 1.1.14.2 | Selected Location formatted weather briefings     |      |
|          | using weather graphic products.                   |      |
+----------+---------------------------------------------------+------+
| 3.       | The AFSM system [must]{.underline} provide        |      |
| 1.1.14.3 | Selected Location formatted weather briefings     |      |
|          | using aeronautical data.                          |      |
+----------+---------------------------------------------------+------+
| 3.1.1.15 | The AFSM system [must]{.underline} provide Trend  |      |
|          | Weather Information through the display and       |      |
|          | integration of alphanumeric and graphic products. |      |
+----------+---------------------------------------------------+------+
| 3.1.1.16 | The AFSM system [must]{.underline} allow customer |      |
|          | access to the same weather briefing products      |      |
|          | available to the flight service specialists       |      |
|          | through an FAA-approved web portal.               |      |
+----------+---------------------------------------------------+------+
| 3.1.1.17 | The AFSM system [must]{.underline} provide Delta  |      |
|          | weather briefings.                                |      |
+----------+---------------------------------------------------+------+
| 3.1.2    | Flight Plan Processing                            |      |
+----------+---------------------------------------------------+------+
| 3.1.2.1  | The AFSM system [must]{.underline} perform flight |      |
|          | planning functions IAW FAA Order 7110.10, Flight  |      |
|          | Services.                                         |      |
+----------+---------------------------------------------------+------+
| 3.1.2.2  | Process Domestic flight plans                     |      |
+----------+---------------------------------------------------+------+
| 3        | The AFSM system [must]{.underline} validate       |      |
| .1.2.2.1 | Domestic flight plans.                            |      |
+----------+---------------------------------------------------+------+
| 3        | The AFSM system [must]{.underline} file Domestic  |      |
| .1.2.2.2 | flight plans.                                     |      |
+----------+---------------------------------------------------+------+
| 3        | The AFSM system [must]{.underline} activate       |      |
| .1.2.2.3 | Domestic flight plans.                            |      |
+----------+---------------------------------------------------+------+
| 3        | The AFSM system [must]{.underline} amend Domestic |      |
| .1.2.2.4 | flight plans.                                     |      |
+----------+---------------------------------------------------+------+
| 3        | The AFSM system [must]{.underline} close Domestic |      |
| .1.2.2.5 | flight plans.                                     |      |
+----------+---------------------------------------------------+------+
| 3        | The AFSM system [must]{.underline} cancel         |      |
| .1.2.2.6 | Domestic flight plans.                            |      |
+----------+---------------------------------------------------+------+
| 3.1.2.3  | Process International Civil Aviation Organization |      |
|          | (ICAO) flight plans                               |      |
+----------+---------------------------------------------------+------+
| 3        | The AFSM system [must]{.underline} validate ICAO  |      |
| .1.2.3.1 | flight plans.                                     |      |
+----------+---------------------------------------------------+------+
| 3        | The AFSM system [must]{.underline} file ICAO      |      |
| .1.2.3.2 | flight plans.                                     |      |
+----------+---------------------------------------------------+------+
| 3        | The AFSM system [must]{.underline} activate ICAO  |      |
| .1.2.3.3 | flight plans.                                     |      |
+----------+---------------------------------------------------+------+
| 3        | The AFSM system [must]{.underline} amend ICAO     |      |
| .1.2.3.4 | flight plans.                                     |      |
+----------+---------------------------------------------------+------+
| 3        | The AFSM system [must]{.underline} close ICAO     |      |
| .1.2.3.5 | flight plans.                                     |      |
+----------+---------------------------------------------------+------+
| 3        | The AFSM system [must]{.underline} cancel ICAO    |      |
| .1.2.3.6 | flight plans.                                     |      |
+----------+---------------------------------------------------+------+
| 3.1.2.4  | Process Military flight plans                     |      |
+----------+---------------------------------------------------+------+
| 3        | The AFSM system [must]{.underline} validate       |      |
| .1.2.4.1 | Military flight plans.                            |      |
+----------+---------------------------------------------------+------+
| 3        | The AFSM system [must]{.underline} file Military  |      |
| .1.2.4.2 | flight plans.                                     |      |
+----------+---------------------------------------------------+------+
| 3        | The AFSM system [must]{.underline} activate       |      |
| .1.2.4.3 | Military flight plans.                            |      |
+----------+---------------------------------------------------+------+
| 3        | The AFSM system [must]{.underline} amend Military |      |
| .1.2.4.4 | flight plans.                                     |      |
+----------+---------------------------------------------------+------+
| 3        | The AFSM system [must]{.underline} close Military |      |
| .1.2.4.5 | flight plans.                                     |      |
+----------+---------------------------------------------------+------+
| 3        | ##### The AFSM system [must]{.underline}          |      |
| .1.2.4.6 |  cancel Military flight plans. {#the-afsm-system- |      |
|          | must-cancel-military-flight-plans.-1 .unnumbered} |      |
+----------+---------------------------------------------------+------+
| 3.1.2.5  | Process Stereo flight plans                       |      |
+----------+---------------------------------------------------+------+
| 3        | The AFSM system [must]{.underline} validate       |      |
| .1.2.5.1 | Stereo flight plans.                              |      |
+----------+---------------------------------------------------+------+
| 3        | The AFSM system [must]{.underline} file Stereo    |      |
| .1.2.5.2 | flight plans.                                     |      |
+----------+---------------------------------------------------+------+
| 3        | The AFSM system [must]{.underline} amend Stereo   |      |
| .1.2.5.3 | flight plans.                                     |      |
+----------+---------------------------------------------------+------+
| 3        | The AFSM system [must]{.underline} close Stereo   |      |
| .1.2.5.4 | flight plans.                                     |      |
+----------+---------------------------------------------------+------+
| 3        | The AFSM system [must]{.underline} cancel Stereo  |      |
| .1.2.5.5 | flight plans.                                     |      |
+----------+---------------------------------------------------+------+
| 3.1.2.6  | Process DVFR flight plans                         |      |
+----------+---------------------------------------------------+------+
| 3        | The AFSM system [must]{.underline} validate DVFR  |      |
| .1.2.6.1 | flight plans.                                     |      |
+----------+---------------------------------------------------+------+
| 3        | The AFSM system [must]{.underline} file DVFR      |      |
| .1.2.6.2 | flight plans.                                     |      |
+----------+---------------------------------------------------+------+
| 3        | The AFSM system [must]{.underline} activate DVFR  |      |
| .1.2.6.3 | flight plans.                                     |      |
+----------+---------------------------------------------------+------+
| 3        | The AFSM system [must]{.underline} amend DVFR     |      |
| .1.2.6.4 | flight plans.                                     |      |
+----------+---------------------------------------------------+------+
| 3        | The AFSM system [must]{.underline} close DVFR     |      |
| .1.2.6.5 | flight plans.                                     |      |
+----------+---------------------------------------------------+------+
| 3        | The AFSM system [must]{.underline} cancel DVFR    |      |
| .1.2.6.6 | flight plans.                                     |      |
+----------+---------------------------------------------------+------+
| 3.1.2.7  | Process Special VFR (SVFR) flight plans           |      |
+----------+---------------------------------------------------+------+
| 3        | The AFSM system [must]{.underline} validate SVFR  |      |
| .1.2.7.1 | flight plans.                                     |      |
+----------+---------------------------------------------------+------+
| 3        | The AFSM system [must]{.underline} file SVFR      |      |
| .1.2.7.2 | flight plans.                                     |      |
+----------+---------------------------------------------------+------+
| 3        | The AFSM system [must]{.underline} activate SVFR  |      |
| .1.2.7.3 | flight plans.                                     |      |
+----------+---------------------------------------------------+------+
| 3        | The AFSM system [must]{.underline} amend SVFR     |      |
| .1.2.7.4 | flight plans.                                     |      |
+----------+---------------------------------------------------+------+
| 3        | The AFSM system [must]{.underline} close SVFR     |      |
| .1.2.7.5 | flight plans.                                     |      |
+----------+---------------------------------------------------+------+
| 3        | The AFSM system [must]{.underline} cancel SVFR    |      |
| .1.2.7.6 | flight plans.                                     |      |
+----------+---------------------------------------------------+------+
| 3.1.2.8  | The AFSM system [must]{.underline} insert         |      |
|          | preferential routes for IFR flight plans.         |      |
+----------+---------------------------------------------------+------+
| 3.1.2.9  | The AFSM system [must]{.underline} insert         |      |
|          | aircraft and pilot data into flight plan data     |      |
|          | fields.                                           |      |
+----------+---------------------------------------------------+------+
| 3.1.2.10 | The AFSM system [must]{.underline} automatically  |      |
|          | address flight plans for transmission to          |      |
|          | appropriate facilities.                           |      |
+----------+---------------------------------------------------+------+
| 3.1.2.11 | The AFSM system [must]{.underline} allow manual   |      |
|          | override to flight plan data fields.              |      |
+----------+---------------------------------------------------+------+
| 3.1.2.12 | The AFSM system [must]{.underline} allow          |      |
|          | additions to flight plan data fields.             |      |
+----------+---------------------------------------------------+------+
| 3.1.2.13 | The AFSM system [must]{.underline} validate       |      |
|          | flight plan data fields for accuracy and format.  |      |
+----------+---------------------------------------------------+------+
| 3.1.2.14 | Process Aircraft Movement Messages                |      |
+----------+---------------------------------------------------+------+
| 3.       | The AFSM system [must]{.underline} format         |      |
| 1.2.14.1 | aircraft movement messages for transmission.      |      |
+----------+---------------------------------------------------+------+
| 3.       | The AFSM system [must]{.underline} validate       |      |
| 1.2.14.2 | aircraft movement messages for transmission.      |      |
+----------+---------------------------------------------------+------+
| 3.       | The AFSM system [must]{.underline} validate       |      |
| 1.2.14.3 | aircraft movement messages from external systems. |      |
+----------+---------------------------------------------------+------+
| 3.1.2.15 | Process Control Messages                          |      |
+----------+---------------------------------------------------+------+
| 3.       | The AFSM system [must]{.underline} format control |      |
| 1.2.15.1 | messages for transmission.                        |      |
+----------+---------------------------------------------------+------+
| 3.       | The AFSM system [must]{.underline} validate       |      |
| 1.2.15.2 | control messages for transmission.                |      |
+----------+---------------------------------------------------+------+
| 3.       | The AFSM system [must]{.underline} validate       |      |
| 1.2.15.3 | control messages from external systems.           |      |
+----------+---------------------------------------------------+------+
| 3.1.2.16 | The AFSM system [must]{.underline} convert ICAO   |      |
|          | flight plan data fields to domestic flight data   |      |
|          | format.                                           |      |
+----------+---------------------------------------------------+------+
| 3.1.2.17 | The AFSM system [must]{.underline} convert        |      |
|          | domestic flight plan data fields to ICAO flight   |      |
|          | data format.                                      |      |
+----------+---------------------------------------------------+------+
| 3.1.2.18 | The AFSM system [must]{.underline} display flight |      |
|          | plan information history at any position.         |      |
+----------+---------------------------------------------------+------+
| 3.1.2.19 | The AFSM system [must]{.underline} allow flight   |      |
|          | plan information history import into a flight     |      |
|          | plan mask.                                        |      |
+----------+---------------------------------------------------+------+
| 3.1.2.20 | Display Current Flight Plan                       |      |
+----------+---------------------------------------------------+------+
| 3.       | The AFSM system [must]{.underline} display        |      |
| 1.2.20.1 | current flight plan information by aircraft call  |      |
|          | sign.                                             |      |
+----------+---------------------------------------------------+------+
| 3.       | The AFSM system [must]{.underline} display        |      |
| 1.2.20.2 | current flight plan information by a wildcard     |      |
|          | search.                                           |      |
+----------+---------------------------------------------------+------+
| 3.1.2.21 | Display Flight Plan Lists                         |      |
+----------+---------------------------------------------------+------+
| 3.       | The AFSM system [must]{.underline} display        |      |
| 1.2.21.1 | prestored aircraft flight plan lists.             |      |
+----------+---------------------------------------------------+------+
| 3.       | The AFSM system [must]{.underline} display        |      |
| 1.2.21.2 | partial aircraft flight plan lists.               |      |
+----------+---------------------------------------------------+------+
| 3.       | The AFSM system [must]{.underline} display        |      |
| 1.2.21.3 | proposed aircraft flight plan lists.              |      |
+----------+---------------------------------------------------+------+
| 3.       | The AFSM system [must]{.underline} display        |      |
| 1.2.21.4 | suspense aircraft flight plan lists.              |      |
+----------+---------------------------------------------------+------+
| 3.       | The AFSM system [must]{.underline} display        |      |
| 1.2.21.5 | inbound aircraft flight plan lists.               |      |
+----------+---------------------------------------------------+------+
| 3.       | The AFSM system [must]{.underline} display        |      |
| 1.2.21.6 | timed-out, closed, and cancelled flight plans in  |      |
|          | a single list.                                    |      |
+----------+---------------------------------------------------+------+
| 3.1.2.22 | The AFSM system [must]{.underline} display data   |      |
|          | entry error messages.                             |      |
+----------+---------------------------------------------------+------+
| 3.1.2.23 | Process General Messages                          |      |
+----------+---------------------------------------------------+------+
| 3.       | The AFSM system [must]{.underline} format general |      |
| 1.2.23.1 | messages for transmission.                        |      |
+----------+---------------------------------------------------+------+
| 3.       | The AFSM system [must]{.underline} validate       |      |
| 1.2.23.2 | general messages for transmission.                |      |
+----------+---------------------------------------------------+------+
| 3.       | The AFSM system [must]{.underline} validate       |      |
| 1.2.23.3 | general messages from external systems.           |      |
+----------+---------------------------------------------------+------+
| 3.1.2.24 | The AFSM system [must]{.underline} display a      |      |
|          | traffic count database.                           |      |
+----------+---------------------------------------------------+------+
| 3.1.3    | In-Flight Processing                              |      |
+----------+---------------------------------------------------+------+
| 3.1.3.1  | The AFSM system [must]{.underline} maintain       |      |
|          | multiple In-Flight work queues.                   |      |
+----------+---------------------------------------------------+------+
| 3.1.3.2  | The AFSM system [must]{.underline} perform        |      |
|          | In-Flight functions in accordance with FAA Order  |      |
|          | 7110.10.                                          |      |
+----------+---------------------------------------------------+------+
| 3.1.3.3  | The AFSM system [must]{.underline} transfer       |      |
|          | retrieved flight plan information to In-Flight    |      |
|          | work queues.                                      |      |
+----------+---------------------------------------------------+------+
| 3.1.3.4  | The AFSM system [must]{.underline} provide a      |      |
|          | configurable electronic strip-bay.                |      |
+----------+---------------------------------------------------+------+
| 3.1.3.5  | The AFSM system [must]{.underline} provide a      |      |
|          | configurable airport advisory display that        |      |
|          | combines stored and real-time information.        |      |
+----------+---------------------------------------------------+------+
| 3        | The airport advisory display [must]{.underline}   |      |
| .1.3.5.1 | display stored and real-time weather information. |      |
+----------+---------------------------------------------------+------+
| 3        | The airport advisory display [must]{.underline}   |      |
| .1.3.5.2 | display stored and real-time aeronautical         |      |
|          | information.                                      |      |
+----------+---------------------------------------------------+------+
| 3        | The airport advisory display [must]{.underline}   |      |
| .1.3.5.3 | display electronic strip-bay information.         |      |
+----------+---------------------------------------------------+------+
| 3.1.3.6  | The AFSM system [must]{.underline} provide ADS-B  |      |
|          | flight path deviation alerting.                   |      |
+----------+---------------------------------------------------+------+
| 3.1.3.7  | The AFSM system [must]{.underline} display a      |      |
|          | contact list.                                     |      |
+----------+---------------------------------------------------+------+
| 3.1.4    | Search and Rescue                                 |      |
+----------+---------------------------------------------------+------+
| 3.1.4.1  | The AFSM system [must]{.underline} validate SAR   |      |
|          | messages on receipt.                              |      |
+----------+---------------------------------------------------+------+
| 3.1.4.2  | The AFSM system [must]{.underline} generate SAR   |      |
|          | alerts when SAR messages are received.            |      |
+----------+---------------------------------------------------+------+
| 3.1.4.3  | The AFSM system [must]{.underline} retrieve       |      |
|          | global SAR data.                                  |      |
+----------+---------------------------------------------------+------+
| 3.1.4.4  | Process SAR Messages                              |      |
+----------+---------------------------------------------------+------+
| 3        | The AFSM system [must]{.underline} allow for the  |      |
| .1.4.4.1 | entry of SAR messages.                            |      |
+----------+---------------------------------------------------+------+
| 3        | The AFSM system [must]{.underline} allow for the  |      |
| .1.4.4.2 | editing of SAR messages.                          |      |
+----------+---------------------------------------------------+------+
| 3        | The AFSM system [must]{.underline} allow for the  |      |
| .1.4.4.3 | transmission of SAR messages.                     |      |
+----------+---------------------------------------------------+------+
| 3        | The AFSM system [must]{.underline} format SAR     |      |
| .1.4.4.4 | messages for transmission.                        |      |
+----------+---------------------------------------------------+------+
| 3        | The AFSM system [must]{.underline} validate SAR   |      |
| .1.4.4.5 | messages for transmission.                        |      |
+----------+---------------------------------------------------+------+
| 3.1.4.5  | The AFSM system [must]{.underline} perform        |      |
|          | automatic flight plan tracking.                   |      |
+----------+---------------------------------------------------+------+
| 3.1.4.6  | The AFSM system [must]{.underline} generate an    |      |
|          | alert when an aircraft has reached a configurable |      |
|          | overdue state.                                    |      |
+----------+---------------------------------------------------+------+
| 3.1.5    | Data Management                                   |      |
+----------+---------------------------------------------------+------+
| 3.1.5.1  | The AFSM system [must]{.underline} process        |      |
|          | aeronautical data.                                |      |
+----------+---------------------------------------------------+------+
| 3.1.5.2  | The AFSM system [must]{.underline} process        |      |
|          | weather data.                                     |      |
+----------+---------------------------------------------------+------+
| 3.1.5.3  | The AFSM system [must]{.underline} maintain a     |      |
|          | database of pre-stored flight plans.              |      |
+----------+---------------------------------------------------+------+
| 3.1.5.4  | Alert queue(s) for improperly formatted messages  |      |
+----------+---------------------------------------------------+------+
| 3        | The AFSM system [must]{.underline} maintain alert |      |
| .1.5.4.1 | queue(s) for improperly formatted messages.       |      |
+----------+---------------------------------------------------+------+
| 3        | The AFSM system [must]{.underline} allow editing  |      |
| .1.5.4.2 | of improperly formatted messages from alert       |      |
|          | queue(s).                                         |      |
+----------+---------------------------------------------------+------+
| 3        | The AFSM system [must]{.underline} allow storing  |      |
| .1.5.4.3 | of properly formatted messages from alert         |      |
|          | queue(s).                                         |      |
+----------+---------------------------------------------------+------+
| 3.1.5.5  | The AFSM system [must]{.underline} maintain a     |      |
|          | database of flight plans.                         |      |
+----------+---------------------------------------------------+------+
| 3.1.5.6  | The AFSM system [must]{.underline} transmit       |      |
|          | flight related updates to aircraft equipped with  |      |
|          | data-link capable systems upon specialist         |      |
|          | approval.                                         |      |
+----------+---------------------------------------------------+------+
| 3.1.5.7  | The AFSM system [must]{.underline} automatically  |      |
|          | update Law Enforcement list(s) IAW FAA Order      |      |
|          | 7110.10.                                          |      |
+----------+---------------------------------------------------+------+
| 3.1.5.8  | The AFSM system [must]{.underline} maintain an    |      |
|          | A/N weather database.                             |      |
+----------+---------------------------------------------------+------+
| 3.1.5.9  | The AFSM system [must]{.underline} maintain a     |      |
|          | graphical weather database.                       |      |
+----------+---------------------------------------------------+------+
| 3.1.5.10 | The AFSM system [must]{.underline} maintain a     |      |
|          | NOTAM database.                                   |      |
+----------+---------------------------------------------------+------+
| 3.1.5.11 | The AFSM system [must]{.underline} allow the      |      |
|          | retrieval of flight plans by any flight plan      |      |
|          | field.                                            |      |
+----------+---------------------------------------------------+------+
| 3.1.5.12 | The AFSM system [must]{.underline} allow the      |      |
|          | editing of flight plans.                          |      |
+----------+---------------------------------------------------+------+
| 3.1.5.13 | The AFSM system [must]{.underline} allow the      |      |
|          | re-transmittal of flight plans upon completion of |      |
|          | editing.                                          |      |
+----------+---------------------------------------------------+------+
| 3.1.5.14 | The AFSM system [must]{.underline} maintain an    |      |
|          | active record of all completed flight data        |      |
|          | transactions for a configurable number of days.   |      |
+----------+---------------------------------------------------+------+
| 3.1.5.15 | The AFSM system [must]{.underline} update flight  |      |
|          | plan information received from external sources.  |      |
+----------+---------------------------------------------------+------+
| 3.1.5.16 | The AFSM system [must]{.underline} update flight  |      |
|          | plan information received from internal sources.  |      |
+----------+---------------------------------------------------+------+
| 3.1.5.17 | The AFSM system [must]{.underline} allow for      |      |
|          | internal messaging.                               |      |
+----------+---------------------------------------------------+------+
| 3.1.5.18 | The AFSM system [must]{.underline} transmit       |      |
|          | traffic count information directly into the FAA   |      |
|          | national database.                                |      |
+----------+---------------------------------------------------+------+
| 3.1.5.19 | The AFSM system [must]{.underline} allow the      |      |
|          | transmittal of data via e-mail link.              |      |
+----------+---------------------------------------------------+------+
| 3.1.5.20 | The AFSM system [must]{.underline} maintain a     |      |
|          | telephone database.                               |      |
+----------+---------------------------------------------------+------+
| 3.1.5.21 | Integrated Facsimile Server                       |      |
+----------+---------------------------------------------------+------+
| 3.       | The AFSM system [must]{.underline} allow for      |      |
| 1.5.21.1 | transmission of documents via an integrated fax   |      |
|          | server.                                           |      |
+----------+---------------------------------------------------+------+
| 3.       | The AFSM system [must]{.underline} allow for      |      |
| 1.5.21.2 | receipt of documents via an integrated fax        |      |
|          | server.                                           |      |
+----------+---------------------------------------------------+------+
| 3.1.5.22 | The AFSM system [must]{.underline} maintain a     |      |
|          | general message database.                         |      |
+----------+---------------------------------------------------+------+
| 3.1.5.23 | The AFSM system [must]{.underline} maintain a     |      |
|          | master flight plan database.                      |      |
+----------+---------------------------------------------------+------+
| 3.1.5.24 | The AFSM system [must]{.underline} maintain a     |      |
|          | radio contact database.                           |      |
+----------+---------------------------------------------------+------+
| 3.1.5.25 | The AFSM system [must]{.underline} maintain a     |      |
|          | traffic count database.                           |      |
+----------+---------------------------------------------------+------+
| 3.1.5.26 | The AFSM system [must]{.underline} maintain a     |      |
|          | view sequence database.                           |      |
+----------+---------------------------------------------------+------+
| 3.1.5.27 | The AFSM system [must]{.underline} maintain an    |      |
|          | aeronautical information database.                |      |
+----------+---------------------------------------------------+------+
| 3.1.5.28 | The AFSM system [must]{.underline} maintain an    |      |
|          | aircraft hexadecimal database for ADS-B equipped  |      |
|          | aircraft.                                         |      |
+----------+---------------------------------------------------+------+
| 3.1.5.29 | Maintain Alerts for Delayed Products              |      |
+----------+---------------------------------------------------+------+
| 3.       | The AFSM system [must]{.underline} maintain       |      |
| 1.5.29.1 | alerts for delayed A/N products.                  |      |
+----------+---------------------------------------------------+------+
| 3.       | The AFSM system [must]{.underline} maintain       |      |
| 1.5.29.2 | alerts for delayed graphical weather products.    |      |
+----------+---------------------------------------------------+------+
| 3.1.5.30 | Message Transmission Queues                       |      |
+----------+---------------------------------------------------+------+
| 3.       | The AFSM system [must]{.underline} monitor        |      |
| 1.5.30.1 | message transmission queue(s) for messages in     |      |
|          | queue for more than a configurable number of      |      |
|          | minutes.                                          |      |
+----------+---------------------------------------------------+------+
| 3.       | The AFSM system [must]{.underline} signal alert   |      |
| 1.5.30.2 | for messages in queue for more than a             |      |
|          | configurable number of minutes.                   |      |
+----------+---------------------------------------------------+------+
| 3.1.5.31 | Real-time System Updates                          |      |
+----------+---------------------------------------------------+------+
| 3.       | The AFSM system [must]{.underline} perform        |      |
| 1.5.31.1 | real-time 56-day updates.                         |      |
+----------+---------------------------------------------------+------+
| 3.       | The AFSM system [must]{.underline} perform        |      |
| 1.5.31.2 | real-time software releases.                      |      |
+----------+---------------------------------------------------+------+
| 3.1.6    | Weather Observation Processing                    |      |
+----------+---------------------------------------------------+------+
| 3.1.6.1  | Weather Observations Processing (includes METARs  |      |
|          | & SPECIs)                                         |      |
+----------+---------------------------------------------------+------+
| 3        | The AFSM system [must]{.underline} allow for the  |      |
| .1.6.1.1 | entry of multiple weather observations.           |      |
+----------+---------------------------------------------------+------+
| 3        | The AFSM system [must]{.underline} allow for the  |      |
| .1.6.1.2 | editing of multiple weather observations.         |      |
+----------+---------------------------------------------------+------+
| 3        | The AFSM system [must]{.underline} allow for the  |      |
| .1.6.1.3 | transmission of multiple weather observations.    |      |
+----------+---------------------------------------------------+------+
| 3        | The AFSM system [must]{.underline} format weather |      |
| .1.6.1.4 | observation messages for transmission IAW         |      |
|          | WMO-386.                                          |      |
+----------+---------------------------------------------------+------+
| 3        | The AFSM system [must]{.underline} validate       |      |
| .1.6.1.5 | weather observation messages for transmission IAW |      |
|          | WMO-386.                                          |      |
+----------+---------------------------------------------------+------+
| 3.1.6.2  | Pilot Reports Processing (includes PIREPs and     |      |
|          | urgent PIREPs)                                    |      |
+----------+---------------------------------------------------+------+
| 3        | The AFSM system [must]{.underline} allow for the  |      |
| .1.6.2.1 | entry of multiple pilot reports.                  |      |
+----------+---------------------------------------------------+------+
| 3        | The AFSM system [must]{.underline} allow for the  |      |
| .1.6.2.2 | editing of multiple pilot reports.                |      |
+----------+---------------------------------------------------+------+
| 3        | The AFSM system [must]{.underline} allow for the  |      |
| .1.6.2.3 | transmission of multiple pilot reports.           |      |
+----------+---------------------------------------------------+------+
| 3        | The AFSM system [must]{.underline} format pilot   |      |
| .1.6.2.4 | report messages for transmission IAW WMO-386.     |      |
+----------+---------------------------------------------------+------+
| 3        | The AFSM system [must]{.underline} validate pilot |      |
| .1.6.2.5 | report messages for transmission IAW WMO-386.     |      |
+----------+---------------------------------------------------+------+
| 3.1.6.3  | The AFSM system [must]{.underline} display data   |      |
|          | entry error messages.                             |      |
+----------+---------------------------------------------------+------+
| 3.1.6.4  | The AFSM system [must]{.underline} provide        |      |
|          | graphical weather observations.                   |      |
+----------+---------------------------------------------------+------+
| 3.1.7    | Notice-To-Airmen Processing                       |      |
+----------+---------------------------------------------------+------+
| 3.1.7.1  | NOTAMs Processing                                 |      |
+----------+---------------------------------------------------+------+
| 3        | The AFSM system [must]{.underline} allow for the  |      |
| .1.7.1.1 | entry of multiple NOTAMs.                         |      |
+----------+---------------------------------------------------+------+
| 3        | The AFSM system [must]{.underline} allow for the  |      |
| .1.7.1.2 | editing of multiple NOTAMs.                       |      |
+----------+---------------------------------------------------+------+
| 3        | The AFSM system [must]{.underline} allow for the  |      |
| .1.7.1.3 | transmission of multiple NOTAMs.                  |      |
+----------+---------------------------------------------------+------+
| 3        | The AFSM system [must]{.underline} allow for the  |      |
| .1.7.1.4 | entry of multiple NOTAM Cancellations.            |      |
+----------+---------------------------------------------------+------+
| 3        | The AFSM system [must]{.underline} allow for the  |      |
| .1.7.1.5 | editing of multiple NOTAM Cancellations.          |      |
+----------+---------------------------------------------------+------+
| 3        | The AFSM system [must]{.underline} allow for the  |      |
| .1.7.1.6 | transmission of multiple NOTAM Cancellations.     |      |
+----------+---------------------------------------------------+------+
| 3        | The AFSM system [must]{.underline} allow for the  |      |
| .1.7.1.7 | simultaneous entry of multiple NOTAMs and         |      |
|          | multiple NOTAM Cancellations.                     |      |
+----------+---------------------------------------------------+------+
| 3        | The AFSM system [must]{.underline} allow for the  |      |
| .1.7.1.8 | simultaneous editing of multiple NOTAMs and       |      |
|          | multiple NOTAM Cancellations.                     |      |
+----------+---------------------------------------------------+------+
| 3        | The AFSM system [must]{.underline} allow for the  |      |
| .1.7.1.9 | simultaneous transmission of multiple NOTAMs and  |      |
|          | multiple NOTAM Cancellations.                     |      |
+----------+---------------------------------------------------+------+
| 3.       | The AFSM system [must]{.underline} format NOTAM   |      |
| 1.7.1.10 | messages for transmission.                        |      |
+----------+---------------------------------------------------+------+
| 3.       | The AFSM system [must]{.underline} validate NOTAM |      |
| 1.7.1.11 | messages for transmission.                        |      |
+----------+---------------------------------------------------+------+
| 3.1.7.2  | The AFSM system [must]{.underline} display data   |      |
|          | entry error messages.                             |      |
+----------+---------------------------------------------------+------+
| 3.1.7.3  | The AFSM system [must]{.underline} maintain a     |      |
|          | NOTAM log IAW FAA Order 7930.2.                   |      |
+----------+---------------------------------------------------+------+
| 3.1.7.4  | The AFSM system [must]{.underline} provide for    |      |
|          | recording of NOTAM coordination activity.         |      |
+----------+---------------------------------------------------+------+
| 3.1.7.5  | The AFSM system [must]{.underline} provide        |      |
|          | templates/sample NOTAMs customized for individual |      |
|          | locations/situations to be maintained locally.    |      |
+----------+---------------------------------------------------+------+
| 3.1.7.6  | The AFSM system [must]{.underline} provide        |      |
|          | graphical NOTAMs.                                 |      |
+----------+---------------------------------------------------+------+
| 3.1.7.7  | The AFSM system [must]{.underline} record NOTAM   |      |
|          | entries into the traffic count database.          |      |
+----------+---------------------------------------------------+------+
| 3.1.8    | Training Support Processing                       |      |
+----------+---------------------------------------------------+------+
| 3.1.8.1  | Operational Training Modes                        |      |
+----------+---------------------------------------------------+------+
| 3        | The AFSM system [must]{.underline} provide a      |      |
| .1.8.1.1 | scripted (data sent in a timed sequence)          |      |
|          | operational training mode.                        |      |
+----------+---------------------------------------------------+------+
| 3        | The AFSM system [must]{.underline} provide an     |      |
| .1.8.1.2 | interactive (instructor generated message)        |      |
|          | operational training mode.                        |      |
+----------+---------------------------------------------------+------+
| 3.1.8.2  | Configuration Training Modes                      |      |
+----------+---------------------------------------------------+------+
| 3        | The AFSM system [must]{.underline} provide a      |      |
| .1.8.2.1 | scripted (data sent in a timed sequence)          |      |
|          | configuration training mode.                      |      |
+----------+---------------------------------------------------+------+
| 3        | The AFSM system [must]{.underline} provide an     |      |
| .1.8.2.2 | interactive (instructor generated message)        |      |
|          | configuration training mode.                      |      |
+----------+---------------------------------------------------+------+
| 3.1.8.3  | Capture Live Data for Training                    |      |
+----------+---------------------------------------------------+------+
| 3        | The AFSM system [must]{.underline} capture live   |      |
| .1.8.3.1 | alphanumeric weather data.                        |      |
+----------+---------------------------------------------------+------+
| 3        | The AFSM system [must]{.underline} capture live   |      |
| .1.8.3.2 | graphical weather data.                           |      |
+----------+---------------------------------------------------+------+
| 3.1.8.4  | Store Live Data for Training                      |      |
+----------+---------------------------------------------------+------+
| 3        | The AFSM system [must]{.underline} store live     |      |
| .1.8.4.1 | alphanumeric weather data.                        |      |
+----------+---------------------------------------------------+------+
| 3        | The AFSM system [must]{.underline} store live     |      |
| .1.8.4.2 | graphical weather data.                           |      |
+----------+---------------------------------------------------+------+
| 3.1.8.5  | Import of Weather Data                            |      |
+----------+---------------------------------------------------+------+
| 3        | The AFSM system [must]{.underline} allow import   |      |
| .1.8.5.1 | of the stored alphanumeric weather data to other  |      |
|          | AFSM systems.                                     |      |
+----------+---------------------------------------------------+------+
| 3        | The AFSM system [must]{.underline} allow import   |      |
| .1.8.5.2 | of the stored graphical weather data to other     |      |
|          | AFSM systems.                                     |      |
+----------+---------------------------------------------------+------+
| 3.1.8.6  | Export of Weather Data                            |      |
+----------+---------------------------------------------------+------+
| 3        | The AFSM system [must]{.underline} allow export   |      |
| .1.8.6.1 | of the stored alphanumeric weather data to other  |      |
|          | AFSM systems.                                     |      |
+----------+---------------------------------------------------+------+
| 3        | The AFSM system [must]{.underline} allow export   |      |
| .1.8.6.2 | of the stored graphical weather data to other     |      |
|          | AFSM systems.                                     |      |
+----------+---------------------------------------------------+------+
| 3.1.8.7  | The AFSM system [must]{.underline} allow edit and |      |
|          | "replay" of the captured and stored weather data  |      |
|          | as specific weather scenarios in the operational  |      |
|          | scripted or interactive modes on selected         |      |
|          | terminals without operational impact.             |      |
+----------+---------------------------------------------------+------+
| 3        | The AFSM system [must]{.underline} allow for a    |      |
| .1.8.7.1 | "start" command within the scenario to begin      |      |
|          | replay.                                           |      |
+----------+---------------------------------------------------+------+
| 3        | The AFSM system [must]{.underline} allow for a    |      |
| .1.8.7.2 | "stop" command within the scenario during replay. |      |
+----------+---------------------------------------------------+------+
| 3        | The AFSM system [must]{.underline} allow for a    |      |
| .1.8.7.3 | "resume" command within the scenario during       |      |
|          | replay.                                           |      |
+----------+---------------------------------------------------+------+
| 3        | The AFSM system [must]{.underline} allow for an   |      |
| .1.8.7.4 | instantaneous \"fast forward\" command to         |      |
|          | specific times within the scenario during replay. |      |
+----------+---------------------------------------------------+------+
| 3        | The AFSM system [must]{.underline} allow an       |      |
| .1.8.7.5 | instantaneous \"rewind\" command to specific      |      |
|          | times within the scenario during replay.          |      |
+----------+---------------------------------------------------+------+
| 3        | The AFSM system [must]{.underline} record         |      |
| .1.8.7.6 | transaction entries during replay.                |      |
+----------+---------------------------------------------------+------+
| 3.1.8.8  | The AFSM system [must]{.underline} provide online |      |
|          | Help.                                             |      |
+----------+---------------------------------------------------+------+
| 3.1.8.9  | The AFSM system [must]{.underline} provide        |      |
|          | multiple simultaneous training scenario           |      |
|          | capabilities.                                     |      |
+----------+---------------------------------------------------+------+
| 3.1.9    | Supervisory / Administrative Processing           |      |
+----------+---------------------------------------------------+------+
| 3.1.9.1  | Local Activity Report                             |      |
+----------+---------------------------------------------------+------+
| 3        | The AFSM system [must]{.underline} provide an     |      |
| .1.9.1.1 | exportable report on local activity.              |      |
+----------+---------------------------------------------------+------+
| 3        | The AFSM system [must]{.underline} allow report   |      |
| .1.9.1.2 | parameters to be modifiable.                      |      |
+----------+---------------------------------------------------+------+
| 3.1.9.2  | Monitor System                                    |      |
+----------+---------------------------------------------------+------+
| 3        | The AFSM system [must]{.underline} monitor local  |      |
| .1.9.2.1 | resource use.                                     |      |
+----------+---------------------------------------------------+------+
| 3        | The AFSM system [must]{.underline} monitor        |      |
| .1.9.2.2 | external interface status.                        |      |
+----------+---------------------------------------------------+------+
| 3        | The AFSM system [must]{.underline} monitor system |      |
| .1.9.2.3 | status.                                           |      |
+----------+---------------------------------------------------+------+
| 3        | The AFSM system [must]{.underline} monitor system |      |
| .1.9.2.4 | alarms.                                           |      |
+----------+---------------------------------------------------+------+
| 3.1.9.3  | The AFSM system [must]{.underline} generate law   |      |
|          | enforcement alerts when an aircraft               |      |
|          | identification match is found in the law          |      |
|          | enforcement list(s).                              |      |
+----------+---------------------------------------------------+------+
| 3.1.9.4  | Generate System ATCSCC Alerts                     |      |
+----------+---------------------------------------------------+------+
| 3        | The AFSM system [must]{.underline} generate       |      |
| .1.9.4.1 | ATCSCC alerts when ATCSCC messages are received.  |      |
+----------+---------------------------------------------------+------+
| 3        | The AFSM system [must]{.underline} generate       |      |
| .1.9.4.2 | ATCSCC alerts when ATCSCC messages are cancelled. |      |
+----------+---------------------------------------------------+------+
| 3.1.9.5  | The AFSM system workstations [must]{.underline}   |      |
|          | be configurable by operational function.          |      |
+----------+---------------------------------------------------+------+
| 3.1.10   | Logical Display Manipulation                      |      |
+----------+---------------------------------------------------+------+
| 3.1.10.1 | The AFSM system [must]{.underline} allow resizing |      |
|          | of multiple logical displays within the physical  |      |
|          | display.                                          |      |
+----------+---------------------------------------------------+------+
| 3.1.10.2 | The AFSM system [must]{.underline} allow          |      |
|          | scrolling of multiple logical displays within the |      |
|          | physical display.                                 |      |
+----------+---------------------------------------------------+------+
| 3.1.10.3 | The AFSM system [must]{.underline} allow          |      |
|          | relocation of multiple logical displays within    |      |
|          | the physical display.                             |      |
+----------+---------------------------------------------------+------+
| 3.1.10.4 | The AFSM system [must]{.underline} allow          |      |
|          | configuration of displays.                        |      |
+----------+---------------------------------------------------+------+
| 3.1.10.5 | The AFSM system [must]{.underline} provide the    |      |
|          | capability for logical displays on as many as two |      |
|          | physical monitors.                                |      |
+----------+---------------------------------------------------+------+
| 3.1.10.6 | The AFSM system [must]{.underline} provide the    |      |
|          | capability for drag and drop of information       |      |
|          | between multiple logical displays.                |      |
+----------+---------------------------------------------------+------+
| 3.1.10.7 | The AFSM system [must]{.underline} provide the    |      |
|          | capability to log a briefing from multiple        |      |
|          | logical displays.                                 |      |
+----------+---------------------------------------------------+------+
| 3.1.11   | Continuous Data Recording                         |      |
+----------+---------------------------------------------------+------+
| 3.1.11.1 | The AFSM system [must]{.underline} history record |      |
|          | all input from internal sources.                  |      |
+----------+---------------------------------------------------+------+
| 3.1.11.2 | The AFSM system [must]{.underline} history record |      |
|          | all input from external sources.                  |      |
+----------+---------------------------------------------------+------+
| 3.1.11.3 | The AFSM system [must]{.underline} history record |      |
|          | all output data packets to internal sources.      |      |
+----------+---------------------------------------------------+------+
| 3.1.11.4 | The AFSM system [must]{.underline} history record |      |
|          | all output data packets to external sources.      |      |
+----------+---------------------------------------------------+------+
| 3.1.11.5 | The AFSM system [must]{.underline} history record |      |
|          | all data necessary to recreate system status.     |      |
+----------+---------------------------------------------------+------+
| 3.1.11.6 | The AFSM system [must]{.underline} history record |      |
|          | all data necessary to recreate performance.       |      |
+----------+---------------------------------------------------+------+
| 3.1.11.7 | The AFSM system [must]{.underline} history record |      |
|          | all data necessary to recreate system             |      |
|          | environment.                                      |      |
+----------+---------------------------------------------------+------+
| 3.1.11.8 | The AFSM system [must]{.underline} delete         |      |
|          | historical data after a configurable number of    |      |
|          | days.                                             |      |
+----------+---------------------------------------------------+------+
| 3.1.11.9 | The AFSM system, including the hardware           |      |
|          | configuration, [must]{.underline} record all      |      |
|          | operational data for a configurable number of     |      |
|          | days.                                             |      |
+----------+---------------------------------------------------+------+
| 3        | The AFSM system [must]{.underline} time stamp all |      |
| .1.11.10 | recorded input data to a calibrated national time |      |
|          | standard source in UTC format.                    |      |
+----------+---------------------------------------------------+------+
| 3        | The AFSM system [must]{.underline} time stamp all |      |
| .1.11.11 | recorded output data to a calibrated national     |      |
|          | time standard source in UTC format.               |      |
+----------+---------------------------------------------------+------+
| 3        | The AFSM system [must]{.underline} synchronize    |      |
| .1.11.12 | all recorded input data to a calibrated national  |      |
|          | time standard source in UTC format.               |      |
+----------+---------------------------------------------------+------+
| 3        | The AFSM system [must]{.underline} synchronize    |      |
| .1.11.13 | all recorded output data to a calibrated national |      |
|          | time standard source in UTC format.               |      |
+----------+---------------------------------------------------+------+
| 3        | The AFSM system [must]{.underline} record all     |      |
| .1.11.14 | critical data required for recovery of the system |      |
|          | to a serviceable state.                           |      |
+----------+---------------------------------------------------+------+
| 3        | The AFSM system [must]{.underline} record all     |      |
| .1.11.15 | critical data required for return of the system   |      |
|          | to a serviceable state.                           |      |
+----------+---------------------------------------------------+------+
| 3        | The AFSM system [must]{.underline} allow the      |      |
| .1.11.16 | critical recorded data required for operations to |      |
|          | be accessible regardless of system status.        |      |
+----------+---------------------------------------------------+------+
| 3        | The AFSM system [must]{.underline} allow          |      |
| .1.11.17 | historical data to be archived for further use.   |      |
+----------+---------------------------------------------------+------+
| 3.1.12   | Event Reconstruction                              |      |
+----------+---------------------------------------------------+------+
| 3.1.12.1 | The AFSM system [must]{.underline} automatically  |      |
|          | store time-stamped data for a configurable number |      |
|          | of days, for archive purposes.                    |      |
+----------+---------------------------------------------------+------+
| 3.1.12.2 | The AFSM system [must]{.underline} allow for data |      |
|          | retrieval and reconstruction of time-stamped      |      |
|          | data, without interference with the live          |      |
|          | operational system.                               |      |
+----------+---------------------------------------------------+------+
| 3.1.12.3 | The AFSM system [must]{.underline} generate a     |      |
|          | report on Flight Service user-defined operational |      |
|          | information.                                      |      |
+----------+---------------------------------------------------+------+
| 3.1.13   | Monitor and Control                               |      |
+----------+---------------------------------------------------+------+
| 3.1.13.1 | The AFSM system Monitor and Control function      |      |
|          | [must]{.underline} monitor system health.         |      |
+----------+---------------------------------------------------+------+
| 3.1.13.2 | The AFSM system Monitor and Control function      |      |
|          | [must]{.underline} monitor system performance.    |      |
+----------+---------------------------------------------------+------+
| 3.1.13.3 | The AFSM system Monitor and Control function      |      |
|          | [must]{.underline} generate visual alarms.        |      |
+----------+---------------------------------------------------+------+
| 3.       | The AFSM system Monitor and Control function      |      |
| 1.13.3.1 | [must]{.underline} generate visual alarms in case |      |
|          | of system errors that affect system operation.    |      |
+----------+---------------------------------------------------+------+
| 3.       | The AFSM system Monitor and Control function      |      |
| 1.13.3.2 | [must]{.underline} generate visual alarms in case |      |
|          | of out of tolerance conditions that affect system |      |
|          | operation.                                        |      |
+----------+---------------------------------------------------+------+
| 3.       | The AFSM system Monitor and Control function      |      |
| 1.13.3.3 | [must]{.underline} generate visual alarms in case |      |
|          | of recovery actions that affect system operation. |      |
+----------+---------------------------------------------------+------+
| 3.       | The AFSM system Monitor and Control function      |      |
| 1.13.3.4 | [must]{.underline} generate visual alarms in case |      |
|          | of overloads that affect system operation.        |      |
+----------+---------------------------------------------------+------+
| 3.       | The AFSM system Monitor and Control function      |      |
| 1.13.3.5 | [must]{.underline} generate visual alarms in case |      |
|          | of failed LRUs that affect system operation.      |      |
+----------+---------------------------------------------------+------+
| 3.       | The AFSM system Monitor and Control function      |      |
| 1.13.3.6 | [must]{.underline} generate visual alarms in case |      |
|          | of other conditions that affect system operation. |      |
+----------+---------------------------------------------------+------+
| 3.1.13.4 | The AFSM system Monitor and Control function      |      |
|          | [must]{.underline} generate audible alarms.       |      |
+----------+---------------------------------------------------+------+
| 3.       | The AFSM system Monitor and Control function      |      |
| 1.13.4.1 | [must]{.underline} generate audible alarms in     |      |
|          | case of system errors that affect system          |      |
|          | operation.                                        |      |
+----------+---------------------------------------------------+------+
| 3.       | The AFSM system Monitor and Control function      |      |
| 1.13.4.2 | [must]{.underline} generate audible alarms in     |      |
|          | case of out of tolerance conditions that affect   |      |
|          | system operation.                                 |      |
+----------+---------------------------------------------------+------+
| 3.       | The AFSM system Monitor and Control function      |      |
| 1.13.4.3 | [must]{.underline} generate audible alarms in     |      |
|          | case of recovery actions that affect system       |      |
|          | operation.                                        |      |
+----------+---------------------------------------------------+------+
| 3.       | The AFSM system Monitor and Control function      |      |
| 1.13.4.4 | [must]{.underline} generate audible alarms in     |      |
|          | case of overloads that affect system operation.   |      |
+----------+---------------------------------------------------+------+
| 3.       | The AFSM system Monitor and Control function      |      |
| 1.13.4.5 | [must]{.underline} generate audible alarms in     |      |
|          | case of failed LRUs that affect system operation. |      |
+----------+---------------------------------------------------+------+
| 3.       | The AFSM system Monitor and Control function      |      |
| 1.13.4.6 | [must]{.underline} generate audible alarms in     |      |
|          | case of other conditions that affect system       |      |
|          | operation.                                        |      |
+----------+---------------------------------------------------+------+
| 3.1.14   | AFSM Voice Switch                                 |      |
+----------+---------------------------------------------------+------+
| 3.1.14.1 | See Appendix 5: AFSM Voice Switch Requirements    |      |
+----------+---------------------------------------------------+------+
| 3.1.15   | Alternate Access                                  |      |
+----------+---------------------------------------------------+------+
| 3.1.15.1 | The AFSM system [must]{.underline} provide        |      |
|          | customer access through an FAA-approved web       |      |
|          | portal.                                           |      |
+----------+---------------------------------------------------+------+
| 3.       | The AFSM web portal [must]{.underline} support a  |      |
| 1.15.1.1 | standard web browser for the user interface.      |      |
+----------+---------------------------------------------------+------+
| 3.       | The AFSM web portal [must]{.underline} comply     |      |
| 1.15.1.2 | with US Government and FAA security requirements. |      |
+----------+---------------------------------------------------+------+
| 3.       | The AFSM web portal [must]{.underline} comply     |      |
| 1.15.1.3 | with US Government and FAA web content policies.  |      |
+----------+---------------------------------------------------+------+
| 3.       | The AFSM web portal [must]{.underline} provide    |      |
| 1.15.1.4 | low bandwidth web pages for users who have low    |      |
|          | connection speed internet connections.            |      |
+----------+---------------------------------------------------+------+
| 3.       | The AFSM web portal [must]{.underline} allow      |      |
| 1.15.1.5 | users to access current AFSM weather databases.   |      |
+----------+---------------------------------------------------+------+
| 3.       | The AFSM web portal [must]{.underline} provide a  |      |
| 1.15.1.6 | glossary of aviation weather terms.               |      |
+----------+---------------------------------------------------+------+
| 3.       | The AFSM web portal [must]{.underline} provide    |      |
| 1.15.1.7 | historical (trend) weather information.           |      |
+----------+---------------------------------------------------+------+
| 3.       | The AFSM web portal [must]{.underline} provide 3  |      |
| 1.15.1.8 | character to 4 character location identifier      |      |
|          | (LOCID) conversion.                               |      |
+----------+---------------------------------------------------+------+
| 3.       | The AFSM web portal [must]{.underline} provide 4  |      |
| 1.15.1.9 | character to 3 character LOCID conversion.        |      |
+----------+---------------------------------------------------+------+
| 3.1      | The AFSM web portal [must]{.underline} provide 3  |      |
| .15.1.10 | character/4 character LOCID encode and decode.    |      |
+----------+---------------------------------------------------+------+
| 3.1      | The AFSM web portal [must]{.underline} display    |      |
| .15.1.11 | current Alaskan Pilot Bulletins.                  |      |
+----------+---------------------------------------------------+------+
| 3.1      | The AFSM web portal [must]{.underline} allow      |      |
| .15.1.12 | pilots to file domestic VFR flight plans.         |      |
+----------+---------------------------------------------------+------+
| 3.1      | The AFSM web portal [must]{.underline} allow      |      |
| .15.1.13 | pilots to file domestic IFR flight plans.         |      |
+----------+---------------------------------------------------+------+
| 3.1      | The AFSM web portal [must]{.underline} allow      |      |
| .15.1.14 | pilots to file ICAO VFR flight plans.             |      |
+----------+---------------------------------------------------+------+
| 3.1      | The AFSM web portal [must]{.underline} allow      |      |
| .15.1.15 | pilots to file ICAO IFR flight plan.              |      |
+----------+---------------------------------------------------+------+
| 3.1      | The AFSM web portal [must]{.underline} allow      |      |
| .15.1.16 | pilots to file DVFR flight plans.                 |      |
+----------+---------------------------------------------------+------+
| 3.1      | The AFSM web portal [must]{.underline} have       |      |
| .15.1.17 | access to the Alaskan Master Flight Plan          |      |
|          | database.                                         |      |
+----------+---------------------------------------------------+------+
| 3.1      | The AFSM web portal [must]{.underline} provide    |      |
| .15.1.18 | route briefings.                                  |      |
+----------+---------------------------------------------------+------+
| 3.1      | The AFSM web portal [must]{.underline} provide    |      |
| .15.1.19 | area briefings.                                   |      |
+----------+---------------------------------------------------+------+
| 3.1      | The AFSM web portal [must]{.underline} provide    |      |
| .15.1.20 | RAIM data in an understandable graphical form.    |      |
+----------+---------------------------------------------------+------+
| 3.1      | The AFSM web portal [must]{.underline} support    |      |
| .15.1.21 | Personal Desktop Assistant (PDA) and small screen |      |
|          | rendering devices (SSR).                          |      |
+----------+---------------------------------------------------+------+
| 3.1      | The AFSM web portal [must]{.underline} provide    |      |
| .15.1.22 | interactive weather briefings with a FSS          |      |
|          | specialist if requested by the user.              |      |
+----------+---------------------------------------------------+------+
| 3.1      | The AFSM web portal [must]{.underline} support    |      |
| .15.1.23 | weather and aeronautical information from a FSS   |      |
|          | delivery via an e-mail messaging platform.        |      |
+----------+---------------------------------------------------+------+
| 3.1      | The AFSM web portal [must]{.underline} support    |      |
| .15.1.24 | Pilot/Flight Service user forums.                 |      |
+----------+---------------------------------------------------+------+
| 3.1      | The AFSM web portal [must]{.underline} allow      |      |
| .15.1.25 | access to Alaskan weather Cameras.                |      |
+----------+---------------------------------------------------+------+
| 3.1      | The AFSM web portal [must]{.underline} allow      |      |
| .15.1.26 | pilots to cancel VFR flight plans.                |      |
+----------+---------------------------------------------------+------+
| 3.1      | The AFSM web portal [must]{.underline} allow      |      |
| .15.1.27 | pilots to close VFR flight plans.                 |      |
+----------+---------------------------------------------------+------+
| 3.1      | The AFSM web portal [must]{.underline} allow      |      |
| .15.1.28 | pilots to amend VFR flight plans.                 |      |
+----------+---------------------------------------------------+------+
| 3.1      | The AFSM web portal [must]{.underline} provide a  |      |
| .15.1.29 | Plain Language option.                            |      |
+----------+---------------------------------------------------+------+
| 3.1      | The AFSM web portal [must]{.underline} provide    |      |
| .15.1.30 | access to flight planning functionality.          |      |
+----------+---------------------------------------------------+------+
| 3.1      | The AFSM web portal [must]{.underline} provide    |      |
| .15.1.31 | access to flight planning resources.              |      |
+----------+---------------------------------------------------+------+
| 3.1.15.2 | The AFSM system [must]{.underline} provide access |      |
|          | through a remote user access terminal.            |      |
+----------+---------------------------------------------------+------+
| 3.       | The AFSM system [must]{.underline} provide Flight |      |
| 1.15.2.1 | Service Specialist remote user access to all of   |      |
|          | the AFSM system functionality and data through    |      |
|          | the remote user access terminal.                  |      |
+----------+---------------------------------------------------+------+
| 3.       | The AFSM system [must]{.underline} provide access |      |
| 1.15.2.2 | through a remote user access terminal at remote   |      |
|          | locations.                                        |      |
+----------+---------------------------------------------------+------+
| 3.       | The AFSM system [must]{.underline} provide access |      |
| 1.15.2.3 | through a remote user access terminal with        |      |
|          | interaction between the user pilot and the Flight |      |
|          | Service Specialist.                               |      |
+----------+---------------------------------------------------+------+
| 3.       | The AFSM system [must]{.underline} provide access |      |
| 1.15.2.4 | through a remote user access terminal that is     |      |
|          | configurable for temporary Flight Service Station |      |
|          | operations.                                       |      |
+----------+---------------------------------------------------+------+
| 3.1.15.3 | The AFSM system [must]{.underline} provide        |      |
|          | exportable activity reports.                      |      |
+----------+---------------------------------------------------+------+
| 3.       | The AFSM system [must]{.underline} provide        |      |
| 1.15.3.1 | exportable web portal activity reports.           |      |
+----------+---------------------------------------------------+------+
| 3.       | The AFSM system [must]{.underline} provide web    |      |
| 1.15.3.2 | portal activity reports with site adaptable       |      |
|          | parameters.                                       |      |
+----------+---------------------------------------------------+------+
| 3.       | The AFSM system [must]{.underline} provide        |      |
| 1.15.3.3 | exportable activity reports.                      |      |
+----------+---------------------------------------------------+------+
| 3.       | The AFSM system [must]{.underline} provide        |      |
| 1.15.3.4 | activity reports with site adaptable parameters.  |      |
+----------+---------------------------------------------------+------+
| 3.1.16   | Automated Text To Voice (ATTV) Processing         |      |
+----------+---------------------------------------------------+------+
| 3.1.16.1 | The AFSM system [must]{.underline} interface with |      |
|          | the existing ATTV system.                         |      |
+----------+---------------------------------------------------+------+
|          |                                                   |      |
+----------+---------------------------------------------------+------+
| 3.2      | **Product Characteristics and Performance         |      |
|          | Requirements**                                    |      |
+----------+---------------------------------------------------+------+
| 3.2.1    | Service Levels                                    |      |
+----------+---------------------------------------------------+------+
| 3.2.1.1  | Reserved                                          |      |
+----------+---------------------------------------------------+------+
| 3.2.2    | Availability                                      |      |
+----------+---------------------------------------------------+------+
| 3.2.2.1  | The AFSM system availability (A~o~)               |      |
|          | [must]{.underline} be greater than or equal to    |      |
|          | (≥) 0.999.                                        |      |
+----------+---------------------------------------------------+------+
| 3.2.3    | Reliability                                       |      |
+----------+---------------------------------------------------+------+
| 3.2.3.1  | The AFSM system [must]{.underline} have a         |      |
|          | Mean-Time-Between-Failures (MTBF) of no less than |      |
|          | 5000 hours over the full range of environmental   |      |
|          | conditions.                                       |      |
+----------+---------------------------------------------------+------+
| 3.2.4    | Maintainability                                   |      |
+----------+---------------------------------------------------+------+
| 3.2.4.1  | The AFSM system Mean-Time-To-Repair (MTTR) for    |      |
|          | the system [must]{.underline} not exceed 0.5      |      |
|          | hours. This period includes all time necessary to |      |
|          | localize, repair, test and restore a failed       |      |
|          | system/unit to its established baseline           |      |
|          | performance once on-site repair activity has      |      |
|          | begun.                                            |      |
+----------+---------------------------------------------------+------+
| 3.2.4.2  | The AFSM system total time to complete all        |      |
|          | periodic tasks [must]{.underline} not exceed 12   |      |
|          | staff hours annually; nor [must]{.underline} any  |      |
|          | periodic maintenance event require more than one  |      |
|          | person to accomplish the task.                    |      |
+----------+---------------------------------------------------+------+
| 3.2.4.3  | The AFSM system [must]{.underline} have the       |      |
|          | capability to automatically diagnose the cause of |      |
|          | system faults.                                    |      |
+----------+---------------------------------------------------+------+
| 3.2.4.4  | The AFSM [must]{.underline} have the capability   |      |
|          | to identify failures to Lowest Replaceable Unit   |      |
|          | (LRU).                                            |      |
+----------+---------------------------------------------------+------+
| 3.2.4.5  | The AFSM [must]{.underline} allow replacement of  |      |
|          | failed LRU without affecting functional           |      |
|          | operations.                                       |      |
+----------+---------------------------------------------------+------+
| 3.2.5    | Recovery                                          |      |
+----------+---------------------------------------------------+------+
| 3.2.5.1  | The AFSM system [must]{.underline} restore itself |      |
|          | in less than 15 minutes after restoration of      |      |
|          | electrical power to the normal operational mode   |      |
|          | in effect at the time of power loss.              |      |
+----------+---------------------------------------------------+------+
| 3.2.6    | System Reserve                                    |      |
+----------+---------------------------------------------------+------+
| 3.2.6.1  | The AFSM system processing resource               |      |
|          | [must]{.underline} meet the following reserves:   |      |
+----------+---------------------------------------------------+------+
| 3        | Central Processing Unit (CPU) use. The AFSM       |      |
| .2.6.1.1 | system [must]{.underline} contain reserve         |      |
|          | processing capacity so that the mean use over any |      |
|          | 5-minute interval is no more than 50 percent of   |      |
|          | the maximum processing capacity.                  |      |
+----------+---------------------------------------------------+------+
| 3        | Memory Use. The AFSM system [must]{.underline}    |      |
| .2.6.1.2 | contain reserve memory capacity so that memory    |      |
|          | use does not exceed 50 percent of the maximum     |      |
|          | memory capacity.                                  |      |
+----------+---------------------------------------------------+------+
| 3        | Storage Use. The AFSM system [must]{.underline}   |      |
| .2.6.1.3 | contain on-line reserve storage capacity so that  |      |
|          | the storage use within the system does not exceed |      |
|          | 50 percent of the maximum on-line storage         |      |
|          | capacity.                                         |      |
+----------+---------------------------------------------------+------+
| 3.2.7    | Portability                                       |      |
+----------+---------------------------------------------------+------+
| 3.2.7.1  | The AFSM system software [must]{.underline} be    |      |
|          | portable to the extent that:                      |      |
+----------+---------------------------------------------------+------+
| 3        | Porting AFSM system software to another           |      |
| .2.7.1.1 | implementation of the Operating System (OS) and   |      |
|          | programming language on the same hardware         |      |
|          | platform [must]{.underline} satisfy all           |      |
|          | functional and performance requirements and 98    |      |
|          | percent of the code [must]{.underline} be         |      |
|          | portable without change.                          |      |
+----------+---------------------------------------------------+------+
| 3        | Porting AFSM system software to another Portable  |      |
| .2.7.1.2 | Operating System Interface Standard               |      |
|          | (POSIX)-compliant hardware platform               |      |
|          | [must]{.underline} satisfy all the functional and |      |
|          | performance requirements and 95 percent of the    |      |
|          | code [must]{.underline} be portable without       |      |
|          | change.                                           |      |
+----------+---------------------------------------------------+------+
|          |                                                   |      |
+----------+---------------------------------------------------+------+

[(This Page Intentionally Left Blank)]{.smallcaps}