2022.10.31 BSCM PWS.pdf

DRAFT for FY24 Re-compete

PERFORMANCE WORK STATEMENT

FOR

SURFACE DEPLOYMENT AND DISTRIBUTION COMMAND (SDDC)

BUSINESS SUPPORT & CONTAINER MANAGEMENT (BSCM)

24 June 2022

This page is left intentionally blank

PERFORMANCE WORK STATEMENT (PWS)

SDDC

BUSINESS SUPPORT & CONTAINER MANAGEMENT

Table of Contents

Contents

1. DESCRIPTION OF SERVICES

1.1. Background

1.2. Scope

1.3. Specific Tasks

1.3.1. Task 1: Contract Level and Project Management

1.3.1.1. Task 1 Subtask 1: Weekly Status Report (WSR)

1.3.1.2. Task 1 Subtask 2: Trip Reports

1.3.1.3. Task 1 Subtask 3: Employment Status Report

1.3.2. Task 2: Contract Transition and Knowledge Transfer and Transition (KT&T)

1.3.2.1. Task 2 Subtask 1: Ramp Up Requirements

1.3.2.2. Task 2 Subtask 2: Knowledge Transfer and Transition (KT&T) 10

1.3.2.3. Task 2 Subtask 3: Knowledge Receipt from Previous Contractor

1.3.2.4. Task 2 Subtask 4: Exit Requirements - Transition Period Activities (OPTIONAL)

1.3.2.5. Task 2 Subtask 5: Exit Requirements - Transition Period Activities (OPTIONAL)

1.3.2.6. Task 2 Subtask 6: Exit Requirements - Disposition of Government Furnished Property (GFP) (OPTIONAL)

1.3.2.7. Task 2 Subtask 7: Exit Requirements - Closeout Report

(OPTIONAL)

1.3.3. Task 3: PAT/JCM System Sustainment

1.3.3.1. Task 3 Subtask 1: Sustain PAT/JCM Functionality

1.3.3.2. Task 3 Subtask 2: Disaster Recovery/Contingency Operations .. 17

1.3.3.3. Task 3 Subtask 3: System Support

1.3.3.4. Task 3 Subtask 4: Tier II/III Help Desk Support

1.3.3.5. Task 3 Subtask 5: Software Testing Support

1.3.3.6. Task 3 Subtask 6: Support SDDC G3/G4

1.3.4. Task 4: PAT/JCM Enhancements

1.3.4.1. Task 4 Subtask 1: Enhance Application Capabilities

1.3.4.2. Task 4 Subtask 2: Software Testing Support

1.3.5. Task 5: New Software Development /Advanced Technology

Application & Cloud Migration

1.3.5.1. Task 5, Subtask 1: Contractor Development and Testing Environment Migration

1.3.5.2 Task 5, Subtask 2: Cloud One Migration

1.3.5.3 Task 5, Subtask 3: New Software Development/Advanced

Technology Application (OTIONAL)

1.4. Task 6: Configuration Management (CM)

1.4.1.1. Task 6, Subtask 1: CM Planning

1.4.1.2. Task 6, Subtask 2: Change Control

1.4.1.3. Task 6, Subtask 3: Asset Management

1.4.1.4. Task 6, Subtask 4: Configuration Control Board (CCB)

1.4.1.5. Task 6, Subtask 5: Source Code Configuration Control (Versioning)

1.4.2. Task 7: Training Support

1.4.3. Task 8: Customer Service

1.4.4. Task 9: Cargo Reconciliation

1.4.5. Task 10: Metrics and Reporting

1.4.6. Task 11: Information Assurance

1.4.6.1. Task 11, Subtask 2: Accreditation Sustainment

1.4.6.2. Task 11, Subtask 4: Writing Secure Application Software

1.4.6.3. Task 11, Subtask 5: Delivery of the Secure Application Software

2. DELIVERABLES

3. SERVICE DELIVERY SUMMARY

4. GOVERNMENT-FURNISHED AND CONTRACTOR-

FURNISHED EQUIPMENT AND INFORMATION

4.1. Government Furnished Equipment (GFE):

4.2. Government Furnished Information (GFI)

5. GENERAL INFORMATION

5.1. Place of Performance

5.2. Period of Performance

6. Travel and Other Direct Costs (ODCs)

6.1.1. Travel

6.1.2. Other Direct Costs

6.2. Software

6.3. Hardware

6.4. Cooperation with Other Contractors and Government Personnel

6.5. Contractor Employees

6.6. Contract Manager

6.7. Quality Assurance

7. SECURITY

7.1 General Security Information

7.2 Personnel Clearance Level (PCL) / Investigation Requirements ... 44

7.3 Company FCL

7.4 Clearance / Investigation Validation Checks

7.4 CAC Issuance

7.5 Scott AFB/USTRANSCOM/HQ SDDC Physical Access

7.6 Visits by Non-Assigned Contractors

7.7 Visits by Permanently Assigned Contractors

7.8 In & Out-Processing

7.9 Standard Form 312

7.10 Security Training

7.11 Total Employee Development (TED)

7.12 Security Permissions on DoD Systems

7.13 Security Permissions on DoD Systems

7.14 Security Compliance / Deviations

7.15 FPCON Impact on Work Levels (US Installations Only)

7.16 Security Regulation Compliance

7.17 Security Regulation Guidance

