201216 Draft GATES PWS.pdf

PERFORMANCE WORK STATEMENT

FOR

UNITED STATES TRANSPORTATION COMMAND

(USTRANSCOM)

MILITARY SURFACE DEPLOYMENT AND

DISTRIBUTION COMMAND (SDDC)

SDDC SYSTEMS FUNCTIONAL SUPPORT

Prepared by

MILITARY SURFACE DEPLOYMENT AND DISTRIBUTION

COMMAND (SDDC)

TRANSPORTATION PROGRAMS POLICIES AND SYSTEMS

DIRECTORATE

16 Dec 2020

1 DESCRIPTION OF SERVICES

1.1 Background.

The Military Surface Deployment and Distribution Command (SDDC) Global Air Transportation Execution System (GATES), is an automated information system designed to support the operational requirements of the Department of Defense (DoD) for obligating, tracking, documenting, and payment of DoD cargo. SDDC requires functional support for GATES-Surface/Water, for its battalions, detachments, reserve and active units and shippers to continue operations when necessary, for cargo transiting the DTS (Defense Transportation System).

1.2 SCOPE.

1.2.1.

The purpose of the contract is to provide GATES-Surface/Water support as required by the functional management office for the SDDC portion of GATES. The requirement is to provide support for SDDC G3 Systems Branch, system functional training, testing, and support to include, but not limited to; responding to functional questions/assistance related to GATES-Surface/Water, performing actions to facilitate the resolution of Customer issues (CONUS/OCONUS), to include, providing instructions/clarification to the customer to perform problem resolution at their location. This requirement includes site visits to shipper locations (worldwide), active duty and reserve units for training assistance, in person, virtual or computer based training for GATES users worldwide, G3 systems functional manager with system customer testing and acceptance of releases, and briefing of GATES and related transportation information. Requirements will also include design, development, implementation, and maintenance of a complete training package, in support of computer based training (CBT), virtual and in person, which will be provided to anyone in need of GATES training, as approved by the G3. This package/course will take the place of what is currently being offered at the Transportation School (T-school), Ft Eustis Va. (As of 8/2021, they will no longer offer GATES). Contract will also cover administration and upkeep of hardware and software updates to the GATES training kits and all peripherals. GATES is fielded worldwide in support of military operations, reserve training and readiness for an estimated 2,500-account/user base. Currently SDDC has 28 terminals located worldwide that we lend support to.

1.2.2.

The Contractor shall perform all tasks identified in this PWS and gather all pertinent information. Contractor estimates and timelines shall be determined based on the deliverable due dates specified in Paragraph 1.5 (Deliverables). The Contractor shall coordinate with the Government to ensure that all activities are well synchronized and integrated within the G33 Directorate’s management efforts. All reports, studies and other identified deliverables in the Performance Work Statement (PWS) shall be prepared and submitted for Government approval or acceptance. All functions and activities shall be task driven, and work performed shall be in accordance with applicable regulations and guidelines.

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 consists of the functional activities relating to the administration and management of this effort. The contractor shall provide program management of contractor personnel performing tasks in this contract. The contractor shall designate a principal point of contact for the Government concerning technical and functional issues. These functions shall include administrative support by preparing documents, such as, briefings, point papers, and meeting minutes related to the status of the performance of this contract.

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

The contractor shall prepare an integrated (i.e., Government and contractor) Project Plan, which defines tasks, resources, and dependencies. The Management Plan shall include the technical and functional approach, organizational resources, and management controls of cost, performance, and schedule requirements throughout contract execution. The Draft Plan will be submitted within ten (10) business days of contract award. The Government will review the plan and provide comments to the contractor. The contractor will submit the Final Plan, no later than fifteen (15) business days from receipt of Government’s comments. The plan should not be a reiteration of the PWS requirements.

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

The contractor shall provide a Monthly Status Report monitoring quality assurance and configuration management. The status report will list, by each active task/project area, the accomplishments for the reporting period. The MSR shall outline the current funding status for travel and Other Direct Costs (ODCs) and include a brief synopsis of the efforts completed, deliverables provided, and conferences and trips conducted/attended during the reporting period, and an overall evaluation of the requirement to date. (Contractor name, trip location and purpose, and dates of travel shall report estimated and actual travel costs.) The report will list the deliverables for each task and any issues, problem areas, and items, which require Government action. The MSR shall include a Summary Report on Support to Ft

