TSA Responses to Questions_00001.pdf

Question No. Reference Question Category Question Answer

1 SOW Technical

Since the 140 trays were not mentioned in prior documentation (eg

QDP), and are a much higher number than necessary in our system, what is the basis of this calculation?

140 bins per system is the requirement based on operational need.

2 SOW CHAPTER 8 Contract

Chapter 8 mentions a lot of info on maintenance and spares, how do you see the relationship between this program and the existing

ILS contract?

The existing ILS contract is separate from the subject RFP, and will be treated as such.

3 SOW 8.5.5.2 Contract chapter 8.5.5.2 mentions preventive maintenance, at intervals of monthly, quarterly or annually but if the OEM maintenance manuals requires a higher frequency, is this acceptable?

Yes, as defined in OEM maintenance manual.

4 SOW 4.4.4.2 Contract Does this point refers to only workstations of simulators, or to all workstations in the contract?

See Amendment 00001. SOW Section 4.4. (CPSS Simulator) has been revised.

5 sow 4.6.2.3.1 Contract

The requirements in the QDP stated 48 hours installation time. If the installation is based on 8‐hour working days, then the time stated here does not match the original requirement. Please explain?

See Amendment 00001. SOW Section 4.1.5.2 has been added.

What is the payment arrangement to enable storage for 6 months?

Per the SOW 6.3, the Contractor shall provide storage for each CPSS system at no additional cost to the Government for up to six (6) months after FAT to accommodate deployment. Invoicing remains the same as what is noted in RFP Table 3‐ Invoice Guidance

Should this storage for 6 months be a complete system including scanner, or can the individual components be stored in different locations?

See Amendment 00001. SOW Section 6.3 has been revised.

7 SOW 4.1.3 Contract

The CRPG is referenced in this paragraph but generally refers to current system standards. Whilst some recommendations will apply, will the new CPSS System be considered as a variation to the current recommendations?

Yes, it will be considered a variation.

8 SOW 4.1.9.2 Technical Percentage of slope is different to the FRD (in the FRD it is 2%).

What is the correct value?

See Amendment 00001. SOW Section 4.1.10.2 (formerly Section

4.1.9.2) has been revised to 2%.

9 RFP Part 5 General Please supply contact details for the Contract Support Offices? See Amendment 00001 RFP section 5.1 for contact details.

10 RFP Part 5 General Please define the term "Lead System Integrators"?

Please see Basic Ordering Agreement (BOA) section 3.2.15

"PROHIBITED FINANCIAL INTERESTS FOR LEAD SYSTEM

INTEGRATORS".

11 CPSS BOA Contract

Vetting of foreign employees is to be done no later than 90 days prior to the start of the contract. Can we start vetting employees before 31‐5‐2021, just in case?

Yes.

12 RfP SOW Contract Please define what you consider the scope of the simulator to be and to what extent would you consider a simulator compliant?

See Amendment 0001. RFP Table 1 and SOW Table 1 have been revised. A complaint simulator is one that meets all of the requirements contained within SOW Section 4.4 (CPSS Simulators).

13 SOW 4.1.4 Contract How soon after the award would the installation locations be published?

Deployment regions will be provided at time of award. Actual TSA

Facilities will be provided at the Post‐Award Conference.

14 SOW 4.1.8 Contract

Within the CPSS FRD, there was no mention of the measures to provide protection to reduce the potential exposure of passengers and the TSA workforce to public health threats. Since it is mentioned here, how do you see the relationship between this point and the CPSS‐requirements in terms of configuration management, optional items and costing?

See Amendment 00001. RFP Table 1 and SOW section 4.1.8 have been revised. This requirement shall be priced as a separate optional CLIN.

15 SOW 4.1.11 Technical Please define the term "final images”?

See Amendment 00001. SOW section 3 has been updated to include definition.

Mid‐Size Statement of Work (SOW), Section 3.1, pg. 3 Contract Please confirm that "Automatic bin return system" is not required? It is not required for Mid‐Size.

Mid‐Size Statement of Work (SOW), Section 4.1.5.1, pg. 6 Contract What is the anticipated Period of Performance for CLIN 0001?

There is no anticipated Period of Performance of this CLIN, however; the delivery schedule of this CLIN shall be provided at the

Post Award Order Conference Meeting.

Mid‐Size Statement of Work (SOW), Section 4.1.5.1, pg. 6 Contract What is the anticipated Period of Performance for CLIN 0001A?

There is no anticipated Period of Performance of this CLIN, however; the delivery schedule of this CLIN shall be provided at the

Post Award Order Conference Meeting.

Mid‐Size Statement of Work (SOW), Section 4.1.10, pg. 7 Technical Does that include Prohibited Item Algorithms?

See Amendment 00001. SOW Section 4.1.11 (formerly Section

4.1.10) has been revised. It does not include Prohibited Items.

Mid‐Size Statement of Work (SOW), Section 4.1.10, pg. 7 Technical

Please clarify if no cost to the government includes any associated costs with installation, SAT or training associated with the upgrade?

See Amendment 00001. SOW Section 4.1.11 (formerly Section

4.1.10) has been revised.

Mid‐Size Statement of Work (SOW), Section 4.1.10, pg. 7 Contract

If the government future requirements require extra computing hardware to achieve higher levels of certification, is it’s the government intention to require vendors to upgrade the hardware at no cost

See Amendment 00001. SOW Section 4.1.11 (formerly Section

4.1.10) has been revised.

Mid‐Size Statement of Work (SOW), Section 4.1.10, pg. 7 Contract

If algorithms to achieve certification at future defined detection level are developed by the offeror with private funding, is the offeror still required to upgrade the system at no cost to the government

Yes.

Mid‐Size Statement of Work (SOW), Section 4.1.10, pg. 7 Contract

If the government is requesting no cost upgrades to hardware and software for future detection requirements, will the government continue to fund algorithm development to address these future threats and if so for how many years?

It is at the TSA's discretion to determine if the agency will continue to fund algorithm development. At this time, a determination has not been made.