7.18 HQ SDDC Industrial Security Point of Contact

8. CYBER SECURITY

8.1 General Cyber Security Requirements

8.1.1 Handling and Protection of Non-Public Information

8.1.2 Operationally Critical Support

8.2 Cyber Security Assessments and Mitigation Plans

8.3 Cyber Incident Reporting

PERFORMANCE WORK STATEMENT

BUSINESS SUPPORT & CONTAINER MANAGEMENT (BSCM)

MISSION: The Military Surface Deployment and Distribution Command (SDDC) provides global surface deployment and distribution services to meet the nation’s objectives. SDDC is the Army component of the United States Transportation Command (USTRANSCOM). Other Component Commands of USTRANSCOM include the Navy component, Military Sealift Command (MSC), and the Air Force component, Air Mobility Command (AMC).

1. DESCRIPTION OF SERVICES

1.1. Background

Data and the information derived from data are key enablers to Department of Defense (DoD) managers and United States (US) warfighters. Managing the enterprise’s data and promoting its quality across the enterprise ensures the best possible information is available for making informed decisions regarding surface transportation. Integrating data from a number of disparate sources is required to provide the operators a clear picture of the surface transportation mission – from beginning to end. SDDC books, manifests, moves, tracks, bills, and pays for DoD cargo movement around the globe. SDDC must gather booking data from booking system(s), manifest data from manifesting system(s), and movement data from DoD and carrier systems in order to integrate and share that data across the SDDC enterprise and with other DoD entities. SDDC validates, corrects if needed, integrates, and forwards the data to all SDDC trading partners/systems. SDDC takes the data, applies the appropriate context and business rules, and provides the data to the appropriate user communities, giving them the tools to most efficiently execute DoD’s surface transportation mission.

SDDC’s Operations Directorate (G3) coordinates with other SDDC directorates, higher Commands, DoD shipping agencies, and commercial industry partners to facilitate ocean cargo transportation. The business model for ocean transportation is constantly evolving, and while many efforts have successfully streamlined ocean cargo documentation and tracking, the process still requires new software development and the maintenance and updating of existing business tools, software and practices.

With over 1,000 shippers and over 25 commercial ocean carriers participating in worldwide ocean cargo movement, G3 must constantly seek better ways to support and execute its operations. One of the objectives of this PWS is for the contractor to maintain and provide software solutions to support SDDC’s business and container management mission execution, to include the Documentation, Carrier Services/Compliance, Cost & Billing and Process and Systems sections of SDDC G3 and, the G4’s Global Container Management Branch. These software solutions will be achieved through a suite of tools and reporting capabilities under the Pipeline Asset Tool (PAT) “system of systems” umbrella, the program managed by the BSCM Program Manager’s Office (PMO). The BSCM PMO resides in the SDDC Communications Directorate (G6). PAT has approximately 2,000 total users and averages 200 unique users per day. Additionally, the contractor shall provide technical support, system administration, and database management for PAT as well as the applications that fall

Page | 6 under PAT and the Joint Container Management System (JCM). The JCM application has approximately 2,000 users and averages 100 unique users per day.

The PAT/JCM staging and production (hardware and software) environments are currently hosted within TRANSCOM’s GovCloud environment. Any phrase such as “operational environment(s)” or use of the word “environment(s),” without further specification, refers to the GovCloud hosted environments.

In addition, SDDC G6-IMA has an Information Assurance team that will provide certification and accreditation (C&A) support to the PAT/JCM applications. The contractor shall be responsible for providing application-specific documentation and information required for the applications’ C&A packages. Lifecycle Information Assurance guidance is provided in 1.3.11.

The Contractor or its subcontractors, may in the course of and pursuant to the contract, create, conceive, develop or contribute to material, including, but not limited to software, technical documentation, ideas, inventions (whether or not patentable), hardware, know-how, marketing plans, designs, techniques, documentation and records, regardless of the form or media, if any, on which such is stored and which the Contractor or subcontractor may attempt to mark or otherwise treat as proprietary in nature. In accordance with this contract, the Contractor and its subcontractors are prohibited from doing so and shall transfer to the Government, any such Proprietary Property which the contractor claims to conceive, develop or contribute in pursuit of this contract, and all intellectual and industrial property and other rights of any kind in or relating to the Proprietary Property, including but not limited to all copyright, patent, trade secret and trade-mark rights in or relating to the Proprietary Property. The Contractor or subcontractor assigns to the Government, any and all rights that it may have or obtain or intent to obtain, in or to the Proprietary Property. Material or information conceived, developed or contributed to by the Contractor or subcontractors, during, or outside work hours on the on behalf of the Government, or in pursuit of this contract, or through the use of the Government's assets shall also be governed by this Agreement.

All tasks shall be performed in accordance with (IAW) all regulations and guidelines as shown in Appendix B.

1.2. Scope

The primary purpose of the effort described in this PWS is to support the BSCM PMO in SDDC G6. The contractor shall sustain and improve existing PAT/JCM applications with integrated global container management capabilities presented via a single user interface, along with providing operational and technical support to SDDC G/G4 in the execution of all day-to-day aspects of surface cargo documentation. Support includes providing shipper and carrier data quality, surface cargo visibility, invoicing, import and export customs document processing, detention tracking, lift onboard

