70T04020R9NAP6617 A00001 091720.pdf

(x)

70T04020R9NAP6617

x x

1 copies of the amendment; (b) By acknowledging receipt of this amendment on each copy of the offer submitted ; or (c) By separate letter or telegram which includes a reference to the solicitation and amendment numbers. FAILURE OF YOUR ACKNOWLEDGEMENT TO BE RECEIVED AT

THE PLACE DESIGNATED FOR THE RECEIPT OF OFFERS PRIOR TO THE HOUR AND DATE SPECIFIED MAY RESULT IN REJECTION OF YOUR OFFER. If by virtue of this amendment you desire to change an offer already submitted , such change may be made by telegram or letter, provided each telegram or letter makes reference to the solicitation and this amendment, and is received prior to the opening hour and date specified.

x

Arlington VA 20598

701 S 12TH STREET

CONTRACTING AND PROCUREMENT

09/17/2020

13. THIS ITEM ONLY APPLIES TO MODIFICATION OF CONTRACTS/ORDERS. IT MODIFIES THE CONTRACT/ORDER NO. AS DESCRIBED IN ITEM 14.

12. ACCOUNTING AND APPROPRIATION DATA (If required) is not extended.is extended, Items 8 and 15, and returning

Offers must acknowledge receipt of this amendment prior to the hour and date specified in the solicitation or as amended , by one of the following methods: (a) By completing

The above numbered solicitation is amended as set forth in Item 14. The hour and date specified for receipt of Offers

11. THIS ITEM ONLY APPLIES TO AMENDMENTS OF SOLICITATIONS

FACILITY CODE CODE

10B. DATED (SEE ITEM 13)

10A. MODIFICATION OF CONTRACT/ORDER NO.

9B. DATED (SEE ITEM 11)

9A. AMENDMENT OF SOLICITATION NO.

CODE

8. NAME AND ADDRESS OF CONTRACTOR (No., street, county, State and ZIP Code)

7. ADMINISTERED BY (If other than Item 6)CODE 6. ISSUED BY

PAGE OF PAGES

4. REQUISITION/PURCHASE REQ. NO.3. EFFECTIVE DATE2. AMENDMENT/MODIFICATION NO. 5. PROJECT NO. (If applicable)

1. CONTRACT ID CODE

AMENDMENT OF SOLICITATION/MODIFICATION OF CONTRACT

09/17/2020

CHECK ONE A. THIS CHANGE ORDER IS ISSUED PURSUANT TO: (Specify authority) THE CHANGES SET FORTH IN ITEM 14 ARE MADE IN THE CONTRACT

B. THE ABOVE NUMBERED CONTRACT/ORDER IS MODIFIED TO REFLECT THE ADMINISTRATIVE CHANGES (such as changes in paying office, C. THIS SUPPLEMENTAL AGREEMENT IS ENTERED INTO PURSUANT TO AUTHORITY OF:

D. OTHER (Specify type of modification and authority) appropriation date, etc.) SET FORTH IN ITEM 14, PURSUANT TO THE AUTHORITY OF FAR 43.103(b).

E. IMPORTANT: Contractor is not, is required to sign this document and return __________________ copies to the issuing office.

ORDER NO. IN ITEM 10A.

14. DESCRIPTION OF AMENDMENT/MODIFICATION (Organized by UCF section headings, including solicitation/contract subject matter where feasible.)

This Request for Proposal 70T04020R9NAP6617 is hereby amended to revise the Statement of

Work, Technical Requirements, B. Scheduling as follows:

Delete: All work, including final acceptance must take place no later than four (4) months after award. Refer to the deliverables table for specifics.

Insert: All work, including final acceptance must take place no later than thirty (30) days after notice of completion. Refer to the deliverables table for specifics.

16A. NAME AND TITLE OF CONTRACTING OFFICER (Type or print)15A. NAME AND TITLE OF SIGNER (Type or print)

15C. DATE SIGNED 16B. UNITED STATES OF AMERICA 15B. CONTRACTOR/OFFEROR 16C. DATE SIGNED

(Signature of person authorized to sign) (Signature of Contracting Officer)

Jaylin Wilson

STANDARD FORM 30 (REV. 10-83)

Prescribed by GSA

FAR (48 CFR) 53.243

NSN 7540-01-152-8070

Previous edition unusable

Except as provided herein, all terms and conditions of the document referenced in Item 9 A or 10A, as heretofore changed, remains unchanged and in full force and effect .

A00001

X 1

09/17/2020 /s/

70T04020R9NAP6617 – TSIF CBIS Upgrade RFP Page 3 of 78

Transportation Security Administration Systems Integration Facility

(TSIF) Checked Baggage Inspection System (CBIS) Upgrade

Request for Proposal 70T04020R9NAP6617/A00001 (all changes are in red text)

Table of Contents Section Description I Pricing Schedule II Statement of Work

III

Contract Terms and Conditions A. TSA Special Contract Requirements B. Information Technology Clauses C. FAR and HSAR Clauses D. FAR Provisions

IV Proposal Submission and Evaluation

70T04020R9NAP6617 – TSIF CBIS Upgrade RFP Page 4 of 78

SECTION I – PRICING SCHEDULE

A. Description of Supplies

The contractor shall provide all necessary supplies and support as required in accordance with the terms and conditions of this RFP and described in the Statement of Work (SOW).

B. Contract Line Item Number (CLIN) Structure The prices shall be inclusive of all costs necessary to implement and fulfill the item numbers and accompanying item descriptions shown in the Price Schedule below.

CLIN Description CLIN Type

Unit of Issue QTY Unit Price Total Price

