Attch_1_-_PWS_30Oct15_AFG-PAK_3PL.pdf

SURFACE DEPLOYMENT DISTRIBUTION COMMAND

PERFORMANCE WORK STATEMENT

Logistics Monitoring Support

831st Transportation Battalion

30 October 2015

Table of Contents

1.0 Description of Services

2.0 Logistics and Tracking Requirements

3.0 Reports

4.0 Personnel

5.0 Key Control

6.0 Security Requirements

7.0 Bagram Specific Security Requirements

8.0 Cargo Movement Reporting

9.0 Sealing Operations

10.0 RFID/CIDD/Satellite Tags (Container Intrusion Detention Device) Operations

11.0 Cargo Surveys / Inspections

12.0 USC Contractor Surveillance

13.0 Route Reporting

14.0 Cargo Expeditors

15.0 Government Furnished Property and Facilities

16.0 Organizational Conflict of Interest

17.0 Ethics Training

18.0 Confidentiality and Non-Disclosure of Information

19.0 Synchronized Pre-Deployment Operational Tracker (SPOT)

20.0 Bagram (SPECIFIC) Requirements

21.0 Deliverables

22.0 Cyber Security

Appendix A: Performance Requirement Summary

Appendix B: Deliverables Schedule

Appendix C: Minimum Security Controls – Cyber Security

AFGHANISTAN/PAKISTAN LOGISTICS MONITORING SUPPORT

1.0 Description of Services

1.1 The contractor shall perform import and export logistics and tracking services at selected locations in Pakistan and Afghanistan with the level of operations varying from location to location. This contract will require interfacing with the Universal Services Contract commercial carriers for reporting information, provided that the logistics monitoring support contractor does not unduly impede the carrier’s operations. The US Government (USG) will provide any training required to update information on the Surface Deployment & Distribution Command (SDDC) Electronic Transportation

Acquisition (ETA) website. Cargo movement reporting at all locations is required seven days a week;

additional services outlined below must be able to be performed 24 hours a day, 7 days a week, 365 days a year.

1.1.1 Terms such as “manage,” “administer,” and “oversee” as used in this contract shall not be taken to mean that the Contractor personnel can perform inherently governmental functions. Decision making, supervision and directing US Government employees (hereafter referred as Government) are examples of inherently governmental functions and unauthorized under this contract. Contractor personnel shall only provide recommendations to the 595 th

TBDE management and cannot make final decisions in any manner.

1.2 The 831

st

DDSB requires a large logistics monitoring contractor presence in the combined areas of

Pakistan and Afghanistan in order to provide / perform the below services:

a) Cargo movement reporting at designated locations throughout both countries – to include the submission of daily operational reports

b) Sealing operations (bolt, cable, or other) at locations throughout both countries

c) Radio Frequency Identification (RFID) / Container Intrusion Detection Device (CIDD) operations at pre-determined locations where appropriate training and equipment has been provided by the US Government

d) IBS-CMM (Integrated Booking System – Container Management Module) status updates

e) Cargo surveys and inspections

f) USC Contractor Surveillance

g) Regular route updates and intelligence, to include threat assessments throughout Afghanistan and

Pakistan, and trend / transit time analyses

1.3 These services will be required for SDDC and other US military-sponsored shipments entering

Pakistan via Karachi or Port Qasim (all terminals) and entering Afghanistan via the Chaman, Torkham, Hairaton, Sher Khan, and / or ALT CASA border crossings (import) and exiting Afghanistan and

Pakistan via the aforementioned nodes (export). Additional entry and exit nodes may be added at the discretion of the US Government.

1.4 There will be an average of 1000 import conveyances transiting the Afghanistan and Pakistan ground lines of communication (GLOC) per month (to include shipments arriving via the northern distribution network) and 500 export conveyances. This number may increase or decrease due to US military transportation requirements.

1.5 The Government will notify the contractor within 30 days of any additional locations where the above-mentioned services are required to be performed. The contractor must maintain a constant capability to surge to any location within Afghanistan or Pakistan within this 30-day period.

1.6 The contractor must provide personnel capable of facilitating, coordinating, obtaining, and reporting critical movement control data and information to the appropriate USG personnel at multiple locations identified by the COR/Procuring Contracting Officer (PCO). The COR will provide the Contractor with all required Points of Contact and e-mail distribution lists.

1.7 The Contractual work requires knowledge in transportation, logistics, port operations, customs clearance, and documentation procedures. Contractor personnel must have experience and qualifications in transportation movement control procedures and operations. Contractor personnel will have knowledge in the Microsoft Office Suite applications. They must also speak and write in fluent English. Contractor ensures personnel are ready to work and no disruption in operation will occur once personnel commence service. Procuring Contracting Officer (PCO) will direct changes to the Contractor’s tasks in coordination with the 595 th

TBDE Contracting Officer Representative

(hereafter referred as COR).

2.0 Logistics and Tracking Requirements

2.1 The Contractor shall perform reporting functions for cargo movement on the United States

Transportation Command (USTRANSCOM) Universal Service Contract (USC). This includes tallying cargo/trucks, scanning cargo labels, and uploading information into USG data systems.

2.2 Contractor will track and trace cargo from origin to the final destination and assist if there are any issues with documentation, including verifying information for any discrepancies.

2.3 Contractor will process and verify cargo shipping and customs documentation with Customs

Officials and 595 th

TBDE/831

Trans BN COR Representative.