Mid‐Size Statement of Work (SOW), Section 4.1.10, pg. 7

How will contractors access the systems to install the upgrades?

Will TSA provide contractors physical access to the systems? Is upgrade over the TSA (STIP) network an option?

Upgrades will be coordinated with TSA and physical access will be granted once contractor has been vetted through the TSA

Personnel Security vetting process. Upgrades over the TSA (STIP) network is not an option at this time.

Mid‐Size Statement of Work (SOW), Section 4.2.1, pg. 8 Contract

If the OEM TSE qualifies with a lower quantity of bins, does the

OEM need to provide 140 bins per system?

Yes.

6 SOW 6.3 Contract

Amendment 00001 TSA Responses to Questions

70T04021R7672N001

Mid‐Size Statement of Work (SOW), Section 4.3.1, pg. 8 Contract

The FRD specified table lengths of 6 feet. Is it TSA intent to have tables no longer than 4 feet or can the tables be modular and of different length (3,4, 6) to match site needs?

See Amendment 00001. SOW section 4.3.1 has been revised.

Mid‐Size Statement of Work (SOW), Section 4.4.1, pg. 9 Contract Is it 2 simulators per airport or per system?

See Amendment 00001. SOW Section 4.4. (CPSS Simulator) has been revised.

Mid‐Size Statement of Work (SOW), Section 4.4.1, pg. 9 Contract

Can the government clarify what the workstations and servers the government refers to? Are they in addition to the two simulators?

See Amendment 00001. SOW Section 4.4. (CPSS Simulator) has been revised.

Mid‐Size Statement of Work (SOW), Section 4.4.1 ‐ 4.4.3, pg. 9

Each section states the provision or installation of two (2) simulators as part of the CPSS System. Please confirm that this is not six (6) in total per CPSS System but 2 will be delivered at the time of each system.

See Amendment 00001. SOW Section 4.4. (CPSS Simulator) has been revised.

Mid‐Size Statement of Work (SOW), Section 4.4.5; pg. 9 Technical

Please clarify, does the intended target machine run the simulator in a virtual machine that emulates the OEM's defined OS, or is it a machine with multiple bootable partitions and the TSA selects which machine to boot into at startup?

See Amendment 00001. SOW Section 4.4. (CPSS Simulator) has been revised.

Mid‐Size Statement of Work (SOW), Section 4.4.5; pg. 9 Technical

Please provide the specifications of the existing TSA training computers in terms of memory, GPU, CPU cores, etc. available to the simulator program.

See Amendment 00001. SOW Section 4.4. (CPSS Simulator) has been revised.

Mid‐Size Statement of Work (SOW), Section 4.4.5; pg. 9 Technical

If the simulator software will not fit on a CD media format, would distribution on a USB drive be acceptable?

See Amendment 00001. SOW Section 4.4. (CPSS Simulator) has been revised.

Mid‐Size Statement of Work (SOW), Section 4.4.7, pg. 9 Technical

Can TSA clarify what is meant by the ability to develop and maintain multiple random simulation sessions?

See Amendment 00001. SOW Section 4.4. (CPSS Simulator) has been revised.

Mid‐Size Statement of Work (SOW), Section 4.4.10, pg. 10 Technical

Can TSA clarify what will constitute STIP capability?

Would an ethernet connection and disk storage dedicated for the

STIP client be acceptable?

See Amendment 00001. SOW Section 4.4. (CPSS Simulator) has been revised.

Mid‐Size Statement of Work (SOW), Section 4.4.10, pg. 10 Technical

The current STIP is being decommissioned and a new STIP is currently under development by the TSA. Does the TSA expect connectivity with the existing STIP program or the new program?

See Amendment 00001. SOW Section 4.4. (CPSS Simulator) has been revised.

Mid‐Size Statement of Work (SOW), Section 4.7.6.8.2, pg. 14 Contract What are the “TSA mandated fixes … from TSA … Testing?”

These are to be determined based on the results of the qualification process.

Mid‐Size Statement of Work (SOW), Section 4.7.6.8.2, pg. 14 Contract

Will TSA designate which test findings require a mandated fix? If so, when will TSA provide a list of mandatory fixes to offerors?

Yes. These fixes will be provided throughout the qualification process prior to proceeding to the next step.

Mid‐Size Statement of Work (SOW), Section 5.2.1. pg. 16 Contract

The Basic Ordering Agreement, Section 2.7.1 states post award conference within 14 days, the SOW states 30 days. Please clarify which is correct?

30 days from award; see Amendment 00001

Mid‐Size Statement of Work (SOW), Section 6.3, pg. 18 Contract

Can the TSA put a limit on the total number of units stored so unnecessary cost is not added to the proposal? As stated, 6 months x 22 units per month=132 scanners, Automated Diverters and roller tables is significant storage.

No, the TSA will not determine how an Offeror shall include this requirement in their FFP price proposal.

Mid‐Size Statement of Work (SOW), Section 7.1.4, pg. 19 Contract

Please confirm that upgrades on equipment will have the same warranty period as the original equipment?

Yes. The warranty period will remain the same as the original equipment. TSA will not restart the warranty period.

Mid‐Size Statement of Work (SOW), Section 7.1.4, pg. 19 Contract

Please provide maximum number of software upgrades that will be required of installed systems per year.

There is no maximum number of software upgrades that will be required of installed systems per year. Upgrades must be provided as needed.

Mid‐Size Statement of Work (SOW), Section 8.5.8.5, pg. 27 Contract

The only stated requirement to apply a "survey sticker upon completion" is in 8.5.7.4 (Dynamic testing). Please clarify that it is

TSA's intent that no "completion" sticker is required for static testing?

See Amendment 00001. SOW section 8.5.7.4 has been updated. A completion sticker is required for both static and dynamic radiation surveys.

Mid‐Size Statement of Work (SOW), Appendix D, Section , E and L, pg. 42, 43 and 47

Contract Please clarify whether Appendix D, Section , E and L, is applicable

