Attachment 2 - DRAFT OASIS System Specification.pdf

U. S. DEPARTMENT OF TRANSPORTATION

FEDERAL AVIATION ADMINISTRATION

DRAFT SYSTEM SPECIFICATION

OASIS SYSTEM

Comments, suggestions, or questions on this document should be addressed to:

Federal Aviation Administration 800 Independence Avenue, SW

Washington, DC 20591 ii

05/31/2023

Table of Contents

1 SCOPE

1.1 Scope 16

1.2 Document Organization

1.3 System Overview

2 APPLICABLE DOCUMENTS

2.1 General 18

2.2 Government Documents

2.2.1 Government Specifications, Standards, and Handbooks

2.2.2 Other Government Documents

2.3 Non-Government Publications

2.4 Order of Precedence

3 REQUIREMENTS

3.1 System Definition

3.1.1 Functional Layouts

3.1.1.1.2 Alphanumeric Weather Briefings

3.1.1.1.2.1 Standard Weather Briefing

3.1.1.1.2.1.1 Standard Weather Briefing Products ........ Error! Bookmark not defined.

3.1.1.1.2.2 Abbreviated Weather Briefing

3.1.1.1.2.3 Outlook Weather Briefing

3.1.1.1.2.4 Delta Weather Briefing

3.1.1.1.2.5 Area Briefing Format

3.1.1.1.2.6 Region Briefing Format

3.1.1.1.2.7 Route Briefing Format

3.1.1.1.2.8 Trend Briefing Format

3.1.1.1.2.9 Selected Product Retrieval

3.1.1.1.2.10 Forecast Winds and Temperature Aloft

3.1.1.1.3 Weather Graphics

iii

3.1.1.1.3.1 Weather Graphic Products

3.1.1.1.3.1.1 NEXRAD Radar Products

3.1.1.1.3.1.2 Satellite Imagery Products

3.1.1.1.3.1.3 Gridded Data Products

3.1.1.1.3.2 Static Overlays

3.1.1.1.3.3 Dynamic Overlays

3.1.1.1.3.4 Popup Displays

3.1.1.1.3.5 Animation

3.1.1.1.3.6 Product Sequencing

3.1.1.1.3.7 Zoom, Scroll, Pan and Drag

3.1.1.1.3.8 FAA Weather Cameras

3.1.1.1.3.9 Distance Measuring

3.1.1.1.3.10 Other Overlays

3.1.1.1.4 NOTAMs

3.1.1.2 Flight Plan Processing

3.1.1.2.1 Flight Planning Functions

3.1.1.2.2 Auto Addressing

3.1.1.2.3 Manual Override of Flight Plan Fields

3.1.1.2.4 Flight Plan Field Validation

Table 3–1. Flight Plan Field Entries

Table 3–2. Route Element Formats

NOTE 58

3.1.1.2.4.1.1 Validation of Route Elements

3.1.1.2.4.1.2 Route Override

3.1.1.2.5 Process Domestic Flight Plans

3.1.1.2.5.1 Domestic Flight Plan Validation

3.1.1.2.5.2 Domestic Flight Plan Filing

3.1.1.2.5.2.1 In-Area Domestic Flight Plan Filing

3.1.1.2.5.2.1.1 In-Area Domestic VFR Flight Plan Filing

3.1.1.2.5.2.1.2 In-Area Domestic IFR Flight Plan Filing

3.1.1.2.5.2.2 Out-of-Area Domestic Flight Plan Filing

3.1.1.2.5.2.2.1 Out-of-Area Domestic VFR Flight Plan Filing

iv

3.1.1.2.5.2.2.2 Out-of-Area Domestic IFR Flight Plan Filing

3.1.1.2.5.3 Domestic Flight Plan Activation

3.1.1.2.5.3.1 Domestic VFR Flight Plan Activation

3.1.1.2.5.3.2 Domestic IFR Flight Plan Activation

3.1.1.2.5.4 Domestic Flight Plan Amendment

3.1.1.2.5.5 Domestic Flight Plan Closure

3.1.1.2.5.6 Domestic Flight Plan Cancellation

3.1.1.2.6 Process ICAO Flight Plans

3.1.1.2.6.1 ICAO Flight Plan Validation

3.1.1.2.6.2 ICAO Flight Plan Filing

3.1.1.2.6.2.1 In-Area ICAO Flight Plan Filing

3.1.1.2.6.2.1.1 In-Area ICAO VFR Flight Plan Filing

3.1.1.2.6.2.1.2 In-Area ICAO IFR Flight Plan Filing

3.1.1.2.6.2.1.3 In-Area ICAO VFR Flight Plan Filing within the NAS

3.1.1.2.6.2.1.4 In-Area ICAO IFR Flight Plan Filing within the NAS

3.1.1.2.6.2.1.5 Canadian In-Area ICAO VFR Flight Plan Filing

3.1.1.2.6.2.1.6 Canadian In-Area ICAO IFR Flight Plan Filing

3.1.1.2.6.2.2 Out-of-Area ICAO Flight Plan Filing

3.1.1.2.6.2.2.1 Out-of-Area ICAO VFR Flight Plan Filing

3.1.1.2.6.2.2.2 Out-of-Area ICAO IFR Flight Plan Filing

3.1.1.2.6.2.2.3 Out-of-Area ICAO VFR Flight Plan Filing within the NAS

3.1.1.2.6.2.2.4 Out-of-Area ICAO IFR Flight Plan Filing within the NAS

3.1.1.2.6.2.2.5 Canadian Out-of-Area ICAO VFR Flight Plan Filing

3.1.1.2.6.2.2.6 Canadian Out-of-Area ICAO IFR Flight Plan Filing

3.1.1.2.6.3 ICAO Flight Plan Activation

3.1.1.2.6.3.1 In-Area ICAO Flight Plan Activation

3.1.1.2.6.3.1.1 In-Area ICAO VFR Flight Plan Activation

3.1.1.2.6.3.1.2 In-Area ICAO VFR Flight Plan Activation within the NAS

3.1.1.2.6.3.1.3 Canadian In-Area ICAO VFR Flight Plan Activation

3.1.1.2.6.3.2 Out-of-Area ICAO Flight Plan Activation

3.1.1.2.6.3.2.1 Out-of-Area ICAO VFR Flight Plan Activation within the NAS

3.1.1.2.6.3.2.2 Canadian Out-of-Area ICAO VFR Flight Plan Activation v

3.1.1.2.6.4 ICAO Flight Plan Amendment within the NAS

3.1.1.2.6.4.1 Proposed ICAO VFR Flight Plan Amendment within the NAS

3.1.1.2.6.4.2 Active ICAO VFR Flight Plan Amendment within the NAS

3.1.1.2.6.4.3 Canadian ICAO VFR Flight Plan Amendment

3.1.1.2.6.4.4 Proposed ICAO IFR Flight Plan Amendment

3.1.1.2.6.4.5 Canadian ICAO IFR Flight Plan Amendment

3.1.1.2.6.5 ICAO Flight Plan Closure

