VCS RFI QnA Final Sep 23.xlsx

XLSX spreadsheet 28 KB Posted Nov 16, 2023

Attached to: Air Traffic Control Voice Communication Switch Replacement
Solicitation number: FA8102-23-R-2003
Issued by: Department of the Air Force Materiel Command Lifecycle Management Center Tinker Air Force Base

About this file

Written by GovTribe AI · Dec 20, 2023

This document contains questions and answers related to a Request for Information (RFI) for an Air Traffic Control Voice Communication Switch Replacement. The RFI seeks information to replace the current ETVS system with a new Voice over IP system. Key details include that the replacement is for 126 CONUS and 26 OCONUS locations, with ED-137C compliance and MIL-STD-461 required for tactical systems. Questions cover areas such as system requirements, architecture, interfaces, delivery timelines, and data rights. Responses provide clarification around applicable standards, network information to be included in the RFP, and review timing. No products or services are currently solicited, as this appears to be a market research document in preparation for an upcoming RFP.

View the file

Other files

File	Type	Posted
4 Draft VCS SRD Fixed Based 4 Dec 23.docx	DOCX document	Dec 4, 2023
2 Draft VCS SRD Tactical 4 Dec 23.docx	DOCX document	Dec 4, 2023
1 Draft VCS SRD Tactical 14 Nov 23.docx	DOCX document	Nov 16, 2023
3 Draft VCS SRD Fixed Based 14 Nov 23.docx	DOCX document	Nov 16, 2023
4 Draft ATC_VCS_SOW_ 14 Nov 23.docx	DOCX document	Nov 16, 2023
VCS Industry Day Presentation Final.pptx	PPTX presentation	Sep 8, 2023
2 DRAFT VCS SRD v0 3Aug23.pdf	PDF	Aug 3, 2023
3 DRAFT ATC_VCS_SOW_Clean V0 3Aug23.docx	DOCX document	Aug 3, 2023
FINAL SSS RFI VCS 3 Aug 23.docx	DOCX document	Aug 3, 2023
Industry Day Notice.docx	DOCX document	Aug 3, 2023
Contractor Data for Industry Day EAL.xlsx	XLSX spreadsheet	Aug 2, 2023

Show all 11

On GovTribe

Work with this file

Download the original file
Contacts named in this file
Similar government files
Ask GovTribe AI about this file

Try for free Login

Text version

The file's text, extracted by GovTribe without its formatting.

RFI Questions

	Document Title/Date	Reference
	Comment Type (Technical, Acquisition)	Reviewer's Comment / Suggested Change/Rationale	Response
	System Requirements Document	1.2. System Overview	Technical	Can you specify the brand and model of the current EVTS in use? Is this the system that the USAF would expect the replacement contractor to maintain? It would be beneficial to provide the ETVS system architecture and concept of operations to support technology transition planning.	The OEM for ETVS is Northrup Grumman/Denro. No maintenance of the legacy ETVS system is expected under this effort.
	System Requirements Document	Table 2.11
IF-4 (KPP) Communication Interface	Technical	It is our understanding that the VoIP interfacing will adhere to the ED-137C guidelines. Can the USAF confirm that the system should be fully ED137 compliant?	ED-137C is mandatory see OP-8 in SRD Section 2.12 Operational Requirements.
	System Requirements Document	Table 2.11
IF-5 Interoperability	Technical	We are operating under the assumption that the FTI/FENS Network will transition to or incorporate VoIP.
Can you describe the current USAF Network architecture? Is the USAF considering maintaining the current network, possibly for backup or redundancy purposes? Is there more than one network that we will be integrating the VCS into, and can the USAF provide a listing of those networks?	Information about USAF Network architecture, backup, and redundancy will be provided within the final RFP at release.
	System Requirements Document	Table 2.11
