TRANSCOM19D018_RFI_DRAFT_PWS.pdf

DRAFT PERFORMANCE WORK STATEMENT

FOR

SURFACE DEPLOYMENT AND DISTRIBUTION COMMAND

(SDDC)

INTEGRATED BOOKING SYSTEM (IBS)

Last Revision: 10 July 2019

TRANSCOM19D018

This page is intentionally left blank.

Table of Contents 1 Description of Services

1.1 Introduction

1.2 Background

1.3 Objective

1.4 Scope

2 Contract Requirements

2.1 Information Sharing

2.2 Post Award Task Order Meetings/Conferences

3 Specific Tasks

3.1 Task 1: Contract and Program Management

Task 1 Subtask 1: Agile Team Definition ........................................ Error! Bookmark not defined.

Task 1 Subtask 2: Program Management

Task 1 Subtask 3: Government Furnished Equipment (GFE) and Property Accountability and Inventory Error! Bookmark not defined.

Task 1 Subtask 4: Documentation

Task 1 Subtask 5: Development Methodologies & Processes

3.2 Task 2: Sustainment and Maintenance

Task 2 Subtask 1: Agile Team Definition

Task 2 Subtask 2: Software Sustainment and Maintenance

Task 2 Subtask 3: Migration and Implementation of IBS into the Government Cloud

Task 2 Subtask 4: Sustain Existing Documentation and Artifacts

Task 2 Subtask 5: Interface Artifacts

Task 2 Subtask 6: User and Training Manuals

Task 2 Subtask 7: System Administrator (SA) Manual

Task 2 Subtask 8: Database Administrator (DBA) Manual

Task 2 Subtask 9: System and Software Analysis, Design, and Documentation

Task 2 Subtask 10: System Integration

Task 2 Subtask 11: System and Database Technical Support

Task 2 Subtask 12: System and Database Administration

Task 2 Subtask 13: Operating, Systems, RDBMS and Application Tuning

Task 2 Subtask 14: Maintain Disaster Fail-Over Environment

Task 2 Subtask 15: Disaster Recovery/Contingency Plan

Task 2 Subtask 16: DRE Exercise Operations

Task 2 Subtask 17: Tier II/III Help Desk Support

Task 2 Subtask 18: Data Analysis

Task 2 Subtask 19: Configuration Control Board (CCB)

Task 2 Subtask 20: Base-lined Source Code

Task 2 Subtask 21: Software Release Notes (SRN)

Task 2 Subtask 22: Accreditation Sustainment

Task 2 Subtask 23: Configuration Management (CM)

Task 2 Subtask 24: Information System Controls Audit Manual (FISCAM) and FIAR Support

Task 2 Subtask 25: Cargo Transportation Contract Modifications (e.g., USC9, GTMO, Multi-modal Contracts)

3.3 Task 3: Enhancements

Task 3 Subtask 1: Agile Team Definition

Task 3 Subtask 2: Enhancement Development Methodologies and Processes

Task 3 Subtask 3: Integrate Enterprise Capabilities

Task 3 Subtask 4: Phase I Transformation Requirements Definition (OPTIONAL)

Task 3 Subtask 5: Phase II Transformation

3.4 Task 4: (OPTIONAL) New Development

4 Deliverables

4.1 Service Delivery Summary (SDS)

5 Cyber Security

5.1 Malicious Code Warranty

5.2 Delivery of the Secure Application

5.3 Non-Secure Software Delivered to Government

5.4 Dedicated Computers Use

5.5 Software Code Scans

5.6 Information Assurance (IA)

Annual Training

One-Time Training:

Specialized Training (Required for privileged access):

Software Development

Writing Secure Application Software

Tracking Security Issues

5.7 Remote Access GFE

6 General Information

6.1 Virtual Desktop Infrastructure (VDI)

6.2 Place of Performance/Hours of Operations

6.3 Period of Performance

6.4 Risk Management and Applicable Documents

6.5 Government Furnished Equipment

6.6 Travel

6.7 Source and Change Control

6.8 Software Automated Testing

6.9 System Environments

6.10 Maintains Operational Capabilities and Compliance

6.11 Compliance with the SDDC EA v2020 initiative

6.12 The Use of Open-Source Middleware

6.13 Making Source Code Available to the Government

6.14 Training Support

6.15 Artifact Tracking

7 Security (Physical, Personnel, Information, Industrial, Operations, Antiterrorism, and Force Protection) Requirements

7.1 General Security Information

7.2 Personnel Clearance (PCL) / Investigation Requirements

7.3 Company Facility Clearance (FCL)

7.4 Clearance / Investigation Validation Checks

7.5 CAC Issuance

7.6 Scott AFB/USTRANSCOM/HQ SDDC Physical Access

7.7 Permanently Assigned Contractors at Scott AFB

Visitor Request

7.8 In/Out-Processing

7.9 Security Briefing/Debriefing Statement

7.10 Security Training

Initial Security and AT Level I Training

Reporting Training Completion

7.11 Security Permissions on DOD Systems

7.12 Security Compliance / Deviations

