Transportation Security Administration Government... · Transportation Security Administration...

Transportation Security Administration

EXPLOSIVE DETECTION SYSTEM

QUALIFIED PRODUCTS LIST (EDS QPL)

70T04019R9CAP1086

FUNCTIONAL CATEGORY TYPE II /

TRACK 0 / WINDOW 1

Request for Qualification Verification Package

(RFQVP)

July 16, 2019

Amendment 00001

70T04019R9CAP1086 Functional Category Type II / Track 0/ Window 1

of 16

TABLE OF CONTENTS SECTION 1 – ANNOUNCEMENT OF QPL FUNCTIONAL CATEGORY TYPE II / TRACK 0 /

WINDOW 1 3

SECTION 2 – RELEASE REQUIREMENT DOCUMENTS 3

2.1 Functional Category Type II / Track 0 / Window 1 Requirements Documents 3

2.2 Instructions to Request and Access the SSI and Classified Requirements Documents 4

SECTION 3 – SUBMISSION ELEMENTS 8

SECTION 4 – DECISION GATE 1: QVP SUBMISSION 9

4.1 Decision Gate 1 – QVP Submission Instructions 9

4.2 Decision Gate 1 – QVP Submission Date 10

4.3 Decision Gate 1 – Questions about RFQVP 11

4.4 Decision Gate 1 - QVP Evaluation 11

SECTION 5 – DECISION GATE 2: CERTIFICATION TESTING 12

SECTION 6 – DECISION GATE 3: QDP SUBMISSION 13

6.1 Decision Gate 3 – QDP Submission Date 13

6.2 Decision Gate 3 – QDP Submission Evaluation 13

SECTION 7 – DECISION GATE 4: Government Verification and Validation 14

SECTION 8 – ADDITIONAL INFORMATION 14

8.1 Required Qualification Level 14

8.2 Evaluation Results and Remediation 15

SECTION 9 – APPLICABLE FUNCTIONAL CATEGORY TYPE II / TRACK 0 / WINDOW 1

CLAUSES 16

9.1 FAR Clause 52.204-2 Security Requirements (Aug 1996) 16

SECTION 10 – ATTACHMENTS 16


of 16

SECTION 1 – ANNOUNCEMENT OF QPL FUNCTIONAL

CATEGORY TYPE II / TRACK 0 / WINDOW 1

Explosive Detection System (EDS) Functional Category Type II (Stand-Alone and Mini-In-Line

EDS) / Track 0 (Functional Requirements Document (FRD) v4.0) / Window 1 is hereby being

opened to solicit Qualification Verification Packages (QVPs) for Transportation Security

Administration’s (TSA’s) EDS’. These systems will be used primarily for screening for

explosives. These systems shall be designed to operate in checked baggage airport environments.

These systems shall have the ability to withstand a variety of environmental conditions and meet

all applicable cybersecurity requirements as outlined in the requirements documents.

In order to submit a QVP, vendors must be registered in the System for Award Management

(SAM) and must not have any Active Exclusion Records. Reference the EDS QPL Overview

document for instructions.

Functional Category Type II / Track 0 / Window 1 requires successful completion of all eight (8)

steps outlined in the EDS QPL Overview document. Evaluations identified in this document are

conducted as an integral part to approve advancement through Steps 1 - 8 of the overall

Qualification Process used by TSA to place approved EDS on the QPL.

The intent is that TSA will be soliciting under Functional Category Type II / Track 0 / Window 1

for an earliest possible award in Fiscal Year 2021. The Government is not required to delay a

proposed award in order to provide a potential vendor with an opportunity to demonstrate its ability

to meet the standards, even if the vendor has been accepted into the Qualification Process.

If a system/configuration has already been qualified by TSA, please submit your TSA qualification

letter or equivalent (i.e. proof of TSA purchase) for transfer to this QPL.

SECTION 2 – RELEASE REQUIREMENT DOCUMENTS

