09.27.2023 GFM PWS.pdf

HTC711-25-F-DXXX

PERFORMANCE WORK STATEMENT (PWS)

FOR

SURFACE DEPLOYMENT AND DISTRIBUTION COMMAND (SDDC)

GLOBAL FREIGHT MANAGEMENT (GFM)

PERFORMANCE WORK STATEMENT (PWS)

SDDC

GLOBAL FREIGHT MANAGEMENT

Table of Contents

Vision Statement:

1.0 Introduction

1.1 Background

1.2 Scope

1.2.1 Definitions

1.2.2 Information Sharing

1.2.3 Application Sustainment, Enhancement, Development Methodologies and Processes

1.3 Specific Tasks

1.3.1 Task Area 1: Contract Level and Project Management (FFP)

1.3.1.1 Task 1 Subtask 1: Monthly Status Report (MSR)

1.3.1.2 Task 1 Subtask 2: Master Release Schedule (MRS)

1.3.1.3 Task 1 Subtask 3: Quarterly Program Management Reviews (QPMRs)

1.3.1.5 Task 1 Subtask 5: Integrated Product Team (IPT) Meetings

1.3.1.6 Task 1 Subtask 6: Technical Exchange Meetings (TEM)

1.3.1.7 Task 1 Subtask 7: Employment Status Report

1.3.1.8 Task 1 Subtask 8: Contractor Manpower Reporting

1.3.2 Task Area 2: GFM Application Sustainment (FFP)

1.3.2.1 Task 2 Subtask 1: Functional Requirements and Documentation

1.3.2.2 Task 2 Subtask 2: Interface and Electronic Commerce/ Electronic Data Interchange (EC/EDI) Support

1.3.2.3 Task 2 Subtask 3: User Training and Training Manuals - Distant Web Learning

1.3.2.4 Task 2 Subtask 4: System and Database Administration

1.3.2.5 Task 2 Subtask 5: Tier II/III Help Desk Support

1.3.2.6 Task 2 Subtask 6: Unscheduled Downtime Events

1.3.2.7 Task 2 Subtask 7: Disaster Recovery Exercise (DRE)

1.3.2.8 Task 2 Subtask 8: Data Analysis

1.3.2.9 Task 2 Subtask 9: Software Implementation

1.3.2.9.1 Task 2 Subtask 9.1: Software Development Unit Test (SDT)

1.3.2.9.2 Task 2 Subtask 9.2: Software Reviews and Software Version Description (SVD)

1.3.2.10 Task 2 Subtask 10: Bills of Lading (BLs)

1.3.2.11 Task 2 Subtask 11: Remote Carrier Access

1.3.2.12 Task 2 Subtask 12: Cloud Environments

1.3.3 Task Area 3: Enhancements (FFP)

1.3.3.1 Task 3 Subtask 1: Enhanced Capabilities Development

1.3.3.2 Task 3 Subtask 2: Enhancement Development

1.3.3.3 Task 3: Team Composition

1.3.3.4 Task 4: Enhancement Projects

1.3.4 Task Area 4: Emerging Capital Projects (LH): (Optional)

1.3.5 Task Area 5: Application & Oracle System Operations & Maintenance

1.3.5.1 Task Area 5 Subtask 1: Database Management Systems (DBMS) Oracle Administration

1.3.6 Task Area 6: Configuration Management (CM) (FFP)

1.3.7 Task Area 8: Information Assurance (IA) (FFP)

1.3.8.1 Task 8 Subtask 1: Writing Secure Application Software

1.3.8.2 Task 8 Subtask 2: RMF Accreditation Sustainment

1.3.8.3 Task 8 Subtask 3: Covered Defense Information (CDI) (DFARS 252.204-7012)

1.3.8.4 Task 8 Subtask 4: Handling of Non-Public Information

1.3.8.5 Task 8 Subtask 5: Operationally Critical Support (OCS)

1.3.8.5.1 Cybersecurity Incident Reporting

1.3.9 Task Area 9: Contract Transition and Knowledge Transfer (FFP)

1.3.9.1 Task 9 Subtask 1: Successor Contractor Transition Phase-In

1.3.9.2 Task 9 Subtask 2: Incumbent Contractor Transition Phase-Out (OPTIONAL)

1.3.9.3 Task 9 Subtask 3: Phase-Out Transition Plan

1.3.9.4 Task 9 Subtask 4: Transition Execution

1.3.9.5 Task 9 Subtask 5: Exit Requirements

2.0 Deliverables and Data Rights

2.1 Service Delivery Summary

2.2 Quality:

3.0 Place of Performance/Hours of Operations

3.1 Travel (Cost)

3.2 Other Direct Costs (ODC)

3.3 Transfer of Materials

3.4 Period of Performance

3.5 Transfer of developer environment

4.0 Special Requirements

4.1 Security Regulation Guidance

4.2 Applicable Directives

5.0 SECURITY (PHYSICAL, PERSONNEL, INFORMATION, INDUSTRIAL, OPERATIONS,

ANTITERRORISM, and FORCE PROTECTION) REQUIREMENTS

6.0 General Information

Appendix A: GFM Application Descriptions

Appendix B: Environments Supported

Appendix C: Regulation Guidance:

Appendix D: GFM Trading partners

Appendix E: GFM Data Exchange Templates

