ATT J01 TO 01 PWS.pdf

ATTACHMENT 1

PERFORMANCE WORK STATEMENT (PWS)

GLOBAL COMBAT SUPPORT SYSTEM-MARINE CORPS

(GCSS-MC)

POST DEPLOYMENT SYSTEM SUPPORT (PDSS)

Task Order M67854-24-F-7611

July 2024

Version 1.1

Program Manager (PM), Program Management Warfare

(PMW 230)

Marine Corps Systems Command (MCSC)

Quantico, VA 22134-5011

PART 1: GENERAL INFORMATION

The Program Manager (PM), Logistics Integrated Information Solutions - Marine Corps (LI2S-MC) has a requirement for Post Deployment System Support (PDSS) services for the Global Combat Support System - Marine Corps (GCSS-MC). The mission of PM LI2S-MC is to transform and deliver state-of-the-art systems and services that enable the highest performance and readiness of Marine Corps (United States Marine Corps (USMC)) logistics operations worldwide.

PM LI2S-MC’s portfolio falls under the Department of the Navy's (DON) Program Executive Office for Manpower, Logistics and Business Solutions. The LI2S-MC capabilities are critically important to the daily operations of the Marine Corps, enabling force readiness through various logistics, supply chain and manpower enterprise solutions.

1.

GCSS-MC is a Program of Record within the portfolio of the PM LI2S-MC. The GCSS-MC Product Manager (PdM) has overall responsibility for cost, schedule, and performance of the GCSS-MC program. Supporting the PdM in this responsibility are three Government Team Leads focusing on specific aspects of the GCSS-MC effort as described below and depicted in Figure 1-1.

• Operations Team Lead: Responsible for the daily operations of the GCSS-MC capability and providing on-site support services for deployed events when requested by the Fleet. Within the Operations Team is the GCSS-MC Operations Center (GOC) which provides constant surveillance of systems operations. The GCSS-MC Enterprise Service Desk (ESD) is the initial customer Point of Contact (POC) for worldwide GCSS-MC Enterprise user support. Details on the Operations Team’s Fiscal Year (FY) 23 efforts are described in the Operations Team’s FY23 Program Management Plan (PMP).

• Sustainment Team Lead: Responsible for maintaining all GCSS-MC services. The Sustainment Team is responsible for all efforts to ensure the underlying hardware and software remain viable and support GCSS-MC operations. Efforts include break/fix, patch management, upgrades, Change Requests (CRs), and technical refreshes. Details of the Sustainment Team’s FY23 efforts are described in the Sustainment Team’s FY23 PMP.

• New Capabilities Development (NCD) Team Lead: Responsible for the initial development and testing of all new capabilities to be integrated into the system. Details of the FY23 NCD Team’s efforts are described in the NCD Team’s FY23 PMP.

Figure 1-1: Program Management Office (PMO) Organization

1.1 Description of Services/Introduction

The contractor shall provide all personnel, equipment, supplies, facilities, transportation, tools, materials, and other services and items necessary to perform the GCSS-MC PDSS work in, this TO Performance Work Statement (PWS). The contractor shall perform to the standards in the contract.

The GCSS-MC Enterprise system is an integrated composite Enterprise Resource Planning (ERP) system with the Oracle Enterprise Business Suite (EBS) product at its core. Components of this integrated system include a customized Common Access Card (CAC)-enabled authentication architecture with role-based authorization; a reporting capability handled by the Oracle Analytics Server (OAS);

a Mobile Field Service (MFS) application; and customized workflows in support of 20+ external partners via 40+ interfaces utilizing the Oracle Service Oriented Architecture (SOA) tools with Business to Business (B2B) functionality. The Disaster Recovery/Continuity of Operations Planning (DR/COOP) is a second instance of the GCSS-MC production system that takes over when the primary system is unavailable due to natural or manmade disasters and planned or unplanned system outages.

The GCSS-MC Enterprise is currently comprised of the DR/COOP, Production (PROD), Production Support System (PSS), and the Government Procured Cloud-Based Solution Development Environment (SDE).

The PROD and PSS environments reside within the same hardware. Connectivity to the environments is controlled via Local Area Network (LAN) configurations and dedicated Oracle virtual servers. PROD has one set of Internet Protocol (IP) addresses and PSS has another set of IP addresses. The Development (DEV), Configuration Management (CM), and Training instances also share common hardware and are in the SDE. Although the Training environment can be hosted on shared hardware, it is currently a separate environment that allows for the development, testing, and dissemination of training system updates and training material. The Mobile Training Suites (MTSs) are utilized by the Formal Learning Centers (FLCs) and each of the major commands to conduct sustainment training of the GCSS-MC Enterprise system. Each MTS has its own closed environment of the GCSS-MC Enterprise application to support its function. The following subparagraphs provide further description of the GCSS-MC environments.

1.1.1 GCSS-MC Enterprise Production System (PROD)

The PROD is comprised of Oracle Engineered hardware with the Exadata 6-2 as its foundation. PROD is in the Kansas City Information Technology Center (KCITC) in Kansas City, MO. GCSS-MC PROD is web-accessible to over 23,500 worldwide users, serving ~6,000 distinct users per day, with a concurrent usage of ~2000 users at any given time.

1.1.2 GCSS-MC Production Support System (PSS)

The PSS resides on the same hardware as the PROD but is separated (via IP address block and separate virtual servers) from the PROD environment. The PSS is used to conduct Government Acceptance Testing (GAT) and the staging of changes before they are deployed to the PROD.