2.4 Contractor may either submit shipment information through automated USG systems or via e-mail, telephone, or fax.

3.0 Reports

3.1 Contractor shall submit all reports detailed in PWS Appendix B, Deliverables Schedule.

3.2 In addition to the reports detailed in the Deliverables Schedule, the Contractor may be required to generate ad-hoc queries, charts, and reports.

3.3 Reporting Format: The Contractor will submit all information and reports to the 595 th

TBDE/831

Trans BN COR using Microsoft suites such as Word, Excel, Access, or Power Point.

4.0 Personnel

4.1 The contractor shall not employ any person under this contract who is simultaneously an employee of the United States Government. The Contractor may employ Local Nationals (LN’s) to perform services at all locations except on Bagram Air Field. The Contractor shall only employ Other Country Nationals

(OCN’s) to perform services on Bagram Airfield.

4.2 The contractor shall provide list of the personnel’s employed in Bagram Airfield. Information at a minimum will be Name, Nationality, Country Identification number, address and age.

5.0 Key Control

5.1 The Contractor shall establish and implement key control procedures ensuring that keys issued to the

Contractor by the Government; (i.e., for vehicles, containers, etc.) are not lost, misplaced or duplicated.

5.2 The Contractor shall report the occurrence of a lost or duplicated key, any misuse of keys, tampering, or breaking of locks/seals to the COR within thirty (30) minutes from when the Contractor becomes aware of the occurrence. In the event such a situation occurs, the Contractor shall immediately re-key or replace the affected locks or seals at his own expense.

5.3 The Contractor shall be responsible for prohibiting the use of keys issued by the Government by any person other than the Contractor's employees or his authorized subcontractors.

6.0 Security Requirements

6.1 The overall classification of work associated with this contract is at the UNCLASSIFIED level.

Under the requirement of this contract, there are personnel that may require an alternative PKI credential

(ASCL Token). The ASCL Token will be issued only after the following requirements are met:

a. The investigation must be consistent with National Agency Check and Inquires (NACI) requirements, to the greatest extent possible,

b. A fingerprint check against the FBI criminal history database with favorable results, and

c. A FBI investigation files (name check) search and a name check against the terrorist screening database. IAW DOD 5200.46.

No CACs will authorized under this contract.

6.2 595th S2 must initiate and ensure completion of a background investigation before applying the credentialing standards to a non-U.S. national at their location. The background investigation must be favorably adjudicated before an ASCL Token can be issued to a non-U.S. national at a foreign location.

The type of background investigation may vary based on standing reciprocity treaties concerning identity assurance and information exchanges that exist between the U.S. and its allies or agency agreements with the host country.

6.3 Non-U.S. Nationals who have resided in the U.S. or U.S. territory for three years or more will be processed for a NACI investigation IAW existing regulations and policy procedures.

6.4 Contractor personnel shall read and comply with applicable DoD security regulations, policies, and procedures for access to specific installations and facilities

6.4.1. The Contractor is responsible for being aware of and complying with the requirements associated with Installation Access Control. The Government is not liable for any costs associated with performance delays due solely to a firm’s failure to comply with Installation Access Control processing requirements.

6.4.2 Contractor personnel shall adhere to all security requirements set forth by the Pakistan and

Afghanistan Port Director/Commander.

6.5 Prior to the beginning of contract performance, the Contractor shall submit a complete list to the

Contracting Officer (CO) of all personnel who will perform services under this contract. The list shall contain:

a. Name and address of each employee.

b. Copy of the Identification Document or driving license of each employee, and certificate of good conduct.

c. Copy of employment card or equivalent.

6.5.1 The Contractor is responsible for keeping this listing accurate and reporting changes to the COR within forty eight (48) hours of Recruitment/Termination of any employees performing services under this contract.

6.6 If the Government notifies the contractor that the employment or the continued employment of any contractor employee is prejudicial to the interests or endangers the security of the United States of

America, that person shall be removed and barred from the worksite. This includes security deviations/incidents and credible derogatory information on contract members during the course of the contract period. The company receiving award of this task order shall make any changes necessary in the appointment(s).

6.7 The contractor personnel that require access to government systems shall comply with the provisions of AR 530-1, Operations Security (OPSEC). The OPSEC process identifies the critical information of military plans, operations and supporting activities and the indicators that can reveal it, and then develops measures to eliminate, reduce, or conceal those indicators. The Contractor shall ensure that any

USG information intended for public release is reviewed and approved by a USG OPSEC Officer prior to release to any public forum (i.e.: Internet web pages, professional publications, company newsletter).

For clarification on any OPSEC questions or issues, the contractor shall coordinate with the COR to contact a certified USG OPSEC Officer for assistance.

7.0 Bagram Specific Security Requirements

7.1 Bagram Entry Requirements

7.1.1 To gain entry to Entry Control Point 2 (ECP-2), an individual must possess the following:

a. Bagram Badge (Red, Yellow, or Green)

b. Letter of Authorization (LOA)

c. Original Passport/Taskera

7.1.2 Only badges issued by the Force Protection Screening Cell (FPSC) will be considered as Official

Bagram Airfield badges. All civilians, including contactors, are required to display a Bagram Airfield

Badge at all times.

7.1.3 Bagram Badging Process

7.1.3.1 Other Country Nationals (OCN’s) are screened and searched in accordance with point of entry and force protection requirements. This includes:

a. Personnel and property search.

b. Biometric enrollment and screening.

c. Must process through all security check points before gaining entry onto Bagram Airfield.

