RFP Attachment L-4_ManSys_Task_Order_PWS.pdf

M95494-22-R-0013 RFP Attachment L-4

Performance Work Statement for Sample Task Order 2, Manpower Systems

1.0 Background

The Technology Services Organization (TSO) operates and sustains several mature United States Marine Corps (USMC) Business Information Systems (BISs). TSO is responsible for several layers of Information Technology (IT) in support of its BISs, from the infrastructure level through the software application layers.

1.1 Scope

This Task Order (TO) will provide sustainment services as defined in Section 2.0 to a subset of TSO BIS and business processes. The following BISs are within scope of this TO as indicated in each subsection of Section 2.0.

1.1.1 Automated Performance Evaluation System (APES)

APES is the USMC BIS for creating, processing, and reviewing the fitness reports (FITREPs) of senior enlisted Marines above the E-5 level and Marine officers. The system’s user base consists of Marines as well as their reporting seniors and reviewing officers.

1.1.2 Marine Corps Total Force System (MCTFS)

MCTFS is the integrated pay and personnel system for active duty and reserve Marines, and the authoritative source of data for all Marine Corps pay and personnel information consisting of over 500,000 records.

1.1.3 Models

Models is the USMC BIS for creating, manipulating, and viewing force structure models and manpower data sets.

This BIS is leveraged by personnel within Manpower and Reserve Affairs (M&RA) Department, Headquarters Marine Corps (HQMC).

1.1.4 Marine Online (MOL)

MOL is the web-based counterpart of MCTFS, providing pay and personnel data to over 160,000 unique web users every month.

1.1.5 Optical Data Imaging – Records Management System (ODI-RMS)

ODI-RMS provides HQMC, M&RA, MMRP personnel a means for storing, requesting, viewing, correcting, retiring, and loaning Official Military Personnel Files (OMPFs). ODI-RMS is the authoritative data source for all USMC performance evaluation and promotion functions. ODI-RMS also provides promotion and selection board support for HQMC.

1.1.6 Requirements Transition and Manpower Management System (RTAMMS)

RTAMMS is the USMC BIS for the manpower management of Marine reservists. The BIS consist of three modules for managing reserve drills, medical entitlements, and inventory management.

1.1.7 Total Force Retention System (TFRS)

TFRS is the USMC BIS for retaining (reenlisting or extending) or reclassifying active duty and active reserve Marine personnel. The system’s user base consists of Marines.

1.1.8 Total Force Data Warehouse (TFDW)

TFDW is the USMC BIS for storing and retrieving historical manpower data. The system serves as the single, authoritative source to satisfy Congressional and DoD mandated end strength reporting requirements, to provide decision-support capabilities, and to provide analytical capabilities to enable business process insight, analysis and improvement.

1.1.9 Web-based Manpower Assignment Support System (WebMASS)

WebMASS is the USMC BIS for managing active duty and active reserve Marine personnel assignments, conducting financial management and analysis related to Permanent Change of Assignment (PCA) and Permanent Change of Station (PCS) budgeting, and providing hard copies of orders to enable individual Marines to complete administrative requirements to execute household shipments. This BIS is leveraged by assignment personnel within M&RA Department, HQMC.

2.0 Tasks

In accordance with Section 2.0 of the Performance Work Statement (PWS) under the base Contract, the Contractor shall perform the following tasks. Unless otherwise specified, all deliverables other than software source code shall be delivered to TSO via a Jira ticket associated with the tasking. Software source code shall be delivered via check-in to government furnished software repositories.

2.1 Software Development Lifecycle (SDLC) (Base Contract PWS 2.1) — MCTFS

2.1.1 Operational Test Support

The Contractor shall provide technical support for software releases to include operational testing, research, and analysis in accordance with the standards described in the MCTFS Operational Test Manual located in the TSO Document Management System (DMS) on TSO SharePoint. Operational Test discrepancies shall be documented via Jira tickets. After analysis, if the Government determines that a design or programming change is required, the Contractor shall coordinate with the programmer that made the modification to take corrective action. The Contractor shall resolve tickets within five (5) business days. If the Contractor is unable to resolve tickets within this time, a comment should be made in the ticket providing status and the anticipated resolution date.