3.1.1.2.6.5.1 ICAO Flight Plan Closure within the NAS

3.1.1.2.6.5.2 Canadian ICAO Flight Plan Closure

3.1.1.2.6.6 ICAO Flight Plan Cancellation

3.1.1.2.6.6.1 ICAO VFR Flight Plan Cancellation

3.1.1.2.6.6.2 Canadian ICAO VFR Flight Plan Cancellation

3.1.1.2.6.6.3 ICAO IFR Flight Plan Cancellation

3.1.1.2.6.6.4 Canadian ICAO IFR Flight Plan Cancellation

3.1.1.2.6.7 ICAO Composite Flight Plan Processing

3.1.1.2.7 Process Military Flight Plans

3.1.1.2.7.1 Military Flight Plan Validation

3.1.1.2.7.2 Military Flight Plan Filing

3.1.1.2.7.2.1 In-Area Military Flight Plan Filing

3.1.1.2.7.2.1.1 In-Area Military VFR Flight Plan Filing

3.1.1.2.7.2.1.2 In-Area Military IFR Flight Plan Filing

3.1.1.2.7.2.2 Out-of-Area Military Flight Plan Filing

3.1.1.2.7.2.2.1 Out-of-Area Military VFR Flight Plan Filing

3.1.1.2.7.2.2.2 Out-of-Area Military IFR Flight Plan Filing

3.1.1.2.7.2.3 Military Stopover Flight Plan Filing

3.1.1.2.7.2.3.1 VFR Military Stopover Flight Plan Filing

3.1.1.2.7.2.3.2 IFR Military Stopover Flight Plan Filing

3.1.1.2.7.3 Military Flight Plan Activation

3.1.1.2.7.3.1 Military VFR Flight Plan Activation

3.1.1.2.7.3.2 Military IFR Flight Plan Activation

3.1.1.2.7.3.3 Military Stopover Flight Plan Activation

3.1.1.2.7.3.3.1 Military VFR Stopover Flight Plan Activation

vi

3.1.1.2.7.3.3.2 Military IFR Stopover Flight Plan Activation

3.1.1.2.7.4 Military Flight Plan Amendment

3.1.1.2.7.5 Military Flight Plan Closure

3.1.1.2.7.6 Military Flight Plan Cancellation

3.1.1.2.8 Process Stereo Flight Plans

3.1.1.2.8.1 Stereo Flight Plan Validation

3.1.1.2.8.2 Stereo Flight Plan Filing

3.1.1.2.8.3 Stereo Flight Plan Amendment

3.1.1.2.8.4 Stereo Flight Plan Cancellation

3.1.1.2.9 Process ICAO DVFR Flight Plans

3.1.1.2.9.1 ICAO DVFR Flight Plan Validation

3.1.1.2.9.2 ICAO DVFR Flight Plan Filing

3.1.1.2.9.2.1 In-Area ICAO DVFR Flight Plan Filing

3.1.1.2.9.2.2 Out-of-Area ICAO DVFR Flight Plan Filing

3.1.1.2.9.3 ICAO DVFR Flight Plan Activation

3.1.1.2.9.3.1 In-Area ICAO DVFR Flight Plan Activation

3.1.1.2.9.3.2 Out-of-Area ICAO DVFR Flight Plan Activation

3.1.1.2.9.4 ICAO DVFR Flight Plan Amendment

3.1.1.2.9.4.1 Proposed ICAO DVFR Flight Plan Amendment

3.1.1.2.9.4.2 Active ICAO DVFR Flight Plan Amendment

3.1.1.2.9.5 ICAO DVFR Flight Plan Closure

3.1.1.2.9.6 ICAO DVFR Flight Plan Cancellation

3.1.1.2.10 Preferential Routes

3.1.1.2.11 Master Flight Plans

3.1.1.2.12 Aircraft Movement Message Processing

3.1.1.2.12.1.1 Civil Domestic Flight Notification Message

3.1.1.2.12.1.2 Military Flight Notification Message

3.1.1.2.12.1.3 Departure Message

3.1.1.2.12.1.4 ICAO Flight Plan Message (Proposed-Inbound)

3.1.1.2.12.1.5 ICAO Departure Message

3.1.1.2.12.1.6 IFR Flight Plan Message

3.1.1.2.12.1.7 Stereo Flight Plan Message

vii

3.1.1.2.12.1.8 Proposed VFR Flight Plan Message

3.1.1.2.12.1.9 Proposed IFR Flight Plan Message

3.1.1.2.12.1.10 Cancellation Message

3.1.1.2.12.1.11 Arrival Message

3.1.1.2.12.1.12 Change ETA Message

3.1.1.2.12.1.13 Roger Message

3.1.1.2.12.1.14 ICAO Supplementary Flight Plan Message

3.1.1.2.12.1.15 Proposed ICAO Modification Message

3.1.1.2.12.1.16 Active ICAO Modification Message

3.1.1.2.12.1.17 ICAO Arrival Message

3.1.1.2.12.1.18 ICAO Cancellation Message

3.1.1.2.12.1.19 Proposed ICAO Flight Plan Message

3.1.1.2.12.1.20 ICAO Logical Acknowledgement Message

3.1.1.2.12.1.21 ICAO Logical Rejection Message

3.1.1.2.12.2 Aircraft Movement Messages Received

3.1.1.2.12.2.1 Civil Domestic Flight Notification Message

3.1.1.2.12.2.2 Military Flight Notification Message

3.1.1.2.12.2.3 Departure Message

3.1.1.2.12.2.4 ICAO Flight Plan Message (Proposed-Inbound)

3.1.1.2.12.2.5 ICAO Departure Message

3.1.1.2.12.2.6 Proposed VFR Flight Plan Message

3.1.1.2.12.2.7 Proposed IFR Flight Plan Message

3.1.1.2.12.2.8 Cancellation Message

3.1.1.2.12.2.9 Arrival Message

3.1.1.2.12.2.10 Change ETA Message

3.1.1.2.12.2.11 Roger Message

3.1.1.2.12.2.12 Reject Message

3.1.1.2.12.2.13 Error Message

3.1.1.2.12.2.14 ICAO Supplementary Flight Plan Message

3.1.1.2.12.2.15 Proposed ICAO Modification Message

3.1.1.2.12.2.16 Active ICAO Modification Message

3.1.1.2.12.2.17 ICAO Arrival Message

vii

3.1.1.2.12.2.18 ICAO Cancellation Message

3.1.1.2.12.2.19 Proposed ICAO Flight Plan Message

3.1.1.2.12.2.20 ICAO Acknowledgement Message

3.1.1.2.12.2.21 ICAO Reject Message

3.1.1.2.12.2.22 ICAO Logical Acknowledgement Message

3.1.1.2.12.2.23 ICAO Logical Rejection Message

3.1.1.2.13 Control Message Processing

3.1.1.2.13.1 Control Messages Received

3.1.1.2.13.1.1 SUA Messages

3.1.1.2.13.1.1.1 IFR Military Training Route (IR) Messages