7.1.3.2 The contractor is to ensure that all applicants are escorted from the point of entry to FPSC.

7.1.3.3 The contractor presents the employee to the FPSC for screening and badge determination. The

Hiring Authority, on behalf of the employee, is responsible for presenting:

a. Original Taskera/Passport

b. Badging Application Form 103

c. Complete Medical Screening

d. Proof employee is at least 17 years old

7.1.3.4 Screening and Vetting Requirements

7.1.3.4.1 Screening and vetting is the process by which the FPSC determines the identity and suitability of individuals wishing to obtain a Bagram Access Badge. If an OCN fails the screening process:

a. The FPSC informs the appropriate Counter-Intelligence Agency

b. The FPSC immediately documents the results of the screening

c. The contractor must remove the individual from the installation as soon as possible

d. If during the screening a major threat is suspected, the FPSC notifies the Counter-Intelligence

Support Team or appropriate CI agencies.

7.2 Escort Badges

7.2.1 For escorting of vehicles and/or convoys on and off post the Contractor will have to be properly cleared/badged and determined feasible by the Force Protection Security Agency on Bagram Air Field.

7.2.2 The following are required to receive an escort badge:

a. Memo signed by the Hiring Authority.

b. Must possess a valid yellow or green badge.

c. Must complete the escort class given at the FPSC in Bagram.

d. Required to speak Basic English.

e. Be able to answer general questions during an emergency.

7.2.3 Contractor employees with Escort Badges must be stationed and reside on Bagram Airfield.

8.0 Cargo Movement Reporting

8.1 Due to current limitations on having US military presence in Pakistan and threat levels precluding

US Military active involvement with the contractor “outside the wire” in Afghanistan, the contractor must be proactive at identifying appropriate methods for obtaining the necessary in-transit visibility information outlined below. At select locations determined by the COR throughout Pakistan and

Afghanistan – to include ports, border crossings, official and unofficial checkpoints and rest stops, and final destinations / base camps within the theater of operations.

8.2 Cargo Movement Report (Import) Information. The contractor shall physically track and report the following import information at a minimum:

- Container Numbers

- Integrated Booking System (IBS) Transportation Control Numbers (TCNs)

- Port Call File Numbers (PCFNs)

- Military TCNs

- Size / Conveyance Types

- All Seal Numbers

- RFID Tag Numbers

- Vessel Names

- Voyage Numbers

- Discharge Dates

- Dispatch Dates

- Border Crossing Dates / Names

- Destination Arrival Dates

- Delivery Dates

- Truck Numbers (all interchanges)

- Driver Names (all interchanges)

8.2.1 Cargo Movement Report (Export) Information. The contractor shall track and report the following export information:

- IBS TCNs

- Port Call File Numbers (PCFNs)

- Military TCNs

- Size / Conveyance Types

- All Seal Numbers

- RFID Tag Numbers

- Origins

- Border Crossing Dates and Names

- Port Arrival Dates / Names

- Vessel Names

- Voyage Numbers

- Sail Dates

- Truck Numbers (all interchanges)

- Driver Names (all interchanges)

8.2.2 All Cargo Movement reports shall be submitted in excel format to a COR-approved distribution list. The exact layout of the reports, including necessary fields, will be provided by the COR Not Later

Than 10 days after contract award.

8.2.2.1 Should one or more reports be transitioned to an online / automated process, the contractor will be provided sufficient training and access so as to accomplish their regular updates with minimal additional effort.

8.2.3 Cargo Movement reports shall be submitted 7 days a week, 365 days a year.

8.2.4 Logistics / tracking locations:

8.2.4.1 Pakistan: Karachi (KICT and PICT), Qasim, Karachi Port Trust, Quetta, Torkham, and

Chaman.

8.2.4.2 Afghanistan: Torkham, Hairatan, Kabul (Supreme / Camp Phoenix / ANA-ANP Depots), Jalalabad, Bagram, Kandahar, Spin Boldak, Sher Khan Border, Towraghaundi

9.0 Sealing Operations

9.1 For import containers, the contractor shall monitor and report on a daily basis how many containers arrived in Pakistan / Afghanistan with adequate cable and bolt seals, the cable and bolt seal serial numbers, their corresponding container numbers, and how many containers arrived without cable and bolt seals. Containers arriving in Karachi and Qasim without seals shall be re- sealed by the contractor and the new seal serial numbers shall be annotated on the contractor’s Seal Operation

Report. Data shall be consolidated on a weekly, monthly, and / or yearly basis and a report provided to a COR-approved distribution list.

9.2 For export containers, the contractor shall monitor and report on a daily basis how many containers departed from the origins in Afghanistan with adequate cable and bolt seals, the cable and bolt seal numbers, their corresponding container numbers, and how many containers departed without cable and bolt seals. Containers departing without seals shall be re-sealed by the contractor and the new seal serials numbers shall be annotated on the contractor’s regular reports. Data shall be consolidated on a weekly, monthly, and / or yearly basis and a report provided to a COR - approved distribution list.

9.3 If a container arrives at any entry or exit node (import and export cargo) identified as logistics / tracking location without a cable and / or bolt seal or a cable and / or bolt seal of a different serial number than the cable and bolt seal reported at the previous event location, the 831 st

DDSB will be notified immediately and a joint inspection of the container in question may be carried out with carrier, contractor, US Government, and / or host nation (customs) representatives. At the very least, all containers – import and export – will have a new cable and / or bolt seal applied at the location where the discrepancy is noted.