(i.e. will this contract have the cited Special Contract Terms?).

Appendix D Sections E and L are applicable.

Mid‐Size Statement of Work (SOW), Appendix D, Section D.7,. pg. 43 Contract

Is the TSA requiring the OEM to perform monthly security scans of the scanners?

Yes.

Mid‐Size Statement of Work (SOW), Appendix D, Section E.5, pg. 43 Contract Does the TSA intend for the COOP to be exercised annually? Yes.

Mid‐Size Statement of Work (SOW), Appendix D, Section T.2, pg. 51 Technical

Is it TSA intent to use PIV & PIN for equipment logon for scanners bought under this program?

No, the TSA requires only username and password at this time.

Mid‐Size Statement of Work (SOW), Section 4.1.8, pg. 6 Contract

Ultraviolet disinfection was not part of the Functional

Requirements Document nor testing. Should this added feature be a required part of the cost proposal?

See Amendment 00001. RFP Table 1 and SOW section 4.1.8 have been revised. This requirement shall be priced as a separate optional CLIN.

Mid‐Size Statement of Work (SOW), Section 4.1.8, pg. 6 Technical

Please define what is required for this requirement on barriers with drawings and configurations defined?

See Amendment 00001. SOW section 4.1.8 has been revised.

Mid‐Size Statement of Work (SOW), Section 4.1.8, pg. 6 Technical

Please define the requirements of the ultraviolet technology to disinfect trays See Amendment 00001. SOW section 4.1.8 has been revised.

Request for Proposal, Section 2.2.1, pg.

Contract Will TSA be providing an Excel Spreadsheet for pricing purposes? No.

Request for Proposal, Section 2.2.1, pg.

Contract

The CLIN Description column of the table as a number of Units listed. Is TSA expecting ladder pricing to be added to that column?

Offerors may provide ladder pricing for Mid‐size systems under

CLIN 0001a.

Request for Proposal, Section 2.2.1, pg.

Contract

CLINs 00001 and 00001A include Site Acceptance Testing (SAT) but

SAT cannot occur until after shipping and installation which is ordered separately under CLIN 0005 and 000005A. Will TSA always order one Installation / Shipping with each System?

TSA intends to procure one (1) Shipping (CLIN 00004‐00004b) with each system (CLINs 00001‐00001b). Both SAT and Installation are included as part of CLINs 00001, 00001a, and 00001b.

Request for Proposal, Section 2.2.1, pg.

Contract

Please confirm that all systems for a single airport will be delivered

"together" during the same single mobilization.

This cannot be confirmed.

Request for Proposal, Section 2.2.1, pg.

Contract

Can the TSA put a limit on the number of installation events at a given airport (for travel costing purposes)?

This cannot be confirmed.

Amendment 00001 TSA Responses to Questions

Request for Proposal, Section 2.2.1, pg.

Contract

Please confirm the minimum # of systems that will be delivered to an airport.

This cannot be confirmed.

Request for Proposal, Section 2.2.1, pg.

Contract

Discounts in pricing is typically derived from efficiencies in manufacturing and quantity discounts through supply chain, therefore please confirm that CLIN 00001a systems will be ordered in batches of 50

No. The TSA reserves the right to exercise optional equipment, at any quantity, up to NTE quantity.

Request for Proposal, Section 2.2.1, pg.

Contract

Discounts in pricing is typically derived from efficiencies in manufacturing and quantity discounts through supply chain, therefore please confirm that CLIN 00001a systems will be awarded at one time.

The TSA reserves the right to exercise optional equipment, at any quantity, up to NTE quantity.

Request for Proposal, Section 2.2.1, pg.

Contract

Please confirm that OCONUS only includes, Alaska, Hawaii and the

United States Territories and does not include other countries.

Yes.

59 Request for Proposal 2.2.1, pg. 7 Contract

In the notes section of the pricing matrix for CLIN 5, you request that the pricing be provided for the region with the highest proposed unit cost. Typically that will be OCONUS. Base on the installation of majority of units will be CONUS, should the evaluation be based on CONUS only?

See Amendment 00001. RFP Table 1 Notes have been updated.

60 Request for Proposal 2.2.1, pg. 7 Contract

For CLIN 0004, can TSA define the calculation of maintenance costs independent of whether there are existing maintenance staff at airports?

No. It is the responsibility of each offeror to determine the necessary maintenance costs.

Maintenance support provided under other TSA contracts is separate from the subject RFP, and will be treated as such.

61 Request for Proposal 2.2.1, pg. 7 Contract

For CLIN 0001 ‐ are items defined in CLIN 7‐12 priced in this CLIN or priced separately in CLIN 7‐12 to account for varied deployment options?

See Amendment 00001 RFP Table 1 and SOW section 4.4 (CPSS

Simulator). CLIN 00001, 00001a, and 00001b must be inclusive all of the requirements contained within SOW Section 4. and SOW Table

1. CLINs 00005‐00012 are priced separately as additional optional quantities.

62 Request for Proposal, Section 2.5, pg. 8 Contract

Wording states that TSA is the only Authorized DHS Agency to issue orders, however, the Basic Ordering Agreement Section 2.3 states

DHS Agencies and Components, other than TSA, reserve the right to issue their own Orders under the BOA following a full and open competition and receipt of proposals. Please clarify.

RFP Section 2.5 specifically references that the TSA is the only authorized DHS Agency to issue and administer an Order resulting from this solicitation .

Request for Proposal, Section 5.1, pg.

Contract

To expedite agreements, please provide contact information (email and phone number) for RELI Group, Global Systems Technologies, Inc. and SAIC.

See Amendment 00001 RFP section 5.1 for contact details.

Request for Proposal, Section 5.1, pg.

Contract

If the contractor support organization does not respond to a request to provide the documentation required, will that be considered a non‐responsive response by the submitter if the submitter provides evidence of attempting to obtain the documentation?

No, however; evidence of attempting to obtain the documentation must be provided.

Request for Proposal, Section 6.5, pg.