Removal of Contract Employees

Threat Awareness and Reporting

Base Access and Control Procedures

Operations Security (OPSEC)

7.13 FPCON Impact on Work Levels (US Installation Only)

7.14 Security Regulation Compliance

8 Security Regulation Guidance

9 Contract Transition (OPTIONAL TASK)

9.1 Contractor Transition and Exit Requirements

9.2 Incoming Contractor Transition

Transition-In Start and Planning

Sufficient Personnel

Receipt of Materials

9.3 Incumbent Contractor Transition

Transition Planning

Contract Summary

Transfer of Materials

Sufficient Personnel

Exit Requirements

PERFORMANCE WORK STATEMENT

INTEGRATED BOOKING SYSTEM

1 Description of Services

1.1 Introduction

The Head Quarters (HQ) Military Surface Deployment and Distribution Command (SDDC) mission is to provide global surface deployment and distribution services to meet the nation’s objectives. SDDC is the Army component of the United States Transportation Command (USTRANSCOM) Transportation Component Commands (TCCs), which includes Military Sealift Command (MSC), and HQ Air Mobility Command (AMC). SDDC’s primary functions include worldwide port operations, global traffic management, software engineering, and development of integrated transportation systems.

1.2 Background

The Integrated Booking System (IBS) is the lead execution system of the Defense Transportation System (DTS) for the global shipment of ocean cargo in support of all wars, major contingencies, and humanitarian relief operations where Government personnel are deployed. IBS is available to users worldwide, twenty-four

(24) hours a day and seven (7) days a week.

IBS resides in the G6 directorate which is a staffed HQ SDDC directorate for Command, Control, Communications, Information Management and Intelligence. The G6 directorate oversees Information Management, delivers Information technology capabilities and supports SDDC’s mission by designing, developing, implementing, and operating DOD global transportation systems.

SDDC G6 consists of two (2) Divisions, the Operations Division and the Automated System Division. IBS resides in the Automated System Division, under the Ocean Cargo Branch which supports the SDDC mission by managing the IBS.

1.3 Objective

The objective of this contract is to achieve greater efficiencies in the global shipment of ocean cargo with IBS. As the manager of IBS, the Government expects a contractor to continue maintenance, integration support, future capabilities and requirements implemented across the IBS enterprise They shall include development of enterprise strategies, technical standards and services as the program transitions into the commercial cloud computing platform.

1.4 Scope

The scope of this requirement is to acquire software engineering services, data management, enterprise-wide support and technical guidance related to mission needs and issues concerning the requirement to support SDDC and the IBS.

Services include requirements definition, software maintenance and engineering, implementation, configuration management (CM), cyber security and information assurance (IA), area manager support, training, documentation, technical support, and project management. All tasks shall be performed in accordance with (IAW) all regulations and guidelines as shown in Appendix E - Applicable Documents (Federal Laws & Statutes and DOD Regulations).

The Contractor shall assist the Government in managing cost, scheduling, performance, cyber security, Financial Improvement and Audit Readiness (FIAR) compliance and risk for IBS related activities and projects. The Contractor shall coordinate with the Government to ensure all activities are synchronized and integrated with other SDDC and USTRANSCOM efforts.

The IBS enterprise consists of separate development, staging, quality assurance (QA), production and Fail- Over environments hosted in the Centralized Enclave (CE) and is in the process of migrating all environments to a cloud computing platform.

The IBS Program Manager (PM) or their designated representative will make all decisions regarding government requirements and priorities. Contracting Officer’s Representative/Alternate Contracting Officer’s Representative (COR/ACOR) will assist the IBS PM with contract QA, surveillance and performance assessments in the Contractor’s execution of the contract.

The PWS includes the following task areas:

Task 1: Contract and Program Management Task 2: Sustainment and Maintenance Task 3: Enhancements Task 4: (OPTIONAL) New Development Task 5: (OPTIONAL) Contract Transition, Knowledge Transfer and Overall Transition (KT&OT)

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.

The execution of Optional Tasks may be required at any time during the Base and Option Periods.

2 Contract Requirements

The Contractor shall establish and utilize best practices, standards, and repeatable and measureable controls in performing and delivering products associated with existing and future tasks. Unless otherwise specified in this PWS, all days are considered calendar days.

2.1 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 in accordance with applicable statutes, regulations, and policies.

2.2 Post Award Task Order Meetings/Conferences

Technical meetings and/or post award orientation conferences may be necessary to resolve problems and to facilitate understanding of the requirements of the contract and/or of each task. Participants at these meetings/conferences shall be members of the Contractor’s technical staff and technical representatives of the Government. These meetings/conferences shall be scheduled by agreement of the parties and arrangements made between the Contracting Officer (CO), his/her representative, and/or the Contractor. Records of these meetings/conferences shall be made by the Contractor and submitted to the Government within five (5) business days after conclusion of the meetings/conferences. All costs associated with the attendance at these meetings/conferences shall be at no direct charge to the contract.

3 Specific Tasks

All Categories will be identified, determined and annotated by the Government within current CM application. Areas of responsibility by Task shall include but are not limited to the following:

Sustainment and Maintenance:

Address/Mitigate security issues/findings (RMF/STIG compliance) Patch testing Helpdesk/Functional support, (replicate and verify the issue, determine work-a-round/corrective action) Contractual Obligations/Statutory/Legal Compliance and Financial Audit Compliance Changes Monitor/Correct Internal/External Interfaces (Existing) Internal System Improvements/Corrections Software/Environment/Technical upgrades, testing of existing hardware, software and/or equipment Requirement meetings Perform analysis and testing Update Use Case/Test Cases/Test Plans to support operational and/or business processes and changes Review/Update User Training and Manuals Support software releases Mitigate operational risk (Software/Hardware/Environments)

Enhancements:

Adding new requirements to existing software Requirement meetings Modify/update Internal/external interfaces Review/Update User Training and Manuals Web Services (WS) Creation/Updating/Integrate

New Development:

New projects New applications/capabilities New functionality Create new Interface Create/Update User Training and Manuals Conduct training

3.1 Task 1: Contract and Program Management

This task and associated deliverables are considered Not Separately Priced (NSP).

The Contractor shall provide all materials, services, personnel, planning, direction, coordination, and control necessary to provide the services required by this contract. The Contractor must perform program management, project management, and contract management to ensure timely and effective performance.

Task 1 Subtask 1: Program Management

The Contractor shall manage and oversee all activities performed by contractor personnel (including subcontractors and teaming partners, as applicable) to satisfy all performance requirements. The Contractor shall effectively plan, manage, and monitor work activities and supervising contractor personnel to support effective performance and control risk, as well as escalate problems or concerns to the CO and COR/ACOR.

The Contractor shall designate a PM to provide project management of all projects and tasks within the scope of this PWS. The person performing this task shall be the Contract Lead, certified as a Project Management Institute (PMI); Project Management Professional or an equivalent Project Management certification, shall maintain this certification throughout the life of the contract, and shall provide day-to-day oversight of all tasks and projects within the scope of this PWS.

The Contractor shall assist the Government to ensure cost, schedule, performance, cyber security, and risks are managed for SDDC’s IBS related activities and projects. The Contractor shall coordinate with the Government to ensure all activities are well synchronized and integrated with SDDC and other transportation organizations management efforts.

Task 1 Subtask 2: Documentation

The Contractor shall provide support to draft, review, revise, and deliver documents (e.g. reports, briefings, point papers, business case analysis, meeting minutes) required in conjunction with the contract. The Contractor shall provide technical writing and document support to include all the tasks identified in this

PWS.

3.1.2.1 Task 1 Subtask 3: Weekly Status Meetings

The Contractor shall deliver a Work Breakdown Structure (WBS) which shall include but is not limited to each significant project and all its lower level tasks and their dependences with start, finish and milestone dates. The Contractor shall schedule a weekly status meeting to present and reviews the WBS, all defined tasks, durations, timelines, resources, and dependencies for all projects on this contract. The contract shall provide minutes and action item from the meeting no later than (NLT) the next week’s meeting. The weekly status meetings format shall be agreed upon by the COR/ACOR and it shall also contain, but are not limited to, the following:

A list of planned outages for the next thirty (30) days and unplanned outages for the past thirty (30) days. This list shall detail the outage’s duration, start and end times, cause of the outage, and for unplanned outages, a description of the mitigating actions planned to prevent future outages.

Risk assessment and mitigation recommendations Proposed activities NOT included in the WBS Minutes and Action Items

The weekly status meetings shall also describe the technical approach, and management controls employed to meet the cost, performance, security and schedule requirements throughout contract execution.

DELIVERABLE: Weekly status meeting, minutes and action items. Minutes and action items NLT the next meeting.

DELIVERABLE: WBS to include milestone schedules. Updates NLT the next meeting.

3.1.2.2 Task 1 Subtask 4: Employment Status Report and Organization Structure

The Contractor shall provide an employee status report and organization structure containing names and labor categories of personnel supporting the IBS Contract. The report will be provided within thirty (30) calendar days after contract award and updates to the COR/ACOR NLT one (1) business day after change in personnel. The Contractor shall ensure all personnel assigned to this contract meet the minimum requirements specified in the Contractor’s proposal.

DELIVERABLE: Employment Status Report within thirty (30) days after contract award; updates NLT one (1) day after change in personnel.

3.1.2.3 Task 1 Subtask 5: Contractor Management Report (CMR)

The Contractor shall report ALL contractor labor hours (including subcontractor labor hours) required for performance SDDC via a secure data collection site. The Contractor is required to completely fill in all required data fields using the following web address https://cmra.army.mil/Login.aspx . The applicable Unit Identification Code for this requirement is W0QFAA.

Reporting inputs will be for the labor executed during the period of performance during each Government fiscal year (FY), which runs 01 October through 30 September. While inputs may be reported any time during the FY, all data shall be reported NLT 31 October of each calendar year, beginning with 2019. Contractors may direct questions to the help desk at: https://cmra.army.mil/Login.aspx .

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

