SPECIAL NOTICE
70 -- National Airspace System (NAS) VoICE Software Assurance and iFAT Industry Day
- Notice Date
- 5/20/2021 6:16:02 AM
- Notice Type
- Special Notice
- NAICS
- 334210
— Telephone Apparatus Manufacturing
- Contracting Office
- 693KA8 SYSTEM OPERATIONS CONTRACTS WASHINGTON DC 20591 USA
- ZIP Code
- 20591
- Solicitation Number
- 693KA8-21-RFI-VoICE-07
- Response Due
- 5/12/2021 2:00:00 PM
- Archive Date
- 05/27/2021
- Point of Contact
- Mary M. Johnson, Phone: 2022673670, Mary M. Johnson, Phone: 2022673670
- E-Mail Address
-
9-AWA-VoiceInfo@faa.gov, MARY.M.JOHNSON@FAA.GOV
(9-AWA-VoiceInfo@faa.gov, MARY.M.JOHNSON@FAA.GOV)
- Description
- Amended May 20, 2021 to add Software Assurance and iFAT Industry Day Industry Day presentation to the Attachments/Links.� Purpose The purpose of this notice is to announce a VoICE over IP Communication Enterprise (VoICE) Software Assurance and initial Factory Acceptance Test (iFAT) Industry Day. The VS&R Program Office will hold a virtual industry day, specific to the VoICE Software Assurance and iFAT requirements, on May 20, 2021 from 9:00am - 12:00pm EDT, via online collaborative webinar media. Interested parties must register to participate the virtual industry day event and submit questions (if any), related to Software Assurance and iFAT requirements, no later than May 17, 2021 at 5PM EDT. See additional information and details below. Industry input will assist the FAA in determining an acquisition strategy for VoICE procurements that will meet its needs. The FAA would prefer to acquire commercial items via competition. To the extent that commercial items will not meet its needs, the FAA will consider competing for non-developmental items. Throughout this pre-solicitation dialogue with industry, the FAA is interested in what particular requirements are not currently met by commercial items or, separately, may require development. The FAA will use information obtained to consider adjusting its overall requirements for the actual VoICE SIRs. Disclaimer This is not a screening information request (SIR) or request for proposal. The FAA is not seeking or accepting unsolicited proposals. The FAA is seeking interested sources that are capable of fulfilling the FAA�s requirements. In accordance with Acquisition Management System (AMS) Policy 3.2.1.2.1, this market survey is to solicit statements of interest and capabilities from interested business concerns. This market survey also seeks to identify potential vendors for this work, including groups of business teams. For questions about FAA�s acquisition policies, please visit https://fast.faa.gov, which provides the FAA�s AMS Policy and Guidance as well as provisions and clauses used by the FAA in its acquisitions. Participation in this market survey is voluntary and respondents may choose to respond to all or some of the requests. Submissions in response to this market survey announcement must be relevant to the subject of the market survey and the survey questions. Responses will be reviewed by U.S. Government employees and a limited number of Government support contractors working under non-disclosure agreements. VoICE Background The mission of the FAA�s Voice Switch & Recorder (VS&R) Program Office�s VoICE program is to provide a flexible, network-based voice communication enterprise system that will replace aging, increasingly expensive to maintain legacy voice switches. The VoICE program will also address Radio Control Equipment (RCE) obsolescence and End-of-Life (EOL) issues. The VoICE program will replace voice switching core infrastructure at select ATCTs, TRACONs, and ARTCCs with a modern and supportable Voice over Internet Protocol (VoIP) enabled networked voice communication system. The VoICE program will consist of multiple competitive procurements in a two-phased approach: Phase 1 will provide IP-analog interfaces (i.e., Air-to-Ground (A/G) Protocol Converter (APC) and Ground-to-Ground (G/G) Protocol Converter (GPC) Systems) through two procurements: The APC System procurement will involve deploying an A/G interface capability that converts analog voice/signaling (currently used by all FAA voice switches, radios, and RCE) to European Organization for Civil Aviation Equipment (EUROCAE) ED-137-compliant VoIP. The APC System will also convert ED-137-compliant VoIP to analog voice/signaling. The APC System will replace the aging RCE with an IP-compatible capability The GPC System procurement will involve deploying a G/G interface capability that converts analog voice/signaling (currently used by all FAA VoICE switches) to European Organization for Civil Aviation Equipment (EUROCAE) ED-137-compliant VoIP. The GPC System will also convert ED-137 compliant VoIP to analog voice/signaling. Phase 2 will provide native-VoIP switching systems through one or more procurements with a priority to replace the voice switches at the ARTCCs and Core Terminal facilities. The native-VoIP communications systems will use the APC and GPC Systems deployed with phase 1 for communicating with legacy analog interfaces. Software Assurance FAA beta.SAM notice 693KA8-21-PSIR-APC-01 Attach 03 J.1.2, APC System Draft Software Requirements (also attached with this notice), contains the requirements for all system software development activities that occur under the APC contract. The FAA is releasing, for the first time, Attachment J.1.7, VoICE APC System Tool Software Requirements Document (Tool SRD); we are not soliciting comments at this time but will request them in the near future under a separate notice. These requirements will be common between the Phase 1 APC and GPC, and Phase 2 native IP switching systems. Any software development for APC System software that occurs under the APC contract must adhere to the requirements defined in Attachment J.1.2, VoICE APC System Software Requirements Document (APC SRD). Any software development for tool software that occurs under the APC contract must adhere to the requirements defined in Attachment J.1.7, VoICE APC System Tool Software Requirements Document (Tool SRD). The FAA uses RTCA DO-278A (Software Integrity Assurance Considerations for Communication, Navigation, Surveillance and Air Traffic Management (CNS/ATM) Systems) as a basis for its software requirements. Specifying a DO-278A assurance level aids in determining which requirements are applicable to the system. The FAA has already determined which requirements are applicable to the system, as reflected in Attachment J.1.2, VoICE System Software Requirements. PLEASE NOTE: Software Assurance Requirements will be identical for APC, GPC, and VCS VoICE procurements. iFAT The APC Preliminary SIR (SOW C.6.8.3, Attachment J.1.8, APC System Test and Evaluation Requirements, Section 3.4) contains the initial Factory Acceptance Test (iFAT) concept. During Source Selection, the FAA will ask Offerors to complete a Verification Requirements Traceability Matrix (VRTM) stating which of the FAA APC requirements the Offeror believes its proposed solution already meets. The Offeror will also submit test procedures and test reports showing that the product passed validation testing for the requirements it believes the solution already meets. The Offeror would be proposing development of the remaining requirements (e.g., cost and schedule) as part of its offer. The FAA will select the offer that represents the best value to the FAA, based in part on the cost and schedule associated with the development effort. At contract award, the FAA will add the VRTM submitted by the winning Offeror to the APC contract as Attachment J.1.6, APC System Initial Factory Acceptance Test (iFAT) Technical Requirements. At contract award, the FAA will order an iFAT system to be delivered to the Contractor�s facility within 60 days. The iFAT system would be the product on which the Contractor is basing its solution (i.e., the vendor�s commercial product that may not meet all FAA requirements at this stage of the program). The Contractor will then execute its COTS test procedures on the iFAT system with FAA witnesses to demonstrate the solution�s ability to pass the tests. After review of the procedures by the FAA to ensure they adequately demonstrate compliance, and after an initial System Requirements Review (iSRR), the FAA may provisionally accept some or all of the iFAT results in place of testing those requirements during the later Factory Acceptance Test. Requirements that are not accepted (e.g., Contractor did not claim as �met� at proposal time, requirements related to iFAT testing that did not pass, requirements related to tests where the FAA deems the COTS procedures don�t adequately test the FAA requirement, etc.) would be included in development by the contractor and would be validated during the later FAT testing. Any requirements provisionally accepted as a result of iFAT may need to be retested if development to meet FAA requirements impacts requirements covered by those provisionally accepted during the iFAT. Following iFAT and throughout the development phase leading to FAT, the iFAT system would be upgraded to reflect the latest software and hardware baseline and used by the Contractor as an engineering testbed to support development required to get to FAT. This system could also be used to develop and dry run the FAT procedures and possibly the System Test procedures. The upgraded iFAT system would be used for FAT conduct. VoICE Software Assurance and iFAT Industry Day The VS&R Program Office will hold a virtual industry day, specific to the VoICE Software Assurance and iFAT requirements, on May 20, 2021 from 9:00am - 12:00pm EDT, via online collaborative webinar media. The purpose of the industry day is to allow discussion of FAA Software Assurance (Attachment J.1.2, VoICE System Software Requirements) and iFAT (APC SOW C.6.8.3, Attachment J.1.8, APC System Test and Evaluation Requirements, Section 3.4.) requirements. The FAA requests that industry submit questions related to Software Assurance and iFAT requirements with its registration, to ensure a response is available as part of the FAA presentation. This industry day event is intended to facilitate detailed interchange and discussion. While the FAA appreciates all feedback provided by industry, including that provided real-time during the industry day event, if participants are not comfortable sharing feedback in a group setting, feedback may be provided in writing as part of a response to this announcement (please submit to 9-AWA-VoiceInfo@faa.gov.) Industry feedback will be considered in the preparation of formal solicitation documents, however, any revision to the VoICE Software Assurance and iFAT requirements remains solely at the FAA's discretion. Registration Interested parties must register to participate the virtual industry day event and submit questions (if any), related to Software Assurance and iFAT requirements, no later than May 17, 2021 at 5PM EDT. The FAA will confirm attendance no later than 5PM EDT May 18, 2021 and provide the webcast access information. Registration Requests:� For those interested in attending this event, please submit your request to 9-AWA-VoiceInfo@faa.gov with the following information: Company name and address Attendee name(s) Attendee phone number; email address List your company�s experience with designing, building, and deploying voice communication systems and if it has any systems currently in operation List of questions related to Software Assurance and iFAT requirements.
- Web Link
-
SAM.gov Permalink
(https://beta.sam.gov/opp/df6111946ad047688b72d163f952798b/view)
- Record
- SN06008107-F 20210522/210521201526 (samdaily.us)
- Source
-
SAM.gov Link to This Notice
(may not be valid after Archive Date)
| FSG Index | This Issue's Index | Today's SAM Daily Index Page |