2024.11.14 JOPES PWS Final Draft.pdf

JOINT OPERATION PLANNING AND EXECUTION SYSTEM (JOPES) AND

TRANSPORTATION VISUALIZER (TRANSVIZ) FUNCTIONAL MANAGEMENT

SUPPORT PERFORMANCE WORK STATEMENT (PWS)

14 November 2024

1. DESCRIPTION OF SERVICES

1.1. Background.

1.1.1. The mission of United States Transportation Command (USTRANSCOM) is to provide air, land, and sea transportation for the Department of Defense (DoD) during both peace and war. Prior to providing transportation, USTRANSCOM conducts transportation feasibility analysis for all movement requests and provides multi-modal transportation solutions for all customers to include supported commanders, military Services, coalition partners, and agencies. This requires USTRANSCOM to have the ability to collect, transmit, assimilate, process, and analyze transportation related data so to possess accurate information by utilizing robust, high capacity, and easy to use tools including state-of-the-art automation and telecommunications technologies. The functional support tasks detailed in this PWS contributes to the command fulfilling its role in providing joint transportation solutions.

1.1.2. JOPES is not just software but includes formally established policies and procedures that guide conventional operations planning and execution. JOPES brings together these policies and procedures with personnel (users as well as those that keep the system operational), communications, and automated data processing systems to provide a total system for contingency and crisis action planning. JOPES incorporates standard data files and applications into a system compatible with the deployment requirements of the war fighter. USTRANSCOM is responsible for Secret components of JOPES.

1.1.3. TransViz was developed by USTRANSCOM as a transportation requirements and plan analysis tool to work with JOPES for global force movements. The program can give users full access to real-time JOPES data and provide a clear visual environment as well. In TransViz, users can manipulate data in one location and instantly see their changes reflected across one or more collaborative workspaces.

Planners in multiple locations can analyze information, share thoughts, evaluate courses of action and, if their JOPES permissions allow, make data changes to fifteen (15) different transportation-related fields.

Planners can quickly identify exceptions, outliers, and anomalies, collaborate across organizations to facilitate decision making and then make necessary changes to achieve a transportation solution. The TransViz workspace contains visualization tools that allow collaboration as well as planning what-if analysis.

1.1.4. The pace of current operations and development of applications and system enhancements requires increased emphasis in the following areas:

• Functional Management Support

• Error Identification and Resolution

• Account Administration

• Testing new applications and upgrades

• Research and Analysis support

1.2. Scope. This PWS contains requirements for JOPES and TransViz Functional Manager Support Services. The specific tasks are:

• Task Area 1, Contract-Level and Task Order Management

• Task Area 2, JOPES Functional Management Support

• Task Area 3, TransViz Functional Management Support

• Task Area 4, Research and Analysis Support

1.3. Specific Tasks.

1.3.1. Task Area 1 - Contract-Level and Task Order Management.

1.3.1.1. Subtask 1 - Contract Level Program Management. This task consists of the functional activities relating to the administration and management. The contractor shall provide a team leader responsible for oversight of contractor personnel performing tasks outlined in this PWS. The team leader provides daily supervision and direction to support staff and is responsible for formulating and enforcing work standards, assigning work schedules, supervising contractor personnel, and communicating the organization’s policies, purposes, and goals to subordinates. Contractor program reviews shall be held quarterly to assess performance under this task as defined in PWS Paragraphs 2.1 and 2.2.

At a minimum, the program review shall include reports covering the following information:

• System status of JOPES and TransViz

• Number of JOPES accounts including the number of new accounts created

• Number of TransViz accounts

• Sampling audit of account processing

• Transaction and error rate metrics

• JOPES System, application tests, and updates results

• Establishment of TransViz Schedule and Performance baselines

• Progress tracking and reporting of TransViz baselines

• Descriptions of activities during the current quarter by task and recommendations for problem solution

• Review of deliverables completed during the report period and any changes in the planned deliverables schedule

Subtask 2 - Task Order Management Plan (TOMP). The Contractor shall provide a TOMP as defined in PWS paragraphs 2.1 and 2.2.The Government will review the plan and provide comments to the Contractor. The Contractor shall submit the final plan as defined in PWS paragraphs 2.1 and 2.2.

1.3.2. Task Area 2 – JOPES Functional Management Support.

1.3.2.1. Subtask 1 – Application Knowledge.

1.3.2.1.1. At a minimum, the contractor JOPES Functional support personnel shall be able to operate each of the following applications/systems and shall provide assistance to USTRANSCOM personnel including from the transportation component commands and subordinate organizations using these applications:

Webmin File Transfer, Global Decision Support System, Scheduling and Movement Interface (SMINT), Global Video Services (GVS) and/or TEAMS, JOPES Editing Tool, Internet Browsers, Rapid Query Tool, Time-Phased Force and Deployment Data (TPFDD) Management Tool, Web Scheduling and Movement, Structured Query Language, Sun Secure Global Desktop, JOPES Synchronization Process, JOPES Subscriptions, JOPES Data Network Services, UNIX operating system, Shell Scripting, Extensible Markup Language, Gnome Terminal, Windows operating system, Windows-based applications, Newsgroup applications, and functional database manager user and error processing applications. In the event that new applications are introduced, the Government will provide introductory training to contractor personnel.

