70T04021Q7672N004 - A1 Attachment 1 Q-A.pdf

70T04021Q7672N003‐Amendment‐1:

Vendor Questions/Comments and TSA Responses

Question: Request to extend the proposal due date to August 31, 2021.

TSA Response: The request for a proposal due date extension is not granted. The proposal due date shall remain unchanged.

1 Comment: RFP Section D.4.1 Payment Milestones states: “The vendor shall submit a single invoice each month for services performed and/or equipment delivered within that monthly billing period. Services and Equipment are to be billed based on the payment milestones outline in section D.4.2.”

Can TSA confirm the Contractor is limited to submitting only one invoice per month for any/all CLINs delivered/performed within that month?

TSA Response: Yes, TSA should receive only one invoice per month for all CLINS. The only exception is Warranty payments. Those can be invoiced in a separate single monthly invoice. See Amendment A0001 for updated language.

2 Question: Could TSA provide any information regarding airports that the units would be delivered to?

TSA Response: TSA is not able to provide the list at this time as locations and deployments are based on both airport and equipment availability at the time of need.

3 Question: Is there any intention from TSA to integrate the RSEDS units into a semi‐inline configuration?

TSA Response: No, not at this point in time. If the units are to be integrated, that will be handled separately under another contract.

4 Question: SOW ‐ Section 1.1 General Requirements states: “The Contractor shall be responsible, exclusive of Airport Authority, System Integrator and Rigger activities, for all labor, materials, equipment, and support services needed to manufacture, assemble, power up, configure, and install, and test the EDS and ancillary equipment and the requisite networks into the required operational condition.”

Does TSA intend to add a CLIN for Networking (installation labor and material)?

TSA Response: At this time, TSA does not intend to network multiple EDS together. The networks noted above simply refer to the connection from EDS to PVS and SVS as necessary. Separate CLINs should not be required, connecting PVS and SVS to the EDS should be included in the PVS (CLIN 0011) and SVS (CLIN 0012) FFP pricing.

5 Question: SOW ‐ Section 1.1 General Requirements “The Contractor shall, at a minimum: Provide support and engineering services for all installation, integration, networking and testing activities.”

Does TSA intend to add CLINs for integration and Networking (installation labor and material)?

TSA Response: At this time, TSA does not intend to integrate and/or network multiple EDS together. The “requisite” networks noted above simply refer to the connection from EDS to PVS and SVS as necessary. Separate CLINs should not be required, connecting PVS and SVS to the EDS should be included in the PVS (CLIN 0011) and SVS (CLIN 0012) FFP pricing.

6 Question: SOW ‐ Section 1.1.1 Configuration Management and 1.1.2 Configuration Identification (CI) reference the STSS contract which will expire.

Does TSA intend to extend the existing STSS contract or award a new STSS contract?

TSA Response: Please see Amendment 0001 which updates current STSS language to general fleet management language. General fleet management language refers to the current STSS or any other future fleet management support contract that TSA might put into place.

7 Question: SOW ‐ Section 1.3.1 RSEDS Scanner General Information (CLIN 0010). “The Operator Manual shall describe any operations of the Contractor’s network management, remote monitoring and control system functions, and procedures.”

Does TSA intend to integrate and network these systems?

TSA Response: At this time, TSA does not intend to integrate and/or network multiple EDS together. The “requisite” networks noted above simply refer to the connection from EDS to PVS and SVS as necessary. Separate CLINs should not be required, connecting PVS and SVS to the EDS should be included in the PVS (CLIN 0011) and SVS (CLIN 0012) FFP pricing.

8 Question: SOW ‐ Section 1.3.6 Uninterruptible Power Supply (incorporated in CLIN 0010 pricing). “The Contractor shall ensure that the UPS site installation guidelines are included in the EDS Installation Manual and executed in accordance with this

SOW.”

If the UPS is internal to the system, then the Contractor would not include site installation instructions in the EDS Installation Manual. Can TSA update the language?

TSA Response: Please see Amendment A0001 for updated language.

9 Question: SOW ‐ Section 1.4.1.1.4 Project Management Reviews (PMR). “The Contractor shall prepare and submit PMR slide(s) to be included in the STSS PMRs in accordance with the PMR CDRL.”

TSA Response: Please see Amendment 0001 which updates current STSS language to general fleet management language. General fleet management language refers to the current STSS or any other future fleet management support contract that TSA might put into place.

Question: SOW ‐ Section 1.4.1.1.5 Weekly Project (WP) Status. “These conference calls cover the entire Engineering, Production, and Installation projects for the entire TSA fleet of equipment for each OEM, and are officially conducted under the STSS Contracts.”

TSA Response: Please see the RFQ Amendment 0001 which updates current STSS language to general fleet management language. General fleet management language refers to the current STSS or any other future fleet management support contract that TSA might put into place.

Question: SOW ‐ Section 1.4.3.2 Site Acceptance Test Procedures and Reports. “If the Government has required services requiring permits, companies with special qualifications and licenses, etc., the Contractor shall provide such requirement. All equipment is subject to Government approval for each installation site configuration.”

When would TSA notify the Contractor of this requirement and should it be priced into a particular CLIN?

TSA Response: This section has been updated per Amendment 0001.

Question: SOW ‐ Section 1.4.5 Training (CLIN 0008). “In addition to the training noted above, the Contractor shall provide the training simulator software license for the RSEDS User Interface (UI) software to TSA. This software will be designated for use with TSA’s Universal Simulator Platform (USP) at the Threat Mitigation Laboratory (TML) and TSA designated airport locations. The software should be installed in conjunction with installation of the RSEDS at the designated airport sites. Note: If a site does not already possess a Simulator, the hardware procurements are to be negotiated and priced separately. If an installation is required prior or post installation, travel costs will be negotiated and approved separately.”

o Does TSA intend to pay for the training simulator software license with each Training ordered under CLIN 0008?

o Does TSA intend to only purchase/use a total of 15 training simulator software licenses and not transfer the software to other USPs?

TSA Response: Please see Amendment A0001 for updated language. TSA is asking for pre‐ approved training software to be delivered in conjunction with the EDS installation. TSA already holds universal licenses for training simulators based on the current approved configurations. A separate license for additional trainings should not be required.

Additional Updates to Section B:

Section B 1.1.1 – Fleet Management Language Added for clarification.

Section B.1.4.4 has been updated with needed Field Data Reporting System (FDRS) language.

Section B.1.5.5 has been updated with needed Field Data Reporting System (FDRS) language.