Contract

States that proposal must be valid for 180 days, however, Section

6.7.c Period for Acceptance of Offerors states "The offeror agrees to hold the prices in its offer firm for 30 calendar days from the date specified for receipt of offers, unless another time period is specified in an addendum to the solicitation." Please clarify.

Proposals must be valid for 180 days.

Request for Proposal, Section 6.7, pg.

Contract

Please confirm that Offerors are limited to those firms that have submitted QPL systems under an OTA for test and evaluation.

See RFP Section 6.6 Qualification Requirements.

Request for Proposal, Section 6.7.a, pg.

Contract

The associated NAICS code is 334511 with a small business size standard of 1,250 employees, however, this section references "the small business size standard for a concern which submits an offer in its own name, but which proposes to furnish an item which it did not itself manufacture, is 500 employees." Please elaborate on why there is a difference between the two.

FAR Clause 52.212‐1 stipulates that the small business size standard for a concern which submits an offer in its own name, but which proposes to furnish an item which it did not itself manufacture, is

500 employees.

Request for Proposal, Section 6.7.a, pg.

Contract

The associated NAICS code is 334511 with a small business size standard of 1,250 employees, however, this section references "the small business size standard for a concern which submits an offer in its own name, but which proposes to furnish an item which it did not itself manufacture, is 500 employees." Please define manufacture.

A manufacturer is defined as a business that, with its own facilities, performs primary activities in transforming inorganic or organic substances, including the assembly of parts and components, into the end product being acquired.

Request for Proposal, Section 6.7.a, pg.

Contract

Will a business of less than 500 people who do not manufacturer their own product get extra consideration?

No.

Request for Proposal, Section 6.7 b (8),

pg. 35 Contract

Does the offeror have to provide in the written response all reps and certs or only the ones not completed electronically?

See RFP Section 5.4 Annual Representations and Certifications FAR

52.212‐3 Offeror Representations and Certifications ‐ Commercial

Items (OCT 2020).

Request for Proposal, Section 7.3, pg.

Contract

Please confirm that Offerors will be able to continue to test at Level

0 or if achieved, will be able to test at higher detection levels leading up to the procurement?

Yes, testing can continue. Per RFP Section 6.10.2, "TSA will verify the proposed CT system's highest level of detection certification standard achieved no later than May 31, 2021." Per the FRD, the minimum requirement is Accessible Property Screening System

(APSS) Detection Standard Version 6.2 Level 0.

Request for Proposal, Section 7.4, pg.

Contract

Please elaborate on the weighting of each of the 4 Technical

Capabilities in determining the adjectival ratings for Factor 1

See RFP Section 7.6.1. Technical Capabilities within Factor 1 are equal in importance.

Request for Proposal, Section 7.4, pg.

Contract

Please confirm that Detection Capability is the most important capability in determining the adjectival ratings for Factor 1

See RFP Section 7.6.1. Technical Capabilities within Factor 1 are equal in importance.

Request for Proposal, Section 7.4, pg.

Contract

Please elaborate on each of the weighting of Socio‐Economic

Considerations and Past Performance in determining the adjectival ratings for Factor 2?

This information is Source Selection Sensitive.

Request for Proposal, Section 7.6, pg.

Contract

Please provide how the throughput of 200 items per hour will be recorded and calculated?

Throughput is measured by average rate of items per hour under fully loaded conditions and shall be verified based on official results collected through testing under the associated QPL.

Amendment 00001 TSA Responses to Questions

Request for Proposal, Section 7.6, pg.

Contract

Please provide how the Mean Time Between Critical Failure will be recorded and calculated.

Mean Time Between Critical Failure is calculated as (Operating

Hours ‐ Downtime) / Number of Critical Failures. It shall be verified based on official results collected through testing under the associated QPL.

77 RFP Table 1, CLIN Schedule Contract Could TSA please define what is meant by search benches? CLIN

00007

See Amendment 00001. SOW Table 1: Major Components and

Section 4.7 (Search Bench) have been revised.

78 RFP Table 1, CLIN Schedule Contract CLIN 00001, Is the assumption that installation and freight are the same CLIN or should installation be included in CLIN 1 instead?

See Amendment 0001. RFP Table 1 has been revised. CLIN 00001, 00001a, and 00001b are inclusive of installation. Shipping by region is separately included under CLIN 00004.

79 RFP Table 1, CLIN Schedule Contract CLINs 10, 11 and 12. Does TSA not consider these as part of CLIN

00001?

See Amendment 00001 RFP Table 1 and SOW Table 1. CLIN 00001, 00001a, and 00001b must be inclusive all of the requirements contained within SOW Section 4 except for SOW section 4.1.8. SOW section 4.1.8 requirements are separately priced optional CLINs

00014 and 00015. CLINs 00005‐00012 are priced separately as additional optional quantities.

80 RFP Table 1, CLIN Schedule Contract

CLIN 00005, Can TSA provide a rough estimate of how many systems would be deployed to each region (West, Central, and

East) and/or outside the continental U.S.?

This cannot be confirmed.

81 RFP Table 1, CLIN Schedule Contract CLIN 00004, Does the TSA want the simulators/workstations to be covered by the Maintenance and Logistics service contract?

No. All equipment under CLINs 00001, 00001a, and 00001b plus all optional equipment exercised under CLINs 00005‐00012 shall be included in the warranty of this subject contract.

82 RFP Table 1, CLIN Schedule Contract

CLIN 00004, Does TSA want the other items (bins, carts, brackets, etc.) provided by Smiths to be covered by the Maintenance and

Logistics service contract

No. All equipment under CLINs 00001, 00001a, and 00001b plus all optional equipment exercised under CLINs 00005‐00012 shall be included in the warranty of this subject contract.

83 RFP Table 1, CLIN Schedule Contract CLIN 00004, Does the TSA want the simulators/workstations to be covered by the Maintenance and Logistics service contract?

No. All equipment under CLINs 00001, 00001a, and 00001b plus all optional equipment exercised under CLINs 00005‐00012 shall be included in the warranty of this subject contract.

