Attachment 2 - AAC Automation Requirements Document.pdf

Alaska Automation Capability (AAC) Automation Requirements Document

Version 1.2

3/16/2026

Focal Point Name: Robyne Schroeder

Organizational Code: AJR-B200 Phone Number: (202) 267-2943

Federal Aviation Administration 800 Independence Avenue SW

Washington, DC 20591

V1.1 – 3/16/2026

THIS PAGE INTENTIONALLY LEFT BLANK

i

Table of Contents

1 Introduction

1.1 Description

1.1.1 Purpose

1.1.2 Program Description

1.1.3 Program Background

1.1.4 Alaska Flight Service Shortfalls

1.1.5 Assumptions

1.2 Scope

2 Capability Description and Program Information

2.1 Operational Concept

2.2 Quantities and Location

2.3 Program Constraints and Dependencies

3 Functional and Performance Requirements

3.1 Functional Requirements

3.1.1 Preflight Services

3.1.2 Inflight Services

3.1.3 Flight Data Services/Operational Services

3.1.4 Self-Assisted Services

3.1.5 Electronic Flight Strip Systems

3.2 Alaska Data and Information Requirements

3.2.1 General Alaska Data Requirements

3.2.2 Alaska FSS Local Area Knowledge requirements

3.3 Performance Requirements

3.3.1 System Performance

3.3.2 Performance Management

3.3.3 Recovery Requirements

3.4 Reliability, Maintainability, Availability, and Operational Continuity

3.4.1 Reliability

3.4.2 Maintainability

3.4.3 Availability

3.4.4 Continuity of Operations

4 Integration Requirements ii

4.1 Physical Integration

4.1.1 Environmental Requirements

4.1.2 Land and Facility

4.1.3 Telecommunications

4.2 Functional Integration

4.2.1 Interfaces to Other FAA Enterprise Architecture Elements

4.2.2 External Interfaces

4.2.3 Spectrum Requirements

4.3 Human Factors

4.3.1 Usability

4.3.2 Human-System Interfaces

4.3.3 Computer-Human Interfaces (CHI)

4.3.4 General Control and Visual Indicator Information

4.4 Employee Safety and Health

5 Security and Safety Requirements

5.1 Facility Security

5.2 Personnel Security

5.3 Information Systems Security

5.3.1 Security Management

5.3.2 Security Assessments

5.3.3 Security-Related System Support

5.3.4 Security and Information Access

5.3.5 System and Information Monitoring

5.3.6 System and Information Protection

5.3.7 Privacy Information Protection

5.4 System Safety

5.4.1 Existing Controls

5.4.2 Safety Requirements

6 Quality Management Requirements

6.1 Quality Assurance

6.2 Configuration Management

6.2.1 Configuration Management Program

6.2.2 Configuration Management Planning

7 Test and Evaluation Requirements iii

7.1 Planning and Test Design Requirements

7.2 Developmental Test (DT) Requirements

7.3 Operational Test Requirements

7.3.1 Interoperability Testing Requirements

7.3.2 Operational Suitability Requirements

7.4 Site Test Requirements

7.5 Reporting Requirements

7.6 Test Support Requirements

7.7 Critical Operational Issues

8 In-Service Support and Management

8.1 Integrated Logistics Support

8.2 Maintenance Planning

8.3 Packaging, Handling, Storage, and Transportation

8.4 Support Equipment Maintenance

8.4.1 Tools and Test Equipment

8.4.2 Maintenance Operations

8.5 Training, Training Support, and Personnel Skills

8.5.1 FAA Academy Training System

8.5.2 AAC Training, Training Support, and Personnel Skills

8.6 Technical Data

Appendix A Critical Performance Requirements

Appendix B Acronyms and Glossary

B.1 Acronyms and Abbreviations

B.2 Terms and Definitions

Appendix C Reference Documents

C.1 FAA Documents

C.2 Other Government Documents

C.3 Non-Government Documents iv

Index of Figures

No table of figures entries found.

Index of Tables

Table 2 - Product Acquisition Performance Requirements Table 3 - FSS Site Peak Loading Table 4 - FSS Site Peak Concurrent Transaction Rates Table 5 - Operational Performance Parameters Table 6 - Critical Performance Requirements Table 7: Acronyms and Abbreviations Table 8: Terms and Definitions

1 Introduction

This document presents the functional requirements for the Alaska Automation Capability (AAC), identifying essential system functional capabilities and performance measures necessary to support flight services in Alaska.

This Automation Requirements Document is provided to establish operational context and baseline insight into the Government’s current understanding of capability needs. For purposes of this Challenge-Based Acquisition phase, respondents are not required to demonstrate full compliance with each requirement. Rather, respondents should use this material to inform their conceptual approach and describe how their proposed solution would address the Government’s objectives at a capability level.

Binding performance obligations, final requirement refinement, and compliance validation will be defined as appropriate, in any subsequent production award instrument.

Flight Service collects, processes, interprets, translates, and disseminates aeronautical and meteorological information to promote safe and expeditious flights through pilot weather briefings, inflight weather advisories, and flight plan filing. Flight Service relays Instrument Flight Rules (IFR) and Special Visual Flight Rules (SVFR) clearances as appropriate and provides applicable information on preferred IFR routes as well as departure and arrival procedures. In addition, Flight Service provides Search and Rescue (SAR) services integrated with commercial Global Positioning Service (GPS) aircraft tracking, and orientation services to Visual Flight Rules (VFR) flights. Flight Service is an important source of information flow to the National Airspace System (NAS) through the filing of flight plans, aircraft movement messages, and the collection and dissemination of Notices to Air Missions (NOTAMs), and Pilot Weather Reports (PIREPs).