Appendix F: Acronyms

Appendix I: Programmatic State:

Appendix J: Government Furnished Equipment (GFE)

Appendix K: Achieve Compliance with SDDC Application Modernization Strategy

PERFORMANCE WORK STATEMENT

GLOBAL FREIGHT MANAGEMENT

Vision Statement:

This contract will enable sustainment of the ability to access commercial shipping of freight via motor, rail, barge, pipeline, air and small package via tender and contract utilizing the Global Freight Management (GFM) system. The successful execution of this contract will provide System Development, Maintenance, and Sustainment for GFM System.

1.0 Introduction

The Military Surface Deployment and Distribution Command (SDDC) must expertly maintain software and hardware related to its transportation systems to effectively manage the 24-hour worldwide operation of moving freight for SDDC customers. SDDC requires the Contractor to provide comprehensive, high-quality software for GFM related transportation systems and report results effectively in order for SDDC to make critical implementation decisions.

1.1 Background

SDDC is the surface transportation component of the United States Transportation Command. SDDCs primary functions include worldwide port operations, global traffic management, deployability engineering, and development of integrated transportation systems. SDDCs Deputy Chief of Staff for Information Management

- Chief Information Officer (IM/CIO) supports SDDC’s mission by designing, developing, implementing, and operating standard Department of Defense (DOD) transportation systems for which SDDC has been assigned responsibility. The Surface Cargo Branch supports the SDDC mission by managing GFM. GFM is the capstone automated execution system of the Defense Transportation System (DTS) for the movement of domestic freight. It is also used to a certain degree as an outside the continental United States (OCONUS) shipping tool. Users access the GFM system through Transportation Enhanced Authentication Management Services (TEAMS) System via an Internet connection 24 hours a day, 7 days a week. GFM currently supports the development, testing, staging/non-prod, and production for all small applications in traditional data centers (physical) and Dev/Ops in a Cloud Computing environment (virtual).

1.2 Scope

This Performance Work Statement (PWS) is to provide technical services and Software Development Life Cycle (SDLC) management support of the GFM system and software applications to comply with the Joint Chiefs of Staff planning doctrine, to implement SDLC and Transportation Component for applications as classified above and managed by the GFM PMO. The purpose of this contract is to implement SDLC and Transportation Component Command (TCC) requests for new capability and enhancements to existing capability, and to prototype new algorithms to improve the veracity of transportation planning.

The services provided within the scope of this contract are considered Operationally Critical Support (OCS) and Covered Defense Information (CDI) as defined in Defense Federal Acquisition Regulation Supplement (DFARS) 252.204-7012, "Safeguarding Covered Defense Information and Cyber Incident Reporting.”

GFM is a complex, n-tiered system comprised of many components. The GFM system is comprised of 15 applications sustained by the Contractor. Most of these applications are developed using Java, which are hosted on Apache and Tomcat application servers. Many trading partners interact with GFM using Electronic Data Interchange (EDI) and eXtensible Markup Language (XML) files for ASCII X12 and Web Service data exchanges. GFM uses Axway to translate between EDI and a User Defined Format (UDF) and Java EDI (JEDI) to move the data between the translator and GFM servers.

SDDC Enterprise Support division maintains Axway for SDDC programs that require EDI translation service.

All deliverables identified in the PWS shall be prepared and submitted for Government approval IAW the applicable Contract Data Requirements List (CDRL).

The PWS includes the following task areas:

Task Area 1: Contract Level and Project Management Task Area 2: GFM Application Sustainment Task Area 3: Enhancements Task Area 4: Emerging Capital Projects Task Area 5: Cloud Migration and Optimization Task Area 6: Application and Oracle System Operations and Maintenance Task Area 7: Configuration Management (CM) Task Area 8: Information Assurance (IA) Task Area 9: Contract Transition and Knowledge Transfer

1.2.1 Definitions

Contract award is the date on which the Government awards the contract. Contract Initial Operational Capability (IOC) is the first day of contract performance--i.e., the first day of the transition period; IOC ends at the conclusion of the transition period. Contract Full Operational Capability (FOC) is full contract performance, beginning immediately upon completion of transition/spin-up period; FOC is the point when the Contractor assumes full and sole responsibility for all contracted GFM tasks outlined in this PWS.

The Government Contracting Officer and Contracting Officer’s Representative/Alternate Contracting Officer’s Representative (COR/ACOR) are the points of contact regarding decisions on Government requirements and priorities. Unless otherwise specified in this PWS, all days are designated as business days.

The phrases “Government environment(s)” and “GFM environment(s)” or word “environment(s)” refers to Cloud hosted environments. The contractor may have to sustain GFM simultaneously with Cloud operations.

Sprint: A defined amount of work to accomplish one or more user stories. Multiple user stories can be accomplished within each Sprint based on the complexity of the user stories.

Release: Production implementation of software changes that are the result of one or more Sprints. Sometimes a Sprint results in code changes that cannot be pushed to production on their own. In this case, multiple Sprints will occur before the code is implemented in production.

Risk Management Framework: (Presented in NIST SP 800-37) RMF provides a disciplined and structured process that integrates information security and risk management activities into the system development life cycle. The 7 steps of RMF lay out the process an organization must follow: prepare, categorize, select, implement, assess, authorize, monitor.

1.2.2 Information Sharing

