RFP-CATBPSS - 4.6.11.pdf

HSTS04-11-R-CT2042

Office of Acquisition

Credential Authentication Technology– Boarding Pass Scanner System (CAT/BPSS)

Request for Proposal

NSN 7540-01-152-8064 STANDARD FORM 33 (REV 9-97)

PREVIOUS EDITION NOT USABLE Prescribed by GSA

SOLICITATION, OFFER AND AWARD 1. THIS CONTRACT IS A RATED ORDER

UNDER DPAS (15 CFR 700)

RATING

DO-N4

PAGE OF PAGES

2 | 129

2. CONTRACT (Proc. Inst. Ident.)

NO.

3. SOLICITATION NO.

4. TYPE OF SOLICITATION

[ ] SEALED BID (IFB)

[x] NEGOTIATED (RFP)

5. DATE ISSUED

April 6, 2011

6. REQUISITION/PURCHASE NO.

2111201CT2042

7. ISSUED BY

TSA-Office of Security Technology/TSA-25

701 South 12th Street

Arlington, VA 20598

8. ADDRESS OFFER TO (If other than item 7)

NOTE: In sealed bid solicitation "offer" and "offeror” mean "bid" and "bidder".

SOLICITATION

9. Sealed offers in original and copies for furnishing the supplies or services in the Schedule will be received at the place specified, in the depository located in until local time See Section L. . (hour) (date)

CAUTION - LATE Submissions, Modifications, and Withdrawals: See Section L. Provision No. 52.215-1. All offers are subject to all terms and conditions contained in this solicitation.

10. FOR INFORMATION

CALL:

A. NAME

Holly Hamilton Bolger

B. TELEPHONE :

571-227-3036

C. E-MAIL ADDRESS

Holly.Bolger@dhs.gov

11. TABLE OF CONTENTS

(x) SEC. DESCRIPTION PAGE(S) (x) SEC. DESCRIPTION PAGE(S)

PART I - THE SCHEDULE PART II - CONTRACT CLAUSES

X A SOLICITATION/CONTRACT FORM 2 X I CONTRACT CLAUSES 72-88

X B SUPPLIES OR SERVICE AND PRICES/COSTS 3-8 PART III - LIST OF DOCUMENTS, EXHIBITS, AND OTHER ATTACH.

X C DESCRIPTION/SPECS/WORK STATEMENT 9-50 X J LIST OF ATTACHMENTS 89

X D PACKAGING AND MARKETING 51-52 PART IV - REPRESENTATIONS AND INSTRUCTIONS

X E INSPECTION AND ACCEPTANCE 53-55 X K REPRESENTATIONS, CERTIFICATIONS, AND 90-100

X F DELIVERIES OR PERFORMANCE 56 OTHER STATEMENTS OF OFFERORS

X G CONTRACT ADMINISTRATION 57-62 X L INSTRS., COND., AND NOTICES TO OFFERORS 101-123

X H SPECIAL CONTRACT REQUIREMENTS 63-71 X M EVALUATION FACTORS FOR AWARD 124-129

OFFER (Must be fully completed by offeror)

NOTE: ITEM 12 does not apply if the solicitation includes the provisions at 52.214-16, Minimum Bid Acceptance Period.

12. In compliance with the above, the undersigned agrees, if this offer is accepted within calendar days (120 calendar days unless a different period is inserted by the offer) from the date for receipt of offers specified above, to furnish any or all items upon which prices are offered at the price set opposite each item, delivered at the designated point(s), within the time specified in the schedule.

13. DISCOUNT FOR PROMPT PAYMENT SEE

14 (See section I, Clause No 52.232-8)

10 CALENDAR DAYS

20 CALENDAR DAYS

30 CALENDAR DAYS

CALENDAR DAYS

14. ACKNOWLEDGMENT OF AMENDMENTS AMENDMENT NO. DATE AMENDMENT NO. DATE

(The offeror acknowledges receipt of amendments to the solicitation and related documents ) numbered and dated:

15A. NAME CODE FACILITY 16. NAME AND TITLE OF PERSON AUTHORIZED

AND

ADDRESS

OF

OFFEROR

TO SIGN OFFER (Type or print)

15B. TELEPHONE NO. (Include area code)

15C. CHECK IF REMITTANCE ADDRESS [ ] IS

DIFFERENT FROM ABOVE - ENTER SUCH

ADDRESS

17. SIGNATURE 18. OFFER DATE

AWARD (To be completed by Government)

19. ACCEPTED AS TO ITEM NUMBERED

20. AMOUNT 21. ACCOUNTING AND APPROPRIATION

22. AUTHORITY FOR USING OTHER THAN FULL AND OPEN COMPETITION:

[ ] 10 U.S.C. 2304(c)( ) [ ] 41 U.S.C. 253(c)( )

23. SUBMIT INVOICES TO ADDRESS SHOWN IN

(4 copies unless otherwise specified)

ITEM

24. ADMINISTRATION BY (If other than Item 7) CODE 25. PAYMENT WILL BE MADE BY CODE

26. NAME OF CONTRACTING OFFICER (Type or print)

Lance Nyman

27. UNITED STATES OF AMERICA

(Signature of Contracting Officer)

28. AWARD DATE

IMPORTANT - Award will be made on this form, or on the Standard Form 26, or by other authorized official written notice.

SECTION B – SUPPLIES OR SERVICES AND PRICES/COSTS

B.1 Identification of Supplies/Services The contractor shall provide supplies and services necessary to design, manufacture, test and test support, and deliver the Credential Authentication Technology– Boarding Pass Scanner System hereinafter referred to as the ―CAT/BPSS‖ to sites throughout the United States and its territories as identified by the Government.