0001 TSIF CBIS Upgrades FFP MO 10 $ $

Other Direct Costs – Materials & Warranty (Not to Exceed)

COST LOT $

0003 Travel (Not to Exceed) COST LOT $54,880.00 Total Price $

*CLIN 0003 Travel is a Government provided not-to-exceed amount and will not be evaluated. The values shall be included in the contractor’s pricing submission.

C. General Information

1. For this procurement, the standard industrial classification (NAICS) code is 541330 (Engineering Services).

2. All contract terms and conditions of the prime contract shall flow down through all subcontracts, and any subcontracting or teaming agreement shall comply with all clauses listed in Sections IV and V, pertaining to subcontracting.

3. The Transportation Security Administration (TSA) is exempt of sales tax and does not have to file a tax exemption form, since the state of Virginia does not require any form or filling to achieve tax exempt status. TSA FEIN #: 80-0038533

4. The Period of Performance shall be ten (10) months from the date of award.

70T04020R9NAP6617 – TSIF CBIS Upgrade RFP Page 5 of 78

SECTION II – STATEMENT OF WORK

BACKGROUND AND OBJECTIVE

Testing and Evaluation (T&E) supports TSA’s Acquisition Program Management (APM) mission by testing and qualifying equipment with necessary security capabilities for deployment to the field.

The Transportation Security Administration Systems Integration Facility (TSIF) is a facility where TSA conducts testing to evaluate the effectiveness, security, and efficiency of security systems to drive the standards for security.

The TSIF Checked Baggage Inspection System (CBIS) is often viewed as a showcase to the nation’s airports, which is capable of demonstrating the latest concepts, principles and advances in CBIS methodology and technology. Originally constructed in 2007, it predates the first release of the Planning Guidelines and Design Standards (PGDS).

The current version of the PGDS is version 6.0, and soon to be version 7.0. The PGDS has continually incorporated the progressing knowledge of Baggage Handling System (BHS) design since the first version was published over ten years ago. The improvements in baggage tracking algorithms, system reports and operating concepts are implemented in any new baggage system, as required by the PGDS.

The objective of this requirement is to allow for the automatic transfer of baggage from the CBIS to the Cargo area. This will alleviate the requirement to manually transport baggage throughout the TSIF when testing alternative technologies for checked baggage such as Mobile Inspection Tables and modified Checked Baggage Resolution Area (CBRA) processes as well as temporary Explosive Detection System (EDS) installation for testing.

SCOPE

The contractor shall provide a complete turnkey solution to provide management and engineering services to modify the existing CBIS conveyors and to install equipment (e.g., conveyors and vertical lifts) to facilitate transporting baggage to/from the TSIF CBIS to/from the TSIF Cargo Area. All work shall be in accordance with the industry and most recent PGDS version best practices. The contractor shall:

• Provide program management and personnel for the entire scope of the project.

• Possess relevant experience performing/executing work in a 9001; 2015 Compliant facility.

• Possess experience and vast knowledge with PGDS 6.0 or later standards to include design work, installation, commissioning and testing.

• Perform demolition/decimation of exiting conveyors.

• Perform installation of conveyors, quoting, infeed’s and discharge from/to the CBIS to the vertical lift, power turns and panels as required.

• Install catwalks.

• Modify/update all existing Human Machine Interface (HMI) Screens to incorporate all newly installed or modified conveyors and devices.

• Install new Programmable Logic Controller (PLC) and associated devices to accommodate the new system.

70T04020R9NAP6617 – TSIF CBIS Upgrade RFP Page 6 of 78

• Install a new remote HMI adjacent to lift VLU-02 in the Cargo area.

• Modify the upper level system reports to accommodate reporting of all new devices, tracking, and statuses.

• Ensure that test plans and the installation sequence are published and approved by the

Owner during design review meetings prior to beginning installation.

• Provide all mechanical, structural, electrical, and network drawings as applicable.

• Supply labor to “handle” bags as required to support loading and unloading of bags into the BHS for testing.

TECHNICAL REQUIREMENTS

A. Materials

The contractor shall provide a detailed Bill of Materials (BOM) for TSA approval prior to procurement of all materials.

B. Scheduling

All work, including final acceptance must take place no later than thirty (30) days after notice of completion. Refer to the deliverables table for specifics.

C. Description of Requirement

The contractor shall provide all labor, tools, and material to upgrade the TSIF CBIS to allow for the automatic transfer of baggage from the CBIS to and from the Cargo area in accordance with the requirements as outlined in the SOW, including but not limited to the following:

C1. Modifying existing CBIS conveyors to install equipment and conveyors to facilitate transporting of baggage from the CBIS to the Checkpoint (C2C) equipment testing area (Cargo Area). All manpower, tools, and hardware required for the installation and integration of the C2C transfer line will be supplied by the Contractor.

70T04020R9NAP6617 – TSIF CBIS Upgrade RFP Page 7 of 78

*Figure 1: CBIS/Cargo Transfer Line Overview

This shall be accomplished by the following:

• Modifying conveyors at ETDCL-02 and 03 and installing a VLU-01 and associated feed conveyor (see Figure 2 and 3 for reference) for transferring baggage to the Cargo area.

• Updating the Sortation Allocation Computer (SAC) to allow for specific bags to bypass all CBRA workstations and be sorted to the new Cargo area.

• Updating the reporting system to reflect device statues and sortation statistics.

• Installation of a second VLU-02 in the Cargo area. Installation of a pair stacked conveyor (2) for moving baggage between the Cargo area to CBIS and from CBIS to the Cargo area.

• Installation of a double stacked in and out [elevator lift? Some other device?] (at the bottom of the lift) in the cargo lift. (See figure 2 below).