3.1.1.2.13.1.1.2 VFR Military Training Route (VR) Messages

3.1.1.2.13.1.1.3 MOA Messages

3.1.1.2.13.1.2 ATCSCC Messages

3.1.1.2.13.1.3 LE Messages

3.1.1.2.14 Flight Plan Conversion

3.1.1.2.14.1 ICAO to Domestic Conversion

3.1.1.2.14.2 Domestic to ICAO Conversion

3.1.1.2.15 Flight Plan Information History

3.1.1.2.15.1 Display History of User Information

3.1.1.2.15.2 Display Local Facility Completed Flight Data Transactions

3.1.1.2.16 Display Current Flight Plan

3.1.1.2.16.1 Display Partial Flight Plans

3.1.1.2.17 Display Flight Plan Lists

3.1.1.2.17.1 Display Prestored Flight Plan List

3.1.1.2.17.2 Display Proposed Flight Plan List

3.1.1.2.17.3 Display Suspense List

3.1.1.2.17.4 Display Inbound Flight Plan List

3.1.1.2.17.5 Display Inactive Flight Plan List

3.1.1.2.18 General Message Processing

3.1.1.2.18.1 General Messages Transmitted

3.1.1.2.18.2 General Messages Received

3.1.1.2.19 Law Enforcement Contact Message Processing

ix

3.1.1.2.19.1 Law Enforcement Contact Messages Transmitted

3.1.1.3 Inflight Processing

3.1.1.3.2 Digital Flight Progress Strips

3.1.1.3.3 Inflight Work Queues

3.1.1.3.4 Flight Plan Data Transfer

3.1.1.3.5 Electronic Strip-Bay

3.1.1.3.5.1 Active Flight Workspace

3.1.1.3.6 Contact List

3.1.1.4 Search and Rescue (SAR)

3.1.1.4.1 SAR Message Receipt

3.1.1.4.2 SAR Message Transmission

3.1.1.4.3 SAR Message List

3.1.1.4.4 SAR Message Cancellation

3.1.1.4.5 SAR Search

3.1.1.5 Data Management

3.1.1.5.1 Aeronautical Data

3.1.1.5.2 Weather Data

3.1.1.5.3 Static Data

3.1.1.5.4 Pre-Stored Flight Plan Database

3.1.1.5.5 Alert Queues

3.1.1.5.5.1 SVCB Message List

3.1.1.5.5.2 SVCA Message List

3.1.1.5.5.3 Runway Safety NOTAMs List

3.1.1.5.5.4 Critical OPS NOTAMs List

3.1.1.5.6 WMO Header Database

3.1.1.5.7 Flight Plan Database

3.1.1.5.8 Flight Related Updates

3.1.1.5.9 LE Database

3.1.1.5.10 NOTAM Database

3.1.1.5.11 Internal Messaging

3.1.1.5.12 Master Contact Database

3.1.1.5.13 Integrated Scanner

x

3.1.1.5.14 Integrated Printer

3.1.1.5.14.1 Color Printer

3.1.1.5.15 Secondary Storage Device

3.1.1.5.16 Standard COTS Application Software

3.1.1.5.17 General Message Database

3.1.1.5.18 MFP Database

3.1.1.5.19 Inflight Contact Database

3.1.1.5.20 Traffic Count Database

3.1.1.5.21 Master Contact Categories Database

3.1.1.5.22 View Sequence Database

Table 3–3. Configurable Parameters

3.1.1.5.23.2 Facility Parameters

3.1.1.5.23.3 User Parameters

3.1.1.5.24 Online Help

3.1.1.6 Weather Observation Processing

3.1.1.6.1 Weather Observations Processing

3.1.1.6.2 Pilot Reports Processing

3.1.1.7 NOTAM Processing

3.1.1.7.1 NOTAM Transmit Processing

3.1.1.7.2 NOTAM Log

3.1.1.7.3 NOTAM Coordination Activity

3.1.1.7.4 NOTAM Templates

3.1.1.7.5 Briefing Log Multiple Contact Logging Actions

3.1.1.7.6 MFP Responsible FSS Indicator and Call Out Order

3.1.1.7.7 NOTAM Overlay

3.1.1.7.8 Terminal Procedures and Chart Supplements

3.1.1.7.9 Facility Message List, Weather Data List, Search and Rescue (SAR) List Multiple entries deletion

3.1.1.7.10 DVFR Transponder Code Assignment Creation and Lists

3.1.1.7.11 Two-Way Communication Capability

3.1.1.7.12 GPS Device eSRS Interface in OASIS

3.1.1.8 Training Support Processing

xi

3.1.1.8.1 Configuration Training Mode

3.1.1.8.2 Scenarios

3.1.1.8.3 Operational Training Mode

3.1.1.8.4 Scenario Replay

3.1.1.8.5 Import of Weather Data

3.1.1.8.6 Export of Weather Data

3.1.1.9 Supervisory/Administrative Processing

3.1.1.9.1 Tally Reports

3.1.1.9.1.1 Traffic Count

3.1.1.9.1.2 Position Log

3.1.1.9.2 Monitor System

3.1.1.9.3 Workstation Configuration

3.1.1.9.4 User Assignments

3.1.1.9.5 Local Knowledge

3.1.1.9.6 Monitoring States and Modes

3.1.1.10 Continuous Data Recording

3.1.1.11 Event Reconstruction

3.1.1.12 Monitor and Control

3.1.1.13 Alternate Access

3.1.1.13.1 Remote User Access Terminal

3.1.1.13.2 Exportable Activity Reports

3.1.1.14 ATTV Processing

3.1.2 OASIS External Interfaces

3.1.2.1.1 AMOC

3.1.2.1.2 ERAM System

3.1.2.1.3 Flight Data Processing 2000 (FDP 2000)

3.1.2.1.4 HCS

3.1.2.1.5 NAVCANADA

3.1.2.1.6 Flight Service for the 21st Century (FS21) System

3.1.2.1.7 North American Aerospace Defense Command (NORAD)

3.1.2.1.8 Military Base Operations (MBO)

3.1.2.1.9 ATCSCC

xii

3.1.2.1.10 USNS

3.1.2.1.11 EPIC

3.1.2.1.12 Weather Message Switching Center Replacement (WMSCR)

3.1.2.1.13 FAA Weather Camera Systems

3.1.2.1.14 Foreign Air Traffic Control (ATC)

3.1.2.1.15 Advanced Technologies and Oceanic Procedures (ATOP)

3.1.2.1.16 NAS Enterprise Messaging System (NEMS)

3.2 Performance

3.2.1 Operational Performance

3.2.1.2 Operational Safety Human Factors

3.2.1.2.1 Consistency

3.2.1.2.2 Standardization

3.2.1.2.3 User-Centered Perspective

3.2.1.3 Operational Performance Response Times

3.2.2 Physical

3.2.2.1 General Physical Characteristics

3.2.2.2 Design and Construction

3.2.2.3 Materials and Parts