3.1.2.4 Task 1 Subtask 6: Monthly Status Reporting (MSR)

The Contractor shall provide an MSR NLT the fifth (5th) business day of each month. The MSR format shall be agreed upon by the COR/ACOR and the Contractor. During the reporting period, identify, establish and report on quality controls and processes for evaluating software and associated documentation. Identify reviews conducted, results and process improvements on quality control during the reporting period.

The Contractor shall establish and report to the Government on the status of Quality Control Reporting (QCR) in the MSR. The Contractor shall establish quality controls and processes for evaluating software and associated documentation, and report on them in the MSR. This should include reviews conducted, results and process improvements on quality control during the reporting period.

DELIVERABLE: MSR NLT the fifth (5th) business day of each month.

3.1.2.5 Task 1 Subtask 7: User Manuals and Artifacts

The Contractor shall develop and maintain user manuals and artifacts for all current and/or future applications and capabilities. User manuals will be the primary method for user training. All user manuals shall be updated, current and based upon the most current production environments and software.

DELIVERABLE: All updates to the User manuals, based upon the SCR implemented, shall be implemented at the time of the SCR change is implemented.

Task 1 Subtask 5: Development Methodologies & Processes

The Contractor shall conduct all software development entirely from within this consolidated USTRANSCOM/SDDC government environments. The Contractor may access remotely from their facilities through a Government *-approved VPN connection, from isolated dedicated development workstations that comply with Government security guidelines.

The Contractor shall be responsible for the successful installation and implementation of government-owned application software onto the government-owned environments. The Government will make use of a centralized software installation/implementation team that will perform code scans and installation of the code into the government-owned environments. For all deliveries, the Contractor shall provide all source code, documentation (including those related to architecture, test design and testing results, and installation procedures), delivered to the government.

SDDC IA policies require base-lined source code to be scanned (Refer to Section 5.5 Software Code Scans) prior to release to the Staging and Production environments. The tool currently used for these software scans is Fortify. Code Scans shall be provided prior to code release to staging/production environment and within thirty (30) days of a new rule pack release.

Software developer shall apply agile and iterative development methodologies where practical for Sustainment, Enhancement and New projects. The Contractor shall develop, in accordance with agile and iterative development methodologies and the Government PM and COR/ACOR, a Project Execution Plan.

The Project Execution Plan shall account for Sprint planning, cross-functional and technical team collaboration (e.g., SCUM), capacity, backlog and burn down planning and velocity tracking. The Project Execution Plan shall lay out and account for approach, tools, to be used in execution, Sprint planning, cross-functional and technical team collaboration, capacity, backlog and burn down planning and velocity tracking.

Additionally, as part of the Project Execution Plan the Contractor shall implement sprint iterations in short timeframes (time boxes) that shall typically last from four (4) to six (6) weeks.

The Project Execution Plan shall also incorporate and account for Government acceptance testing prior to every sprint Software release. After the establishment of the Project Execution Plan the Contractor shall be required to meet the scheduled sprint software release dates, or not exceed the scheduled sprint release date by more than ten (10) business days unless the delay is coordinated with the Government and approved by the COR/ACOR. Those significant delays, delays greater than ten (10) business days, shall be documented and shall include the COR/ACOR signature.

The Contractor shall meet the defect metrics defined in Appendix F - Software Defect Definition & Metrics.

DELIVERABLE: Software Project Execution Plan within thirty (30) days of execution of this PWS and then continuously updated.

DELIVERABLE: Meet the scheduled sprint software release date.

DELIVERABLE: Meet software release defect metrics.

3.2 Task 2: Sustainment and Maintenance

The Contractor shall sustain, maintain and update all IBS Legacy and Transformation Applications and Capabilities (Refer to Appendix A – System Application Descriptions and Architecture for a list of both Application and Capability descriptions and Appendix B - System Environment Description). This list includes but is not limited to software, technologies, processes, applications, capabilities, databases, interfaces and web services. The Contractor shall provide system solution operation and maintenance (O&M) support activities related to the on-going support for the performance of routine, preventive, predictive, scheduled, and unscheduled actions aimed at maintaining and improving system performance, capabilities and security.

This includes performance monitoring and bug fixes and preventing system/production failure by working with hosting and development staff to properly engineer and deploy capabilities to support performance. In addition, O&M support activities include software improvements and correcting production software defects with the goal of increasing efficiency and reliability on a continuous basis by deploying patches/upgrades as needed. The Contractor shall follow all IA requirements as part of this task (Refer to Section 5.6 Information Assurance for a description of the IA tasks required for this effort).

The Contractor shall configure, develop, maintain, test, and deploy maintenance releases and/or bug fix/hotfix releases through a Continuous Integration and Continuous Delivery (CI/CD) life cycle methodology framework. The Contractor shall provide technical documentation and execute these life cycle processes throughout the period of performance to support the delivery of functionality. Releases may occur after hours and/or during the weekend. It is expected that all deployment release packages are completely developed and Subject Matter Expert (SME) advisory and troubleshooting support is provided. For Production releases, Contractor support staff shall be identified and available if there is a problem.