84 RFP Section 5.1 Contract Can TSA please provide POCs for each company and we can coordinate NDAs with them?

See Amendment 00001 RFP section 5.1 for contact details.

85 RFP Section 5.3 Contract

This section requires OEMs confirm whether or not we are acting as lead system integrators. Does TSA intend to utilize systems integrators for installations typical of previous deployments?

Yes.

86 RFP Section 6.6 Contract

Can TSA clarify whether or not a certain configuration, once added to the QPL, can only be sold by the Prime that submitted that particular configuration's QDP?

The TSA has no limitations concerning who may propose a system that has been successfully added to the QPL.

87 RFP, Table 1 CLIN 00014 Technical

For FAT, There are scenarios where the CT and ASL could be different companies. Is TSA open to FAT'ing a certain number initially only (preferred), or alternatively allowing FATs to take place individually/separately for CT and ASL?

An ASL is not required for CPSS Mid‐Size Systems. FATs are the

Contractor's responsibility, but the COR must approve the

Contractor's FAT Plan and TSA reserves the right to observe the scheduled FATs as determined necessary by the Government.

88 SOW Section 4.1.8 Contract systems must include acrylic barriers and ultraviolet technology to disinfect baggage tray bins. Can TSA please further define this requirement for pricing purposes?

See Amendment 00001. RFP Table 1 and SOW section 4.1.8 have been revised. This requirement shall be priced as a separate optional CLINs.

89 SOW Section 4.1.8 Technical

Are vendors expected to provide details of acrylic barriers and UVC disinfectant capabilities as part of this response? If so, in what section and does it affect page count?

No. See Amendment 00001. RFP Table 1 and SOW section 4.1.8 have been revised. This requirement shall be priced as a separate optional CLINs.

90 SOW Section 4.1.9 Contract

Can TSA provide a rough estimate of the number of systems that will need seismic brackets, leveling shims, and/or AT2 roller table attach brackets?

This cannot be confirmed prior to award; quantities per site will vary.

91 SOW Section 4.1.8 Contract

This section requires OEMs to provide ultraviolet technology to disinfect bins. Can TSA provide more details on how this would be installed on a mid‐size systems that has no tray return system?

See Amendment 00001. RFP Table 1 and SOW section 4.1.8 have been revised. This requirement shall be priced as a separate optional CLINs.

92 SOW Section 4.1.9.3 Technical

For the purposes of this bid, can the vendors assume that referenced radiation testing requirement is consistent with current practice (i.e. radiation surveys performed every 6 months) during planned maintenance activities?

Please refer to SOW Section 8.5.8.

Offerors shall prepare their bid in accordance with the radiation testing requirements outlined in this solicitation SOW.

93 SOW Section 4.1.10 Technical Does this requirement also include potential future upgrades to system hardware to provide PI detection capability?

See Amendment 00001. SOW Section 4.1.11 (formally 4.1.10) has been revised. It does not include Prohibited Items.

94 SOW Section 4.4.1 Technical Is the requirement to supply the appropriate servers and workstations to support two (2) simulators?

See Amendment 00001. SOW Section 4.4. (CPSS Simulator) has been revised.

95 SOW Section 4.4.5 Technical

How does the Government intend to pay for or license the use of a simulator application aside from what is delivered with the two procured simulators?

See Amendment 00001. RFP Table 1 and SOW Section 4.4. (CPSS

Simulator) have been revised. There is an optional CLIN to procure additional Simulators, as needed.

96 SOW Section 4.1.14 Technical

Would the TSA consider amending this requirement as the simulator software can only be guaranteed to meet the requirements spelled out in previous sections when used with the appropriate vendor‐provided hardware? Furthermore, the simulator software contains IP and data rights that may not be provided in the response to this solicitation.

See Amendment 00001. SOW Section 4.4. (CPSS Simulator) has been revised.

97 RFP 2.1 page 5, paragraph 1 Contract

If only one bidder’s product is on the QPL by May 31, 2020 but, other bidders' products are still undergoing QDP review, QT and/or

OT&E on that date, is the TSA compelled to award to the one QPL bidder even if a non‐QPL bidder would ultimately represent the best value to Government?

The Government will award an order resulting from this RFP to the responsible Offeror whose offer, conforming to the RFP, is determined to be the most advantageous to the Government and represents the best value considering trade‐offs between price and all non‐price factors.

98 RFP 2.2.1 pages 5‐6, and 2.9.2 page 9 Contract

Table 1 in Section 2.2.1 indicates a base period of one year (see

CLIN 00003). Section 2.9.2 indicates a period of performance with a base period of three years. Would TSA please clarify the length of the base period? If three years, should the number of months for

CLIN 00003 be changed from 12 to 36?

Yes, see Amendment 00001. RFP Table 1 has been revised.

RFP 3.2.2 (Table 3, CLINs 00002 &

00002a), page 14 Contract

Would TSA consider allowing the Contractor to submit invoices for delivered simulators on a per unit basis?

No.

Amendment 00001 TSA Responses to Questions

RFP 3.2.2 (Table 3, CLINs 00006 ‐

00012), page 14 Contract

Would TSA consider allowing the Contractor to submit invoices for delivered accessories on a per unit basis?

No.

101 RFP 5.1, page 15, paragraphs 3‐6 Contract

Can TSA provide points of contact for each of the proposed

Contractors supporting the selection process in order to facilitate the execution of the required non‐disclosure agreements?

See Amendment 00001 RFP section 5.1 for contact details.

102 RFP 5.1, page 15, paragraphs 2 Contract Does TSA have a standard format for such non‐disclosure agreements and, if so, can TSA provide a template?

No.

103 RFP 5.1, page 15, paragraph 6 Contract In which volume of the proposal shall the requested agreements be included?

See Amendment 00001. RFP Table 7 and section 6.10.1 have been revised.

104 SOW 4.1.10, page 7 Contract