3.2.2.4 Equipment Size

3.2.2.5 Weight

3.2.2.6 Color and Finish

3.2.2.7 Labeling

3.2.2.8 Accessibility

3.2.2.9 Loading and Installation

3.2.2.10 Handling

3.2.2.11 Space Allocation

3.2.2.12 Structural and Seismic Stability

3.2.2.13 Grounding, Bonding, Shielding, and Lightning Protection

3.2.3 Reliability/Availability

3.2.3.2 Availability

3.2.4 Maintainability

3.2.4.2 Maintainability Functional Requirements

xii

3.2.4.3 First Level Maintenance Requirements

3.2.4.3.1 Maintenance Monitors

3.2.4.4 Second Level Maintenance Requirements

3.2.4.4.2 Maintenance Support of Software and Databases

3.2.4.4.3 Monitoring and Control

3.2.5 Recovery

3.2.5.2 Recovery from a System Reset

3.2.5.3 Recovery of Essential Data

3.2.6 Environments

3.2.6.1 General Environment Characteristics

3.2.6.2 Environmental Characteristics of the ARTCC & FSS Equipment Room System Components

3.2.6.3 Environmental Characteristics of the FSS Operations Room System Components

3.3 System Characteristics

3.3.1 Safety

3.3.1.1 Personnel Safety

3.3.1.2 Electrical Safety

3.3.1.3 System Equipment –Related Personnel Safety

3.3.1.4 Thermal Contact Hazards

3.3.1.5 Physical Hazards

3.3.1.6 Temperature Hazards

3.3.1.7 Fire Protection

3.3.1.8 Noise Hazards

3.3.1.9 Labeling and Markings

3.3.2 Security

3.3.3 Interchangeability

3.3.4 Human Factors

3.3.4.1.1 Displays

3.3.4.1.2 Data Entry

3.3.4.1.3 Maintainer Computer-Human Interface

3.4 Logistics 256

3.4.1 Maintenance

xi

3.4.2 Supply Support

3.4.2.2 Field Level Maintenance Repair

3.5 Verification Methods

4 QUALITY ASSURANCE PROVISIONS

4.1 OASIS Verification

4.1.1 Test (T)

4.1.2 Demonstration (D)

4.1.3 Analysis (A)

4.1.4 Inspection (I)

5 PREPARATION FOR DELIVERY

APPENDIX A. ACRONYMS AND ABBREVIATIONS

APPENDIX B. PERFORMANCE REQUIREMENTS

B.1 Product Acquisition Performance Requirements

Table B–1. Product Acquisition Performance Requirements

B.2 Functional Performance Requirements

Table B–2. FSS Site Peak Loading

Table B–3. FSS Site Peak Concurrent Transaction Rate

Table B–4. Operational Performance Parameters

APPENDIX C. VERIFICATION REQUIREMENTS TRACEABILITY MATRIX

Table C–1. OASIS Automation System Requirements — Verification Correlation Matrix xv

List of Tables

Table 3–1. Flight Plan Field Entries Table 3–2. Route Element Formats Table 3–3. Configurable Parameters Table B–1. Product Acquisition Performance Requirements Table B–2. FSS Site Peak Loading Table B–3. FSS Site Peak Concurrent Transaction Rate Table B–4. Operational Performance Parameters Table C–1. OASIS Automation System Requirements — Verification

Correlation Matrix

Contract Info:

1 SCOPE

1.1 Scope

This OASIS Automation System Specification establishes the functional, performance, design, construction, support and verification requirements for the Alaska Flight Service Automation system.

For ease of reference and reduction of repeated wording, the Alaska Flight Service Automation system will be referred to as: ‘the System’, 'the system’, ‘System’, or ‘system’ throughout the entirety of this document.

1.2 Document Organization

Section 1, Scope. Presents a brief overview of the OASIS specification's contents.

Section 2, Applicable Documents. Identifies the various government and industry standards referenced in this Specification.

Section 3, Requirements. Defines the functionality, products, system characteristics, external interfaces, operational and implementation aspects of the System.

Section 4, Quality Assurance Provisions. Provides a matrix of all System requirements in this specification correlated with their unique Identification Numbers and the expected verification methods.

Section 5, Preparation for Delivery.

Appendix A, Acronyms and Abbreviations. Lists the acronyms used in this document and their definitions. Defines specific terms used in this specification related to the Alaska Flight Service operations and system capabilities.

Appendix B, Performance Requirements. This appendix identifies the performance requirements of the OASIS facilities, the definition of the measurements, and a definition of the loading conditions that apply to each performance requirement and measurement.

1.3 System Overview

The OASIS system is used operationally by FAA Flight Service Specialists in Alaska. FAA Flight Service supplies weather information, aeronautical information, flight planning and flight monitoring services to general aviation pilots and other users. Alaska Flight Service users include airline transport, government, commercial, private pilots;

military, air taxi and on-demand charter Part 135 operators; domestic and international aviation interests; and public safety and law enforcement agencies.

The capabilities provided by the OASIS include alphanumeric and graphic weather product acquisition and display, flight plan processing, search and rescue services, law enforcement messages, administrative and supervisory capabilities, flight planning and regulatory information, and system maintenance functions. The weather graphic product acquisition and display capabilities include the capability to acquire, display, and store near real-time weather radar images and products, and weather satellite imagery data. The OASIS provides capabilities to acquire alphanumeric weather and aero- nautical data, as well as flight data.

Flight Service Specialists and Supervisors operate the system while Flight Service System Administrators and First Level and Second Level Engineering Maintenance personnel provide support. The Functional, External Interfaces, Government Furnished Equipment, Government Furnished Information, and System States and Modes comprise the System definition. External Interfaces to National Airspace System (NAS) systems, Non-NAS systems, and Flight Service Specialist remote access to support Air shows and temporary operations provide indirect user and system interaction with the System.

2 APPLICABLE DOCUMENTS

2.1 General

The documents listed in this section are specified in sections 3, 4, or 5 of this specification. This section does not include documents cited in other sections of this specification or recommended for additional information or as examples. While every effort has been made to ensure the completeness of this list, document users are cautioned that they must meet all specified requirements of documents cited in sections 3, 4, or 5 of this specification, whether or not they are listed.

2.2 Government Documents.

2.2.1 Government Specifications, Standards, and Handbooks

The following specifications, standards, and handbooks form a part of this document to the extent specified. Unless otherwise specified, the issues of these documents are those cited in the solicitation or contract.

FAA–G–2100H

May 9, 2005

FAA–STD–019e December 22, 2005

FAA–STD–020b May 11, 1992

DOT–FAA/CT/03–05

(HF–STD–001)

May 2003

MIL–HDBK–454B

April 15, 2007

MIL–STD–1472

January 11, 2012

NAS–IR–23040001B

August 11, 2014

Electronic Equipment, General Requirements, Specification

Lightning and Surge Protection, Grounding, Bonding and Shielding Requirements for Facilities and Electronic Equipment, Standard

Transient Protection, Grounding, Bonding and Shielding Requirements for Electronic Equipment, Standard

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