The Contractor shall design; develop; conduct unit, integration, and regression testing; fully integrate all new capabilities, enhancements, and software fixes with current software; and, as specified by the requirement, provide requisite documentation for each new change and/or capability. The Contractor shall provide server administration support, maintenance support, migration support, and troubleshooting support. The Contractor shall provide Critical Defect Investigation and After Action Reports when requested by the Government.

The Contractor shall comply with all Architecture Standards for database design; perform all development using ANSI standards, and other DOD standards as directed. The Contractor shall ensure that information systems cyber security is employed during all changes to software and the system architecture.

The IBS suite of interoperable systems consists of the applications described in this PWS, Appendix A – System Application and Descriptions and Architecture and in Appendix B - System Environment Description.

These applications and capabilities include but are not limited to provide automated tools to support carrier contract requirement definition, rate and service solicitations and evaluation; vessel schedules; fleet management; book unit and sustainment cargo; produce shipment documentation; provide cargo offering and status information; produce orders, customs and manifesting documentation

SDDC has prescribed adoption of a common SDDC user experience using the latest version of SNAPUI Framework (GOTS) built on a custom platform for all programs modernizing their interfaces.

DELIVERABLE: Create/Update requisite documentation for each new change and/or capability.

DELIVERABLE:After Action Report within seven (7) days after experiencing a Production defect.

Task 2 Subtask 1: Agile Team Definition