B.2 Type of Contract The Transportation Security Administration (―TSA‖ or ―Government‖) contemplates the award of a single Indefinite Delivery/Indefinite Quantity (IDIQ) contract with firm-fixed-price (FFP) and time and-materials (T&M) Contract Line Item Numbers (CLINs). The Government, in its sole discretion, will issue either firm-fixed-price (FFP), time-and-materials (T&M) or hybrid (i.e., FFP and T&M) Delivery Orders (DOs). The order type shall be determined at the time of order.

Except as stated in the Statement of Work (SOW), the contractor shall furnish all equipment, management, supervision, personnel, material, supplies and services necessary for performance of this contract.

*Note: the terms ―Delivery Order‖ or ―DO‖ and ―Task Order‖ or ―TO‖ may be used interchangeably throughout this contract.

B.3 Indefinite Quantity Contract- Minimum and Maximum Amount During the period of performance of this contract the Government may issue one (1) or more delivery orders. The Government is not obligated to order more than the stated minimum quantity of supplies or services under this contract. The contractor must furnish any additional quantities, not to exceed the stated maximum.

The minimum guaranteed quantity for this contract is one (1) CAT/BPSS First Article Test System unit (CLIN 0001).

The maximum amount for all orders established under this contract is $79,000,000.

B.4 Contract Line Item Numbers (CLINs)

B.4.1 Indefinite Delivery/Indefinite Quantity (IDIQ) CLINs

CLIN Title Type Unit Of

Issue Unit Price

0001 First Article Unit FFP EA TBD

Full Production Systems

B.4.2 Quantity Discount Pricing (applicable to CLINs 0002A and 0002B)

The respective prices for CLINs 0002A and 0002B depend upon the number of units to be provided under a given Delivery Orders. The same price applies to all units under a given delivery order and all units within the quantity tier. These prices are as follows:

0002A Full Production Systems with Batteries

FFP EA See B.4.2

0002B Full Production Systems without Batteries

FFP EA See B.4.2

0003 Technical Manual

0003A Operations Manual FFP EA TBD

0003B Installation/Integration Manual

FFP EA TBD

0003C Maintenance Manual FFP EA TBD

Technical Data Package

FFP EA TBD

0005 Training

0005A Operator Training FFP EA TBD

0005B Instructor Training Course

FFP EA TBD

0005C TSA Subject Matter Expert (SME) Training

FFP EA TBD

Engineering Support Services

FFP

or

T&M

EA/

NTE

TBD

0007 Excepted Maintenance

FFP

or

T&M

EA/

NTE

TBD

0008 Equipment Installation FFP EA TBD

0009 Travel and Shipping T&M NTE $600,000

Identification Database Update

FFP EA TBD

Corrective and Preventative Maintenance

FFP EA TBD

CLIN Title Type Unit of Issue

Delivery Order Qty

Unit Price

0002A Full Production Systems with Batteries

FFP EA 1-10 TBD

11-20 TBD

21-30 TBD

31-40 TBD

41-50 TBD

51-60 TBD

61-70 TBD

71-80 TBD

81-90 TBD

91 & up TBD

0002B Full Production Systems without Batteries

FFP EA 1-100 TBD

101-200 TBD

201-300 TBD

301-400 TBD

401-500 TBD

501-600 TBD

601-700 TBD

701-800 TBD

801-900 TBD

901 & up TBD

Apart from CLINs 0002A and 0002B, all CLIN prices offered will be the effective regardless of quantity ordered and will not be subject to quantity discounts unless proposed by the contractor.

B.4.3 RMA Disincentives (Applicable to CLIN 0011)

The Reliability, Maintainability and Availability (RMA) performance of CAT/BPSS systems is critical to TSA. Therefore, and in accordance with FAR 16.402-2, a negative performance incentive will be imposed to ensure that the Contractor meets the RMA requirements, TSA will adjust the final value of the Corrective and Preventive Maintenance CLIN (CLIN 0011) based on the information described in the table below. TSA will calculate the actual CAT/BPSS average RMA data for systems in operation, limited to those in a given delivery order, two years after said delivery order is placed.

The final adjusted CLIN value shall be effected via a contract modification executed unilaterally at the end of said two year period.

Performance Requirement

Threshold Performance

Standard

Disincentive for Failing to Meet Threshold

Mean Down Time (MDT) ≤12 hours

The following information shows the amount of money that will be withheld from CLIN 0011 if the vendor is not able to meet the threshold.

> 12 hours, up to 15 hours = 5% > 15 hours = 10%

Mean Time Between Critical Failure

(MTBCF) ≥600 hours

The following information shows the amount of money that will be withheld from CLIN 0011 if the vendor is not able to meet the objective.

< 600 hours, down to 450 hours = 5% < 450 hours = 10%

Operational Availability

(AO) ≥95%

The following information shows the amount of money that will be withheld from CLIN 0011 if the vendor is not able to meet the threshold.

< 95%, down to 92% = 5% < 92%, down to 89% = 10% < 89%, down to 86% = 15% < 86% = 20%

B.4.4 Firm Fixed Price/Time and Materials CLINs (Applicable to CLINs 0006, 0007 and 0009)

These CLINs may be issued on a Firm Fixed Price (FFP), Time & Materials (T&M) or hybrid (i.e., both FFP and T&M) basis on any given Delivery Order (DO) depending upon the best interests of the Government.

The ceiling for any T&M portion of this contract is not to exceed (NTE) $9,000,000.00. The contractor shall, when so ordered by the Government under these CLINs, provide the necessary management, labor, facilities, materials, services and supplies to perform tasks as stated in individual DOs, in accordance with the fixed, fully-burdened labor rates contained herein.

The contractor will be reimbursed for all allowable and allocable costs in accordance with contractor‘s disclosure statement. All labor rates are applicable at the date of order, not the date of performance.

The following labor categories and rates are applicable for the T&M CLINs.

Labor Category Labor Rate -

Year 1

Labor Rate -

Year 2

Labor Rate -

Year 3

Engineer II TBD TBD TBD

