PSIR-APC-01 Industry Day 4_21_2021 FINAL.pdf

Federal Aviation AdministrationFor Official Use Only 2April 21, 2021

Voice over IP Communications Enterprise (VoICE) Air-to-Ground Protocol Converter (APC) System

Pre-solicitation Virtual Industry Day

(693KA8-21-PSIR-APC-01)

April 21, 2021

AdministrationFor Official Use Only 3April 21, 2021

• Introduction

• APC System Overview

• APC System Acquisition Summary

• Break (15 minutes)

• High-level Acquisition Strategy and Source Selection

• Request for Information & Instructions for Submittals

• Wrap-Up

APC System Pre-solicitation Industry Day Agenda

AdministrationFor Official Use Only 4April 21, 2021

Industry Day Panelists

FAA Employees

• Mary Johnson – Contracting Officer

• Clarissa Riffe – VoICE Program Manager

• Doug Sanders – Program Lead

• Marty Peterson – Technical Lead

FAA Support

• Jeff Hall

• Pearl Sun

AdministrationFor Official Use Only 5April 21, 2021

Responsibility & Disclaimer

• Industry is responsible for becoming knowledgeable on the FAA’s acquisition processes, terms and conditions, public law, etc.

• Some general information related to acquisition terms and conditions will be presented.

• The information provided and discussed during this meeting does not relieve offerors from becoming knowledgeable of the acquisition process or of meeting the requirements, terms, and conditions of any future SIR.

• Any written information provided by the FAA to industry takes precedence over the information provided and discussed during this meeting.

AdministrationFor Official Use Only 6April 21, 2021

Q&A Function:

– Use the Q&A function of Zoom

– Questions are seen by panelist only

Questions will be reviewed and answered, to the best of our ability, during the meeting.

Questions During the Meeting

AdministrationFor Official Use Only 7April 21, 2021

Release of Industry Day Presentation

• Presentation will be posted on beta.SAM through announcement 693KA8-

21-PSIR-APC-01

• Questions received in response to this industry day will be reviewed and responses may be released.

AdministrationFor Official Use Only 8April 21, 2021

APC System Overview

AdministrationFor Official Use Only 9April 21, 2021

VoICE Program Overview

• The global voice communications industry has evolved from TDM-based architecture with analog interfaces to a native Voice over Internet Protocol (VoIP) architecture.

– Most of the FAA’s legacy VS&R infrastructure is being sustained until the next Voice Communications System (VCS) is available.

– VoIP voice switch systems are now operational with Air Navigation Service Providers (ANSP) for international Air Traffic Management (ATM).

• The FAA has consulted the marketplace to validate the VCS acquisition strategy and to update the requirements.

ARTCC

TRACON

ATCT

AdministrationFor Official Use Only 10April 21, 2021

• The VoICE acquisition will replace aging voice switching core infrastructure at Air Traffic Control Towers (ATCTs), Terminal Radar Approach Control facilities (TRACONs), and Air Route Traffic Control Centers (ARTCCs) with a modern and supportable VoIP-enabled, networked voice communication system enterprise

• VoICE will consist of IP-analog APC System and GPC System combined with native-VoIP switching systems (Voice Communications Systems – VCSs)

– The APC System and GPC System can provide interface capability for the new native IP switches as well as for existing legacy switches during the extended voice communication transition from legacy analog to VoIP. The APCS will replace the existing legacy Radio Control Equipment (RCE) in the

NAS.

VoICE Program Overview

AdministrationFor Official Use Only 11April 21, 2021

VoICE Phases Diagram

AP

C

S Pr oc ur em en t

PHASE 1

IP-Analog

A/G Interface

VC

S

Pr oc ur em en t

VoIP Voice

Switch

PHASE 2

PRESENT FUTURE

G

PC

S Pr oc ur em en t

IP-Analog G/G

Interface

PHASE 1

AdministrationFor Official Use Only 12April 21, 2021

RCE to APCS

• Current Radio Control Equipment (RCE) is facing supportability issues and is only designed to communicate using analog interfaces.

• The RCE:

– Is used for Air traffic control applications where audio and radio signals needed to be transported to remote radio facilities (i.e., off airport grounds).

– Enables FAA air traffic control facilities to cover a larger geographic area through the use of remotely-located radios and antenna equipment.

– Provides simultaneous voice and data transmission over point-to-point leased 4-wire telephone lines.