Lee, VA., Transportation School, Active and Reserve Forces, and Customer Support Log of Actions completed. The contractor shall provide the MSR no later than the fifth business day of each month. The MSR will be submitted electronically to the COR, angela.m.wolfe.civ@mail.mil.

1.3.1.3 Task 1 Subtask 3: Service Contract Reporting

The contractor shall report in the System for Award Management (SAM): 1) the total dollar amount invoiced for services performed during the previous Government fiscal year under the contract; 2) the prime contractor direct labor hours expended on the services performed during the previous Government fiscal year; and 3) if applicable Tier 1 subcontract number, including DUNS number/Unique Entity Identifier (UEI) and name, and the number of subcontractor direct labor hours expended under the contract. Reporting inputs will be for the labor executed during the period of performance during each Government fiscal year (FY), which runs October 1 through September 30.

1.3.2. Task Area 2: Functional Support

1.3.2.1 Task 2 Subtask 1: Software Test Plans: The contractor shall prepare and provide the Government a fully descriptive Software Test Plan in support of testing requirements for Customer Acceptance Testing (CAT) for GATES and Independent Verification and Validation (IV&V). The Software Test Plan shall walk a tester through 100 percent of the software application to be tested using scenario based testing and assume the tester to be a typical end user. As part of the software test plans the contractor shall create scenarios to fully test the listed platforms and systems. Scenarios shall be tied to standard data sets to incorporate representative cargo records with known data format and content flaws to emulate real world data, utilizing data from SDDC’s critical interfaces. Critical interfaces are 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), Marine Air-Ground Task Force (MAGAF), Deployment Support System II (MDSS II), Munitions Transportation Management System (MTMS), Army War Reserve Deployment System (AWARDS), and Distribution Standard System

(DSS).

Scenarios shall be standardized and grouped by functional areas. GATES test scenarios should include testing with Hawkeye, VSAT’s, CAISI wireless and other communication devices utilized during D-GATES operations. Software Test Plans support requirements for testing corrections to Emergency or Urgent Problem Reports submitted by users in the field.

The contractor shall provide the Draft Software Test Plan no later than four weeks prior to test start. The contractor shall provide the Final Software Test Plan no later than two weeks prior to test start. Typically testing events will simulate production events and processes utilizing production-like data. Modifications to previously created plans shall be made to accommodate functional changes and additions addressed in the software change package. Discrepancies will be forwarded to the Contracting Officer’s Representative (COR) for resolution. Support of this task is estimated once per quarter.

1.3.2.2 Task 2 Subtask 2 – Test Support. The contractor shall validate and verify the software meets functional and provide a Software Report of Test within five (5) business days of test completion. The contractor shall execute GATES software test as an end user or assist field representatives to ensure proper functioning of all installation requirements and changes. The contractor shall conduct regression testing to ensure other related processes are not affected by code changes. The contractor shall follow the developer’s guidance for all possible dependent processes, which will require specific testing. Any problems or issues will be identified in the Daily Update Report (Mon-Fri), provided electronically by the contractor and submitted to the COR. These problems/issues will be discussed at the weekly GATES meeting with Government representatives during the system testing cycle. Place of performance for this task will be at Scott AFB, IL. Support of this task is estimated once per quarter, for a period of up to 3 weeks at a time, unless regression testing is required.

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

The contractor shall prepare GATES briefing PowerPoint slides, informational documentation concerning SDDC Movement Orders & Shipping Processes/Systems Division issues, system upgrades, changes and general transportation information.

All documentation will be reviewed and accepted by the Government. The contractor shall provide updated documentation and briefings as new and/or revisions of GATES. Versions will be implemented no later than five (5) business days after implementation. Documentation shall be formatted to SDDC standard and templates.

1.3.2.6 Task 2 Subtask 4- Service tickets: The contractor shall have personnel available during a core period between 0700 and 1730 hours Central Time, Monday- Friday to provide GATES customer support. The contractor shall respond to GATES trouble tickets generated from Service Now which are assigned to the G33.