2.1 Functional Category Type II / Track 0 / Window 1

Requirements Documents

The applicable requirements for Functional Category Type II / Track 0 / Window 1 EDS are the

following:

2.1.1. TSA Qualification Management Plan for the Electronic Baggage Screening

Program Explosives Detection Systems v 3.0 (QMP) (For Official Use Only)

2.1.2. TSA Functional Requirements Document for the Electronic Baggage Screening

Program, Type I and Type II EDS v4.0, EDS Competitive Procurement 2 - Track

0 (FRD) (Sensitive Security Information (SSI))

2.1.3. TSA Detection Standards v5.8 & v7.2 (SECRET)

2.1.4. TSA Detection Functional Requirements Document (DFRD) v7.3a, Rev. 1

(SECRET)


of 16

2.1.5. TSA Acquisition Qualification Policy v1.0

2.1.6. TSA Test & Evaluation Guidebook, Rev. 3

2.1.7. TSA OSC Third Party Testing Strategy v1.0

Instructions for requesting these documents are provided within Section 2, Paragraph 2.2.

2.2 Instructions to Request and Access the SSI and Classified

Requirements Documents

Potential vendors must obtain specific authorization in order to obtain SSI and Classified

information. SSI and Classified information will not be available or otherwise provided or

disclosed to any person not specifically authorized to receive it. SSI and Classified information

provided under this RFQVP announcement may only be used to satisfy acquisition requirements

associated with the EDS QPL.

Vetting is anticipated to take approximately three (3) weeks (additional time is required for vetting

Foreign Nationals). TSA requests vetting submissions to be limited to no more than 10 employees.

Vendors are required to submit their SSI vetting request to review the applicable requirements

documents no later than 30 days after the Window is open. Vendors requesting SSI vetting after

this time will have to wait until the next submission Window. Vendors may add or remove a total

of two (2) people from the SSI approval list anytime throughout the Qualification Process.

However, any requests for individuals to be added must first be approved by the Contracting

Officer prior to initiation, and these individuals will be required to be vetted in accordance with

the process stated within the applicable Window.

2.2.1. Request for SSI –

o Background. Sensitive Security Information (SSI) may be available to vendors

in preparing responses to this acquisition. Potential vendors must obtain

specific authorization in order to obtain SSI. SSI will not be available or

otherwise provided or disclosed to any person not specifically authorized to

receive it. SSI provided under this acquisition may only be used to satisfy

acquisition requirements.

o Senior Corporate Official. Each vendor (and subcontractor/team member) must

separately designate in writing to the Contracting Officer a single, corporate

official who will serve as the single point of contact for sensitive information.

This individual must certify that all appropriate protections will be followed,

only authorized individuals will have access to the sensitive information, and

that those individuals adequately understand their responsibilities to protect the

information. This official must also certify to the Contracting Officer every 60

days that all appropriate protections have been followed, only authorized

individuals have access to the sensitive information, and that those individuals

with access adequately understand their responsibilities to protect the

information. A copy of this certification shall also be emailed to

[email protected]. This official will also ensure that the Contracting

mailto:[email protected]


of 16

Officer is notified of staffing changes or circumstances in which individuals no

longer need access to the information.

o Vendor Responsibility. The Contracting Officer will review the System for

Award Management (SAM) and Dunn and Bradstreet to ensure that the

corporate entity would not otherwise be precluded from receiving a contract

award. While this review does not replace the responsibility determination

required by FAR part 9, it may prohibit vendors from receiving SSI information

during the solicitation phase of the acquisition.

o Criteria for Release. As part of this acquisition, SSI may only be accessed by

individuals which have successfully passed a Security Threat Assessment. This

assessment may include a verification of site facility clearance in the National

Industrial Security Program (NISP), contractor suitability determination or

other federal background investigation, individual security clearance(s), and if

required, a criminal history records check (CHRC) and/or a check against