The General Aviation (GA) community represents the primary customer base and generates the majority of all service requests. These include requests for preflight planning, pilot briefings, flight plan filing, meteorological and aeronautical information, and inflight orientation services.

Flight Service supports disaster relief, medical evacuations, weather and traffic reporting, and business/personal travel to thousands of airports/landing areas throughout the NAS. Military, law enforcement, commercial, corporate, air taxi, U.S. Customs and Border Protection (CBP), Civil Air Patrol, Medevac and others also benefit from services provided by Flight Service.

Flight Service also supports other FAA Air Traffic Organization (ATO) service units. Flight Service Specialists (Specialists) and Certified Professional Controllers (CPCs)1 relay communications from pilots to Terminal and En Route controllers (when no direct means exist)

1 Flight Service Specialists provide contracted flight services for the contiguous United States (CONUS) through an existing contract, while Certified Professional Controllers provide flight services in Alaska as FAA FTEs.

and assist in data collection and data entry. Flight Service coordinates with Technical Operations regarding equipment (e.g., radio, NAVAIDs) status information. Flight Service has historically provided meteorological data, aeronautical information, and flight planning services to its pilot customers in two ways. The traditional service delivery (human-assisted) consists of pilots contacting a Specialist by phone or radio. Specialists access a variety of meteorological products, aeronautical data, and other related information based on the pilot’s requested route and share that information with the pilot orally. Alternatively, pilots can obtain preflight information and file flight plans through an online web portal. Pilots accessing preflight information online are responsible for obtaining and understanding all available information about their flight prior to filing a flight plan.

Over the past decade, emerging technologies in communications, personal computing, and mobile devices have provided opportunities to deliver flight services more efficiently to users.

User preferences and demands are reflected in the continuing decline in the use of human-assisted services as pilots take advantage of automated and enhanced technologies (e.g., integrated weather products, electronic flight bags, Automatic Dependent Surveillance – Broadcast [ADS-B]) available through the FAA and private sector.

In 2005, the FAA awarded a contract to a commercial provider (Lockheed Martin/Leidos) for preflight planning support and in-flight advisory assistance in the contiguous United States (CONUS), Hawaii, and Puerto Rico. That contract, known as Flight Service for the 21st Century (FS21), realized operational improvements (OIs) along with economies in staffing and infrastructure.

In Alaska, flight services are provided by federal employees using the Operational and Supportability Implementation System (OASIS II). The OASIS II system consists of a leased automation system operated by Federal CPCs providing the full range of flight services in Alaska.

Alaska Flight Service (AFS) relies on voice switch and automation systems, both of which are facing current operational and technical gaps and face increasing risks that could fail, preventing Flight Service from performing the critical services in Alaska. The legacy automation system, OASIS II, provides the capability to acquire, store, retrieve and display information to compile and deliver the services through voice and data connectivity with pilots and FAA ATC facilities.

However, the system has been maintained but not modernized or improved for many years and is using aging hardware that have reached end-of-life. The OASIS II managed services contract is currently extended with annual and semi-annual option years through 2028.

The legacy automation system faces several shortfalls including system limitations such as data management, communication, and bandwidth limitations which lead to labor and management inefficiencies and minor safety impacts. Additionally, these limitations contribute to administrative inefficiencies which lead to costs increases in administrative affairs and staffing resource management. This Automation Requirements Document is intended to address key operational shortfalls by implementing a modernized automation solution that deploys updated technology and supports the FAA’s objectives to greatly improve Flight Service capabilities.

The following assumptions apply to the AAC acquisition:

• The solution will be a rapidly deployable, web-based cloud hosted Flight Service system.

• The FAA’s NAS Trusted Cloud (NTC) will be in place and accepting client services in time for this acquisition.

• The FAA will modernize its communications infrastructure to utilize IP-based network technologies. This will include terrestrial-based communications to Alaska Flight Service Stations (FSS).2

• FAA Telecommunications Services will be transitioned in Alaska from FAA Telecommunications Infrastructure (FTI) to FAA Enterprise Network Services (FENS) prior to AAC site implementation activities.

• Demand for services in Alaska will continue at or above current levels.

• The Flight Service delivery model for Alaska will remain unchanged.

• Flight Service Certified Professional Controller (CPC) training will continue to be conducted at the AFS Training Academy in Kenai.

• Maintenance training can be conducted at a vendor facility or FAA training facility.

• FAA Technical Operations will provide first-level system support for all hardware equipment contained in Alaska facilities.

• All NOTAM management activities will be supported through the FAA’s cloud-based NOTAM Management Service (NMS).

• Self-assisted services for Alaska will be provided by the existing FS21 system.

• The Government will provide all telecommunication services and access necessary for the performance of AAC.

The scope of AAC and these requirements includes providing flight services for Alaska. The flight services should be distinct from pilot-facing subscription products, even if derived from those products. Flight Services include:

• Providing preflight planning services, which includes telephone based, preflight pilot briefings that accompany flight planning and filing both IFR and VFR flight plans via phone calls or through self-assisted means.

• Managing existing IFR/VFR flights plans, including active VFR tracking, overdue alerts, and flight plan close-outs.

• Maintaining and providing continual weather broadcasts on selected Navigation Aids (NAVAIDs).

• Integrating FAA authoritative weather, aeronautical data, and flight plan services as outlined in FAA Order 7110.10.

• Issuing and cancelling Notice to Airmen (NOTAM).

2 All Alaska FSS are expected to receive fiber-optic networking infrastructure by contract implementation, apart from the McGrath FSS.

• Relaying clearances and providing Airport Advisory services at non-towered or part-time towered airports.

• Developing, translating, processing, and coordinating aeronautical, meteorological and aviation information, to advise, notify and educate customers.