The Government may use and disclose reported information (e.g., information regarding threats, vulnerabilities, incidents, or best practices) that does not include attribution information, at its discretion to assist entities in protecting information or information systems (e.g. threat information products, threat assessment reports);

provided that such use or disclosure is otherwise authorized IAW applicable statutes, regulations, and policies.

1.2.3 Application Sustainment, Enhancement, Development Methodologies and Processes

1.2.3.1: General requirements The Contractor shall apply agile and iterative development methodologies when practical in execution of the requirements of this PWS.

Contractor shall provide concurrent development efforts with multiple development lanes. Each development lane will fulfill requirements for independent Sprints. The Contractor shall enhance and improve the existing GFM application software and/or its applications to ensure maximum system optimization. The Contractor shall conduct all software development entirely within the consolidated /SDDC Government environments. The Contractor shall be responsible for the successful installation and implementation of government-owned application software onto the government-owned environments. The Contractor may access remotely from their facilities through a government approved Virtual Public Network (VPN) connection and from isolated dedicated development workstations that comply with Government security guidelines.

The Contractor shall make changes as functional requirements and business operations change for all legacy and cloud native products as defined and directed by the COR/ACOR and GFM PMO. These changes may include but are not limited to software, tools, applications, servers, interfaces and databases for all GFM applications and related functional tools in support of the GFM user community and the GFM PMO.

The Contractor shall maintain/sustain GFM Production and Non-Production environments, assist in urgent analysis for the GFM, and optimize operation and resource utilization. Daily activities include application configuration and operation. Software development and maintenance shall not cause a degradation of the current systems performance. Performance tuning shall be conducted to obtain systems optimization for maximum application workload while maintaining historical performance data to be used as a benchmark.

1.2.3.2: Acceptance testing and documentation The Government will perform acceptance testing prior to every Sprint release. Contractor will build a test plan for each release. Each release is unique in its complexity and design. The Enterprise Testing Team and the Contractor’s development team will coordinate what release requirements will be required in preparation for and execution of Government Acceptance Testing (GAT). The PMO, Enterprise Testing Team, and Contractor shall work together to create, use and maintain a single automated test and web service test library. This will require the Enterprise Test Team to have access to the developers’ requirements task management tool.

The Contractor shall continuously maintain and update documentation on the architecture of interfaces, data and software. The Contractor shall comply with all Architecture Standards for database design; performing all development using ANSI standards, and other DoD standards as required. The Contractor shall ensure that information systems security engineering is employed during all changes to the system architecture.

For all deliveries, the Contractor shall provide all source code and documentation (including those related to architecture, test design, test plan and testing results, and installation procedures).

1.2.3.3: Sprint scheduling and status reports

The Contractor shall schedule Sprints in coordination with the Development Release Schedule and Work Breakdown Structure (WBS). The Release Schedule will incorporate and account for Government acceptance testing prior to every software release.

Contractor shall continue to provide a weekly status report reflecting all development and sustainment efforts.

In addition to non-Sprint efforts, the report should detail ongoing Sprint Team efforts and scheduling of all future Sprints. The weekly status report will identify any issues preventing software development and sustainment efforts as well as proposed resolution efforts.

Contractor shall meet the schedule in accordance with the PWS and Master Release Schedule. Any expected delays will be coordinated with the Government and approved by the PM/COR/ACOR by email. The contractor must provide a plan of action to get the project/requirement timeline back on track in line with the Master Release Schedule.

Deliverable: Weekly status report received each Monday not later than 1300L. Should Monday be a holiday the following day is acceptable.

1.3 Specific Tasks

1.3.1 Task Area 1: Contract Level and Project Management (FFP) This task consists of the functional activities relating to the administration and management of this effort.

The Contractor shall

Provide program management for all Contractor tasks, personnel resources and ensure all deliverables meet schedule.

Designate a principal point of contact for technical/engineering issues.

Provide support by preparing documents such as required briefings, point papers, training aids, and meeting minutes.

Provide a Contract Manager who shall be responsible for the performance of the work. The name of the Contract Manager and alternate(s), who shall act for the Contractor when the Contract Manager is absent, shall be designated in writing to the COR.

Notify the PM/COR/ACOR in writing of any changes to personnel within three business days after the information is known.

Government personnel will make all decisions regarding project requirements and/or actions. The Contracting Officer Representative (COR) will submit the required evaluations and recommendations to the Program Manager and/or Contracting Officer (KO) for further action.

Deliverable: Notify the COR/ACOR in writing of any changes to personnel within three business days after the information is known.

1.3.1.1 Task 1 Subtask 1: Monthly Status Report (MSR)

The Contractor shall submit an MSR due to the Government no later than (NLT) the fifth business day of each month. The MSR format will be agreed upon by the COR and the Contractor

Deliverable: Monthly Status Report, NTL 5th business day of each month.

1.3.1.2 Task 1 Subtask 2: Master Release Schedule (MRS)

The Contractor shall develop an MRS in Microsoft Project format that provides a schedule for all major milestones as currently tasked to the Contractor, for a minimum period of 12 months into the future. It also shall include anticipated future work to support schedule and workload deconfliction. The MRS shall include a Master Schedule that lists the major milestones and completion dates associated with each. The MRS shall also include sub-tasks necessary to achieve the milestone and scheduled completion dates for each sub-task. The MRS delivered to the Government shall address each task to include development, test, and deployment for software candidate releases and patches containing approved new capability, enhancements, or problem reports, and shall show the critical path. The Contractor shall keep this schedule current, making schedule changes as necessary after coordinating these changes with the PM. The MRS delivered shall include projected tasks for the next 12 months. Any changes must first be coordinated through the PM/COR/ACOR.