Would the TSA please consider removing the phrase "or any subsequent version of this document"? There is a considerable and undefined amount of risk for a Contractor to commit to meeting unknown requirements at no cost to the Government.

Yes, see Amendment 00001. SOW Section 4.1.11 (formerly Section

4.1.10) has been revised.

105 SOW 4.1.9.2, page 7, FRD page 19 Technical

The FRD requirement (shall 105) is 2%. The SOW requirement is

2.5%, which is inconsistent with the FRD. Would TSA please confirm the Contractor needs to meet the FRD requirement, which is the requirement applicable to the qualification data package already submitted?

See Amendment 00001. SOW Section 4.1.10.2 (formerly Section

4.1.9.2) has been revised to 2%.

106 SOW 4.2.1, page 8 Contract

The SOW states that the Contract "shall" provide bin return and bin rerun carts, but the CLINs covering these items (00008 and 00009) are optional. Should there be a quantity of bin return and bin rerun carts that are not optional?

See Amendment 00001 RFP Table 1, SOW Table 1, and SOW section

4.4 (CPSS Simulator). CLIN 00001, 00001a, and 00001b must be inclusive all of the requirements contained within SOW Table 1 and

SOW Section 4. CLINs 00005‐00012 are priced separately as additional optional quantities.

107 SOW 4.4.10, page 10 Technical

The STIP requirement in SOW 4.4.10 appears to go beyond what is required by the FRD (see shall statements 177‐182). Since the STIP interface definition has not yet been completed, it is not yet possible to provide this capability. Would TSA consider deleting

SOW 4.4.10?

Yes, see Amendment 00001. SOW Section 4.4. (CPSS Simulator) has been revised.

108 SOW 4.6.2.3.1, page 12 Technical

Regarding "taking the intended checkpoint location down for installation", would TSA please clarify what specific event marks the beginning of the two‐day period?

When the TSA Systems Integrator (SI) is on site and work begins on installation efforts after removal of the existing lane equipment and completion of any site preparation for new equipment.

109 SOW 4.6.2.3.1, page 12 Technical

Would TSA please confirm the two‐day period starts after removal of the existing lane equipment (by others) and completion of any site preparation for the new equipment (by others)?

Yes, that is correct.

SOW 4.6.2.3 page 12, SOW 4.6.2.3.1 , Technical

Would the TSA please confirm the SAT takes place after the two days of lane down time for installation (i.e., on a third day)?

SAT takes place whenever system installation is complete. It may be the same day or the next day.

111 SOW 8.4.2 page 22 Contract

Would the TSA please confirm that the 10% disincentive is deducted from the monthly maintenance price per unit (CLINs

X0004) times the number of units at the airport, as is the standard on other TSA ILS contracts?

Confirmed.

112 SOW Attachment 10 page 59 Technical

Paragraph 10.2.4 Service Level Agreement (SLA) Performance

Metrics and paragraph 10.2.5 Contract Disincentives refer to the

Contractor meeting the SLA performance requirements as specified in C.4.4.1. Where is paragraph C.4.4.1 located?

Typographical error. See Amendment 00001. Attachment 10 has been updated.

SOW Attachments 1 ‐ 14, page 55

(¶7.1), page 57 (¶10.2.5.2 and

¶10.2.5.3), page 58 (¶10.2.2), page 59

(¶10.2.3 three times)

Technical

There are several references to Attachment D‐2 (Transportation

Security Equipment (TSE) Metrics Terms and Definitions and RMA

Metrics). Where do we find this attachment?

Typographical error. See Amendment 00001. Attachments have been updated.

114 SOW, Section 4.1.1. Contract & Technical Is the Contractor responsible for providing tables, chairs for screening operations?

The Contractor shall provide all tables required for the system (i.e., search table/bench, PVS table, and divest tables, as applicable).

The Contractor is not responsible for providing chairs.

115 SOW, Section 4.1.4 Contract

SOW states, "Contractor shall deliver and maintain a First Article

Test and Evaluation unit at the Contractor's facility that has successfully completed a Factory Acceptance Test". Will TSA be observing the initial FAT test?

Yes.

116 SOW, Section 4.1.5.1 Contract

"Contractor shall deploy a minimum of twenty‐two (22) CPSS Mid‐

Size systems per month". Pricing requested is for 50 units. If TSA ordered 50 units in the first month (or two months), how long should the Contractor be prepared to produce a minimum of 22 systems per month?

The contractor shall deploy a minimum of 22 systems per month, or until there are no more systems funded on the contract to deploy.

117 SOW, Section 4.1.8 Contract & Technical

"Contractor shall deliver a system that provides protection to reduce the potential exposure of passengers and the TSA workforce to public health threats. This includes, but is not limited to acrylic barriers to increase social distance and reduce direct contact between passengers and TSA employees, and ultraviolet technology to disinfect baggage tray bins against transmission of contagions." These items were not requested in the QDP or for testing and were not part of the OTA pricing scope. There is no TSA specification for the acrylic barriers or ultraviolet technology in the

Acceptable Capability List or Checkpoint Requirements and

Planning Guide (CRPG). How do we account for the cost and requirements for these items asked to be included?

See Amendment 00001. RFP Table 1 and SOW section 4.1.8 have been revised. This requirement shall be priced as a separate optional CLINs.

118 SOW, Section 4.1.8 Contract & Technical

"This includes, but is not limited to acrylic barriers" We did not see

TSA specifications for acrylic barriers or ultraviolet technology in the Checkpoint Requirements and Planning Guide (CRPG) or TSA

Acceptable Capability List (ACL/QPL). Do you have specifications for these items you want included? Are they required to be acrylic barriers?

See Amendment 00001. RFP Table 1 and SOW section 4.1.8 have been revised. This requirement shall be priced as a separate optional CLINs.

119 SOW, Section 4.1.9 & 4.1.9.1 Contract

"Seismic brackets": Does the contractor need to include seismic brackets and associated costs in every system or only the systems that will be deployed to a location that has state requirements for seismic?