1.1.3 GCSS-MC Solution Development Environment (SDE)

The SDE mirrors the PROD environment to support development, testing, and troubleshooting of the GCSS-MC software. The contractor shall operate and maintain the SDE system. The current SDE consists of hardware and software to create the necessary environments to support multiple simultaneous development and testing efforts. Within the SDE there are three sub-environments:

• Dev.

• CM.

• Integration.

Within the Integration sub-environment, there are these functions:

• Patch.

• GRC.

• Information Assurance (IA) Dev.

• Training.

• Audit Vault.

• Sandbox.

• Training MTS.

1.1.4 GCSS-MC Mobile Training Suite (MTS)

The MTS provides a stand-alone capability to deliver GCSS-MC training at the user location. The MTS consists of hardware, software, database, documentation, and procedures used in the training of GCSS-MC Enterprise users on the GCSS-MC Enterprise system and processes. MTSs are built within portable enclosures (cases) so they can be easily transported, set up, and stored at any training environment. MTS cases consist of a server, storage array, 24 laptops, switches to connect the laptops to the server/array, and all ancillary equipment to have a complete computer-based classroom. Annually, the contractor shall ship an updated Gold Disk image to each major command and the image is uploaded to the MTS by the local command staff. MTSs are deployed to various locations worldwide.

1.1.5 Information Technology Infrastructure Library (ITIL)

The Information Technology (IT) Infrastructure Library (ITIL) is a framework of industry best practices for delivering IT services.

ITIL’s systematic approach to IT service management can help businesses manage risk, strengthen customer relations, establish cost-effective practices, and build a stable IT environment that allows for growth, scale, and change.

The ITIL processes have been tailored for implementation within the GCSS-MC program as indicated in Table 1-1.

Table 1-1: GCSS-MC ITIL Processes

Process/Service Area Process Owner Process/Service Area Process Owner Request Fulfillment Operations Team Incident Management Operations Team Access Management Operations Team Problem Management Operations Team Application Management Operations Team Event Management Operations Team

Change Management Sustainment Team Release Management Sustainment Team Build Pipeline Sustainment Team Interface Management Sustainment Team Availability Management Sustainment Team Capacity Management Sustainment Team

Database Management Sustainment Team Technical Management Sustainment Team Instance (Environment) Management

Sustainment Team Backup and Disaster Recovery Plan (tape backup)

Sustainment Team

Deployment Management Sustainment Team Asset Management Sustainment Team

Document Management Sustainment Team Solution Development Operations, Sustainment & NCD

Teams Requirements Management

Operations, Sustainment & NCD Teams Testing Operations, Sustainment & NCD

Teams

Training & Education Operations, Sustainment & NCD Teams

Continual Service Improvement

(CSI)

Operations, Sustainment & NCD Teams

System Engineering APdM-Eng Strategic IT Roadmap APdM-Eng Configuration Management APM-Eng

GCSS-MC Disaster Recovery/Continuity of Operations Planning (DR/COOP)

The GCSS-MC DR/COOP hybrid cloud environment shall be used as described below to maintain warfighter critical operations, guarantee data availability to fleet Marine forces, and directly support unit readiness during emergency situations. The contractor shall operate and maintain the GCSS-MC DR/COOP system, which is a duplicate version of the primary GCSS-MC system.

The DR/COOP continually replicates data and configuration information obtained from the primary GCSS-MC. In the event of a critical or planned primary GCSS-MC outage, the DR/COOP takes over primary GCSS-MC duties until the primary GCSS-MC attains full mission recovery status.

1.1.6 Other System/Application Descriptions

1.1.6.1 System Software/Oracle EBS