9.4 The contractor shall coordinate with Pakistan Customs authorities, be present, and monitor when

Pakistan customs seals are applied to DOD containers. The contractor shall tally the number of seals and provide seal serial numbers along with corresponding container numbers in daily reports.

9.5 The contractor shall coordinate with Pakistan Customs authorities and be present and monitor when Pakistan customs seals are checked and removed from DOD containers upon crossing into

Afghanistan.

10.0 RFID/CIDD/Satellite Tags (Container Intrusion Detention Device) Operations

10.1 On a daily basis, the contractor shall record the arrival of shipments with RFID Tags at the

Pakistan / Afghanistan entry nodes. The contractor shall conduct Hand Held Interrogator (HHI) operations to capture all arrivals at each entry / exit node (i.e. port terminals and border crossings). If

HHI operations are not allowed or not feasible for any reason, the contractor shall conduct human interrogator operations to record RFID “pings” for every shipment with an RFID tag.

10.2 The contractor shall update, as required, the software for TIPS Write on US Government issued laptops and Savi Mobile Manager on the HHIs.

10.3 The contractor shall update as required the firmware on all US Government-issued HHIs.

10.4 A list of Government-issued equipment to be maintained by the contractor will be provided upon contract award. Appropriate training will be arranged by the COR at a location convenient to all parties.

10.5 The Contractor will make available a team of personnel to be trained on the Savi ST 654i and ST

656i Tags (in any subsequent upgrading tags) procedures and utilization of the appropriate HHIs for management of this operation. Once trained, it is the responsibility of the Contractor to interrogate and arm / re-arm tags.

10.6 The contractor will follow established breach procedures in the event a 654i and 656i tags has had both the door and light alarms triggered. When directed by the COR, the contractor will arrive at a designated location, conduct a joint inspection of the container with the carrier, trucker, and host-nation / US Government representatives, reseal the container, and re-arm the tag. In all instances, the contractor will be expected to provide the RFID incident report complete with photographs.

11.0 Cargo Surveys / Inspections

11.1 When requested by the COR, the contractor will dispatch appropriate personnel to any location within Pakistan and Afghanistan for the purpose of conducting joint surveys and inspections in conjunction with carrier, trucker, US Government, and host-nation representatives. These inspections may occur at any time due to accidents, pilferage, armed attacks, or documentation / seal discrepancies.

In all instances, the contractor must provide a detailed report following the inspection that will include personnel present, actions taken, all available information on the cargo, and photographs. The contractor will recommend viable courses of action to the COR for disposition of the cargo.

12.0 USC Contractor Surveillance

12.1 The contractor must remain proactive and vigilant in order to photograph and identify contractual failures and transgressions committed by the USC contractors and immediately prepare and submit reports to the appointed government official, that identify the cargo involved. Due to restrictions on the military presence at key logistical locations in Afghanistan and Pakistan, quality assurance on USC shipments is problematic. Therefore, the contractor must document and report any deficiencies found in the disposition of USC contractor shipped cargo. All findings shall be submitted to the COR for validation of the deficiency. Common violations include: Failure to tarp cargo, failure to properly secure cargo, failure to take proper measures to prevent damage, and improper use of US Government equipment. However, any perceived instance of the mishandling of USG cargo while in a carrier’s possession must be documented and reported to the COR. All instances must be recorded and submitted to the COR without hindering or otherwise impeding the movement of the cargo.

13.0 Route Reporting

13.1 Upon request, the contractor will conduct research and analysis on the status of the routes throughout Pakistan and Afghanistan, to include road deterioration, threat level, official and unofficial involvement in the metering of traffic, weather delays, tribal interference, and other tangible and intangible aspects of transportation in these countries. A Status of Routes Report will be prepared and disseminated as required. The contractor will also prepare and submit a historical trend / transit time analysis based on the logistics tracking information obtained by the contractor. The analyses may include raw data, charts, graphs, or other modes of presentation.

14.0 Cargo Expeditors

14.1 The Contractor shall provide all personnel, equipment, supplies, facilities, transportation, tools, materials, supervision, other items, and non-personal services necessary to perform SDDC Cargo

Expediting at the locations identified by the 831 st Transportation Battalion. The contractor will be responsible for expediting all frustrated and delayed cargo not being allowed transit through the

Afghanistan/Pakistan border control points, and contracted carrier trucks build up at the border and within carrier controlled holding yards outside of the wire but still within Afghanistan/Pakistan. The Contractor shall establish logistics monitoring offices within the identified border control stations; assist carriers and the US Embassy Kabul Customs Department in locating, tracking, and presenting, border crossing memorandums (BCMs), T-1 Tariff Exemptions, ITM’s (Import Tariff Memo) Tazkira, and Freedom of

Movement documentation to customs officials; Work directly with Afghanistan/Pakistan customs officials and carrier representatives in Designated Border Locations; clear, and move cargo across the

Afghan-Pakistan border; Work directly with Afghan customs officials to establish SDDC truck lanes at designated border crossings; Communicate requirements for updated documentation directly to carrier representatives, SDDC, and the US Embassy Customs Departments in Kabul and Islamabad; Provide the

Daily Border Crossing Report that includes truck, driver name, carrier, and Transportation Control

Number (TCN) to SDDC, carrier representatives, and the US Embassy Customs Departments in Kabul and Islamabad. Provide the Containers in Yard report daily. The format will be approved by the COR.