General Guidelines for Electronic Equipment, Handbook

Human Engineering, Design Criteria Standard

Operational and Supportability Implementation System (OASIS) to External Users, Interface Requirements Document

2.2.2 Other Government Documents

The following other Government documents, drawings, and publications of the exact revision level shown form a part of this document to the extent specified.

29 CFR Part 1910 Occupational Safety and Health Standards, Labor, Regulations Standards

47 CFR Part 15 Federal Regulations — Telecommunications

FMH–1 (FCM–H1–

2005) September 2005

FMH–12 (FCM–

H12–1998) December 1998

Order 1050.10D November 16, 2015

Order 1100.157A June 9, 1995

Order 1370.82A September 11, 2006

Order 3900.19B April 29, 1999

Order 6000.30F April 22, 2013

Order 6950.2D October 1, 1998

Order JO 7110.10CC April 20, 2023

Order JO 7210.3DD April 20, 2023

Order JO 7350.9EE June 15, 2023

Order JO 7930.2S December 11, 2018

SP 800–53,

Rev 4 April 30, 2013

Surface Weather Observations and Reports, Federal Meteorological Handbook No. 1

United States Meteorological Codes and Coding Practices, Federal Meteorological Handbook No. 12

Environmental Pollution Control and Abatement at FAA Facilities

Program Procedures, Operational Support (AOS)

Information Systems Security Program

FAA Occupational Safety and Health Program

National Airspace System Maintenance Policy

Electrical Power Policy Implementation at National Airspace System Facilities

Flight Services

Facility Operation and Administration

Location Identifiers

Notices to Air Missions (NOTAM)

Security and Privacy Controls for Federal Information Systems and Organizations

2.3 Non-Government Publications

The following documents form a part of this document to the extent specified. Unless otherwise specified, the issues of these documents are those cited in the solicitation or contract.

DOC 4444–ATM/501

DOC 4444–ATM/501,

Amendment 1 November 15, 2012

NFPA–70

NFPA–70E

UL 1950

UL 60950–1

December 2005

WMO–306

WMO–386

Procedures for Air Navigation Services, Air Traffic Management

Procedures for Air Navigation Services, Air Traffic Management

National Electrical Code

Standard for Electrical Safety in the Workplace

An IEC–950-Based US Standard for Information Technology Equipment Including Electrical Business Equipment

Information Technology Equipment — Safety — Part 1: General Requirements, International Standard

Manual on Codes — International Codes

Manual on the Global Telecommunication System: Annex III to the WMO Technical Regulations

2.4 Order of Precedence

In the event of a conflict between the text of this document and the references cited, the text of this document takes precedence. Nothing in this document, however, supersedes applicable laws and regulations unless a specific exemption has been obtained.

3 REQUIREMENTS

3.1 System Definition

The objective of the System is to provide users the capability/services to obtain useful, timely and accurate weather and aeronautical information to support flight planning and inflight functions.

To support this objective the system provides the capabilities to acquire, validate, retrieve, restore, store, and display information to support weather briefing, pre-flight planning, and inflight operations. In addition, the System provides remote access for specialists and pilots, provides general support functions to provide maintenance support, and provides Help functions for the users.

3.1.1 Functional Layouts

3.1.1.1 Weather Briefing

3.1.1.1.1 Alphanumeric (A/N) and Aeronautical Data

a. The System must simultaneously receive, validate, and store A/N weather data and aeronautical data messages.

[1]

b. The System must receive, validate, and store Meteorological Aviation Routine Weather Report (METAR) data.

[2]

c. The System must receive, validate, and store Aviation Special METAR (SPECI) data.

[3]

d. The System must receive, validate, and store Radar Weather Report (SD) data.

[4]

e. The System must receive, validate, and store routine Pilot Report (UA) data.

[5]

f. The System must receive, validate, and store Urgent Pilot Report (UUA) data.

[6]

g. The System must receive, validate, and store Notice to Airmen (NOTAM) data.

[7]

h. The System must receive, validate, and store FDC NOTAM data.

[8]

i. The System must receive, validate, and store NOTAM rejects.

[9]

j. The System must receive, validate, and store Area Forecast (FA) data.

[10]

k. The System must receive, validate, and store Winds and Temperature Aloft Forecast (FD) data.

[11]

l. The System must receive, validate, and store Terminal Aerodrome Forecast (TAF) data (including 30 Hr).

[12]

m. The System must receive, validate, and store AIRMET (WA) data.

[13]

n. The System must receive, validate, and store SIGMET (WS) data.

[14]

o. The System must receive, validate, and store Cyclone SIGMET (WC) data.

[15]

p. The System must receive, validate, and store Volcanic Ash SIGMET (WV) data.

[16]

q. The System must receive, validate, and store Convective SIGMET (WST) data.

[17]

r. The System must receive, validate, and store Severe Weather Watch Bulletins (WW) data.

[18]

s. The System must receive, validate, and store Convective Outlook (AC) data.

[19]

t. The System must receive, validate, and store Center Weather Advisory (CWA) data.

[20]

u. The System must receive, validate, and store Hurricane Advisory (WH) data.

[21]

v. The System must receive, validate, and store Air Traffic Control System Command Center (ATCSCC) data.

[22]

w. The System must receive, validate, and store Special Activity Airspace (SAA) data.

[23]

x. The System must receive, validate, and store Military Training Route (MTR) data.

[24]

y. The System must receive, validate, and store Military Operations Area (MOA) and Temporary Military Operations Area (TMOA) data.

[25]

z. The System must receive, validate, and store Law Enforcement (LE) aeronautical and alert data.

[26]

aa. The System must inhibit the output of superseded weather and aeronautical data.

[27]

ab. The System must inhibit the output of canceled weather and aeronautical data.

[28]

ac. For duplicate weather and aeronautical data, the System must consider the latter product as the most current and up to date.

[29]

ad. The System must be user selectable to receive, validate, and store A/N weather data that results from a World Meteorological Organization (WMO) header request.

[30]

ae. The System must be user selectable to receive, validate, and store A/N weather data that results from an individual product request.

[31]

af. The System must be user selectable to specify a list of products that when updated will alert the user.

[32]

3.1.1.1.2 Alphanumeric Weather Briefings

a. The System must provide data for weather briefings in accordance with Order JO 7110.10.

[33]

b. The System must receive, transmit, validate, and store A/N weather and aeronautical data.

[34]

c. The System must provide Standard, Abbreviated and Outlook Weather Briefings.

[35]

d. The System must provide a Delta Weather Briefing.

[36]

e. The System must provide user configurable parameters that provide filtering of a weather briefing.

[37]

f. The System must carry forward into a flight plan mask all weather briefing data fields related to flight plan functions.

[38]

g. The System must be user selectable to print a weather briefing.

[39]

h. The System must be user selectable to change weather briefing parameters after a briefing is displayed without reentry of all data.

[40]

i. The System must provide weather briefings for:

(1) Alaska

[41]

(2) Canada [42]