Problems, issues, questions, account concerns, training, etc… generated to the GATES SRC helpdesk, will be documented with a service ticket within Service Now and be resolved. The contractor shall be responsible for all service tickets up to and including Tier III level. The contractor shall determine if the problem is a functional or technical issue, or with hardware or software, isolated or systemic, and routed appropriately. The contractor shall respond within 24 hour of receipt of a call unless the service ticket is generated over the weekend or holiday, then it will be responded to within 24 hours of next business day. All responses to service tickets will be recorded in Service Now, maintained by G6. For reference and information purposes only, historical GATES data averaged an estimated 85-100 service tickets per month. Future workload may vary depending on deployments and exercises, which may fluctuate the number of calls received. The contractor shall provide GATES level 3 system support via Service Now, for all functional service ticket requirements. The contractor will provide a response with 24 hours of receiving notice of trouble ticket.

1.3.3 Task 3 Training Support

1.3.3.1 Task 3 Subtask 1 - Training/Virtual Training/CBT/In-person. The contractor shall provide the GATES user community with three (3) type of training, virtual, CBT and in-person training. Virtual training shall be provided in the form of the Continuous Learning Environment (CLE) via acceptable government telecom systems (TEAMS, VTC, DTS, etc.). The contractor shall be responsible for creating a training agenda and all applicable training materials to include supporting documentation and handouts. The contractor shall provide an After Action Report (AAR) electronically which details assistance provided during the training, participants, and points of contact, purpose of training, summary of events, observations and recommendations within five calendar days after each training session. Training shall include student rosters and assessments of the effectiveness of the training provided. Any issues or concerns with the GATES system will be captured and included in the report. Virtual training is estimated to take place four times a quarter. 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 1 ( one) person, working this contract, is expected to be proficient, from end to end, in training students in any type of environment (in person, virtual).

Training may consist of GATES functional training, basic transportation knowledge and limited IBS knowledge.

1.3.3.2 Task 3 Subtask 2-Continuous Learning Environment (CLE) The CLE provides global aerial port & surface terminal community an enterprise web accessible proficiency database/capability. The contractor shall provide functional (surface) support to the Transportation School located at Fort Lee, Virginia, until the T-school ends the GATES training course on/around 9/1/2021.

The contractor shall assist the Army Transportation School (T House) with updating Transportation School Program of Instruction (POI) for GATES. The contractor shall provide the T-School with GATES training. The contractor shall provide the T-School with GATES Service Now tickets response within 1 hour of documented Service Ticket. Training shall be in accordance with (IAW) Department of the Army, Training and Doctrine Command, TRADOC Regulation 350-70 and TRADOC

Pamphlet 528-8-2. The contractor shall support setup and execution of GATES courses.

1.3.3.3 Task 3 Subtask 3 – Course Design, development, implementation and maintenance: As of Sept 2021, the current GATES course taught at the T-School, Ft Lee, VA will no longer be offered. The implementation, management and coordination of this course will now be handled by SDDC, G3. The Contractor shall design, develop, implement, update and maintain a training program that will cover all functionalities of GATES, as outlined by the points of instruction (POI’s) and determined by G3 Systems. This training program shall be developed via CBT, virtual and in-person training. The Contractor shall be responsible for updating the program as necessary, as changes occur within GATES. The Contractor shall also be responsible for providing training to the user community as determined by G3.

Training length and type will be determined on an individual basis, based on training need as determined by the G3. Development of the training modules shall be based on: CBT shall include a training module for each POI in GATES, and shall be self-paced by the individual user. Virtual training shall be based on individual POI’s of GATES, and shall cover each POI in-depth. Virtual training shall not exceed 24 sessions in a calendar year. In person training shall be based on the GATES POI’s and shall cover each POI in-depth. In-person training shall not exceed 12 times per calendar year. In-person training will consist of a 2 week/80-hour training course.

1.3.3.4 Task 3 Subtask 4 – Hardware/Software Maintenance of GATES equipment SDDC utilizes a series of GFE computers and peripherals (printer, scanners, etc.) for training and exercises. The Contractor shall maintain, update, troubleshoot and setup the training systems and peripherals as necessary, in support of training events, class training, MRX’s or any other reason necessary.

