SAI SIR Section J.3 12.27.23.xlsx
XLSX spreadsheet 18 KB Posted
- Attached to
- Surface Awareness Initiative Federal contract opportunity
- Solicitation number
- 693KA7SAI
About this file
This document outlines critical requirements and performance measures for a Surface Awareness Initiative (SAI) system as part of a solicitation. The SAI system must provide increased situational awareness to air traffic control personnel through displays running surface awareness applications at airports. The applications must differentiate aircraft from vehicles, display targets detected by the SAI system within 5 nautical miles of runways, and update positions at least every 1 second for non-stationary targets. The system is required to detect over 99% of ADS-B equipped targets on airport surfaces and within coverage areas, with delays of 1 second or less between message receipt and display. Additional requirements include equipment specifications, information systems security controls, maintenance of over 99% availability, and a target loading capacity of over 200 targets. Interested offerors are encouraged to provide feedback on the final Screening Information Request documents before the response deadline pursuant to the solicitation issued by the Department of Transportation Federal Aviation Administration Enroute Terminal Contracts.
View the file
Other files for this federal contract opportunity
Show all 47
On GovTribe
Work with this file on GovTribe
- Download the original file
- Contacts named in this file
- Similar government files
- Ask GovTribe AI about this file
Text version
MRD
| Critical Requirements | Yes/No | Verification | ||
| Method | Notes | |||
| 3.1 Critical Functional Requirements | ||||
| 3.1.1 Display System | ||||
| [SAI-1] | The SAI system must include display(s) running surface awareness applications that provide increased situational awareness to ATC personnel. Note: The quantity of displays will be based on individual site surveys. | Demonstration (D) | ||
| [SAI-2] | The surface awareness application must display Targets that are detected by the SAI system and are within the defined Coverage Volume. | Demonstration (D) | ||
| [SAI-3] | The surface awareness application must differentiate aircraft from vehicles. | Demonstration (D) | ||
| [SAI-4] | The surface awareness application must include a map that accurately depicts the: | Demonstration (D) | ||
| a. Runways, taxiways, and other areas of an airport/heliport which are utilized for taxiing/hover taxiing, air taxiing, takeoff, and landing of aircraft. | Demonstration (D) | |||
| b. Gates, ramps, parking areas, and other areas of an airport where aircraft may be present. | Demonstration (D) | |||
| [SAI-5] | The surface awareness application must be user interactive, including the following basic functions: | Demonstration (D) | ||
| a. Pan | Demonstration (D) | |||
| b. Zoom | Demonstration (D) | |||
| c. Selectable Data Blocks for displayable Targets | Demonstration (D) | |||
| d. System Time | Demonstration (D) | |||
| e. Rotate the map | Demonstration (D) | |||
| [SAI-6] | The surface awareness application must display the current System State. | Demonstration (D) | ||
| 3.1.2 Surveil Target | ||||
| [SAI-7] | The source of SAI Target information must be derived from ADS-B data. | Demonstration (D) | ||
| [SAI-8] | The SAI system must detect actively transmitting ADS-B equipped aircraft. | Inspection (I) |
Demonstration (D) [SAI-9] The SAI system must detect actively transmitting ADS-B equipped ground vehicles (e.g., trucks). Inspection (I) Demonstration (D)
| [SAI-10] | The display of Targets must be configurable based on location and altitude. | Demonstration (D) | |
| 3.1.3 Equipment | |||
| [SAI-11] | The SAI display used in the tower cab must have mounting options compatible with existing tower configurations, including VESA and freestanding mounting. | Inspection (I) | |
| [SAI-12] | The display presentation must be discernable in all lighting conditions. | Demonstration (D) | |
| [SAI-13] | The display equipment must provide user controls for brightness, contrast, and sharpness. | Demonstration (D) | |
| [SAI-14] | The display must have a diagonal viewing size of at least 20 inches. | Inspection (I) | |
| [SAI-15] | The SAI system must provide its own communication networks independent of the FAA networks. | ||
| Note: Access to the FAA Admin / Mission Support networks may be granted for client-side display of targets via a web browser. | Inspection (I) | ||
| [SAI-16] | SAI equipment installed outdoors must be protected from the environment. | Inspection (I) |
Demonstration (D)
| [SAI-17] | SAI equipment installed inside of FAA facilities must not interfere with operations or existing equipment. | Analysis (A) | |
| [SAI-18] | SAI equipment connected to facility power must comply with the power quality requirements of FAA-G-2100J, Electronic Equipment, General Requirements, Paragraph 3.1.1.2 | Analysis (A) | |
| [SAI-19] | SAI solutions must adhere to FAA spectrum management requirements in accordance with FAA Order 6050.32, Spectrum Management Regulations and Procedures Manual, and FAA Order 6050.19E, Radio Spectrum Planning. | Analysis (A) | |
| 3.1.4 System Control | |||
| [SAI-20] | The SAI solution must include an interface(s) that provides control AND monitoring of the service to the service provider. | Demonstration (D) | |
| [SAI-21] | The SAI system must automatically collect service performance data in support of the Technical Performance Measures Report (TPMR). | Demonstration (D) | |
| [SAI-22] | The SAI system must automatically monitor the health of subsystems to determine the System State. | Demonstration (D) | |
| [SAI-23] | The SAI system must periodically synchronize its system time to Coordinated Universal Time (UTC). | Demonstration (D) | |
| [SAI-24] | The timestamps in all messages must be relative to UTC. | Inspection (I) | |
| 3.1.5 Information Systems Security | |||
| [SAI-25] | The SAI solution must include Information Systems Security (ISS) controls that address confidentiality, integrity, availability, and security. | ||
| Note: This requirement allows for various ISS approaches based on industry and/or Government standards (e.g., ICAO Doc-9985, ISO/IEC 27001, NIST 800-53). | Analysis (A) | ||
| 3.2 Critical Performance Requirements | |||
| [SAI-26] | The SAI system must detect ADS-B equipped Targets located on the airport surface and within 5 nautical miles of each runway threshold greater than or equal to 99 percent of the time. | Analysis (A) | |
| [SAI-27] | The SAI system must be capable of receiving AND decoding all ADS-B messages, including both 1090 Mega Hertz (MHz) and 978 MHz sources, in accordance with DO-260B AND DO-282B. | Demonstration (D) | |
| [SAI-28] | The maximum delay between the receipt of the last bit of a valid ADS-B position message at the ground station and the display of the Target on the controller application must be less than or equal to 1.0 seconds 99% of the time. | Analysis (A) | |
| [SAI-29] | All Targets within the defined Coverage Volume must be updated and maintained on the display at least every: |
1.0 sec 95% of the time for non-staionary 1090ES Targets
5.5 sec 85% of the time for stationary 1090ES Targets
| 1.3 sec 95% of the time for UAT Targets. | Demonstration (D) | ||
| [SAI-30] | The display map registration must have an accuracy of at least 20 feet. | Analysis (A) | |
| [SAI-31] | The SAI system Adjusted Service Availability must be greater than or equal to 0.99 over the preceding 12 months. | Analysis (A) | |
| [SAI-32] | The SAI system must have a Mean Time-to-Repair (MTTR) less than or equal to 0.5 hours. | Analysis (A) | |
| [SAI-33] | The SAI system Target loading capacity must be greater than or equal to 200 Targets located anywhere within the coverage area. | Analysis (A) |
PWS
| Requirements | Yes/No | Notes | |
| Operations and Maintenance | |||
| C.4.2.1 | Program Management | ||
| C.4.2.1.1 | Meeting Support | ||
| C.4.2.1.2 | Integrated Master Schedule | ||
| C.4.2.1.3 | Data Management | ||
| C.4.2.1.4 | Risk Management | ||
| C.4.2.1.5 | Configuration Management | ||
| C.4.2.2 | Systems Engineering | ||
| C.4.2.3 | Training | ||
| C.4.2.5 | System Safety | ||
| C.4.2.6 | Service Requalification Testing | ||
| C.4.2.7 | Service Performance Monitoring | ||
| C.4.2.7.1 | Discrepancy Management | ||
| C.4.2.7.2 | Discrepancy Database | ||
| C.4.2.8 | Service Monitoring, Operations, and Maintenance | ||
| C.4.2.8.1 | Customer Support Service | ||
| C.4.2.8.2 | Service Performance | ||
| C.4.2.8.3 | Service Maintenance | ||
| Implementation | |||
| C.4.2.9 | Implementation | ||
| C.4.2.9.1 | Implementation Planning | ||
| C.4.2.9.2 | Design Site Survey | ||
| C.4.2.9.3 | Site Design | ||
| C.4.2.9.4 | Site Readiness | ||
| C.4.2.9.5 | Site Implementation | ||
| C.4.2.9.6 | Service Acceptance Test | ||
| C.4.2.9.7 | Equipment Storage | ||
| C.4.2.9.8 | Damage to Site |
File details come from the government source that posted it. Updated .