RFP Attachment L-4_SABRS_Task_Order_PWS.pdf

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

Performance Work Statement for Sample Task Order 3, SABRS Support

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 Standard Accounting, Budgeting, and Reporting System (SABRS)

The SABRS BIS consists of several subsystems which integrate the accounting, budgeting, and financial reporting functions of the Marine Corps and Navy. SABRS satisfies the financial information requirements of Marine Corps users at all organizational levels, from the fund administrators at each command to appropriation sponsors at Headquarters Marine Corps (HQMC). The BIS interfaces with numerous other governmental accounting, supply, and personnel systems.

1.1.2 SABRS Management Analysis Reporting Tools Service (SMARTS)

The SABRS Management Analysis Reporting Tools Service (SMARTS) BIS utilizes an Oracle database and IBM Cognos BI (Business Intelligence) to provide the reporting service for SABRS data. All relevant SABRS files have been mapped to the SMARTS database instance and schemas of twenty five (25) tables. SMARTS allows access to standard or canned reports but also provides users the ability to create their own reports based on data elements contained in the SMARTS data model. Information updated in SMARTS comes from a total of twenty four (24) SABRS files, four (4) SABRS table files, one (1) SABRS table maintenance file, and fifteen (15) sequential files.

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 will 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)

2.1.1 SABRS

The Contractor shall provide software sustainment services for the SABRS BIS, a mainframe system written in the Natural programming language and supported by the adaptable database system (ADABAS).

2.1.1.1 Programming Production Trouble Reports (PTRs)

The Contractor shall complete design, programming, unit testing, and peer review for SABRS PTRs. Typically, eight (8) PTRs are required each month, with the average PTR being completed in less than a week. 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 SABRS mainframe environment.

2.1.1.2 SABRS Programming Technical Support

The Contractor shall provide technical reviews and research on proposed technical enhancements to SABRS such as streamlining existing processes, 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.1.3 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 SABRS Standard Project Procedures located in the TSO Confluence system. 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 create, document, and perform JIRA Xray test procedural steps and testing to document and validate system modifications. 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.1.4 Sustainment Support

The Contractor shall provide sustainment of the SABRS residing on an International Business Machines (IBM) z/OS mainframe OS utilizing Natural, Job Control Language (JCL), and Customer Information Control System (CICS).

The Contractor shall follow design requirements documented within the SABRS functional design documents located within TSO Confluence to start, stop, or modify job execution to fix anomalous system activity. The contractor shall provide this support during core business hours and on an on-call basis during nights, weekends, and federal holidays.

2.1.2 SMARTS

The Contractor shall provide software sustainment services for SMARTS.

The Contractor shall provide software sustainment support utilizing Agile-Scrum methodologies. The Contractor shall provide approximately 500 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 design documentation based on user story and upload to the corresponding Jira tickets.

7. Program sustainment changes based on story parameters, participate in product peer reviews, and modify initial capability changes based on feedback from peer reviews and coding analysis.

8. Execute design and sustainment testing as defined within SPRINT user stories.

9. Deliver reporting and design changes to the TSO source code repository and any supplemental documentation to their corresponding Jira tickets.

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

2.2 Data and Platform Analysis (Base Contract PWS 2.4)

The Contractor shall provide Business Intelligence (BI) engineering support for the SMARTS. The Contractor shall perform the following tasks during each 4 week sprint for SMARTS (6 database) within the IBM Cognos Analytics components of SMARTS.

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 Release Management activities supporting sustainment efforts, for delivery to system owners.

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.

8. Provide BI tool monitoring to include troubleshooting and performance enhancement recommendations.

9. Provide support for BI tool and environment recovery.

2.3 Mainframe BIS Operations (Base Contract PWS 2.6)

The Contractor shall provide mainframe BIS operations support for the SABRS BIS.

2.3.1 Mainframe Production Control Support

The Contractor shall provide mainframe production control support seven days per week, every week of the year.

1. Develop Software Release (SR) spreadsheet of jobs which will be utilized throughout each release.