• Supporting safety operations, such as emergency services, Search and Rescue, and pilot orientation services.

2 Capability Description and Program Information

The Respondent-provided web-based, cloud automation system will incorporate functionality that supports the FAA CPC delivery of flight services for any Alaska Flight Plan Area (FPA), also known as an Area of Responsibility (AOR), from any workstation at an Alaska FSS facility.

Provision of these services will comply with FAA Order JO 7110.10, Flight Service. The automation will combine capabilities currently supporting Flight Service operations including self-assisted (e.g., web enabled) services along with legacy functions necessary for the conduct of operations in Alaska. Support will be provided to Alaska Flight Service CPCs and supervisors for applications such as weather briefings, inflight services, flight data services, quality assurance and control (QA/QC) processes, and supervisory and administrative functions.

Flight Service operations in Alaska are currently supported by 17 facilities — three Hub FSSs and 14 Satellite FSSs. Hub FSSs include Kenai, Fairbanks, and Juneau. Satellite FSSs include Barrow, Deadhorse, Kotzebue, Nome, Northway, Iliamna, Talkeetna, McGrath, Dillingham, Cold Bay, Homer, Palmer, Sitka, and Ketchikan. At night and during seasonal closings, Hub FSSs subsume Satellite FSS operations. When the Satellite FSSs close within a flight plan area, the radio frequencies and telephone lines at the Satellite FSSs are transferred to the assigned Hub FSS.

Each facility has several different types of working positions, including In-Flight, Pre-Flight, Flight Data, Supervisor, and Maintenance positions. Additionally, some facilities currently have training positions and spare working positions. To avoid redundancy, the current listing of Alaska FSSs and number of positions is provided in other program documentation.

Operationally, the AAC web-based, cloud automation system requires functionality that ensures compliance with the current FAA Order JO 7110.10. This order, which is periodically revised, prescribes the procedures and phraseology for use by Flight Service personnel providing services to the users of the NAS. The Program Office for AAC will maintain awareness of updates to this order to ensure the AAC functional capabilities provided by the Respondent remain in alignment with the order.

3 Functional and Performance Requirements

Each requirement (“must” statement) in this document provides a permanent identifying tag in the form of “AAC-####” where the #### indicates a 4-digit value that is unique to the requirement and is persistent through the life of the requirement. This is used for configuration management and requirement life-cycle control.

Flight services are categorized into the following areas: Preflight Services, Inflight Services, Flight Data/Operational Services, and Self-Assisted Services.

The Respondent must [AAC-1004] provide data for Alaska CPCs to provide Standard, Abbreviated, Outlook, and Delta Weather Briefings for assigned AORs in accordance with FAA Order 7110.10.

The Respondent must [AAC-1006] provide the capability for Alaska CPCs to perform flight planning functions in accordance with FAA Order 7110.10, Flight Services.

The Respondent must [AAC-1008] provide the capability for Alaska CPCs to perform flight planning functions in accordance with NAS-IR-23040001.

The Respondent must [AAC-1010] provide the capability for Alaska CPCs to perform flight planning functions in accordance with ICAO Rules of the Air and Air Traffic Services document 4444.

The Respondent must [AAC-1012] provide the capability for Alaska CPCs to perform Inflight functions in accordance with FAA Order 7110.10.

The Respondent must [AAC-1014] provide functionality and data necessary for Alaska CPCs to perform flight data services in accordance with FAA Order JO 7110.10, Flight Services.

The Respondent must [AAC-0084] support aviation activities pertaining to national security in accordance with current national security restrictions and guidance.

The Respondent must [AAC-0086] protect national security and sensitive information in accordance with FAA Order 1600.2, Classified National Security Information.

The Respondent must [AAC-0087] release national security and sensitive information to authorized parties as following:

• As directed by the Government

• As addressed in FAA Order 1600.2, Classified National Security Information

• As addressed in FAA Order 1600.69, FAA Facility Security Management Program

The Respondent must [AAC-4132] provide the capability for Alaska CPCs to perform Search and Rescue (SAR) functions in accordance with FAA Order 7110.10.

The Respondent must [AAC-4134] allow Alaska CPCs to manage SAR messages received from the Enhanced Special Reporting Service (eSRS).

The Respondent must [AAC-1460] accept SAR messages from external facilities.

The Respondent must [AAC-1481] automatically address SAR messages for transmission to appropriate facilities, appending address(es) into the appropriate field based upon the type of SAR message.

The Respondent must [AAC-4136] make available for edit improperly formatted SAR messages.

The Respondent must [AAC-0092] log all user actions performed on the automation system.

The Respondent must [AAC-0093] log all user actions performed on the web portal/application.

The Respondent must [AAC-0094] record all communications from operational positions.

The Respondent must [AAC-0096] maintain all system logs in accordance with FAA Order JO 7210.3, Facility Operation and Administration.

The Respondent must [AAC-0097] maintain all system recordings in accordance with FAA Order JO 7210.3, Facility Operation and Administration.

The Respondent must [AAC-2230] allow authorized FAA personnel the ability to create work position configurations which support Alaska FS operations based on Area of Responsibility, Work Position, and Flight Service Facility.

The Respondent must [AAC-2232] permit the definition of work position configurations in the configuration database sufficient to support Alaska flight service operations.

Note: Alaska flight service currently supports 11 functional positions for CPCs and supervisors (Administrator, Flight Data, Inflight Controller in Charge (CIC), Inflight, Maintenance, Operational Supervisor (OS) CIC, Preflight, Quality Assurance/Quality Reliability Officer (QRO), Test, Training, Other) and is operational at 17 facilities.