terrorism databases.

o Information Requirements. Consistent with the criteria release described

above, vendor’s Senior Corporate Officials must provide the appropriate

information to the TSA as identified below. Note that this requirement applies

likewise to any prospective subcontractor, joint venture partner, or “team”

company whose access to the specified SSI and consequent input into the

planned proposal is necessary to prepare and complete the proposal. All

information must be emailed to [email protected].

Senior Corporate Officials shall provide the Contracting Officer via

email with the CAGE code of the vendor’s facility that will manage the

proposal, company DUNS number, and address; and

Senior Corporate Officials shall provide the following information for

all employees who require access to SSI in a single password protected

Microsoft Excel spreadsheet emailed to the Contracting Officer. The

password for the password-protected spreadsheet shall be sent to the

Contracting Officer in a separate email, at the same time.

Employee Full Name:

Employee Gender: (i.e., Male or Female)

Employee Birth Date:

Employee Citizenship:

Social Security Number:

Indication of whether any nominated employees have:

o Previously received a TSA suitability determination;

o Undergone a federal background investigation; or

o Possess an individual security clearance



of 16

o Privacy Act Statement. TSA will use the information provided to conduct a

security threat assessment on individuals who seek access to Sensitive Security

Information (SSI). The information will be shared within DHS with personnel

who need the information to perform their official duties. Additionally, DHS

may share the information with law enforcement, intelligence, or other

government agencies as necessary to identify and respond to potential or actual

threats to transportation security in accordance with the routine uses identified

in the applicable Privacy Act system of records notice (SORN), DHS/TSA 002,

Transportation Security Threat Assessment System (T-STAS). This SORN was

last published in the Federal Register on November 8, 2005, and can be found

at 70 FR 67731- 67735. Authority: 49 USC 114. Furnishing this information

is voluntary. However, failure to furnish the requested information may delay

or prevent the completion of your security threat assessment, without which you

may not be granted access to the SSI.

o Notification of Assessment. If it is determined that covered individuals are not

eligible to receive access to particular SSI based on the threat assessment, TSA

will provide the individuals and company point of contact a written

determination that provides notification that the individual does not qualify to

receive SSI. Appeal of the determination will not be permitted due to the time

sensitive nature of the acquisition process, however, the potential vendor may

nominate another individual to receive SSI access. In the event that an

individual is determined to be a security threat and the individual believes that

the results of the screening are inaccurate, he or she will be informed by TSA

on how to pursue redress from TSA, however due to the demanding acquisition

schedule, TSA will not delay an acquisition to resolve redress issues.

o Non-Disclosure Agreements. Each vendor employee requesting access to SSI

as specified herein will be required to execute a Non-Disclosure Agreement

(DHS Form 11000-6). The executed forms shall be provided with and as part

of the submission of information reflected in Paragraph E above. The vendor

should understand that employees granted access to SSI and signing a non-

disclosure agreement are bound by the terms of that agreement indefinitely,

notwithstanding their employment status or any other background checks or

clearances granted by any Government agency.

o Return of SSI. Any SSI provided to the vendor must be returned to the

Government and verified by the Government prior to the beginning of proposal

evaluations. Any vendor not returning SSI provided directly to them will be

subject to penalties as prescribed by law and otherwise rendered ineligible for

further consideration in the evaluation.

2.2.2. Request for Classified National Security Information (CNSI) –

o Under this RFQVP, the vendor may access classified material at the TSA

headquarters and/or at a vendor’s facility.


of 16

o Only vendors who possess a valid Personnel (Security) Clearance (PCL) will

be authorized to discuss or read classified materials at TSA headquarters only.

o Only vendors who possess a valid Facility (Security) Clearance (FCL) and PCL

will be authorized to receive and store CNSI at their facility in order to develop

a QVP.

o To access Classified National Security Information (CNSI) a vendor must have

an approved DD Form 254 for each company that will participate in the