• Installation of new ControlLogix PLC and communications modules into the existing PLC5 rack located in the CBIS control room (Firmware v32).

• Demolition of 20 feet of existing conveyor at EDTCL-02 and ETDCL-03.

• Installation of VLU-01 at ETDCL-02 and -03 and VLU-02 in the Cargo area.

o Note: Nerak vertical lift units shall be used for the design purposes. Alternatives may be provided if the units have been commissioned at any given US Cat-X airport for five or more years. (References must be supplied and alternatives must be approved by TSA).

• Modifying ETDCL-02 and -03.

• Installation of approximately 200 feet (double stacked 100 feet each) of tracked Conveyor from the VL1 (C1C) line to the VL2 (C2C) line in the Cargo area.

• Installation of two (2) five (5) foot queues at the infeed of the transfer line on VL1 and VL2.

• Installation of two (2) five (5) to ten (10) foot conveyor sections on the infeed and discharge of the VL2 lift for loading and unloading cargo.

• Installation of four (4) power turns.

• Installation of 120 feet of catwalk with ladders at each end from the CBIS to the Cargo area

(smaller platforms and ladders may be an option).

• Installation of one (1) Power Distribution Panel (PDP) with Inputs/Outputs (I/O) for new

70T04020R9NAP6617 – TSIF CBIS Upgrade RFP Page 8 of 78

CBIS to Cargo 1 (C1C) and CBIS to Cargo 2 (C2C0 from the CBIS to the cargo conveyors and back.

• Installation of one (1) stanchion mounted remote HMI touch screen in the Cargo area.

*Figure 2: Double stacked conveyors on cargo lift

C2. BHS Controls: The contractor shall ensure all devices are connected via IO Link (IEC 61131-9) standards. Refer to figure 3 for an example of the system architecture.

70T04020R9NAP6617 – TSIF CBIS Upgrade RFP Page 9 of 78

*Figure 3: BHS controls system architecture

The contractor shall:

• Modify/update all existing HMI Screens to incorporate all newly installed or modified conveyors and devices.

• Install a new remote HMI adjacent to lift VLU-02 in the Cargo area.

• Modify the upper level system reports to accommodate reporting of all new devices, tracking, and statuses.

• Ensure that test plans and installation sequences are published and approved by the Owner during design review meetings prior to beginning installation.

• Ensure that all BHS reprogramming and all modifications necessary for the successful integration of the new system with the existing system are completed. The contractor will provide a comprehensive report detailing any deficiencies, if any, in the existing system, be it mechanical or electrical hardware, prior to conducting any onsite work.

• Remove any unused or excess wiring and hardware after commissioning and acceptance.

• Ensure that in Final Code Deliverables:

a) New PLC code and database additions match the existing format and data structures as installed at TSIF to ensure consistency.

b) Unused inputs, outputs, coils, rungs, labels, variable names, and subroutines from the PLC program are deleted and only the elements that are applicable to the work are included.

c) Delivered As-Built PLC Source Code include code capable of being read and loaded onto all the PLCs used in the project. As an example: the file type for Allen-Bradley ControlLogix processors is *.acd.

*Note: All software and source code developed or reused beyond PLC coding for this effort will also be 100% transferred to the TSA and in no way be protected from modifications.

C3. General Requirements

• All manpower, tools and hardware required for the installation and integration of the Cargo 2CBIS (C2C) line will be supplied by the Contractor.

• The contractor shall supply labor to ‘handle” bags as required to support loading and unloading of bags into the BHS for testing.

• All work will be performed in accordance with the original BHS specifications provided for the Baggage Area Screening System, (BASS), TSA Contract Number: HSTS04-08-C- CT8021VTC Project Number: DB6TSA08205, Revision G, Dated June 25, 2008. The items below are project specific to the CBIS to Cargo transfer line and outside of the original specification package.

• All conveyors shall be 39” inches wide.

• All conveyors shall have 12” inch side guards.

• All drives shall be equipped with VFDs and fed from the PDP.

a) Location to be determined by TSA.

b) The PDP shall be fed from the power feeds under the Cargo area.

• All drive units and other components shall be installed on the catwalk site for maintenance access.

70T04020R9NAP6617 – TSIF CBIS Upgrade RFP Page 10 of 78

• A single, non-redundant PLC matching the existing controls infrastructure shall be utilized.

a) The new PLC shall be installed in the existing PLC cabinet in the BHS control room (a rack is installed and provided by TSA).

• All reports shall be incorporated into the existing database and reporting infrastructure.

• All graphics shall report to the existing HMI.

• All control infrastructure and programming shall match the existing architecture and environment.

• All devices, drives, encoders, control stations, etc., shall utilize IO Link via Ethernet/IP.

• Stack-lights shall be located at each vertical lift.

C.4 Acceptance Testing

Commissioning (testing) requirements shall be evaluated through a top-level suite of CBIS tests listed in Appendix D of the PGDS. All testing and approvals shall be in conjunction with the ATSA engineering Test Team.

DELIVERABLES

Deliverable Description Due Date and

Frequency Approval

Project Plan and Schedule

Provide a project plan and schedule for all milestones, deliverables and task of the project.

20 days after Notice to Proceed (NTP)

Contracting Officer’s Representative (COR)/Technical Monitor (TM)

System Specifications

Provide the system performance specifications, inclusive of upper and lower level modifications.

30 days after NTP COR/TM with SME concurrence

System Layout Drawings

Provide the system plan view drawings to scale in accordance to TSIF blueprints.

20 days after NTP l COR/TM with SME concurrence