1.3.2.1.2. The contractor shall support the Joint Staff Support Center (JSSC) with application and system problem identification and verification.

1.3.2.2. Subtask 2 - System Support.

1.3.2.2.1. The contractor shall participate in activities involved in the efforts to improve JOPES system performance. Activities include, but are not limited to, attending JOPES meetings, conferences, and working groups and attending video teleconference meetings. The contractor shall facilitate meetings to identify issues and findings and make recommendations for corrective actions. The contractor shall prepare meeting minute summaries as defined in PWS paragraph 2.1.

1.3.2.2.2. The contractor shall provide JOPES account administration and reports and perform administrative matters to properly maintain JOPES accounts in accordance with JOPES Functional Management manuals, instructions, and policies. These procedures include ensuring validity of account requests before building JOPES accounts, building accounts, granting functional permissions, granting Operations Plan (OPLAN) series permissions, and managing and auditing current accounts. The contractor shall submit a monthly account administration report as defined in PWS paragraphs 2.1 and 2.2.

1.3.2.2.3. The contractor shall perform daily status checks of JOPES systems to include SMINT, Newsgroups/Mail, JSSC JOPES Monitoring Tool, and Functional Manager tools used to ensure OPLAN synchronization and OPLAN error resolution.

1.3.2.2.4. In addition to monitoring system status, the contractor shall monitor, troubleshoot, analyze, and report system degradation and ensure coordination of scheduled server outages with the Deployment and Distribution Operations Center (DDOC), USTRANSCOM Operations Integration Division (TCJ3-I), JSSC, and other appropriate agencies. The contractor shall analyze outages or degradation and coordinate with the JSSC to ensure the command maintains JOPES operational capability as defined in PWS 2.1 and 2.2

1.3.2.3. Subtask 3 – Functional Testing.

1.3.2.3.1 The contractor shall be responsible for JOPES system functional testing of new applications a n d application upgrades. The contractor shall coordinate functional testing with command and component command operators and command and component command external system interfaces, to include their system administrators and project management offices when directed by the government. Application testing may require the contractor to provide a test plan as defined in PWS paragraphs 2.1 and 2.2.

1.3.2.3.2 The contractor shall provide a written functional test report, as defined in PWS paragraphs 2.1 and 2.2, of results that includes tests and updates, recommended solutions for necessary application improvement, and reviews of JOPES data and technical documentation for correctness and applicability (as appropriate). Support shall include functional and technical support to JOPES demonstrations in accordance with (IAW) the tasks of this PWS.

1.3.2.4. Subtask 4 – JOPES Error Processing and System Status Reports. The contractor shall provide on-going error resolution by identifying, troubleshooting, and resolving transaction failures and conflicts between the JOPES server enclaves. The contractor shall identify, analyze, and reprocess SMINT errors; support the JSSC with conflict resolution; ensure JOPES reference files are current; and develop and maintain transaction and error rate metrics IAW the daily tasks of this PWS. The contractor shall submit a weekly Error Processing and Systems Status report as defined in PWS paragraphs 2.1 and 2.2.

1.3.2.5. Subtask 5: JOPES Training. The contractor shall coordinate Joint Deployment Training Command (JDTC) Mobile Training Team (MTT) training for USTRANSCOM. JOPES training provided by the MTT includes both the JOPES Support Personnel Course (JSPC) and the JOPES Action Officer Course (JAOC). Both courses are conducted at USTRANSCOM normally two times a year. The contractor shall be responsible for coordinating dates of training with JDTC and then scheduling the classroom(s) for the training. The contractor shall coordinate the number of seats available for each course with JDTC and TCJ3-7 training. The contractor shall be the point of contact (POC) for the JDTC instructors and ensure they are informed of security requirements and classroom location as well as coordinate any training materials sent by the instructors. The contractor shall ensure students enrolled in the class have completed prerequisites for each course. Based upon the acceptance parameters set for each class by the Government, the contractor shall notify students of approval or disapproval for each class, create and execute a ‘stand-by’ list, and ensure each class is full to the extent possible given the number of students on the waiting list.

1.3.2.6. Subtask 6 - USTRANSCOM Liaison to JOPES Communities. The contractor, in support of USTRANSCOM, is required to attend JOPES meetings and events.

1.3.2.6.1. The contractor shall serve as a member of USTRANSCOM team supporting the JOPES Action Group (JAG) and coordinate JOPES related issues with the JSSC. The contractor shall interface with the JSSC, the Strategic Server Management Center, and Command Functional Managers to ensure smooth operation of the system.

1.3.2.6.2. Task support will involve worldwide travel for temporary duty (TDY). The contractor shall attend meetings in support of mission requirements. These may include, but are not limited to:

• JAG meetings held quarterly, normally lasting three (3) to five (5) business days.

• System testing for programs associated with JOPES. These testing requirements could occur numerous times within the year, each for a period of two (2) to four (4) business days.

1.3.3. Task Area 3 – TransViz Functional Management Support.