Deliverable: Initial MRS is due twenty business days following contract start. MRS updates to be delivered as an appendix to the MSR.

1.3.1.3 Task 1 Subtask 3: Quarterly Program Management Reviews (QPMRs)

The Contractor and COR/ACOR shall schedule and conduct QPMRs to begin the first month of each contract period; meeting typically lasts no more than an hour. QPMRs shall summarize status, progress, new capability requirements, trouble ticket updates, and program schedule to include new requirements, risk identification, and proposed remediation plan in any task area. The Contractor shall provide an agenda and presentation materials. Presentation materials shall be prepared and provided to the PM/COR. Following the QPMR, the Contractor shall submit minutes of the QPMR with a copy of the presentation slides used at the

QPMR.

Deliverables:

QPMR Draft and Final Agenda and Presentation Materials.

QPMR Minutes, five business days after QPMR.

1.3.1.4 Task 1 Subtask 4: Web-Based Application Lifecycle Management Solutions (WBALMS) The Contractor shall use the Government provided WBALMS to prepare release candidate roadmaps, to define requirements, project and organizational resources, schedules, and dependencies throughout contract execution. (Currently SBM and JIRA)

Deliverable: The Contractor shall import/populate the initial product backlog into the WBALMS within 20 business days following contract start.

Deliverable: Populated Product Backlog in the Government provided WBALMS

1.3.1.5 Task 1 Subtask 5: Integrated Product Team (IPT) Meetings The Contractor shall participate in weekly IPT meetings at the Government site or utilizing a web collaboration platform (example: Microsoft Teams) when scheduled by the Government. Meetings typically last 30 to 60 minutes and topics may include updates on progress, requirements management, metrics, MRS, upcoming calendar events, and other pertinent issues as agreed upon by the Government.

1.3.1.6 Task 1 Subtask 6: Technical Exchange Meetings (TEM)

The Contractor shall attend TEMs to support design and development, enhancements, interfaces, sustainment, maintenance, and cloud migration. The Contractor shall participate via teleconference in recurring TEMs that will last approximately one hour. At Government request, the Contractor shall travel to Scott Air Force Base (SAFB) IL, or other locations, to participate in the TEMs in person.

1.3.1.7 Task 1 Subtask 7: Employment Status Report

The Contractor shall provide an employee status report (listing/spreadsheet) containing names, location, employment status and labor categories of personnel supporting this contract. The report shall be provided within thirty (30) calendar days after contract award. Contractor shall notify the PM/COR/ACOR in writing of any changes in personnel within three business after the information is known.

Deliverable: Employment Status Report within 30 calendars of contract award and updates as applicable.

1.3.1.8 Task 1 Subtask 8: Contractor Manpower Reporting

The contractor shall report in the System for Award Management (SAM):

1) The total dollar amount invoiced for services performed during the previous Government fiscal year under the contract.

2) The prime contractor direct labor hours expended on the services performed during the previous Government fiscal year.

3) If applicable, Tier 1 subcontract number, including DUNS number/Unique Entity Identifier (UEI) and name, and the number of subcontractor direct labor hours expended under the contract.

Reporting inputs will be for the labor executed during the period of performance during each Government fiscal year (FY), which runs October 1 through September 30.

Deliverable: Contractor Management Report prior to 31 October of each year of the contract.

1.3.2 Task Area 2: GFM Application Sustainment (FFP)

To support GFM’s reliability during the contract life cycle, the Contractor shall:

1) Ensure development resources are available to address any production/change requests within GFM.

2) Participate in product grooming of the product backlog prior to each Sprint and/or Kanban event in coordination with the PMO.

3) Participate in Sprint/Kanban review and retrospective at the end of each Sprint in coordination with the PMO.

4) Provide updates at least two times a week to the Government Program Management Office.

Depending on the health of the system, the government may dictate additional updates as required.

During the sustainment period, the Contractor shall provide enhancement, integration, test (including unit, regression, and integration testing), and documentation for all GFM software. The Contractor shall ensure that the GFM software is compatible with the current and any projected SDDC software configurations (e.g., USAF SDC, network, security, Internet browsers). The Government will furnish the Contractor with the approved SDDC software configurations.

Operating System (OS) support for GFM Production, Simulator, Testing, Development and Quality Assurance will be primarily supported under a separate contact by the Government’s Centralized Enclave (CE) Contractor. GFM requires systems administration and analysis support for the Production, Testing, Simulator, Development and Quality Assurance environments during the period of this contract, GFM will strive to become cloud native.

Note of reference: Historically averaged two maintenance releases per month. For estimation purposes, between 12 and 24 maintenance releases occur every year outside of core hours, r being 6 hours in duration.

NOTE: Historically for FY22: 200 Sustainment fixes and 207 CM requests.

The GFM suite of interoperable systems consists of the applications described in Appendix A, GFM Application Descriptions. The System Environment Description is in Appendix B.

The Contractor shall:

Maintain, sustain, and update all GFM applications, databases, and technologies.

Provide software engineering services and support to ensure the GFM complies with U.S. Laws, Agency Policy, statutory, regulatory, and user requirements required to accomplish the existing mission and minimize operation risk.

Maintain software, tools, applications, servers, interfaces, and databases for all GFM applications and related functional tools in support of the GFM user community and the GFM Program Management Office (PMO).

Comply with SDDC Enterprise Architecture Standards for database design; perform all development using ANSI and DOD standards.

Apply agile and iterative development methodologies in order to provide timely capabilities to the user community and the warfighter.

Ensure that information systems security engineering is employed during all changes to the system and software development life cycle.

1.3.2.1 Task 2 Subtask 1: Functional Requirements and Documentation The Contractor shall sustain, create, review, and update system documentation in accordance with this PWS for Sustainment, Enhancement, New projects and Accreditation.

Review change requests ensuring understanding of functional and user requirements.

Be responsible for performing system/functional analysis and creating/documenting user stories/acceptance criteria in support of agile development efforts. These descriptions shall translate functional requirements received from the Program Management Office based on the needs of the customer. Each requirement will documented in Solutions Business Manager (SBM).

Maintain acute functional knowledge of the GFM subsystems identified in Appendix A.

Prepare technical documentation for the GFM Project to include System Requirements, System

Manuals and processes, Interface Requirements, Database Description Documents (DDD), Flow chart, Checklists, Web Services documents, System-user documents and other GFM system documentation requested by the program management team. Existing documents such as Memorandum of Understanding (MOUs), The Interface Design Document (IDDs) and Interface Requirements Agreement (IRAs) will be provided to the Contractor at the beginning of the contract.

Documents will be stored on the SDDC provided repository.

Prepare and maintain Standard Operating Procedures (SOPs) to ensure consistency of system performance. Activities related to hardware and software configuration shall be documented. SOPs should include, but not limited to: code standards, code scans, code promotion, backups and restores, baseline changes, licensing, installing software, and applying patches. SOPs will be updated two times per year.

Prepare any artifacts or documentation required for the RMF Process. This includes ATO accreditation packages, continuous monitoring and IATTs. Some examples of this will include: hardware list, software list, PPS, STIG Applicability list, program topology, etc.

Prepare and maintain detailed Interface Requirement Agreement (IRA) documents for each interface between GFM and its trading partners. The Contractor will maintain and update this information in the designated CM tool. Signed documents will be stored electronically on a government-owned server to be designated by the COR. Changes to a document will be made by a complete revision and identified by unique Document History Control Number. The justification for the modification is to be recorded in the Document History. If no change proposals are submitted during the annual review period, that fact is to be noted in the Document History and the document will be notated Reviewed on (date) with no change required.

Document server application configuration changes for each server within the GFM environments.

Provide a server application configuration change document when configuration changes are implemented.

Prepare and maintain system architecture diagrams, system documentation, and other system-related documentation.

System Administrator (SA) Manual The Contractor shall maintain the SA Manual. At a minimum, the SA Manual shall address:

Install application code, or packaging for CE SAs to install GFM System startup procedures User interfaces Standard Service Level Agreement (SLA) agreements with SDDC Enterprise Integration Program

(EIP)/CE team

Database Administrator (DBA) Manual The Contractor shall maintain the GFM DBA Manual. At a minimum, the DBA Manual shall address:

Shutdown and restart GFM database servers or instances Recovering database procedures Creating and managing table space, user accounts, and privileges Database install and configuration procedures Create and maintain a list of business rules as applied by Database and/or User Interface (UI). The rules should be broken down as appropriate by table, field, application and form. This should be a living document and delivered/updated as appropriate for each release.

Deliverable: Functional Requirements and Documentation (Sustainment, Enhancement, and New Projects) as required when changes are made to the environment that affect an application.

1.3.2.2 Task 2 Subtask 2: Interface and Electronic Commerce/ Electronic Data Interchange (EC/EDI)

Support The Contractor shall support the current data exchange capabilities in GFM. These are currently done via Electronic Data Interchange (EDI) exchanges, Extensible Markup Language (XML), and Web Services.

Create and maintain Web Services in compliance with the SDDC Service Oriented Architecture (SOA) vision.

Create and maintain User Defined Format (UDF) business logic and crosswalk mappings that comply with the Defense Transportation Electronic Business (DTEB) Implementation Conventions (ICs) for Electronic Data Interchange

Be responsible for the day-to-day processing of data exchanges within the GFM domain and its trading partners and ensure all inbound transactions are retrieved, processed and stored. Note, with the direction from the PMO, the contractor may need to coordinate with outside supporting agency during EDI/UDF trouble events.

Support the Enterprise EDI team (EET) and Enterprise Interface/Data Architecture teams as needed for day-to-day receipt, distribution, and resolution of data exchanges outside the GFM domain.

Provide support for updating existing and/or creating new schemas and Web Services Description Language (WSDL) to ensure accurate data exchanges between GFM and its trading partners.

Ensure all data elements are recorded in the schema and WSDL comply with GFM business requirements and enterprise standards.

Update existing and/or creating new XML to ensure accurate data exchanges between GFM and its trading partners.

