Attachment 2 - Legacy PIMS Task Map and Labor Projections.pdf

O&M: ME-PIMS

O&M and

Decommission:

SE-PIMS

Projections Report Modeling:

ME-PIMS

Projections Report Modeling:

SE-PIMS

Technical Assistance:

ME & SE

Special Project:

ME & SE

3.1 Actuarial Services, Actuarial Expertise, Actuarial Studies and PIMS Related Projects

3.1 (1)

Annual actuarial evaluations of PBGC's expected operations and financial status required under Section 4008 of ERISA. This includes all PIMS related modeling support required to develop PBGC’s annual Projections Report, as well as performing the “transcription process” to document all numbers published in the Projections Report to the underlying source (including but not limited to PIMS output).

x x

3.1 (2) Analyses of legislative, regulatory, and/or policy proposals to determine the impact on PBGC's financial position, projected PBGC cash flows, and/or the impact to the universe of plans insured by PBGC. This includes all PIMS-related modeling support. x

3.1.(3) Other ad hoc analysis to support PRAD research projects, analysis of PRAD assumptions, or other special projects as requested by PBGC management. This may include PIMS-related modeling support or other ad hoc analytical analysis x

3.1.(4) Scope statements for system change requirements to support the production of the annual Projections Report. x x

3.2 Operation and Maintenance (O&M) to the Legacy PIMS Models

3.2 (1) Contact users and provide technical support to ensure issues are resolved timely. Effectively communicate with the users to provide the status of the open issues x x

3.2 (2)

Conduct analysis of problems reported by users and recommend functional and/or technical improvements, including the addition of business and technical features to existing software. Provide alternative solutions to improve the related processes and assist in exploring possibilities of using new features, functions, and modules x x

3.2 (3) Participate in root cause analysis in order to resolve production and user support issues effectively x x

3.2 (4)

Effectively respond to questions about the system outages and errors. Resolve technical issues with Information Technology Infrastructure Operations Department (ITIOD), production SQL Database Administrators (DBAs), network support, other PBGC teams, and other systems.

x

3.2 (5) Provide support to ITIOD to resolve application production issues x

3.2 (6) Support system administration duties as needed x

3.2 (7) Support application and system audits from external and internal auditors x

3.2 (8) Participate in corporate-wide IT initiatives such as System Security Plan (SSP) updates and assist with PIMS System Assessment and Accreditation (SA&A) process leading to the attainment of an Authority to Operate for ME PIMS and SE PIMS x

3.2 (9) Provide technical support to PBGC as needed. Examples include, but are not limited to, testing and migration of applications to future versions of software, database and operating systems on servers x

3.2 (10) Retire applications. The Contractor may propose processes, and methods for retiring and archiving applications, as long as they do not conflict with the current PBGC guidelines for decommissioning systems and are approved by the COR and ITIOD x

3.2 (11) Plan and participate in Disaster Recovery (DR) testing for the PIMS applications; develop DR testing scenarios; work with users and DR team to execute DR tests and document results if requested x

3.2 (12) Support activities for transitioning applications from/to other teams x

3.2 (13) Support other PBGC teams responding to questions related to PIMS and/or related applications x x

3.2 (14) Provide other production support as needed, such as troubleshooting, debugging, identifying problems/errors, making corrections and improving efficiencies of PIMS and implementing changes in laws, policies and regulations as they occur x x

3.2 (15) Ensure compliance with the PBGC infrastructure changes and ITIOD roadmap and infrastructure requirements x

3.2 (16) Support the IT and Business Program Managers in conducting the annual operational analysis x

3.2 (17)

Decommissioning: Upon request of the COR, the contractor shall take all steps required to decommission the system and/or components. This includes archiving code and documentation, coordinating removal/uninstall of code and components from all IT environments and ensuring data back-up and archiving as well as working with PIMS Transformation Contractor related to any data migration for the transition to the new PIMS system x

3.2 (18)

18) Support for:

I. Giving ongoing expert advice in the operations and capabilities to users on all areas of the PIMS and related systems II. Maintaining a "problem log" of reported PIMS problems. The "problem log" is an up-to-date list of PIMS system problems which have been reported to the Contractor either by application users or by the Contractor's own personnel.

III. Determining the scope and level of effort of proposed modification or corrections to the existing PIMS system.

IV. Making corrections to the PIMS system as requested and approved by the Subject Matter Expert (SME) and the COR according to an agreed upon schedule.

V. Providing corrections to documentation according to an agreed upon schedule.

VI. Providing subject matter expertise in the current workings of PIMS and current PIMS technology to IT groups and PIMS Transformation team including working with PIMS transformation contractor.

x x

3.3 System Modification to Legacy PIMS

3.3 (1)

Perform and complete project initiation, planning, research, analysis, design, development, and testing and implement any approved system modification and requirements to the existing application in compliance with the IT processes including Information Security Risk Management Framework and Information Technology Solutions Life Cycle Management (ITSLCM) Framework x x x x

3.3 (2) Schedule and coordinate the releases with the integrated project/program team and deliver the releases on time x x x

3.3 (3) Deploy high quality software releases in production and minimize downtime in production due to quality issues x x x

3.3 (4) Leading the effort to analyze, prioritize and conduct meetings to determine system modifications x x x x

3.3 (5) Ensure the design is interoperable with other integrated systems and meets Enterprise Architecture (EA) guidelines and other PBGC standards x x x

3.3 (6) Coordinate extensively with all stakeholders such as OIT, PRAD, Security and Privacy teams, and other applicable divisions and systems within PBGC and the Federal Government x x x

3.3 (7)

Deploy all software system modifications through releases according to established PBGC Software Configuration Management Procedures and Change and Release Management Policy, Processes and Procedures and PBGC security policies to ensure the agency standards are accurately captured and incorporated into the releases x x x

3.3 (8)

Conduct appropriate system level tests (e.g., unit testing, parallel testing, regression testing, integration testing, performance testing, load testing, functionality testing) to modify the quality of software releases. The Contractor may use automated testing tools x x x x

3.3 (9)

Support and assist application users in User Acceptance Testing (UAT) of the application, including, but not limited to, (1) the preparation of test plans, test cases/scripts and test results, (2) the use of automated testing tools, and (3) the development and maintenance of operation system documentation and procedures x x x x

3.3 (10) Effectively coordinate the notification of the deployment of releases to users, stakeholders, Service Desk, COR, and other impacted parties in a timely manner to provide impacted parties time to prepare for the release x x x x

3.3 (11) Providing system modifications that include the design, programming, testing and implementation of major upgrades or significant new modeling capabilities based on user requirements developed by PRAD x x x x

3.3 (12) Propose system modifications and corrections for both Models x x x x

3.3 (13) Implement system modifications or corrections to both Models as approved by PRAD management and in accordance with an agreed upon implementation schedule x x x x

3.3 (14) Produce a System Change Request (SCR) document x x x x

3.3 (15) Provide on-call support as needed during periods of Technical Assistance requests x

3.4 Project Management - Planning, Scheduling, Tracking, Managing, Reporting

3.4 (1)

Conduct scope management to ensure project scope is baselined and changes to scope are managed through the project lifecycle.

This includes the initial and preliminary “Scope Statements” to include requirements for system and model changes to support annual Projections Reports. Establish and follow procedures for release management and change control, including an impact assessment.

x x x x x x

3.4 (2)

Follow the Change Management Process outlined in Attachment 3 – “Team Workflow and Separation of Duties Chart”. This process and any changes required to be implemented during the performance period shall be implemented by the contractor at the discretion of the agency.

x x x

3.4 (3) Conduct schedule management to include establishing a resource-loaded and baselined schedule in PBGC’s approved project management system (currently Microsoft Project Online, a.k.a. P3M) x x x x x x

3.4 (4)

