GATES PWS_DRAFT.docx

Attachment 1

HTC711-25-Q-D023

PERFORMANCE WORK STATEMENT

FOR

MILITARY SURFACE DEPLOYMENT AND DISTRIBUTION COMMAND (SDDC)

GLOBAL AIR TRANSPORTATION EXECUTION SYSTEM (GATES)

Prepared by

HQ SDDC

OPERATIONS DIRECTORATE

25 November 2024

TABLE OF CONTENTS

1. DESCRIPTION OF SERVICES

1.1 Background

Global Air Transportation Execution System (GATES) Surface/Water is an automated information system that supports operational requirements for the Department of Defense (DoD). GATES serves as a single port management system providing cargo planning, in- transit visibility, vessel manifesting, customs clearance, cargo documentation, and sends payment data to SDDC G8 for cargo billing. SDDC requires functional support for GATES. This support will be provided to brigades, battalions, detachments, reserve units, active-duty units, and shippers to continue operations for the cargo transiting the Defense Transportation System (DTS).

1.2 SCOPE

1.2.1.

The purpose of this contract is to provide GATES support to G3 Functional Systems & Analysis by providing high- quality instructor for GATES course designated as per the syllabus and curriculum guidelines. Develop lesson plans, instructional material and assessments that align with course objectives. Maintain records of student attendance, grades, and other required documentation. Provide technical support for hardware, software and network issues. Install configure and maintain IT equipment and software. Provide training and resource to users for effective use of IT GATES systems.

1.2.2.

The Contractor is responsible for performing all tasks outlined in this Performance Work Statement (PWS) and gathering all relevant information. Estimates and timelines for the Contractor's work shall be based on the specified due dates for deliverables in Paragraph 1.4. The Contractor shall coordinate with the Government to ensure that all activities are well management efforts of the G3 Directorate. All reports, studies, and other deliverables identified in the PWS shall be prepared and submitted to the Government.

Task Area 1: Contract-Level Management Task Area 2: Functional Support Task Area 3: Training Support

1.3 Specific Tasks.

1.3.1 Task Area 1: Contract Level Management.

This task involves the functional activities related to the administration and management of this project. The contractor is responsible for overseeing the tasks performed by their personnel under this contract. They must designate a main point of contact for the Government regarding technical and functional issues. These functions include providing administrative support by preparing documents such as briefings, point papers, and meeting minutes that pertain to the progress of this contract.

1.3.1.1 Task 1 Subtask 1: Task Order Management Plan (TOMP).

The contractor is required to develop an integrated Project Plan that encompasses both Government and contractor perspectives. This plan shall outline the tasks, resources, and dependencies identified. The Management Plan must cover the technical and functional approach, organizational resources, and management controls for cost, performance, and schedule requirements throughout the contract execution. The contractor shall submit a Draft Plan within ten (10) business days after contract award. The Government will review the plan and provide feedback to the contractor. The contractor shall then submit the Final Plan no later than fifteen (15) business days after receiving the Government's comments. It is important that the plan does not simply restate the requirements outlined in the Performance Work Statement.

1.3.1.2 Task 1 Subtask 2: Monthly Status Report (MSR).

The contractor shall submit a Monthly Status Report that monitors quality assurance and configuration management. This report shall detail the accomplishments for the reporting period, categorized by each active task or project area. The MSR shall provide an overview of the current funding status for travel and Other Direct Costs (ODCs), as well as a summary of completed efforts, delivered items, and conferences or trips attended during the reporting period. Additionally, it shall include an overall evaluation of the progress made thus far. The report shall include estimated and actual travel costs, along with the contractor's name, trip location and purpose, and dates of travel. The report shall highlight any deliverables for each task and identify any issues, problem areas, or items that require action from the Government. The contractor shall submit the MSR no later than the fifth business day of each month, electronically emailed to the COR.

The Contractor shall promptly notify the Contracting Officer Representative (COR) of any problems or failures that may affect performance. The COR may issue a Contract Discrepancy Report (CDR) when the Contractor fails to meet the terms and conditions of the contract. When issued, the Contractor shall provide the COR with a written plan of corrective action, including a proposed timeline, within 5 business days of receipt. This plan shall describe proposed Contractor actions to correct the problem or deficiency and bring performance back in compliance with identified performance standards.

1.3.2. Task Area 2: Functional Support