System Installation Phasing Plan

Describe all the phases of the installation in the phasing plan.

20 days after NTP COR/TM with SME concurrence

Mechanical Provide all mechanical /engineering drawings for the system.

14 days prior to initial CBIS install

COR/TM with SME concurrence

Electrical Provide all electrical/ engineering drawings for the system to the facility connection point.

14 days prior to initial CBIS install

COR/TM with SME concurrence

Recommended Spare Parts

Provide a list of all recommended spare parts

10 days prior to initial CBIS install

COR/TM with SME concurrence

70T04020R9NAP6617 – TSIF CBIS Upgrade RFP Page 11 of 78 and provide a timeline on when those spare parts are needed for continuous operation for up to 5 years

Description of Operations

Provide a document describing the concept of operations of the system.

20 days after NTP COR/TM with SME concurrence

System Reports & Format

Provide system format for approval, and system reports to prove that the reports are based on the format.

As needed COR/TM with SME concurrence

Training Plan & approach

Provide a training plan and training approach for the TSIF C2C transfer line.

10 days prior to system training

COR/TM with SME concurrence

Draft O&M Manual Provide a draft Operational & Maintenance manual for the system.

10 days prior to system training

COR/TM with SME concurrence

Final Spare Parts List

Provide an updated Final Spare Parts List.

10 days prior to substantial completion

COR/TM with SME concurrence

Static, Dynamic & Functional Test Plan

Provide a Static, Dynamic & Functional test plan for approval to allow the government to verify performance.

15 days prior to contractor system testing

COR/TM with SME concurrence

Test Results Provide test results and associated test results.

5 days prior to Readiness Verification

COR/TM with SME concurrence

Spare Parts on Site Provide and supply 5% spare parts onsite.

To Be Determined COR/TM with SME concurrence

Notice of System Compliance

Provide notice to TSA that owner acceptance has been completed and ready for internal TSA testing.

5 days prior to substantial completion

COR/TM with SME concurrence

Final Operations and Maintenance (O&M) Manuals

Provide full O&M manuals to TSA for review, including all new system components as well as maintenance and warranty information.

10 days prior to scheduled acceptance

COR/TM with SME concurrence

As-Built Drawings Provide final as-built drawings.

10 days prior to scheduled acceptance

COR/TM with SME concurrence

PLC

Documentation

Provide PLC code and documentation, including

10 days prior to scheduled acceptance concurrence

70T04020R9NAP6617 – TSIF CBIS Upgrade RFP Page 12 of 78 commented code.

HMI / SAC

Documentation

Provide HMI code and documentation, including commented code.

10 days prior to scheduled acceptance

COR/TM with SME concurrence

Notice of Punch List Completion

Inform TSA that all outstanding items have been corrected and system is ready for TSA validation.

5 days prior to scheduled acceptance

COR/TM with SME

Notice of Final Completion

Inform TSA that all outstanding items have been corrected and system is ready for TSA final walk through.

5 days prior to scheduled acceptance

PLACE OF PERFOMANCE

The place of performance shall be at the Contractor facility and the Transportation Security Administration Integration Facility located at 3701 Post Office Rd Washington, DC 20528.

TRAVEL

The Contractor is required to travel in support of this requirement. All travel shall be in accordance with the Federal Travel Regulations and will be reimbursed based on actual costs.

70T04020R9NAP6617 – TSIF CBIS Upgrade RFP Page 13 of 78

SECTION III – CONTRACT TERMS AND CONDITIONS

A. TSA Special Contracts Requirements

G.5200. 242.001 CONTRACTING OFFICER’S REPRESENTATIVE (COR) AND

TECHNICAL MONITORS (JUL 2015)

The principle role of the COR is to support the Contracting Officer in managing the contract. This is done through furnishing technical direction within the confines of the contract, monitoring performance, ensuring requirements are met within the terms of the contract, and maintaining a strong relationship with the Contracting Officer. As a team the Contracting Officer and COR must ensure that program requirements are clearly communicated and that the agreement is performed to meet them. The principle role of the Technical Monitor (TM) is to support the COR on all work orders, tasks, deliverables and actions that require immediate attention relating to the approved scope and obligated funding of the contract action.

The Contracting Officer hereby designates the individual(s) named below as the Contracting Officer's Representative(s) and Technical Monitor(s). Such designations(s) shall specify the scope and limitations of the authority so delegated.

TSA CORs:

NAME: Edwin Martinez

PHONE NUMBER: 202-525-0238

EMAIL: Edwin.Martinez2@tsa.dhs.gov

The COR(s) and TM(s) may be changed at any time by the Government without prior notice to the Contractor, but notification of the change, including the name and phone number of the successor COR, will be promptly provided to the Contractor by the Contracting Officer in writing.

The responsibilities and limitations of the COR are as follows:

• The COR is responsible for the technical aspects of the project and technical liaison with the

Contractor. The COR is also responsible for the final inspection and acceptance of all reports and such other responsibilities as may be specified in the contract.

• The COR may designate assistant COR(s) to act for him/her by naming such assistant in writing and transmitting a copy of such designation through the Contracting Officer to the Contractor.

• The COR will maintain communications with the Contractor and the Contracting Officer.

The COR must report any observed fraud, waste, or opportunities to improve performance of cost efficiency to the Contracting Officer.

• The COR will immediately alert the Contracting Officer to any possible Contractor deficiencies or questionable practices so that corrections can be made before the problems become significant.

• The COR is not authorized to make any commitments or otherwise obligate the Government or authorize any changes which affect the contract’s price, terms or conditions. Any Contractor request for changes shall be referred to the Contracting Officer directly or through the COR. No such changes shall be made without the expressed prior authorization of the Contracting Officer.

