Question and answers sheet for Solicitation FA460025Q0004.docx
DOCX document 15 KB Posted
- Attached to
- ACARS Messaging Support Federal contract opportunity
- Solicitation number
- FA460025Q0004
About this file
This is a Question and Answer document for Solicitation FA460025Q0004 regarding ACARS messaging support for E-4B aircraft. The document addresses technical inquiries about the Ground Host Processor (GHP) and flight following requirements.
The Q&A clarifies that 1 ACCS aircraft use the standard "MC" code through AMC's DSP-3 contract, with messages routed by ARINC and SITA nodes. The GHP vendor's role is to simplify the interface for processing AOC messages, rather than act as a "virtual airline." Regarding flight following requirements, while only 2 users can be logged in simultaneously, the system needs to accommodate up to 10 different qualified users total. The system uses commercial industry standards for ACARS communications. Messages are currently routed to a third-party GHP that processes AOC messages but not PDC, D-ATIS, or CPDLC messages.
View the file
Other files for this federal contract opportunity
| File | Type | Posted |
|---|---|---|
| Amendment 02 FA460025Q00040002 SF 30.pdf | ||
| Solicitation Amendment 01 FA460025Q00040001.pdf | ||
| Solicitation - FA460025Q0004.pdf | ||
| Statement of Work (SOW) 8 July 2024.docx | DOCX document |
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
Question and answers sheet for Solicitation FA460025Q0004
Question:
Does 1ACCS handle ACARS like an airline, or like a BA operator?
Answer:
1 ACCS aircraft are currently being serviced under the USAF’s Air Mobility Command (AMC) DSP-3 (Datalink Service Provider) contract. The IATA code being used is the standard “MC” code used by all AMC aircraft, though 1 ACCS aircraft do not actually belong to AMC. So, all of 1 ACCS’ datalink messages are routed by ARINC and are carried by either ARINC or SITA nodes. All aircraft downlink Airline Operations Center (AOC) messages are currently routed to a Ground Host Processor (3rd party) that is uniquely programmed to receive, process and reply to AOC downlinks. This GHP only processes AOC messages and does not process PDC, D-ATIS, or CPDLC messages.
Question:
Said differently, do you require your vendor to act as the “virtual airline,” an abstraction layer for handling ACARS for this opportunity? Or do you need your GHP vendor to simplify the interface with your handling of these messages?
Answer:
The Government probably falls into the category of needing the GHP vendor to simplify the interface.
Question:
In the PWS, under the Flight Following Requirements section, one of the characteristics requests the following: Capacity for up to 10 different user logins, with acknowledgement that only 2 can be logged in at any given time. Is the requirement for ten different user logins a "hard requirement" for the USAF, or can it be addressed as an upgrade feature?
Answer:
The concept is The Government will never have more than 2 individuals logged into the fight following interface at any given time. However, The Government will have up to 10 different individuals trained and qualified to act in the flight follower role. However, the vendor chooses to support this concept would be acceptable to the users.
Question:
What language does the system use to communicate?
Answer:
The system uses the commercial industry standards for ACARS communications.
File details come from the government source that posted it. Updated .