2. Maintain all daily/weekly/monthly/on-request Job Control Language (JCL) jobs as directed via Jira tickets.

SABRS runs the following Control M jobs across multiple break fix, test, and production environments.

o 654 jobs, daily cycle o 454 jobs, weekly cycle o 534 jobs, quarterly cycle o 565 jobs, weekly cycle

3. Design, test, and implement changes as needed.

4. Provide Tier 2 release management support utilizing the Treehouse Software N2O application.

5. Monitor and troubleshoot issues with batch jobs following TSO production control documentation.

6. Provide daily status reports via Jira or e-mail.

2.3.2 ADABASE Support

1. Provide daily monitoring of database reports and report events and incidents using the TSO-provided Key Performance Indicators (KPIs).

2. Follow up on findings discovered during the database monitoring process utilizing the TSO incident and event reporting processes.

3. Store audit artifacts as directed via Jira ticket into the TSO Audit document repository.

4. Perform necessary database maintenance such as run status commands (RUNSTATs), image copies, reorganization commands (REORGs), monitoring database size, troubleshooting database issues, etc. as requested in Jira tickets and provide documented results to the requestor via Atlassian Suite (Jira, Confluence).

5. Perform database refresh and copy data to sustainment and test databases as requested.

6. Complete incoming Database Administrator (DBA) tickets in Jira and, for email requests from groups unable to submit tickets via Jira, write a Jira ticket to support the request.

7. Perform performance tuning.

8. Monitor storage capacity and recommend increases as needed.

9. Determine if file mods impact any normal DBA processes or jobs.

10. Provide natural security administration Tier 1 support.

11. Provide account management in accordance with Terminal Area Security Office (TASO) Jira tickets.

12. Investigate and resolve issues with data (e.g. missing, file formats, permissions, etc.).

13. Perform Access request function for the Mainframe DBA and Data Analysis (DA) groups.

14. Create Account ID for new users, delete users when appropriate, and perform password resets and remove suspensions when requested.

2.3.3 Mainframe Engineering Support

1. Troubleshoot security and other problems as reported.

2. Perform performance tuning.

3. Maintain the log for additions/deletions of reports.

4. Provide input and execute Requests for Assistance (RFAs).

5. Maintain Information Management System (IMS) in-house documents for historical purposes.

6. Analyze current security configurations and attach a written report to the applicable Jira tickets. Make formal recommendations through the Mainframe Engineering team for modifications when necessary.

7. Troubleshoot security issues and determine the necessary corrections.

2.3.4 General support for all three major tasks above

1. Create and update existing process and system documentation in the SABRS document repository, providing the final documents to the government via the applicable Jira tickets.

2. Troubleshoot security and other problems as reported.

3. Provide design, programming, and testing assistance to Sustainment Teams.

4. Attend regularly scheduled team meetings and any other meetings as assigned. Regular scheduled meetings include daily scrum meetings, weekly engineering and release meetings.

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 Systems Engineer – The Senior Mainframe Systems Engineer is responsible for analyzing, planning, designing, and documenting application installation and operations within a z/OS based mainframe BISs. The Senior Mainframe Systems Engineer leads infrastructure planning, application support, infrastructure analysis and assessment, and infrastructure test and troubleshooting.

o Experience:

10 years or more in engineering and operating z/OS based mainframe BISs 5 years or more integrating Software AG Natural/CICS applications into z/OS environments.

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

Management Framework implementations.

Experience in concept exploration, requirements definition, analysis, process design, systems design, integration testing and evaluation within complex environments.

Experienced in development of operational and system level architecture views.

• Senior Mainframe Application Engineer – The Senior Mainframe Application Engineer is responsible for analyzing, planning, designing, and documenting changes to mainframe software applications written in Software AG Natural and ADABASE 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 developers 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 accounting, budgeting, and reporting 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.

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 Sections 2.2, 2.3.2, and 2.3.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)

GFI will not be provided under this Task Order.

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 one (1) trip averaging four (4) days per trip will be required to Indianapolis, IN and that one (1) trip 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.