The Respondent must [AAC-2240] recover from a system restart with the future Alaska FS workstation configurations available for specialist initiation at each position.

The Respondent must [AAC-2254] permit any Alaska FS workstation to be used to access supervisory functions.

The Respondent must [AAC-2256] allow a FAA FS Supervisor the ability to assign Alaska configurations to staff to support daily work assignments based on Specialist: AOR qualifications, work schedule, facility, and/or Work Position.

The Respondent must [AAC-2272] allow FAA Specialist the ability to configure the Controller Work Position based on their shift assignment.

The Respondent must [AAC-2274] display the current user identification and their currently assigned FS role and AOR.

The Respondent must [AAC-2276] allow FAA Specialist to configure the CWP to support user preferences.

The Respondent must [AAC-2278] allow the FAA specialist to store user preferences.

The Respondent must [AAC-2286] prevent the interruption of service during reconfiguration on those positions and external interfaces not affected by the reconfiguration.

The Respondent must [AAC-2288] ensure that reconfiguration process does not disconnect any established call at the position until reconfiguration is accepted.

The Respondent must [AAC-2290] require no more than one minute to prepare reconfiguration data, measured from the time reconfiguration is invoked by the operator to the time that the System requests the first position acknowledgment of reconfiguration, or to the time that the System performs the reconfiguration, for resources that do not require acknowledgment.

The Respondent must [AAC-2325] provide FAA Airway Transportation System Specialist (ATSS) personnel monitoring and control capabilities for all AAC equipment located in FAA facilities.

The Respondent must [AAC-2326] ensure that the initial state of each installed device on startup is configurable as being online, offline, or maintenance busy.

The AAC Monitor and Control (M&C) function must [AAC-2210] monitor system health.

The AAC M&C function must [AAC-2211] monitor system performance.

The Respondent must [AAC-2224] display the status of any ongoing reconfigurations on the authorized access levels’ workstation.

The Respondent must [AAC-2304] perform fault and failure detection and isolation.

The Respondent must [AAC-2306] ensure that fault detection does not interfere with system operations.

The Respondent must [AAC-2308] report all detectable faults to the maintenance workstation(s) and to the maintenance log simultaneously.

The Respondent must [AAC-2312] permit the initiation of manual diagnostic testing.

The Respondent must [AAC-2316] generate a maintenance log that contains faults detected by the system fault detection features.

The AAC maintenance log must [AAC-2318] contain restoration activities.

The AAC maintenance log must [AAC-2320] contain reconfiguration events.

The AAC maintenance log must [AAC-2322] be capable of storing at least 90 days of maintenance history.

The Respondent must [AAC-2324] permit authorized users to print the maintenance logs from any Alaska FSS.

Self-Assisted Services in Alaska will be provided by the existing FS21 system.

The AAC will provide Alaska CPCs an electronic input device and output display to create and edit digital flight progress strips. The CPCs will also be able to create digital flight progress strips from flight plan masks in an Active Flight Workspace bay, and in Inflight Work bays.

Digital flight progress strips will allow the CPCs to perform designated flight planning and flight service support functions directly from the electronic input device. These functions include, but are not limited to, filing, logging, weather briefing, canceling, closing, amending, and activating a flight plan; and initiating search and rescue operations.

The AAC Electronic Flight Strips system (EFS) must [AAC-1318] provide an input device for managing digital flight progress strips.

Note: In the above requirement, the actions associated with “managing” digital flight progress strips include, but are not necessarily limited to creating, editing, deleting, copying, and manipulating.

The AAC EFS must [AAC-1319] provide the capability to create a digital flight progress strip using the electronic input device.

The digital flight progress strip must [AAC-1320] include an Aircraft ID field.

The digital flight progress strip must [AAC-1321] include an Aircraft Type/Special Equipment field.

The digital flight progress strip must [AAC-1322] include a TAS/Alt field.

The TAS/Alt field must [AAC-1323] include an Airspeed field.

The TAS/Alt field must [AAC-1324] include an Altitude field.

The digital flight progress strip must [AAC-1325] include a Departure field.

The digital flight progress strip must [AAC-1326] include a Route field.

The digital flight progress strip must [AAC-1327] include a Destination field.

The digital flight progress strip must [AAC-1328] include a Time of Departure field.

The digital flight progress strip must [AAC-1329] include an ETA field.

The digital flight progress strip must [AAC-1330] include an ETE field.

The digital flight progress strip must [AAC-1331] include a Flight Type field.

The digital flight progress strip must [AAC-1332] include a Remarks field.

The digital flight progress strip must [AAC-1333] provide the capability to record a Time of Contact with a Pilot when communication with a Pilot is established based on user input.

The digital flight progress strip must [AAC-1334] include an Information Received from Pilot/Another Facility field.

The digital flight progress strip must [AAC-1335] include a Data Issued to the Aircraft field.

The digital flight progress strip must [AAC-1336] provide a capability to record a Number on Board for a flight based on user input.

The digital flight progress strip must [AAC-1337] provide a capability to record current Flight Rules for a flight based on user input.

The digital flight progress strip must [AAC-1338] provide a capability to record Fuel on Board for a flight based on user input.

The digital flight progress strip must [AAC-1339] provide a capability to record Pilot Data based on user input.

The digital flight progress strip must [AAC-1340] provide a capability to record Responsible FSS Data.

The digital flight progress strip must [AAC-1341] provide a capability to record Notification Data.

The digital flight progress strip must [AAC-1342] include a Comm/Nav Equipment field.

The digital flight progress strip must [AAC-1343] include a Transponder field.

The digital flight progress strip must [AAC-1344] include a Wake Turbulence field.

The AAC EFS must [AAC-1345] provide the capability to display digital flight progress strip records.