IF-6 Voice recording	Technical	We assume that a DALR (Digital Audio Logging Recorder) is already in place and will need to interface with the new Voice Communication System (VCS). Please provide the interface requirements for the DALR and identify if interfaces will solely be analog, VOIP, or both.	The replacement for DALR, the FAA NVR, a Nice Systems Recorder that will be operating ANALOG upon installation and will be converted to VOIP at the time of the VCS installation.
	System Requirements Document	Table 2.11
IF-7 Lightning	Technical	We are operating under the assumption that the lightning system is already in place and requires no intervention from the bidder.
Can you confirm if our assumption about the lightning system is correct?	Lighting is correct word (typo in SRD document)

This is defined by the required Human Factors in the Air Traffic Control environment.

	System Requirements Document	Table 2.12
OP-5 (KPP) Interoperability	Technical	We're working under the assumption that FAA FTI/FENS is transitioning to or is based on VoIP. What is the USAF Network interfacing? Will the USAF Network serve as a backup to the FTI/FENS VoIP in the event of system issues or outages?	The intent of this effort is to rely solely on VOIP systems upon installation of the new switch when the recorder, radios and phone lines are interfaced.
	System Requirements Document	Table 2.12
OP-6 (KPP) Voice recording	Technical	We assume that a DALR (Digital Audio Logging Recorder) is already in place and will need to interface with the new Voice Communication System (VCS). Please provide the interface requirements for the DALR and identify if interfaces will solely be analog, VOIP, or both.	A final SRD will be provided with the RFP. All operational & technical requirements will be found there.
	System Requirements Document	Table 2.12
OP-7 Lightning	Technical	We are operating under the assumption that the lightning system is already in place and requires no intervention from the bidder.
Can you confirm if our assumption about the lightning system is correct?	Lighting is correct word (typo in SRD document) This is defined by the required Human Factors in the Air Traffic Control environment.
	System Requirements Document	Table 2.16
CYB-5 Network	Technical	We're operating under the assumption that the Network will be supplied by the Customer. Given the absence of specific details in this section, we are assuming the IP network model to be the one previously identified as FAA FTI/FENS. Please provide more detailed information regarding the IP network in the specifications?	USAF Network architecture will be provided within the final RFP at release.
	System Requirements Document	Table 2.17
TAC-1 Dimension	Technical	It is understood that the VCS (Voice Communication System) for the Tactical service is not designed to fit into a standard 19" rack structure. Please provide a sketch or diagram of the area dedicated to the VCS, including the relevant mounting or fixing details?	MSN-7 racks are non-standard. The dimensions shown are the max dimensions allowable for all non-operator position or “central processing” equipment. Operating equipment will consist of touch screens. The space can be filled with multiple shelves up to the maximum height. Offeror will need to provide the necessary number of shelves along with their tactical voice switch.
	System Requirements Document	Table 2.17
TAC-1 Dimension	Technical	Will the USAF be expecting the offeror to provide new equipment racks or will the USAF use existing rack space?	New equipment racks will be required for the fixed voice switch

Existing racks will be utilized for the tactical system, but new shelves will be required to fit equipment provided

	System Requirements Document	Table 2.17
TAC-3 Vibration	Technical	We are working under the assumption that the VCS will be installed into an existing rack which will be integrated in a shelter structure through an appropriate shock absorbers and anti-vibration devices. Can you confirm the accuracy of our assumption regarding the VCS integration and the presence of shock and vibration absorbers? If this is the case, should the shock and vibration requirements be applied to the VCS both as a standalone unit and when considering its installation within the existing structure?	Shock and vibration requirements are applicable to tactical system only. The requirements will be found in the SRD with the final RFP release.
	Sources Sought Synopsis	Page 7

B. Hardware and Production Questions: 14. New Question: Redundancy Technical In order to comprehensively address the operational impact and remaining capabilities during connection interruptions at consolidated base/site locations, we require further details. Specifically:

Could you clarify the nature of the sites being referenced? Are these primarily radio sites, radiotelephone sites, or other Air Traffic Service Units where additional VCSs are operational?

What kind of connection network is anticipated? Are we considering an analog system, IP, or a hybrid of both?

With this information, we'll be better positioned to provide a thorough response regarding system redundancy and associated operational impacts.	System arcitecture with redundancy requirements will be provided with the final RFP release.
	Statement of Work	Page 14
5.2.3. ATC VCS Software Delivery	Acquisition	In reference to the statement: "All Contractor code and software specifically written and designed for the ATC VCS system shall be delivered to the Government with unlimited rights", we seek confirmation on its scope. Does the USAF intend for this to apply solely to the software custom-developed for this particular project? Given that the ATC VCS is understood to be a pre-existing commercial system developed at the Contractor's expense, we would also like to confirm that this requirement does not extend to our legacy software developed prior to and independent of this contract. Is this understanding accurate? We request that the USAF include a method in the RFP package that allows offerors to identify data rights exclusions based on previously developed products?	DFARS 252.227-7015 and DFARS 252.227-7013 will apply to all data rights addressed in the SOW.
	Statement of Work	Page 25
9.1.2.5. Software	Acquisition	In relation to the provision that test software be delivered with source code, executable code, and build instructions, we seek more specific context. Is it expected that source and executable code developed prior to this project and at the contractor's expense be included in the deliverables? If this is the case, how does the USAF plan to handle and safeguard the intellectual property rights associated with such pre-existing software assets? We request that the USAF include a method in the RFP package that allows offerors to identify data rights exclusions based on previously developed products?	DFARS 252.227-7014 and DFARS 252.227-7019 will apply to all data rights addressed in the SOW.
	System Requirements Document	Table 2.7
International Agency Documents	Technical	Please add the EUROCAE ED-137 standards document to the applicable documents and state that the VCS must be fully ED-137 compliant.	ED-137C is mandatory see OP-8 in SRD Section 2.12 Operational Requirements
	System Requirements Document	N/A	Technical	The USAF has not identified any requirements for classified and non-classified communications (Red/Black) or security encryption for IP data communications. Will the USAF please provide requirements as it relates to these communication capabilities as we see other military entities require these capabilities.	No classified transmitions required.
	Statement of Work	N/A	Acquisition	Will the USAF require a VCS system or system(s) to be delivered as part of the proposal for evaluation? If so, we request that the USAF provide details as soon as possible on the size and quantity of systems so offerors can prepare.	Not required at this time.
	Statement of Work	Page 41