1.3.3.5 Task 3 Subtask 5- Data Security:

The Contractor shall protect unclassified DoD data from unauthorized access or disclosure in accordance with DoDI 8582.01, “Security of Unclassified Information on Non-DoD Information Systems,” DoDM 5200.01, Volume 3, and classified information under DoD 5220.22-M, National Industrial Security Program Operating Manual, and the program’s Security Classification Guide. Contractor personnel will be required to sign non-disclosure agreements in order to perform tasks assigned under this PWS.

1.3.3.6 Task 3 Subtask 6 – Data Rights and Protections:

The Government obtains under this contract “unlimited rights” to all non-commercial executable computer software, computer software documentation, enhancements, and similar non-commercial data developed exclusively at Government expense and delivered to the Government under this contract.

“Unlimited rights” means rights to use, modify, reproduce, release, perform, display, or disclose in whole or in part, in any manner and for any purpose whatsoever, and to have the ability to authorize others to do so.

1.4. Deliverables

One (1) copy of the transmittal letter with deliverable attached in electronic format to the COR. 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.

Upon receipt of the Government comments, the contractor shall have ten calendar days to incorporate the Government's comments and/or change requests and to resubmit the deliverable in its final form, unless otherwise stated within the PWS task.

All deliverables shall meet professional standards and meet the requirements set forth in contractual documentation. Unless noted otherwise, the contractor shall provide all deliverables electronically to the COR in Microsoft Office formats pursuant to the following schedule. Deliverables will be identified by contract number, PWS subtask, and deliverable title.

PWS

Para

Deliverable Title Delivery Schedule

1.3.1.1 Task Order Management Plan

(TOMP)

Draft - within ten (10) Business days after task order award. Final – within fifteen (15) business days after receipt o Government comments.

1.3.1.2 Monthly Status Report (MSR) No later than the 5th business day of each month.

1.3.2.1 Software Test Plans Draft plan 4 weeks prior to test start.

Final plan 2 week prior to test start.

1.3.2.2 Software Report of Test Within 5 business days of test completion.

1.3.2.2 Daily Update Report Provided electronically to the COR daily (Mon-Fri).

1.3.2.3 Briefing/Documentation/ After Action

Report

Within 5 calendar days after each implementation

1.3.2.4 Virtual Training AAR Within 5 calendar days after each Virtual training session

1.3.2.5 CLE AAR Within 5 calendar days after each

site visit.

1.3.2.6 Service Tickets No later than 24 hours after ticket is opened

1.3.3.3 Course Design, Development, Implementation and Maintenance

Initial design must be ready within Twenty (20) days of contract award.

Final design ready within thirty (30) days after design is accepted.

1.3.3.4

Hardware/Software Maintenance of GATES equipment

Ongoing

2.0 SERVICE DELIVERY SUMMARY

The Services Delivery Summary (SDS) represents the most important contract objectives that, when met, will ensure contract performance is satisfactory.

Although not all PWS requirements are listed in the SDS, the contractor is fully expected to comply with all requirements in the PWS.

PWS

Para

Performance Objective Performance Threshold

1.3.1.2 Monthly Status Report

(MSR)

100% of the time each report is timely and accurate

1.3.2.1 Software Test Plans 95% of the time each draft and final plan is timely.

1.3.2.2 Software Report of Test 95% of tested code executes as required or is noted on discrepancy report.

1.3.2.2 Daily update report 95% of the time the report is timely, accurate, and complete.

1.3.2.3 After Action Report to

Active Duty Component (On-site Response)

95% of the time reports are delivered within five calendar days of return from site visit and 100% of the time reports contain all applicable information

1.3.2.4 After Action Report

Brigade/Battalion (On-site Response)

95% of the time the report is timely, accurate, and complete.

1.3.2.5 After Action Report