mailto:Edwin.Martinez2@tsa.dhs.gov

70T04020R9NAP6617 – TSIF CBIS Upgrade RFP Page 14 of 78

• The COR is not authorized to direct the Contractor on how to perform the work.

• The COR is not authorized to issue stop-work orders. The COR may recommend the authorization by the Contracting Officer to issue a stop work order, but the Contracting Officer is the only official authorized to issue such order.

• The COR is not authorized to discuss new proposed efforts or encourage the Contractor to perform additional efforts on an existing contract or order.

The responsibilities and limitations of the TM are as follows:

• Coordinating with the COR on all work orders, task, deliverables and actions that require immediate attention relating to the approved scope and obligated funding of the contract action.

• Monitoring the Contractor’s performance in relation to the technical requirements of the assigned functional area of the contract to ensure that the Contractor’s performance is strictly within the contract’s scope and obligated funding.

• Ensuring that all recommended changes in any work under the contract are coordinated and submitted in writing to the COR for consideration.

• Informing the COR if the Contractor is not meeting performance, cost, schedule milestones.

• Performing technical reviews of the Contractor’s proposals as directed by the COR.

• Performing acceptance of the Contractor’s deliverables as directed by the COR.

• Reporting any threats to the health and safety of persons or potential for damage to

Government property or critical national infrastructure which may result from the Contractor’s performance or failure to perform the contract’s requirements.

G.5200.242.003 SUBMISSION OF INVOICES (JUL 2015)

Background: The Transportation Security Administration (TSA) partners with the United States Coast Guard Finance Center for financial services in support of TSA operations, including the payment of contractor invoices. Therefore, all contractor invoices must be submitted to, and will be paid by, the U.S. Coast Guard Finance Center (FinCen).

A. Invoice Submission Method: Invoices may be submitted via facsimile, U.S. Mail, or email.

Contractors shall utilize ONLY ONE method per invoice submission. The submission information for each of the methods is as follows in order of preference:

1. Facsimile number is: 757-413-7314

The facsimile number listed above shall be used by contractors for ORIGINAL invoice submission only. If facsimile submission is utilized, contractors shall not submit hard copies of invoices via the U.S. mail. It is the responsibility of the contractor to verify that invoices are received, regardless of the method of submission used. Contractors may inquire regarding the receipt of invoices by contacting the U.S. Coast Guard Finance Center via the methods listed in subparagraph (d) of this term.

2. Address to mail invoices:

United States Coast Guard Finance Center TSA Commercial Invoices P.O. Box 4111

70T04020R9NAP6617 – TSIF CBIS Upgrade RFP Page 15 of 78

Chesapeake, VA 23327-4111

3. Email Address: FIN-SMB-TSAInvoices@uscg.mil or www.fincen.uscg.mil

B. Invoice Process: Upon receipt of contractor invoices, FinCen will electronically route invoices to the appropriate TSA Contracting Officer’s Representative and/or Contracting Officer for review and approval. Upon approval, the TSA will electronically route the invoices back to FinCen. Upon receipt of certified invoices from an Authorized Certifying Official, FinCen will initiate payment of the invoices.

C. Discounts on invoices. If desired, the Contractor should offer discounts directly upon the invoice submitted, clearly specifying the terms of the discount. Contractors can structure discounted amounts for payment for any time period less than the usual thirty day payment period specified under Prompt Payment requirements; however, the Contractor should not structure terms for payment of net amounts invoiced any sooner than the standard period required under FAR Subpart 32.9 regarding prompt payments for the specified deliverables under contract.

Discounts offered after invoice submission. If the Contractor should wish to offer a discount on a specific invoice after its submission for payment, the Contractor should submit a letter to the Finance Center identifying the specific invoice for which a discount is offered and specify the exact terms of the discount offered and what time period the Government should make payment by in order to receive the discount. The Contractor should clearly indicate the contract number, invoice number and date, and the specific terms of the discount offered. Contractors should not structure terms for net amount payments any sooner than the standard period required under FAR Subpart 32.9 regarding prompt payments for the specified deliverables under contract.

D. Payment Status: Contractors may inquire on the payment status of an invoice by any of the following means:

1. Via the internet: https://www.fincen.uscg.mil Contacting the FinCen Customer Service Section via telephone at 1-800-564-5504 or (757) 523- 6940 (Voice Option #1). The hours of operation for the Customer Service line are 8:00 AM to 5:00 PM Eastern Time, Monday through Friday. However, the Customer Service line has a voice-mail feature that is available 24 hours per day, 7 days per week.

2. Via the Payment Inquiry Form: https://www.fincen.uscg.mil/secure/payment.htm

E. Invoice Elements: Invoices will automatically be rejected if the information required in subparagraph (a)(2) of the Prompt Payment Clause, contained in this Section of the Contract, including EFT banking information, Taxpayer Identification Number (TIN), and DUNS number are not included in the invoice. All invoices must clearly correlate invoiced amounts to the corresponding contract line item number and funding citation. The Contractor shall work with the Government to mutually refine the format, content and method of delivery for all invoice submissions during the performance of the Contract.

F. Supplemental Invoice Documentation: Contractors shall submit all supplemental invoice documentation (e.g. copies of subcontractor invoices, travel vouchers, etc.) necessary to approve mailto:FIN-SMB-TSAInvoices@uscg.mil http://www.fincen.uscg.mil/ https://www.fincen.uscg.mil/ https://www.fincen.uscg.mil/secure/payment.htm