1.3.2.1 Task 2 Subtask 1: Software Test Plans:

The contractor is responsible for preparing and providing the Government with a comprehensive Software Test Plan that supports the testing requirements for Customer Acceptance Testing (CAT) for GATES, Independent Verification and Validation (IV&V) and regression testing. This Software Test Plan shall serve as a guide for testers throughout the entire software application process, using scenario-based examples that assume the tester to be a typical end user. Additionally, the contractor shall develop scenarios that thoroughly test the specified platforms and systems. These scenarios should be linked to standard datasets that include representative cargo records with known data format and content flaws, in order to simulate real-world data. The contractor shall utilize data from SDDC's critical interfaces, such as the Integrated Booking System (IBS), Transportation Financial Management System (TFMS), Transportation Coordinator's- Automated Information For Movement System (TC AIMS II), Integrated Computerized Deployment System (ICODES), Integrated Surface Distribution Data Cleansing Tool (iSDDC), Deployment Support System II (MDSS II), Munitions Transportation Management System (MTMS), Army War Reserve Deployment System (AWARDS), Distribution Standard System (DSS), and others as determined by G3. Scenarios shall be standardized and categorized according to functional areas. GATES test scenarios shall include testing with Hawkeye, VSATs, CAISI wireless, and other communication devices used during D- GATES operations. The Software Test Plans shall support the requirements for testing corrections to Emergency or Urgent Problem Reports submitted by field users. The contractor shall provide the Draft Software Test Plan no later than four weeks before the start of the test. The contractor shall provide the Final Software Test Plan no later than two weeks before the test begins. Typically, testing events will simulate production events and processes using production-like data. Any modifications to previously created plans shall be made to accommodate functional changes and additions addressed in the software change package. Any discrepancies should be brought to the attention of the Contracting Officer's Representative (COR) for resolution. Support should be accomplished as a release is performed.

1.3.2.2 Task 2 Subtask 2 – Test Support.

The contractor is responsible for ensuring that the software meets functional requirements and shall provide a Software Test Report within five (5) business days after completing the testing. The contractor will perform various GATES roles to properly test functionally during software testing. Additionally, the contractor shall conduct regression testing to ensure any code changes do not negatively impact other related processes. The contractor shall follow the developer's guidance for testing any processes that are dependent on the software. Any problems or issues that arise shall be documented in the Daily Update Report, which shall be submitted electronically to the COR from Monday to Friday by COB. These problems/issues will be discussed during the weekly GATES meeting with Government representatives throughout the system testing cycle. Support for this task may vary, depending on sprint schedule.

1.3.2.3 Task 2 Subtask 3 – Prepare GATES Briefings and Documentation.

The contractor is responsible for creating PowerPoint slides for GATES briefings, as well as informational documents related to SDDC Movement Orders & Shipping Processes/Systems Division issues, system upgrades, changes, and general transportation information. All documents will be reviewed and approved by the Government. The contractor shall provide updated documentation and briefings whenever there are new versions or revisions of GATES. These updates shall be implemented within five (5) business days after their release. The documentation should be formatted according to SDDC standards and templates.

1.3.2.4 Task 2 Subtask 4- Service tickets.

The contractor must ensure that personnel are available during the designated core period, which is from 0700 to 1730 hours Central Time, Monday to Friday, to provide customer support for GATES. The contractor is required to address any trouble tickets generated from Service Now that are assigned to the G33. Any problems, issues, questions, account concerns, training needs, that are reported to the GATES SRC helpdesk will be documented with a service ticket in Service Now and resolved. The contractor shall oversee all service tickets up to and including Tier II level. It is the contractor's responsibility to determine whether the problem is a functional or technical issue, related to hardware or software, isolated or systemic, and route it accordingly. Contractor shall respond to all helpdesk tickets within 24 hours, unless the service ticket is generated over the weekend or on a holiday, in which case the response should be provided on the next business day. All responses to service tickets will be recorded in Service Now, which is maintained by G6 for reference and informational purposes. It is worth noting that historical data indicates an average of approximately 85-100 service tickets per month for GATES. However, the workload may vary in the future depending on deployments and exercises, which could affect the number of calls received. The contractor shall provide GATES level 3 system support through Service Now for all functional service ticket requirements.

1.3.3 Task Area 3: Training Support

1.3.3.1 Task 3 Subtask 1 - Training/Virtual Training/CBT/In-person.