The AAC EFS must [AAC-1346] provide the capability to edit digital flight progress strip records based on user input.

The AAC EFS must [AAC-1347] provide the capability to perform flight planning functions based on user input.

The AAC EFS [AAC-1348] must provide the capability to file flight plans based on the digital flight progress strips records and data for a flight. The handwriting input device must [AAC- 1349] log the following:

The log time must [AAC-1350] default to the current time.

The AAC EFS must [AAC-1351] log airport advisories.

The AAC EFS must [AAC-1352] log pilot briefings.

The AAC EFS must [AAC-1353] log Special Visual Flight Rules (SVFR) clearances issued.

The AAC EFS must [AAC-1354] log IFR clearances issued.

The AAC EFS must [AAC-1355] log aircraft contacts.

The AAC EFS must [AAC-1356] log radio contacts.

The AAC EFS must [AAC-1357] log Request/Response information.

The handwriting input device must [AAC-1358] provide the capability to request a weather briefing.

The AAC EFS must [AAC-1359] cancel a flight plan based on user input.

The AAC EFS must [AAC-1360] close a flight plan based on user input.

The AAC EFS must [AAC-1361] provide the capability to amend a flight plan based on user input.

The AAC EFS must [AAC-1362] provide the capability to activate a flight plan based on user input.

The AAC EFS must [AAC-1363] provide the capability to search for a digital flight progress strip using the handwriting input device.

The AAC EFS must [AAC-1364] provide the capability to create a digital flight progress strip template.

The digital flight progress strip template must [AAC-1365] include a Flight Type field.

The digital flight progress strip template must [AAC-1366] include a Flight Rules field.

The digital flight progress strip template must [AAC-1367] include an Aircraft ID field.

The digital flight progress strip template must [AAC-1368] include an Aircraft Type field.

The digital flight progress strip template must [AAC-1369] include an Airspeed field.

The digital flight progress strip template must [AAC-1370] include an Altitude field.

The digital flight progress strip template must [AAC-1371] include a Departure field.

The digital flight progress strip template must [AAC-1372] include a Route field.

The digital flight progress strip template must [AAC-1373] include a Destination field.

The digital flight progress strip template must [AAC-1374] include a Time of Departure field.

The digital flight progress strip template must [AAC-1375] include an ETA field.

The digital flight progress strip template must [AAC-1376] include a ETE field.

The digital flight progress strip template must [AAC-1377] include a Number on Board field.

The digital flight progress strip template must [AAC-1378] include a Fuel Capacity field.

The digital flight progress strip template must [AAC-1379] include a Comm/Nav Equipment field.

The digital flight progress strip template must [AAC-1380] include a Transponder field.

The digital flight progress strip template must [AAC-1381] include a Pilot Data field.

The digital flight progress strip template must [AAC-1382] include a Wake Turbulence field.

The AAC EFS must [AAC-1383] provide the capability to store digital flight progress strip templates by:

a. Site

b. User

The AAC EFS must [AAC-1386] provide the capability to edit digital flight progress strip templates.

The AAC EFS must [AAC-1387] provide the capability to delete digital flight progress strip templates.

The AAC EFS must [AAC-1388] provide the capability to display digital flight progress strip templates by:

a. Site

b. User

The AAC EFS must [AAC-1391] provide the capability to copy Site digital flight progress strip templates to User digital flight progress strip templates.

The AAC EFS must [AAC-1392] provide the capability to copy User digital flight progress strip templates to Site digital flight progress strip templates.

The AAC EFS must [AAC-1393] provide the capability to display and copy another User's digital flight progress strip templates.

The AAC EFS must [AAC-1394] provide the capability to copy another User's digital flight progress strip templates to the User Storage of the logged in User.

The AAC EFS must [AAC-1395] provide the capability to copy another User's digital flight progress strip templates to the Facility Storage of the logged in User.

The AAC EFS must [AAC-1396] provide the capability to display another User's digital flight progress strip RID data.

The AAC EFS must [AAC-1396.5] provide the capability to copy another User's digital flight progress strip RID data.

The AAC EFS will provide CPCs a configurable electronic strip-bay, like physical flight progress strips and bay. The digital flight progress strip display will allow the CPCs to configure flight strip layouts into partitions corresponding to separate airports or other user-defined groupings.

The AAC EFS must [AAC-1422] provide a user configurable electronic strip-bay layout containing the following digital flight progress strips:

a. Proposed

b. Inbound

c. Overflight

d. Separator

The AAC EFS must [AAC-1427] provide the capability to divide the electronic strip-bay display into the following sections:

a. Proposed List

b. Inbound List

c. Active Flight Workspace

d. Other Active Flight Workspaces

e. Common Area

The AAC EFS must [AAC-1433] display digital flight progress strips at the top of the electronic strip-bay when added.

The AAC EFS must [AAC-1434] visually indicate when digital flight progress strips are added to the electronic strip-bay.

The AAC EFS must [AAC-1435] visually indicate if the flight plan is on the Inbound List.

The AAC EFS must [AAC-1436] visually indicate if the flight plan is on the Proposed List.

The AAC EFS must [AAC-1437] provide the capability to display individual digital flight progress strips in the active flight workspace.

The AAC EFS must [AAC-1438] provide the capability to minimize an individual digital flight progress strip in the active flight workspace.

The AAC EFS must [AAC-1439] provide the capability to display abbreviated digital flight progress strips.

The AAC EFS must [AAC-1440] provide the capability to store digital flight progress strips in the electronic strip-bay.

The AAC EFS must [AAC-1441] provide the capability to delete a digital flight progress strip from the electronic strip-bay.

The AAC EFS must [AAC-1442] provide the capability to manually arrange the digital flight progress strips in the electronic strip-bay.