Ensure schema, WSDL and XML support the procedures and requirements prescribed to Transportation Service Providers (TSP), providing commercial transportation and related services to the Department of Defense (DOD) and other authorized users of the Defense Transportation System (DTS), as published in the Defense Transportation Regulation-Part II and Military Freight Traffic Unified Rules Publication-1 (MFTURP-1).

Ensure all data elements are recorded in the User Designed Format (UDF) comply with GFM business requirements and enterprise standards.

Ensure all inbound and outbound EDI/UDF transactions are retrieved from and/or deposited in the appropriate directory on a GFM server or the Managed File Transfer server (MFTS). Ensure the transactions are successfully processed into/generated by the GFM system. Note, with the direction from the PMO, the contractor may need to coordinate with outside supporting agency during EDI/UDF trouble events.

Perform root cause analysis on data and the underlying business issues spanning multiple GFM applications, schemas, or interfacing systems.

Ensure all inbound and outbound XML and web service transactions are deposited in and retrieve from the appropriate directory on a GFM server or SDDC Enterprise Service Bus (ESB).

Provide qualified and trained personnel to build and/or support the technical infrastructure needed to support EC/EDI.

o This support shall include personnel that possess detailed technical knowledge of EDI ASC

X12 Transportation Standards, DOD Implementation Conventions, data requirements, and software associated with the system.

o Provide 24x7 software monitoring and assist the enterprise EDI teams as needed in support, upgrade and trouble shoot GFM EDI.

Provide proven expertise to include coordinating changes to the Trading Partner profiles Master Files within the Enterprise EDI translator tool, initiate, establish and maintain GFM Trading Partner interfaces using secure shell, creating and maintaining Unix shell scripts to transfer and consolidate files between GFM zones and the Command Run On (CRON) jobs that schedule them, maintenance of customized Unix shell scripts to start up and shut down the current SDDC EDI translator tool.

Collaborate with outside agencies with coordination through the PMO to research/validate issues impacting EDI transactions.

Setup interfaces for outbound and inbound system traffic.

Deliverable: Update existing and/or creating new XML/WSDL as required when changes are made to the environment that affect an application. Contractor shall maintain three versions of all web services. (Current and two previous)

See Appendix D for GFM Trading Partners See Appendix E for GFM Data Exchange Templates

1.3.2.3 Task 2 Subtask 3: User Training and Training Manuals - Distant Web Learning The Contractor shall maintain the Distance Learning Program (DLP) for the GFM suite of applications in Appendix A. The manuals and guides are maintained in soft copy format. The Contractor shall:

Ensure integration of these products with the existing developmental strategies of GFM and current training.

Ensure that all training and learning tools are updated consistent with and are synchronized with each software upgrade and each version release.

Maintain or create user interactive training modules for all current and/or future GFM applications.

o Interactive training modules are the primary method for user training.

Training modules include practical exercises containing data files that are consistent with the application and realistic to the functions being explained to the user.

o No less than five times per month, the Contractor shall conduct training in support of users.

Typical class time is approximately two hours. Trainings are typically conducted via an online collaboration tool (example: Microsoft Teams).

Deliverable: User Training and Training Manuals as required when changes are made to the environment that affect an application.

1.3.2.4 Task 2 Subtask 4: System and Database Administration

The Contractor shall perform all System Administration (SA) and Database Administration (DBA) on GFM Development Enhancements, Quality Assurance (QA), Consolidated Training (CTE), Testing and Production site zones/ Environments. Standard zones or virtual servers will be provided to the Contractor by the Government’s CE Contractor. The Contractor shall work with the network management team to configure permissions, user groups and directory structures.

Complete all Application Administration, Oracle Database administration, and uniquely GFM tasks for Oracle and System Administration.

o The Government’s CE Contractor is the primary Systems Administrators and Oracle DBAs for these environments.

Work with the Government’s CE Contractor to ensure all databases, Operating Systems (OS), permissions and security are maintained at the appropriate levels.

Coordinate database backup preparation.

o GFM requires specific database backups to keep the Oracle and databases synchronized on date and time stamp. GFM SA shall prepare data for team to coordinate backups in all environments.

Monitor the accuracy and timeliness of the backup service provided by the SDDC Systems administration support contract, set-up directory structure and permissions for the GFM Oracle

Database environment as well as other GFM applications (See Appendix A), set-up monitoring support tool configurations

Perform GFM application maintenance and updating of application patches. Systems Administration tasks that are uniquely GFM in nature, to include required Oracle Database synchronization steps.

Configure permissions, groups, directory structures and load applications.

Perform all required patching (excluding operating system) for application, database for Oracle, and any required maintenance, updating and documentation.

Be fully responsible for maintenance and support of the development instances.

Maintain VMs, Bastion Host or equivalent instance.

Currently GFM has a development environment that consist of a front-end application tier, a backend database tier, web tier, code repository server and code scanning server. These applications are housed on Solaris or RHEL and Windows virtual servers zones.

Propose changes that the Contractor believes will improve the efficiency and/or performance of GFM or resolve software/ hardware problems which have the potential for causing system failure or situations which will improve the overall performance of GFM.

Submit system and process changes where GFM may take advantage of code sharing and/or re-use, data or databases tables sharing; presentation changes focusing on uniformity in look and feel across multiple applications; and design and development practices that focus on overall improvements and advantages in system integration across multiple applications.