2.1.2 Programming Production Trouble Reports (PTRs)

The Contractor shall complete design, programming, unit testing, and peer review for MCTFS PTRs. Typically, ten

(10) PTRs are required each month, with the average PTR being completed in less than a week. PTRs will be prioritized such that they will not typically be worked concurrently. PTRs are generated from technical system issues as well as problematic business logic, so the Contractor shall analyze pay and personnel business logic and translate it into effective and secure designs and code within the MCTFS mainframe environment.

2.1.3 MCTFS Programming Technical Support

The Contractor shall provide technical reviews and research on proposed technical enhancements to MCTFS such as streamlining existing processes and conversions of data storage/access methods. Technical reviews shall include analyses and impact on critical computer resources and potential risks of changes. The Contractor shall review and monitor projects during sustainment and testing in order to maintain an awareness of all changes being made. The Contractor shall review projects to provide technical guidance and recommendations on ways to proceed.

2.1.4 Estimates for Software Release and Standalone Software Change Requests

The Contractor shall provide hour estimates within the MCTFS Estimating Management System (EMS) on all Software Release and Standalone Software Change Requests (SCRs) as assigned and include all replacement pages and addenda provided by the functional customer. This estimate will include Design, Programming, and/or Test tasks depending on what portions are tasked to the Contractor.

2.1.5 Sustainment Support

The Contractor shall provide sustainment of the MCTFS residing on an International Business Machines (IBM) z/OS mainframe OS utilizing Common Business Oriented Language (COBOL), Job Control Language (JCL), and Customer Information Control System (CICS) and leveraging CI/CD tools already established within MCTFS SDLC. Tasks shall be submitted by SCR and Functional Change Request (FCR) and tracked within Jira. Typically 10 SCRs and 10 FCRs are required each year. SCRs and FCRs will be prioritized such that they will not typically be worked concurrently. The Contractor shall follow design requirements documented within the Design Logic Table (DLT) application provided by the government. The Contractor is required to architect solutions based upon the DLT & SCR/FCR requirements, program, and unit test the solutions providing the impacted Configuration Items (CIs) to the government for review/approval and acceptance testing.

2.2 SDLC (Base Contract PWS 2.1) — Web and Client/Server Systems

The Contractor shall provide SDLC support for the web and client/server BIS and their subcomponents to address emergent sustainment requirements. Such sustainment requirements include assessing, designing, implementing, and testing system changes in response to production outages, system bugs, and system change requests.

2.2.1 MOL Architecture and Engineering Support

The Contractor shall provide architecture and engineering support to ten (10), four (4) week sprints. Documentation generated by the Contractor shall be submitted to the government by attaching it to the Jira ticket that documents the support requirement. The span of architecture and engineering support includes:

1. Assess the architecture of MOL, its subcomponents, and its logical interfaces in the context of emergent sustainment requirement and make written recommendations on architectural changes or additions required to address the requirements.

2. Assess MOL subcomponents in the context of emergent sustainment requirement and make written recommendations on the engineering design and implementation approach for the relevant subcomponents.

3. Document government-approved architecture and engineering changes via the update or creation of system architecture and subsystem engineering documents such as logical design diagrams, data flow diagrams, and interface diagrams.

4. Refine architecture and engineering approaches and documentation based on iterative feedback from software coders.

2.2.2 Software Sustainment Support

The Contractor shall provide software sustainment support utilizing Agile-Scrum methodologies. The Contractor shall provide approximately eleven thousand eight hundred (11,800) points worth of stories on the Fibonacci scale.

Tasks for each story shall include:

1. Review and update the product vision and backlog, to included updating priorities and sizes.