The AAC EFS must [AAC-1443] provide the capability to automatically save the contents of the electronic strip-bay upon logoff.

The AAC EFS must [AAC-1444] provide the capability to automatically retrieve the information from the electronic strip-bay upon logon.

The active flight workspace will allow the Alaska CPC to create digital flight progress strips without using the handwriting input device. It also will allow the CPC to edit existing digital flight progress strips without using the handwriting input device.

The AAC EFS must [AAC-1445] include an Active Flight Workspace associated with the electronic strip-bay.

The AAC EFS must [AAC-1446] populate the Active Flight Workspace with the current active digital flight progress strip.

The AAC EFS must [AAC-1447] provide the capability to create digital flight progress strips in the Active Flight Workspace.

The AAC EFS must [AAC-1448] provide the capability to edit digital flight progress strips in the Active Flight Workspace.

The AAC EFS must [AAC-1364] provide the capability to create a digital flight progress strip template.

The AAC EFS must [AAC-1391] provide the capability to copy Site digital flight progress strip templates to User digital flight progress strip templates.

The AAC EFS must [AAC-1392] provide the capability to copy User digital flight progress strip templates to Site digital flight progress strip templates.

The AAC EFS must [AAC-1393] provide the capability to display and copy another User's digital flight progress strip templates.

The AAC EFS must [AAC-1394] provide the capability to copy another User's digital flight progress strip templates to the User Storage of the logged in User.

The AAC EFS must [AAC-1395] provide the capability to copy another User's digital flight progress strip templates to the Facility Storage of the logged in User.

To support Alaska CPC provided flight services, AAC will maintain aeronautical and weather dynamic data, maintain a database of prestored flight plans, maintain alert queues for improperly formatted messages and safety related NOTAMs received, edits of flight data, updates flight plan information, and maintain a NOTAM database.

The Respondent must [AAC-1544] maintain static reference data as required by Order JO 7210.3.

The Respondent must [AAC-1546] maintain prestored flight plans which will support Alaska CPC provided services.

The Respondent must [AAC-1547] maintain frequently used pilot/aircraft owner information which will support Alaska CPC provided services.

The Respondent must [AAC-1548] store pilot/aircraft owner contact information using AES– 128 encryption.

The Respondent must [AAC-1550] maintain frequently used information pertinent to an aircraft for use for with automatically filling common flight plan fields and for search and rescue procedures.

The Respondent must [AAC-1763] maintain an Alaska CPC Inflight Contact Database.

The Respondent must [AAC-1767] maintain an Alaska CPC Traffic Count Database.

The Respondent must [AAC-1687] provide two an integrated printers at each Alaska Hub FSS and one at each Alaska Satellite FSS.

The Respondent must [AAC-2127] provide the capability to store local knowledge associated with geographic locations in the form of static data.

The Respondent must [AAC-2128] archive a copy of the local knowledge upon creation.

The Respondent must [AAC-2130] provide the capability to display local knowledge associated with geographic locations by any site.

The Respondent must [AAC-2131] overlay local knowledge onto any earth locatable graphic map.

The Respondent must [AAC-2136] provide the capability to edit local knowledge associated with geographic locations by any site.

The System must [AAC-2137] archive a copy of the local knowledge upon editing.

The Respondent must [AAC-2139] provide the capability to delete local knowledge associated with geographic locations by any site.

The Respondent must [AAC-2140] retain the archived copies upon deletion.

The Respondent must [AAC-2141] provide the capability to copy local knowledge overlay label text from a list of nearby local knowledge overlays.

This section identifies the performance requirements, the definition of the measurements, and a definition of the loading conditions that apply to each performance requirement and measurement.

The AAC system must [AAC-3307] meet, as a minimum, the performance specifications as provided in Table 1, Table 2, Table 3, and Table 4 -

Table 1 - Product Acquisition Performance Requirements

Products Acquisition Rates Expected Product Rate and Frequency at FSS Site

WSR-88D

products

Products are acquired at the rate and frequency they are made available from the WSR-88D.

Product updates every 5,6, or 10 minutes based on individual radar site mode.

Satellite products

Satellite image data is acquired at the rate and frequency they are made available from the satellite.

1 product update every 15 minutes

Gridded products

Products are acquired at the rate and frequency they are made available from the source.

Gridded data updated every 12 hours

Graphic products

Products are acquired at the rate and frequency they are made available from the source.

Product updates every 3 hours to 12 hours based on individual product.

A/N weather products

Products are acquired at the rate and frequency they are made available from the source.

Product update as defined in NAS-IR-23040001.

The System will disseminate the products received from the source to all AFSSs within 30 seconds on average from the receipt of the last byte of data.

Functional performance requirements are defined for the various processing that occurs at the FSS site. Loading is based on a site with between 10 and 30 workstations, A/N weather data being received and processed, and weather graphic data being received and products generated.

Table 2 - FSS Site Peak Loading

Item Size (bytes)

Average Number Per Peak Hour

Total Size/Hr (bytes)

Route Oriented Briefing 5000 205 1.02 Mbytes

Pilot Weather Briefing 1500 107 160 Kbytes

Flight Plans 1000 150 150 Kbytes

Item Size (bytes)

Average Number Per Peak Hour

Total Size/Hr (bytes)

Aircraft Contacts 40 94 3760 bytes

Miscellaneous 100 1190 119 Kbytes

Column 1 of Table 2 (Item) identifies the items or types of transactions the Automation System is expected to process. Column 2 (Average Number Per Peak Hour) represents the average number of transactions to be processed by the System for the Peak Hour by an FSS. During peak operations, certain types of transactions identified in Table 2 may be imposed on the system concurrently. These concurrent transactions imposed on the system may be either manually input by the specialist or prescheduled by the specialist to occur at the same time. In either case, the System will be capable of receiving up to 58 concurrent transactions. Due to receipt of these types of concurrent transactions, the System will be capable of scheduling concurrently up to 174 messages for transmission.