19. Cybersecurity	Technical	Will the USAF provide a copy of the DoDIN Approved Products List (APL) so offerors may review their system baselines to ensure all Information Technology (hardware and software) used in the ATC VCS is on the APL?	The Gov't will not be providing a list. The APL can be found online. The web address is https://aplits.disa.mil/processAPList.action Offerors will be required to provide confirmation of items proposed on the APL at time of RFP sumbittal.
	Statement of Work	22.1 - Data Deliverables	Technical	Will to USAF update the table to include the Deliverable Dates / Frequency? Will the USAF be providing the Data Item Descriptions (DiD) as part of a draft RFP? If there are Data Deliverables required to be submitted with the proposal, which ones are they?	CDRLs will be provided with the offical RFP release; Data Deliverables are not required at this time with the proposal. Data Item Descriptions are found at https://quicksearch.dla.mil/qsSearch.aspx
	System Requirements Document	N/A	Technical	Has the USAF come up with a technical transition strategy to move from the ETVS system to the new VOIP VCS system? Can the USAF provide any concepts they would like offerors to consider?	USAF represented personnel will be present to modifiy NVR and radios that will be required to interface at the time of cutover. Vendor will need to propose a recommended installation plan/technical transition strategy.
	Statement of Work	N/A	Technical	Please provide the USAF long term sustainment concept of operations as part of the SOW. It is not clear how long Interim maintenance is to be performed.	Interim Contractor Support is currently estimated to extend over a four year time period. Long term sustainment concept determination is unknown at this time.
	Statement of Work	N/A	Technical	Please provide more clarity on the levels of support Tier 1, Tier 2, Tier 3 and the related response times required (On-Site Support and Deport Spare Parts Replenishment Time)	Details for expected levels of supply and maintenace support will be provided in final SOW.
	Sources Sought Synopsis	N/A	Acquisition	Can the USAF provide the contract vehicle planned for this procurement?	Single award ID/IQ with Task Orders issued to fund requirements
	Sources Sought Synopsis	N/A	Acquisition	Can the USAF provide the draft section L and draft section M for offerors to review and comment on?	The Government does anticipate issueing a draft RFP to include L&M for industry to provide feedback.
	Sources Sought Synopsis	N/A	Acquisition	Can the USAF provide the acquisition timeline?	Currently the award schedule is not approved. Once approved it will be released to Industry for planning purposes.
	Sources Sought Synopsis	D. Contract Strategy Development, No. 4	Conflict in SSS/SOW	The SSS stated delivery of first article "... will be 120 days after contract award and the production units will be required to be ready for install 120 days after first article approval". The SOW states an objective delivery of first unit within 6 months after contract award and second, within 8 months after contract award. A threshold delivery for both system as 9 months. Question: Can you please confirm your expectation of the preferred delivery objective, 120 days or 6 / 8 months?	Clarifying First Article (FA) delivery epectations: First FA delivery NLT 6 months after contract award (ACA), 2nd FA NLT 8 months ACA. This is an estimate at this time and the final requirement will be released in the RFP.
	Statement of Work	5.2.4.2 First Deliver Order (Initial Production), pg 14	Conflict in SSS/SOW
	System Requirements Document	N/A	General	Will there be additional documentation providing operational features/requirements released prior to the RFP? Only the crash notification and select-to-lockout feature are specifically listed as operational requirements for the system.	The Government is anticipating releasing another draft SRD that incorporates changes that occured since the last release. The goal is to provide industry an opportuity to comment on an updated version of the draft SRD in Q1 of FY 24.
	System Requirements Document	1.4 Scope	Requirements	Can the Government provide the source where AF1067 Air Traffic Control Voice Control Switch/ ETVS Replacement dated 6 April 2023 can be accessed or, can you provide the document?	All requirements obtained from the AF1067 are found in the SRD. The AF 1067 is not releaseable to the public as it has PII.
	System Requirements Document	1.4 Scope	Requirements	On 05 June 2023 on SAM.GOV, the Sources Sought for the MSN7 Contractor Logistics Support was posted. It contains a PWS dated 26 May 2023 . Is this the intended reference document, or can the GOV provide the source where AF1067 MSN-7 Voice Communication Switching System (VCSS) Replacement dated 23 May 2023 can be accessed?	The Sources Sought for the MSN-7 CLS is a separate opportunity. All requirements obtained from the VCS AF 1067s are found in the VCS SRD. The AF 1067s are not releaseable to the public as they contain PII.
	System Requirements Document	2.11
IF-4	Requirements	Can the Government provide further clarification as to what DoD systems the VCS shall interface?	Gov't is still identifying all required interfaces. All final operational and technical requirements will be suppplied with the final RFP SRD release.
	System Requirements Document	2.12
OP-4	Requirements	Can the Government provide further clarification as to what DoD systems the VCS shall interface?	Gov't is still identifying all required interfaces. All final operational and technical requirements will be suppplied with the final RFP SRD release.
	System Requirements Document	2.12
OP-7	Requirements	We assume that the word "lightning" was meant to be "lighting", with the intent that operator TED's shall be suitable for viewing in both environments, control tower and radar room. Can the Government confirm?	Lighting is correct word (typo in SRD document). Human factors for lighting for both ATC and RAPCON are the same. MSN-7 has an additional night vision requirement that can be satisfied by a filter.
	System Requirements Document	2.16