The cost of seismic brackets is to be included in the cost for installation, which is included as part of the CPSS system. Seismic brackets will only be required in certain locations based on state and local requirements.

Amendment 00001 TSA Responses to Questions

120 SOW, Section 4.1.9.1 Contract & Technical

Seismic Brackets: "The points (e.g. brackets) shall be outward facing for ease of installation". There are not specifications provided in the CRPG under Section 9‐3 Seismic Anchoring, Fire

Codes and Other Local Codes. Can you provide a specification, drawing or elaborate on the definition of brackets being "outward facing"?

Seismic brackets are required based on state and local codes. TSA requires that CPSS systems meet all applicable federal, state and local codes. Seismic brackets must be easily accessible for system maintenance or removal and installed under machine or in a fashion that it does not protrude into the path or potential path to create a trip hazard.

121 SOW, Section 4.1.13 Contract Can you please provide an example, template or document outline for an interface control document (ICD)?

No.

SOW, Section 4.4.1 and RFP, Section

2.2.1 CLIN Structure

Contract

"Contractor shall provide two (2) simulators, workstations and servers as part of the CPSS system". The line item for CLIN 00002‐

CPSS System Simulators 100. Can you please clarify the number of simulators as 100? What are the number of workstations? What is the number of servers? Is the price for the workstations and servers to be included in the CLIN 00001 CPSS Mid‐Size Systems price?

See Amendment 00001 RFP Table 1, SOW Table 1, and SOW section

4.4 (CPSS Simulator). CLIN 00001, 00001a, and 00001b must be inclusive all of the requirements contained within SOW Table 1 and

SOW Section 4. CLINs 00005‐00012 are priced separately as additional optional quantities.

123 SOW, Section 4.4.9. Contract & Technical

"4.4.9. The Contractor shall provide simulator software with a

Graphical User Interface (GUI) that has the same look, feel, and functionality as the actual CT machine." This is a new requirement and requires further review for competitive purposes.

(coloration, button‐ology, etc.).

No response required.

124 SOW, Section 4.6.1.2 Contract

Does the scheduled FAT have to take place individually for the CT and the ASL? Would another one be scheduled for the two integrated systems?

ASLs are not required for CPSS Mid‐Size Systems. The FAT should be on the fully integrated CPSS Mid‐size System.

125 SOW, Section 4.6.2.3 Contract Can TSA provide a copy of the approved iSAT plan, procedures and testing requirements?

No. Per SOW Section 4.10.2.1. (formerly SOW Section 4.6.2.1.), "The Contractor shall provide support, as needed, for TSA's

SAT/iSAT plan and procedures development. Once these procedures are developed, they will be provided to the Contractor.

The Contractor shall review and provide their final recommendations to the COR within twenty (20) calendar days."

126 SOW, Section 4.6.2.3.1 Contract

"System shall be installed and operational within two days of taking down the intended checkpoint location down for installation". Is this dependent upon the number of lanes being installed? Is

Contractor required to be ready for iSAT within 48 hours of installation? Does this requirement including all system testing required for iSAT? Can you please define this requirement further?

The requirement is for an individual lane/system install, regardless of number of systems being installed. The two day installation requirement is not inclusive of SAT/iSAT. SAT/iSAT is typically performed one (1) day after the completion of system installation.

SOW, Section 4.6.2.3.3.

Contract & Technical

TSA will provide notification of SAT/iSAT to the Contractor at least ten (10) calendar days prior to execution of SAT/iSAT. How is this and section 4.6.2.3 possible if the TRN can only be submitted after the system in installed and tested for iSAT readiness?

CPSS System delivery, installation, and SAT/iSAT timeline should be coordinated and agreed upon between the vendor and TSA.

128 SOW, Section 6.3 Contract

"Contractor shall provide storage for each CPSS system as no additional cost to the Government for up to six (6) months after

FAT to accommodate deployment". Does TSA want the Contractor to assume and include the cost of storage for each CPSS system for six months then? What if the time period is longer than six (6) months for a system?

Per the SOW, the Contractor shall provide storage for each CPSS system at no additional cost to the Government for up to six (6) months after FAT to accommodate deployment. The TSA will not determine how an Offeror shall include the potential need for storage in their price proposal. The TSA does not anticipate the need for storage longer than a duration of six (6) months.

129 SOW, Section 7.1.4 Contract

"Warranty period shall include hardware or software upgrades to support new algorithms". If the warranty period could last as long as 10 years, would TSA pay for these upgrades as it is unknown what hardware or software may be required for an undetermined specification today?

See Amendment 00001. SOW section 4.1.11 (formally 4.1.10) has been revised.

130 SOW, Section 8.1.3.6 Contract "Contractor responsible for storage of all spare parts". Should the cost of warehousing spare parts be included in each lane?

The TSA will not determine how an Offeror shall include this requirement in their price proposal.

131 SOW, Section 8.3.1 Contract

"Contractor shall provide the calculations and raw data on a monthly basis to TSA". Does TSA require Maximo for Service Level

Reporting?

No. The methods and tools to capture, store and report data is determined by the contractor.

132 SOW, Section 8.5.5.1 Contract

"Level I‐TSA primarily performs preventive maintenance every shift on a daily (one (1) to three (3) times) and weekly basis." Who monitors the Level 1 TSA responsible maintenance tasks? What if

Level 1 tasks are not performed and adversely effect the

Operational Availability (Ao)? How is this monitored, reported and accounted for in any disincentive scenario.

The airport tracks Level 1 preventive maintenance completion monthly. If failures occur due to regular screening usage, (not unintentional or intentional external occurrence in operational environment) then the failure would be considered a relevant critical failure and tracked and reported as defined in Attachment

10, TSE Metrics Terms and Definitions & RMA Metrics.

SOW, Section 18‐6.2.2‐ Installation &

Site Prep Contract

The System Integrator will handle the site preparation, shipping from Riggers Staging Facility to the airport (as needed), rigging, and coordination with OEM. Is the System Integrator going to deliver the equipment to the checkpoint and place the equipment in the location according to TSA and OEM design specifications? (i.e.‐ who is responsible for the delivery from airport curb to checkpoint, floor protection and final placement of the CT and lane modules, etc.?)