For transmission, concurrent transactions are defined as the number of messages with the same scheduled transmit time. For reception, concurrent transactions are defined as the number of simultaneous incoming messages. As a minimum, these concurrent transactions should be completed two minutes prior to the scheduled retransmit time.

Some of the transactions in Column 1 of Table 2, when processed by the System, will cause the system to generate external messages to remote system interfaces. As stated above, the System will be capable of scheduling concurrently up to 174 messages for transmission. Table 3 further defines the mix of concurrent transactions and their schedule for transmission.

Table 3 - FSS Site Peak Concurrent Transaction Rates

# of Concurrent Message Types # of External Messages Scheduled for Transmission

10 Prestored Flight Plans to a single destination address, one closure point address, along with a copy to AMOC

Greater than or equal to 40 Flight Plans concurrently scheduled in the system using the IFR or FSS Transmit times to a single destination address, with a copy to AMOC and a copy to one Closure Point Address

Greater than or equal to 120

Greater than or equal to 8 General Facility messages of 15 lines (Miscellaneous) to a single destination address, one closure point address, along with a copy to AMOC

Greater than or equal to 24

Table 4 - Operational Performance Parameters

Requirement Description

Condition(s) (Product Sizes May Exceed Specified Values)

Time (seconds)

Mean 95th %-tile

99th %-tile

a) Receive, Process and Store Products

From receipt of last byte of data to completion of product storage a.1) Single Non-breakdown A/N Weather Product

500 byte product 1 1.8 2.5 a.5) Graphic Product All non-imagery graphic products 3 5.6 7.5 a.6) Individual Radar Product

3 5.6 7.5 a.7) National Radar Mosaic Product

7 10.5 14 a.8) GOES Satellite Imagery

3 5.2 7.5 a.9) Polar Orbit Satellite Imagery

3 5.2 7.5

b) A/N Weather and NOTAM Product Display

From data request entry on the user workstation to beginning of product display b.1) Weather Product Single 500 byte product 2 3.7 5 b.2) NOTAM Product Single 500 byte product 2 3.7 5 b.3) Standard Route Weather Briefing

500nm route, 2 legs, 100nm route corridor width, 400nm winds aloft corridor width, all required briefing items

2.5 4.6 6.2 b.4) Standard Area Weather Briefing Products

Area radius 300nm, low altitude, all required briefing items 2.5 3.7 5 b.5) Outlook Route Weather Briefing Products

500nm route, 2 legs, route corridor width 100nm, all required briefing items, except no current data 2.5 4.6 6.2 b.6) Outlook Area Weather Briefing Products

Area radius 300nm, low altitude, all required briefing items 2.5 4.6 6.2

Description

Condition(s) (Product Sizes May Exceed Specified Values)

Time (seconds)

Mean 95th %-tile

99th %-tile b.7) Product Weather Briefing (By LOCID)

10 LOCIDs, 3 product types 2 3.7 5 b.8) Product Weather Briefing (By State)

1 state, 1 product type, minimum of 50 products 2 3.7 5 b.9) Product Weather Briefing (Route)

500nm route, 2 legs, route corridor width 100nm, 2 product types

2.5 4.6 6.2 b.10) Product Weather Briefing (Area)

Area radius 300nm, 2 product types

2.5 4.6 6.2 b.11) Product Directory Single product type 1 1.8 2.5

c) Graphic and Imagery Product Display

From data request entry on the user workstation to beginning of display c.1) Graphic Weather Product

All non-imagery graphic products, includes map background

2 3.7 5 c.2) Graphic Weather Product

All non-imagery graphic products, includes map background and route/area overlay.

2 3.7 5 c.3) Automatically Generated Products

All non-imagery graphic products, includes map background and route/area overlay.

2 3.7 5 c.4) Radar Product (Single Station)

Includes map background and route/area overlay 2 3.7 5 c.5) National Radar Mosaic

Includes background map and route/area overlay 2 3.7 5 c.6) Satellite Imagery Includes background map and route/area overlay 2 3.7 5 c.7) Graphic Sequence 4 product single station radar sequence with map background

2 3.7 5

d) Flight Data Retrieval and Display

From data request entry on the user workstation to beginning of display d.1) Pre-stored Flight Plan Single pre-stored flight plan 1.5 3 4 d.2) Preferred Route Single preferred route 1.5 3 4 d.3) Flight Plan Single flight plan by aircraft ID 2 3.7 5

Condition(s) (Product Sizes May Exceed Specified Values)

Time (seconds)

Mean 95th %-tile

99th %-tile d.4) Flight Data Lists Single aircraft ID from Proposed, Inbound, In-flight Contacts, Suspense and Law Enforcement Lists

1 1.8 2.5 d.5) Flight Data List In-flight contacts 1 1.8 2.5 d.6) ATCSCC Traffic Messages

Any text message of at least 500 bytes 2 3.7 5 d.7) Static flight data Any static flight data set 3 5.6 7.5 d.8) Application Logon From Username/Password OK to Functional User Selection

5 9.3 12.5

e) Convert Flight Plan Data

From data request entry on the user workstation to completion of conversion e.1) Convert Domestic Flight Plan to ICAO Format

Single domestic flight plan 1 1.8 2.5 e.2) Convert ICAO Flight Plan to Domestic Format

Single ICAO flight plan 1 1.8 2.5

f) Flight Information Updates

From receipt of last byte of update information to completion of DB update.