Reserve (On-site Response

95% of the time the report is timely, accurate, and complete.

1.3.2.6 System Briefings and

Documentation

95% of the time the report is timely, accurate, and complete.

1.3.3.1 Training (In-person, Virtual, CBT)

95% of the time the report is timely, accurate, and complete.

1.3.3.3 Course design, development, Implementation and, Maintenance

95% of the time the defined requirements are met and d Developed on schedule.

3.0 GOVERNMENT-FURNISHED EQUIPMENT AND SERVICES

3.1 Government-Furnished Information (GFI)

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, Base-line 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, to include scanners, docking stations, and bar code printers.

A complete list with serial numbers of GFE will be provided upon task order award.

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 Use and Safeguarding of GFE

GFE shall be used solely and exclusively for the performance of work under this PWS. The contractor shall safeguard GFE and take reasonable precautions to prevent fraud, waste, and abuse. The contractor shall designate at least one primary and one alternate custodian whose responsibility it is to receive, account for, and safeguard

GFE.

3.4 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 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 accountability 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.

3.5 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 shortage, loss, or destruction of, damage and excessive wear and tear to GFE.

3.6 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.7 Repair vs. Replacement

GFE shall not be replaced if it can be repaired or rebuilt, to return it to the condition existing at the time it was accepted by the contractor. 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.8 Warranties

The Government will furnish warranty information on all GFE. All GFE under manufacturer’s warranty shall be operated, maintained, and repaired in accordance there with. 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.9 Disposal, Salvage, Reclamation, and Recycling

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

3.10 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).

4.0 GENERAL INFORMATION

4.1 Place of Performance

Tasks shall be performed at SAFB, or at a location specified by the COR.

Due to current conditions concerning COVID-19, and the unknown duration of the pandemic, Contractor shall provide an office within a reasonable distance (10 miles) from SAFB for contract employees to work at, if and when the SDDC building is unavailable for use during COVID conditions, as well as non COVID conditions.

Contractor facility shall also be used for meetings and training, directly relating to the contractor and services covered under the contract. Telework may be considered on an as needed basis, and will be discussed as needed.

Project Manager does not need to be located at Scott AFB, but must be able to travel as necessary to perform duties and attend meetings, that can’t take place via TEAMS or other electronic means. (locations may be discussed at a later date)

IT Specialist will be located at Beaumont, Texas and will travel to SAFB or other locations as needed/requested by COR. This position requires access to the Ft Hood network which can only be established as an employee at Ft. Hood. Current GATES equipment is currently configured to the Ft Hood network. Employee may be required to travel to various locations to support training exercise when the GATES communication kit will be utilized.

Senior Functional/Functional (3 positions) will be located at SAFB, within the G3 area. These individuals will be responsible for daily tasks, such as trouble tickets, and research. They will aid in the development and maintenance of GATES products to support the training and mission capabilities of GATES. This requirement is in support of short-notice on demand training and requirements as defined in the PWS.

Software designer/support position may be located at the Contractor facility or remotely. If remotely, and not in the local commuting area of SAFB, employee will be expected to travel to support requirements and meetings that can be conducted via an electronic means (VTC, TEAMS). This requirement is in support of the rapid timeline for development of the training packages. Employee will coordinate location with COR on a weekly basis.

On occasion, Contractors who normally work at Contractor facilities will be required to attend meetings at SDDC, Scott AFB, IL. Contractor personnel are expected to conform to agency operating hours (0730 – 1730 CST/CDT) unless otherwise agreed upon. Work will generally consist of 40-hour work weeks, Monday through Friday, excluding federal holidays. While traveling or supporting missions, contract personnel may be required to work longer than an 8-hour work day and/or weekend/holiday hours. Personnel may be required to support short notice adjustments to the daily work hours. To accommodate the Contractor’s on-site support personnel, the Government will provide controlled working space, phone, computer, fax, and connections to the Non-Secure Internet Protocol Router Network (NIPRNET), as required, at no cost to the Contractor.

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 three twelve-month option periods.

Transition: 25 May 2021 – 24 Jun 2021 Base Period: 25 Jun 2021 – 24 Jun 2022 Option Period 1: 25 Jun 2022 – 24 Jun 2023 Option Period 2: 25 Jun 2023 – 24 Jun 2024 Option Period 3: 25 Jun 2024 – 24 Jun 2025