15.0 Government Furnished Property and Facilities

15.1 Property

15.2 The contractor shall perform a joint inventory of Government furnished property (GFP) with the

COR. The property is to be furnished in an ‘‘as-is’’ condition. The contractor shall document damage and shortage items. The contractor shall repair or replace the damaged items and acquire the shortage items to maintain a fully mission capable status, and maintain one hundred percent (100%) property accountability of all GFP. The contractor shall perform monthly cyclic inventories of all Government property IAW the FAR Part 45.

15.3 The contractor shall no later than 31 Oct of each year, provide to the COR a report for all DoD property for which the contractor is accountable under the contract. The report shall be prepared IAW the requirements of DD Form 1662, DoD Property in the Custody of Contractors, or a substitute format approved by the PCO.

15.4 The Government reserves the right to provide Government Furnished Property (GFP) at any time under this contract to support cargo operations.

15.5 In the event GFP is provided, the Contractor shall be responsible for maintenance and repair.

Responsibilities include but are not limited to:

15.5.1 Perform 10/20 level maintenance on GFP equipment and/or replace and repair parts as necessary

15.5.2 Document and maintain records of maintenance performed and corrected on DA Form 2404.

15.5.3 Develop maintenance plan within thirty (30) days of receipt of GFP that identifies procedures, policies and actions required to implement, maintain and conduct maintenance on whether GFP or

Contractor furnished property (CFE). The maintenance plan will be IAW Government and civilian regulations.

15.5.4 Submit Property Status Report when equipment is considered to be deadline or inoperable. The deadline report shall identify the property as either: Contractor Acquired Government Owned (CAGO)

Property and Government Furnished Property (GFP). The report shall include:

Item Description

Model Number

Serial Number

GP Number (GFP)

Deadline Reason

Deadline Date

15.5.5 Government Furnished Property

NSN NOMENCLATURE UI QUANTITY PRICE

702501C147032 COMPUTER, OPTIPLEX 980 EA 1 $1417.69

702501C163795 COMPUTER, OPTIPLEX 980 EA 1 $1417.69

702101C145018 MONITOR, P2211H DELL EA 1 $389.00

702501C172587 MONITOR, P2211H DELL EA 1 $389.00

N/A DESKS EA 2 $1976.64

N/A CHAIRS EA 2 $802.70

Government Furnished Facilities

Location Name Sq Ft Utilities

Bagram Bldg. 55592-C (RPAT) 320 Provided

Item Description Serial/Service tag/Part/UDA

Number

QTY

Price

Laptop, Dell XFRDB30 CJQ7JH1 1 $1300

650 Mobile Reader, 123K with DB-9

Conn. 475006110052 1

Model 751 G HHI

27700600687

$2200

36000701562 $2200

36000701652 $2200

700 C Single Dock, 225-683-006 30350700539

$192

30350700531 $192

650 Mobile Reader, 123K with Intermec

Conn. 475006110062 1

$158

Battery Charger, 700 Color Single 852-

060-004 N/A 1

$185

Battery Pack SMR 751G-06 749 1 $38

Universal adapter Power Supply, 851-061-

103 601772 1

$66.99

Handheld Carry Case for HHI N/A 1 $72.00

Holster N/A 1 $72.00

USB Cable Adapter N/A 2 $138.0

Power Dec SMR 650 Charger N/A 2 $337.68

Model 675I RF Tag-For Training

5715943

5716878 $94.00

5716879

5715942

RFID Portable Deployment Kit(PDK)

TAVPDK 5201

TAVPDK5206 $49140.00

TAVPDK5295

16.0 Organizational Conflict of Interest

16.1 Business Integrity and Organizational Conflict of Interest. While not performing any inherently governmental functions, the contractor will be providing logistics and tracking services as well as reporting functions for cargo movement on the United States Transportation Command (TRANSCOM)

Universal Service Contract (USC). If the contractor were also a source for performing services under the USC contract, there is potential that the contractor would be unable to give unbiased, impartial advice to the Government because of its conflicting roles as the entity performing the cargo movement and the entity reporting on the performance of the cargo movement. Accordingly, this creates an

Impaired Objectivity Organizational Conflict of Interest (OCI) and award of this contract for Afghanistan and Pakistan logistics monitoring precludes the Contractor from submitting proposals in response to solicitations or working on other Government contracts, as either a prime contractor or sub-contractor, for procurements and/or contracts on which Contractor personnel are providing services under the

TRANSCOM USC contract. This restraint also applies to future contracts when employees have privileged information that may subject the Contractor to a conflict of interest. The Contractor's attention is directed to FAR Subpart 9.5 Organizational and Consultant Conflicts of Interest. The

Government will require, with proposals for this effort, a signed “Statement of Non-Compete" that the

Contractor, any subsidiary, joint venture or team member, or other affiliate does not currently, and shall not in the future, hold any Government contracts that create OCI issues under the contract from providing USC contract services. If during performance of the contract, the Contractor discovers additional actual or potential OCI with respect to the contract, the Contractor shall make an immediate and full disclosure in writing to the Contracting Officer. The disclosure shall include identification of the conflict, the manner in which it arose, and a description of the action the Contractor has taken or proposes to take to avoid, eliminate or neutralize the conflict.

17.0 Ethics Training

17.1 Prior to commencing contract performance, the Contractor shall require all employees to complete ethics training. Ethics training shall cover FAR 3.104, Procurement Integrity, personal and organizational conflicts-of-interest IAW FAR Subpart 9.5 and instruct contractor employees on identifying actual and potential OCI’s and proper use of government resources and non-disclosure of government information. Prior to commencing contract performance, the Contractor shall furnish to the