(3) Contiguous United States (CONUS) [43]

(4) Hawaii [44]

(5) Russia [45]

(6) Mexico [46]

3.1.1.1.2.1 Standard Weather Briefing

a. The System must provide data for Standard Weather Briefings in accordance with Order JO 7110.10.

[47]

b. The System must provide a selectable A/N text only Standard Weather Briefing.

[48]

c. Standard Weather Briefings must label, segment, and output adverse weather products to the user for the affected area, region or route corridor.

[49]

d. Standard Weather Briefings must label, segment, and output the latest surface observations to the user for the departure, destination and, alternate(s) affecting the area, region or route corridor.

[50]

e. Standard Weather Briefings must label, segment, and output the latest sur-face observations to the user for the affected area or region, and the latest enroute surface observations to the user for the affected route corridor.

[51]

f. Standard Weather Briefings must label, segment, and output the latest terminal forecasts to the user for the departure, destination and, alternate(s) affecting the area, region or route corridor.

[52]

g. Standard Weather Briefings must label, segment, and output pilot reports to the user for the affected area, region or route corridor.

[53]

h. Standard Weather Briefings must label, segment, and output the latest forecast winds and temperature aloft reports to the user for the affected area, region or route corridor.

[54]

i. Standard Weather Briefings must label, segment, and output the latest radar reports to the user for the affected area, region or route corridor.

[55]

j. Standard Weather Briefings must label, segment and output NOTAMs to the user for the area, region or route corridor.

[56]

k. Standard Weather Briefings must label, segment, and output the latest ATC delay and flow control advisories to the user for the affected area, region or route corridor.

[57]

l. Standard Weather Briefings must label, segment, and output the latest area forecast to the user for the area, region or route corridor.

[58]

(1) The System must output those portions of the area forecast that affect the user specified route.

[59]

(2) The System must output those portions of the area forecast that affect the user specified area.

[60]

(3) The System must output those portions of the area forecast that affect the user specified region.

[61]

m. Standard Weather Briefing products must be user selectable for an Area.

[62]

n. Standard Weather Briefing products must be user selectable for a Region.

[63]

o. Standard Weather Briefing products must be user selectable for a Route.

[64]

p. The System must provide the capability to request a Standard Weather Briefing from a weather briefing mask.

[65]

q. The System must provide the capability to request a Standard Weather Briefing from a flight plan display.

[66]

3.1.1.1.2.1.1 Standard Weather Briefing Products

a. Standard Weather Briefings must label, segment, and output A/N weather products and NOTAMs to the user.

[67]

b. Standard Weather Briefings must label, segment, and output the following Adverse Conditions to include:

(1) Area Forecast

[68]

(2) Convective Outlook [69]

(3) Severe Weather Warning [70]

(4) SIGMETs [71]

(5) AIRMETs [72]

(6) Center Weather Advisory NOTAMs[73]

(7) NOTAMs

[74]

c. Standard Weather Briefings must label, segment, and output the following Current Conditions to include:

(1) Surface Observation

[75]

(2) Pilot Weather Report (PIREP) [76]

(3) Radar Report [77]

(4) NOTAMs [78]

d. Standard Weather Briefings must label, segment, and output the following Forecast Conditions/Outlook to include:

(1) Area Forecast

[79]

(2) Terminal Forecast [80]

(3) Winds Aloft Forecast [81]

e. Standard Weather Briefings must label, segment, and output the following NOTAMS to include:

(1) NOTAM D (Distant) [82]

(2) GPS NOTAMs [83]

(3) LORAN NOTAMs [84]

(4) Military NOTAMs [85]

(5) ICAO NOTAMs [86]

(6) TFR NOTAMs [87]

(7) FDC NOTAMs [88]

(8) FDC Special NOTAMs [89]

(9) General FDC [90]

(10) CARF NOTAMs [91]

(11) USD NOTAMs [92]

(12) UAR NOTAMs [93]

f. Standard Weather Briefings must label, segment, and output ATCSCC information.

[94]

g. Standard Weather Briefings must label, segment, and output SUA status.

[95]

3.1.1.1.2.2 Abbreviated Weather Briefing

a. The System must provide the capability for users to provide Abbreviated Weather Briefings in accordance with Order JO 7110.10.

[96]

b. The System must provide a selectable A/N text only Abbreviated Weather Briefing.

[97]

c. Abbreviated Weather Briefings must label, segment, and output requested weather products to the user for the affected area, region or route corridor.

[98]

d. Abbreviated Weather Briefing products must be user selectable for an Area.

[99]

e. Abbreviated Weather Briefing products must be user selectable for a Region.

[100]

f. Abbreviated Weather Briefing products must be user selectable for a Route.

[101]

g. Abbreviated Weather Briefing products must be user selectable for Trend Weather.

[102]

h. The System must provide the capability to request an Abbreviated Weather Briefing from a weather briefing mask.

[103]

i. The System must provide the capability to request an Abbreviated Weather

[104]

3.1.1.1.2.3 Outlook Weather Briefing

a. The System must provide the capability for users to provide Outlook Weather Briefings in accordance with Order JO 7110.10.

[105]

b. The System must provide a selectable A/N text only Outlook Weather Briefing.

[106]

c. Outlook Weather Briefings must label, segment, and output requested weather products to the user for the affected area, region, or route corridor when the Estimated Time of Departure (ETD) is 6 or more hours from the briefing time.

[107]

d. Outlook Weather Briefings must provide the following information:

(1) Adverse conditions

[108]

(2) Forecast conditions [109]

e. Outlook Weather Briefing products must be user selectable for an Area.

[110]

f. Outlook Weather Briefing products must be user selectable for a Region.

[111]

g. Outlook Weather Briefing products must be user selectable for a Route.

[112]

h. The System must provide the capability to request a Outlook Weather Briefing from a weather briefing mask.

[113]

i. The System must provide the capability to request a Outlook Weather

[114]

3.1.1.1.2.4 Delta Weather Briefing

a. The System must provide a Delta Weather Briefing that identifies changes in weather conditions and aeronautical information between a start time and current time.

[115]

b. The System must provide a selectable A/N text only Delta Weather Briefing.

[116]

c. The Delta Weather Briefing products must be user selectable for an Area.

[117]

d. The Delta Weather Briefing products must be user selectable for a Region.

[118]

e. The Delta Weather Briefing products must be user selectable for a Route.

[119]

f. The Delta Weather Briefing products must be user selectable for Trend Weather.

[120]

g. The System must provide the capability to request a Delta Weather Briefing from a weather briefing mask.

[121]

h. The System must provide the capability to request a Delta Weather Briefing from a flight plan display.

[122]

i. The System must provide the capability to request a Delta Weather Briefing from a digital flight progress strip.

[123]

3.1.1.1.2.5 Area Briefing Format

a. The System must provide the capability for users to provide an area oriented briefing through a Standard, Abbreviated, Outlook or Trend briefing mask.

[124]

b. The System must orient A/N weather, aeronautical, and graphic data to a defined area.