– Supports primary and backup telephone line capabilities as well as adaptable connection modes to support dual control and separate radio site configurations (i.e., a transmitter site and a receiver site).

*****Respondents are encouraged to request RCE technical documentation from the FAA Contracting Officer. Documents are not available under the public notice, but will be provided separately, at the FAA’s discretion, by email upon request by any legitimate, interested company.

AdministrationFor Official Use Only 13April 21, 2021

RCE Migration to APCS Current Radio Control Equipment (RCE)

• C-RCE to VCS interface is analog (i.e., analog audio and discrete signaling)

• C-RCE to R-RCE interface is analog (4-wire analog phone service)

• Analog WAN is a voice-grade 4-wire telephone circuit

• R-RCE to radio interface is analog (i.e., analog audio and discrete signaling)

• C-RCE and R-RCE typically deployed in pairs but ability to control a single R-RCE from two control sites (i.e., two separate C-RCEs) is also used in some instances

• Some radio sites may be difficult to transition to IP services because of infrastructure (e.g., “last mile” of a radio site that sits on top of a mountain)

Legacy VCS C-RCE R-RCE

Radio

Radio

Radio

Radio

Radio

Radio

Radio

Radio

Analog Analog Analog

Analog

FTI

Analog Service

(“WAN”)

Control Site ATCT, TRACON, or ARTCC

Remote Radio Site RCAG, RTR, etc.

Analog

Note: Simplified view does not represent every component or element

AdministrationFor Official Use Only 14April 21, 2021

RCE Migration to APC System APCS migration for FAA In Service Decision (Nov 2025) – “VoIP First”

• L-APC to VCS interface will be analog

• L-APC to R-APC interface will be ED-137C VoIP

• WAN will support IP

• R-APC to radio interface will need to support both ED-137C and analog

• C-RCE and R-RCE will be replaced at the same time (i.e., as pairs)

• FAA’s intent is to align with FENS transition if possible to avoid transitioning the radio sites twice (once to analog FENS service and later to IP)

• FAA has identified sites that can be transitioned to immediately in IP mode while vendor adds the analog link capability between L-APC and R-APC

• Analog option is for sites where providing IP services is problematic

Legacy VCS L-APC R-APC

Radio

Radio

Radio

Radio

Radio

Radio

Radio

Radio

Analog ED-137C VoIP

ED-137C

VoIP Analog and

ED-137C

VoIP

FENS

IP

Service

(“WAN”)

Control Site ATCT, TRACON, or ARTCC

Remote Radio Site RCAG, RTR, etc.

Note: Simplified view does not represent every component or element

AdministrationFor Official Use Only 15April 21, 2021

APCS – VoIP First Approach

• Approach

– Market research shows Analog Link capability is not prevalent in current industry offerings

– FAA will defer development and testing of the Analog Link until after FAA achieves In Service Decision

(ISD) – planned for November 2025

– Allows faster deployment using existing ED-137C VoIP Link (will still need to meet all VoIP requirements)

– Faster deployment mitigates risk associated with obsolete RCE equipment (recover and reuse RCEs)

• Technical Requirements

– The contract will include all APC system requirements (VoIP Link and Analog Link); the difference is the timing of developing, testing, and deploying the capabilities.

– VoIP-first approach does not impact L-APC to VCS interface requirements for ISD.

– VoIP-first approach does not impact R-APC to radio interface requirements for ISD.

• VoIP Link for ISD

– The FAA plan is to require support for the VoIP Link between L-APC and R-APC be provided for FAT and

System Test (i.e., tested for ISD)

• Analog Link after ISD

– FAA will require that the addition of the Analog Link capability between L-APC and R-APC be priced at award and the capability will be added to the APC System after FAA achieves ISD using the FAA’s Engineering Change Proposal (ECP) process (see SOW C.4.9.4.3)

– The ability to upgrade the APC System to include the analog communication link capability will be a factor at contract award. Section M will provide the relative importance vs other evaluated factors.

AdministrationFor Official Use Only 16April 21, 2021

Cont’d APC – VoIP First Approach

• One baseline or two?

– As long as the Analog Link capability meets contract requirements, the FAA will consider solutions that involve updates to the initial hardware baseline or a separate hardware baseline for APC Analog Link capability (e.g., different part numbers for the two solutions).

• Form Factor

– The form factor for the analog solution must still meet the physical space requirements in the specification.

• Early Deployments will be VoIP