Qualification Process. If an existing approved DD Form 254 specific to the

TSA is not available, a DD Form 254 approval request must be submitted within

30 days of the release of this solicitation.

o Information Requirements. The Senior Corporate Officials shall provide the

following information via email (Note that this requirement applies likewise to

any prospective subcontractor, joint venture partner, or “team” company whose

access to the specified CSNI is necessary):

Vendor Name

Vendor CAGE Code

Vendor Facility Security Officer’s Name

Vendor Facility Security Officer’s Phone Number

Vendor Facility Security Officer’s Email

Request to access classified material at the TSA headquarters and/or at

a vendor’s facility

o Issuance of a DD Form 254 is anticipated to take approximately six (6) weeks

(additional time for Foreign Nationals). Once the DD Form 254 is approved,

the Senior Corporate Official will receive notification of approval and the

applicable requirement documents will be provided to the vendor point of

contact.

o The DD Form 254 must be approved for each vendor before CNSI is available

or otherwise provided or disclosed to any vendor.

o The Contractor shall store and safeguard classified material in accordance with

Executive Order 13526, Classified National Security Information, and its

Implementing Directive 32 CFR Part 2001 at the SECRET level in support of

program office requirements. Additionally, in accordance with the Department

of Defense (DOD) Manual 5220.22-M, “National Industrial Security Program

Operating Manual (NISPOM) for Safeguarding Classified Information,”

Chapter 5, Section 5-502, the contractor is authorized to disclose TSA classified

information to cleared subcontractors when access is necessary to perform tasks

or services for fulfillment of a prime or subcontract. In accordance with the

NISPOM, Chapter 5, Section 5-506, the contractor shall not disclose classified


of 16

information received or generated under this TSA contract to any other Federal

agency unless specifically authorized in writing by the TSA Program Office

that has classification management jurisdiction over the information and the

TSA Contracting Officers’ Representative (COR). In accordance with the

NISPOM, Chapter 5, Section 5-509, the contractor shall not disclose classified

information to another contractor except to support a contract, subcontract or

other TSA purpose.

o Any resultant contract award under Function Category Type II / Track 0 will be

subject to FAR Clause 52.204-2 to the extent the contract involves access to

information classified as “Secret”.

SECTION 3 – SUBMISSION ELEMENTS This Qualification Process consists of the following submissions:

Submission Limitations Due Date

SSI Vetting Request, Section

2.2

10 Employees only 30 days after window

opening

Decision Gate 1 - QVP

Package, Section 4.0

In accordance with the

QMP

October 2, 2019 at 3:00 PM

EST

Bailment Agreement for

Systems, Section 3.2

Bailment to be provided by

TSA CO

TBD

Decision Gate 2 - Submission

of one system to support

Certification Testing, Section

3.3

N/A TBD


of QDP, Section 6.0

In accordance with the

QMP

3 months after QVP Approval

and receipt of Certification

Approval.


of minimum of two systems to

support Government

Verification and Validation,

Section 7.0

N/A TBD

3.1. Upon receipt of an acceptable QVP, the TSA will provide a written notification of

the vendor’s ability to enter Certification Testing or a later stage of the Qualification

Process if the System Under Test (SUT) is approved with sufficient maturity and

substantiation.

3.2. The vendor shall enter into a no-cost bailment agreement with TSA that will address

the responsibilities and liabilities of the parties for the equipment while in the

custody of the TSA during the Qualification Process. The QPL CO will provide a

no-cost bailment agreement to the vendor for review and signature.


of 16

3.3. To support Certification Testing, the vendor shall be responsible for shipping one (1)

EDS to the TSL and upon approval from the QPL CO, ship one (1) identical EDS to

the TSIF at no cost to the Government to support Qualification Testing.

3.4. To support Field Testing and/or IOT&E, the vendor shall be responsible for

shipping two (2) identical EDS systems to airports as identified by TSA. These