The contractor shall provide the GATES community with classroom instructions that maybe in person or virtual. Virtual training must be provided on government approved systems such as (Teams, Video Teleconferencing, and VTC). The training must be accomplished using the Continuous Learning Environment (CLE). The contractor shall be responsible for creating training agenda, and applicable training materials to include, but not limited to handouts. The contractor must have all training material approved by government prior to use in the classroom setting. The contractor must provide an After-Action Report (AAR) electronically with the following details: participants, training summary, observations, and any recommendations within 5 days from the completion date of training. Any issues or concerns with the GATES system will be captured and included in the report. Training shall be IAW Department of the Army Training and Doctrine Command, TRADOC Regulation 350-70 and TRADOC Pamphlet 525-8-2. A minimum of one (1) person working this contract, is expected to be proficient, from end to end, in training students in any type of environment (in person and/or virtual). Training may consist of GATES functional training, basic transportation knowledge and limited IBS knowledge. The Contractor shall provide a training facility that can accommodate up to ten (10) students, three (3) instructors, and all necessary GATES training equipment. The training environment must be conducive to learning and should have computer style desks that will accommodate 2 students at each desk, chairs, a small conference table, projector or television monitor’s that can be used for display/projection purposes, and other necessary training needs. This facility should be in the same location that the equipment is maintained and should be within 10 miles of Scott AFB.

1.3.3.2 Task 3 Subtask 2 - Continuous Learning Environment (CLE) The CLE offers a comprehensive web-based proficiency database and capability for the global aerial port and surface terminal community. The contractor will update the Program of Instruction (POI) for GATES based on guidance from G3, as necessary.

1.3.3.3 Task 3 Subtask 3 – Training Programs

The contractor shall teach a Handheld Terminal Course (HHT). This training will cover both functional and technical aspects of the hand held device, directed to the technical (S6) audience as well as functional capabilities directed to the functional (S3) audience. The contractor will simulate real port operations by using visual cargo aids and Military Shipment Labels (MSL). The instructor will provide a 4-day, 8-hour training course that guides students through out of the box device setup and configuration for the technical training. The instructor will provide guidance on the use of the scanners, to include file transfer and port operation steps on how to process cargo, using various methods.

The HHT course will be a Mobile Training Team at CONUS and OCONUS locations. The course will be 4-6 times per fiscal year. The contractor shall maintain and update all classroom materials for HHT course. The contractor shall assist with troubleshooting HHTs during classroom instruction, in conjunction with G6 Technical Managers.

The contractor must provide an After-Action Report (AAR) electronically with the following details: participants, training summary, observations, and any recommendations within 5 days from the completion date of training. Any issues or concerns with the GGT system will be captured and included in the report.

1.3.3.4 Task 3 Subtask 4 – Training/Exercise Support

The contractor shall support training / exercises, including, but not limited, to MRX, EDRE, JRE, SEDRE, and training/fielding exercises. The contractor must transport, set-up, and maintain required equipment during MRXs, MTTs, and all other applicable missions. The contractor will support and provide input to scenarios as necessary and simulate cargo port operations. The contractor must be available to provide continued support throughout the entire training/ exercise; this could fall outside of SDDC core hours, over holidays and/or weekends. Below is an estimated data summary of previous exercises, however required support, rotational schedules of units and real-world events may impact the amount and timing of future needs. The contractor must provide an After-Action Report (AAR) electronically with the following details: participants, training summary, scenarios completed, observations, outcome and any recommendations within 5 days from the completion date of training. Any issues or concerns with the GGT system will be captured and included in the report.

Estimated Historical Data

(approximate)

Training/Fielding (non-local)

Up to 18 yearly

5 days each

Note that training locations include CONUS and OCONUS

1.3.3.5 Task 3 Subtask 5- GATES Training Kits