– The FAA will prioritize sites with IP connectivity for the early deployments and does not envision retrofitting any site with Analog Link capability once deployed with IP WAN capability.

AdministrationFor Official Use Only 17April 21, 2021

APC Acquisition Summary

AdministrationFor Official Use Only 18April 21, 2021

FAA’s Acquisition Management System (AMS)

• Procurement will be funded through the

FAA’s Airport & Airway Trust Fund (AATF), specifically Facilities & Equipment (F&E).

• The FAA will adhere to the programmatic and acquisition processes and policies defined by the AMS.

• Information is available at:

– Programmatic Policy:

https://fast.faa.gov/NFFCA_NAS_FE_Funded_Capital_Assets.cfm

– Procurement Policy - https://fast.faa.gov/PPG_Procurement.cfm

AdministrationFor Official Use Only 19April 21, 2021

FAA Acquisition System Toolset

- Overview

• Walk through - https://fast.faa.gov/

Provides:

Programmatic milestone information Acquisition information https://fast.faa.gov/

AdministrationFor Official Use Only 20April 21, 2021

Purpose of APC System Procurement

• Deploy an A/G interface capability that converts between analog voice/signaling and EUROCAE ED-137C-compliant VoIP

• Replace aging RCE with an IP-compatible capability

AdministrationFor Official Use Only 21April 21, 2021

Acquisition Scope Delta design, development, test, and implementation of the APCS

– The FAA is anticipating approximately 27,000 total APC interfaces

• L-APC – roughly 11,000

• R-APC – roughly 11,000

• LLR-APC – roughly 5,000

– The FAA is anticipating approximately 350 Control Sites

• The 21 ARTCCs range from about 100 to 300 total APCs each with a median of 160

• The 330 Terminal facilities range from 1 to 80 total APCs with a median of 7

• Includes program management, systems engineering, test and evaluation, delivery, and installation, integrated logistics support (including training), and operational support

AdministrationFor Official Use Only 22April 21, 2021

Contract Summary

• Full and open competition

• Complex Source Selection

• Single contract award

• Estimated Contract Award FY23 3rd Quarter

• Total period of performance – 10 years

AdministrationFor Official Use Only 23April 21, 2021

High-level Acquisition Strategy and Source Selection

AdministrationFor Official Use Only 24April 21, 2021

APC Notional Schedule (PSIR Section 7.2.1) Draft SIRs provided for industry review and feedback.

– Draft SIR Part A - 693KA8-21-PSIR-APC-01:

• Acquisition strategy, Statement of Work, and various J Attachments including CDRLS/DIDs

• Open, responses due May 7, 2021

– Draft SIR Part B - 693KA8-21-PSIR-APC-02:

• Anticipate draft Section B, Supplies or services and prices/costs; Section H, Special contract requirements; Section L, Instructions, conditions, and notices to offerors; Section M, Evaluation factors for award

• Anticipated release: May 24, 2021

• Anticipated response date: June 21, 2021

• Anticipated Final APC SIR: FY22 2nd Quarter

• Estimated Contract Award FY23 3rd Quarter

AdministrationFor Official Use Only 25April 21, 2021

APC Contract Type (PSIR Section 7.2.2)

• Anticipate single award

– COTS delta design, development, test, and implementation of the APC is intertwined

– Multiple awards or splitting of the requirement would be duplicative

• Contract price is closely related to contract type - type is determined through consideration of:

– Nature and complexity of the requirement

– Degree to which requirements can be described

– Performance period

– Need for incentives

– Urgency

– Market conditions

– Industry practices

– Procurement history

AdministrationFor Official Use Only 26April 21, 2021

Con’t APC Contract Type (PSIR Section 7.2.2)

• Appropriate contract type results in:

– Reasonable cost/price and reasonable contractor risk

– Efficient and economical contractor performance.

BUYER’S RISK

SELLER’S RISK

LOW

LOWHIGH

HIGH

Fixed Price (FP)

FFP

FP-EPA

FPIF

Time & Material Cost Reimbursable

CPFF

CPAF

CPIF

AdministrationFor Official Use Only 27April 21, 2021

Con’t APC Contract Type (PSIR Section 7.2.2)

• Example FFP CLINs:

– Program Management

– Training Course Conduct

• Example Non-FFP CLINS:

– FAA-Conducted Test Support

– System Engineering

• A combination of contract types, assigned to specific contract line item numbers (CLINs), is appropriate.