Page | 7 documentation submission and processing, approval of shipment delay and staging requests, and global container management. This PWS requires use of existing tools and technology to optimize daily operations and the overall surface cargo shipping and container management processes. It also requires the contractor to develop customized electronic solutions to new and ongoing surface cargo and container management requirements as part of the overall application Configuration Control Board (CCB) process.

The umbrella system supporting the existing tools and applications is PAT. PAT’s original purpose was to serve as an In-Transit Visibility (ITV) tool to track and monitor ocean cargo movement. While it still serves that purpose, it has since transformed into a multi-functional, agile tool that supports a variety of SDDC functions and reporting capabilities. PAT/JCM are modular and accessed using the Transportation Enhanced Access Management Service (TEAMS) website (https://eta-teams.transport.mil/), SDDC’s single sign on authentication service used to access a variety of transportation systems. Access to PAT through TEAMS requires a valid account, and a valid Common Access Card (CAC) or a valid Public Key Infrastructure (PKI) certificate. The contractor shall ensure all access to PAT is available only through TEAMS authentication. The contractor shall maintain and update all existing databases, web pages, applications, and tools associated with PAT as detailed in this PWS.

Software development to add new capabilities to support SDDC business operations and DoD container management is included in Task 5 in this PWS.

The contractor shall coordinate with the Government to ensure all activities are well synchronized and integrated with other SDDC and transportation management efforts.

Unless otherwise specified in this PWS, all days designated are calendar days. Normal duty hours are 0730 to 1630, Monday through Friday, exclusive of federal holidays.

The PWS includes the following task areas:

A. Overall Contract and Project Management

Task Area 1: Contract Level and Project Management (FFP) Task Area 2: Contract Transition and Knowledge Transfer (FFP)

B. Program Support

Task Area 3: PAT/JCM Sustainment (FFP) Task Area 4: PAT/JCM Enhancements (LH) Task Area 5: New Software Development / Advanced Technology & Cloud Migration (LH) Task Area 6: Configuration Management (FFP) Task Area 7:

Training Support (FFP) Task Area 8: Customer Service

Matthew Hellmann Is that Task 5?

Matthew Hellmann Are any task areas considered Mission Essential?

Arbelo, Deborah S CIV USARMY SDDC (USA) No

Matthew Hellmann Is there any historical workload (hours) or estimates we can provide the offerors so that they have a gauge on the level of effort required?

Arbelo, Deborah S CIV USARMY SDDC (USA) Added Appendix with Tasks and historic avg hours.

Page | 8

(FFP) Task Area 9: Cargo Reconciliation (FFP) Task Area 10: Metrics and Reporting (FFP) Task Area 11: Information Assurance (FFP)

The services provided within the scope of this contract are considered Operationally Critical Support (OCS) as defined in DFARS 252.204-7012 Safeguarding Covered Defense Information and Cyber Incident Reporting. Operationally critical support means “supplies or services designated by the Government as critical for airlift, sealift, intermodal transportation services, or logistical support that is essential to the mobilization, deployment, or sustainment of the Armed Forces in a contingency operation.” Sustaining/enhancing PAT/JCM is key to mission accomplishment.

1.3. Specific Tasks

1.3.1. Task 1: Contract Level and Project Management

This task consists of the contractor activities relating to the administration and management of the entire effort. The contractor shall provide project management of all projects and tasks within the scope of this contract. The principal project manager shall provide oversight of all tasks and projects within the scope of this contract and shall provide and prepare documents such as point papers, briefings, and meeting minutes related to the status and performance of projects. This task shall also provide administrative/technical support to the other tasks in preparation of deliverables.

1.3.1.1. Task 1 Subtask 1: Weekly Status Report (WSR)

The contractor shall provide a WSR every Thursday with issues for discussion during the Thursday PAT/JCM development meeting attended by the BSCM Program Manager (PM), Contract Officer Representative (COR), Alternate Contract Officer Representative (ACOR), G3 representatives, and all contractor personnel working under this contract. The WSR shall be no more than five pages and will outline the status of all new application development, enhancement, and maintenance activities.

WSR format should include information on the following: development in progress;

planned and completed releases; planned development; maintenance in progress;

planned maintenance, and personnel leave/travel schedule. Changes to the WSR format shall be agreed to by the COR/ACOR and the contractor Program Lead.

In addition, the contract lead shall attend a weekly meeting with the Global Container Management (GCM) and Army Intermodal and Distribution Platform Management Office (AIDPMO) teams to discuss JCM development status.

Deliverable: WSR weekly on Thursdays.

Deliverable: Security issues reported with risk mitigation COAs and a recommended COA in the WSR (see 1.3.11.4).

Page | 9

1.3.1.2. Task 1 Subtask 2: Trip Reports

Performance under this task order may require contractor travel within and outside the Contiguous United States. The following table represents an example of the estimated annual travel requirements for this work.

Location Number of Trips

Number of Days Number of People

595th TB – Kuwait 1 5 1 598th TB – Germany 1 5 1 599th TB – Hawaii 1 5 1 System Training (typically CONUS)

4 5 1

When not accompanied by Government personnel, the contractor shall submit a trip report within seven days of return that includes the following details at a minimum:

purpose, location, length of trip, individuals contacted and/or trained during trip (including the organization/Command of each individual), synopsis of all discussions, future actions identified, and/or issues of concern arising during trip.

1.3.1.3. Deliverable: Trip report provided within seven (7) calendar days after return from travelTask 1 Subtask 3: Employment Status Report

The contractor shall provide an employee status report (listing/spreadsheet) containing names and labor categories of personnel supporting the tasks identified in paragraph 1.2.

Employee Status Report should also include Common Access Card (CAC) number and account requirements. The initial report shall be provided within ten calendar days after contract award. Any updates shall be provided to the COR/ACOR within 24 hours of the change occurring.

Deliverable: Employment Status Report, within ten calendar days of contract award;

updated at Contract Initial Operational Capability (IOC), Contract Full Operational Capability (FOC), and within 24 hours of change in contractor staffing levels or personnel.

1.3.2. Task 2: Contract Transition and Knowledge Transfer and Transition (KT&T)

1.3.2.1. Task 2 Subtask 1: Ramp Up Requirements

The contractor shall perform all activities necessary for transition of BSCM PMO contractor support during the Base Period. The contractor shall complete administrative actions such as obtaining CACs and base access credentials (line badges), provide non-disclosure agreements, establish account access, and set-up development and testing environments (Command hosted or in the Cloud, as applicable). The contractor shall ensure personnel are available to accomplish all PWS tasks at the start of FOC, on 01 October 2023.

Bealer, Rachael N CIV TRANSCOM TCAQ (USA) Not a complete sentence

Done

Page | 10

The contractor shall have at least 25 percent (25%) of all proposed staffing on contract at the beginning of KT&T (05 September 2023). The contractor shall have 90 percent (90%) of proposed staffing available by FOC on 01 October 2023.

The contractor will provide a by-name list of employees requiring CACs with justification along with a listing of accounts to which each employee requires access.

Deliverable: By-name list of employees requiring CACs with justification, a listing of accounts to which each employee requires access, and subsequent status of CAC issue and account access. Initial list due within ten (10) calendar days of contract award;

updates within 24 hours of change in contractor staffing levels or personnel.

1.3.2.2. Task 2 Subtask 2: Knowledge Transfer and Transition (KT&T)

KT&T consists of two components facilitated by the Government: receiving KT&T from the previous contractor and providing KT&T to the future contractor at termination of this contract.

1.3.2.3. Task 2 Subtask 3: Knowledge Receipt from Previous Contractor

The contractor shall identify personnel to participate in the KT&T. KT&T will begin on 05 September 2023 and run through 30 September 2023. This will include Integrated Mission Support for Surface Deployment and Distribution Command (ISDDC) and Electronic Data Interchange (EDI) overview, infrastructure, data flow, software tools and processes, Commercial off the shelf (COTS), application administration, training, Help Desk, systems architecture, operations activities, security and sustainment activities. This will consist of classroom and over the-shoulder (e.g., observe current contractor working), phases as facilitated by the Government. All meetings during this period shall be conducted within a 10 miles radius of Scott Air Force Base. The incoming contractor shall ensure personnel representing the following areas are available to participate in the complete KT&T:

• Lead Engineer

• Database Administrator(s) (SQL)

• Operations Lead

• Sustainment Lead

• CM Lead

• Testing Lead

1.3.2.4. Task 2 Subtask 4: Exit Requirements - Transition Period Activities

(OPTIONAL)

The current contractor recognizes that the services under this contract are vital to the Government and shall be continued without interruption until the last day in the current Period of Performance. The contractor shall provide for knowledge transfer to facilitate

Page | 11 successful transition of duties and responsibilities from the current contractor to the successor contractor as well as to Government designated third parties as facilitated by the Government.

The incumbent contractor shall develop a forty-five (45) calendar day transition period exit plan. The Government shall review, at its discretion, the plan prior to approval.

The transition plan shall include the items in PWS paragraphs 1.3.2.3 through 1.3.2.5 below.

1.3.2.5. Deliverable: Forty-five (45) day Exit Plan with data described above, due seventy-five (75) calendar days prior to contract end dateTask 2 Subtask 5: Exit Requirements - Transition Period Activities

(OPTIONAL)

During the forty-five (45) calendar day transition period leading to contract end, the incumbent contractor shall provide the assistance and support required to ensure the orderly transition of all logistics support and provide transitional planning necessary to enable the succeeding contractor to commence uninterrupted operations at the end of the transition period. The contractor shall ensure the succeeding contractor personnel are permitted access to observe all operations, including workflow, priorities, scheduling, equipment handling/processing, safety, and security.

Familiarization visits shall not interfere with the activities of the incumbent contractor or Government personnel.

The current contractor shall document their strategy for transition of all tasks. The current contractor shall be responsible for preparation for all briefing materials and deliver the material to the Government prior to commencement of KT&T activities. The current contractor shall provide classroom and over the-shoulder (e.g. successor contractor observing current contractor work)transition to the successor contractor. The current contractor shall deliver the 45-day schedule to the Government due 75 days prior to the commencement of exit KT&T.

a. General Requirements. The transition shall include the following requirements:

• Provide System Recovery Contingency Plan should the system fail during transition, and establish the timing of the transition to minimally impact system operations

• Provide a Technical Issues and Problems Report so the Government and succeeding contractor have a clear understanding of the issues that shall impact or influence future activities and state of the system

• Initiate the transition activities with the succeeding contractor within five (5) business days of initiating the transition period

• Ensure the succeeding contractor has an opportunity to participate (i.e., over-the-shoulder observations, etc.) and collaborate with the incumbent contractor to implement software releases and patches in the BSCM environments

• Ensure the succeeding contractor has an opportunity to participate (i.e., , over-

Page | 12 the-shoulder observations, etc.) and collaborate with the incumbent contractor in processing software change requests (SCRs) (if SCRs are in-process during the transition period) and operating and sustaining the system

b. Knowledge Transfer. The Government will facilitate discussion between the incumbent contractor and the succeeding contractor to ensure successful knowledge transfer. The incumbent contractor shall provide the succeeding contractor’s program and technical staff system orientation, familiarization, and software code review to clearly define the system’s current state and explain the recurring PAT/JCM processes and activities. This transfer shall occur with minimal disruption to system operations.

The incumbent contractor shall support and allow the succeeding contractor to have hands-on familiarity with the system during the transition period. Knowledge transfer shall address and/or provide, at a minimum, the following areas:

• System operational, functional, and technical descriptions

• System functional and technical capabilities

• System engineering and design

• System security features

• End-to-end (E2E) code review

• All PAT/JCM and supporting COTS applications

• Tier 3 Help Desk and work order management processes

1.3.2.6. Task 2 Subtask 6: Exit Requirements - Disposition of Government Furnished

Property (GFP) (OPTIONAL)

The transition plan shall detail the prescribed processes for hand-off, receipt, and disposition of GFP. The transfer of GFP shall begin within ten (10) business days after the transition period start date and shall be completed no later than the last calendar day of the contract or task order. The contractor shall perform the following:

• Identify specific hardware models, versions, and configurations

• Provide the rationale for using the selected hardware

• Provide the current manuals and instructions for each hardware item

• Provide licensing and data rights information

• Provide all program-related current, backup, and/or historical data files kept on

CD, floppy disk, flash drives, or other storage media whether or not the files exist on GFP computer hard drives, to include program-related files developed and/or stored on non-GFP computing devices

• Provide copies of all files, programs, or other digitized information developed for the project kept on the contractor’s network drives

• The incumbent contractor shall not erase any data or programs from GFP computing devices without coordination and expressed written consent of the Government (i.e., the incumbent contractor shall not erase or “scrub” hard drives of any GFP computer) with exception of GFP laptops

• Ship GFP (i.e., hardware, software, etc.) to the Government as determined by the Government and at the Government’s expense. Formal shipping and

Page | 13 receipting of program and system documents and GFP will be IAW DoD instructions and directions and the Defense Federal Acquisiton Regulation Supplement (DFARS)

• Ensure all security badges, CACs, vehicle passes, and software access permissions are revoked and returned to the Government within the transition period

1.3.2.7. Task 2 Subtask 7: Exit Requirements - Closeout Report (OPTIONAL)

The following items comprise exit criteria for KT&T and shall be provided by the current contractor to the Government at least ten days prior to end of contract in a Closeout Report:

• The current contractor shall organize all work-related documents and files, store them on the designated shared drives, and provide a file plan outlining the file structure

• Status for each project shall be documented, to include recent, current, and pending actions

• The current contractor shall provide a listing of all COTS utilized in support of this contract and soft copies of all procedures and training materials developed as part of this task order

• The current contractor shall provide a complete list of all badges, vehicle passes, and

Government software access permissions by individual currently working on the task order

• The current contractor shall ensure no logistics or contract data is corrupted, changed, or altered in a manner that would cause damage to the Government

1.3.3. Deliverable: Contract Closeout Report with data described above NLT ten (10) business days prior to end of contractTask 3:

PAT/JCM System Sustainment

Any phrase such as “operational environment(s)” or use of the word environment(s),” without further specification shall refer to Cloud-hosted environments.

The contractor shall maintain, to include fixing defects, application software, tools, capabilities, servers, interfaces, databases, and related functionality in support of application user communities and the BSCM PMO. The contractor shall apply agile development methodologies in order to provide rapid support and capabilities to the warfighter. The contractor shall continuously maintain and update documentation on the systems architecture and of existing interfaces, data and software.

1.3.3.1. Task 3 Subtask 1: Sustain PAT/JCM Functionality

The PAT/JCM applications currently reside in the GovCloud’s production and Partner test (integrated test), environments. The program receives operational System Administrator and Database Administrator support from the support team of the SDDC Cloud IT Support Services (SCITSS). The contractor shall support the SCITSS as applicable, with any application-specific configuration, and/or software requirements within these environments.

The contractor shall ensure PAT/JCM tools and functions continue to support their associated purpose requirements. Current tools and functions include:

Page | 14

- Surface In-Transit Visibility (SITV) Module

- Shipper Performance Portal (SPP)

- Lift Onboard (LOB) Portal

- Carrier Performance Portal (CPP)

- Delay Request and Authorization Portal (D-RAP)

- Domestic Freight routing Request and Order (DFRRO)

- Invoice Process Portal (IPP) – including Container Return Management

- Customs Document Portal (CDP)

- Contract Decision Tool (CDT)

- Customs and Border Protection (CBP) Manager/Importer Security Filings

- Container Ownership Inventory Listing (COIL)

- Claims Portal

- PAT Global Administration

- PAT Unit Move Portal

- PAT One-Time-Only (OTO) Portal

- PAT Installation Outloading Capability Collection (OCC) Portal

- International Organization for Standardization (ISO) Register/Procurement

Approval Module – used to support the issue and tracking of container ISO numbers for government containers.

- Lease Module– used to support the issuing of delivery orders to procure lease containers and to manage/track customer lease funding accounts.

- Mobile Module - used to upload container inventory, maintenance, movement, and inspection information to JCM via a mobile handheld terminal.

- Military Inter-departmental Purchase Request (MIPR) Management Module

– (SDDC users only) - Used to track funding provided by external customers via MIPR

The contractor shall maintain and enhance the JCM application. JCM will consist of a Global Container Management database capability supported by a single user interface.

It will leverage container data provided by external systems or applications to include data from PAT, and other systems and applications as required via web services in order to provide data integration and management capabilities.

JCM application elements include the following:

Single Container Request – Provide one place for users to request or schedule containers to fulfill shipping requirements.

Container Sourcing – Container sourcing requires decision support capability to help container managers determine whether to fill a request with government-owned, government leased or commercial containers. This capability will support the purchase decision process for government leased and commercial containers.

Enhanced Container Accountability – Requires the ability to account for containers

Page | 15 for their entire lifecycle (from the time they are acquired until they are returned to their owners or disposed of). This includes tracking the status of containers throughout the distribution pipeline.

Execution Visibility – Execution visibility is the ability to collect planning and distribution information along with consolidation and containerization information.

Also includes the ability to provide accurate status to customers and provide command and control over movements.

Container Maintenance – Maintenance includes scheduling and tracking inspections, repairs, re- stenciling, and turn-in of containers.

Leased Container Invoice Validation Capability – The ability to verify costs prior to payment and verify completed payments for leased containers.

Lease Management – Allows for the management of container leases from the time containers are obtained until they are returned to owners.

The contractor shall update tools and applications as needed to support changes to the PAT/JCM information technology or business environments. The contractor shall document and update related business rules as changes occur to be provided within 5 business days of changes/updates. The contractor shall meet with the COR/ACOR and the Government Program Manager (PM) a minimum of once per week to discuss current capabilities and prioritize any proposed changes to existing software engineering priorities. The contractor shall maintain and update documentation on architecture of existing interfaces, data, and software as changes occur to be provided within 5 business days of changes/updates. The contractor shall ensure existing capabilities are documented and are Information-Assurance (IA) compliant according to current DoD IA requirements as described below in 1.3.11.2. Contractors maintaining or updating existing PAT/JCM software and web pages shall possess an Information Assurance Technical (IAT) Level II certification at a minimum.

The contractor shall ensure that the PAT/JCM modules, tools, and applications continue to support their associated functional requirements, to include:

- Uploading and validating carrier container detention invoices to manage and recommend payment of container detention invoices

- Uploading and processing of delay and staging requests and approvals. These will include generation of delay, staging and available for delivery EDI transactions.

- Processing, monitoring and reporting of shipment documentation including shipping instructions and customs documents

- Uploading and validation of ocean carrier LOB documentation to ensure timely and accurate cargo manifesting

- Providing authorized users access to the Booking Reconciliation tool within the LOB.

- Monitoring and reporting of carrier performance metrics (RDD, EDI and LOB submission compliance)

Bealer, Rachael N CIV TRANSCOM TCAQ (USA) Is there another reference to a weekly meeting that this should be tied to?

Page | 16

- Monitoring and reconciliation of cargo shipment records per defined business rules

- Providing authorized users access to ITV transactions to track containerized and break-bulk cargo from origin to destination

- Tracking and reporting on containers moving into, within, and out of locations worldwide with an emphasis on identifying and lowering detention costs

- Monitoring and reporting of US Government and Commercial Ocean Carrier container ownership

The contractor shall update and enhance modules, tools, and applications as needed to support changes to commercial surface cargo contracts and business rules.

The contractor shall compile, sort, store, and analyze surface cargo documentation and information pertaining to cargo documentation submitted by shipping agencies and ocean carriers. This documentation includes but is not limited to import and export customs documents, shipping instructions, documents supporting delay and staging requests and Lift-On-Board (LOB) reports. The contractor shall maintain document repositories such that these documents are accessible to SDDC personnel and external PAT/JCM users via the web. When necessary, the contractor shall research and resolve documentation discrepancies.

The contractor shall manage submission of customs documents via the PAT Customs Document Portal (CDP) for surface transportation movements managed globally by SDDC. The contractor shall identify and track customs documentation for all Combatant Command Areas of Responsibility via the CDP. Customs documents will be made available to SDDC personnel and other users as required via the web.

The contractor shall monitor Importer Security Filings (ISF) through the ISF VPN to Customs and Border Security (CBP).

The contractor shall monitor carrier submission and upload of LOB documents in the PAT LOB Portal for use and viewing by SDDC and other PAT users. The contractor shall also monitor submission of electronic documentation, to include shipping instructions, and take steps to ensure electronic submissions are available to SDDC and other PAT users via the web.

At a minimum, the contractor shall maintain the following existing capabilities related to Documentation Management:

• Delay request and staging documents

- Contractor shall ensure processing and uploading of delay request and staging direction documentation and making documents available to authorized users via the D-RAP.

• Customs documents

- Contractor shall process and upload customs documentation and make customs documentation available to authorized users via the CDP webpage.

• Lift Onboard (LOB) documents

Page | 17

- Documents uploaded by the ocean carriers to the LOB portal. The PAT LOB Portal is a repository of ocean cargo lift documentation that is used by SDDC personnel responsible for the timely and accurate manifesting of ocean cargo and by general Department of Defense users to track ocean cargo movements.

• Detention invoices

- Contractor shall ensure detention invoices are uploaded and accessible by all authorized users via the IPP

• Ocean Carrier Container Fleet lists

- Contractor shall ensure Ocean Carrier submitted container fleet lists are uploaded accessible by all authorized users via COIL

• Container Lease Invoices

- Contractor shall ensure container lease invoices are uploaded and accessible by all authorized users via the JCM Lease Management page.

The contractor will ensure that operational software is fully tested and provide functioning tools, modules, and applications installed and operating in the current production environment with no major defects, available to users via the web greater than 98.5% of the time.

In addition, the contractor wil ensure that data received through interfaces shall be integrated into Program databases no later than 24 hours after interface feed is provided.

The contractor will maintain accurate document repositories in each of the tools, modules, and applications that are accessible to all users via the web. Documents shall be available for export and download as required greater than 98.5% of the monthly available time.

Deliverable: Business Rules: The contractor shall document and update related business rules within 90 days of FOC and as changes occur.

Deliverable: Database Design documents. The contractor shall document and update related database design changes within 90 days of FOC and as changes occur.

1.3.3.2. Task 3 Subtask 2: Disaster Recovery/Contingency Operations

Maintain Disaster Recovery Environment.

The contractor shall work with the SDDC Cloud IT Support Services (SCITSS) team to ensure all required applications are correctly installed and configured. In normal circumstances, the contractor will be able to remotely access the system(s). In situations where remote access is not available, the contractor shall be required to access system(s) from the physical location. To ensure operationally correct software, the contractor shall work with the SCITSS team to install/configure application software.

Matthew Hellmann This is not a deliverable, but can be considered an SDS item.

Deborah

Matthew Hellmann This would not be listed in the Deliverable table as a deliverable, but instead in the SDS table below. Those are the most critical functions that must be met for satisfactory contract perform. In this case, the threshold for satisfactory perform of this item is 98.5% of the time the tools, modules and applications are installed and operating with no major defects.

Arbelo, Deborah S CIV USARMY SDDC (USA) Edited

Matthew Hellmann This is not deliverable; it is a task. Is this clearly spelled out?

Deborah Data feeds come into the application through several data interfaces. Then the data is integrated into the system.

Matthew Hellmann What are they delivering to the Government?

Arbelo, Deborah S CIV USARMY SDDC (USA) Edited

Matthew Hellmann This is not a deliverable, but can be considered an SDS item.

Matthew Hellmann See comment above on the SDS item.

Edited

Page | 18

The contractor shall provide support to the Government during contingency or emergency operations in accordance with approved disaster recovery and contingency operations plans. The contractor shall ensure resources/key personnel are available throughout an emergency in accordance with the established plan.

Disaster Recovery/Contingency Plan. Once a year, NLT 30 September, the contractor shall update the SCITSS’s plan for disaster recovery and/or contingency operations in coordination with the enterprise Disaster Recovery Exercise (DRE) solution and SCITSS team. The plan shall include the following: crisis emergency management (onsite and offsite) (technical and functional); disaster recovery; pre and post emergency operations requirements; and fail-over management.

Exercise Operations. Shall assist in the development of test plans as required by SDDC.

Deliverable: Updated PAT/JCM Disaster Recover Plans once per year NLT 30 September.

1.3.3.3. Task 3 Subtask 3: System Support.

Development and Test Environment The contractor shall ensure the PAT/JCM test and development environments are fully operational and support rapid/agile software engineering and testing.

Development and Test Support The contractor shall work with SDDC IA staff to ensure compliance with current IA guidance (see paragraph 1.3.11). The contractor is responsible for assisting the Government SCITSS team’s system administrators in loading application and COTS software on the Test and Development, Staging, Production, and Disaster Recovery Exercise (DRE) servers/platforms.

Operational Support The contractor shall provide a support role to the SCITSS in monitoring server and database performance, ensuring connectivity, and complying with all IA and C&A requirements in all computing environments. The contractor shall participate in the enterprise change management processes. The contractor shall identify and document current and planned interface, data, software, or technical changes. Supporting the PAT/JCM, and Container Management Module (CMM) hardware in their respective environment(s) requires knowledge of the following:

- Configuration skills within an n-Tier enterprise architecture and network topology

- Virtualized server environments

- Windows 2008 (and higher) servers

- SAN devices

- Information Assurance Vulnerability Assessments (IAVAs)

- Security Technical Implementation Guides (STIG’s)

The contractor shall be required to test and troubleshoot PAT/JCM applications after Common Computing Environment (CCE)/Common Development Environement (CDE) outages/upgrades that typically occur during non-duty hours. The contractor shall coordinate with the SCITSS if they discover any issues after the outage and may be

Bealer, Rachael N CIV TRANSCOM TCAQ (USA) Can we remove this or consolidate with the paragraph above?

Page | 19 required to assist the SCITSS to restart some services to bring the PAT/JCM back to normal operations. Typical CCE maintenance outages occur twice each month, on alternating Wednesdays.

Deliverable: Operational Software: Fully tested and functioning tools, modules, and applications installed and operating in the current production environment with no major defects, available to users via the web greater than 98.5% of the time.

1.3.3.4. Task 3 Subtask 4: Tier II/III Help Desk Support

The contractor shall provide responsive Tier II/III help desk support during normal duty hours to the PAT/JCM users. All tickets resolved within five business days. The PAT/JCM Tier II/III help desk support shall include the detailed analysis and troubleshooting of problems referred from Tier I. The contractor shall log problem status and resolution information in the SDDC ticketing database and shall work with SDDC’s Tier I helpdesk personnel to identify trends and areas for improvement. In addition, Tier II help desk support shall perform a variety of administration tasks such as answering email from PAT/JCM users and notifying Tier I and the user community of planned system outages, application changes, and technical issues. The contractor shall perform help desk support during after-duty hours in case of a system outage, if required. PAT/JCM average approximately 15 Tier II/III calls each per day.

Deliverable: Tier II/III help desk support: All tickets resolved within five business days.

1.3.3.5. Task 3 Subtask 5: Software Testing Support

The contractor shall perform software testing as an integral component of the program’s overall product quality assurance. Testing shall consist of unit and integrated testing activities. The contractor shall create test cases and plans to provide end-to-end testing of all developed applications, reports, scripts, scenarios, procedures, extract-transform-load (ETL), and other software entities. The contractor shall create and maintain test plans; updated documents are required to be delivered quarterly, starting within 120 days of contract start. Routine changes require significantly fewer testing resources than the more complex changes but testing resources must be available to support both types of changes. Testing should be sufficient to identify and minimize defects released to the production environment. Testing shall occur rapidly in synchronization with the development effort to ensure the most rapid fielding of enhancements/new capabilities. A major defect is defined as a defect that prevents the accomplishment of an operational or mission essential capability or jeopardizes safety, security, or other requirements designated “critical” where no work-around solution is known.

Deliverable: Sustainment Test Plans: Updated quarterly to start within 120 days of contract start. Test results shall be captured within the Enterprise Change Control Tool (CCT) as the tests are conducted.

1.3.3.6. Task 3 Subtask 6: Support SDDC G3/G4

The contractor shall provide functional expertise to provide on-site support and training

Page | 20 to the SDDC G3/G4 at a minimum of one day per week. The contractor shall assist the PAT/JCM user communities by answering operational questions concerning the use of the applications. The contractor shall build specialized reports within the PAT/JCM applications to answer specific questions. The contractor shall also capture the users’ emerging requirements and build appropriate change requests for those requirements.

These emerging requirements shall be documented as defined in the PAT/JCM Configuration Management Plan (CMP) and shall follow normal CM processes as defined in Task 6 (1.4.1.1).

Deliverable: Minimum of one day per week on-site training support to the SDDC G3, as required.

1.3.4. Task 4: PAT/JCM Enhancements

1.3.4.1. Task 4 Subtask 1: Enhance Application Capabilities

Automated information systems require changes as functional requirements and operations change. Therefore, upon coordination with the Government BSCM PM, contractor shall develop system enhancements to include custom databases, new/updated interfaces, web pages, reports, and functions to streamline or supplement SDDC business and container management processes. The contractor Lead Program Manager shall lead a weekly status review meeting, with the Government PM, COR/ACOR, and all contractor personnel to review the status of all ongoing updates, repairs, and changes to existing capabilities and discuss and validate new system enhancement requirements using the CCB process to track. Users and the Government PM will identify high priority projects via a SCR form, for development evaluation and scheduling.

Changes to the applications may include, but not be limited to, additional data sources, interface partners, additional reports to support the user base, migration of capability from other programs to eliminate duplicative efforts, and enhancing capabilities based on evolving business and container management automation requirements. Typically, routine (minor) enhancements include changes to reports, and/or the display of new data elements already available within the existing database. Routine changes within the PAT program average less than 40 man-hours to develop and test. Changes that are more complex may include new interface partners or new capabilities, and webpages that require more resources to deploy.

The contractor shall develop and test enhancements that are more complex and schedule release in coordination with the Government PM as required. PAT averages approximately 15 complex changes per year and approximately 250 routine changes per year. JCM averages approximately 5 complex changes per year and 100 routine changes per year.

PAT and JCM have historically released on a monthly basis. Software change releases must meet scheduled release dates +/- 10 business days. The contractor shall coordinate delays with the Government PM/COR. The contractor shall design, develop and implement secure applications and configurations in accordance with current DoD guidance. Refer to paragraph (1.3.11 for a description of the information assurance

Page | 21 tasks required for this effort.

The contractor shall stay abreast of new technologies. The contractor shall discuss options with the BSCM PM to determine if the program will leverage these new capabilities. Enhancements that have already been identified for incorporation into PAT or JCM include the following:

Pipeline Asset Tool – Leverage mapping services from TGIS Program

Pipeline Asset Tool – Provide a replacement for ISDDC’s CIET capability in the PAT EDI Generator of the SITV module. Completed NLT 30 September 2024.

Container Management Mobile Capability Enhancement The contractor shall engineer and maintain enhanced JCM application software, related functionality, and capabilities to support installation on commercially available handheld devices such as common smart phones or tablets (i.e., Apple, Android, etc.).