systems can include the same systems submitted to the TSL/TSIF for Certification

and Qualification Testing.

3.5. In the event of performance issues during the Qualification Process, TSA recommends

vendors leave one (1) EDS system at the TSL and one (1) EDS system at the TSIF

during field testing and IOT&E at no cost to the Government. Although not required,

staging of these additional systems can reduce risk and decrease the time in the

Qualification Process.

3.6. The vendor shall be responsible for shipping, system installation, removal,

configuration management, offline EDS software installation, and training. Please

see the QMP for additional information.

3.7. The following are the anticipated time frames for Government action qualification

steps once SUTs are properly installed and operational. Results analysis and

reporting vary by the event and are not included in these time frames (please see

QPL Overview document for information on the steps and acronyms):

3.7.1. Step 4B TSL Certification Testing: Approximately 30 business days / 45

calendar days

3.7.2. Step 6A TSIF Qualification Testing: Approximately 40 business days / 60

calendar days

3.7.3. Step 6B Field Testing: Approximately 40 business days / 60 calendar days

3.7.4. Step 7 IOT&E: Approximately 30 business days / 45 calendar days

3.7.5. Step 8 Add Technology to QPL: Up to 150 business days / 225 calendar days

depending on level and thoroughness of review board and approval as required

by the TSA and DHS.

3.8. Once testing is complete, vendors shall coordinate shipping of the EDS systems out

of the TSL, TSIF, and any airports as directed by the TSA.

SECTION 4 – DECISION GATE 1: QVP SUBMISSION

4.1 Decision Gate 1 – QVP Submission Instructions

4.1.1. TSA hereby requests interested vendors to submit a QVP for application into the

Qualification Process.

4.1.2. The information submitted within the vendor’s QVP shall be in compliance with

the instructions provided within the QMP. Specifically, the instructions can be


of 16

found in Appendix A of the QMP. Appendix A of the QMP also sets forth the page

limits for the QVP.

4.1.3. Vendors shall submit two (2) hard copies and two (2) electronic copies (DVD or

CD-ROM format) of the QVP to the address below:

Melyssa Bertucci

701 South 12th Street, Floor 10

Arlington, VA 20598

Phone: 571-227-2521

4.1.4. In addition, vendors shall send an email to the QPL Contracting Officer (QPL CO)

and QPL Contract Specialist (QPL CS) addresses below with the following

information:

4.1.4.1. Notification to the QPL CO and QPL CS that the QVP was submitted by

providing the tracking number and confirmation of the date that the package

was shipped to both locations. All documents shipped seven days before the

due date will be considered on time. Should vendors choose to hand deliver the

packages, coordination must be made with the QPL CO or QPL CS first;

4.1.4.2. All required information per SECTION 4 of the EDS QPL Overview (complete

FAR 52.209-1, FAR 52.225-2, and FAR 52.225-6) and confirmation that the

vendor is registered in SAM;

4.1.4.3. All submitted documents must be properly marked for SSI, if there are

questions about properly shipping SSI, please contact the QPL CO and CS. No

Classified information shall be included in the RFQVP submissions.

QPL CO: Melyssa Bertucci QPL CS: Joseph Furtek

[email protected] [email protected]

4.1.5. This RFQVP does not commit the Government to pay any costs incurred in the

preparation of the QVP or to contract for supplies or services. System purchases

shall be initiated only by issuance of a fully executed contract issued by a

Contracting Officer.

4.2 Decision Gate 1 – QVP Submission Date

4.2.1. Functional Category Type II / Track 0 / Window 1 will be open through October

2, 2019 3:00 pm EST.

4.2.2. QVPs can be submitted at any time during an open Window period, but a complete

QVP package must be submitted no later than October 2, 2019 3:00 pm EST. It

is the vendor’s responsibility to verify receipt of the QVP with the QPL CO

and CS. Late submissions will not be considered.




of 16

4.3 Decision Gate 1 – Questions about RFQVP