[125]

c. The area radius must be configurable per area briefing.

[126]

d. The winds aloft radius must be configurable per area briefing.

[127]

e. The SPECI Time Interval user parameter must be configurable per area briefing.

[128]

f. The System must be user selectable to overlay the area briefing on any weather graphic map.

[129]

3.1.1.1.2.6 Region Briefing Format

a. The System must provide the capability for users to provide a region oriented briefing through a Standard, Abbreviated, Outlook or Trend briefing mask.

[130]

b. The System must orient A/N weather, aeronautical, and graphic data to a defined region.

[131]

c. For Alaskan region briefings, the System must orient the region briefing for one of three sub-state identifiers: AA (Anchorage), AF (Fairbanks) and AJ (Juneau).

[132]

d. For Canadian region briefings, the System must orient the region briefing for a specified province.

[133]

e. For CONUS region briefings, the System must orient the region briefing for a specified state.

[134]

f. The SPECI Time Interval user parameter must be configurable per region briefing.

[135]

g. The System must be user selectable to overlay the region briefing on any

[136]

3.1.1.1.2.7 Route Briefing Format

a. The System must provide the capability for users to provide a route oriented briefing through a Standard, Abbreviated, Outlook or Trend briefing mask.

[137]

b. The System must orient A/N weather, aeronautical, and graphic data to a defined route.

[138]

c. The route corridor width must be configurable per route briefing.

[139]

d. The winds aloft corridor width must be configurable per route briefing.

[140]

e. The System must stratify forecast winds aloft by altitude within the route corridor.

[141]

f. The SPECI Time Interval user parameter must be configurable per route briefing.

[142]

g. The System must be user selectable to overlay the route briefing on any

[143]

3.1.1.1.2.8 Trend Briefing Format

a. The System must provide the capability for users to provide a trend briefing through a Standard, Abbreviated or Outlook briefing mask.

[144]

b. A trend briefing must contain current surface observations.

[145]

c. A trend briefing must contain all surface observations received during the previous two hours.

[146]

d. A trend briefing must contain special surface observations as defined by a user configurable parameter.

[147]

e. A trend briefing must contain the Pilot Reports as defined by the user configurable parameter. [148]

f. A trend briefing must contain the current TAF.

[149]

g. A trend briefing must display current data before older data.

[150]

h. The System must be user selectable to overlay the trend briefing on any

[151]

3.1.1.1.2.9 Selected Product Retrieval

The System provides the capability to perform a selected product retrieval to request individual briefing product(s) for a specific location(s) for display.

a. The System must provide selected product retrieval for specific locations that are entered.

[152]

b. The System must provide a selected product retrieval applicable for a specified site. (e.g., — METAR, UA, TW, TAF, & NOTAM).

[153]

c. The System must provide a selected product retrieval for a specified site that is applicable for an area. (e.g., — WA, WH, WS, WST, WW, AC, CWA, FA, FD, SD, & FDC).

[154]

d. The System must provide ATCSCC messages for a selected product retrieval when the affected facility of the ATCSCC message matches the locations that are entered.

[155]

e. The System must provide NOTAM messages for a selected product retrieval when the affected facility of the NOTAM message matches the locations that are entered.

[156]

f. The System must provide IR reports for a selected product retrieval when route numbers are entered.

[157]

g. The System must provide VFR Route (VR) reports for a selected product retrieval when route numbers are entered.

[158]

h. The System must provide MOA reports for a selected product retrieval when MOA names are entered.

[159]

i. The System must provide ICAO reports for a selected product retrieval when WMO Headers are entered.

[160]

j. The System must provide the capability to enter up to 20 locations for a selected product retrieval.

[161]

k. The SPECI Time Interval user parameter must be configurable per selected product retrieval request.

[162]

l. The System must be user selectable to overlay the selected locations and product retrieval on any weather graphic map.

[163]

3.1.1.1.2.10 Forecast Winds and Temperature Aloft

a. The System must use Forecast Winds and Temperature Aloft or Gridded Winds and Temperature Aloft to interpolate for flight level winds.

[164]

b. The System must interpolate between forecast levels.

[165]

3.1.1.1.3 Weather Graphics

a. The System must receive, validate, store, and display weather graphics that provide geopolitical boundary coverage of the following:

(1) Alaska

[166]

(2) Canada [167]

(3) CONUS

[168]

(4) Hawaii [169]

(5) Russia [170]

(6) Mexico [171]

b. The System must receive, validate, store, and display weather graphics concurrently with the receipt and processing of A/N weather and aeronautical message data.

[172]

c. The System must provide and interact with industry standard Commercial-off-the-Shelf (COTS) software for the user development of local graphic products.

[173]

3.1.1.1.3.1 Weather Graphic Products

a. The System must receive, validate, store, and display National Weather Service weather graphics.

[174]

b. The System must receive, validate, store, and display National Oceanic and Atmospheric Administration (NOAA) weather graphics.

[175]

c. The System must receive, validate, store, and display Environment Canada weather graphics.

[176]

d. The System must receive, validate, store, and display Weather Depiction products (5 minute updates).

[177]

e. The System must receive, validate, store, and display AAWU Surface Analysis products.

[178]

f. The System must receive, validate, store, and display the following Composite Moisture products:

(1) Freezing Level

[179]

(2) Lifted Index [180]

(3) Precipitable Water [181]

(4) Relative Humidity [182]

g. The System must receive, validate, store, and display Lightning Data products.

[183]

h. The System must receive, validate, store, and display Constant Pressure products.

[184]

i. The System must receive, validate, store, and display Observed Wind and Temperatures Aloft products.

[185]

j. The System must receive, validate, store, and display the following Satellite Imagery products:

(1) Infrared

[186]

(2) Visible [187]

(3) Mosaic [188]

k. The System must receive, validate, store, and display the following Next Generation Weather Radar (NEXRAD) radar products:

(1) Individual Sites [189]

(2) Mosaics [190]

l. The System must receive, validate, store, and display Gridded products.

[191]

m. The System must receive, validate, store, and display the following 12 hour to 60 hour Forecast products:

(1) Significant Weather Prognosis (including 60 Hr) [192]

(2) Forecast Winds and Temperature Aloft (include direction and temperature) [193]

n. The System must receive, validate, store, and display the following Trend products:

(1) Sea Level Pressure and 1000–500 mb Thickness [194]

(2) Sea Level Pressure and 850–300 mb Thickness [195]

(3) Precipitation and Vertical Velocity [196]

(4) Height and Vorticity Analysis [197]

o. The System must receive, validate, store, and display Local Graphic products.

[198]

p. The System must receive, validate, store, and display Blank Map products.

[199]

q. The System must receive, validate, store, and display Area of Turbulence Forecast products.

[200]

r. The System must receive, validate, store, and display Thunderstorm Probability products.

[201]

s. The System must receive, validate, store, and display Icing Potential products.

[202]

t. The System must receive, validate, store, and display Collaborative Convective Forecast products.

[203]