Contracting Officer, an Employee Ethics Training Report which shows evidence that each contractor employee has received Ethics Training. The report shall include a signed statement by each contractor employee whereby the employee agrees that he or she will not discuss, divulge or disclose any such information or data to any person or entity except those persons within the contractor’s organization directly concerned with the performance of the contract.

18.0 Confidentiality and Non-Disclosure of Information

18.1 Information made available to the Contractor by the Government for the performance or administration of this effort shall be used only for those purposes and shall not be used in any other way without the written agreement of the Contracting Officer. The Contractor shall protect the confidentiality of non-public Government information. Pursuant to FAR 9.505-4, which governs contractor’s obtaining access to proprietary information, the Contractor’s employees under this effort shall identify their access to proprietary information to other companies in accordance with FAR 9.505-

4(b). Procuring Contracting Officers may require disclosure of Contractor access to proprietary information in any solicitations resulting from services performed under this contract for logistics monitoring support services and execution of a nondisclosure agreement prior to the solicitation closing date. If such disclosure is required, the solicitation shall provide a Contractor Point of Contact (POC) from whom potential offerors may obtain nondisclosure agreements. The Contractor shall furnish copies of properly executed non-disclosure agreements to the Procuring Contracting Officer for the acquisition involved.

19.0 Synchronized Pre-Deployment Operational Tracker (SPOT)

19.1 SPOT has been designated as the Joint Enterprise contractor management and accountability system to provide a central source of contingency contractor information IAW DoDI 3020.41, Contractor

Personnel Authorized to Accompany the U.S. Armed Forces, dated 3 Oct 05. Contractor companies are required to maintain by name accountability within SPOT while government representatives utilize

SPOT for oversight of the contractors they deploy. Currently SPOT requires an Army Knowledge Online

(AKO) email and password for access. The website for SPOT is http://www.defenselink.mil/bta/products/spot.html. This website can be utilized to generate bar coded

Letters of Authorization (LOAs) as required by CENTCOM FRAGO 09-1451. Also see https://spot.altess.army.mil/privacy.aspx and https://www.us.army.mil/suite/kc/12559209.

20.0 Bagram (SPECIFIC) Requirements

20.1 The Contractor shall provide Non-Personal services in support of the 595

TBDE and subordinate units. These services shall include, but are not limited to: IBS-SUST/CMM, In Transit Visibility (ITV)

Reports, Truck Escorting Services, Logistics and Tracking, and Computer Operations.

20.2 Contractor employees working on Bagram Airfield must be OCN’s and are required to live on post

(per Bagram Base Policy). Lodging and meals will be provided for such employees and are not chargeable to the Contractor.

20.3 Contractor employees with Escort Badges must be stationed at Bagram.

20.4 Integrated Booking System (IBS)

20.4.1 Contractor will track and trace cargo from origin to the final destination and assist if there are any issues with documentation and including verifying information for any discrepancies.

20.4.2 Contractor will process and verify cargo shipping and customs documentation with customs officials and 595

TBDE Representative.

20.4.3 Customers may submit shipment requirements through automated systems or from customers via email or off line modes such as telephone and fax.

20.5 ITV Reports

20.5.1 The contractor shall provide ITV reports detailing cargo in-gating/out-gating, and cargo in-transit via Bagram Borders and check points including various locations on post.

http://www.defenselink.mil/bta/products/spot.html http://www.defenselink.mil/bta/products/spot.html https://www.us.army.mil/suite/kc/12559209

20.6 Truck Escort Services

20.6.1 The Contractor shall provide Truck Escort Services per 8 hour shifts, 7 days a week, the current requirement is two shifts but subject to change based on mission requirements. The contractor will add and/or reduce shifts based on the current mission within an official 30 day notice.

20.6.2 The Contractor shall provide three (3) escort vehicles and drivers for each shift. Vehicles and drivers shall be ready to perform escort duties at all times. Vehicles on post shall be maintained, checked, fueled, and ready to perform escort services.

20.6.3 The Contractor shall comply with all Force Protection requirements while on Bagram Airfield.

20.6.4 Escort Procedures

a. Personnel with escort privileges may escort up to 10 personnel.

b. A single vehicle escort is required for a single vehicle movement. For convoys of two to ten vehicles, a lead and a trail vehicle escort is required. One escort vehicle will be added for every five trucks after ten.

c. Escorts are responsible for the conduct and safety of the personnel they are escorting. Escorts must remain in close proximity and remain in constant view of the individuals they are escorting. Escorts will continuously monitor all escorted personnel and direct them during any Base security operations.

d. Failure to properly execute escort duties is considered a violation of FPSC Policy and escorts will have privileges revoked.

20.7 Logistics and Tracking

20.7.1 The Contractor shall provide logistics and tracking services for all cargo transiting Bagram

Airfield as well as outside Bagram Airfield.

20.7.2 All Logistics and Tracking requirements detailed elsewhere in this PWS are herein incorportated and required at Bagram.

20.7.3 Computer Operations

20.7.4 The Contractor shall have personnel stationed on Bagram Airfield that are properly vetted and have passed all security screenings to obtain ASCL Tokens for access to USG DataSystems (e.g. ETA

(SDDC), etc.).

20.8 Transporter Meetings