The GATES training kits may be utilized during classroom instruction or for exercise support. The contractor shall ensure that all GATES equipment is functioning, updated, maintained, and stored at the contractor facility within 10 miles of SAFB. The contractor shall provide a secure and controlled area to the store GATES equipment. The contractor shall ensure that all GATES equipment remains in online status. The contractor shall be responsible for proper transportation of GATES equipment to and from all training locations and exercise. The contractor shall maintain accountability of equipment while TDY. It is the responsibility of the contractor to maintain, image, and configure all devices associated with the GATES equipment. This includes supporting WAN connections and internet connectivity, as well as configuring wireless technology for wireless LAN. The contractor shall possess knowledge of the OSI model protocol and its relevance to network and systems troubleshooting. Additionally, they may be required to travel to exercise locations at the request of the COR to provide training and support for offsite missions. The contractor shall perform both local and remote troubleshooting of end-user problems and requests. This includes conducting regular maintenance tasks, such as vulnerability patching, hardware/software updates, and workstation and peripheral replacements. The contractor must be proficient in lifecycle maintenance, operations and maintenance (O&M), backup and recovery procedures, a maintaining the MESA 2 devices. Furthermore, the contractor shall establish necessary accounts in GATES for end users. Upon completion of missions, the contractor shall receive the returned equipment and conduct inventory checks. If necessary, they shall be responsible for repairing any damaged equipment. Additionally, the contractor shall provide support for trouble tickets as required.

1.3.3.6 Task 3, Subtask 6 - GATES Computer Based Training (CBT) Development, Upkeep and Maintenance Contractor shall develop, update and maintain all Computer Based Training Modules. Modules will consist of different levels of GATES training, to include but not limited to Shipper, Central Site, RGATES, DGATES and HHT’s.

Modules will be developed/updated/maintained using the POI’s with a minimum requirement of 4.0 hours of instruction for the Shipper and Central training at the request of G3. CBT instruction for Remote (RGATES), shall be developed/updated/maintained using the POI’s with a minimum of 6 hours of instruction. DGATES, GEMS and HHT CBT’s will be a minimum of 4 hours of instruction and will be based on the POI’s

1.3.3.7 Task 3 Subtask 7 – Hardware/Software Maintenance of Gates Equipment (Located at Beaumont) SDDC utilizes a series of GFE computers and peripherals (printer, scanners, etc.) for training and exercises. The Contractor shall be responsible for the maintenance, imaging and configuration of all devices associated to the GATES kits, supporting WAN connections and internet connectivity, supporting wireless technology configurations in support of wireless LAN, working with the OSI model protocol and how they pertain to network and systems trouble shooting, traveling to exercise locations at the request of the COR to support training and offsite missions. Performing local and remote troubleshooting of end of user problems and requests, provide touch maintenance to include vulnerability patching, hardware/software updates and replacement of workstations and peripherals, lifecycle maintenance, O&M, backup and recovery, imaging laptops, monitoring system performance and capacity, imaging and maintaining the MESA 2 HHT handheld device (or current model) baseline for all MESA’s, establish necessary accounts in GATES for end users. Upon completion of missions, receive the returned equipment, inventory and repair if necessary. Provide support to trouble tickets as necessary.

1.4 DELIVERABLES

1.4.1 Deliverables

Reports, documents, and narrative type deliverables will be accepted when all discrepancies, errors, or other deficiencies identified in writing by the Government have been corrected. For the initial (draft) deliverables required by this PWS, the following procedures will apply:

The Government will provide written acceptance, comments, and/or change requests, if any, within five calendar days from receipt by the Government of the initial deliverable.

Once the Government's comments are received, the contractor will have ten calendar days to incorporate the comments and/or change requests and submit the final version of the deliverable, unless otherwise specified in the PWS task.

It is essential that all deliverables adhere to professional standards and fulfill the requirements outlined in the contractual documentation. Unless otherwise specified, the contractor should provide all deliverables electronically to the COR in Microsoft Office formats, following the schedule provided. Each deliverable should be clearly identified by the contract number, PWS subtask, and deliverable title.

The contractor is required to provide data and software, along with their respective data rights, as specified in the tables below. In accordance with the Defense Federal Acquisition Regulation Supplement (DFARS) 252.227-7013 and DFARS 252.227- 7014, the Government will have "unlimited rights" to all non-commercial computer software, software source code, computer software documentation, enhancements, technical data, and similar non-commercial data that are developed exclusively at Government expense and delivered under this contract. "Unlimited rights" means that the Government has the rights to use, modify, reproduce, release, perform, display, disclose, or authorize others to do so, in whole or in part, for any purpose whatsoever. The contractor must ensure that all data/software provided during the contract performance is marked in accordance with the requirements stated in DFARS 252.227-7013, 252.227-7014, or other applicable references, regardless of how it is developed or modified.