Engineer III TBD TBD TBD

Engineer IV TBD TBD TBD

Programmer II TBD TBD TBD

Programmer III TBD TBD TBD

Programmer IV TBD TBD TBD

Trainer III TBD TBD TBD

Trainer IV TBD TBD TBD

Computer Technician I TBD TBD TBD

Computer Technician II TBD TBD TBD

Computer Technician IV TBD TBD TBD

Quality Control Analyst II TBD TBD TBD

Information Assurance Consultant III TBD TBD TBD

Information Assurance Consultant IV TBD TBD TBD

Installation Support Specialist I TBD TBD TBD

Installation Support Specialist II TBD TBD TBD

Installation Support Specialist III TBD TBD TBD

B.4.5 Travel

Costs for transportation, lodging, meals, and incidental expenses incident to performance under CLINs 0002, 0005, 0006, 0007, 0008, 0010 and 0011 will be reimbursed in accordance with the version of the Federal Travel Regulations (FTR) current at date of order placement. In case of conflict with the below terms, the FTR shall take precedence.

The reimbursement for those costs shall be as follows:

Travel subsistence reimbursements will be authorized under the rates and conditions under the FTR.

Per diem will be reimbursed, at actual costs, not to exceed the per diem rates set forth in the

FTR.

Per diem shall be one-half of the Meals and Incidental Expenses (M&IE) rate applicable to the locations of temporary duty assignment when travel is more than 10 hours, but less than 24 hours, and when no lodging is required. If more than one temporary duty point is involved, the allowance of one-half of the M&IE rate is prescribed for the location where the majority of the time is spent performing official business. The per diem allowance shall not be allowed when the period of official travel is 10 hours or less during the same calendar day.

Airfare costs in excess of the lowest rate available offered during normal business hours are not reimbursable.

All reimbursable contractor travel shall be authorized through the issuance of a task order executed by the Contracting Officer.

Local Travel Costs will not be reimbursed under the following circumstances:

Travel at Government installations where Government transportation is available;

Travel performed for personal convenience/errands, including commuting to and from work;

and

Travel costs incurred in the replacement of personnel when such replacement is accomplished for the contractor‘s or employee‘s convenience.

The FTR can be found online, including at the following address:

http://www.gsa.gov/portal/ext/public/site/FTR/file/FTRTOC.html/category/21865/hostUri/port al

B.4.6 Shipping

The contractor shall be reimbursed for actual costs of shipping any systems ordered under CLIN 0001 CLIN 0002A, and 0002B. Said reimbursement shall not exceed the lowest rate available to commercial companies. Shipping includes all actions related delivering to the systems to their required destination.

B.4.7 Shipping and Travel Not Otherwise Provided

Except as provided in paragraphs B.4.5 and B. 4.6 above, all prices shall be inclusive of any shipping and travel necessary for their performance.

http://www.gsa.gov/portal/ext/public/site/FTR/file/FTRTOC.html/category/21865/hostUri/portal http://www.gsa.gov/portal/ext/public/site/FTR/file/FTRTOC.html/category/21865/hostUri/portal

SECTION C—STATEMENT OF WORK

1.0 SCOPE

This Statement of Work (SOW) defines the requirements for the design, manufacture, test and test support, and delivery of the Credential Authentication Technology – Boarding Pass Scanner System hereinafter referred to as the CAT/BPSS. The CAT/BPSS is intended to enable an operator to identify fraudulent identifications (ID) and boarding passes.

This SOW includes requirements for program management, systems engineering management, quality assurance, configuration management, test and evaluation, training, and Integrated Logistics Support

(ILS).

1.1 Background

In concert with its overall responsibilities to safeguard the flying public, Transportation Security Administration (TSA) requires all passengers to present a valid form of ID and an active boarding pass to a Transportation Security Officer (TSO) before entering the carry-on passenger screening area.

Given the hugely diverse population, the ever growing threats from radical groups, the increasing passenger volumes at our airports, and the relative ease in which some travel documents can be altered or forged, TSA has initiated the CAT/BPSS to support validation of IDs and boarding passes.

Most legitimate forms of ID issued today, including such IDs as passports and driver‘s licenses, have some form of encoded data that is written into the article by the issuing authority in one or more widely accepted formats. The most common formats include one- and two-dimensional barcodes, magnetic stripes, embedded circuits, and machine readable text. A newer format, Radio-Frequency Identification (RFID), is also growing in popularity due to its stealthy appearance and its inherent ability to wirelessly transmit data when placed in close proximity to a pulsed electro-magnetic field.

The ordinary boarding pass has also evolved over time to address security, primarily through data encoding, and to facilitate the actual boarding process. Along with a valid ID, this pass is regarded by TSA as a one-time entitlement for the passenger to proceed to the sterile screening area and then ultimately to the gate. Like the ID, boarding passes appear in a variety of physical formats although the encrypted data typically conforms to the International Air Transport Association (IATA) standards for a two-dimensional barcode. Their design and layout, however, are controlled by the issuing airline and they are produced at the ticket counter, at curbside check in, from self-serve kiosks, or by personal computers. A new generation of electronic pass has even evolved to provide an added convenience to those travelers using electronic devices, such as a Blackberry, cell phone, or Personal Digital Assistant (PDA).

The goal of CAT/BPSS is to deploy a computerized system that will read and analyze data and embedded security features on every passenger‘s ID and boarding pass, and to identify fraudulent IDs and boarding passes.

2.0 APPLICABLE DOCUMENTS

The following specifications, handbooks, orders, standards, and drawings form a part of this SOW and are applicable to the extent specified herein. The latest version of these documents as of the contract date shall apply, unless a specific date for the document is specified below.

2.1 Government Documents

Reference Document Location Section

5 United States Code (U.S.C.) 552

Public information;

agency rules opinions, orders, records and proceedings http://uscode.house.gov/uscode-cgi/fastweb.exe?search