The Contractor shall provide a minimum of one (1) Agile Sustainment and Maintenance Team (a minimum of sixteen (16) FTE resources made up of the appropriate technical skill sets (e.g., Senior Computer Programmer, Senior Developer, Journeyman Computer Programmer, Senior Business Intelligence Analyst, Senior Network and Computer SA, Senior DBA, Senior Software QA Engineer and Tester, etc.). It is anticipated that the level of effort and mix of resources for the Agile Sustainment and Maintenance Team necessary to complete each task will remain consistent through the base and option periods. This Team shall support the emergent requirements of the IBS program. This Team shall support but not be limited to enhancements, Cargo transportation contract modifications and transformation requirements of the IBS program. This IBS Agile Team shall perform but not be limited to testing activities (identified in Section 6.8 Software Automated Testing), IA security engineering activities (identified in Section 5.3 Non-Secure Software Delivered to the Government, 5.5 Software Code Scans and 5.6 Information Assurance (IA)), and CM activities (identified in Section 3.7.23 Task 2 Subtask 23 Configuration Management (CM)) for IBS, as required.

The Technical Agile Teams shall be multidisciplinary, capable of performing a full range of software sustainment, maintenance and development, and whose technical skill sets can evolve to meet the necessary stage of the software development lifecycle and technical nature of the project.

Task 2 Subtask 2: Software Sustainment and Maintenance

As part of the Software Sustainment and Maintenance Task Area for this PWS, the Contractor shall generate a Project Execution Plan and implement the same processes, procedures and sprint iterations, using agile and iterative development methodologies, as defined in Section 3.1.5 Development Methodologies & Processes.

The Contractor shall deliver, for each application, a useable product that is abort free with fully documented program source code and complimenting executable code for processing on SDDC hardware. The Contractor shall continuously maintain and update documentation on the system architecture and of existing interfaces, data and software.

The Contractor shall employ the use of Service Oriented Architecture (SOA), Electronic Data Interchange (EDI), Extensible Markup Language (XML), and WS as directed by the Government, which includes but is not limited to:

The Contractor shall maintain and upgrade all IBS EDI transactions based upon the Defense Transportation Electronic Board (DTEB) Implementation Conventions (IC) and SDDC functional requirements. The Contractor shall evaluate EDI changes, ensure IBS business requirements are captured appropriately, risks are identified and addressed, and changes are implemented. Contractor shall work with the IBS government team and the SDDC EDI Team to ensure DTEB changes meet IBS business rules and practices.

The Contractor shall coordinate with the SDDC EDI Team for updates to existing EC/EDI transaction sets, or to create new EDI transaction sets. Currently, IBS utilizes the EDI 300, 301, 303, 304, 315, 824, 858 and 997 but not limited to these transaction sets with IBS, SDDC systems and trading partner(s).

The Contractor shall upgrade to a newer standard based upon SDDC migration.

The Contractor shall work with the SDDC EDI Team to test any changes or new transaction sets to ensure the changes meet IBS business rules and practices.

The Contractor shall identify existing sources for new WS for consumption by existing IBS applications where appropriate.

The Contractor shall implement SOA methodologies and principals and create WS when possible. SOA methodologies and principals, including WS, shall be developed in coordination with SDDC Enterprise Service Standards (e.g., Enterprise Service Bus (ESB)) and in coordination with the SDDC MPS Team.

Development using SOA methodologies and principals, in particularly WS, shall be for increasing software reusability, decreasing redundant features and functionality and promoting efficiencies. SOA shall be implemented as directed by the Department of the Army.

The Contractor shall design, develop, maintain and implement the capability to allow the exchange of data between different applications and platforms. Integration Capabilities shall include but not be limited to WS, EDI, SFTP, User Defined files (UDF).

The Contractor shall design, develop, implement, maintain and document WS in support of consumers of the WS. Support capabilities shall include but not be limited to the Vessel Schedule, ETRR/ETR, transformation and GPE WSs. The WSs shall be extensible and flexible enough to be utilized throughout the IBS and SDDC Enterprise. The WSs security mechanism shall be implemented utilizing the current security implementation used by IBS and follow SDDC standards and best practices for WS security. The Contractor shall develop the software using agile development based on iterative and incremental development methodologies and SOA principles. The Contractor shall develop and deliver documentation for each service which covers description, authentication, error handling, and HTTP information.

Task 2 Subtask 3: Migration and Implementation of IBS into the Government Cloud

SDDC is in the process of modernizing and transitioning IBS to a Cloud Service Provider (CSP), leveraging cloud managed services and automated pipeline technologies. The desired end-state is to realize CI/CD as part of DevOps per the Command’s Capability Delivery Concept of Operations (ConOps).

The Contractor shall upgrade and implement all IBS on-premises applications, databases, technologies and environments to the Government defined Cloud environments. The Contractor shall ensure all IBS functionality, business rules and capabilities are available and operate successfully in the cloud, just as in the on-premises IBS system and environments. The following acceptance criteria shall be meet before the Government will accept delivery of the IBS Cloud system from the Contractor.

All IBS production functionality and capabilities residing in the on-premises system and environments also resides in the Cloud system and environments

The Cloud Production System is fully operational and free of defects Stakeholders, users and interface partners can access and use the IBS systems with no adverse or undesirable effects Stakeholders and users can submit transactions successfully, to completion and all transactions can be viewed All current business rules function properly and successfully and are replicated from the current on-premises IBS system and environments into the Cloud system and environments All transactions, including EDI transactions, flow in and out of the system successfully, correctly, as designed and are defect free All on-premises WS are migrated to the cloud and operation and function as designed and are defect free The cloud system meets all DOD security requirements The IBS Cloud system has an RMF certification All environments have been replicated successfully in the Cloud, are accessible from the required stakeholders, and operate successfully as designed All production source code and data has been successfully migrated to the Cloud

Task 2 Subtask 4: Sustain Existing Documentation and Artifacts

Contractor shall sustain, review, and update system documentation, to include but are not limited to database, data, system, user, training, interface, architectural, capabilities and software/application documentation. The Contractor shall provide input to briefing packages and reports as required by the Government.

Task 2 Subtask 5: Interface Artifacts

The Contractor shall maintain but is not limited to the following interface artifacts:

Interface Design Description (IDD) Interface Requirements Specifications (IRS) Interface Requirement Agreement (IRA) Interface Control Document (ICD) Memorandum of Agreement (MOA) Service Level Agreement (SLA)

The Contractor shall participate in meetings involving the interface artifacts to resolve issues and/or share information. The Contractor shall submit minutes/comments resulting from these reviews to the IBS COR/ACOR electronically. IBS Interfaces are defined but are not limited to those specified in Appendix C - Interface Requirements Specifications. The IRS shall conform to the requirements of Contract Data Requirements List (CDRL) A001 (Data Item Description DI-IPSC-81434A, Interface Requirements Specification (tailored)).

DELIVERABLE: Update artifact based upon changes within thirty (30) business days of changes in procedures/processes. Reviewed annually for each contract period. Due by 31 March or defined at the beginning of each contract period.

Task 2 Subtask 6: User and Training Manuals

The Contractor shall maintain and update all user and training manuals in an approved Microsoft Products and Portable Document Format (pdf) versions of the documents when required. These include any manuals/pamphlets affected by any change(s) or update(s) to IBS. The Training Manuals shall include practical exercises containing data files realistic to the functions being explained/taught. The Contractor shall update manuals based upon system updates and software change requests (SCR). All manuals/pamphlets shall be updated and stored via a Version Management tracking tool and will be fielded with the associated SCRs.

See Appendix D - User and Training Manuals (U&TM) for the current list of User and Training Manuals.

DELIVERABLE: User and Training Manual updates are required based upon system updates and SCRs. The updates shall be fielded at the time of the associated SCR’s release. Document updates shall be fielded with the corresponding production change.

Task 2 Subtask 7: System Administrator (SA) Manual

The Contractor shall maintain the SA Manual. The SA Manual shall address but is not limited to the following:

Shutdown and restart Oracle databases Setup and configuration (e.g., WebLogic, WS02, applications and services) Infrastructure diagram and network architecture for IBS IBS System startup/shutdown procedures User interfaces (UI), ports and protocols Linux, UNIX, Windows and Oracle environment, architecture and access Archive, locations and management of transaction files Daily monitoring, reporting and checklists Rate Load operations and procedures (Reference Attachment 9 - IBS Rate Load Process) Installation code, procedures, build and configuration options and associated definitions System maintenance, updates, and upgrade policies, operating procedures, error recovery, and schedules

Database schema, network topology, and flowcharts used to illustrate items such as system designs, data communications, program logic, and the relationships between network nodes

Instructions for opening/closing and starting/stopping applications, devices, and services under various conditions

Frequently asked questions and troubleshooting techniques for common issues Roles, responsibilities, and contact information for key personnel and support staff Other miscellaneous and/or relevant items

DELIVERABLE: SA Manual shall be updated as changes occur, reviewed yearly.

Task 2 Subtask 8: Database Administrator (DBA) Manual

The Contractor shall maintain the DBA Manual. The DBA Manual shall address but is not limited to the following:

Adding and dropping roles Recovering database procedures Updating reference files Managing cyber security via DBA Application and user roles in Oracle environments Creating and managing table space, user accounts, and privileges Database instance install and configuration procedures Rate load operations and procedures (Reference Attachment 9 - IBS Rate Load Process) System maintenance, updates, and upgrade policies, operating procedures, error recovery, and schedules Database schema, network topology, and flowcharts used to illustrate items such as system designs, data communications, program logic, and the relationships between network nodes Instructions for opening/closing and starting/stopping applications, devices, and services under various conditions

DELIVERABLE: DBA Manual shall be updated as changes occur, reviewed yearly.

Task 2 Subtask 9: System and Software Analysis, Design, and Documentation

The Contractor shall perform analysis and design for all Sustainment and Maintenance changes required for the system IBS. As part of the analysis and design effort, the Contractor shall incorporate all information produced into the appropriate IBS documentation. The Contractor shall also maintain functional requirements and the Interface Requirements Specification (IRS) documents for all Sustainment and Maintenance changes required for IBS. The Contractor shall maintain and update this information in the designated location.

IBS includes but is not limited to all requirements defined in Appendix C - Interface Requirements Specifications. Additionally, the Contractor shall:

a. Submit to the Government for approval proposed changes that the Contractor believes will improve the efficiency and/or performance of IBS or resolve software/hardware problems which have the potential for causing system failure or situations which will improve the overall performance of the system.

b. Submit to the Government for approval, system and process changes where IBS 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.

c. Submit to the Government for approval, areas were SOA principles, methodology and WS, can be incorporated and utilized for interoperability and reuse.

d. Provide initial and secondary impact statements on changes, identifying the changes and the projected number of man-hours/level of efforts required to complete.

e. Participate in both the SDDC G6 and IBS Configuration Control Board (CCB) meetings to discuss requirements, changes and target completion dates for implementation.

DELIVERABLE: The generation of briefings, packages and reports as requested by the COR/ACOR.

Task 2 Subtask 10: System Integration

The Contractor shall perform system and data integration tasks necessary to assure IBS applications meets the technical, and performance requirements established by the IBS Branch. This includes ensuring accessibility through Electronic Transportation Acquisition (ETA) single sign on, and through the .mil or .com networks, for all applications in all environments. Additionally, the Contractor shall ensure system, software and application integration developed by other vendors is consistent with the SDDC open systems architecture.

Task 2 Subtask 11: System and Database Technical Support

The Contractor shall provide skilled Linux/UNIX/Windows Engineers with expertise in SA and DBA tasks who are trained, experienced, and proficient in hardware/software used with the IBS capabilities and environments. The Contractor will assist, and work in coordination with the CE and Cloud teams in maintaining and updating the IBS capabilities, software and environments to include but not limited to Development, Staging, QA, Fail-Over and Production, both on premises and in the Cloud. The Contractor shall provide Systems Analysis and Engineering Support in the maintaining, updating and documenting of the hardware and software associated with the IBS current Development, Staging, QA, Fail-Over and Production Environments. The Contractor shall be responsible for end-to-end operations and maintenance services to ensure connectivity of all installed devices related to IBS in the Development environment.

Task 2 Subtask 12: System and Database Administration

SDDC and IBS are in the process of transitioning from a traditional hosted computing environment to a cloud services computing platform, offering compute power, servers, storage, databases, content delivery and a broad set of application services. The transition including ongoing support shall carry through this contract as part of standard system and software upgrade, maintenance and modernization efforts. The cloud integration and maintenance will take advantage of and utilizing USTRANSCOM Virtual Desktop Infrastructure (VDI), a Cloud Integrator, Cloud Service Provider, and Dev/Ops pipeline software tools and technology.

The Contractor shall be responsible for performing or assisting in SA and DBA on all databases and operating systems in the IBS Development, Staging, QA and Fail-Over Sites on premises and in the Cloud environments. Administrational tasks shall be performed in the Development, Staging and QA and Fail-Over Site on premise and cloud environments during the period or performance or as directed. The Contractors responsibilities shall include, but are not limited, to the following:

a) Production