2. Develop and refining user stories.

3. Participate in Sprint Zero or Joint Application Development (JAD) sessions to conduct impact analyses.

4. Estimate all backlog items using the Fibonacci scale.

5. Plan and design sprints to define the sprint goal, establishing the “definition of done”, and select user stories to be addressed.

6. Develop software design documentation based on user story and upload to the corresponding Jira tickets.

7. Program software changes based on story parameters, participate in product peer reviews, Modify initial software changes based on feedback form peer reviews and source code analysis software.

8. Execute software testing as defined within user story.

9. Deliver software changes to the TSO source code repository and supplemental documentation to the corresponding Jira tickets.

10. Participate in sprint review and sprint retrospectives to contribute lessons learned.

The total workload will be split across the BISs programming languages as follows.

Programming Languages Fibonacci Points C# 1,620

C++ 180 Fortran 180

Java 8,460 Power Builder 360

2.2.2.1 APES

The APES BIS is written in Java and is a low complexity system form a software architecture and business logic perspective. The tasks for this system will be a mix of application maintenance and upgraded features, but the number of tasks is projected to be low. This system’s sustainment team operates on an iterative sprint cycle and releases to production as-needed.

2.2.2.2 Models

The Models BIS is written in C++ and Fortran. It is a high complexity system form a software architecture and business logic perspective. The tasks for this system will be a mix of application maintenance and upgraded features, but the number of tasks is projected to be low. This system’s sustainment team operates on a monthly sprint cycle and releases to production monthly.

2.2.2.3 MOL

The MOL BIS is written in C# and Java. It is a high complexity system form a software architecture and business logic perspective. The tasks for this system will be a mix of application maintenance and upgraded features, and the number of tasks is projected to be high. This system’s sustainment team operates on an iterative sprint cycle and releases to production monthly.

2.2.2.4 ODI-RMS

The ODI-RMS BIS is written in Power Builder. It is a high complexity system form a software architecture and business logic perspective. The tasks for this system will be application maintenance only. This system’s sustainment team operates on an iterative sprint cycle and releases to production as-needed.

2.2.2.5 RTAMMS

The RTAMMS BIS is written in Java. It is a medium complexity system form a software architecture and business logic perspective. The tasks for this system will be a mix of application maintenance and upgraded features, and the number of tasks is projected to be medium. This system’s sustainment team operates on an iterative sprint cycle and releases to production as-needed.

2.2.2.6 TFRS

The TFRS BIS is written in C# and is a high complexity system form a software architecture and business logic perspective. The tasks for this system will be application maintenance only, and the number of tasks is projected to be low. This system’s sustainment team operates on an iterative sprint cycle and releases to production as-needed.

2.2.2.7 WebMASS

The WebMASS BIS is written in C# and ASP.NET. It is a medium complexity system form a software architecture and business logic perspective. The tasks for this system will be a mix of application maintenance and upgraded features, and the number of tasks is projected to be high. This system’s sustainment team operates on an iterative sprint cycle and releases to production as-needed.

2.3 Data and Platform Analysis (Base Contract PWS 2.4)

The Contractor shall provide Business Intelligence (BI) engineering support for the MOL, Models, RTAMMS, and TFDW BISs. The support tasks shall comprise of scripting/macro writing, software product maintenance and upgrades, and performance tuning. The Contractor shall perform these support functions in government furnished development and production environments following TSO’s change management procedures and all other applicable configuration management plans.

2.3.1 IBM Planning Analytics and Certent Disclosure Management (CDM)

1. Manage twelve (12) Tables Manager 1 (TM1) planning cubes with weekly and monthly data loads and processing.

2. Provide TM1 analytical authority via TSO-provided tools, with the end deliverable remaining in the tool for system owner use.

2.3.2 Statistical Analysis System (SAS) Analytics

1. Support twenty five (25) users with the authoring of reports to be executed within SAS Analytics.

2. Historically provided sixty five (65) data pulls per year with monthly data loads.