3.0

29 Code of Federal Regulations (CFR) 1910.7

Definition and Requirements for a Nationally Recognized Testing Laboratory http://www.gpoaccess.gov/cfr/index.html 4.2

29 CFR 1910.1200 Hazard Communication Standard http://www.gpoaccess.gov/cfr/index.html 4.2

49 CFR Parts 15 and

Protection of Sensitive Security Information http://www.gpoaccess.gov/cfr/index.html 3.0, 3.13.2

DD Form 254 Contract Security Classification Specification http://www.dtic.mil/whs/directives /infomgt/forms/eforms/dd0254.pdf

3.13.1

DD FORM 1692,

AUG 96

Engineering Change Proposal

Available upon request 3.4.3

DD FORM 1694,

AUG 96

Request for Deviation/ Request for Waiver

Available upon request 3.4.3

Department of Homeland Security (DHS) Management Directive (MD) 11042.1

Safeguarding Sensitive But Unclassified (For Official Use Only) Information http://www.dhs.gov/xfoia/gc_1254501589035.shtm 3.13.2

DHS MD 11044 Protection of http://www.dhs.gov/xfoia/gc_1254501589035.shtm 3.13.2 http://www.dtic.mil/whs/directives

Classified National Security Information Classification Management

DHS/TSA/Office of Security Technology (OST)

/ENG/CAT/BPSS-

2.6

CAT/BPSS

Procurement Specification

Solicitation Document *contains SSI Available upon request

3.0, 3.2.1, 3.5.2, 3.5.2.2, 3.8.1.1 3.8.1.4.1, 4.4, 4.4.1, 4.4.2, 4.7

Federal Aviation Administration

(FAA)-D-2494/B

Appendix I, Commercial Instruction Books

Available upon request 3.6.1

OST-Configuration Management Plan

(CMP)-2600.3.1-1

Rev B

Transportation Security Administration Office of Security Technology Configuration Management Plan, 15 June

Available upon request 3.4.1, 3.4.1.1, 3.4.3, 3.4.3.1, 3.4.4, 3.4.5, 3.4.5.1.1, 3.4.5.1.2

Operational and Technical Training OTT Training Standards, Version 1, 28 Sept 2006

Available upon request 3.9

TSA

Configuration Management Requirements, 22 Oct 2008

Available upon request 3.4.1, 3.4.3, 3.4.3.1, 3.4.3.2, 3.4.3.3, 3.4.4, 3.4.5, 3.4.5.1.1, 3.4.5.1.2

TSA Failure Mode Identifier (FMI) Process Document

Available upon request 3.4.5

TSA ILS

Reliability, Maintainability, Availability (RMA) Metrics Terms and Definitions

Available upon request 4.3.1, 4.4

TSA Security Requirements Document

Available upon request 3.13.2

MIL-DTL-31000C Technical Data Packages Detail Specification

Can be ordered from the Department of Defense Single Stock Point (DODSSP), Building 4/Section D, 700 Robbins Avenue, Philadelphia, PA 19111- 5098. Information is available at their Website, http://dodssp.daps.dla.mil/.

3.6.2 http://dodssp.daps.dla.mil/

2.2 Military Specifications

Military Detail

(MIL-DTL)-

31000C

Detail Specification – Technical Data Packages, 9 July 2004

Can be ordered from the Department of Defense Single Stock Point (DODSSP), Building 4/Section D, 700 Robbins Avenue, Philadelphia, PA 19111-5098. Information is available at their Website, http://dodssp.daps.dla.mil/.

3.6.2

2.3 Other Documents

American Society for Testing and Materials

(ASTM)-D-3951

Standard Practice for Commercial Packaging

American Society for Quality, 600 North Plankinton Avenue, Milwaukee, WI 53203.

Phone: (800)248-1946.

Information is also available at their Website, http://www.asq.org.

2.4

2.4 Source of Documents

Requests for documents not readily available should fully identify material desired and cite the solicitation or Contract Number.

2.5 Order of Precedence

In the event of conflict between the text in this SOW and the references cited, the text of this SOW takes precedence. Nothing in this SOW, however, supersedes applicable laws and regulations unless there is a specific written exemption.

http://dodssp.daps.dla.mil/ http://www.asq.org/

3.0 REQUIREMENTS

The Contractor shall provide program management, systems engineering management, quality assurance, configuration management, test and evaluation, training, corrective and preventative maintenance, and integrated logistics support in accordance with this SOW. In addition, the Contractor shall provide any materials and support required to test, deliver, and install the CAT/BPSS in accordance with this SOW.

Data Items Descriptions (DID) referenced by their Contract Data Requirements List (CDRL) titles are to be developed in accordance with the CDRL of the same name. All data deliverables shall be prepared or updated and delivered in accordance with the corresponding CDRL items specified under the SOW requirement.

Any documents containing Sensitive Security Information (SSI) as defined in 49 CFR Parts 15 and 1520 shall contain the following statement:

WARNING: This record contains Sensitive Security Information that is controlled under 49 CFR Parts 15 and 1520. No part of this record may be disclosed to persons without a ―need to know‖, as defined in 49 CFR Parts 15 and 1520, except with the written permission of the Administrator of the Transportation Security Administration or the Secretary of Transportation. Unauthorized release may result in civil penalty or other action. For U.S.

Government agencies, public disclosure is governed by 5 U.S.C. 552 and 49 CFR Parts 15 and 1520.

The Contractor must request written government approval prior to release of any information, text, images, or video associated with this contract.

The Contractor shall perform in accordance with the plans developed in response to this SOW and as approved by the Government CO. The plans shall be updated as required and submitted for approval prior to implementation of any changes. All reference to the ―Government‖ in this SOW shall mean ―by authority of the CO or designee.‖ All digital media submitted to the Government in response to SOW requirements shall be compatible with the Microsoft Office suite of products. Acceptable digital media are Compact Disc – Read-Only Memory (CD-ROM) or Digital Versatile Disc (DVD).