4.3.1. If you have any questions about this RFQVP, please contact Melyssa Bertucci, the

QPL CO with a copy to Joseph Furtek, the QPL CS to the email addresses

provided above.

4.4 Decision Gate 1 - QVP Submission Evaluation

The primary objectives of the QVP evaluation are as follows:

4.4.1 Ensure the vendor has provided all substantiation required,

4.4.2 Verify the vendor’s test plans, procedures, schedule and system baseline that will

be tested to substantiate that the EDS is likely to meet the requirements, and

4.4.3 Verify the vendor has provided documentation intended to conduct EDS

assessments using a production or production-representative system configuration.

The system used to develop substantiation data shall be representative of production

systems and not specifically developed, selected, or tuned for qualification test

purposes.

The TSA will evaluate the QVP for sufficiency, accuracy, validity, and associated details in

accordance with the requirements documents and QMP.

The QVP shall be clear, well organized, and address every requirement as detailed in the

requirements documents identified in Section 2.0 and in the format required by the QMP. The

QVP shall include a full substantiation matrix by completing the Verification Requirements

Traceability Matrix, which can be found as an attachment to the FRD, and identify where in the

QVP the substantiation is documented.

After submission, vendors must coordinate with and gain approval from TSA or receive a specific

request by the TSA prior to making any changes to a submitted QVP. There is no limit on the

number of resubmissions but vendor initiated changes received after the decision gate closing

deadline will not be accepted. If the QVP fails to meet some or all TSA QVP requirements,

vendors will be notified of their final revision opportunity and will be allowed one (1) revision

window limited to 30 calendar days for vendor corrections. Corrections shall be submitted via

email to the QPL CO and CS by 3:00 PM EST by the thirtieth (30th) calendar day. Further revision

submission instructions will be provided via email by the QPL CO or CS if revisions are needed.

If the QVP fails to meet some or all TSA QVP requirements after the revision submission, the

vendor may be removed from the qualification process and will have to wait until the next Window

is opened to resubmit the QVP.

Submitted QVPs will be reviewed in the order they are received. In cases where multiple

verification packages are received concurrently, evaluation of the verification packages will be

conducted serially.


of 16

TSA anticipates that evaluation of a QVP submission may take up to four (4) weeks, depending

on the complexity of the QVP. Changes to the QVP submission may result in the suspension of

review activities until the update is received and may also restart the review process and timeline

from the beginning. TSA will provide QVP evaluation results in writing. Verbal discussions of

final evaluation results may be conducted if determined to be necessary.

Any vendor receiving an overall Decision Gate adjectival rating of ‘Fails to Meet’ following one

(1) revision opportunity for the QVP may be considered ineligible to move forward into

Certification Testing.

SECTION 5 – DECISION GATE 2: CERTIFICATION

TESTING The primary objectives of the Certification Testing are as follows:

5.1. Certification Testing will take place at the Transportation Security Lab under the

observance of the Department of Homeland Security’s Science and Technology

division and will follow the guidelines detailed in the QMP and Certification

Management Plan.

5.2. Vendors are required to meet or exceed all requirements within the Detection

Standards and Detection Functional Requirement Document (DFRD) annotated by

the use of a bold italic “shall”. TSA also plans to use the tested and documented

ability of a system to meet requirements to inform future best value competitions

for EDS.

5.3. At the completion of Certification Testing, TSA will provide the vendor formal

notification in writing and a tailored test results briefing. Verbal discussions of

evaluation results may also be conducted by the TSA with the vendor if deemed

necessary by the TSA.

5.4. Vendors will be provided one (1) initial Government-funded testing round and one

(1) Government-funded re-attempt following substantiation of EDS alterations to

meet detection requirements. An updated QVP may be required at the discretion of

the government following a failed certification attempt. If the system does not pass

Certification Testing in either of those attempts, it will be removed from the

Qualification Process and will have to wait until another Window is opened to