CYB-4	Requirements	Can the Government identify/define “connections” that must be encrypted? We assume this is at the boundary to any external/untrusted networks.	Information about USAF Network architecture, backup, and redundancy will be provided within the final RFP at release.
	System Requirements Document	2.17
Tactical System Requirements	Requirements	Will the Tactical system be required to interface to radios, phones, and recorders via VoIP, or analog, or both?	At this point, it is anticpated that both connection options will be required.
	System Requirements Document	2.17
TAC-1	Requirements	Standard rack width is 19”? What are the maximum dimensions allowable?	These are tactical only maximum dimensions. Further dimensions beyond standard rack needs will be provided with final RFP release.
	System Requirements Document	2.18
MISC-2, MISC-3	Requirements	Can the Government provide a requirements document for Primary and Secondary Crash?	A final SRD will be provided with the RFP. All operational & technical requirements will be found there.
	System Requirements Document	2.18
MISC-2, MISC-3	Requirements	Is this a broadcast system (i.e., voice broadcast over console speakers) with no ringdown needed? If not, what external circuit types should be supported (i.e., FXO, FXS, SIP)?	A final SRD will be provided with the RFP. All operational & technical requirements will be found there.
	System Requirements Document	2.20
ORM-1	Requirements	Does the 0.998 Availability apply to both the fixed based systems and the Tactical system?
	Yes.
	System Requirements Document	General Question	Requirements	Can the Government confirm if MIL-STD-461 is a requirement for the Tactical System?	Confirmed. MIL-STD-461 is required and applies to tactical systems only.
	Statement of Work	Section 3.1	Acquisition	Does the referenced document have an assigned Government Document Number?	The overarching document is not releaseable. All applicable NAS requirements will be documented in the final SRD.
	Statement of Work	Section 3.1	Acquisition	Will the government provide access to the referenced document? We can only find ATCALS NAS II.	The overarching document is not releaseable. All applicable NAS requirements will be documented in the final SRD.
	Statement of Work	Section 5.2.4.5	Acquisition	Will the Government provide this attachment?	Expected delivery locations to be provided with final RFP release. Approximate number of locations is 126 CONUS and 26 OCONUS.
	Statement of Work	Section 5.3.2, d	Requirements	Can the Government provide a list of telecom circuit types that are expected for connection to host nation telecom?	Types of OCONUS telephone circuits to be released with the final RFP.
	Statement of Work	Section 4.2.3	Acquisition	The SOW calls for a technical review to define the functional baseline. This is effectively going to be handled like a combined SRR/SFR?	Still refining this requirement. Will be laid out in final RFP release.
	Statement of Work	Section 4.2.3	Acquisition	The SOW also specifies a second review that will define the allocated baseline as well as put under control the hardware and software baselines prior to starting testing. This would effectively be a combined PDR/CDR, correct?	Still refining requirements for each level of review. This will be laid out in final RFP release.
	Statement of Work	Section 5.1.1	Acquisition	The SOW requires that “The Commercial NDI must be manufactured and ready for shipment/delivery, with all proposed Commercial NDI features implemented, within six (6) months of award.” The technical reviews are at 120 days and 210 days. This seems to be inconsistent with a 6-month (181 days) delivery. Could you please clarify?	Thank you for pointing this out. We will take this into consideration while building out our requirements.
	Statement of Work	Section 5.2.1	Acquisition	The SOW requires delivery of “production representative” units at contract award. What is the specific meaning of “production representative” in this context?	Thank you for pointing this out. We will reword the timeline to state required delivery after contract award and make in line with contract requirements. All production representative units must meet all contractual requirements (Government Requirements) when presented to the government.
	Statement of Work	Section 5.2.1	Acquisition	The SOW states that the “production representative” units will be used to support program testing. How does this relate to the fact that: "The Commercial NDI must be manufactured and ready for shipment/delivery, with all proposed Commercial NDI features implemented, within six (6) months of award."? Is the initial testing intended to verify the systems meet the contractor’s published requirements? And then later testing will verify that the systems, once updated, meet the government’s requirements in the SRD?	No. All production representative units provided for testing must meet all contractual requirements (Government Requirements) when presented to the government.
	Statement of Work	Section 6.1	Acquisition	The SOW requires the development and delivery of a SEMP. Is this consistent with an NDI	A SEMP is a requirement as part of this RFP.
	Statement of Work	Section 7.1.2	Acquisition	The SOW specifies that the VCS will be verified as meeting the government requirements. The second technical review is at approximately 7 months and one of its purposes is to: "Establish and control the hardware/software baselines before start of testing." This seems to result in deliveries being made to the government well in advance of the baseline and the verification testing. Is the intent that there will be an upgrade of delivered systems prior to the start of testing?	The timeliness for deliveries is still under review and will be released in the RFP.
	Statement of Work	Section 8.2	Acquisition	Is this section intended to mean that the ECP is developed at no additional cost, or that the implementation of the ECP is done at no additional cost, or both?	Cost of development and implementation would be contractor responsibility in the case of a deficiency. Any change to the approved configuration required by the Contractor would be at the Contractor's cost. If the change is Government requested then it would be funded on an ECP CLIN.
	Statement of Work	Section 8.3	Acquisition	This seems more extensive than a typical factory acceptance test, which is primarily concerned with demonstrating that there are no manufacturing defects, along with tests of some key performance parameters to ensure there are no variations lot to lot that impact the system sufficiently to not meet the requirements of the SRD. However, the factory acceptance test does not verify that the system “conforms to applicable specifications”. The conformance to the specification is verified by First Article Testing, through requirements verification and environmental testing. In addition, the reference to the system being identical in form, fit and function, while an important aspect of the production process, this is validated by the PCA and controlled by the contractor’s CM process. The Factory Acceptance Test is not able to validate this on every unit. Are we possibly misinterpreting something here? If so, could you please clarify?	Thank you for the concerns. We will review and reword requirements for factory test verse first article test in the final RFP.
	System Requirements Document	2.2 ORM-6	Requirements	As written, the requirement is ambiguous, since it refers to both isolation and detection. Usually the detection requirement is the higher of the two and the fault isolation is a few percentage points lower. Second, a 100% requirement is impossible to verify statistically, though there could be a specific verification approach defined that all parties would find acceptable. But there are fault modes like bad ethernet cables, bad connections, etc. that make up that last .01% of failures that make meeting 100% isolation to a single item next to impossible. Perhaps the intent was that Detection would be 100%, with Isolation being some amount less?	This requirement is being reviewed and the final version released with the RFP.
	Statement of Work	Section 5.2	Acquisition	Can the Government provide more information on the intent of the first two production representative units?	These units will be used for gov testing of fixed based capabilities at locations to be determined by the USAF.
	Statement of Work	Section 8.2	Acquisition	Please confirm this refers to a First Article Test to be run on the initial system.	The test referenced in SOW Paragraph 8.2 is a test to be conducted at the the contractor facility on the intial system prior to First Article Test at an AF Location.
	Statement of Work	Section 13.1	General	Assume section 13.2?	Noted. We will correct typo in SOW.
	Statement of Work	Section 13.2	General	Assume Paragraph 13	Noted. We will correct typos in SOW.
		Direct email question reworded	General	Is the ATC Voice Recorder Replacement part of the Voice Communication Switch Replacement?	The Voice Recorder Replacement is a separate program the USAF is partnering in with the FAA. FAA is leading that replacement effort.

SAM.gov Announcement No. 693KA8-23-RFI-GPC-01 &P&N

File details come from the government source that posted it. Updated Nov 16, 2023.