Where specific sections are referenced in this SOW, it is intended to also include all subordinate sections.

3.1 Program Management (CLINs 0001, 0002A, and 0002B)

The Contractor shall implement Program Management activities in accordance with Section 3.1 of this SOW and shall include all organizational functions required for Program Management, including preparation and delivery of referenced CDRLs.

3.1.1 Program Management Organization

The Contractor shall establish and maintain a formal organization to manage the CAT/BPSS and ILS program Contracts and associated Subcontracts. The Contractor shall develop and implement a Management Program to efficiently and effectively execute the requirements of this Contract.

The Contractor‘s Program Manager is identified in Section G of this Contract. The Program Manager is responsible for accomplishment of all tasks required by this SOW and must be authorized to commit on behalf of the Contractor. The Program Manager shall organize, plan, schedule, implement, control, analyze, and report on all elements of the Contract. The Program Manager shall have resources and authority to ensure efficient and timely program execution and shall be the Contractor's focal point for all required program tasks. The Contractor's Program Manager shall be prepared at all times to present and discuss the status of Contract activities, ILS maintenance activities, requirements, and issues. The Program Manager shall notify the Contracting Officer‘s Technical Representative (COTR) of all performances cost, financial, personnel, and security problems that, if unresolved may adversely affect the Contractor‘s performance, schedule, or costs. The Contractor shall take appropriate measures to mitigate any adverse impact(s) to the Contract.

The Contractor shall prepare and deliver the Program Management Plan (PMP) in accordance with the referenced CDRL.

CDRL E001, Program Management Plan

3.1.2 Risk Management

The Contractor shall identify cost, maintenance cost, schedule, and technical risks, and describe how it will effectively manage these risks throughout the performance of this Contract. The Contractor shall describe its risk management program in the Risk Management Plan (RMP).

The Contractor shall quantify risks with respect to the impact on integration, installation, performance, technical parameters, schedule, and cost. The Contractor shall identify risks and assign a priority for developing a recommended course of action for resolution. The Contractor shall develop and maintain a list identifying, analyzing, and classifying program risks. Program and maintenance risks shall be classified as low, medium, or high priority. The Contractor shall conduct risk mitigation planning for risks considered medium or high priority. The Contractor shall provide the status of mitigation actions for identified program risks at Program Management Reviews (PMR) and in the Program Status Reports (PSR). The Contractor shall notify the Government of high risk items within 24 hours of identification.

The Contractor shall prepare and deliver the Risk Management Plan in accordance with the referenced

CDRL.

CDRL E002, Risk Management Plan

3.1.3 Meetings and Reviews

The Contractor shall conduct meetings and reviews in accordance with the Government-approved PMP and this SOW. The Contractor shall prepare and submit meeting agenda and presentation materials to the Government at least five (5) business days in advance. The Contractor shall be prepared to substantiate assumptions made and methodologies used in arriving at recommendations or conclusions. The Contractor shall record meeting minutes during all meetings. The Contractor shall prepare formal written minutes, accompanied by a summary of action items and all presentation materials used, for Government CO approval. Meetings and reviews shall not be considered finalized until the Government CO has approved the minutes.

Support provided by the Contractor shall include, but not be limited to, facilities, materials, office equipment, clerical personnel, mockups, technical data, and Subcontractor participation (when appropriate).

The Contractor shall prepare and deliver the Meeting Agenda and Meeting Minutes in accordance with the referenced CDRLs.

CDRL E003, Meeting Minutes CDRL E021, Meeting Agenda

3.1.3.1 Post-Award Conference

A post-award conference will be conducted at the Contractor‘s facility; TSA Headquarters, Arlington, Virginia; or an alternative site specified by the Government, within thirty (30) calendar days after contract award. The TSA will designate Government conference attendees and will identify any unique conference support requirements. The Contractor shall provide the minutes for the conference.

3.1.3.2 Program Management Reviews

The Contractor shall conduct and administratively support monthly PMRs at a Contractor site; TSA Headquarters, Arlington, Virginia; or an alternative site specified by the Government CO. Typically, PMRs will alternate between the Contractor site and TSA Headquarters. The Contractor's PMRs shall be targeted for no more than one (1) day in length. Attendance will generally be limited to 5–10 key Government personnel and 5–10 Contractor personnel. The Government reserves the right to replace a formal monthly review with a less formal update completed by teleconference, to change the location of the reviews at any time, and to increase or decrease the frequency of reviews as required.

The results of the PMR shall be documented as outlined in Section 3.1.3, Meetings and Reviews.

PMRs shall include, at a minimum, a review and status of the following topics:

Major accomplishments during reporting month;

Organizational status;

Work to be accomplished in the next month;

Delivery Order (DO) and Contract Line Item Number (CLIN) status;

CDRL status;

Corrective Action Report (CAR);

Program Trouble Report (PTR) status (See Section 3.1.4.1);

Cost, schedule, and performance (technical) aspects of the Contract;

Technical and implementation problems/issues;

Risk identification, assessment, impact, priority, mitigation plans and status;

Updated Verification Requirements Traceability Matrix;

Quality related issues, status, and initiatives;

Training related issues and status;

Engineering Change Proposals (ECP), Requests for Deviation (RFD), and Requests for

Waiver (RFW) status;

Subcontractor's technical progress on all assigned tasks;

RMA performance of fielded systems;

Status of previous PMR action items;

New PMR action items; and Determination of date for next PMR.

3.1.3.3 Technical Interchange Meetings

The Contractor shall conduct and administratively support periodic Technical Interchange Meetings (TIM) at least monthly at a Contractor site; TSA Headquarters, Arlington, Virginia; or an alternative site specified by the Government CO. During the TIMs, the Contractor and the Government will discuss specific technical activities, including technical activities associated with ILS, studies, design issues, technical decisions, test plans, test results, and implementation concerns to ensure continuing Government visibility into the technical progress of the Contract.