70T04020R9NAP6617 – TSIF CBIS Upgrade RFP Page 16 of 78 an invoice along with the original invoice. The Contractor invoice must contain the information stated in the Prompt Payment Clause in order to be received and processed by FinCen.

Supplemental invoice documentation required for review and approval of invoices may, at the written direction of the Contracting Officer, be submitted directly to either the Contracting Officer, or the Contracting Officer’s Representative. Note for “time-and-material” type contracts: The Contractor must submit the following statement with each invoice for labor hours invoiced under a “time-and-materials” type contract, order, or contract line item: “The Contractor hereby certifies in accordance with paragraph (c) of FAR 52.232-7, that each labor hour has been performed by an employee (prime or subcontractor) who meets the contract’s specified requirements for the labor category invoiced.”

G. Additional Invoice Preparation Instructions for Software Development and/or Hardware.

The Contractor shall clearly include a separate breakdown (by CLIN) for any software development activities (labor costs, subcontractor costs, etc.) in accordance with Federal Accounting Standards Advisory Board Statement of Federal Financial Accounting Standards Number 10 (Preliminary design costs, Development costs and post implementation costs) and cite payment terms. The contractor shall provide make and model descriptions as well as serial numbers for purchases of hardware and software (where applicable.)

H. Frequency of Invoice Submission. This area is for the CO to document how often the contractor is allowed to submit invoices. An example is” Invoices shall be submitted on a monthly basis in accordance with the schedule.”

G. 5200.243.001 CONTRACTING OFFICER (CO) (JUL 2015)

The Contracting Officer is the only person authorized to make any changes, approve any changes in the requirements of this contract, issue orders, obligate funds and authorize the expenditure of funds, and notwithstanding any term contained elsewhere in this contract, such authority remains vested solely in the Contracting Officer. (For further information, the Contracting Officer is a federal government employee who is specifically authorized and appointed in writing under specified agency procedures and granted the authority to enter into, administer, and/or terminate contracts and make related determinations and findings.) In the event, the Contractor makes any changes at the direction of any person other than the Contracting Officer, the change will be considered to have been without authority and no adjustment will be made in the contract price to cover any increase in costs incurred as a result thereof.

The following Primary Contracting Officer is assigned to this contract. Alternate Contracting Officers may be assigned:

TSA Contracting Officer:

NAME: Jaylin Wilson

PHONE NUMBER: 571-227-5562

EMAIL: Jaylin.Wilson@tsa.dhs.gov

H.5200.204.002 CONTRACTOR PERSONNEL ACCESS TO TSA FACILITIES,

INFORMATION AND/OR SYSTEMS (SEP 2018)

mailto:Jaylin.Wilson@tsa.dhs.gov

70T04020R9NAP6617 – TSIF CBIS Upgrade RFP Page 17 of 78

A. All Contractor personnel requiring access to TSA facilities, information systems, and/or information will be subject to the security procedures set forth in this contract.

B. All contractor employees seeking to provide services to TSA under a TSA contract are subject to a fitness determination to assess whether their initial employment or continued employment on a TSA contract protects or promotes the efficiency of the agency. TSA, by and through the Law Enforcement/Federal Air Marshall Service’s, Personnel Security Section (PerSec), will allow a contractor employee to commence work on a TSA contract only if a review of the contractor employee’s preliminary background check is favorable. Contractor employees with unfavorable preliminary background checks will not be allowed to work on a TSA contract.

C. A fitness determination involves the following three phases:

1. Phase 1: Enter On Duty Fitness Determination: a review of a contractor employee’s consumer credit report, criminal history records, and submitted security forms to determine, to the extent possible, if the contractor employee has bad debt and/or criminal offenses and/or falsification issues that would prohibit employment as a TSA contractor. This determination may include verification of citizenship for contractor employees born outside of the United States. A favorable Enter On Duty Suitability Determination is not a final fitness determination; rather, it is a preliminary review of external data sources that allows the contractor employee to commence work prior to the required background investigation being completed.

When a contractor employee is deemed eligible to commence work on a TSA contract, TSA PerSec will notify the appropriate Contracting Officer’s Representative (COR) of the favorable determination. Similar notifications will be sent when a contractor employee has not passed the preliminary background check and has been deemed unsuitable.

2. Phase 2: Background Investigation: Once the contractor employee commences work on a

TSA contract, TSA PerSec will process all submitted security forms to determine whether the contractor has previously been the subject of a federal background investigation sufficient in scope to meet TSA minimum investigative requirements. Contractor employees who have a federal investigation sufficient in scope will immediately be processed for final fitness adjudication. Those contractor employees who do not have a previous federal background investigation sufficient in scope will be scheduled for the appropriate level background investigation through the submission of their security forms to the Office of Personnel Management (OPM).

3. Phase 3: Final Fitness Adjudication: TSA PerSec will complete the final fitness determination after receipt, review, and adjudication of the completed OPM background investigation. The final fitness determination is an assessment made by TSA PerSec to determine whether there is reasonable expectation that the continued employment of the TSA contractor will or will not protect or promote the efficiency of the agency. An unfavorable final fitness determination will result in a notification to the COR that the contractor employee has been deemed unfit for continued contract employment and that he/she shall be removed from the TSA contract.

D. The period of performance may begin 60 days after contract award to allow for the Enter On

Duty Fitness Determination. A contract modification shall be executed to revise the period of

70T04020R9NAP6617 – TSIF CBIS Upgrade RFP Page 18 of 78 performance once the determination process is completed. For Fixed price awards, in the event of staggered completed determinations the parties may negotiate fixed monthly rates so that performance can begin with partial staff.