AdministrationFor Official Use Only 28April 21, 2021

Con’t APC Contract Type (PSIR Section 7.2.2)

• Draft SIR Part B - 693KA8-21-PSIR-APC-02 will request:

– Input to draft Section B

– Recommendations for incentivizing performance

AdministrationFor Official Use Only 29April 21, 2021

Applicability of the Buy American Requirements (PSIR Section 7.2.3) The APC will be considered a Manufactured Product (T3.6.4(A)4), FAA Buy American - Steel and Manufactured Products and 49 U.S.C §50101

For manufactured end products, the Buy American statute uses a two-part test to define a domestic end product.

• The article must be manufactured in the United States; and

• The cost of domestic components must exceed 50 percent of the cost of all the components. This component test of the Buy American statute has been waived for acquisitions of information technology COTS items.

Labor costs involved in final assembly are not included in calculating the cost of components.

AdministrationFor Official Use Only 30April 21, 2021

Cont’d Buy American Requirements (PSIR Section 7.2.3) Buy American Act also applies to end items/supplies required for performance of the contract (T3.6.4(A)2, Buy American Act – Supplies)

– The article must be manufactured in the United States; and

– The cost of domestic components must exceed 50 percent of the cost of all the components.

Industry should submit specific questions, including facts, for FAA consideration and review.

Draft SIR Part B - 693KA8-21-PSIR-APC-02 will request input to the Buy American Act clauses and certification requirements.

Applicable AMS Clauses:

3.6.4-2 Buy American Act – Supplies 3.6.4-5 Buy American - Steel and Manufactured Products 3.6.4-15 Buy American Act Certificate 3.6.4-18 Certification Regarding Steel and Manufactured Products

AdministrationFor Official Use Only 31April 21, 2021

NDAA Section 889, Prohibition on Certain Telecommunications and Video Surveillance Services (PSIR Section 7.2.4)

Recommendation for clause interpretation and completion:

1. Read and understand clause 3.6.4-23 – the definitions apply to both 3.6.4-22 and 3.6.4-24

2. Read and understand clause 3.6.4-22

3. Read and understand clause 3.6.4-24

3.6.4-22 Representation Regarding Certain Telecommunications and Video Surveillance Services or Equipment Represents whether covered telecommunications equipment or services will or will not be provided in performance of the contract.

Represents does or does not use covered telecommunications equipment or services, or use any equipment, system, or service that uses covered telecommunications equipment or services.

*** Clause references both 3.6.4-23 and 3.6.4-24 ***If responding “will” or “does”, additional information is required

3.6.4-23 Prohibition on Contracting for Certain Telecommunications and Video Surveillance Services or Equipment

3.6.4-24 Covered Telecommunications Equipment or Services- Representation Representation is similar to 3.6.4-22 and responses should be consistent

AdministrationFor Official Use Only 32April 21, 2021

Organizational Conflict of Interest (OCI) (PSIR Section 7.2.5) An OCI means that because of existing or planned activities, an offeror or contractor:

– Is unable or potentially unable to render impartial assistance to the agency; or

– Has an unfair competitive advantage; or

– The offeror or contractor's objectivity is or might be impaired.

****Resources:

• AMS Procurement Guidance T3.1.7 Organizational Conflict of Interest

• Federal Acquisition Regulation (FAR) Subpart 9.5

AdministrationFor Official Use Only 33April 21, 2021

Con’t Organizational Conflict of Interest (OCI) (PSIR Section 7.2.5)

AMS OCI clauses:

3.1.7-2 Organizational Conflicts of Interest 3.1.7-4 Organizational Conflict of Interest - Mitigation Plan Required 3.1.7-5 Disclosure of Conflicts of Interest 3.1.7-1 Exclusion from Future Agency Contracts

****Resources:

• AMS Procurement Guidance T3.1.7 Organizational Conflict of Interest

• Federal Acquisition Regulation (FAR) Subpart 9.5

AdministrationFor Official Use Only 34April 21, 2021

Con’t Organizational Conflict of Interest (OCI) (PSIR Section 7.2.5) Examples – also reference Federal Acquisition Regulation (FAR) Subpart 9.5

• Unequal Access to Information. Access to "nonpublic information" as part of the performance of an FAA contract, grant, cooperative agreement, or other transaction agreement that could provide the contractor a competitive advantage in a later competition for another FAA contract.

