Attachment 9 - QA-AAC Ch-BA-20260410-GovernmentResponses.pdf

Item # Response Reference Question Government Response

1 General Based on the current copy available of NAS-IR-23040001 dated 08/11/2014 regarding SVC-B messaging formatting requirements;

Please confirm that the SVC-B messaging format requirements within the 7110.10 supersede all message formatting.

The AAC automation system will need to provide SVC-B messaging in accordance with examples provided FAA JO 7110.10. The messages route through NADIN (National Airspace Data Interchange Network) and include all Flight Service Station identifiers (AFTN - Aeronautical Fixed Telecommunication Network). FAA JO 7110.10 is the Flight Service order that contains formatting and examples of SVC-B messaging.

2 General What companies have an organizational conflict of interest in the AAC ChBA and a precluded from this ChBA?

The Government does not provide determinations identifying specific companies as having an Organizational Conflict of Interest (OCI) or, at this stage, being precluded from participation.

Each vendor is responsible for assessing its own potential OCI in accordance with applicable requirements and disclosing any actual or potential conflicts as part of its response. The Government will evaluate OCI considerations, including any proposed mitigation, when and as appropriate.

Nothing in this notice should be interpreted as a pre-determination regarding any vendor’s eligibility.

3 Attachment 2 - AAC Automation requirements Document Section 3.1.1

For requirement [AAC-1008] provide the capability for Alaska CPCs to perform flight planning functions in accordance with NAS-IR-23040001;

Please provide the version and date of the NAS-IR-23040001 the offeror should be in compliance with.

The Gov't has attached the updated document, dated 3/26/25.

4 Attachment 2 - AAC Automation requirements Document Section 3.1.5.1

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

Given the AAC respondent-provides a web-based, cloud automation system, (Section 2.3 Page 5), please confirm that FAA will provide the EFS device PC with touchscreen as GFE.

This requirement is for developing the software for managing flight progress strips. It includes all software and the GUI, which the vendor is responsible for developing. We are requesting a web-based software capability that works with input devices, like touch screens or tablets, to help manage digital flight progress strips as noted in the requirement. The input device allows Controllers to use stylus pens to handwrite information on the strip for quick updates.

The FAA would like to collaborate with the vendor on required specifications for the input devices as part of the AAC automation solution, and the Government will provide those devices as GFE.

5 Attachment 2 - AAC Automation requirements Document Section 3.2.1

For requirement [AAC-1687] provide two an integrated printers at each Alaska Hub FSS and one at each Alaska Satellite FSS;

Given the AAC respondent-provides a web-based, cloud automation system, (Section 2.3 Page 5), please confirm that FAA will provide the integrated printers as GFE.

The FAA will update the requirement to the following:

"The Respondent must [AAC-1687] provide the capability to print to two GFE printers at each Alaska HUB FSS and one GFE printer at each Alaska Satellite FSS”.

The Government will provide integrated printers as GFE.

6 Announcement - RFI ChBA

Paragraph 4.2b

With reference to the requirement "Response must be submitted using "12 pitch print or larger, Times New Roman style font", please confirm that font size 8 and above are permissible for graphics and tables.

Clarification - The minimum 12-point Times New Roman (or equivalent) requirement applies to narrative text. For tables and graphics, a smaller font size may be utilized where necessary;

however, it must remain clearly legible in standard viewing format (i.e., without magnification).

As a general note, font sizes for tables and graphics below 8-point are not considered acceptable. An acceptable size is 10-font or above. The Government reserves the right to determine readability during evaluation and may consider content that is not legible as non-responsive.

7 Announcement - RFI ChBA Paragraph 4.2b

With reference to the requirement "Response must be submitted using "12 pitch print or larger, Times New Roman style font"", please confirm that the "12 pitch print or larger, Times New Roman style font" requirement does not apply to screenshots and images.

Confirming - The "12 pitch print or larger, Times New Roman style font" requirement does not apply to screenshots and images.

8 Announcement - RFI ChBA Paragraph 4.2h

The following are excluded from the Concept Paper page limitation count: Cover Page; signed completed Minimum Organizational Requirements Table; and no more than three (3) Prior Experience References. Relevant Experience (not included in page count)

Please confirm that the 3 prior experience references can be included as an appendix.

Confirming - The Experience References may be included as an Appendix

9 Announcement - RFI ChBA Section 2.1

Submission date online and Section 8.3 is posted as 20 April, however, Section 2.1 has is as 17 April. Which date should the team adhere?

The Concept Paper Submission/N/A Phase I is 20 April 2026

10 Is past performance part of the technical solution page count? Yes. Any discussion of prior experience or product history is part of the Technical Solution and counts toward the eight (8) page limit. However, the submission of up to three (3) Prior Experience References (@ Announcement 4.2) are excluded from the page limitation.

11 N/A Are contract past performance write ups requested or just the discussion of product history? The RFI does not request formal contract past performance write-ups.

It is asking for product history and relevant experience descriptions

Q&A -Alaska Automation Capability (AAC Ch-BA)