2.3.3 IBM Cognos Analytics

Support six (6) instances of Cognos deployments with two hundred and fifty (250) users via the following tasks.

1. Provide data mapping services, to include documenting database interconnectivity, for delivery to system owners.

2. Provide BI data modeling within TSO-provided tools, with the end deliverable remaining in the tool for system owner use.

3. Provide BI report authoring via TSO-provided tools, with the end deliverable remaining in the tool for system owner use.

4. Provide engineering support leveraging scope and scale of capabilities within the BI product, for system owner use

5. Provide technical documentation on BI tool and database content, for delivery to system owners.

6. Provide BI tool administration to include configuration changes.

7. Provide BI tool software patching on a monthly basis.

2.4 Business Process Management (Base Contract PWS 2.7)

2.4.1 Business Process Analysis

The Contractor shall provide business process analysis supporting software sustainment utilizing Agile-Scrum methodologies. The Contractor shall complete approximately four thousand (4,000) tasks during the period of performance, which supports the stories executed by the sustainment teams in Section 2.2.2. Tasks shall include:

1. Evaluate business systems and services for functional recommendations, recommend optimization strategies to functional sponsors for determination of implementation.

2. Evaluate business systems and services, anticipating requirements, uncovering areas for improvement, and developing and implementing solutions.

3. Formulate and define systems scope and objectives through research and fact-finding combined with a basic understanding of business systems and service requirements.

4. Assist in formulating and defining software sustainment functional user stories including the development of acceptance criteria to be used as the baseline for testing.

5. Assist in managing projects, developing project plans, and monitoring performance.

6. Document and communicate the results of project efforts.

7. Perform requirements analysis of business and user needs, create requirements documentation, and translate business and user requirements into proper system requirement specifications and proper acceptance criteria/testing.

8. Simulate or recreate user problems to resolve operating difficulties. Recommend systems modifications to reduce user problems via user story collaboration.

9. Perform Data Analysis using SQL and/or Cognos Analytics in association with user stories to ensure solutions meet functional needs and requirements.

10. Serve as a liaison by participating and conducting meetings and presentations to share ideas and fact finding, and to gather critical information from various stakeholders and users to produce useful output.

11. Effectively communicate insights and plans to cross-functional team members and management associated with functional changes.

12. Create, document, and perform JIRA Xray test procedural steps and testing to document and validate system modifications.

13. Identify, perform and assist in the acceptance testing of systems modifications and software bugs.

14. Identify and perform testing for acceptance criteria necessary for regression testing to ensure system modifications does not impact current system functionality.

15. Identify and document software bugs in user story format including defining acceptance criteria.

16. Simulate or recreate user problems to resolve operating difficulties. Recommend systems modifications to reduce user problems.

17. Prepare training tools to support the end user to include but not limited to Quick Start Guides, SR Briefs, Tech Docs, etc.

18. Prepare, update, and maintain system, troubleshooting, process and operations documentation, including user manuals.

3.0 Administrative Tasks

Performance under this Task Order shall be tracked and reported in accordance with Section 3.3 and 3.5 of the PWS under the base Contract.

4.0 Place of Performance

Work will be performed at a Contractor facility.

5.0 Period of Performance

The anticipated period of performance is as follows:

Period of Performance Date of Commencement Date of Completion Base 11/14/2022 11/13/2023

Option One 11/14/2023 11/13/2024 Option Two 11/14/2024 11/13/2025

Option Three 11/14/2025 11/13/2026 Option Four 11/14/2026 11/13/2027

6.0 Key Personnel

In accordance with Section 6.0 of the Contract, the Key Personnel assigned to this Task Order are considered to be essential to the work being performed. The Government prefers these key personnel to meet or exceed the following criteria:

• Senior Mainframe Application Engineer – The Senior Mainframe Application Engineer is responsible for analyzing, planning, designing, and documenting changes to mainframe software applications written in COBOL that execute in a batch or online CICS environment within a z/OS based environment. The mainframe application engineer formulates or updates BIS architectures and assists mainframe software sustainers with the implementation and test of architectures.