• Biased Ground Rules. A contractor in the course of performance of an FAA contract, grant, cooperative agreement, or other transaction agreement, has in some fashion established important "ground rules" for another FAA acquisition, where the same contractor may be a competitor.

• Impaired Objectivity. A contractor in the course of performance of a FAA contract, grant, cooperative agreement, or other transaction agreement, is placed in a situation of providing assessment and evaluation findings over itself, or another business division or a subsidiary of the same corporation, or another entity with which it has a significant financial relationship.

AdministrationFor Official Use Only 35April 21, 2021

APC System Source Selection (PSIR Section 7.2.6)

• Source selection will be based on the best value

– Both cost/price and non-cost/price factors are assessed based on the evaluation criteria

– The solicitation will identify the evaluation factors and the relative importance

– The source selection official (SSO) selects the Offeror representing the best value to FAA

• The FAA anticipates use of the two-phase source selection procedure defined in Procurement Guidance T3.2.2.3(B)9.

– Guidance uses the term “Phase” to refer to the different steps in the process.

– VoICE Program has consistently used the term “Phase” to refer to the different phases of the VoICE program.

– To avoid confusion, the FAA word “Phase” is replaced with “Stage” when referring to the two-phase source selection procedure defined in Procurement Guidance T3.2.2.3(B)9.

AdministrationFor Official Use Only 36April 21, 2021

Con’t APC System Source Selection (PSIR Section 7.2.6)

• Notional two-phase source selection (Procurement Guidance

T3.2.2.3(B)9)

– Stage 1 / Screening Information

• Anticipate 20 business days for proposal submission

• Evaluation will be based on key differentiators

– Stage 2 / Solicitation for Offer - Contracting Officer will request/solicit offers only from sources selected in Stage 1

• Anticipate 40 business days for proposal submission

• The SIR will fully describe the process and requirements for submission of proposals for both Stage 1 and Stage 2

AdministrationFor Official Use Only 37April 21, 2021

APC Evaluation Factors (PSIR Section 7.2.7) Anticipated evaluation factors:

• Management/Technical

• Program Management

• System Engineering

• Test and Evaluation

• Integrated Logistics Support

• Production and Deployment

• Past Performance

• Cost/Price Realism (Reference FAA Procurement Guidance T3.2.3(1)(d)(5)) -

Allows increased focus on realism:

Ensures alignment between price, technical approach, and schedule Realism analysis determines whether an offeror’s proposed costs and/or prices:

• Are realistic for the work to be performed;

• Reflect a clear understanding of the requirements; and

• Are consistent with the various elements of the offeror's technical proposal.

• Cost/Price (excluding realism)– evaluation of whether prices or costs are allowable and reasonable.

AdministrationFor Official Use Only 38April 21, 2021

Request for Information & Instructions for Submittals

AdministrationFor Official Use Only 39April 21, 2021

Submission of Information

Pre-solicitation Part A - 693KA8-21-PSIR-APC-01

Due May 7th:

– Comments, questions, recommendations related to draft

SOW/specification and acquisition strategy

– Notification of interest in the APC procurement

• Pre-solicitation Industry Comment Form – required for responses to PSIR Sections 7.1 and 7.2

• Vendor Notification of Interest Form – required for responses to PSIR Section 7.4

AdministrationFor Official Use Only 40April 21, 2021

Purpose of Sources Sought/Solicitation of Interest

• Inform the FAAs acquisition approach related to small business participation

• Information will help formulate small business subcontract goals

• The FAA does not intend to facilitate teaming arrangements or bring together prime and subcontractors.

• Solicitation of Interest Form fill-in:

– Industry teams may complete a single form

– Small businesses should identify specific parts of the requirement that are of interest

• Draft SIR Part B - 693KA8-21-PSIR-APC-02 will request:

– Input to small business subcontracting goals

AdministrationFor Official Use Only 41April 21, 2021

Distribution of Vendor Comments / FAA Responses

• All public notices have stated that the FAA's intention is that comments and responses will be distributed electronically to all potential Offerors via the beta.SAM website.

– The FAA reserved the right to withhold comments and responses.

• If submitting proprietary/confidential or competition sensitive information, the vendor must include appropriate markings.

• The FAA does not commit to answering questions or comments directly.

– Must result in a positive impact on acquisition

– Must not increase risk associated with meeting the acquisition SIR release schedule.

AdministrationFor Official Use Only 42April 21, 2021