1) The IBS Contractor shall perform IBS Application maintenance and updating.

2) Assist and/or provide technical support to CE with any systems, SA and/or DBA related issues.

3) Satisfy Security Technical Implementation Guide (STIG) requirements and patches.

b) Staging

3) Satisfy STIG requirements and patches.

c) Development

2) The Contractor shall perform IBS operating system and the database maintenance, updating, patching and documentation.

3) Satisfy STIG requirements and patches.

4) End to end operations and maintenance.

5) Document connectivity of all installed devices.

d) Fail-Over

1) The IBS Contractor shall perform IBS application and Database maintenance and updating.

3) Satisfy STIG requirements and patches.

The Contractor shall assist and support operating system and database upgrades as it pertains to the IBS application’s stability and configuration soundness in the staging, production and Fail-Over environments by working with members of the CE or cloud managed services team.

The Contractor shall perform Application software changes to accommodate System and Database software and hardware upgrades and maintenance.

Task 2 Subtask 13: Operating, Systems, RDBMS and Application Tuning

The Contractor shall ensure maximum optimization and uptime of the IBS systems. These tasks include patching, remote and on-site support for all technical aspects associated with IBS for the purpose of tuning/optimizing/maintaining UNIX, Linux, Windows, and the ORACLE RDBMS to ensure that IBS is operationally sustained for high performance levels. This includes all database documentation to track performance and tuning of database changes.