o Experience:

6 years or more in engineering enterprise-scale mainframe software applications 6 years or more implementing and updating DoD pay and personnel business rule logic.

4 years or more in engineering systems within the constraints of the MCAAP or other Risk

Management Framework implementations.

Experienced in development of operational and system level architecture views.

• Senior Web Systems Engineer – The Senior Web Systems Engineer is responsible for analyzing, planning, designing, and documenting changes to web applications written in Java and running within a Linux or Windows server environment. The Senior Web Systems Engineer formulates or updates BIS architectures and assists web software sustainers with the implementation and test of architectures.

o Experience:

5 years or more engineering enterprise-scale web software applications 4 years or more implementing and updating DoD pay and personnel business rule logic.

4 years or more in engineering systems within the constraints of the MCAAP or other Risk

Management Framework implementations.

Experience in architecting, implementing, and sustaining custom-written single sign-on systems.

Ability to support multiple Agile or Kanban software sustainment teams simultaneously.

Experienced in development of operational and system level architecture views.

6.1 Substitution of Key Personnel

Substitution of Key Personnel shall be in accordance with Section 6.1 of the Contract.

7.0 Personnel, Training, and Certification Requirements

Personnel, Training, and Certification Requirements shall be in accordance with Section 7.0 of the Contract.

For this TO, personnel supporting tasks in Section 2.3 must meet Information Assurance Technical (IAT) Level II baseline certification requirements and provide evidence of technical training in their technical domain within the past 364 days.

8.0 Task Order Management

This task order will be managed in accordance with Section 8.0 of the Contract.

9.0 Performance Requirements Summary (PRS)

The Contractor shall be evaluated in accordance with Section 9.0 of the Contract.

10.0 Government Furnished Equipment and Information

10.1 Government Furnished Equipment (GFE)

No GFE under this Task Order.

10.2 Government Furnished Information (GFI)

In addition to the requirements set forth in Section 10.2 of the Contract, the following For Official Use Only documents shall be provided as GFI.

1. MOL SDLC Standard Operating Procedure

2. MCTFS Operational Test Manual

3. USMC Enterprise Cybersecurity Manual 018, MCAAP

11.0 Clearance, Access, and Security Requirements

Clearance, Access, and Security Requirements shall be in accordance with Section 11.0 of the Contract.

12.0 Privacy Act and HIPAA

All services performed relative to the requirements identified in this PWS allow access to unclassified or sensitive information covered by the Privacy Act of 1974 and other DoD and USMC regulations. Some information provided by the Contractor during the application process may be subject to the Health Insurance Portability and Accountability Act (HIPAA).

13.0 Travel

Travel under this Task Order shall be in accordance with Section 13.0 of the Contract. TSO estimates that fifteen

(15) trips averaging four (4) days per trip will be required to Indianapolis, IN and that fifteen (15) trips averaging four (4) days per trip will be required to Quantico, VA to support technical collaboration sessions that cannot be effectively accomplished via remote means.

14.0 Non-Personal Services

Contractor employees performing services under this contract and its Task Orders will be controlled, directed, and supervised at all times by Contractor management personnel. Contractor management shall ensure all employees comply with the performance work standards outlined in this PWS. Contractor employees shall perform their duties independent of, and without the supervision of, any Government official or other Defense Contractor. The tasks, duties, and responsibilities set forth in this PWS shall not be interpreted or implemented in any manner that results in any Contractor employee creating or modifying federal policy, obligating the appropriated funds of the United States Government, overseeing the work of federal employees, providing direct personal services to any federal employee, or otherwise violating the prohibitions set forth in Subparts 7.5 and 37.1 of the Federal Acquisition Regulation (FAR). The Government will grant Contractor access to the facilities and will perform the inspection and acceptance of the completed work.