• Based on responses to previous NAS VoICE beta.SAM notices and responses to this announcement, the FAA may hold one-on-one meetings with vendors.

• One-on-one meetings will be used to:

– Solicit clarification or seek additional detail associated with submitted comments, questions, or recommendations

– Improve the quality of the SIR

– Increase competition

– Positively impact the requirements

• The FAA will not hold one-on-one meetings that will increase risk associated with meeting the acquisition SIR release schedule.

Vendor One on Ones

AdministrationFor Official Use Only 43April 21, 2021

Technical Questions

AdministrationFor Official Use Only 44April 21, 2021

Technical Questions Question: In Phase 2 we noticed the priority to replace the voice switches at the ARTCCs and Core Terminal facilities. Could this mean that the acquisition of the Large VCS could take place before the Small ones?

FAA Response: Yes, the FAA is still formulating its strategy for VCS procurements and will determine the scope and schedule some time this coming fall. The factors driving the decision will include addressing risk to the NAS, providing communications capabilities for new facilities, and providing new capabilities that come with the new native-VoIP systems. Risk to the NAS is driven in large part by the sustainability of the current voice switching systems. Because of the number of control facilities in the NAS, the FAA is constantly replacing control tower and TRACON facilities with new buildings. The FAA does not typically replace the large en route facilities. We need to be able to provide a VCS for these new tower and TRACON facilities. Also driving the decision is the desire to enable the capability provided by the new VoIP technology, such as the ability to address operational contingency and business continuity risks. These factors will all play a part in deciding which VCS procurement is prioritized and what the scope of each of the VCS procurements will ultimately be.

Question: Draft spec states “Note: A maximum of 6 SIP Sessions is a placeholder and may change based on proposed Vendor solutions (e.g., redundant paths)". Please clarify the "redundant paths" concept. Is it required to use some of the 6 SIP sessions as redundant path or is it requested to provide each of the 6 SIP sessions with its own redundant path (in total 12 SIP sessions)?

FAA Response: In the APC System Specification (20210325r1), 6 SIP sessions were provided as a place holder in relation to single connections for up to 6 VoIP VCSs. If redundant paths are proposed in a Vendor's solution to meet the FAA's requirements, then there would be a total of 12 SIP sessions. The FAA will update the requirements to state that the APC system must support a maximum of 12 SIP sessions to be in line with supporting up to 6 VoIP VCSs with redundant paths.

AdministrationFor Official Use Only 45April 21, 2021

Cont’d Technical Questions Question: Draft spec states "The R-APC must provide eight individual Ethernet ports to support connections for up to eight VoIP Radios". Is this request asking for eight physical Ethernet connectors on each APC to link up to 4Rx+4Tx?

FAA Response: Yes, to meet the referenced requirement, the R-APC must provide eight physical Ethernet connectors to support up to 4 VoIP (ED-137) Transmitters and 4 VoIP (ED-137) Receivers.

Question: The initial APC configuration foresees using IP connectivity only, does that mean no other links would be available for Management purpose?

FAA Response: Correct, requirement 3.1.10.f in the draft APC System Specification (20210325r1) states that when there are IP connections available, remote monitoring, maintenance, and configuration of the R-APC will be performed via IP and the management subsystem would located at the local facility.

Question: Is the VOX principle indicated to use a well defined algorithm? Or is it possible to get the result required by using the voice signal power value?

FAA Response: The VOX Operation requirements in section 3.2.1.10 of the draft APC System Specification (20210325r1) stand as written. The method of implementation utilized to meet these requirements is left up to the Vendor.

Question: Is the ITU-T G729 coding required on the WAN connections only or also toward the Radios connected to the APC unit?

FAA Response: Per section 3.2.1.12 of the draft APC System Specification (20210325r1), the APC must support both ITU-T G.711 and ITU-T G729a coding, which would apply to both WAN and IP Radio connections.

AdministrationFor Official Use Only 46April 21, 2021

Cont’d Technical Questions Question: Draft spec 3.5 & 3.5.1, is the "multiple" units solution more probable at the local VCS Sites mainly or also at remote Radio Sites? Can the vendor assume that at the radio sites that no vendor rack would be required and all the space, ventilation, over heath alarms, etc. would be available and provisioned by the FAA? Can the same assumption be made for VCS sites (or wherever no racks are required) where multiple APCs in a single 19" standard chassis shall be installed? Would it be possible to know which sites where extra Rack(s) will be required to be provided by the vendor to satisfy the local configurations? That will permit the correct completion of the physical design for each Site.