Task 2 Subtask 14: Maintain Disaster Fail-Over Environment

The Contractor shall complete all required Fail-Over application configurations to ensure the IBS applications are correctly installed and configured to operate at the SDDC Fail-Over site. The Fail-Over site is located at a separate facility and shall be accessed remotely. In the event of a disaster and to ensure operational consistency, the Contractor shall install, configure and update system and application software and data at the Fail-Over site within one (1) day of availability. The Contractor shall validate that replication of data is occurring.

Based upon all implemented production software changes the Contractor shall update the Fail-Over site to reflect those changes within one (1) day of production implementation.

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.

Task 2 Subtask 15: Disaster Recovery/Contingency Plan

The Contractor shall update the IBS plan for disaster recovery and/or contingency operations in coordination with the enterprise Disaster Recovery Exercise (DRE) solution and the Enterprise Integration Program (EIP) team. The plan shall include: crisis emergency management (onsite and offsite) (technical and functional);

disaster recovery; pre and post emergency operations requirements; and Fail-Over management.

DELIVERABLE: Update the DRE plan within ten (10) working days after DRE schedule is determined.

Task 2 Subtask 16: DRE Exercise Operations

The Contractor shall participate and execute the SDDC G6 DRE for IBS. The exercise is an opportunity to ensure the plan is executable. The Contractor shall perform activities as required by the plan. The exercises are conducted usually over a one-week period, during normal work hours, no more than twice a year.

Task 2 Subtask 17: Tier II/III Help Desk Support

The Contractor shall provide Customer Support for all IBS applications and to SDDC’s Systems Response Center (SRC) help desk. The Contractor shall provide Tier II/III Help Desk Support for all applications for which users have authorization. Tier II/III support includes but is not limited to:

Ensure accuracy and consistency in the standard solutions and information contained in the SRC Application and knowledge database. Develop and maintain additional solutions and information as changes occur.

Identify any systemic problems, based on reports from the SRC database, and work with Ocean Cargo Branch staff to prioritize the correction of these problems.

Identify/coordinate resolution for any issues regarding level of customer service provided by the

SRC.

Provide/coordinate the training of application software including updates, upgrades, and patches to SRC personnel.

Review customer surveys and provide business process recommendations to improve customer satisfaction.

The analysis and resolution of issues and system defects.

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

Develop queries and reports using tools provided by the Government as required.

Perform root cause analysis on data and the underlying business issues.

Respond to all inquiries concerning IBS applications, to include, but not limited to: supporting detail, summary reports, data analysis, data interpretation, and briefing preparation.

Task 2 Subtask 18: Data Analysis

The Contractor shall develop queries and reports using tools provided by the Government in support of operations for IBS applications. Perform reports queries as requested by the IBS PM and IBS stakeholders, which shall include but is not limited to:

- Historical/Archived reports - Operational/Sustainment data

- Data calls

Task 2 Subtask 19: Configuration Control Board (CCB)

The Contractor shall participate in a weekly Enterprise CCB lasting no more than one (1) hour per meeting.

Minimum preparation time is required. The Contractor will be responsible for creating, monitoring and closing CCB and/or Approved Scheduled Interruption (ASI) tickets. Upon request by the Government, the Contractor’s Configuration Manager will participate in the Government’s CCB usually scheduled twice a year. The Contractor’s Configuration Manager will act as the liaison between the Government and Contractor to provide any additional information that the CCB requires. The Contractor shall analyze and prepare all documentation required to prioritize program level requirements.

Task 2 Subtask 20: Base-lined Source Code

The Contractor shall provide/install base-lined code to the Staging environment for Independent Verification and Validation (IV&V) and the government to perform Software Acceptance Testing (SAT) level validation.

The IV&V testing effort is NOT included or apart of this PWS. The IV&V and government testing team will provide feedback to 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. After, the IV&V and government teams have accepted and certified the software released to the Staging environment as error-free and meets intended design, the Contractor shall provide/install base-lined code to the CE’s Production environment. The Contractor shall store, for every designated IBS software release and interim release to the production environment, all base-line source and executable code to the SDDC environment.