For any non-commercial data provided under this agreement, the Government possesses the authority to utilize, alter, replicate, distribute, exhibit, or divulge, either in its entirety or partially, in any manner and for any purpose whatsoever. Furthermore, the Government reserves the right to grant permission to others for the same.

2.0 SERVICE DELIVERY SUMMARY

The Services Delivery Summary (SDS) represents the most important contract objectives that, when met, will ensure that contract performance is satisfactory. Although not all PWS requirements are listed in the SDS, the contractor is fully expected to comply with all the requirements in the PWS.

The Government shall provide as GFI all necessary information required to perform this PWS. GFI includes Interface Design Documents (IDDs) for Critical Interface Partners, Software Requirement Specification (SRSs), User manuals, Baseline Change Request (BCR), Systems Change Request (SCR), System Problem Reports (SPR). The Government shall provide access to Collaborative Lifecycle Management (CLM) for access to all future GFI. The point of contact for GFI will be the COR.

3.2 Government-Furnished Equipment (GFE)

The government shall provide computer terminals, office space, telephone/service, desks, chairs, writing paper, pens, pencils, computer disks, scissors, paper, staplers, and staples for contractor employees performing in government facilities. The Government shall provide specialized equipment to be used exclusively for the performance of work under this PWS, including scanners, docking stations, and bar code printers.

If there is a requirement to call overseas, the contractor shall call SAFB and utilize the SAFB operator to call overseas.

All GFE will be maintained IAW FAR 52.245-1, Government Property, and Army Regulation 25-2, Para 4.5.

3.3 Joint Inventory

The contractor and the COR(s) shall inspect and inventory GFE within 30 calendar days of the start of the phase-in period and ten calendar days prior to the end of the phase-in period/final performance period. The inspection and inventory shall detail the material condition and quantity of such GFE and determine the exact number, location and serviceability of GFE. The contractor shall certify the GFE inspections and inventories, assume responsibility for all GFE, and subsequently report any discrepancies to the COR. GFE shall not be altered without prior written approval of the COR. The contractor shall notify the Contracting Officer in writing of any disagreement regarding the material condition of GFE within five (5) days of completion of an inspection or inventory. The contractor will inspect and inventory the GFE anytime an employee resigns or is terminated from the contract.

3.4 Annual Inventory

The contractor shall also perform an annual inspection and inventory of GFE. These actions shall be conducted during the anniversary month of the initial joint inspection and inventory. The contractor shall submit a report to the COR within ten workdays of the date they are completed. The report shall indicate the shortage, loss or destruction of GFE, and the damage and excessive wear and tear

3.5 Return of GFE

The contractor may, at any time, return GFE it no longer needs for the performance of this PWS; however, returned GFE will not be replaced by the Government, and the unavailability or lack of GFE under these circumstances will not excuse nonperformance, or justify increase in cost to the Government. The contractor shall notify the Government in writing of its intent to return GFE.

3.6 Repair vs. Replacement

GFE shall not be replaced if it can be repaired or rebuilt, to return it to the condition that existed at the time the contractor accepted it. The contractor shall provide the COR with a comparison between the replacement cost of the equipment and the cost of parts required to repair the equipment. If the repair estimate exceeds 50% of the replacement cost, the contractor shall contact the Contracting Officer for approval to replace the item. The COR will closely monitor repair and replacement of GFE.

Any item replaced rather than repaired becomes the property of the Government. Any replacement item shall meet the same performance criteria and quality standards as the original item or better.

3.7 Warranties

The Government will furnish warranty information on all GFE. All GFE under manufacturer warranty shall be operated, maintained, and repaired in accordance with this. The contractor shall report to the COR any difficulties encountered in exercising manufacturers’ warranties. The contractor shall not repair GFE under warranty without COR approval. Repair and replacement of non-GFE is the sole responsibility and expense of the contractor.

3.8 Disposal, Salvage, Reclamation, and Recycling

The contractor shall contact the COR to initiate disposal, salvage, reclamation, or recycling of GFE.

3.9 Equipment Manuals

The Government will provide access to all available equipment manuals for the equipment listed in 3.1. Manuals will be located in appropriate facilities where equipment is used. The contractor shall maintain and update equipment manuals (when received from the manufacturer).