FAA Response: The 1U form factor will be required for the remote sites (radio sites) due to space limitations.

At the control sites (VCS sites), there is an opportunity to provide a "denser" form factor (e.g., "multiple" units in a card cage) for sites with greater number of control units. The FAA has some sites (i.e., more sites) with a small number of control RCEs and some sites (i.e., fewer sites) with a large number of RCEs. Where we have very few RCEs (e.g., 1-3), using the denser form factor may not be possible or practical due to space limitations. Our smaller facilities generally have a harder time providing floor space to accommodate new systems - it will be difficult to find space for a whole rack at our small facilities and it wouldn't make sense to replace 2U-6U of equipment with a whole rack. At facilities where we have a large number of RCEs (range is up to 300 at a site for our largest facility, ARTCCs average 160 per facility), the denser form factor would be advantageous. Our larger facilities can accommodate additional floor space requirements (i.e., for several new racks of equipment) easier than our smaller facilities. Vendors need to support the physical configurations of the APCs per section 3.5.1 of the APC System Specification (20210325r1). FAA sites where cabinets/racks would be required would be determined at the site survey.

AdministrationFor Official Use Only 47April 21, 2021

Cont’d Technical Questions Question: For simplex keying it is required for DC current to flow through the TX audio transformer of the APC? Is it possible to provide TX audio via transformer, but with DC current flowing outside through a solid state circuit, providing the correct insulation and balance (to be defined)?

FAA Response: Figure 3-2 of the APC System to Radio Control Systems IRD (20210325) conveys how DC current for keying the radio flows through the TX Audio transformer. This allows for the use of existing 2-Wire TX audio path and does not require any additional logic circuitry or signaling lines. The requirement for "simplex keying" stands as written.

Question: Is it allowed to use solid state devices instead of relays? The 10M ohm open-contact resistance required seems over estimated against the residual current of 100 microampere. Can 1M ohm be enough?

FAA Response: Vendors can propose solid state devices as their interface solution, but this type of solution must allow for the APC System to meet all of the requirements in the APC System Specification and the APC System to Analog Radio Control Systems IRD (20210325), which includes meeting the referenced interface parameters for Open-Contact resistance and leakage current. The 10 Mega ohm Open-Contact resistance parameter does not directly correlate with the 100 uA leakage current parameter, but it is required for isolation during non-steady state conditions on the interface.

Question: If the use of solid state devices were allowed instead of relays, is it possible to get the electrical characteristics required?

FAA Response: The electrical parameters that the interface must meet are provided in the APC System to Radio Control Systems IRD (20210325).

AdministrationFor Official Use Only 48April 21, 2021

Cont’d Technical Questions Question: Request of contact voltage of any polarity seems not in accordance with the +24 VDV power to be provided. Can you please elaborate?

FAA Response: The Interface must support both +24VDC and -48VDC as defined in the APC System to Radio Control Systems IRD (20210325).

Question: The SOW does not include a general scope to include engineering studies.

Please consider adding at the end of the current SOW the following contract clauses from the standard AMS language to support not only the additional ECP activities envisioned, but continuous security updates, other ILS and system sustainment activities for the life of the contract.

C.11 General Engineering & Technical Support Services C.11.1 Additional Contractor Support for Second Level Engineering C.11.2 Change Request Control Process for APC Build/Release Content

FAA Response: The FAA envisions requiring engineering support, continuous security updates, ILS updates, and system sustainment activities for the life of the contract. We will review the SOW and verify the appropriate support is included (e.g., C.8.3.10.a -The Contractor must provide second-level engineering support for all test and operational systems until the FAA can take over the responsibility, etc.).

AdministrationFor Official Use Only 49April 21, 2021

Cont’d Technical Questions Question: Please provide during industry day presentations clarification about how the P- SIR package will be updated to address the post-ISD modifications to the APC as part of an engineering change proposal (ECP) and explain how the program office will include this in the procurement. Will it be included in the proposal response? If so, will this be in Phase 2?

Or will the ECP be addressed after contract award for the commercial baseline product?

