D-REQUEST FOR INFORMATION, GLOBAL AIR TRAFFIC MANAGEMENT (GATM), DATA LINK SERVICES THIS IS A REQUEST FOR INFORMATION (RFI) AND NOT A REQUEST FOR PROPOSAL (RFP). The Global Air Traffic Operations/Mobility Command and Control (GATO/MC2) Systems Program Office (SPO) has the mission of supporting the acquisition of Communications, Navigation, Surveillance/Air Traffic Management (CNS/ATM) avionics for the U.S. Air Force (USAF) fleet, allowing unrestricted access of military aircraft to worldwide airspace. The intent of this RFI is to obtain market information and determine capabilities of commercial data link service options to support USAF aircraft, which are currently being equipped with commercial data link functionality. Approximately 1,765 aircraft could be equipped with High Frequency (HF), Satellite (SATCOM), and Very High Frequency (VHF) Data Link (VDL), intended to support Air Traffic Services (ATS) and Airline Operational Control (AOL) starting in 2001. FAR 52.215-3, Request for Information or Solicitation For Planning Purposes (OCT 1997) applies to this RFI. 52.215-3(c) Add thefollowing: Information will be used to assist in planning and development of acquisition strategy by the GATO/MC2 SPO and DITCO/DTS22 for eventual procurement of these services. [1] Services: The initial service required will be Aero-I SATCOM (possibly data link and voice) and HF data link in support of Aircraft Communications Addressing & Reporting System (ACARS) based Future Air Navigation System (FANS) 1 operations and limited Airline Operation Control (AOC). Support for Aeronautical Radio, Inc. (ARINC) Specification 622 must be included. It is probable some aircraft will require VDL Mode 2 service or Aero-H service in the future. Describe types of service offerings available or planned that would be most beneficial to the USAF needs. [2] ATS Approval: Initial GATM equipage is intended for use in ATS operations (e.g. Controller-Pilot Data Link Communication (CPDLC) and Automatic Dependent Surveillance (ADS)), all services offered must be approved for use in ATS operations. Discuss status of ATS approval for Aero-I SATCOM and HF data link. Include samples of Federal Aviation Administration (FAA)/Civil Aviation Authorities (CAA) approval documentation if available. [3] Coverage Area: The USAF requires maximum coverage of all data link services. Include current and planned coverage maps for each service offering, including dates for planned availability for each region. [4] Performance Objectives-discuss any concerns or issues associated with the following performance objectives: (a) end-to-end round trip time for uplinks equal to 2 minutes for 95% of messages and 6 minutes for 99% of messages; (b) end-to-end one way time for downlinks equal to 1 minute for 95% of messages and 3 minutes for 99% of messages; (c) undelivered messages must be less than 1%; (d) availability equal to 99.9%; and (e) integrity equal to 10-6. [5] Data link Service Provider (DSP) Inter-networking: The USAF will initially be using GATM for ATS purposes. Describe any inter-networking agreements in place to ensure seamless end-to-end delivery of ATS messages and any inter-networking agreements in place for AOC operations. At a minimum, discuss the nature of the agreements in place today to support FANS 1 operations in the South Pacific and how these agreements will accommodate FANS 1 operations in other regions. [6] Quality of Service: Describe how quality of service is evaluated and modified for the proposed service(s). Provide information on quality monitoring process, customer reporting, problem identification and resolution. Identify any metrics used in the quality program and include metrics for the last two months. Discuss the effects on service planning. [7] Security: Provide information on any security built into the service network that could be of benefit to the USAF. The USAF is especially concerned with the security of its AOC data link messages. Include information on industry initiatives in this area that could benefit the USAF. Include discussion of any future plans in this area. [8] Network Management: Describe in detail howthe service network is managed. Include discussion of both technical and administrative issues including redundancy and other back-up capabilities. [9] Service Planning: Provide information on how the service planning activity is performed. Include discussion on impact of network statistics as well as the frequency and type of modeling used to project future traffic loading. Advise of any projections of USAF traffic. [10] Service Initiation: Advise on how service is initiated and provide any supporting material (e.g. checklist, etc.) the USAF would complete to become a customer. Describe any avionics qualification requirements and/or third party commissioning requirements. Include recommendations on data link routing policies and preferences. Describe any network connections required/preferred to support data link operations. [11] Engineering Support: Discuss types of engineering support (both test and operational) that is provided as part of a service contract. Discuss other types of support that are available in addition to that included as part of a service contract. Provide an example of typical support and resources required for a new data link airline customer and an example for an existing customer. Include information on types of support anticipated for initial operations of the aircraft described above. [12] Financial: Describe the types of commercial service contracts available to customers today. Include discussion of both recurring and non-recurring fees, any differences between ATS and AOC message fees, and volume discounts. Describe how the service provider would manage a contract in support of the USAF. [13] Legal Concerns: Describe any legal concerns that could arise as a result of the USAF relying on a commercial data link service provider. Describe any legal requirements in place today in support of commercial airlines and ATS providers (e.g. data storage, dual routing of data, etc). [14] Growth: Include current statistics on service utilization and anticipated growth for the next ten years. Describe how the estimates are developed and if USAF aircraft are included. Include information on how services would be modified to support a planned Aeronautical Telecommunications Network (ATN). [15] Value Added Services: Describe any value added services that may be of interest to the USAF. These services could range from informational database services used by commercial airlines to unique message routing for the USAF to consolidated billing services that would ease data link service management for the USAF. Specify whether the service offering package would be "turn key" or whether additional elements would need to be procured and what they are. GATO/MC2 SPO and DITCO/DTS22 will use this information to gain an understanding of commercial operations and possible approaches available to support USAF data link operations. To adequately assess commercial services for applicability to USAF data link operations, interested companies should submit as comprehensive a package as possible. Packages should address how the service provider can support data link operations for USAF aircraft as well as identify and quantify possible risk areas or other areas where integration and/or modification would be required. At a minimum, the RFI packages should address all of the subject areas listed above. Specific data submission requirements should include the following items: (1) service descriptions; (2) network diagrams; (3) coverage maps; (4) sample ATS approval documentation; (5) recent performance statistics; (6) copies of inter-networking agreements; (7) sample of recent quality report; (8) network security information; (9) network management information; (10) service planning information; (11) description of avionics qualification program; (12) description of INMARSAT commissioning policy; (13) sample data link routing policy; (14) sample SATCOM Owner's Requirements Table; (15) list of all licenses held for Federal Communications Commission (FCC) and other global regulatory agencies, INMARSAT signatory agreements, and anythird party agreements; (16) description of applicable lab and operational facilities; (17) sample commercial data link service contract including contract type (fixed or cost type) and length of contract; (18) type of Government contract that should be considered. Include a discussion on pros/cons of the various types of contracts which the Government will select from (specific to this industry); (19) applicable legal concerns or constraints; (20) current service statistics; (21) traffic projections for the next ten years; (22) description of ATN transition plan; (23) information on any value added services; (24) discussion of any risk areas; (25) any integration or system modification requirements; (26) other issues/concerns not identified above. Note: The Government understands vendors may not be able to respond to all requested information, as such, the Government will accept partial responses to this RFI. This RFI will be posted to the DITCO Web Page on or about 8 November 1999 at http://www.ditco.disa.mil/asp/news.asp. All questions concerning this RFI shall be directed to Ms. Deborah Wellen, Contracting Officer, 618-229-9547, Email wellend@scott.disa.mil or to Mr. Cary Smith, Communications Specialist, 618-229-9457, Email Smith1c@scott.disa.mil. RFI packages are due to DITCO/DTS22, Attn: Ms. Deborah. Wellen, 2300 East Drive, Scott AFB, IL 62225-5406 NLT 4:30 p.m. CST, 8 December 1999. Due to schedule considerations, packages received after the stated time/date will not be considered. RFI packages shall be delivered in paper copies and soft copy (MS Word 7.0), seven (7) copies each.***** WEB: RFI will be available on the DITCO Contracting Opportunities, http://www.ditco.disa.mil/asp/news.asp. E-MAIL: DITCO Technical POC, Mr. Cary Smith or the Contracting, Smith1c@scott.disa.mil or wellend@scott.disa.mil. Posted 11/08/99 (W-SN398909).

Loren Data Corp. http://www.ld.com (SYN# 0440 19991110\SP-0008.MSC)