u. The System must receive, validate, store, and display FAA Weather Camera Image products.

[204]

v. The System must receive, validate, store, and display FAA Weather Camera Clear Day Photo products.

[205]

w. The System must receive, validate, store, and display Volcanic Ash products.

[206]

x. The System must receive, validate, store, and display Hurricane Tracking products.

[207]

y. The System must display weather graphics along with supporting A/N weather data.

[208]

3.1.1.1.3.1.1 NEXRAD Radar Products

a. The System must receive, validate, store, and display Alaskan NEXRAD products for the following WSR–88D sites:

(1) Nome

[209]

(2) Bethel [210]

(3) King Salmon [211]

(4) Kenai [212]

(5) Middleton Island [213]

(6) Biorka Island [214]

(7) Pedro Dome [215]

b. The System must receive, validate, store, and display the following NEXRAD products for Seattle/Tacoma, WA, Spokane, WA, and Portland, OR:

(1) Base Reflectivity 0.5 degrees products

[216]

(2) Base Reflectivity 1.5 degrees products [217]

(3) Composite Reflectivity products [218]

(4) Velocity Azimuth Display (VAD) Wind products [219]

(5) Echo Top products [220]

c. The System must receive, validate, store, and display Radar Mosaics products.

[221]

d. The System must receive, validate, store, and display NEXRAD products on a per NEXRAD site basis.

[222]

e. The System must provide NEXRAD products with an average refresh rate at the volume scanning rate of the radar.

[223]

f. The System must provide the most current NEXRAD data available.

[224]

g. The System must provide precipitation intensity descriptors in the legend.

[225]

3.1.1.1.3.1.2 Satellite Imagery Products

a. The System must receive, validate, store, and display the following Alaskan Visible Satellite Imagery products:

(1) Bering Strait 1.6 KM

[226]

(2) Arctic Coast 1.6 KM [227]

(3) Alaska 4.4 KM [228]

(4) SE Alaska 1.1 KM [229]

(5) Alaska 1.65 KM [230]

(6) NW Alaska 1.1 KM [231]

(7) Kamchatka 1.6 KM [232]

b. The System must receive, validate, store, and display the following Alaskan Infrared Satellite Imagery products:

(1) Bering Strait 1.6 KM

[233]

(2) Arctic Coast 1.6 KM [234]

(3) Alaska 4.4 KM [235]

(4) SE Alaska 1.1 KM [236]

(5) Alaska 1.65 KM [237]

(6) NW Alaska 1.1 KM [238]

(7) AK Mosaic [239]

(8) Kamchatka 1.6 KM [240]

c. The System must receive, validate, store, and display CONUS GOES East and West satellite imagery.

[241]

d. The System must receive, validate, store, and display high resolution satellite imagery products.

[242]

e. The System must receive validate, store, and display a zoomed imagery product.

[243]

3.1.1.1.3.1.3 Gridded Data Products

The System must display gridded products made up of labeled contours and streamlines.

[244]

3.1.1.1.3.2 Static Overlays

a. The System must provide static overlays in the same projection as the weather product or base map.

[245]

b. The System must be user selectable to toggle on and off all static overlays.

[246]

c. The System must provide Latitude/Longitude overlays.

[247]

d. The System must provide Land/Sea overlays.

[248]

e. The System must provide river and lake overlays.

[249]

f. The System must provide Air Route Traffic Control Center (ARTCC) boundary overlays.

[250]

g. The System must provide Alaskan Area Forecast Subsection boundary overlays.

[251]

h. The System must provide Counties overlays.

[252]

i. The System must provide Geopolitical overlays.

[253]

j. The System must provide Airports overlays.

[254]

k. The System must provide Navigational Aids overlays.

[255]

l. The System must provide Weather Radar Site overlays.

[256]

m. The System must provide Upper Air Sounding station overlays.

[257]

n. The System must provide Routes and Airways overlays.

[258]

o. The System must provide Military Training Route overlays.

[259]

p. The System must provide Special Activity Airspace overlays.

[260]

q. The System must provide Holding Pattern Airspace overlays.

[261]

r. The System must provide Mountain Pass overlays.

[262]

s. The System must provide Canadian Flight Information Regions (FIR).

[263]

t. The System must provide Local Knowledge overlays.

[264]

3.1.1.1.3.3 Dynamic Overlays

a. The System must provide dynamic overlays of A/N weather reports and advisories on base maps and weather graphics.

[265]

b. The System must provide Pilot Report/Urgent Pilot Report dynamic overlays.

[266]

c. The System must provide Severe Weather Forecast Alert dynamic overlays.

[267]

d. The System must provide SIGMET dynamic overlays.

[268]

e. The System must provide Convective SIGMET dynamic overlays.

[269]

f. The System must provide Volcanic Ash SIGMET dynamic overlays.

[270]

g. The System must provide AIRMET dynamic overlays.

[271]

(1) The System must provide CONUS G-AIRMET dynamic overlays.

[xxxx]

h. The System must provide Temporary Flight Restrictions (TFR) dynamic overlays.

[272]

i. The System must provide CWA dynamic overlays.

[273]

j. The System must provide METAR/SPECI dynamic overlays.

[274]

k. The System must provide FAA Weather Camera dynamic overlays.

[275]

l. The System must provide Area Forecast dynamic overlays.

[276]

m. The System must provide TAF dynamic overlays.

[277]

n. The System must provide SAA dynamic overlays.

[278]

3.1.1.1.3.4 Popup Displays

b. The System must provide popup displays on any earth locatable graphic map.

[279]

c. The System must be user selectable to display the following from the context menu of any earth locatable graphic product:

(1) Sectional Charts

[280]

(2) Weather Cameras [281]

(3) IFR En Route High and Low Altitude charts

[282]

(4) Airport Diagrams [283]

(5) Sunrise, Sunset, and Civil Twilight information [284]

3.1.1.1.3.5 Animation

a. The System must automatically update an animation loop when a new product is received.

[285]

b. The System must be user selectable to adjust the animation speed in frames per second.

[286]

c. The System must be user selectable to adjust the pause time between animation loops.

[287]

d. The System must be user selectable to manually step through the animation loop.

[288]

e. The System must be user selectable to continuously run an animation loop.

[289]

f. The System must be user selectable to remove images from the animation loop.

[290]

3.1.1.1.3.6 Product Sequencing

a. The System must be user selectable to store a graphical product sequence.

[291]

b. The System must be user selectable to edit a graphical product sequence.

[292]

c. The System must be user selectable to delete a graphical product sequence.

[293]

d. The System must be user selectable to display a sequence of products that has been stored.

[294]

e. The System must be user selectable to automatically sequence through a display of selected products.

[295]

f. The System must be user selectable to select the time between displays.

[296]

g. The System must be user selectable to manually step through product sequence.

[297]

3.1.1.1.3.7 Zoom, Scroll, Pan and Drag

a. The System must be user selectable to zoom and scroll through a weather graphic map.

[298]

b. The System must be user selectable to pan and drag a weather graphic map.

[299]

c.