3.1.4 Program Control

A clear line of project authority shall exist among all organizational elements. The Contractor shall report on organizational status (i.e., changes, issues) during each PMR. The Contractor shall report on cost, maintenance cost, schedule, and technical progress in meeting reviews/status reports. Program Status Reports shall be provided monthly and shall address cost, maintenance cost, schedule, technical progress, and status of deliverables. The reports shall address problems/risks in the Contractor‘s functional areas (see Section 3.1.1).

The Contractor shall prepare and deliver the Program Status Report in accordance with the referenced

CDRL E004, Program Status Report

3.1.4.1 Program Trouble Report

The Contractor shall establish and maintain a Program Trouble Report (PTR). This report shall be a collection of data that documents problems relative to the design, production, and test of CAT/BPSS hardware and software. This report shall be used as a knowledge base to improve or fix the system.

This report shall be shared with TSA upon request. The Contractor's PTR system shall be described in the PMP.

3.1.4.2 Program Document Library

The Contractor shall maintain a digital Program Document Library (PDL) that contains all documents and data generated by the Contractor or provided to the Contractor by the Government during the performance of this Contract. The Contractor shall provide authorized Government personnel access to the PDL. The list of documents included in the PDL shall be listed in the Document Library Index (DLI). Documents and data provided by the Government in paper only formats are exempt from digital storage requirements.

The Contractor shall prepare and deliver the DLI in accordance with the referenced CDRL.

CDRL E005, Document Library Index

3.1.4.3 Data Accession List

The Data Accession List (DAL) shall list all internally generated documentation, not otherwise deliverable to the Government, used by the Contractor to develop, test, and manage the program.

The Contractor shall prepare and deliver the DAL in accordance with the referenced CDRL.

CDRL E006, Data Accession List

3.1.4.4 Security Equipment List

The Contractor shall establish and maintain a list of Security Equipment (SE). This list shall include the entire inventory (both in warranty and out of warranty) of fielded and warehoused SE. The list shall store the SE by model, part number, serial number, airport or warehoused location identifier, and airport terminal location (as applicable).

The list shall include all accumulating maintenance activity information and warranty information/actions. The list shall contain the failure history, associated maintenance actions, and the warranty information by TSE serial number.

The Contractor shall prepare and deliver the Security Equipment List in accordance with the referenced CDRL.

CDRL E009, SE List

3.2 System Engineering Management (CLINs 000, 0002A, and 0002B)

The Contractor shall develop and implement a System Engineering Management program for the definition, development, verification, integration, and testing of the CAT/BPSS requirements as allocated to both the computer Software Configuration Items (CSCI) and Hardware Configuration Items (HWCI). System engineering efforts shall include all aspects of performance, quality, life cycle costs, maintainability, reliability, schedule, data processing reserves, and future growth requirements.

The System Engineering Management program shall be described in the PMP. The description shall include both hardware and software engineering management with plans for acquiring, testing, and integrating the required hardware and software, including firmware, to meet Contract requirements.

The Contractor shall maintain effective control over the system engineering and design development process, including Subcontract items and services, to ensure cost, performance, and schedule requirements are met; to provide early detection and resolution of problems; and to reduce risk. The Contractor shall specify a primary point of contact for system engineering issues in the PMP.

3.2.1 Requirements Management

The Contractor shall document and manage all CAT/BPSS requirements specified in the Procurement Specification, Attachment J-2. The Contractor shall include requirements traceability in all design and test documents. Traceability shall be maintained for forward and backward reference. This information shall be updated as necessary throughout the life of the Contract and provided to the Government as part of the monthly PMR and the program status reporting requirement.

The Contractor shall prepare and deliver the Requirements Traceability Report in accordance with the referenced CDRL.

CDRL E007, Requirements Traceability Report

3.3 Quality Assurance (CLINs 0001, 0002A, and 0002B)

The Contractor shall establish, implement, and maintain a documented Quality Assurance Management system and shall prepare a Quality System Plan (QSP), as a means of ensuring compliance with all requirements of the Contract. The Contractor shall flow down all applicable requirements to sub-suppliers. The Contractor shall require that sub-suppliers have an appropriately documented quality system that controls the quality of the services and supplies provided.

The Contractor shall identify a single point of contact for all communication on quality-related issues.

The Contractor's quality representative shall be prepared at all times to present and discuss the status of quality activities, requirements, and issues. The Contractor shall provide quality status at the PMR.

The Contractor shall address quality related issues and status in the PSR.

The Contractor shall prepare and deliver a QSP in accordance with the referenced CDRL.

CDRL E008, Quality System Plan

3.4 Configuration Management Program

3.4.1 Configuration Management (CLINs 0001, 0002A, and 0002B)

The Contractor shall establish, implement, and maintain a CM Program based on the TSA Office of Security Technology Configuration Management Plan and the TSA Configuration Management Requirements. The CM program shall provide an organizational structure with configuration identification and control methods, configuration audits, and configuration status accounting procedures for hardware and software. The Contractor shall identify a single focal point, under the Program Manager, who will serve as the primary point of contact for all communication on CM-related issues. The CM requirements are applicable to all deliverables under this contract. The contractor shall provide support for configuration management activities, as required.

3.4.1.1 Configuration Management Plan (CMP)

The Contractor shall prepare and deliver a CMP in accordance with the referenced CDRL.

CDRL L001, Configuration Management Plan

3.4.1.1.1 Configuration Baselines

The Contractor shall establish and maintain the configuration baseline for the CAT/BPSS configuration and establish and maintain the required documentation to support this configuration, referred to as the Product Baseline (PBL). The CAT/BPSS PBL shall be established after successful completion of the associated Functional Configuration Audit (FCA)/Physical Configuration Audit (PCA). (See Section 3.4.5)