f.1) Automatically update flight plan information

ETD change, information received from internal or external source

2 3.7 5 f.2) Automatically update a multiple in-flight work list queue

Information received from internal or external source 2 3.7 5

g) Encode-Decode From data request entered on the user workstation to response display g.1) Encode Request Single location name entry 2 3.7 5 g.2) Decode Request Single location identifier entry 2 3.7 5

h) Wild Card Search From data request entered on the user workstation to response display h.1) Encode Request Single wild card location name (actual first three letters of name provided, state identification not included

Condition(s) (Product Sizes May Exceed Specified Values)

Time (seconds)

Mean 95th %-tile

99th %-tile h.2) Decode Request Single wild card location identifier (2nd or 3rd character wild)

3 5.6 7.5 h.3) History File Transaction Search (last 24 hours)

Single wild card pilot name (first four letters of pilot name)

N/A N/A 15 min

i) Message Dissemination Within FSS Site

From transmit entry on the user workstation or equivalent to last byte received at appropriate function/position(s) i.1) All types of messages 500 bytes, includes flight, weather, alert, and administrative messages

3 5.6 7.5

j) Message Receipt from External Sources

From receipt of last byte of data to update of Proposed, Inbound and Suspense lists.

For non-flight plan message updates of alert queue.

j.1) Non-Flight Plan Messages

500 byte message 1 1.8 2.5 j.2) Flight Plan Messages from Other Alaska Flight Service Facilities

500 byte message 1 1.8 2.5 j.3) Flight Plan Messages from non- Alaska Flight Service Facilities

250 byte message (including flight plan validation) 1 1.8 2.5

k) Message Dissemination to External Sources, except Remote Workstations

From transmit entry on the user workstation or equivalent to last byte received (equivalent means automated initiation of action) k.1) Non-flight Plan Messages

500 byte message

0.5 0.9 1.2 k.2) Flight Plan Message 250 byte message (including flight plan validation and automatic addressing)

0.5 0.9 1.2

l) Message Receipt at Remote Workstation

From receipt of last byte to delivery of first byte at appropriate workstation function/position l.1) All Data Received from Alaska Flight Service Facility

500 byte message N/A N/A N/A

Condition(s) (Product Sizes May Exceed Specified Values)

Time (seconds)

Mean 95th %-tile

99th %-tile

m) Message Dissemination from Remote Workstation

From transmit entry on the Remote Workstation or equivalent to first byte received at Remote Workstation m.1) Non-flight Plan Message

500 byte message

0.2 0.4 0.5 m.2) Flight Plan Message 250 byte message 0.2 0.4 0.5

n) Alert Notification Processing

Receipt of last byte of alert message or event parameter met until alert at designated function/position(s) n.1) All Alert Notifications Alert displayed at designated position(s) 2.5 4.6 6.2

o) Flight Data Request Receipt of request message from user workstation to completion of response message/event report o.1) SAR Request A single aircraft ID, for last 24 hours, transmit response

N/A N/A N/A o.2) Event Reconstruction Request

A single aircraft ID for last 15 days, assemble hardcopy listing

N/A N/A 30 min

p) Products Display From data request entry on the user workstation to beginning of display p.1) Surface Analysis Plot Plot 3 5.6 7.5 p.2) Weather Depiction Plot

Plot 3 5.6 7.5 p.3) Radar Plot Plot 3 5.6 7.5 p.4) Pilot Report Plot Alaska Flight Service area of responsibility, at least 30 PIREPs

6 11 19 p.5) Severe Weather Forecast Alert Plot

Individual product overlay on map 6 11 19 p.6) SIGMET Plot Individual product overlay on map 6 11 19 p.7) Convective SIGMET Plot

Individual product overlay on map 6 11 19 p.8) AIRMET Plot Individual product overlay on map 6 11 19

Condition(s) (Product Sizes May Exceed Specified Values)

Time (seconds)

Mean 95th %-tile

99th %-tile p.9) Center Weather Advisory Plot

Individual product overlay on map 6 11 19 p.10) Special Use Airspace (SUA) Plot

Individual product overlay on map N/A N/A N/A

q) Requested Product From data request entry on the user workstation to beginning of product display q.1) Trend Weather Product

Single weather location 2 3.7 5 q.2) Flight Profile Product 500nm route, 2 legs, corridor width 100nm, low altitude

10 17 27

r) Manually Generated Product

From transmit entry on the user workstation to receipt of first byte r.1) Surface Weather Observation

Single observation

0.5 0.9 1.2 r.2) PIREP Single report 0.5 0.9 1.2 r.3) Data Request (Request-Reply)

Single specialist requests (excludes database restoration requests)

0.5 0.9 1.2 r.4) Data Request (Request-Reply)

Supervisory database restoration request

0.5 0.9 1.2

s) Adjust Viewing Window (Product on Screen)

From scroll or zoom/pan request entry on the user workstation to beginning of action s.1) Scroll Text product N/A N/A N/A s.2) Zoom Graphic and image product N/A N/A N/A s.3) Pan Continuous to limits of graphic N/A N/A N/A

t) Multi-product Overlays From request entry on the user workstation to beginning of display of composite product t.1) Area radar display and GOES visual imagery

With map background

Condition(s) (Product Sizes May Exceed Specified Values)

Time (seconds)

Mean 95th %-tile

99th %-tile t.2) Area radar display and GOES visual imagery

With map background and selected flight route 3 5.6 7.5 t.3) SUA and Weather Depiction Plot

With map background and selected flight route

The Respondent must [AAC-0602] establish and maintain a performance management system to ensure that the appropriate metrics are in place to manage, monitor, and report service performance.

The Respondent must [AAC-0603] maintain the performance…