1.3.3.1. Subtask 1 – Application Knowledge. At a minimum, the contractor TransViz Functional Manager support personnel shall be able to operate each of the following applications and systems and shall provide assistance to other USTRANSCOM personnel and components: TransViz, GVS, Thunderbird, Internet browsers, and Windows-based applications.

1.3.3.1.2. The contractor shall conduct training on TransViz via in-resident or virtually. In-resident classes are two (2) to three (3) business days in length and virtual classes are scalable based on user training requirements. The contractor shall be prepared to conduct up to four (4) in-resident classes annually and monthly virtual classes. Lesson plans shall be approved by the Government. The contractor shall hand out critique forms at the conclusion of each training session and submit completed forms to the Government TransViz Functional Manager.

1.3.3.2. Subtask 2 - System Support.

1.3.3.2.1. The contractor shall participate in activities involved in the efforts to improve system performance of the TransViz tool. Activities include, but are not limited to, attending meetings, conferences and working groups and attending video teleconference meetings. The contractor shall facilitate meetings to identify issues and findings a n d make recommendations for corrective actions.

The contractor shall prepare minutes or summaries of these meetings as defined in PWS paragraphs 2.1 and 2.2.

1.3.3.2.2. The contractor shall perform TransViz user account management functions, which include, but are not limited to, the creation, modification, and deletion of application user accounts. As part of the user account management function, the contractor shall grant appropriate access permissions to specific functions within TransViz based on the user’s organizational role. The contractor shall identify and correct functional user account anomalies. The contractor shall submit a monthly account administration report as defined in PWS paragraphs 2.1 and 2.2.

1.3.3.2.3. The contractor shall be the liaison for updates to the DoD Geographic File (GEOFILE) for USTRANSCOM interests in Port of Embarkation (POE) and Port of Debarkation (POD) locations and their designations, Defense Transportation Regulations (DTR) codes, International Civil Aviation Organization (ICAOs) codes, including creating new Geographic Locations (GEOLOCs) for ports.

1.3.3.2.4. The contractor shall provide hands-on command functional support for TransViz usage such as data retrieval, reporting, and user dashboard setup. The contractor shall provide initial TransViz application training to users as well as follow-up, hands-on assistance on application usage once initial training is completed. The contractor shall develop class training plans, lesson plans, and training activity documents. The contractor shall update lesson plans and training activities as each new software version is released as defined in PWS paragraphs 2.1 and 2.2. The contractor shall develop scripts and scenarios as required to demonstrate application capabilities and provide application demonstrations as directed by the Government.

1.3.3.2.5. With each scheduled software release, the contractor shall review the TransViz Concept of Operations (CONOPS), Standard Operating Procedures (SOPs), and User’s Manual. If software or process changes impact a document, the contractor shall revise the document(s) accordingly as defined in PWS

1.3.3.2.6. The contractor shall provide functional application support by identifying system and data anomalies or other issues impacting TransViz and command operations. The contractor shall identify problems and recommend enhancements to the Government for software development action. The contractor shall also track software developer resolution of Government-submitted problems and enhancements. The contractor shall submit a monthly configuration activity report as defined in PWS

1.3.3.2.7. The contractor shall provide a Monthly Status Report (MSR) detailing TransViz activities, accomplishments, and issues for the preceding month, as defined in PWS paragraphs 2.1 and 2.2.

1.3.3.2.8. The contractor shall function as Gatekeeper for TransViz application website. Duties include, but not limited to maintaining web content on the USTRANSCOM portal and functional account management.

1.3.3.2.9. Task support may involve worldwide travel for TDY. The contractor shall attend meetings in support of mission requirements. These may include, but are not limited to:

• Application training and demonstrations for Joint Planning and Execution Community user organizations lasting three (3) to five (5) business days.

• System functional testing for TransViz. These testing requirements could occur numerous times within the year, each for a period of two (2) to four (4) business days.

1.3.3.3. Subtask 3 – Functional Testing.

1.3.3.3.1. The contractor shall be responsible for TransViz and related system functional testing of new applications and application upgrades. The contractor shall create test plans, provide daily test status reports, if required, and submit a functional test report of results that includes a review of testing events and recommended solutions for necessary improvement as defined in PWS paragraphs 2.1 and 2.2.

1.3.4. Task Area 4 – Research and Analysis Support.

1.3.4.1. Task 1: Systems, Process, and Policy Metrics.

1.3.4.1.1. Subtask 1 – Systems Metrics. The contractor shall utilize data from deployment and distribution Command and Control (C2) source systems to develop and provide metrics, as defined in PWS paragraphs 2.1 and 2.2, indicating the ability of these systems to provide required information.

1.3.4.1.2. Subtask 2 - Process Metrics. The contractor shall utilize data from integrated deployment and distribution C2 source systems to develop and provide metrics, as defined in PWS paragraphs 2.1 and 2.2, indicating adherence to and adequacy of deployment and distribution processes.

1.3.4.1.3. Subtask 3 - Policy Metrics. The contractor shall utilize data from deployment and distribution C2 source systems to develop and provide metrics, as defined in 2.1 and 2.2, indicating adherence to and adequacy of deployment and distribution policies.

1.3.5. Task Area 5 - Global Command and Control System (GCCS-J) Functional Support.

(OPTIONAL)

