Amendment 00001 RFP Attachment D-TSA Responses to Questions.pdf

Question # Reference Question Category Question Answers

1 RFP General Contract How will TSA determine which BOA (first iteration or 2nd) will be utilized for each

Request for Delivery Order?

One BOA will be issued to each vendor for increment 1. Each BOA for increment 1 will include the CPSS size (base, mid, full) for which has been added to the QPL.

A draft BOA was posted as part of this RFP package for informational purposes only to show the most current terms and conditions. If a vendor currently has a BOA, please see BOA section 2.6 "Annual Review of BOA" for guidance concerning changes.

RFP 7.6.2, Factor 2 ‐ Past Performance with Socio‐ Economic Considerations, Contract

The RFP states "The TSA shall evaluate the Offeror’s Past Performance submission with a preference for verified Small Businesses specific to NAICS code 334511."

Can TSA please confirm this evaluation criteria only applies to verified small businesses?

TSA confirms that this evaluation criteria is only applicable to small businesses specific to NAICS code 334511.

3 BOA General Contract Does TSA have a maximum number of BOAs it intends to award? TSA does not have a maximum number of BOAs that it intends to award.

RFP 6.10, Table 7 ‐ Proposal Content

RFP 6.10.2, D. Production and

Reliability

Technical

Section 6.10, Table 7 ‐ Proposal Content shows a page limit of three (3) pages for Vol.

II Factor 1, D. Production and Deployment Capability.

Section 6.10.2, D states "The Offeror shall provide a narrative no more than two (2) pages outlining the proposed monthly deployment capability and methodology."

Can TSA please confirm it intends to allow 3 pages for this section of the response?

Amendment 00001 changes section 6.10.2, D to three (3) pages. TSA confirms three

(3) pages for Vol. II Factor 1, D. Production and Deployment Capability.

5 RFP General Contract Please explain how this RFP impacts existing BOA(s), if any. Further, how will it be addressed?

There is no impact to existing BOAs. See response to question #1 above.

RFP 7.6.1, Factor 1, "Production and

Deployment Capability," #2 Contract

7.6.1 states "Confirmation of the capability to have systems installed and operational within one

(1) day of taking the intended checkpoint lane down for installation." This would indicate the required install time begins following taking down lanes for installation.

Conversely TSA's Attachment C‐Frequently Asked Questions states "Installation time includes removal/decommission time if the lane has an existing unit as well as

SAT/iSAT testing." Can TSA please clarify that the RFP takes precedence over the FAQ document?

The installation requirement begins the day the checkpoint lane is shutdown through SAT of the new system within one (1) day. A day is considered eight (8) hours per day. The Attachment C‐ Frequently Asked Questions document is correct, the Statement of Work has been updated in Amendment 00001.

7 RFP 5.3 , FAR 52.212‐3, page 21 Contract

The RFP calls out FAR 52.212‐3 Offeror Representations and Certifications‐

Commercial items (NOV 2021). Given that the particular version of this clause in

SAM is controlled by DLA, will bidders be required to submit a full set of Reps & Certs with its Volume I if its SAM registration does not reflect (NOV 2021)?

Instructions are provided in Section 5.3, FAR 52.212‐3 Offeror Representations and

Certifications ‐ Commercial Items (nov 2021) "The Offeror shall complete only paragraph (b) of this provision if the Offeror has completed the annual representations and certification electronically in the System for Award

Management (SAM) accessed through https://www.sam.gov. If the Offeror has not completed the annual representations and certifications electronically, the Offeror shall complete only paragraphs (c) through

(v)) of this provision." In addition, Vol. I B states the offerors shall ensure all necessary provisions, representations & certifications, and amendments are completed and provided.

8 RFP 3.2.2 – Table 3‐ Invoice Guidance Contract

CLIN 00002‐80002 indicates "Program Management is not separately priced...."

Program Management is included as a separately priced CLINs in RFP Section "2.9.2

Order Period of Performance" and Attachment A‐ Price Evaluation CLIN Schedule

Excel document. Can TSA please confirm bidders should provide separate pricing for the Program Management CLINS?

Amendment 00001 updates Table 3‐ Invoice guidance for CLINs 00002‐800002.

These CLINs are separately priced.

9 RFP General Contract

RFP Periods of Performance have been modified to state the PoP “must complete a successful SAT within 9 years of date of order award, if applicable.” Does this mean that TSA intends to place orders for delivery and SAT of CLIN 1 systems up to 9 years after order award? If so, is TSA then still intending contractors to provide a two‐year warranty and 8 years of warranty maintenance/logistics support for a period that could be 18‐19 years after original order award? Please clarify the intent of this change to the PoP definition.

Only the two‐year warranty will be applicable if CLIN 1 systems are ordered in year

9. The total period of performance of the order is 11 years.

10 RFP General Contract

Engineering Support Services have been added to the SOW and CLIN Table with three possible levels of complexity and an order quantity NTE 10. Please clarify TSA’s intent in defining an NTE number of ESS events, and how TSA will evaluate contractors’ price proposals when they are based on each Contractors’ assumptions of quantity and complexity of ESS events over a 10+ year PoP?

The unit price is per job. For example, low complexity is up to 40 hours of support.

TSA reserves the right to exercise one job up to 10 times. Per Section 7.6.3, "The total evaluated price will be based on the extended price of all base, option periods, and separately priced optional CLINS at quantities specified in RFP Attachment A:

Price Evaluation CLIN Schedule".

11 RFP General Contract

Invoice guidance has added that invoices may be submitted “upon successful completion and acceptance of FAT/SAT for each… system.” Does this mean that

TSA also does not intend to utilize the systems for security screening until the systems have been fully accepted, without conditions?

Yes.

12 SOW General Contract

TSA’s Base SOW for Increment 1, Window 2 specifies a configuration with zero buffers. How does TSA anticipate using this configuration in an airport operational environment? What would be the CONOPS?

TSA will follow the Base system CONOPs and SOP; no changes anticipated.

13 SOW General Contract

Several new requirements (e.g. powered hands‐free microphone and speakers in shields, operation off of CT power source, etc.) have been added to the SOW.

Shouldn’t these requirements be part of the FRD? Does TSA expect new, or modifications to existing, QPL test articles to be submitted with these capabilities for qualification and OT&E in time to achieve QPL Approval prior to Dec 20, 2022?

No, TSA does not expect new, or modifications to existing, QPL test articles to be submitted with these capabilities for qualification.

14 SOW General Contract

TSA’s Base SOW for Increment 1, Window 2 specifies a configuration with zero buffers. How does TSA anticipate using this configuration in an airport operational environment? What would be the CONOPS?

TSA will follow the Base system CONOPs and SOP; no changes anticipated.

Amendment 00001 RFP 70T04022R7672N004- Base

Attachment D