resubmit a QVP. If the systems successfully pass Certification Testing, the QPL

CO and CS will notify the vendor to proceed with the QDP submission process.


of 16

SECTION 6 – DECISION GATE 3: QDP SUBMISSION

6.1 Decision Gate 3 – QDP Submission Date

Vendors will be required to submit a QDP as defined in the QMP, no later than three (3) months

following QVP approval and receipt of Certification Letter. If the QDP fails to meet some or all

TSA QDP requirements, vendors will be allowed one (1) revision round to attempt to resolve

remediation as required by the TSA. Further revision submission instructions will be provided

via email by the QPL CO or CS if revisions are needed. If the QDP fails to meet some or all TSA

QDP requirements after one (1) formal revision submission, the vendor may be removed from

the process and will have to wait until the next Window is opened to resubmit at the beginning of

the Qualification Process.

6.2 Decision Gate 3 – QDP Submission Evaluation

The primary objectives of the QDP evaluation are as follows:

6.2.1. Ensure the vendor has provided all substantiation required,

6.2.2. Verify the vendor’s data updates all documentation provided in the QVP, properly

documents the system configuration and substantiates the EDS achievement to

meet requirements or potential to meet requirements.

6.2.3. Verify the vendor has gathered data while conducting EDS assessments using a

production or production-representative system configuration. The system used to

develop substantiation data shall be representative of production systems and not

specifically developed, selected, or tuned for qualification test purposes.

The TSA will evaluate QDP substantiation documentation for sufficiency, accuracy, validity, and

associated detail.

The QDP shall be clear, well organized, and address every requirement as detailed in the

requirements documents and in the format required by the QMP. The QDP shall include a full

substantiation matrix and identify where in the QDP the substantiation is documented.

After submission, vendors must coordinate with and gain approval from TSA or receive a

specific request by the TSA prior to making any changes to a submitted QDP. If the QDP fails to

meet some or all TSA QDP requirements, vendors will be allowed one (1) revision round to

attempt to resolve remediation as required by the TSA. Further revision submission instructions

will be provided via email by the QPL CO or CS if revisions are needed. If the QDP fails to meet

some or all TSA QDP requirements after one (1) formal revision submission, the vendor may be

removed from the process and will have to wait until the next Window is opened to resubmit at

the beginning of the Qualification Process.

Submitted QDPs will be reviewed in the order they are received. In cases where multiple data

packages are received concurrently, evaluation of the data packages shall be conducted serially.


of 16

TSA anticipates that evaluation of a QDP submission may take up to three (3) months, depending

on the complexity of the QDP. TSA will provide QDP evaluation results in writing. Verbal

discussions of evaluation results will be conducted if deemed necessary by the TSA.

Any vendor receiving an adjectival rating of ‘Fails to Meet’ for the QDP is considered ineligible

to move forward into the Qualification Process and may be removed. If the vendor receives a

rating of “Meets” for the QDP, the vendor will be eligible to proceed to the next Decision Gate of

the Qualification Process.

SECTION 7 – DECISION GATE 4: GOVERNMENT

VERIFICATION AND VALIDATION

The primary objectives of Government Verification and Validation (V&V) are as follows:

7.1. The Government V&V activities consist of qualification, field and operational

testing and will take place at the Transportation Security Integration Facility and

field sites under the observance of the TSA’s Test & Evaluation Division. Field

and operational testing will take place at one or two airport locations to be

determined by TSA.

7.2. Vendors are required to meet or exceed all requirements within the EBSP

requirements documents identified in Section 2.1 as annotated by the use of a bold

italic “shall.” Specifics on how Qualification Process is conducted is detailed in the

QMP. TSA also plans to use the tested and documented ability of a system to meet

requirements to inform future best value competitions for EDS.

7.3. At the completion of the Qualification Process, TSA will provide the vendor

formal notification in writing and a tailored test results briefing. Verbal discussions