1.3.5.1 Subtask 1 - Application Knowledge. The contractor shall serve as the Command’s subject matter expert regarding (GCCS-J). GCCS-J functional support personnel shall operate the GCCS-J and contribute in using GCCS-J to provide USTRANSCOM with an accurate, near real-time representation of information that supports global mobility laydown and other USTRANSCOM assigned missions. The contractor will work with the Joint Staff and Joint Deployment Training Center on GCCS-J testing new features, troubleshooting, improving performance, documenting software problem reports and capability enhancements. The contractor shall recommend opportunities to leverage GCCS-J in common operating pictures, dashboard developments, and analytical opportunities so to improve the Global Operations Center situational awareness of monitoring key movements within the Joint Deployment and Distribution Enterprise. The contractor shall participate in projects, assignments, and meetings. The contractor shall provide GCCS-J familiarization level training within USTRANSCOM. The contractor shall develop and update Standard Operating Procedures, Policies, and Tactics, Techniques, and Procedures, point papers, talking papers, and briefings. The contractor shall communicate clearly and succinctly both written and orally and present products and ideas in a professional manner.

1.3.6 Task Area 6 - Essential Contractor Services

The Functional Commander has identified services described in PWS paragraphs 1.3.2.1 Subtask 1 and 1.3.2.2 Subtask 2 as Essential Contractor Services as defined and described in DFARS 252.237-7023 “Continuation of Essential Contractor Services”. Hereafter, the personnel identified by the contractor to perform these services shall be referred to as “ Essential Contractor Personnel.”

The Contracting Officer (CO), as required to comply with or perform pursuant to DoD requirements, shall direct the contractor to comply with requirements intended to safeguard the safety and health of Essential Contractor Personnel. The CO may communicate the requirements through a letter of notification or other means, and subsequently modify the contract to incorporate the requirements.

Within twenty (20) business days after contract award, as defined in PWS paragraph 2.1, the contractor shall provide a written list of Essential Contractor Personnel to the Contracting Officer or designee. The list shall identify individual employee names and their work tasks under this contract.

Essential Contractor Services Plan. The Contractor shall provide a plan for Essential Contractor Services. The plan shall include provisions for maintaining system availability as described in PWS paragraph 1.3.2.1 during exercises and contingencies.

2. Service Delivery Summary.

2.1 Deliverables/Delivery Schedule. Deliverables shall meet professional standards and meet the requirements set forth in contractual documentation. The contractor shall provide deliverables electronically in Microsoft Office (Word, Excel, PowerPoint, Project, etc) formats pursuant to the following schedule.

Deliverables in electronic format shall be delivered via DoD SAFE or DOTs Web Transfer Portal.

The Government asserts unlimited rights apply to any prior and current requirement and are described in Asserted Rights column related to this development effort. “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.

The delivery schedule below is described either in terms of calendar days from the date of task order award or in calendar days when other projects or program elements are dependent upon the delivery, e.g., five

(5) calendar days after draft plan approved.

PWS

Para

Deliverable Title Delivery Schedule Asserted Rights

1.3.1.1 Subtask 1

Program Review and Report Quarterly Shall be provided NLT 10 business days after the start of each quarter.

Unlimited

Para

Deliverable Title Delivery Schedule Asserted Rights

1.3.1.1 Subtask 2

TOMP Initial – within ten (10) business days of the task order start date Final – within five (5) business days of Government comment

Unlimited

1.3.2.2.1 Meeting Minutes/Summaries Within ten (10) business days after the meeting

Unlimited

1.3.2.2.2 JOPES Account Administration Report Monthly NLT tenth (10) business day of the month

Unlimited

1.3.2.2.4 Report System Degradation Report within 4 hours of event occurring

Unlimited

1.3.2.3.1 Test Plan When directed by the COR, shall

be submitted within ten (10) business days

Unlimited

1.3.2.3.2 JOPES Functional Testing Report Within ten (10) business days after test

Unlimited

1.3.2.4 JOPES Error Processing Report and

System Status Report

Weekly, day determined by Government Task Lead

Unlimited

1.3.3.2.1 Minutes/Summaries of Meetings Within ten (10) business days after the meeting

Unlimited

1.3.3.2.2 TransViz User Account Management

Functions

Monthly, NLT Tenth (10) business day of the month

Unlimited

1.3.3.2.4 TransViz Usage reports When directed by the Government Unlimited

1.3.3.2.5 TransViz CONOPS and TransViz

User’s Manual

Software impact assessment:

within 3 calendar days of completion of test period.

If updates are required, updated documents due with software release to Production

Unlimited

1.3.3.2.6 TransViz Configuration Activity Report Monthly, NLT Tenth (10th) business day5th business day

Unlimited

1.3.3.2.7 MSR Monthly, NLT Tenth (10th)

business day 5th business day

Unlimited

1.3.3.3.1 TransViz Test Plan End of Day following the review Unlimited

1.3.3.3.1 TransViz Functional Test Reports Within ten (10) calendar days of completion of test period

Unlimited

1.3.4.1.1 System Metrics Monthly, NLT Tenth (10th)

business day

Unlimited

1.3.4.1.2 Process Metrics Monthly, NLT Tenth (10th)

business day

Unlimited