Develop project schedules and project baselines for identified projects to include releases or any activity where resources are deployed to make changes to or support applications in this Task Order. Follow the ITSLCM framework in developing the schedule and ensure the schedule includes the deliverables, milestones, planned durations for each task, project start and end dates, resources, work breakdown structure of activities, and other specific information needed to track the projects. The Contractor will work with the subject matter experts and other stakeholders in eliciting requirements.

x x x x x x

3.4 (5) Maintain relationships and partnerships with all integrated system leadership for systems both internal and external to the project IT applications/systems. x x x

3.4 (6) Prepare project status reports as defined by the Federal IT Project Manager along with understanding agency priorities and aligning their team’s actions to meet changing priorities. x x x x x x

3.4.1 Issue and Risk Management

3.4.1 (1) Include risk management strategies, based on PBGC Risk Management Policy, in the Project Management Plan x x x x x x

3.4.1 (2) Identify and track risks that may impact the project and PBGC systems and identify mitigation strategies in BISD’s system of record (currently P3M). x x x x x x

3.4.1 (3) Identify and track issues and work to resolve to ensure system operations and release remain on-schedule x x x x x x

3.4.2 Status Reporting x x x x x x

3.4.3 Integrated Project Team (IPT)

3.4.3 (1) Coordinate and facilitate IPT governance bodies to enable decisions on system changes and to provide a venue for dissemination of system information x

3.4.3 (2) Provide status on system operations and changes x

3.4.4 Meeting Participation

3.4.4 (1) Develop agendas and circulate those agendas ahead of any meetings organized by the contractor x x x x x x

3.4.4 (2) Develop meeting materials when the contractor is presenting x x x x x x

3.4.4 (3) Facilitate meetings that allow for in-person and/or remote participation via teleconference, Skype and/or other remote participation tools x x x x x x

3.4.4 (4) Record and provide minutes of all meetings conducted or attended as part of this contract work and deliver those minutes for participant review and comment x x x x x x

3.4.4 (5) Participate in meetings as required for other PBGC efforts that may impact or be impacted by this contract x x x x x x

3.4.5 System Documentation and Documentation Maintenance

3.4.5 (1)

Develop or update PBGC documentation, including manuals (e.g., operations, system administration, system maintenance, user and training) and plans (e.g. system integration and site implementation). Documentation shall follow the latest approved standards at the time of the execution effort and delivery of the system. The Contractor shall develop documentation and/or update existing IT Solutions Life Cycle Management (ITSLCM) documents that are required as a result. Additional information about the ITSLCM can be found in Attachment 5 – ITSLCM Framework.

x x x x x x

3.4.5 (2)

Comply with PBGC standards and guidelines for all documentation, update all system documents when changes occur in the application or process, and maintain and revise PBGC system and business process documentation in accordance with the processes determined by the agency.

x x x x x x

3.4.6 Transition Support x x x x x x

O&M: ME-

PIMS

O&M and Decommission:

SE-PIMS

Projections Report

Modeling:

ME-PIMS

Projections Report

Modeling:

SE-PIMS

Technical Assistance:

ME & SE*

Special Project:

ME & SE*

Base Year Labor Category Hours Hours Hours Hours Hours Hours Project Manager 75 250 200 200 75 100 Senior Actuary 25 100 900 500 175 200

Senior Analyst/ Software Engineer 100 600 150 50 Analyst/ Programmer 50 100 25 25 Consulting Actuary 25 100 450 250 75 100

Total 125 600 1550 1650 500 475

* Columns showing Technical Assistance and Special Project CLINs show sample hours for a single CLIN (i.e. 3 Technical Assistance requests; 1 Special Project)

The information in the following table represents an estimate of the labor categories and hours of effort the Government believes will be necessary to successfully perform this work. PBGC is providing this information purely to assist interested contractors in preparing their proposals. Contractors should not rely exclusively upon this information, but instead use it as one of multiple considerations in formulating their proposals.

Contractors may deviate from this estimate as deemed appropriate. Ultimately, each contractor bears responsibility for developing its own staffing plan and proposal prices, and furthermore if selected for award, performing the work as defined in the contract at the contract price.

Task Map