E. Whenever personal identity verification (PIV) cards are required for issuance or re-issuance to contractor personnel for authorized access to Government facilities, under the guidance of the Contracting Officer’s Representative (COR), the Contractor is responsible for making all arrangements for affected Contractor personnel to report in-person at the nearest Government issuing facility to initiate and complete procedures for PIV card issuance. The Government will not be able to provide PIV card issuance at any other locations than those officially designated as available. PIV card issuing facilities that are available for the completion of this requirement for TSA contractors are as listed by the TSA Personnel Security Section, and the COR will advise the Contractor about Government PIV card issuing facility locations that are nearby the contractor’s location(s) of performance that will be potentially available for card issuance when required.

If the contractor will require access to Government Information Systems, include following paragraphs:

F. Computer Access Agreement. All Contractor employees (users, managers, and operators of the

TSA network) must sign TSA Form 1403, Computer Access Agreement. A copy of which shall be provided to the TSA contracting officer’s representative for retention for the duration of the

G. Personnel Security.

1. Privileged access users are individuals who have access to an information technology (IT) system with privileges of Administrator or above and have access to sensitive network infrastructure data. Privileged access users will be appropriately screened on entry into the privileged access position and the initial screening shall be refreshed every two years,

2. Individuals terminating voluntarily or involuntarily from a Contractor performing under contract at TSA must have an exit briefing, conducted by a supervisory or management-level employee of the Contractor in order to identify and explain their post-employment responsibilities to the TSA.

3. Records of exit interviews will be signed and maintained by the Contractor as part of the individual employment record for a period of not less than two years following the termination of the individual’s employment.

4. The Contractor shall notify the Contracting Officer's Representative and the Contracting

Officer with proposed personnel changes. Written confirmation is required. This includes, but is not limited to, name changes, resignations, terminations, and reassignments to another

5. The Contractor shall notify the TSA, in writing of any requested change in access requirements for its employees no later than one day after any personnel changes occur. This includes name changes, resignations, terminations, and transfers to other company

70T04020R9NAP6617 – TSIF CBIS Upgrade RFP Page 19 of 78 engagements. The Contractor shall provide the following information to TSA: full name, social security number, effective date, and reason for change.

6. The Contracting Officer must approve all personnel replacements. Estimated completion of the necessary background investigation for employee access to government facilities and information systems is approximately 30 days from the date the completed forms are received (and acknowledged as complete) in the Security Programs Division.

Failure of any Contractor personnel to pass a background investigation, without timely substitution that meets the contracts requirements, may be grounds for termination of the contract.

H. Non-Disclosure Agreements.

1. All TSA contractor employees and consultants must execute a DHS Form 11000-6, Sensitive But Unclassified Information Non-Disclosure Agreement (NDA) upon initial assignment to TSA and before being provided access to TSA “sensitive and/or mission critical information.” The original NDA will be provided to the TSA contracting officer’s representative for retention for the duration of the contract.

2. The Contractor, and those operating on its behalf, shall adhere to the requirements of the non-disclosure agreement unless otherwise authorized in writing by the Contracting Officer.

I. Performance Requirements.

1. The Contractor shall not be liable for any injury to Government personnel or damage to Government property arising from the use of equipment maintained by the Contractor, unless such injury or damage is due to the fault or negligence of the Contractor.

2. Contracting Officer’s Representative (COR) and IT Security Division shall conduct reviews to ensure that the security requirements in the contract are implemented and enforced.

(End of term)

IF the TSA service contracts requires on-site contractor performance where contractors will have TSA IT accounts with access to the TSA Online Learning Center (OLC) include the following paragraph”.

J. All Contractor personnel with TSA IT accounts requiring unescorted access to TSA facilities, information systems, or information will be required to complete Workplace Violence Prevention training available through the TSA Online Learning Center. The course, entitled “Preventing Workplace Violence at TSA” shall be completed within 60 days of onboarding.

H.5200.204.004 REQUIREMENTS FOR HANDLING SENSITIVE SECURITY

INFORMATION (SSI) (SEP 2018)

Pursuant to 49 U.S.C. § 114(r), Sensitive Security Information and Nondisclosure of Security Activities, Sensitive Security Information (SSI) is a category of sensitive but unclassified (SBU) information that must be protected because it is information that, if publicly released, would be detrimental to the security of transportation. Under 49 Code of Federal Regulations (C.F.R.) §

70T04020R9NAP6617 – TSIF CBIS Upgrade RFP Page 20 of 78

1520.5(a), the SSI Regulation also provides additional reasons for protecting information as SSI beyond the condition that the release of the information would be detrimental to the security of transportation. TSA, however, primarily uses the criterion of “detrimental to the security of transportation” when determining whether information is SSI.