The contractors will require access to SAFB to comply with GFE/identification requirements and potential meetings. The place of performance for the contractors should be within a 10-mile radius of SAFB, and at the same facility as the training location and GATES equipment is maintained. Contractor employees not working in the direct commuting area will be at a place designated/agreed upon by the COR and will provide required connectivity to Government resources to support the PWS requirement.

All contractor employees must be able to dial into government- sponsored teleconferences. Other than GFE specified, the contractor shall provide space, equipment, and resources needed to successfully execute this contract when contractors are not located at Scott AFB. The Scott AFB off site location shall be approved in writing by the COR.

The contractor’s facility shall also be used for meetings and training directly relating to the contract and services covered under the contract. Position(s) at Beaumont, Texas shall support computer operations and maintenance and will travel to SAFB and other locations as needed/requested by COR. This support requires access to the Ft Hood network which can only be established as an employee at Ft. Hood. Employee(s) may be required to travel to various locations to support training exercise when the GATES communication kit will be utilized. For Beaumont location only, the contractor(s) shall not work remotely. This position will require a Secret clearance with the ability to gain a Top Secret.

Telework/remote work policy is subject to change as/if SDDC publishes new information regarding telework/remote work policies.

4.2 Period of Performance

All work under this contract to include submission of all deliverables shall be completed within the one-year base period, and four twelve-month option period.

Transition Period : 1 Sep 2025- 30 Sep 2025 Base Period: 1 Oct 2025- 30 Sept 2026 Option Period 1: 1 Oct 2026– 30 Sept 2027 Option Period 2: 1 Oct 2027– 30 Sept 2028 Option Period 3: 1 Oct 2028– 30 Sept 2029 Option Period 4: 1 Oct 2029– 30 Sept 2030

4.2.1. Hours of Operation and Recognized Holidays

The contractor shall provide support during SDDC core hours between 0700-1630 hours’ central time, Monday through Friday, excluding Federal Government holidays. Contract support hours are subject to change due to increased requirements for operations outside the normal workday, and contractors may be required to provide support outside normal business hours based on operational requirements and/or training/exercise support. The following will be observed as Federal Government holidays: New Year's Day, Martin Luther King's Birthday, President's Day, Memorial Day, Juneteenth, Independence Day, Labor Day, Columbus Day, Veteran's Day, Thanksgiving Day, and Christmas Day. Note: Any of the above holidays falling on a Saturday shall be observed on the preceding Friday. Holidays falling on a Sunday shall be observed on the following Monday.

4.3 Travel

Performance under this task order may require contractor travel within and outside the Continental United States, as required by SDDC G3. The Government will reimburse the contractor for travel expenses subject to Federal Acquisition Regulation 31.205-46, Travel Costs and Joint Travel Regulation. The Government will not pay profit on travel. All travel arrangements for contractors must be coordinated and approved by the primary or alternate COR before any travel expenses are incurred. The contractor must supply sufficient notice of personnel who will be traveling in order to secure the most economical rates for airfare, rental car, and lodging. Unless mission requirements dictate otherwise, a minimum of five (5) business days' advance notice from the travel commencement date is required for long-distance travel. The travel request must be sent in writing and include the dates, location, and estimated travel costs. The contractor must supply supporting documentation, such as invoices and receipts, for all travel reimbursement requests. Actual travel expenses must be reported to the COR within five (5) business days of completing the travel, specifying costs by person and by trip. The contractor will not be reimbursed for local travel and related expenses for daily commuting to and from Scott Air Force Base, IL (SAFB) or the contractor's facility. If the contractor chooses to utilize remote labor, travel to and from SAFB will not be eligible for reimbursement. It is the contractor's responsibility to monitor the status of travel funds and promptly notify the COR when funds fall below 85% of the established not-to-exceed amount stated in the contract.

4.4 Other Direct Costs (ODCs)