Identify areas were SOA principles, methodology and Web Services, can be incorporated and utilized for interoperability and reuse.

Maintenance to the GFM Development, Non-Prod Environment, through database tuning and system patching.

Load all applications and COTS software within the Development Non-Prod Environment.

Provide technical support to the CE Contractor in install/deploy software patches and releases into all environments.

1.3.2.5 Task 2 Subtask 5: Tier II/III Help Desk Support

The Contractor shall resolve and provide Tier II/III Help-Desk support of Service Requests (SRs) or Problem Reports (PRs) escalated from Tier I status.

Analyze problems reported via Tier I and take corrective actions to restore GFM functionality.

Make software changes and System/Data Administration actions as required in order to resolve service interruptions, errors or other problems reported by the user community.

Log problem status and resolution information in the Government owned SDDC ticketing database (Service Now is the current tool to capture this data).

Identify trends and areas for improvement and include this analysis in the Monthly Status Report. Noted trends must be analyzed/documented/resolved by the contractor with coordination from the PMO office.

Trends are considered five tickets concerning the same issue highlighted from multiple GFM users.

Perform Help Desk support outside core work hours in case(s) of a system outage.

Identify on-call personnel for hours outside of the core work hours (07:00 – 16:30 USA Central

Time) that will be available via telephone/cell phone. The Government will not provide telephones or cell phones for this service.

Assist the Government in providing updated information for the maintenance of the Service Response Center (SRC) Application and knowledge database. Contractor-provided updates will be sent by the Government to PMO/SRC staff for updating the SRC Application and knowledge database.

Diagnose and fully restore to service any malfunctioning component.

Provide a PR Analysis and Recommendations Report each contract performance period with specific, feasible, and actionable recommendations in writing to reduce system factors that create SRs. The Government will determine which recommendations to implement in future software releases.

Analyze and resolve escalated Problem Reports (PRs) or Service Request (SR) within five business days after the Tier 2/3 escalation date.

Provide resolution of open software PRs through maintenance releases with resolutions incorporated into the baseline using software versioning methodology.

Prepare a document containing resolutions and test results for the PRs contained in each software version.

Provide a completion status of all PRs.

Design system applications and integration efforts to enhance/improve the performance and efficiencies of GFM software modules and applications.

Deliverable: PR Analysis and Recommendations Report and document containing resolutions and test results - Annually

NOTE: Historically, GFM Tier II/III Help Desk support averages 150 Tier II/III call per month.

1.3.2.6 Task 2 Subtask 6: Unscheduled Downtime Events

Resolve unscheduled downtime events attributable to the GFM software, customized Commercial Off the Shelf (COTS), or interfaces. The GFM Production environment unscheduled downtime shall not exceed a total of four hours per month.

Analyze each unscheduled downtime event (i.e., attributable and non-attributable to the GFM software, customized COTS, or interfaces) to determine and document the root cause of event, event duration, modules affected, volume of accumulated backlog, possible users affected, agencies contacted, and actions taken to resolve the event.

Utilize the Government-provided tools and coordinate with agencies, activities and resources associated with the event to provide a complete analysis.

Report the analysis findings in an unscheduled downtime event report no later than 10:00 AM CT following the day the unscheduled downtime event is initially reported to the Contractor’s service/help desk.

The status of accumulated backlog shall be reported in writing, each business day, until it is resolved.

Deliverable: Unscheduled Downtime Event Report no later than 10:00 AM CT following the day the unscheduled downtime event Failover to alt availability zone (AV)

The Contractor shall:

Complete all required application configurations to ensure the GFM applications are correctly installed and configured to operate should primary availability zone fail.

The Contractor shall ensure all databases are replicated to the secondary availability zone to include Oracle, EDI Data, and all applications are maintained at the same level.

1.3.2.7 Task 2 Subtask 7: Disaster Recovery Exercise (DRE)

Participate in SDDC G6 DRE as directed.

Perform contingency operations planning for SDDC IT systems in coordination with the enterprise

DRE solution and SDDCs Common Computing Environment (CE). The plans will include crisis emergency management (onsite and offsite) (technical and functional); disaster recovery; pre and post emergency operations requirements; and fail-over management.

Complete all required application configurations to ensure GFM is correctly installed and configured to operate at the Disaster Recovery (DR) site.

Provide support to the Government during emergency operations in accordance with approved disaster recovery and contingency operations plans.

Ensure resources/key personnel are available throughout an emergency in accordance with the established plan. Exact Cloud DRE testing procedures are unknown until programs are migrated to the Cloud.

1.3.2.8 Task 2 Subtask 8: Data Analysis

The Contractor shall develop ad hoc queries and reports, such as:

Historical/Archived reports Operational/Sustainment data

In support of Freedom of Information Act inquiries Analysis/impact studies Data calls

Requests shall be submitted via the enterprise configuration management tool.

1.3.2.9 Task 2 Subtask 9: Software Implementation

Provide production ready software to the test environment for Government Acceptance Testing.

o Enterprise Testing will provide feedback to the developers and government team in the form of problem reports (PRs) recorded in the government approved change management tool, on any defects or functionality that does not meet the defined requirements.

Implement all testable components into the Government’s automated testing tool prior to promotion to the next environment.

Automated testing will be handed off to the Enterprise testing manager. Analyze and resolve all defects identified by the Test Team. Corrections will be provided in a software release or patch, as required.