1.3.4.1.3 Policy Metrics Monthly, NLT Tenth (10th)

business day

Unlimited

1.3.5.1 GCCS-J Test Synopsis Within five (5) business days of completing of test period

Para

Deliverable Title Delivery Schedule Asserted Rights

1.3.5.1 GCCS-J Familiarization Training After

Action Repot

Within five (5) business days of completion of training

Unlimited

1.3.6 Written list of Essential Contractor

Personnel

Within 20 business days after contract award

Unlimited

4.4.1 Transition Plan NLT twenty (20)thirty (30)

business days prior to contract scheduled end date

Unlimited

4.3.1 Open Task List NLT twenty (20)thirty (30)

business days prior to contract scheduled end date

Unlimited

4.6 Temporary Duty Trip Report Within five (5) business days after return

2.2 Performance Objectives. The Service Delivery Summary (SDS) represents important contract objectives that, when met, will ensure contract performance is satisfactory. Although not all PWS requirements may be listed in the SDS, the contractor is fully expected to comply with the requirements in the PWS.

PWS Para Performance Objective Performance Threshold 1.3.1 Task Area 1 Contract- Level and Task Order Management

Subtask 1: Assign a Team Leader to effectively manage PWS requirements and write and provide a Quarterly Program Review Report.

Subtask 2: Compliance with approved Task Order Management Plan (TOMP).

100% inspection to ensure timely submission and completeness of deliverables.

90% compliance rate is acceptable

1.3.2 Task Area 2 JOPES Functional Management

Subtask 2: Provide systems support in the areas of JOPES account administration, formulation of SOPs and perform JOPES database management support. Perform daily status check of JOPES system status. Provide a weekly written report on JOPES system status. Monitor, troubleshoot, analyze and report system degradation.

Coordinate scheduled server and system outages to ensure the command maintains operational capability.

100% inspection of deliverables to insure:

Deliverable submission is timely 90% of time.

Recommended solutions are realistic and achievable 100% of the time.

Subtask 3: Functionally test new applications and application upgrades and provide written functional test reports, recommending solutions for necessary application improvements; review JOPES documentation for correctness and applicability as necessary; and provide functional and technical support for JOPES demonstrations.

Subtask 4: Provide on-going error processing with weekly error rate metrics reports. Ensure currency of JOPES reference files.

Subtask 5: Coordinate training for USTRANSCOM with the Joint Deployment Training Command (JDTC) Mobile Training Team (MTT).

Subtask 6: Will be liaison to JOPES communities for USTRANSCOM

1.3.3 Task Area 3 TransViz Functional Management

Subtask 2: Provide systems support in the areas of TransViz account administration, formulation of standard operational procedures, perform TransViz data management support. Analyze data processing transactions and resolve anomalies.

Perform daily status check of TransViz system status. Monitor, troubleshoot, analyze, and report system degradation.

Coordinate scheduled server and system outages to ensure the command maintains operational capability.

Subtask 3: Functionally test new applications and application upgrades and provide written functional test reports, recommending solutions for necessary application improvements; review TransViz documentation for correctness and applicability as necessary; and provide functional and technical support for TransViz demonstrations.

100% inspection of deliverables to ensure:

Deliverable submission is timely 90% of time.

Recommended solutions are realistic and achievable 100% of the time.

1.3.4 Task Area 4 Research and Analysis Support

Subtask 1: Develop and provide Systems Metrics indicating the ability of the systems to provide required information.

100% inspection to ensure timely submission and completeness of deliverables.

1.3.4 Task Area 4 Research and Analysis Support

Subtask 2: Develop and provide Process Metrics indicating adherence to and adequacy of deployment and distribution processes.

Subtask 3: Develop and provide Policy Metrics indicating adherence to and adequacy of deployment and distribution policies.

Deliverable submission is timely 90% of time.

6.2. Cyber-Incident

Reporting

Provide timely cyber-incident reporting. No more than one late cyber-incident report or unreported cyber-incident in a twelve (12) month period.

3. General Equipment (GE)/Government Furnished Information. The Government will supply computer equipment for on-site contractors. Contractor may not be sole user of furnished computer equipment and therefore coordination with other contractors and administrators may be necessary. The Government will furnish appropriate user IDs and passwords for shared resources. The Government will provide necessary facilities such as office space and support. GE issued under this contract shall be for official use only.

4. General Information.

4.1 Place of Performance. The Contractor shall perform PWS tasks at Scott Air Force Base (SAFB), Illinois or Government-owned/controlled facilities in the greater Metropolitan St Louis area. The Government will provide six (6) workspaces at USTRANSCOM, SAFB. The Contractor shall provide space for any additional personnel. Telework by contractor personnel will be allowed on a case-by-case basis. The Government will determine and approve the requirements that can be supported via telework.

4.2 Period of Performance (PoP). The PoP is a base period with four 1-year option periods. Exercise of the option periods will be at the sole discretion of the Government. The PoP is as follows:

Base period: 1 October 2025 – 30 September 2026 (FY26).

Option period (OP) 1: 1 October 2026 – 30 September 2027 (FY27).

OP 2: 1 October 2027 – 30 September 2028 (FY28).