3.4.2 CAT/BPSS Configuration Identification (CLINs 0001, 0002A, and 0002B)

The Contractor's PBL shall retain all documentation for identification, control, and status accounting of any Configuration Item (CI) from initial acquisition to contract close-out.

The CIs are selected based on major components/critical items on a consensus basis by TSA and the Contractor.

The CI identification shall be available in a Master Configuration Item List (MCIL). All system CIs and top level hardware and software CIs shall be uniquely identified and map back to the configuration baseline developed with the offer and established during TSA testing; this is conducted as part of the CAT/BPSS testing and evaluation process.

The Contractor shall prepare and deliver the CAT/BPSS MCIL in accordance with the referenced

CDRL L002, Master Configuration Item Listing

3.4.3 Configuration Change Management (Configuration Control) (CLINs 0001, 0002A, and 0002B)

The Contractor shall apply configuration change management measures to each baseline CI and associated configuration documentation in accordance with the TSA Office of Security Technology Configuration Management Plan and the TSA Configuration Management Requirements. The Contractor‘s configuration change management system shall provide an effective means, as applicable, for proposing changes to CIs and ensuring implementation of the approved change. The Contractor shall maintain configuration change management of hardware, software, firmware, and developmental/commercial and training documentation from contract award to contract close-out.

The Contractor shall maintain configuration change management of hardware to the Lowest Replaceable Unit (LRU) level and software to the version level.

Changes represent opportunities for improvement or correction of deficiencies. Desired changes are documented in Requests for Change (RFC) in the form of ECPs, RFDs, and RFWs, which are uniquely identified. All change requests are entered, tracked, controlled, and documented.

ECPs are requests to incorporate a permanent change to product configuration, which produces a new baseline. RFDs are requests to temporarily incorporate a known departure from product requirements. Authorized deviations are a temporary departure from requirements and do not constitute a permanent change. RFDs must state actions to be taken at the end of the temporary deviation (e.g. restoration to original configuration). RFWs are requests to incorporate a known departure from product requirements. Authorized waivers are for specific quantities of product and do not constitute a change to the baseline configuration or its documentation.

The Contractor shall submit configuration control data submittals in an approved electronic format using the following forms:

ECP DD FORM1692, AUG 96 (EG), Pages 1–7, as applicable; and

RFD / RFW: DD FORM 1694, AUG 96 (EG).

3.4.3.1 Engineering Change Proposal (ECP)/Value Engineering Change Proposal (VECP)

The Contractor shall establish and maintain a system for tracking, controlling, and submitting ECPs in accordance with the TSA Office of Security Technology Configuration Management Plan and the TSA Configuration Management Requirements.

The Contractor is encouraged to voluntarily develop, prepare, and submit Value Engineering Change Proposals (VECP). The Contractor shall share in any net maintenance cost savings realized from accepted VECPs, in accordance with the incentive sharing rates in paragraph (f) of FAR clause 52.248-1. The VECP shall include a clear description and related schedule on how the Contractor plans on incorporating the VECP into fielded CAT/BPSS units without adversely affecting operational availability of the CAT/BPSS.

The Contractor shall prepare and deliver the ECP/VECP in accordance with the referenced CDRL.

CDRL L004, Engineering Change Proposal

3.4.3.2 Request for Deviation (RFD)

The Contractor shall establish and maintain a system for tracking, controlling, and submitting RFDs in accordance with TSA Configuration Management Requirements.

The Contractor shall prepare and deliver the RFD in accordance with the referenced CDRL.

CDRL L005, Request for Deviation

3.4.3.3 Request for Waiver (RFW)

The Contractor shall establish and maintain a system for tracking, controlling, and submitting RFWs in accordance with TSA Configuration Management Requirements.

The Contractor shall prepare and deliver the RFW in accordance with the referenced CDRL.

CDRL L006, Request for Waiver

3.4.4 Configuration Status Accounting (CLINs 0001, 0002A, and 0002B)

The Contractor shall maintain a Configuration Status Accounting (CSA) Information System to assure accurate identification of each CI. The Contractor shall ensure that the CSA information is provided to the Government upon request. The CSA information shall be provided as a monthly Configuration Status Accounting Report (CSAR). The Contractor shall refer to the TSA Office of Security Technology Configuration Management Plan and the TSA Configuration Management Requirements for guidance in establishing the CSA Information System. The CSAR shall identify all deviations from the MCIL for each unit, i.e. for all serial numbers.

The Contractor shall prepare and deliver the CSAR in accordance with the referenced CDRL.

CDRL L007, Configuration Status Accounting Report

3.4.5 Configuration Audits (CLINs 0001, 0002A, and 0002B)

The Contractor shall support PBL audits and perform internal contractor configuration audits in accordance with TSA Configuration Management Requirements.

The Contractor shall prepare and submit a Configuration Audit Plan (CAP) that describes procedures for conducting the audit, including FCA and PCA.

When proposed and approved in the CAP, the Contractor may invite Subcontractors, vendors, and suppliers to participate in the configuration audits, as proposed and approved via the CAP. The Contractor shall prepare and submit a Configuration Audit Summary Report (CASR) documenting the results of each audit and the resolution for each finding. The Contractor shall support Government configuration audits in accordance with the TSA Office of Security Technology Configuration Management Plan and the TSA Configuration Management Requirements.

3.4.5.1 CAT/BPSS Configuration Audits

The Contractor shall prepare and deliver the CAT/BPSS CAP and the CASR in accordance with the

CDRL L008, Configuration Audit Plan CDRL L009, Configuration Audit Summary Report

3.4.5.1.1 CAT/BPSS Functional Configuration Audit