Provide an implementation plan that documents the discrete tasks required to install and/or deploy software patches and/or releases that will require system downtime exceeding 15-minutes. The implementation plan shall include:

o Schedule of events by task o Bulletin, Message of the Day (MOTD), notifying customers and trading partners of the estimated duration and scope of the scheduled downtime.

Prepare a Software Release package for each software change package and deliver it at the time of software delivery. The package shall include all applications and shall be issued for all releases. In each package, identify each SCR number and provide a brief description of the change. Include Step-by-step instructions with acceptance criteria for all functional items. Other items as agreed to with the Enterprise Test Team. These items need to be delivered in draft seven business days prior to Government Acceptance Test start date.

Provide Software Operations Manual and Software Code Installation Guide(s).

Installation of software to the Alternate site or equivalent within one day after installation of Production.

Work with Enterprise Testing on specific release required deliverables depending on the complexity of Data Sets, Workflow Diagrams, and Business rules.

Support Enterprise Testing with build and maintain of automated Test Project Library.

Notify the Government when GFM is operational and accessible to all customers and submit an

After-Action report, identifying events that deviate from the planned work schedule.

Deliverable: Software Implementation Plan - As Required when production release changes are made to an application Deliverable: Prepare a Software Release package for each software change package and deliver at time of software delivery.

1.3.2.9.1 Task 2 Subtask 9.1: Software Development Unit Test (SDT) The contractor shall:

Conduct Software Development Unit Tests (SDT) before releasing software to the GFM PMO.

Develop a Software Development Test Plan, test the software according to the plan, and develop a SDT

Test Results Report for each software SCR and/or PR incorporated.

Regression test all software changes and development prior to Government Acceptance Testing.

Ensure the software is error & abort free and shall verify interoperability and integration with interfacing systems. When possible, development testing should be automated and testing scripts provided to government prior to promotion.

Step-by-step test cases, data sets and specific release deliverables in coordination with PMO/Enterprise Test Team.

Deliverable:

Test Plan and Results - As required when test and production release changes are made to an application Test Cases. 5 Days prior to testing for every software delivery.

1.3.2.9.2 Task 2 Subtask 9.2: Software Reviews and Software Version Description (SVD) The Contractor shall:

Prepare a SVD for each software release and present the SVD to the Government no later than five workdays after deployment of the application. The SVD shall identify and describe an inventory of materials to be released, software/applications contents, changes to be installed, adaptation of data, related documents, installation instructions, and possible problems and known errors.

Conduct software reviews for new development. Software reviews consist of Test Readiness Review (TRR), Fielding Decision Briefing (FDB), Other briefings, walkthroughs, and/or prototype demonstrations.

Provide meeting minutes.

Deliverable:

Prepare SVD - Prepare a SVD for each software release/meeting minutes and present the SVD to the Government no later than five (5) workdays after deployment of the application.

1.3.2.10 Task 2 Subtask 10: Bills of Lading (BLs)

Provide for electronic transfer of BLs among all GFM trading partners through the development and maintenance of software and the monitoring of BL file transmissions.

Develop/maintain the capability to cost and select for traffic currently moving under BLs in order to assure that the Government acquires the best value.

Enable the system to produce electronic and hardcopy BLs.

Ensure that the electronic files are available for transmission to GFM Trading partners (TPs) – one year active / 10 years archived. GFM is the repository for all BLs.

1.3.2.11 Task 2 Subtask 11: Remote Carrier Access

Provide the capability for commercial carriers to access the GFM ATR, CAVS, FCRP and TEOW applications from remote locations and obtain shipment Requests and Responses, Standard Tender of Freight Services, and Bills of Lading information.

Support and enhance the automated process of carriers accessing ATR, CAVS, FCRP, and TEOW via the Internet.

Establish and maintain user accounts in accordance with Army and DOD security guidelines and regulations, and monitor system access patterns. These guidelines and regulations include, but are not limited, to DOD 8500.1, DOD 8500.2, AR 25-2, and AR 38019. All user access shall be positively authenticated and monitored, and non-repudiation must be established. All attempts at non-authorized access shall be monitored, and access attempts that appear to be suspicious shall be reported in a timely manner to GFM PMO personnel.

Implement system changes as necessitated by IT security notifications, the Information Assurance Vulnerability Management Program or as required by Information Assurance Program Manager (IAPM).

Deliverable: 100% of user accounts that have not been accessed for over 35 days are locked, unless authorized otherwise by the Government. 100% of user accounts that have not been accessed for 120 days are deleted, unless authorized otherwise by the Government.

1.3.2.12 Task 2 Subtask 12: Cloud Environments

Development Environment Systems will be developed and QA tested in a developer development environment. The contractor’s development environment shall contain all developmental products, tools, servers, and services, to include databases necessary to conduct development activities within the environment. The contractor’s development environment shall be locked down IAW Defense Information System Agency (DISA)/FedRAMP IL2 standards and remain fully patched. The contractor will perform monthly scanning to check for patch compliance and will provide a patch compliance report to the programs IA Security Officer. The contractor shall administer and execute DevSecOps utilizing this development environment to build, test, release, and deploy cloud agnostic, secure GFM application software, Infrastructure as Code IaC and Configuration as Code CaC to a government managed zone C DevSecOps Pipeline.

The…