OP 3: 1 October 2028 – 30 September 2029 (FY29).

OP 4: 1 October 2029 – 30 September 2030 (FY29).

4.3 End of Contract Transition.

4.3.1 Transition Planning. The Contractor shall provide the Government with a transition plan no later than twenty (20) business days prior to the end of the contract, as defined in PWS paragraph 2.1, that provides for conveying open work and associated materials and assets in their possession to the Government. The contractor shall provide the Contracting Officer Representative (COR) a complete listing of open tasks indicating the status of completion and any performance issues associated with them as part of the TOMP. The report is due no later than twenty (20) business days prior to the contract scheduled end date, as defined in PWS paragraphs 2.1 and 2.2.

4.3.2 Transfer of Materials. The contractor shall transfer to the Government intellectual and real property belonging to the Government which was generated, purchased on behalf of, or provided by the Government for the performance of the work within this contract. The contractor shall provide the source code and executables for software developed and implemented on systems. Some examples would be code or scripts used to perform automated system backups, the monitoring of system processes, web development, code to check for security concerns etc. The contractor acknowledges that anything developed at the expense of the Government during the PoP is the property of the

Government. Electronic copies of the scripts shall be submitted to the Government for baseline control.

4.3.3 Sufficient Personnel. The contractor shall provide a sufficient number of personnel to ensure effective transfer of work in progress so as not to impact mission accomplishment.

4.4 Duty Day Support. The contractor shall provide functional and technical support to USTRANSCOM’s applicable system and application users during normal duty hours (0700 – 1700 (Local)), Monday through Friday, excluding Government holidays. During contingency operations, the Government may require the contractor to augment support for 24x7 operations to maintain rapidly changing asset availability and port constraint configurations.

4.5 On-Call Support. The demands placed upon equipment resources and the availability of personnel and facilities may occasionally require contractor personnel to work during other-than-normal duty hours (0700 – 1700, Local), such as in support of USTRANSCOM and TPFDD Refinement Conference attendees. The contractor shall maintain a 24-hour, 7-day week on-call capability with a 2-hour on-site response capability. The contractor shall provide on-call assistance, when necessary, in support of customer and system requirements.

4.6 Travel. USTRANSCOM will identify travel requirements. The contractor shall be responsible for scheduling travel arrangements associated with a TDY. The Government will normally reimburse contractor travel subject to the limits outlined in the Joint Travel Regulations and the Federal Acquisition Regulation (FAR). The contractor shall identify personnel who will be traveling in sufficient time to obtain the lowest possible rates for airfare, rental car, and lodging. In the event the Government cancels a trip after purchase of a restricted airfare ticket, the contractor will be reimbursed for the cost and penalties through the standard invoice process. The contractor shall submit a written trip report within five (5) business days of return for each trip.

4.7 Inspection and Acceptance. Work performed under this statement of work and final deliverables are subject to inspection and acceptance by the Government.

4.8. Non-Disclosure Agreements (NDA). The Government will require contractor personnel to sign a NDA to protect non-public information of other contractors or the Government.

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

5.1 General Security Information.

The majority of daily work associated with this PWS is on classified information/systems at the SECRET level, and/or classified facility at the SECRET level during performance of this contract/task order. Specific security requirements are identified in this section of the PWS and the DD Form 254 (DoD Contractor Security Classification Specification). A completed/signed DD Form 254 will be attached to the contract.

5.2 Citizenship and Clearance Requirements

The contractor’s, subcontractors, and/or partner’s personnel performing services under this contract/ task order shall be citizens of the United States of America. Overall, 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. Non-US citizens are not eligible for Common Access Cards (CACs) unless they meet the parameters stated in Department of Defense Manual (DoDM) 1000.13, volume 1.

All personnel that will have Information Technology (IT) / Automated Data Processing (ADP) privileged access (i.e. Privileged Users) to US Information Systems (IS), and/or classified information, classified systems, or unclassified areas, shall be US citizens. Foreign Nationals or Local Nationals employed by the DoD are not authorized to have privileged access to US Information systems.

5.3 IS Roles/Categories and Associated Suitability Requirements (Federal Investigative Standards).

Some positions performing services in support of this requirement may require IT/ADP privileged access. The IS roles/categories and the number of personnel assigned to each role is approved by the COR or the CO before the start of the contract/task order. The contractor shall comply with the appropriate provisions of applicable security regulations while assigned to this contract/task order for DoD and USTRANSCOM. The following guidance will be followed when determining background investigation levels for this contract/task order depending on requirements:

IS Role/Category Classified Access

Required Investigation

General User (Non-Privileged Access)

NO Tier 1 (T1)

General User (Non-Privileged Access)

YES Tier 3 (T3)

Privileged User (e.g. System Administrator)

NO Tier 5 (T5)

Privileged User YES Tier 5 (T5) NOTE: USTRANSCOM Joint Security Office (TCCS-S) will initiate/administer Tier 1 investigations to determine CAC eligibility only, classified access will not be granted based on the Tier 1 investigation. Tier 3 and Tier 5 investigations are the responsibility of the contractor. It is incumbent upon the contractor to have the appropriate investigations completed upon the start of the contract/task order.

5.4 Security Clearance and Special Access Requirements