Title 49 of the Code of Federal Regulations, Part 1520 defines the scope, categorization, handling requirements and disposition of information deemed SSI is the 49 C.F.R. Part 1520 (http://ecfr.gpoaccess.gov/). Persons authorized to access specific SSI (i.e., covered persons) include those contracted to DHS or TSA with a need-to-know basis for specific information in the course of fulfilling their TSA contractual obligations. TSA may deliver SSI materials to the Contractor. Also, materials created by the Contractor may require SSI designation and protection, and the Contractor has the responsibility to identify such materials to TSA as possible SSI. For guidance while working on TSA and DHS matters, see the TSA SSI Application Guide, 2011_04_01 for identifying the type of information covered by the regulation.

For purposes of this term, the term “Contractor” shall include an individual or other legal entity who performs work for or on behalf of TSA or DHS under a contract, interagency agreement, or other transaction agreement. Such contracts include, but are not limited to, contracts between any non- Federal entity and/or TSA or DHS and subcontracts, joint venture agreements, and teaming agreements between any non-Federal entity and another non-Federal entity to perform work related to the primary contract with the TSA or DHS.

While SSI is not classified national security information subject to the handling requirements governing classified information, it is subject to certain legal disclosure limitations. To ensure regulatory compliance, the Contractor shall be subject to the following requirements and include this entire term as flow-down in subcontracts, etc.:

A. Handling and Safeguarding. The TSA Contractor shall safeguard and handle any SSI in accordance with the policies and procedures outlined in 49 C.F.R. Part 1520, as well as the DHS and TSA policies and procedures for handling and safeguarding SSI. These safeguarding procedures shall include SSI recognition, identification and marking of materials that possibly contain SSI, including Contractor-created materials, as well as following restrictions on disclosure, storage, handling, sharing, dissemination and destruction of SSI. The Contractor, without exception, shall place this requirement in all subcontracts, joint venture agreements, and teaming agreements related to the performance of this contract.

B. Non-Disclosure Agreements (NDAs). (DHS Form 11000-6, NDAs are required to be signed by all Contractor personnel when access to SSI is necessary for performance of the contract. By signing the NDA, the recipient certifies in writing that they will take the necessary steps to prevent the unauthorized disclosure and use of information.

C. Request for Access to SSI materials. Pursuant to 49 C.F.R. § 1520.9(a)(3), the Contractor must contact SSI@tsa.dhs.gov for guidance on handling requests to access to SSI (before using SSI materials) for any other purpose besides activities falling within the scope of the contract by other persons, including requests from experts, consultants, and legal counsel (“requesters”) hired by the Contractor. The Contractor shall include the Contracting Officer (CO) and Contracting Officer Representative (COR) as a carbon copy “cc” recipient of its contact to SSI@tsa.dhs.gov . The TSA SSI Office must first make a determination as to whether the http://ecfr.gpoaccess.gov/ mailto:SSI@tsa.dhs.gov mailto:SSI@tsa.dhs.gov

70T04020R9NAP6617 – TSIF CBIS Upgrade RFP Page 21 of 78 requesters are a “covered person” with a “need to know” under 49 C.F.R. §§ 1520.7 and

1520.11. Special request processing and handling requirements apply to contractor employees who may be foreign nationals. The Contractor must clearly identify any employees who are not US citizens who are otherwise requested to have access to SSI; the requirements of TSA Management Directive 2810.3, Management of Foreign Access to Sensitive Information apply.

D. Training and Certification. All Contractor personnel who are covered persons with a need-to-know basis must complete the TSA-mandated SSI Awareness Training course prior to accessing SSI, and on an annual basis for the duration of the contract or for the duration of the requester’s need for access to SSI, whichever is later. Contractor personnel must also review and adhere to the SSI Quick Reference Guide for DHS Employees and Contractors. The Contractor shall certify to the Contracting Officer annually that all covered persons have completed the mandated SSI training, that all SSI policies and procedures have been followed, and that those individuals with access understand their responsibilities to protect the information.

E. Breach. In accordance with 49 C.F.R. § 1520.9(c), the Contractor agrees that in the event of any actual or suspected breach of SSI (i.e., loss of control, compromise, unauthorized disclosure, access for an unauthorized purpose, or other unauthorized access, whether physical or electronic), the Contractor shall immediately, and in no event later than one hour of discovery, report the breach to the Contracting Officer and the COR. The Contractor is responsible for positively verifying that notification is received and acknowledged by at least one of the foregoing Government officials.

In the event that an SSI breach occurs as a result of the violation of a term of this contract by the Contractor or its employees, or the Contractor’s covered persons, the Contractor shall, as directed by the Contracting Officer and at no cost to the Government, without delay correct or mitigate the violation.

For unauthorized disclosure of SSI, the Contractor and Contractor's employees and Contractor’s covered persons may also be subject to civil penalties and other consequences as set forth in 49 C.F.R. § 1520.17.

H.5200.204.005 NON-FEDERAL ACCESS TO TSA NATIONAL CAPITAL REGION

FACILITIES (SEP 2016)

A. Background. Department of Homeland Security (DHS) Visitor Access Policy mandates that visitors, to include all parties such as proposed subcontractors, accessing DHS National Capital Region (NCR) Component Headquarters and related Headquarters NCR facilities be subject to a criminal history check. To that end, in July 2016, TSA began requiring the submission of Personally Identifiable Information (PII) for all non-federal visitors and foreign national visitors entering TSA facilities in the National Capital Region, including TSA Headquarters, the Freedom Center, Annapolis Junction, Walker Lane, and the Transportation Security Integration Facility (TSIF), in order to process the required screening checks. Of note, for contracts requiring access to TSA facilities, information systems, or sensitive but unclassified information as part of contract performance, contractor employees are subject to a suitability determination. (See

H.5200.204.002, CONTRACTOR PERSONNEL ACCESS TO TSA FACILITIES,

INFORMATION AND/OR SYSTEMS).

https://ishare.tsa.dhs.gov/Offices/LawEnforcementFAMS/SecuritySvcAssessments/SSIBranch/Quick%20Reference%20Guides/SSI%20Quick%20Reference%20Guide%20for%20DHS%20Employees%20and%20Contractors.pdf

70T04020R9NAP6617 – TSIF CBIS Upgrade RFP Page 22 of 78

B. Purpose: The submitted information will be used to conduct screening checks to permit and maintain records of access to DHS NCR facilities pursuant to the authority of 40 U.S.C. § 1315;

41 C.F.R. Part 102-81; Executive Order. 9397.

C. Applicability: A…