4.2.1. Hours of Operation and Recognized Holidays

The Contractor shall provide support during normal Government business hours between 0730-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. The following will be observed as Federal Government holidays:

New Year's Day, Martin Luther King's Birthday, President's Day, Memorial Day, 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 Contractor travel shall be coordinated and validated as necessary by the primary or alternate COR prior to incurring travel expenses. The Contractor shall identify personnel who will be traveling in sufficient time to obtain the lowest possible rates for airfare, rental car, and lodging. For long distance travel, a minimum of five (5) business days’ advance notice from the travel commencement date is required unless mission requirements dictate otherwise. The travel request shall be in writing and contain the dates, location, and estimated travel costs.

Contractor invoices (along with associated receipts) shall support all travel reimbursement requests. Actual travel costs will be reported to the COR by person, by trip within five (5) business days of completion of travel. The Government will not reimburse local travel and related expenses to the Contractor for daily travel to or from work at Scott Air Force Base, IL (SAFB) or the Contractor’s facility. If the contractor choses to use remote labor travel to and from SAFB will not be reimbursed.

4.4 Other Direct Costs (ODCs)

Prior to incurring costs, the contractor shall coordinate expenditure of ODC funds with the COR. The Government will reimburse materials and fees incurred in the performance of the PWS based on prior coordination with the COR. ODCs may include but are not limited to: copier fees, reproduction, printing, duplication, scanning costs, binding supplies, electronic media such as tapes and CDs, postage and shipping charges, meeting facility charges, conference fees, and other related expenses. The contractor shall submit ODC requests in writing to the COR for approval at least five business days in advance of incurring any expenses. The request shall contain estimated costs supported by a minimum of three competitive quotes. Contractor invoices (along with associated receipts) shall support all ODC reimbursement requests. In no event shall the contractor be authorized to purchase ODCs that exceed the ODC amount funded in the contract. General and Administrative overhead charges will not be accepted or paid for approved ODC purchases.

4.4 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, in accordance with the generic position descriptions provided in the Alliant Small Business Government-Wide Acquisition Contract (GWAC). The contractor shall notify the CO in writing of any changes to personnel within three (3) business days after information is known.

4.4.1 Other Positions within/on Contract

The contractor shall provide a staff that is fully functional in GATES Surface/Water, and well voiced in the areas of surface transportation, transportation systems to include IBS and DTR regulations. At least two employees must have knowledge, skills and past demonstrated performance in training employees on executable systems. Contract employees will be expected to perform duties with limited, to zero oversight from Government COR and other staff due to TDY and other priorities.

Contract employees are expected to respond/maintain service tickets and user inquiries, in a timely manner with limited input from government personnel.

Contract employees will be able to perform GATES duties at a Tier II/III functional level and will be expected to do this beginning on the first day of contract, after credentials are received and system access granted.

4.5 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.6 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.

https://www.dmdc.osd.mil/appl/dwc/index.jsp

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.7 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.8 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.

5.0 Security (Physical, Personnel, Information, Antiterrorism/Force Protection and Industrial Security)

5.1 General Security Information:

The majority of daily work associated with this PWS is at the unclassified level, but contractor personnel may be required to access SECRET information and/or classified areas, during performance of this requirement.

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, all contractor personnel shall possess the appropriate personnel security investigation for the position(s) occupied. Contractor personnel shall be required to have a background investigation that corresponds with the sensitivity level of the tasks to be performed.

5.3 Clearance Requirements and Position Sensitivity.

Contractor personnel with IA administrative privileges and/or who will monitor DOD IT systems or software as designated by DOD Instruction 8500.1 and DOD Manual 5200.2-R may be rated at the various levels listed below. The stipulation of the numbers and what IT/Automated Data Processing (ADP) levels the contractors will have shall be approved by the COR or the CO before the start of the task order.

The contractor shall comply with all appropriate provisions of applicable security regulations while assigned to this task order for DOD and USTRANSCOM. The following guidance will be followed when determining background investigation and clearance levels for this task order depending on requirements:

POSITION LEVEL:

Non-Critical Sensitive Positions (SECRET):