All positions on this contract/task order, require a minimum of either an interim SECRET granted by the Defense CounterIntelligence and Security Agency (DCSA) Vetting Risk Operations (VRO) or a completed adjudication of SECRET granted by the DCSA Consolidated Adjudication Facility Services

(CAS).

5.5 Facilities Clearance (FCL)

The contractor must have a valid FCL at the SECRET level. FCL procedures and security guidelines for adjudicative requirements are outlined in 32 Code of Federal Regulations (CFR), 117. FCLs and interim FCLs must be awarded by the DCSA Facility Clearance Branch.

5.6 Personnel and Facilities Clearance Validation

Upon contract/task order award, the USTRANSCOM contracting team will send TCCS-S the Contractor unique Commercial and Government Entity (CAGE) code for FCL verification via the National Industrial Security System (NISS). The contactor will submit names of the contractor personnel performing on the contract/task order to the USTRANSCOM contracting team, who will provide to TCCS-S for vetting through the DoD personnel security system of record to ensure investigative and clearance requirements have been satisfied. This shall be completed before the COR/Mission Partner Affiliation Sponsor (MPAS) accesses the Mission Partner Identity, Credential, and Access Management (MP ICAM) system and creates CAC applications for contractor 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 employee will be denied the ability to work in support of this contract/task order.

5.7 CAC Issuance Procedures

5.7.1 Facility Security Officer (FSO) will verify, via the DOD personnel security system of record, contractors on the contract/task order have the required background investigation to obtain a CAC and provide those names to the CO/COR. Contractors that require a Tier 3 and Tier 5 investigation are the responsibility of the contractor. Contractors that only require a Tier 1 as determined by the FSO will submit to the TCCS-S Personnel Security Program Manager (through the CO or COR) an OF Form 306 (Declaration for Federal Employment) and a MP ICAM Form 1 with Section 1 completed. TCCS- S will initiate the SF-85 (questionnaire for Non-Sensitive Positions) via the National Background Investigation Services (NBIS) for completion and submission to DCSA, for Tier 1 investigations only.

5.7.2 At the same time, the contractor company will coordinate and obtain electronic fingerprinting for their employee. The third-party Company will "electronically" capture the applicant’s fingerprints, using the USTRANSCOM (SON, SOI, and ALC). Hardcopy fingerprint cards are NOT acceptable.

These steps will be completed before the COR/MPAS accesses the MP ICAM to create a CAC application.

Basic U. S. Citizen Contractor CAC Requirements:

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

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

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

Basic Non- U. S. Citizens Contractor CAC Requirements:

1. Meet (as direct/indirect DoD hire personnel) the investigative requirements for DoD employment as recognized through international agreements pursuant to DoDI 1400.25, Civilian Personnel Management, Volume 1231. In addition to these investigative requirements, a fingerprint check against the Federal Bureau of Investigation (FBI) criminal history database, an FBI investigations files (name check search), and a name check against the Terrorist Screening Database shall be required prior to CAC issuance IAW Office of Personnel Management Memorandum, “Final Credentialing Standards for Issuing Personal Identity Verification Cards under HSPD-12”, July 31, 2008.

2. Possess (as foreign military, employee, or contract support personnel), a visit status and security assurance that has been confirmed, documented, and processed IAW international agreements pursuant to DoDI 1400.25, Civilian Personnel Management.

CAC Applications:

1. The CAC applications must have an adjudicated Tier 1, Tier 3 or Tier 5 background investigation posted in the DoD personnel security system of record, or

2. 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 DCSA.

3. The MP ICAM MPAS will not approve the CAC application in MP ICAM until that MPAS has verified with, a member of USTRANSCOM TCCS-S one of the above requirements.

5.8 Access to Scott Air Force Base or USTRANSCOM Facilities

Upon receipt of the CAC, permanently assigned contractor personnel located at USTRANSCOM at SAFB, IL, may obtain a USTRANSCOM Facility Access Badge if the employee will be assigned physically on SAFB in a USTRANSCOM owned or managed facility, has a valid Visit Access Request on file, and attends Initial Security Training (IST) on-site. The Government will provide unrestricted access to facilities, consistent with security clearance eligibility and need-to-know, necessary for the on-site personnel to perform their work IAW the contract/task order. Contractor personnel assigned on-site at USTRANSCOM will wear and display a USTRANSCOM Facility Access Badge at all times while in USTRANSCOM facilities. 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/Surface Deployment and Distribution Command (SDDC) Buildings Any visit(s) by contractor personnel not permanently assigned to this contract/task order (i.e., company presidents, company security managers, contractor personnel not permanently assigned at SAFB, etc.) require an electronic visit access request be submitted using the DoD personnel security system of record. The DoD personnel security system of record visits can be forwarded to the Security Management Office (SMO) code: USTC-S-USTC-SDDC-1. The visit access request shall annotate the contract/task order number in the POC block of the visit access 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 access request for the current period of performance posted in the DoD personnel security system of record to SMO: USTC- S-USTC-SDDC-1. The visit access request will annotate the contract number in the POC block of the visit access request and the name/phone number of either the functional, COR or CO in the phone number block.