20.8.1 When requested by the COR/ACOR, the Contractor shall attend all meetings with transporters and

Afghan Government officials that occur off-base.

20.8.2 The Contractor shall meet with transporter representatives at the Bagram Gate(s) to pass off important customs/shipping documentation.

21.0 Deliverables

21.1 Reporting Format: The Contractor will submit all information and reports to the 595

TBDE using

Microsoft suites such as Word, Excel, Access, or Power Point. The Contractor must provide personnel capable of facilitating, coordinating, obtaining, and reporting critical movement control data and information from the appropriate USG personnel at multiple locations identified by the COR/PCO.

21.2 Report and Analysis Deliverables:The Contractor will provide the required reports listed in

Appendix B (the COR and Contractor will coordinate changes, additions and/or removals)

21.3 Additional Deliverables: In addition to the regular reports listed above, the 595

TBDE may require the Contractor to generate ad-hoc queries, charts, and reports. If no cost is associated, the COR and

Contractor will agree on the additional deliverables. If a cost is associatied, the Contracting Officer and

Contractor will agree on the additional deliverables

21.4 Hours of Operations: Work hours, including overtime, shall comply with Host Nation Labor Laws.

The Contractor will provide employee coverage to work 7 days per week, including US and Kuwaiti holidays.

22.0 Cyber Security

22.1 Handling and Protection of Non-Public Information

22.1.1 In performance of this contract, the contractor may have access to DOD information. The contractor agrees (a) to use and protect such information from unauthorized disclosure IAW Department of Defense (DOD) Instruction 8582.0 l: Security of Unclassified DOD Information on Non-DOD

Information Systems; (b) to use and disclose such information only for the purpose of performing this contract and to not use or disclose such information for any personal or commercial purpose; (c) to comply with other current Federal and DOD information protection and reporting requirements for specified categories of information (e.g., medical, proprietary, critical program information (CPI), personally identifiable information, export controlled); (d) to obtain permission of the Government

Requiring Activity before disclosing/discussing such information with a third party;(e) to return and/or electronically purge, upon Government request, any DOD information no longer required for contractor performance; and (f) to advise the Contracting Officer (CO) and/or Contracting Officer's Representative

(COR) of any unauthorized release of such information.

22.1.2 To provide adequate security, the contractor shall implement information systems security in its project, enterprise, or company-wide unclassified information technology system(s) that may have DOD information resident on or transiting through them. The information systems security program shall implement, at a minimum, the specified National Institute of Standards and Technology (NIST) Special

Publication (SP) 800-53 security controls identified in Appendix C.

22.2 Incident Handling

22.2.1 Reporting Requirements

22.1.1.1 The contractor shall provide an initial incident report to the Defense Cyber Crime Center (DC3) as soon as possible upon discovery of any suspected cyber intrusion events on the contractor's (or its subcontractors) unclassified information system(s) or network(s) where DOD information is resident or transiting. The initial incident report shall be provided even if some details are not yet available, with follow-on detailed reporting to DC3 within 72 hours. Reportable cyber intrusion events include the following:

a. A cyber intrusion event involving possible data exfiltration, manipulation or unauthorized disclosure of any DOD information resident on or transiting the contractor's (or its subcontractors') unclassified information systems or networks;

b. Intrusion activities that allow unauthorized access to the contractor's unclassified information system(s) or networks(s) on which DOD information is resident or transiting.

22.2.2 Incident Report Content

22.2.2.1 The incident report shall include, at a minimum, the following information:

a. Data Universal Numbering System (DUNS).

b. Contract numbers affected unless all contracts by the company are affected.

c. Facility CAGE code if the location of the event is different than the prime Contractor location.

d. Point of contact if different than the POC recorded in the System for Award Management

(address, position, telephone, email).

e. Contracting Officer Point of contact (address, position, telephone, email).

f. Contract clearance level.

g. Name of subcontractor and CAGE code if this was an incident on a subcontractor network.

h. DOD programs, platforms or systems involved.

i. Location(s) of compromise.

j. Date incident discovered.

k. Type of compromise (e.g., unauthorized access, inadvertent release, other).

l. Description of technical information compromised.

m. Any additional information relevant to the information compromise.

22.2.3 Incident Report Submission

22.2.3.1 The contractor will submit unclassified incident reports to DC3 via the Defense lndustrial Base