In addition to EBS’ out-of-the-box functionality, GCSS-MC Enterprise has implemented Marine Corps conversions (referred to as Reports, Interfaces, Conversions, Extensions, Configurations, Personalization, and Workflows (RICECPW), adapting the EBS to meet Marine Corps specific requirements. Table 1-2 provides a definition of the RICECPW objects.

Table1-2: RICECPW Definitions

RICECPW Object Definition Reports Unique to the Marine Corps Supply and Maintenance capabilities Interfaces GCSS-MC connections to external systems; GCSS-MC Enterprise has approximately 40+ interfaces Conversions Programs to transfer data from legacy systems to the new system; most GCSS-MC

Enterprise conversions are now shut off as the systems conversion is completed Enhancements (or Extensions)

Changes to the existing EBS application that add Marine Corps functionality

Configurations Profile options, user-defined flex fields, function, and data security setups Personalization New prompts, titles, text, added; existing prompt and title changes, reordering of items or regions workflows; and how content is routed for review, approval, and release to the system Workflows Content routing process for review, approval, and release to the system

GCSS-MC relies on internal and external interface partners to ensure the full complement of services within GCSS-MC is functional.

These include but are not limited to the interface list referenced in Attachment J11.

In addition to Oracle EBS, the system includes the use of other Oracle Commercial Off-The-Shelf (COTS) products, including, but not limited to, Oracle Identity Management (OIM), Oracle Access Manager, Oracle Internet Directory (OID), SOA Suite, WebLogic Server, Web cache and WebGate, MFS, OAS, Oracle Enterprise Manager (OEM), Oracle Business Availability Manager, Oracle Advanced Supply Chain Planning, Oracle Database 19c, Connection Manager 19c, and Axway API Gateway.

1.1.6.2 Oracle’s Unified Method (OUM)

The GCSS-MC Enterprise system architecture, design, interfaces, customizations, test scripts, operations procedures, and knowledge management tools are developed using Oracle’s Unified Method (OUM), which is a standards-based method with roots in the Unified Process. OUM is a business process and uses a case-driven methodology and implementation strategy that includes support for the Unified Modeling Language.

1.1.7 GCSS-MC Processes

The system provides the Marine Air-Ground Task Force (MAGTF) and Supporting Establishment with an integrated, distributed logistics capability to plan, manage, execute, and monitor logistics business processes and sub-processes. Specific system functions include asset visibility and transfer, supply, maintenance, readiness, task organization, request tracking, and financial information, as depicted in Table 1-3.

Table-1-3: GCSS-MC Enterprise Logistics Business Processes and Sub-Processes

Business Process Business Sub-Process

Business Process Business Sub-Process

Request Management Create or Update Service Request (SR)

Maintenance Field Maintenance with Replacement Parts

Request for Service Create Preventive Maintenance Schedule

Mass Transfer of Install Base Ownership Readiness Retire Install Base Items Repair with Tasks Maintenance-Related Returns Create Warranty Contract Request for Supply Discrete Manufacturing Request for Technical Assistance OAS Reports Create and Maintain Accountable and Responsible Officers

Finance Create Budget

Flagging Install Base Items for Readiness Depreciate Assets OBIEE Reports Automated Processes

Supply Order Management Execution Budget Inquiry

Business Process Business Sub-Process

Business Process Business Sub-Process

Secondary Repairable or T/E Items Perform Period End Account Maintenance

Miscellaneous Inventory Transactions Funds Check Internal Classify/Declassify Secondary Repairable

(SECREP)

ERS Invoices Created and Matched to Purchase Orders

Requisition to Receipt New Year Open

Demand Planning General Ledger Journal and Account Inquiry

Spares Management Minimum/Maximum Planning Period End Processing and Reporting Item Master and Bill of Materials (BOM) Update Value of Fixed Assets Inquiries and Reports OAS Reports Forecasting System

Administration

(SA)

Task Organization Inventory Minimum/Maximum Planning Daily Business Intelligence Add New System Item Reports Readiness User Management Return of Spares Tools Supply Costing Login Quality Logout Warehouse Management

1.2 Background

GCSS-MC is the technology centerpiece for logistics modernization in the Marine Corps and a single point of entry for logistics requests for products and services.

The GCSS-MC Enterprise Non-Secure IP Router Network (NIPRNET) V2.X system is henceforth referred to as GCSS-MC Enterprise throughout this PWS.

The GCSS-MC Enterprise system provides accurate, near real-time integrated logistics information and enterprise-wide visibility of logistics data, enabling Marines to make informed decisions about the logistics chain commensurate with the operational tempo. The GCSS-MC Enterprise began full sustainment in December 2015.

The term “system” will be used interchangeably with GCSS-MC Enterprise throughout the body of this document, inclusive of its software, hardware, firmware, and hosting environment. The term “application” refers to the EBS and other software components of the system. The term “environment” refers to the collection of hardware and software tools a system developer uses to build software systems. The term “instance” refers to a single copy of the software running on a single physical or virtual server.

Table 1-4 identifies PDSS activities required to support and sustain the system in accordance with Department of Defense (DoD) 5000 series. The PDSS activities shall be consistent with the Defense Acquisition System, Sustainment (Operations and Support) Phase.

Table 1-4: GCSS-MC Enterprise PDSS Activities

System and Database Administration System Integration (SI) Information Assurance (IA)/Cybersecurity Application Sustainment/Development Interface & Data Management Configuration/Change Management Defect / Enhancement Management Engineering Change Proposals Asset Tracking Training & Training Devices Management Release Management Program Management Service Optimization Tuning Enterprise Service Desk Audit Compliance

1.3 Objectives

PM LI2S-MC's overarching objective is to deliver deployable, single point-of-entry solutions with cutting edge technology to support modernized logistics.

The objective of the work contained in this PWS is to deliver GCSS-MC Enterprise PDSS services necessary for operation, sustainment, maintenance, interface, system integration, connectivity, and updates for fielded systems and software.

The contractor shall meet GCSS-MC service requirements for: Service Management; Service Operations (ESD and GOC); PROD and PSS; DR/COOP; SDE; and Enterprise Training, to include the MTS. The contractor shall perform analysis of systems with deployable front-end capabilities to retrieve and transact data from the GCSS-MC and enable and expand supply and maintenance requests in a tactical environment.

GCSS-MC Enterprise provides the MAGTF and Supporting Establishment with an integrated, distributed logistics capability to plan, manage, execute, and monitor logistics business processes and sub-processes. Specific functions include asset visibility, supply, maintenance, readiness, task organization, request tracking, and financial information. The system supports enterprise users from worldwide locations in both garrison and deployed environments. GCSS-MC Enterprise serves as the starting point for addressing key shortfalls impacting the logistics community, including, but not limited to, multiple entry points for submitting and managing requests;

inefficient capacity management and inefficient enterprise-wide processes; limited ability to monitor asset availability; and limited ability to maintain resource situational awareness.

1.4 Scope

This PWS sets forth the requirements for the contractor to provide PDSS for the PM, LI2S-MC, and the GCSS-MC Enterprise, and DR/COOP. The primary scope of support shall include Service Management, Service Operations (ESD and GOC), PROD and PSS, SDE, and Enterprise Training. Additional areas of support include analysis of systems with deployable front-end capabilities to retrieve data from the GCSS-MC, complete transactions, and enable and expand supply and maintenance requests in a tactical environment.

Additional areas of support services include: development of technical approaches to modernizing large ERP systems using Application Program Interfaces (APIs); development of containerized, cloud, and platform/infrastructure/software as service constructs; and planning and contracting for Development, Security, and Operations (DevSecOps) pipelines that, by DoD continuous authority, must meet the DoD/MC/DON Chief Information Officer operating requirements and must be established quickly to meet emerging requirements or budget “plus-ups.”

Successful performance of this PWS and subsequent Task Orders (TOs) will require contractor interaction with personnel from various other contractors and Government agencies, such as, but not limited to, the Hybrid Cloud Services (Formerly Marine Corps Enterprise IT Services (MCEITS)); Marine Corps Cyber Operations Group; and KCITC.

1.5 General Information

1.5.1 Quality Control: See base IDIQ #M67854-24-R-7603.

1.5.2 Quality Assurance

The contractor shall perform the requirements in the PWS in accordance with the performance standards and thresholds in the Performance Requirements Summary (PRS) - Quality Assurance Surveillance Plan (QASP) in contract Attachment J5.

The contractor shall provide a Quality Management Plan that addresses the contractor’s approach to meet quality and performance standards outlined in the PRS of the QASP.

1.5.3 On-Site Working Conditions, Holidays, and Other Closures: See base IDIQ #M67854-24-R-7603.

1.5.4 Hours of Operation: See base IDIQ #M67854-24-R-7603.

1.5.5 Place of Performance: See base IDIQ #M67854-24-R-7603.

1.5.6 Type of Contract: See base IDIQ #M67854-24-R-7603.

1.5.7 Physical Security Requirements: See base IDIQ #M67854-24-R-7603.

1.5.7.1 Safety: See base IDIQ #M67854-24-R-7603.

1.5.7.2 Marine Corps Base Quantico Installation Gate Access: See base IDIQ #M67854-24-R-7603.

1.5.7.3 Marine Corps Systems Command (MCSC) Facility Access: See base IDIQ #M67854-24-R-7603.

1.5.8 CAC Requirement: See base IDIQ #M67854-24-R-7603.

1.5.9 Identification and Disclosure Requirements: See base IDIQ #M67854-24-R-7603.

1.5.10 Marine Corps Enterprise Network (MCEN) Computer Access: See base IDIQ #M67854-24-R-7603.

1.5.10.1 Contractor Assets Connectivity to the MCEN: See base IDIQ #M67854-24-R-7603.

1.5.10.2 Magnetic Hard Drive Storage Devices: See base IDIQ #M67854-24-R-7603.

1.5.11 Annual Block Training: See base IDIQ #M67854-24-R-7603.

1.5.12 Contracting Officer’s Representative (COR): See base IDIQ #M67854-24-R-7603.

1.5.13 Contractor Manpower Reporting: See base IDIQ #M67854-24-R-7603.

1.5.14 Identification of Contractor Employees: See base IDIQ #M67854-24-R-7603.

1.5.15 Travel/Other Direct Costs: See base IDIQ #M67854-24-R-7603.

1.5.16 Organizational Conflicts of Interest (OCI): See base IDIQ #M67854-24-R-7603.

1.5.17 COR Responsibilities: See base IDIQ #M67854-24-R-7603.

PART 2: GOVERNMENT FURNISHED PROPERTY, EQUIPMENT, AND SERVICES

2.1 General: See base IDIQ #M67854-24-R-7603.

2.2 Services: See base IDIQ #M67854-24-R-7603.

2.3 Government Facilities

The Government can provide access to the facilities located at KCITC in Kansas City, MO, and Government Offices in Stafford, VA as needed for contract performance and meetings.

Access to government facilities in Stafford, VA is limited to meetings and short-duration events. The contractor shall submit an unclassified visit request to coordinate access via the Joint Personnel Adjudication System. No permanent Government workspace will be provided. All access must be coordinated in advance. Any unclassified contractor-furnished laptops must be logged with the entry control point sentry upon entrance. Access hours may be further reduced during the working day before, and the day after, Government holidays for locations not requiring 24/7 access.

Contractors will work in Government facilities only on an occasional basis and will not be assigned government seating. Instead, they will use "hotel" desk units on a temporary basis, as required, in Government spaces. In the Government spaces, Contractors will be provided a port on a first come, first served basis to connect to the MCEN. While the majority of the Government spaces have been outfitted with monitors, there is no guarantee that a monitor will be available at the selected space or that the monitors will connect to the Contractor owned laptop, due to the variance of monitor cables to docking stations and to laptops. The Government does not provide ethernet cables, power cords, mice, keyboards, or other peripherals. There may or may not be a desk phone at the Government space. If there is one, the Contractors may utilize it only for phone calls related to work in performance of the contract. The Government provides Government WiFi onsite for MCEN approved devices. The Government will not provide office supplies.

Access to KCITC requires visit requests in accordance with current KCITC policy. Access to other Government facilities will be coordinated through the PMO.

2.4 Equipment

2.4.1 Asset Tracking/Government Furnished Property (GFP)

The contractor shall support Government asset management activities by providing accountability, tracking, and reporting of GCSS- MC Enterprise hardware and software, licenses, and warranty support information. The contractor shall provide the Government with a Quarterly Hardware and Software Report, per deliverable requirements in Section 5.3.1, Appendix C of this document. The required deliverables include, but are not limited to, hardware and software, and firmware asset data elements as defined by the Government, including, at a minimum, location, serial number, version, model, and processor count.

The contractor shall include software information to support licensing requirements, accountability, and CM including, but not limited to, name version of license, number of licenses used, users for named/concurrent licenses, servers, license unit and associated core processor count, license location, and end-of-life/end-of-support dates and details.

The contractor shall report and document any changes to asset data elements—including, at a minimum, location, serial number, version, model, and processor count--resulting from any change, to include those from CRs and/or warranty actions.

The contractor shall support Configuration Status Accounting (CSA), physical configuration audits, and physical inventories to maintain an accurate accountability of GCSS-MC Enterprise assets.

The Government Furnished Property (GFP) provided under this contract is specified in Attachment J6. The contractor shall furnish their own personal computer equipment, phones, administrative supplies, and office supplies required for performance of this contract.

Upon the receipt of GFP, the contractor shall inventory and complete a signed confirmation of the transfer for the property. The contractor shall report all additions, changes, or deletions to an environment/location for all GFP. The contractor shall notify the COR the next business day if they have received GFP that is having issues or is defective. The contractor shall provide written information adequate to determine GFP issues or defects, to include a description of the defect. Upon completion of need or at the end of contract, the contractor shall return all GFP to the Government.

The contractor shall provide a Quarterly GFP Inventory Report per deliverable requirements in Section 5.3.1, Appendix C of this document. for all GFP.

2.4.2 Hardware and Software Licenses and Support

The contractor shall execute hardware procurements and warranty/support agreements and renewals required to sustain and maintain the system. The contractor shall track and provide a Quarterly Hardware and Software Procurement and Warranty Tracker Report that includes, at a minimum, the status of all hardware, warranty/support renewals and warranty actions executed in accordance with deliverable requirements in Section 5.3.1, Appendix C of this document. The contractor shall include in the Quarterly Hardware and Software Procurement and Warranty Tracker tracking and reporting trends in warranty actions, using the data for lifecycle cost analysis that results in cost-effective warranty recommendations.

The contractor shall determine the most cost-effective hardware recommendations that reduce or minimize lifecycle costs while maintaining compliance. The contractor shall provide all support necessary and incidental to the tracking, procuring, and maintenance of system hardware and system component warranties. This may require that the contractor research and provide analysis of alternatives and deliver necessary technical and administrative information to the COR. When directed by the PMO, the contractor shall document, manage configuration, coordinate, and create and retain system records to dispose of hardware assets.

All purchases of licenses, hardware, and warranty agreements shall be provided to the COR for review prior to procuring them. The purchase is not allowed until it is approved by the COR.

The contractor shall deliver receipts for all hardware and software delivered to and accepted by the Government in the Wide Area Workflow Invoice, Receipt, Acceptance, and Property Transfer (iRAPT) record. The contractor shall prepare the 2-in-1 format in iRAPT and submit all receipt documentation to the COR.

2.4.3 Obsolescence Management

The contractor shall perform obsolescence management services and deliver an Obsolescence Management Plan in accordance with deliverable requirements in Section 5.3.2, Appendix C. The contractor shall establish a Diminishing Manufacturing Sources and Material Shortages (DMSMS) Working Group per the GCSS-MC PDSS Obsolescence Management Plan for all hardware and software system components, to include MTS Systems, User Licenses, and PMO laptops. The contractor shall review and update the Obsolescence Management Plan and report updates annually and more often, as required. The contractor shall continually track and assess hardware and software lifecycles and deliver comprehensive monthly DMSMS Reports for all hardware and software to proactively manage and mitigate obsolescence risks in accordance with deliverable requirements in Section 5.3.1, Appendix C. The Report shall cover a rolling 5-year period (current year and the next 4) for all assets.

The contractor shall notify the PMO about supplier announcements regarding end of life and supply shortages of necessary system hardware and software, potential disruption or cancellation of necessary support services, loss, or impending loss of manufacturers and suppliers of necessary supply items and provisions. The contractor shall perform and deliver technology-related assessments and recommendations for upgrades, migrations, or technical refresh options to mitigate obsolescence risks or issues. The contractor shall implement Government approved solutions in a timely manner. The contractor shall develop plans for associated hardware or software solutions in a Hardware and Software Refresh Plan in Section 5.3.1, Appendix C. The contractor shall incorporate all Government approved obsolescence solutions into the GCSS-MC Technology Roadmap in Figure 2-1 as required. The contractor shall compile and deliver procurement and implementation costs to the Government reflecting the prices to replace obsolete items and obtain and deliver source data to support forecasting of obsolescence risks.

The contractor shall perform support services to dispose of hardware and software assets. The contractor shall perform technical services to prepare obsolete items for disposal in accordance with the Obsolescence Management Plan.

Figure 2-1: GCSS-MC Technology Roadmap

2.5 Government Furnished Information

Government Furnished Information (GFI) is being provided to the contractor in the RFP Section J Attachments solely for its performance of this contract. No modifications to the GFI are allowed unless authorized by the Government. The contractor shall not, without Government authorization, release, disclose, or use in any promotions, any GFI. The contractor shall not disclose GFI to any party outside the Government, use GFI generated during or because of performance of this contract; or use or disclose information derived from GFI in any manner beyond what is necessary for the performance of this contract. GFI is not authorized for use by the contractor for the preparation of any proposal for a follow-on or other contract, or for use in litigation against the Government, unless the disclosure is protected by Federal Law for Whistleblowers or a similar statute. All contractor employees shall sign a non-disclosure agreement (NDA), establishing an enforceable agreement between the Government and the individual contractor employee acknowledging their obligation not to release, disclose, or use in contravention of these requirements, or in any way that would permit or result in disclosure to any party outside the Government, any GFI or the proprietary information of any third party furnished to the contractor employee for the performance of this contract, or gained inadvertently by the employee. Further, the prohibition against release of GFI extends to cover such information whether in its original form, e.g., where the information has been included in contractor generated work, or where it is discernible from materials incorporating or based upon such information. These prohibitions regarding GFI and the requirement to submit an NDA shall apply with equal force to any affiliate of the contractor, any subcontractor, consultant, or any entity into or with whom the contractor may merge or affiliate, or its successors, and shall not expire after any given period. A signed copy of every NDA shall be delivered to the Procuring Contracting Officer for the Contract, and the Ordering Officer for the Task Order, if that’s a separate individual. The following GFI will be provided at the Post Award Conference (PAC):

• Current Master Lesson Files (courseware).

• Course specific training materials.

• Updated Transition-in Plan Criteria.

• Refresh Hardware and Software Plan.

• Interface list and drawing.

• GCSS-MC User’s Manual (UM) 4000-25.

• Air Binder.

• CM.070 Configuration Management Baseline Report for FY23Q4.

• Detailed Test Plans (DTPs).

• PM LI2S-MC Risk, Issue, and Opportunity Management Plan (RIOMP), dated 2022.

• GCSS-MC Sustaining Engineering Plan (SEP) Version 1, dated 24 October 2016

• Current Version of Gold Disk.

The contractor shall immediately make full written disclosure to the COR of any violation by the contractor or an employee of the contractor, whether intentional or unintentional, of the above prohibition, with a copy to the Contracting Officer and Agreements Officer, within 3 business days. The notification shall include a description of the circumstances surrounding the improper disclosure of GFI, a description of the contractor’s actions taken to recover, mitigate and prevent future improper disclosures, and any other relevant information. These provisions apply equally to subcontractors, affiliates, and any other entity whose access to the GFI results from their relationship with the contractor.

PART 3: CONTRACTOR ACQUIRED PROPERTY, EQUIPMENT, AND SERVICES

3.1 General

The Government does not anticipate the need for Contractor Acquired Property, Equipment, or Services.

3.3 Contractor Facilities: See base IDIQ #M67854-24-R-7603.

PART 4: SPECIFIC REQUIREMENTS

4.1 Basic Services

4.1.1 Contractor’s Transition

If the Contract award results in selection of a new contractor, a transition period shall be required to transfer GCSS-MC incumbent contractor responsibilities to the new awardee. The transition task objective is to transfer all roles, responsibilities, and knowledge held by the incumbent contractor over to the new awardee in such ways that minimize any negative impacts to system operations and GCSS- MC Enterprise services.

For the non-incumbent, the Transition-In period is 6 months, starting upon the award of this TO. The Transition-Out period for the awardee of this Contract is 6 months and will occur on the final TO of the IDIQ contract.

4.1.2 Contractor’s Transition-In

The contractor’s Initial Transition-In Plan shall be delivered with the contractor’s proposal in accordance with deliverable requirements in Section 5.3.1, Appendix C. The plan shall be updated to a final version no later than five days after the PAC. The contractor shall deliver weekly updates on their progress toward meeting transition criteria, and readiness to assume full support service responsibilities no later than 6 months after TO award. The contractor shall describe how they will reduce and mitigate potential risks. During the transition-in, the Government will provide the contractor access to the systems, databases, repositories, and facilities as required to execute transition to the contractor’s full support status. This process will be managed by the Government. The Government will provide POCs for facilities operated by different organizations that might follow different access procedures. The Government will provide POCs at the PAC/Project Kick-Off (PKO) meeting. The contractor shall interface with the POCs to gain access to their systems. The contractor shall communicate all issues regarding access to any systems required in the support of this PWS to the COR within 24 hours if the issue is not already resolved. In executing the transition, program stakeholders include, but are not limited to, the LI2S-MC PMO, the incumbent contractor, hosting facilities, support vendors, and the GCSS-MC Enterprise user community. At a minimum, the contractor shall meet the transition-in criteria listed below. The contractor shall add to its plan any other criteria deemed necessary for a successful transition-in.

• Transition organization.

• Coordination of transition-out procedures with incumbent contractor.

• Staffing, including, but not limited to, use of transition personnel.

• Transition management.

• Transition communications.

• Establishing knowledge of GCSS-MC Enterprise system’s applications and operations, including, but not limited to, ESD services.

• Review of GCSS-MC documentation, including, but not limited to, CRs, Backlogs, and Engineering Change Proposals (ECPs).

• Assumption of support responsibilities, including, but not limited to, operations, PROD and DEV environments, and support functions.

• Transition schedule, including, but not limited to, Plan of Action and Milestones.

• Managing transition risks and issues.

• Verification of asset management repository.

• Verification of all Government Furnished Equipment and GFI.

• Verification of current system baselines.

The Transition-In period shall begin upon award of this first TO. During the Transition-In period, the contractor shall acquire knowledge of, and experience with GCSS-MC Enterprise PDSS efforts and processes sufficient to commence full performance of required services.

4.1.3 Section Reserved.

4.1.4 Business Relations

The contractor shall integrate and coordinate all activities needed to execute the requirement.

4.1.5 Administration

4.1.5.1 Contract Management

The contractor shall establish processes and assign appropriate resources to effectively perform the work stated in this PWS. The contractor shall identify primary and alternate contractor personnel POCs assigned to this TO. The contractor shall assign work and maintain proper and accurate time keeping records for personnel assigned to this TO to meet the reporting requirements contained in FAR Clauses 52.204-14 and 52.204-15.

4.1.5.2 Subcontract Management

The contractor shall be responsible for any subcontract management necessary to integrate work performed on this contract and shall be responsible and accountable for subcontractor performance on this contract. The prime contractor will manage work distribution to ensure there are no OCIs or appearances of OCIs.

4.1.5.3 Contractor Employees, Conduct, Disciplines, Specialties, and Other Requirements

The contractor shall accomplish the assigned work by employing and utilizing qualified personnel with appropriate certifications.

Contractor employees shall identify themselves as contractor personnel by introducing themselves, or being introduced, as contractor personnel and displaying badges or other visible identification distinguishing them as contractors for meetings with Government personnel. In addition, contractor personnel shall appropriately identify themselves as contractor employees in telephone conversations and in formal and informal written correspondence, including email.

4.1.5.4 Non-Personal Services

The Government shall neither supervise contractor employees nor control the method by which the contractor performs the required tasks. Under no circumstances shall the Government assign tasks to, or prepare work schedules for, individual contractor employees. It shall be the contractor’s responsibility to manage its employees and to guard against any actions that could be characterized as personal services or convey the perception that personal services are being delivered. If the contractor believes that any actions constitute, or are perceived to constitute, personal services, the contractor is responsible to immediately notify the Procurement Contracting Officer (PCO) and follow up to seek the PCO’s resolution.

The contractor is responsible for the performance of its personnel and the personnel of its subcontractors. The contractor shall have appropriate controls in place to engage personnel who are fully qualified for the work assigned to them, who will not endanger persons or property in performance of the contract, who are not under the influence of alcohol, drugs, and any other incapacitating agent, who perform in accordance with the PWS requirements, who are willing and able to comply with installation rules, and, for any contractor personnel outside the Continental United States, who are willing and able to abide by any applicable Status of Forces Agreement. The contractor shall be responsible for removing personnel who fail to perform in accordance with the contractor’s mandated controls and shall provide qualified replacement personnel at no cost to the Government or delay in performance.

An Officer of the company shall execute a Privacy and Security Non-Disclosure Statement, on behalf of all employees working on this contract, or each individual working on the contract shall execute the Privacy and Security Non-Disclosure Statement. Work on this project requires personnel to have access to Privacy Act Information. Personnel shall adhere to the Privacy Act, Title 5 of the United States (U.S.) Code, Section 552a, and applicable agency rules and regulations.

4.1.5.5 Risk Management

The contractor shall implement risk management processes to identify and mitigate project and technical risks and provide metrics in accordance with Monthly Metrics deliverable requirements in Section 5.3.1, Appendix C to monitor project status. The contractor shall participate with the Government to review and collaborate on risk assessments and mitigation approaches in accordance with the current DoD Risk, Issue, and Opportunity Management Guide for Defense Acquisition Programs, and the PM LI2S-MC Risk, Issue, and Opportunity Management Plan (RIOMP) dated 2022.

4.1.5.6 Virtual Dashboard

All Contract Data Requirements List (CDRL) deliverables shall be prepared in accordance with Department of Defense Instruction (DoDI) 5200.48, Controlled Unclassified Information (CUI) and submitted to the COR in accordance with the CDRL submission instructions.

The contractor shall provide all TO deliverables electronically in a form that is compatible with the current Microsoft (MS) Office Suite, unless otherwise specified (e.g., code delivery), to the COR. The contractor shall post Government specified product deliverables to the Government’s MCEITS SharePoint portal at https://mcscviper.usmc.mil/sites/GCSS-MC/PdMPDSS/SitePages/ HomePage.aspx.

The contractor shall develop and maintain a CDRL Virtual Dashboard Status Report for tracking, and management of CDRLs in accordance with deliverable requirements in Section 5.3.1, Appendix C. The site shall be located on a designated Government SharePoint Portal and be continuously accessible to GCSS-MC PMO employees and the Government’s support contractors. The contractor shall brief the CDRL Virtual Dashboard during weekly status meetings with the PMO.

4.1.5.7 Key Positions

A requirement of this contract is to maintain stability of personnel performing the contract effort. Accordingly, the contractor agrees to assign to this contract personnel whose qualifications meet the minimum requirements established in Table 4-1 below.

To the maximum extent possible, the Contracting Officer shall be notified in writing of any proposed substitution at least 45 days, or 90 days if a security clearance is to be obtained, in advance of the proposed substitution. The contractor shall submit a complete resume of the substitute employee in advance of their performing on the contract.

Specifically, the contractor shall provide skilled employees capable of performing program requirements and that meet the qualifications required in the contract. The contractor shall provide personnel for the following Key Positions: Program Manager, Chief Engineer, Information System Support Lead, and Operations and Support Lead. Minimum qualifications for each Key Position are listed in Table 4-1 below. The experience required is in the job positions indicated. Any personnel that are not certified to the required standard within 30 days after award/appointment would be considered unqualified and not able to serve in a Key Position.

Table 4-1: Key Positions

KEY POSITION TABLE

Billet Function Education & Years of

Experience Certifications Qualifications and Experience

Program Manager

• Masters, Information

Systems; or

• Masters, Business

Administration; or

• BS/BA + Min 8 years’ experience

• PMP

• IAM Level II

• ITIL4 ITIL Managing

Professional

• 5+ years’ experience managing programs or portfolio of programs in excess of $25M/year in revenue.

• 5+ years management experience in an IT environment directing 50 or more personnel.

• 5+ years’ experience with operational and technical requirements management similar to what is expected for GCSS- MC/LCM Increment 1 PDSS.

• 5+ years’ experience in a network operations or IT operations center.

infrastructure, and emerging technologies

• 3+ years’ experience overseeing Agile software implementation.

Chief Engineer

• MS +10 years; or

• BS Eng + 12 years;

or

• BS CS +12 years

• Oracle EBS

• ITIL4 Practice

Manager Plan, Implement and Control

• IAT Level II

(All required)

• 5+ years Oracle EBS experience

• 5+ years technical experience in a network operations or IT operations center.

• 5+ years’ experience directing 50 or more technical staff members.

• 3+ years in cloud system management.

https://mcscviper.usmc.mil/sites/GCSS-MC/PdMPDSS/SitePages/%20HomePage.aspx

Information Systems Support Lead

• BS/BA +10 years; or

• IAM/IAT Level III

• CISSM/CASP/CAP

(Required)

• 7+ years IA experience

• 3+ years’ experience in cloud computing security.

Service Desk Lead

• BS/BA +8

Manager: Monitor, Support and Fulfill (Required)

• HDI-TSP (Required)

• 7+ years overseeing Service Desk operations, including service request, incident & problem ITIL processes.

• 3+ years’ experience managing a 24/7/365 Service Desk supporting 15+K Users.

Operations Lead

• BS/BA +8

Manager: Plan, Implement and Control (Required)

• 5+ years managing daily IT production operations ensuring system achieves established performance objectives.

• 7+ years’ experience working in a network operations or IT operations center.

• 5+ years’ experience implementing IT operations concepts, practices, and procedures.

4.2 Non-disclosure Agreements (NDAs): See base IDIQ #M67854-24-R-7603.

4.3 Program Management

The contractor shall perform program management services that support planning, administration, execution, reporting, and continuous improvement of cost, schedule, and performance to satisfy the requirements identified in this PWS.

The contractor shall write and deliver a PMP for Government review and approval in accordance with deliverable requirements in Section 5.3, Appendix C. The contractor shall deliver regular updates to the PMP describing changes to the processes and procedures associated with how the contractor will internally manage and execute tasks required in the TO. The contractor shall deliver accurate and timely cost, schedule, and performance information in PMP updates throughout the lifecycle of the individual tasks.

The contractor shall address the following planning elements in the initial PMP and the subsequent PMP updates:

• Managing and executing TO performance.

• Identifying, monitoring, controlling, mitigating, and reporting risks.

• Managing communications between the contractor and the Government, its affiliates, and stakeholders.

• Developing and maintaining Standard Operating Procedures (SOPs) for all tasks and procedures pertaining to GCSS-MC PDSS, PROD/PSS, DR/COOP and GCSS-MC Enterprise user needs and provide information to address specific needs/issues forwarded from Headquarters, Marine Corps Installations and Logistics (I&L), and the GCSS-MC Marine Corps Logistics Command user representative.

• Developing and maintaining an overall work breakdown structure.

• Developing and maintaining task schedule and performance metrics.

• Developing assumptions and constraints.

• Managing CDRLs.

4.3.1 PM Tools

The contractor shall ensure the tools it uses to manage, deliver, and support the GCSS-MC Enterprise are interoperable with the PMO tools listed below and associated with this contract.

• Solutions Business Manager (SBM).

• Hewlett Packard Application Lifecycle Management (HP ALM®).

• Dynamic Object-Oriented Requirements System (DOORS®).

• Cameo Systems Modeler.

• GitLab.

• Fortify Static Code Analyzer.

• MS SharePoint.

4.3.2 Programmatic Documentation

The contractor shall deliver, update, and maintain programmatic and system documentation as required and in accordance with the tasks described in this PWS. Additionally, documentation shall be updated concurrently with system changes and releases. System documentation that may require development and updates include the following, but are not limited to:

• Performance and Schedule Data.

• GCSS-MC documentation, including, but not limited to, CRs, Backlogs, and ECPs.

• Root Cause Analysis (RCA) updates.

• MTS documentation.

• Tape Backup process and documentation.

• Training Studies and documentation.

• Hardware and Software documentation.

• Test documentation.

• Code migration documentation.

• Change to System Documentation.

• Systems Engineering Management Plan (SEMP).

• Security/IA/Cybersecurity documentation.

• Audit documentation.

4.3.3 Meetings/Integrated Product Teams (IPTs)

4.3.3.1 Meetings

The contractor shall host status meetings as required, deliver task updates, and prepare and deliver Meeting Minutes. The contractor shall deliver Monthly Status Reports (MSRs) in accordance with deliverable requirements in Section 5.3, Appendix C.

The contractor shall attend the meetings required in this PWS. The COR will determine (on a by-case basis) whether a meeting is in person or virtual. The COR may identify specific contractor personnel to attend (in person) on-site at the Government facility or at a Government-identified location. Contractor personnel shall display badges or other visible identification that identifies them as contractor personnel whenever they are in meetings with Government personnel.

The contractor shall prepare and deliver Meeting Agendas and Minutes per deliverable requirements in Section 5.3, Appendix C, and conference support to include coordinating and scheduling…