of results may be conducted if deemed necessary.

Vendors will be provided one (1) initial attempt to pass the Qualification Process. If the system

does not pass the initial Qualification Process attempt, deficiencies will be noted in writing,

suspended from the Qualification Process and recommended for third party testing in accordance

with the QMP. The inability to successfully demonstrate resolution of deficiencies may result in

the vendor being removed from the qualification process and will have to wait until the next

Window is opened to resubmit their system starting at the beginning of the Qualification Process.

SECTION 8 – ADDITIONAL INFORMATION

8.1 Required Qualification Level

8.1.1. Systems being submitted under Functional Category Type II / Track 0 are

required to meet multiple levels of testing and receive a positive TSA Acquisition

Review Board decision and an additional DHS Acquisition Review Board as


of 16

needed and subsequently be added to the QPL. Therefore, all EDS systems that

are proposed to meet the identified requirements under Functional Category Type

II / Track 0 will be required to pass all levels of qualification through IOT&E in

accordance with the TSA Acquisition Qualification Policy v1.0 (12/14/2017).

Additional information on this can be found in the EDS QPL and the QMP.

8.1.2. It is TSA’s intent to complete Transportation Security Laboratory (TSL)

Certification Testing (CT), Transportation Security Integration Facility (TSIF)

Qualification Testing (QT), Field Testing, and IOT&E events in series, with one

event not beginning until the previous one is successfully completed.

8.2 Evaluation Results and Remediation

8.2.1. Vendors are required to meet or exceed all requirements within the requirements

documents identified in Section 2.1 annotated by the use of a bold italic “shall.” It

is anticipated the ability of a system to meet requirements will be used to inform

future best value competitions for EDS systems.

8.2.2. At the completion of each qualification step, TSA will provide the vendor formal

notification in writing and a tailored test results briefing. Verbal discussions of

results may be conducted if determined to be necessary.

8.2.3. Per TSA OSC Third Party Testing Strategy v1.0, the Government reserves the right

to suspend any vendor from any stage in the Qualification Process due to receiving

“Fails to Meet” ratings and require third party substantiation of vendor fixes if the

System Under Test (SUT):

Experiences at least one TSA defined significant failure during QT or OT

TSA determines the TSE has an unacceptable cluster of non-significant

failures during QT or OT

TSA determines the TSE has significant issues prior to testing that will

prevent passing QT or OT

8.2.4. If any vendor fails to substantiate QT or OT fixes within six (6) months under the

third party testing process, the Government reserves the right to remove the vendor

from the Qualification Process.


of 16

SECTION 9 – APPLICABLE FUNCTIONAL CATEGORY

TYPE II / TRACK 0 / WINDOW 1 CLAUSES

9.1 FAR Clause 52.204-2 Security Requirements (Aug 1996)

(a) This clause applies to the extent that this contract involves access to information

classified “Secret.”

(b) The Contractor shall comply with—

(1) The Security Agreement (DD Form 441), including the National Industrial Security

Program Operating Manual (DoD 5220.22-M); and

(2) Any revisions to that manual, notice of which has been furnished to the Contractor.

(c) If, subsequent to the date of this contract, the security classification or security

requirements under this contract are changed by the Government and if the changes

cause an increase or decrease in security costs or otherwise affect any other term or

condition of this contract, the contract shall be subject to an equitable adjustment as if

the changes were directed under the Changes clause of this contract.

(d) The Contractor agrees to insert terms that conform substantially to the language of

this clause, including this paragraph (d) but excluding any reference to the Changes

clause of this contract, in all subcontracts under this contract that involve access to

classified information.

(End of basic clause)

SECTION 10 – ATTACHMENTS

Attachment 1 DHS Non-Disclosure Form (DHS Form 11000-6)

Transportation Security Administration Government... · Transportation Security Administration...

Documents

Transcript of Transportation Security Administration Government... · Transportation Security Administration...