5.11 Supplemental Notes Regarding Visit Information in the DoD Personnel Security System of Record Personnel requiring access to Government facilities will properly complete the “Visit Information” block in the DoD Personnel security system of record. Otherwise, contractor employees will be denied access to the facility and classified and/or sensitive information. Also, prime contractors will annotate their contract number and subcontractors will provide the name of their company, with the prime contract number they are assigned to by the Prime, in the “additional information” block of the Visit table. A valid “Reason for the Visit” must be stated and the “visit access” must not exceed that of the contract.

5.12 Security and Emergency Operations Training

Contractor personnel physically assigned at USTRANSCOM/SDDC at SAFB shall attend/complete the following training as prescribed by DoD, USTRANSCOM and Air Force Instructions: Initial Security, Workplace Violence, Annual Security Awareness, Operations Security (OPSEC), DoD Antiterrorism Level I, Active Shooter/Attacker, Emergency Operations Combating Trafficking in Person (CTIP), Controlled Unclassified Information (CUI), Derivative Classification, and any Security Stand-down Day Training scheduled by the Commander, USTRANSCOM. Contractor personnel assigned elsewhere shall attend security training established by their respective Government security offices and/or installations.

5.13 Additional Security Conditions

All contractors assigned to USTRANSCOM/SDDC on SAFB will complete the contractor in-processing checklist before the start of work on this or any contract/task order in USTRANSCOM.

Contractors starting work on a new contract/task order will report to the Joint Security Desk, located in Building 1900, first-floor, Breezeway. In-processing includes the following:

• Verification of personal Identification.

• Verification of Visit Access Request in the DoD personnel security system of record

• Verification of the contractors Security Clearance eligibility in the DoD personnel security system of record

• Brief and sign the individual SF-312 (Security Agreement).

• Review of facility access requirements

• Issuance of a Temporary USTRANSCOM Facility Access Badge for the facility.

• Creation of a personnel security file.

• Complete North Atlantic Treaty Organization (NATO) Indoctrination

5.14 Derogatory Information.

Any member of the contracted company team (Program Manage, FSO, or other supervisory staff) aware of pending human resource activity of consequence (to include termination or suspension), behaviors or patterns of concern, or misconduct, to include reporting requirements in accordance with Security Executive Agent Directive (SEAD) 3 (for contractors with classified security eligibility), for any contractors supporting this contract/task order during the established period of performance will immediately contact the USTRANSCOM Joint Security Office (TCCS-S Attn: Industrial Security Program Manager. If the Government notifies the contractor that the employment or the continued employment of any contractor personnel is prejudicial to the interests or endangers the security of the United States of America or USTRANSCOM personnel, information, or assets, that employee shall be removed and barred from the worksite. This includes security deviations/incidents and credible derogatory information on contractor personnel as noted in the DoD personnel security system of record. Personnel who have incident reports posted in the DoD personnel security system of record will be denied the ability to support the contract/task order until the issues have been resolved and the incident has been removed in the DoD personnel security system of record. The contractor shall make any changes necessary in the appointment(s), at no additional cost to the Government. If any incident involves or may involve the mishandling of classified information or a potential Negligent Discharge of Classified Information, the USTRANSCOM Joint Security Office Attn: Industrial Security Program Manager will be notified within 24 hours during the normal work week and within 72 hours if the incident occurs over the weekend.

5.15 Accessing NATO Information.

No contractor employee will access NATO information without first being indoctrinated on NATO and having that access recorded in the DoD personnel security system of record. Any NATO information accessed will be only on Secret Internet Protocol Router Network (SIPRNet). Senders of NATO information will ensure the receiving network is accredited and the receiving point is a Sub- Registry or authorized Control Point. No NATO information will be stored with US classified information. Access to NATO information will be based on need-to-know, appropriate access level, and training. NATO information will not be disseminated to unauthorized users. NATO information will not be printed unless authorized by a USTRAANSCOM NATO-Sub Registry person in TCCS-S.

All printed NATO classified information must be strictly controlled and tracked in a NATO registry.

Contact the USTRANSCOM Sub-Registry for additional control measures. In accordance with the 32 CFR, 117, NATO briefed personnel will be re-briefed on an annual basis. USTRANSCOM will indoctrinate all on-site contractor employees and document in the DoD personnel security system of record. Contractor personnel assigned to USTRANSCOM facilities will be NATO briefed and debriefed by USTRANSCOM, with appropriate annotations to the DoD personnel security system of record. Company FSOs may take responsibility for all NATO refresher briefings per 32 CFR, 117 and record the date of the annual briefings in the contractor employee’s records.

5.16 Security Debriefing.

Contractor personnel physically working at USTRANSCOM at SAFB, IL, shall complete the out-processing checklist on the last day of the contract/task order or upon termination or reassignment from duties under the current contract or task order. The following closeout tasks will be completed, before the contractor departs:

• Review of the contractor’s personnel security folder.

• Review and debrief the contractor’s SF-312.

• Debrief anyone with NATO Access.

• Update and annotate the DoD personnel security system of record records reflecting the current status of the contractor at USTRANSCOM.

• Surrender CAC cards (with a copy of the revocation notice from the COR or MPAS) for those off-site, CACs will be physically mailed to TCCS-S for collection and…