Before incurring any costs, the contractor must coordinate the use of ODC (Other Direct Costs) funds with the COR (Contracting Officer's Representative). The government will reimburse the contractor for materials and fees that are necessary for the performance of the PWS (Performance Work Statement), but only if they have been previously coordinated with the COR. ODCs may include various expenses such as copier fees, reproduction and printing costs, duplication and scanning expenses, binding supplies, electronic media like tapes and CDs, postage and shipping charges, TDY (Temporary Duty) meeting facility charges, TDY conference fees, items related to the GATES training kit, and other relevant expenses. The contractor must submit written ODC requests to the COR for approval at least five business days before incurring any expenses. These requests should include estimated costs supported by a minimum of three competitive quotes. All ODC reimbursement requests must be accompanied by contractor invoices and the associated receipts. It is important to note that the contractor is not authorized to purchase ODCs that exceed the amount of ODC funding specified in the contract. The contractor is responsible for monitoring the status of ODC funds and must notify the COR when the funds fall below 85% of the established not-to-exceed amount stated in the contract

4.5 Contract Manager

The contractor shall provide a Contract Manager who shall be responsible for the performance of the work in the PWS. The name of the Contract Manager and alternate(s), who shall act on behalf of the Contractor when the Contract Manager is absent, shall be designated in writing to the Contracting Officer (CO) or (KO). The contractor shall ensure all personnel assigned to this task order meet the minimum requirements specified in the contractor’s proposal. The contractor shall notify the CO in writing of any changes to personnel within three (3) business days after information is known.

4.5.1 Other Positions within/on Contract

The contractor is required to provide a highly skilled staff proficient in GATES Surface/Water operations, as well as knowledgeable in surface transportation and transportation systems, including IBS and DTR regulations. It is necessary for at least two employees to possess expertise, skills, and a proven track record in training employees on executable systems. Contract employees will be responsible for carrying out their duties with minimal to no supervision from the Government COR and other staff members, as they may be on temporary duty or have other pressing priorities. It is expected that contract employees will promptly address and resolve service tickets and user inquiries, with limited involvement from government personnel. They should be capable of performing GATES duties at a Tier II functional level from the commencement of the contract once they have received their credentials and been granted system access.

4.6 Contractor Furnished Equipment and Services

Except for those items or services specifically stated in PWS Section 3.2 as Government- furnished the contractor shall furnish all resources necessary to perform this contract.

4.7 Information Assurance Workforce Improvement Program (IAWIP) DoD 8570.01-M, IAWIP, requires the contractor personnel performing IA functions, on either a full or a part-time basis, to receive a commercial certification. Information Assurance Contractor Training and Certification describes which functions require a particular level of certification. Contractor personnel assigned to those functions must achieve the appropriate certification as specified in DoD 8570.01-M, IAWIP, prior to task order award. (See Appendix 3) Personnel in IA positions must sign a "Statement of Acceptance and Responsibilities." Additionally, contractor personnel performing IA functions must take appropriate actions to complete continuing education and re-certification requirements applicable to their certification. The contractor shall have their personnel properly certified at all times after task order start, unless a waiver has been granted.

Contractor personnel holding an IA certification must release their certification information to the DoD by registering their certification in the Defense Workforce Certification Application (DWCA): https://www.dmdc.osd.mil/appj/dwc/index.jsp The contractor shall complete an on-the-job skills practical evaluation for their personnel in Information Assurance Technical (IAT) positions and provide supporting documentation indicating completion to the CO or designee. After completion of the evaluation and verification of certification, personnel will be issued an appointment letter for the performance of IA duties including a statement of responsibilities.

In addition to the baseline IA certification requirement for their level, the contractor shall ensure that personnel in IAT positions with privileged access possess the appropriate Computing Environment (CE) certification for the operating system or security related tools/devices they support and provide supporting documentation indicating possession of the CE certification to the CO or designee.

4.8 Non-Disclosure Statements

In performance of this contract, the Contractor shall have access to sensitive, non- public information. The contractor agrees (a) to use and protect such information from unauthorized disclosure IAW DTM 08-027 - Security of Unclassified DOD Information on Non- DOD Information Systems, 31 July 2009; (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 obtain permission of the Government before disclosing/discussing such information with a third party; (d) to return and/or electronically purge, upon Government request, any non-public, sensitive information no longer require for contractor performance; and (e) to advise the Government of any unauthorized release of such information. Upon request, the contractor shall have its employees assigned to this contract execute a non-disclosure agreement for delivery to the Government. The Government will require contractor personnel to sign a non- disclosure statement to protect non-public information of other contractors and/or the Government.

See Appendix 2, Non-Disclosure Agreement.

4.9 Quality Assurance

The contractor shall support Government agency reviews and audits of all services and support provided under this PWS. The contractor shall be prepared to support Quality Assurance reviews conducted by the Government. The Government reserves the right to authorize an independent verification and validation of the contractor’s procedures, methods, data, equipment, and other services provided at any time during the performance of this PWS.

1. The contractor is directly responsible for the safety and occupational health (SOH) standards for its employees and must comply with The Occupational Safety and Health Act of 1970; or any other applicable Federal, State, and local laws, codes, ordinances, and regulations.

2. The contractor shall provide and maintain work environments and procedures which will safeguard the public and Government personnel, property, materials, supplies, and equipment exposed to Contractor operations and activities.

3. The contractor shall provide prevention plans and accident investigation procedures upon request from the COR within seven days.

The daily work associated with this PWS is at the SECRET level. All classified material handled by the contract members will be safeguarded and derivatively classified IAW Executive Order (EO) 13526 and per Army Regulation 380-5 (Information Security Regulation) and all applicable Office of the Secretary of Defense (OSD) Classification Guides. Specific security requirements are identified in the DD Form 254, DOD Contract Security Classification Specification. A completed/signed DD Form 254 is attached to the contract.

5.2 Citizenship and Clearance Requirements

The contractor’s, subcontractors, and/or partner’s personnel performing services under this requirement shall be citizens of the United States of America. Overall, contractor personnel should possess the appropriate personnel security investigation for the position(s) occupied. Contractor personnel shall have to have a background investigation that corresponds with the sensitivity level of the tasks to be performed.

5.3 Personnel (Clearance (PCL)/Investigation Requirements.

Personnel working on this contract will require a favorably T3 investigation, or a National Agency Check Local Credit (NACLC), resulting in SECRET eligibility when adjudicated by the Department of Defense Consolidated Adjudication Services (DoD CAS). Interim Secret clearance eligibility is accepted provided it was granted by DoD CAS and the Defense Counterintelligence (DCSA) has opened the investigation. The Facility Security Officer (FSO) handles ensuring the T3 investigations are submitted to DoD CAS and a minimum of Interim SECRET granted prior to contract start day.

5.3.1 Out-processing of Contractors with CACs:

Upon termination or completion of this contract, the contractor employee will surrender all Government supplies, materials, classified material and equipment to the COR.

In addition, the contractors’ CACs and any security badges issued will be turned into the SDDC/USTRANSCOM Protection Service Center (PSC) at SAFB, IL. Off-site contractors will return the CAC to the COR. This will be accomplished on the last day of the contract or upon any termination/reassignment of a contract employee. CORs who obtain CAC and security badges due to short notice terminations or release of contract employees will revoke access in the Mission Partner Identity, Credential and Access Management (MP ICAM) (formerly TASS) and turn the CAC and security badge to the G2 Security Office for final processing/ out-processing. All on-site contract personnel will complete an in/out-processing checklist supplied by the COR/CO.

5.3.2 Passport

Company personnel supporting Government overseas shall obtain and support any applicable/required visa’s/passport’s and shall comply with in country laws and regulations for entry/exit.

5.4 Base Access.

Contractor employees must comply with base access and control procedures.

5.5 Facilities Clearance Level (FCL)

The company who is awarded this contract must have a valid FCL at SECRET. This requirement includes any subcontract companies assigned to personnel working on Task Area 3 of this contract. Interim Secret FCL is acceptable provided it has not expired prior to final adjudication by DCSA. FCL procedures and security guidelines for adjudicative requirements are outlined in 32 CFR Part 117 (NISPOM), DODM 5200.02 and AR 380-67. FCL is required upon the contract’s start date.

5.6 Personnel and Facilities Clearance Validation

Upon contract task order award, the contactor shall submit all names and social security numbers of all contract employees supporting this contract will be submitted to SDDC G2 for vetting in Defense Information System for Security (DISS) to ensure investigative requirements have been obtained before contract start date. This requirement will be completed prior to the COR/Mission Partner Affiliation Sponsor (MPAS) (formerly Trusted Agent-TA) submitting contract employees for their CAC in the Mission Partner Identity, Credential and Access Management (MP ICAM) (formerly TASS). If a contract member does not have the appropriate investigative requirement, the contract employee will be denied the ability to work in support of this task order and the employee’s information will not be loaded into MP ICAM.

5.6.1 Prior to performance start date, permanently assigned contractor employees on Scott AFB (SAFB) will require electronic DISS visit requests submitted to Security Management Office (SMO) Code: SDDC-CONT and USTC-CONT-USTC- CONT-1, POC block is the contract number and phone number block will include…