IT/ADP-II and Non-Critical Sensitive Positions are those positions that: have access to Secret or Confidential information; Security police/provost marshal-type duties involving the enforcement of law and security duties involving the protection and safeguarding of DOD personnel and property; category II automated data processing positions; duties involving education and orientation of DOD personnel;

duties involving the design, operation, or maintenance of intrusion detection systems deployed to safeguard DOD personnel and property; responsible for the direction, planning, design, operation, or maintenance of a computer system, and whose work is technically reviewed by a higher authority of the ADP-I category to ensure the integrity of the system; and any other position so designated by the head of the Component or designee.

Background Investigation Requirements:

(IT-II/ADP-II/Non-Critical Sensitive) Requirements for SECRET – (Tier 3):

Positions designated by the Government at the Non-Critical Sensitive/ADP-II/IT-II rating require a Tier 3 (or acceptable periodic reinvestigation) favorably adjudicated (a favorable adjudication grants eligibility at the SECRET level as prescribed by DOD 5200.2-R). The IT-II/ADP-II requirement mandates the contractor have a minimum FCL at the SECRET (or higher) level due to investigation submissions as directed in DOD 5220.22-M Operating Manual, DODM 5200.01 and JPAS.

POSITION LEVEL:

Non-Sensitive Positions (Position of Trust Determination) (No Classified Access–Tier 1) All other positions involved in computer activities and Common Access Card. No clearance is granted for classified access and only a Position of Trust (PoT) is awarded and posted in JPAS.

Background Investigation Requirements:

(Non-Sensitive/IT-III/ADP-III) Requirements for Position of Trust Determinations (No Classified Access - Tier 1/NACI):

Positions designated by the Government as Non-Sensitive/IT-III/ADP-III require a favorably adjudicated Tier 1/NACI investigation or greater IAW DoDI 5200.46, DoD Investigative and Adjudicative Guidance for Issuing the Common Access Card (CAC), dated 9 Sep 2014, DoDM 1000.13, Vol 1, DoD Identification (ID) Cards:

ID Card Life-Cycle, dated 23 Jan 2014, and National Background Investigations Bureau (NBIB) standards. Before a CAC or NIPRNet access will be granted, a favorable Tier 1/NACI investigation or greater must be on record in Joint Personnel Adjudication System (JPAS), and a favorable Federal Bureau of Investigation (FBI) National Criminal History Check (fingerprint check) on record with the National Background Investigations Bureau (NBIB). A CAC may be issued on an interim basis based on a favorable FBI fingerprint check and successful submission of a Tier 1 investigation to NBIB, and on record in JPAS.

5.3.1 Out-processing of Contractors with CACs: As soon as the contractor company is informed of contractor personnel who will no longer be working on the contract, they shall relay this information to the contracting office. Contractor personnel no longer working on this contract are required to return their CACs to the contracting office.

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

NOTE: The above requirements for Non-Sensitive/IT-III/ADP-III positions are for unclassified access and systems only. No classified access will be granted based on the Tier 1 investigation. USTRANSCOM will only process Tier 1 investigations and will not complete any personnel security investigations (Tier 3/Tier 5) for classified access. It is incumbent upon the contractor to have the appropriate investigations completed upon start of the task order

5.4 Security Clearance and Special Access Requirements

All positions on this requirement require a minimum of a SECRET clearance as granted by the Personnel Security Management Office-Industry (PSMO-I).

5.5 Facilities Clearance Level (FCL)

The contractor must have a valid FCL at the SECRET level. Interim FCLs are acceptable provided they are not expired. FCL procedures and security guidelines for adjudicative requirements are outlined in DOD 5220.22-M FCLs and Interim FCLs must be awarded by the Defense Security Service (DSS) Facility Clearance Branch

5.6 Personnel and Facilities Clearance Validation

Upon contract task order award, the contactor shall submit the names of contractor personnel to the COR, who will coordinate with SDDC G34 Industrial Security Program Manager for vetting through JPAS to ensure investigative and clearance requirements have been satisfied. This will be completed before the COR/Trusted Agent (TA) accesses the Trusted Associate Sponsorship System (TASS) and submits the request for issuance of the CAC to the contractor’s personnel. If a contractor’s employee does not have the required investigative or security clearance level based on the Government’s determination, the contractor’s personnel will be denied the ability to work in support of this task order and the employee’s information will not be loaded into TASS.