Network (DIBNet) Portal (http://dibnet.dod.mil).

22.2.4 Incident Response Coordination

22.2.4.1 In the event of an intrusion or potential intrusion, the contractor agrees to allow follow-on actions by the Government to further characterize and evaluate the suspect activity. The contractor acknowledges that damage assessments might be necessary to ascertain intruder methodology and identify systems compromised as a result of the intrusion. Contractor acknowledges that in certain cases a complete forensic analysis might be necessary to ascertain intruder methodology and identify systems compromised as a result of the intrusion. Once an intrusion is identified, the contractor agrees to take all reasonable and appropriate steps to preserve any and all evidence, information, data, logs, electronic files and similar type information (reference N IST Special Publication 800-61: Computer Security Incident

Handling Guide, (current version)) related to the intrusion for subsequent forensic analysis so that an accurate and complete damage assessment can be accomplished by the Government. The contractor is not required to maintain an organic forensic capability, but must ensure data is preserved (e.g. removing an affected system, while still powered on, from the network meets the intent of this requirement) and all actions documented until forensic analysis can be performed by the Government or mutually agreed upon third party (e.g., Federally Funded Research and Development Center (FFRDC), commercial security contractor, etc.). Any follow-on actions shall be coordinated with the contractor via the CCOR.

22.2.5 Information Sharing

22.2.5.1 The Government may use and disclose reported information (e.g., information regarding threats, vulnerabilities, incidents, or best practices) that does not include contractor attribution information at its discretion to assist entities in protecting information or information systems (e.g., threat information products, threat assessment reports); provided that such use or disclosure is otherwise authorized in accordance with applicable statutes, regulations, and policies.

22.2.6 Confidentiality and Non-Attribution Statement

22.2.6.1 The Government shall take reasonable steps, by controlled access and need-to-know procedures, to protect against public release of attribution information of the contractor. The Government may use and disclose reported information that includes attribution information only on a need-to-know basis to authorized persons for cyber security and related purposes (e.g. in support of forensic analysis, incident response, compromise or damage assessments, law enforcement, counter intelligence, threat reporting, and trend analysis). The Government may disclose attribution information to support contractors that are supporting the Government's cyber security and related activities if the support contractor is subject to legal confidentiality requirements that prevent any further use or disclosure of the attribution information.

The Government agrees to consider available exemption s of the Freedom of Information Act to protect against disclosure of attribution information of the contractor to unauthorized persons. Within a reasonable period necessary to perform an analysis after completion of the assessment, all contractor proprietary information or third party proprietary information in the possession of the Government as a result of the assessment will be destroyed unless other disposition is agreed upon in writing by the Parties or is required by law, Executive Order or regulation.

22.2.7 Law Enforcement/Counterintelligence

22.2.7.1 In the event of a known or potential intrusion, the contractor shall consent to responding counterintelligence or law enforcement investigative agency requests to apply forensic analysis tools to contractor information systems affected by the intrusion, including monitoring tools, imaging tools, and any other techniques that the agency seeks to apply to effectively analyze the intrusion. The contractor shall allow the responding counterintelligence and/or law enforcement investigative agency to image affected systems, including systems containing proprietary information. Nothing in this contract shall limit the ability to conduct law enforcement or counterintelligence activities, or other activities in the interest of the Government.

Appendix A: Performance Requirement Summary

PERFORMANCE

OBJECTIVE

PERFORMANCE

MEASURE

PERFORMANCE

STANDARD

LOT SIZE

DEDUCTION /

DIRECTED

ACTION

1. Cargo Movement

Report (Import)

The contractor will track and report the following import information (at a minimum):

- Container Numbers

- IBS TCNs

- Port Call File

Numbers

(PCFNs)

- Military TCNs

- Size / Conveyance

Types

- All Seal Numbers

- RFID Tag

Numbers

- Vessel Names

- Voyage Numbers

- Discharge Dates

- Dispatch Dates

- Border

Crossing Dates /

Names

- Destination Arrival

Dates

- Delivery Dates

- Truck Numbers

(all interchanges)

- Driver Names (all interchanges)

The exact format of the required reports, the necessary fields, will be provided by the COR NLT

10 days after contract award. All information must be submitted 7 days a week, 365 days a year. At a minimum, the contractor will be required to submit the below

98% of reports received within designated time frame.

Max allowable deviation is 12 hours 100% of the information is accurate

100%

Inspection

Re-performance on Contractor’s account.

Correction of any reporting errors will be at no further cost to the government.

operational reports:

- Daily Import

Report

(Pakistan)

- Containers in

Yard Report

- Northern

Distribution

Network Report

- Daily

Container

Movement

2. Cargo

Report

(Export)

The contractor will track and report the following export information (at a minimum):

- IBS TCNs

- Port Call File Numbers (PCFNs)

- Military TCNs

- Size / Conveyance Types

- All Seal Numbers

- RFID Tag Numbers

- Origins

- Border Crossing

Dates and Names

- Port Arrival Dates /

Names

- Vessel Names

- Voyage Numbers

- Sail Dates

- Truck Numbers

(all interchanges)

- Driver Names

(all interchanges)

The exact format of the required reports, the necessary fields, will be provided by the COR NLT 10 days after contract award. All information must be submitted 7 days a week, 365 days a year.

At a minimum, the contractor will be required to submit the below operational reports:

98% of reports received within designated time frame.

Max allowable deviation is 12 hours 100% of the informatio n is accurate

100%

Inspection

Re-performance on

Contractor’s account.

Correction of any reporting errors will be at no further cost to the government.

- Daily Export Report

- Containers in

Yard Report

- Northern

Distribution

Network Report

- Daily

Container

3. Seal

Operation

Report

Contractor shall monitor and report on a daily basis the number of containers with cable and bolt seals arriving and departing at the ports of Karachi and Qasim and at locations in

Pakistan. The report shall detail the container number and serial numbers of all affixed cable and bolt seals. The report shall also detail the number of containers arriving without cable and bolt seals. The report shall identify the serial numbers of all cable and bolt seals installed by the contractor.”.

98% of reports received within designated time frame.

Max allowable deviation is 12 hours 100% of the informatio n is accurate

100%

Inspection

Re-performance on Contractor’s account.

Correction of any reporting errors will be at no further cost to the government.

4. RFID/CIDD

Report.

On a daily basis, the contractor shall record the arrival of shipments with RFID Tags at the

Pakistan / Afghanistan entry nodes. The contractor shall conduct Hand Held Interrogator

(HHI) operations to capture all arrivals at each entry / exit node

(i.e. port terminals and border crossings).

98%…