The Systems Integrator will provide shipping and rigging from the riggers staging facility (RSF) to the airport via separate contract.

This includes the rigging into the final location in the checkpoint and placing the system in the appropriate lane(s) per approved design.

All aspects of the rigging will be covered by the System Integrator.

134 Attachments+1‐14 Contract

Are these attachments for informational purposes and to be used as a reference for what will be required if selected? These attachments do not require a response for the RFP, correct?

SOW attachments have been provided as SOW references only.

Attachments+1‐14, page 4, 10.2.4.1.2 and 10.2.4.6.5.2 Contract

Can you provide the TSA approved Configuration Item (CI) nomenclature or direct to where this is located?

Refer to SOW attachments.

Attachments+1‐14, page 10,

10.2.4.6.5.6 Contract

Can you provide an example/definition of what are "like items" requiring serial/lot numbers?

“Like items” are assets that are similar in structure, functionality, design, cost, etc.

Amendment 00001 TSA Responses to Questions

RFP: CLINs 00001 and 00001a CPSS Mid‐

Size Systems, Each Contract

Define what is included with procurement of each CPSS Mid‐Size

System as warranty, bins, etc. are listed as separate CLINs.

See Amendment 00001 RFP Table 1, SOW Table 1, and SOW section

4.4 (CPSS Simulator). CLIN 00001, 00001a, and 00001b must be inclusive all of the requirements contained within SOW Table 1 and

SOW Section 4. CLINs 00005‐00012 are priced separately as additional optional quantities.

RFP: 6.6 Qualification Requirements.

Upon receipt of the Offeror's Proposal, TSA will verify with the test team that the Offeror's proposed configuration is successfully placed on the Mid‐size

QPL…

Contract Clarify the language as no Applicate will be successfully placed on the QPL at time 'Upon of Receipt of Offeror's proposal.'

See Amendment 00001. RFP section 6.6 Qualification

Requirements, has been updated.

139 RFP: 6.6 Qualification Requirements Contract Are approved Qualification Data Packages (QDP) required prior to submittal of the RFP?

An approved QDP is not required as a requirement to respond to the subject RFP. However; the Offeror’s proposed CT system must be qualified under the associated QPL in accordance with FAR

52.209‐1 ‐‐ Qualification Requirements on or before May 31, 2021.

140 RFP: Frequency of Invoice Submission Contract

Invoices for Transportation Security Equipment, related peripheral equipment, and/or associated services outlines 'temporary storage'. Define the timeframe for temporary storage pending the airport availability for installation.

Up to six months, per SOW section 6.3.

RFP, Section 2.2.1 (pg 7); Section 7.6.3

(pg 44) Contract

Sections 2.2.1 and 7.6.3 state “The evaluated price shall be evaluated on a quantity to be determined.” When and how will

TSA inform offerors of the quantities to be used in its price evaluation?

Offerors should provide their best pricing for all quantities. Quantity to be evaluated is Source Selection Sensitive.

Attachment A SOW, Section 4.1.10 (pg

7) Contract

SOW Section 4.1.10 states delivered CPSS systems must be

“upgradeable… at no cost to the Government.” Does this provision mean the systems must have the capability to be upgraded to future detection levels at no additional cost, or that the actual work of performing the upgrade (e.g. labor for distribution and physical installation of software changes onto installed systems) is expected to be done at no cost?

See Amendment 00001. SOW Section 4.1.11 (formerly Section

4.1.10) has been revised.

Attachment A SOW, Section 4.1.10 (pg

7) Contract

SOW Section 4.1.10 also states delivered CPSS systems must be upgradeable to all detection levels contained within the 2018 APSS

Detection Standard, “or any subsequent version of this document”.

How can offerors commit to be upgradeable to future Detection

Standards before knowing what subsequent versions of APSS

Detection Standards may require?

See Amendment 00001. SOW Section 4.1.11 (formerly Section

4.1.10) has been revised.

Attachment A SOW Section 4.1.5.1 (pg

6) Contract

The Contractor is required to deploy a minimum of (22) CPSS Mid‐ sized Systems per month after the first operational unit at multiple locations as directed by TSA. Can TSA provide information re. the number, or quantity range, of locations required to be deployed to within a given month?

This cannot be confirmed prior to award; quantities per site will vary.

RFP, Section 2.2.1 (pg 7);

Amendment A SOW, Section 8.6.3 (pg

28)

Contract

RFP Section 2.2.1 requires FFP unit prices for Low, Medium and

High Complexity Events, while Amendment A SOW Section 8.6.3 defines a process for Contractors to respond to catastrophic events and provide a ROM for Corrective Maintenance (CM) based on the actual characteristics of the specific event and its impact on the system(s) involved. Please clarify how these two approaches are compatible? How would TSA define the parameters around a FFP

Event, as each is unique as anticipated in Section 8.6.3?

See Amendment 00001. SOW Section 8.6.3. has been revised to align with the RFP.

RFP Section 2.9.2 (pg 9); RFP Section

2.2.1 (pg 6) Contract

Section 2.9.2 defines Order Period of Performance to be a base period of (3) years from date of award plus eight (8) option years for Warranty/ Maintenance and Logistics Support, which implies a total PoP of 11 years. However, Section 2.2.1 Program

Management (CLIN X0003) has a base period of (1) year followed by (9) Option years, suggesting a total PoP of only 10 years.

Shouldn't these two PoPs be consistent? Please clarify.

Yes, see Amendment 00001. RFP Table 1 has been revised.

Amendment A SOW Section 5.2 (pg

16);

RFP, Section 2.7 (pg 9); BOA Section 2.7

(pg 6).

Contract

Is the Post Award Conference called out in SOW Section 5.2 the same or in addition to the Post Award Order Conference defined in

RFP and BOA Sections 2.7? Whether they are the same or two…