The Contractor shall support Government conducted FCA on the CAT/BPSS system in accordance with the TSA Office of Security Technology Configuration Management Plan and the TSA Configuration Management Requirements. The FCA shall be conducted once, after successful completion of the First Article Test and Evaluation (FAT&E). The FCA shall verify system functional performance requirements. Upon successful completion of the FCA, a PCA will be performed.

3.4.5.1.2 CAT/BPSS Physical Configuration Audit

The Contractor shall support Government conducted PCA on the CAT/BPSS system in accordance with the TSA Office of Security Technology Configuration Management Plan and the TSA Configuration Management Requirements. The PCA shall be conducted after successful completion of the First Article Test (FAT). The PCA shall verify system physical performance requirements. Successful completion of the PCA shall include, but not be limited to, successful conclusion of FCA and Government CO approval of the Contractor‘s final submission of the associated CDRL items.

3.5 Major System Components

3.5.1 First Article Unit (CLIN 0001)

The Contractor shall provide the First Article CAT/BPSS System in accordance with this SOW and the requirements specified in the CAT/BPSS Procurement Specification, Attachment J-2.

The First Article system shall be housed at the Contractor‘s facility until such time as the Government specifies delivery to a site. These units shall be maintained under strict configuration management in accordance with Section 3.4, which will then be referred to as the ―Gold Standard‖ for the entire inventory. All system CIs and top level hardware and software CIs shall be uniquely identified and map back to the configuration baseline developed with the offer and established during TSA testing;

this is conducted as part of the CAT/BPSS testing and evaluation process. The Contractor shall not alter this unit in any way without the express approval of the Government CO.

The FAT&E unit shall receive a Site Acceptance Tests (SAT) in Section 3.8.1.4.3)

3.5.2 Full Production Systems (CLIN 0002A and 0002B)

The Contractor shall provide CAT/BPSS Systems in accordance with this SOW and the requirements specified in the CAT/BPSS Procurement Specification, Attachment J-2.

The Full Production Units shall each receive Factory Acceptance Tests (FAT) Section 3.8.1.4.2) and Site Acceptance Tests (SAT) in Section 3.8.1.4.3)

The FAT&E unit shall have the same configuration as the Full Production System with Batteries.

3.5.2.1 Full Production Systems with Batteries (CLIN 0002A)

This systems shall meet all requirements in CAT/BPSS Procurement Specification, Attachment J-2.

3.5.2.2 Full Production Systems without Batteries (CLIN 0002B)

These systems shall meet all requirements in CAT/BPSS Procurement Specification, Attachment J-2, and only include A/C power sources, but no batter(ies). Battery-related sections in CAT/BPSS Procurement Specification Section 3.3: Electrical and CAT/BPSS Procurement Specification Section 3.12: Battery Charging Station do not apply to units from this CLIN

3.5.3 Identification Database Update (CLIN 0010)

The Contractor shall update the Identification database either every quarter or as identification issuers update the supported documents listed in Section 3.1.1 of the CAT/BPSS Performance Specification. The update shall include new forms of identification, such as for airport and airline employees, when they become available in connection with an engineering change proposal (ECP).

The Contractor shall ensure that the CAT/BPSS can recognize various versions of valid travel documents as listed 3.1.1 of the CAT/BPSS Performance Specification. For example, drivers‘ licenses from versions that are up to one year expired, to any recent updates.

3.6 Documentation

3.6.1 Technical Manuals (CLIN 0003)

The Contractor shall use FAA-D-2494/B Appendix I, Commercial Instruction Books, as a guide in developing the below listed manuals, including any supplemental data required to augment any commercial manuals. The Contractor shall ensure and certify that all technical manuals are current, accurate, and complete before submitting to the Government for validation and acceptance. The Contractor shall plan, coordinate, conduct and document a formal verification and validation of each of the below listed manuals.

3.6.1.1 Operations Manual (CLIN 0003A)

The Contractor shall provide an Operations Manual that describes all functions for the operation of the CAT/BPSS. The Operations Manual shall include detailed instructions on how to execute each function. The Operations Manual shall include any troubleshooting guidance necessary or appropriate to resolve those errors not requiring corrective maintenance by qualified technicians.

The Contractor shall provide an Operations Manual in accordance with the referenced CDRL.

CDRL D003, Operations Manual (CLIN 0003A)

3.6.1.2 Installation/Integration Manual (CLIN 0003B)

The Contractor shall provide an Installation/Integration Manual that describes the necessary instructions/requirements for the installation, and setup, of the CAT/BPSS system to a state ready for commencement of operations according to the specs. The Installation/Integration Manual shall include any special instructions/requirements such as orientation, environmental conditions, power connectivity, maintenance access, that would impact installation, operational, and/or maintenance capabilities.

The Contractor shall provide an Installation/Integration Manual in accordance with the referenced

CDRL D004, Installation/Integration Manual (CLIN 0003B)

3.6.1.3 Maintenance Manual (CLIN 0003C)

The Contractor shall provide a Maintenance Manual to sufficiently detailed to allow on-site scheduled (preventive) and unscheduled (corrective) maintenance performed by maintenance technicians and any maintenance to be performed by users. The Maintenance Manual shall indicate the type and frequency of preventive maintenance actions, including instructions on how to perform each action.

The Maintenance Manual shall contain instructions on performing corrective maintenance, including diagnostics and repair actions.

The Contractor shall provide a Maintenance Manual in accordance with the referenced CDRL.

CDRL L011, Maintenance Manual (CLIN 0003C)

3.6.2 Technical Data Package (CLIN 0004)

The Contractor shall provide a Type 2D Technical Data Package (TDP) in accordance with the requirements established in Detail Specification MIL-DTL-31000C, Technical Data Packages for commercial drawings.

The TDP shall provide engineering and technical information on all assemblies and subassemblies identified as LRUs in the associated maintenance documentation (CDRLS and DIDs), as required to support preventive and corrective maintenance actions and associated provisioning.