5.6.1 Prior to performance start date, permanently assigned contractor employees on Scott AFB (SAFB) will require a visit request for the current period of performance posted in Joint Personnel Adjudication System (JPAS) to Security Management Office (SMO): SSC-CONT. The visit request will annotate the task order number in the POC block of the visit request and the name of the COR/CO in the phone number block. All SAFB permanently assigned contract employees shall in process at the Protection Services Center (PSC) on the first day of contract start at SAFB.

5.7 Common Access Card Issuance Procedures

Upon notification by SDDC G34 that contractor personnel working in the PSC, the TA will create a CAC application in TASS with an expiration date of no more than three years. Contractors are reminded that once a new contract is issued, previously held Government CAC’s or those from other contracts must be revoked, before a new CAC can be issued for the new contract. Once approved by the TA, the contractor employee may go to the nearest Real-Time Automated Personnel Identification System (RAPIDS)/Defense Enrollment Eligibility Reporting System (DEERS) office for CAC issuance.

Basic Contractor CAC Requirements:

Requires access on a continual basis of 6 months or more.

Contract personnel require access to a DoD facility or networks, either on-site or from a remote location.

Users need access to systems for platforms that requires CAC login or user authentication.

Non- U. S. Citizens:

Possess legal U. S. residency for a period of 3 or more years with a completed Tier 1 background investigation and fingerprint card. Also meet (as a direct/indirect DoD hire personnel) the investigative requirements for DoD employment as recognized through international agreements pursuant to subchapter 2131 of DoD 1400.25 (reference M).

Possess (as foreign military, employee or contract support personnel), a visit status and security assurance that has been confirmed, documented and processed I/A/W international agreements pursuant to reference G of DoD 1440.25-M.

CAC Applications:

The CAC applications must have an adjudicated Tier 1, Tier 3 or Tier 5 background investigation posted in JPAS, or

An interim CAC may be approved when the contractor employee has a favorable fingerprint, name and criminal records check completed and has either a Tier 1, Tier 3 or Tier 5 background check “open” with OPM.

The TASS TA will not approve the CAC application in TASS until that TA has verified with the PSC, one of the above requirements.

5.8 Scott Air Force Base/HQ SDDC/USTRANSCOM Physical Access

Upon receipt of the CAC, permanently assigned contractor personnel located at HQ SDDC/USTRANSCOM at SAFB, IL, may obtain the AF 1199 (Restricted Area Badge) if the employee meets the requirements set forth in the SAFB Instruction 31-

101. Only personnel assigned physically on SAFB at least four (4) days a week will be issued the AF 1199. The Government will provide unrestricted access to facilities, consistent with security clearance and need to know, necessary for the on-site personnel to perform their work in accordance with the task order. Visits to SAFB by contractor personnel who do not possess the CAC will be facilitated by the COR/CO sponsoring the employee through the online base access system.

5.9 Visits by Non-Assigned Contractors to USTRANSCOM/SDDC Buildings Any visit(s) by contractor personnel not permanently assigned to this task order (i.e., company presidents, company security managers, contractor personnel not permanently assigned at SAFB, etc.) require an electronic visit request be submitted using JPAS. JPAS visits can be forwarded to the Security Management Office (SMO) code: USTC -SDDC. The visit request shall annotate the task order number in the POC block of the visit request and the name/phone number of either the functional, COR or CO in the phone number block.

5.10 Visits by Permanently Assigned Contractors

Permanently assigned contractor employees on SAFB will require a visit request for the current period of performance posted in JPAS to SMO: CONT. The visit request will annotate the contract number in the POC block of the visit request and the name/phone number of either the functional, COR or CO in the phone number block.

Upon in-processing permanently assigned contractors will require a copy of the DD Form 254 for this task order to show the classified access level for this task order and to assist in assigning permissions on restricted area badges.

5.10.1 Supplemental Notes Regarding Visit Information in JPAS. Personnel requiring access to Government facilities will properly complete the “Visit Information” block in JPAS.