FAA Response: The Analog Link requirements are planned for an ECP. The technical requirements related specifically to the Analog Link are highlighted in the Spec and IRD released with the PSIR. We will most likely look at the Offeror's plan for adding the Analog Link capability as part of the detailed proposal evaluation. This would include the plan to meet the technical requirements as well as evaluating the price/cost aspects of the ECP. The expected approach will be described in Sections L and M, which will be released in draft form with Part B of the PSIR (expect to see that in May). The FAA will evaluate the approach for meeting the requirements and the proposed price during the source selection and will likely defer the execution of the Analog Link requirements until after FAA achieves In Service Decision (planned for November 2025).

Question: When can industry expect the additional J attachments? A number of them were referenced in the SOW but not provided. Will they be provided as part of the second draft SIR package expected in May?

FAA Response: Look for additional J attachments with the release of SIR Part B (expected in May).

AdministrationFor Official Use Only 50April 21, 2021

Cont’d Technical Questions Question: Clarification of ECP and relationship in the SOW between "commercial baseline product" for ISD and the post ISD upgrade that would result in requirements that are identified in the technical specification and other documents released in the P-SIR package, including shaded items in the SOW (for example in the test section) related to additional development, planning, engineering, test, production, delivery, ILS and support for the ECP-driven modifications to the APC described in the P-SIR Announcement Section 6.1, page 7 as the "Analog Transport Areas for APC Communications Links". The SOW does not yet include specific activities, tasks, deliverables, etc. related to this post ISD ECP. Furthermore, other SOW sections that would be required to be performed under an ECP are not identified.

How will the FAA clarify in the D-SIR/Final SIR the differentiation between the base?

FAA Response: The Engineering Change Proposals (ECP) requirements are identified in C.4.9.4.3 and associated CDRL/DID APC-CMP003. The ECP must contain sufficient information to allow the FAA to evaluate the total impact of the proposed change. ECPs should include details of the engineering change, its effects on system support as well as cost and schedule impacts. Content should follow applicable elements described in either the DD-1692 or MIL-HDBK-61A(SE) Appendix D, Table D-4 Checklist B. The Contractor may use MIL- HDBK-61A(SE), Configuration Management Guidance, MIL-STD-973, Configuration Management, as guidance in the classification and content of ECPs and EIA-HB-649, Implementation Guide for Configuration Management, for additional guidance.

AdministrationFor Official Use Only 51April 21, 2021

Cont’d Technical Questions Question: As understood from the “Voice over IP Communication Enterprise (VoICE) Software Requirements”, please confirm the FAA does not require traceability from software design to source-code.

FAA Response: Correct, traceability from software design to source code is not required. However, traceability must be maintained as required in section 2.2.1.7 of the Software Requirements Document (Attachment J.1.2):

Software Trace Data The Contractor must provide the Software Trace Data as an auditable but not formally deliverable artifact, which establishes the associations between life cycle data items contents.

a. Trace Data must be available that demonstrates bi-directional associations between system requirements and software requirements.

b. Trace Data must be available that demonstrates bi-directional associations between software requirements and software design.

c. Trace Data must be available that demonstrates bi-directional associations between software requirements and test cases.

d. Trace Data must be available that demonstrates bi-directional associations between test cases and test procedures.

e. Trace Data must be available that demonstrates bi-directional associations between test procedures and test results.

In addition, traceability must be maintained as required in section 3.7 of the Software Requirements Document (Attachment J.1.2):

Software Configuration Management Process

c. The Contractor must establish traceability of software baselines either to the output it identifies or to the process with which it is associated.

d. The Contractor must establish traceability of software configuration items either to the output it identifies or to the process with which it is associated.

AdministrationFor Official Use Only 52April 21, 2021

Wrap-Up

AdministrationFor Official Use Only 53April 21, 2021

Resources

• FAA Acquisition System Toolset

– https://fast.faa.gov/

• FAA Small Business Office

– https://sbo.faa.gov/Home.cfm

• FAA Contract Opportunities

– https://Beta.sam.gov

AdministrationFor Official Use Only 54April 21, 2021

Follow-up Point of Contact

• Industry personnel are strongly discouraged from contacting or communicating directly with any FAA employee, except for the Contracting Officer, on matters pertaining to APC acquisition.

ALL communication should be sent to the FAA Contracting Officer from the Contractor’s Contract Manager or designee.

• Questions resulting from this industry day must be submitted to the below.

• Point of Contact

– NAS VoICE: 9-AWA-VoiceInfo@faa.gov

– Mary M. Johnson

Contracting Officer, AAQ-320 Mary.M.Johnson@FAA.gov