20_Solicitation - Attachment 9C - TPIMS Transformation Roadmap.xlsx
XLSX spreadsheet 81 KB Posted
- Attached to
- Transformational Pension Insurance Modeling System (T-PIMS) Federal contract opportunity
- Solicitation number
- 16PBGC21R0010
- Issued by
- Pension Benefit Guaranty Corporation
About this file
This document outlines the requirements for the Transformational Pension Insurance Modeling System (T-PIMS) federal contract opportunity. The Pension Benefit Guaranty Corporation is seeking to establish a 10-year Indefinite Delivery Indefinite Quantity contract with task orders to cover the full life cycle of modernization, enhancement, operations and maintenance, and actuarial support services for T-PIMS. The first task order requires modernization of a new T-PIMS with a focus on single-employer plans and delivery within 27 months, and will be competed concurrently with the IDIQ contract. T-PIMS must be built according to PBGC's cloud-hosted blueprint and require a combination of actuarial, economic, and IT expertise to build and sustain over the contract duration. The target is for a faster T-PIMS model running more simulations with a larger data footprint than the current system, and capable of meeting Technical Assistance requests. A single contractor is sought for synergistic systems modernization and ongoing enhancement, operations, and maintenance efforts to increase efficiencies and management effectiveness.
View the file
Other files for this federal contract opportunity
Show all 15
On GovTribe
Work with this file on GovTribe
- Download the original file
- Contacts named in this file
- Similar government files
- Ask GovTribe AI about this file
Text version
T-PIMS Roadmap MVP PRAD 27Mo
| RFP 16PBGC21R0010 |
| ATTACHMENT 9C |
| PIMS Transformation Roadmap |
| PIMS Build Activities | Month 1 | Month 2 | Month 3 | Month 4 | Month 5 | Month 6 | Month 7 | Month 8 | Month 9 | Month 10 | Month 11 | Month 12 | Month 13 | Month 14 | Month 15 | Month 16 | Month 17 | Month 18 | Month 19 | Month 20 | Month 21 | Month 22 | Month 23 | Month 24 | Month 25 | Month 26 | Month 27 | Month 28 | Month 29 | Month 30 |
| Onboarding, Sprint Zero | ||||||||||||||||||||||||||||||
| OIT Transformation Planning (IPT, TRB, Etc.) | ||||||||||||||||||||||||||||||
| Model Governance | ||||||||||||||||||||||||||||||
| Environment Discovery | ||||||||||||||||||||||||||||||
| Validate System Design | ||||||||||||||||||||||||||||||
| Organizational Readiness Planning | ||||||||||||||||||||||||||||||
| Validate ATO and Toolset | ||||||||||||||||||||||||||||||
| Establish Development Cloud Infrastructure | ||||||||||||||||||||||||||||||
| Set up Data Storage (installing configuration) | ||||||||||||||||||||||||||||||
| Set up computational platform | ||||||||||||||||||||||||||||||
| Set up a central code repository | ||||||||||||||||||||||||||||||
| Set up CI/CD Pipeline | ||||||||||||||||||||||||||||||
| Set up User Accounts | ||||||||||||||||||||||||||||||
| Updating Development Cloud Infrastructure | ||||||||||||||||||||||||||||||
| Purchase additional tools as needed | ||||||||||||||||||||||||||||||
| Refine cloud infrastructure | ||||||||||||||||||||||||||||||
| Deliver MVP Sprint 1-n, Go-Live/Post-Production Monitoring & Stabilization | ||||||||||||||||||||||||||||||
| Implement Baseline Security Controls | ||||||||||||||||||||||||||||||
| Comply with Risk/Enterprise Security Framework | ||||||||||||||||||||||||||||||
| Integrating to enterprise LDAP | ||||||||||||||||||||||||||||||
| PIV Authentication | ||||||||||||||||||||||||||||||
| Implement Database | ||||||||||||||||||||||||||||||
| Create Data Model | ||||||||||||||||||||||||||||||
| Populate with Sample Data | ||||||||||||||||||||||||||||||
| Data Migration | ||||||||||||||||||||||||||||||
| Integrate with On-Premises Environment | ||||||||||||||||||||||||||||||
| Integrate with Third-Party to Load Data | ||||||||||||||||||||||||||||||
| Create Synthetic Data | ||||||||||||||||||||||||||||||
| Load Synthetic Data | ||||||||||||||||||||||||||||||
| Testing | ||||||||||||||||||||||||||||||
| Infrastructure/Environment Integration Testing | ||||||||||||||||||||||||||||||
| Create PV Model | ||||||||||||||||||||||||||||||
| Planning (Methodology Planning, Whiteboarding, Pseudo Coding, etc.) | ||||||||||||||||||||||||||||||
| Create Core PV Engine | ||||||||||||||||||||||||||||||
| Implement/Test New Sample Bundling Method | ||||||||||||||||||||||||||||||
| Active | ||||||||||||||||||||||||||||||
| Terminated Vested (TV) | ||||||||||||||||||||||||||||||
| Retiree | ||||||||||||||||||||||||||||||
| Plan Level Calculations | ||||||||||||||||||||||||||||||
| Program Statutory Minimum Funding Calculations | ||||||||||||||||||||||||||||||
| Add (+) Refine Plan Asset Projection Methodology | ||||||||||||||||||||||||||||||
| Add (+) LDI Modeling | ||||||||||||||||||||||||||||||
| Add (+) VRP Risk-Based Premium Capability | ||||||||||||||||||||||||||||||
| Add (+) Binary & Probabilistic BK Model | ||||||||||||||||||||||||||||||
| Add (+) Calibration Improvements for PBGC Trusteed Liability | ||||||||||||||||||||||||||||||
| Add (+) PBGC Asset Projection Methodology | ||||||||||||||||||||||||||||||
| ….Additional Enhancements To Be Determined.... | ||||||||||||||||||||||||||||||
| Bankruptcy Modeling | ||||||||||||||||||||||||||||||
| Planning (Methodology Planning, Whiteboarding, Pseudo Coding, etc.) | ||||||||||||||||||||||||||||||
| Create Credit Rating Transition Model | ||||||||||||||||||||||||||||||
| Create Correlations of Transitions to Econ | ||||||||||||||||||||||||||||||
| Create Time-0 BK model * (dependent on Rating Coverage) | ||||||||||||||||||||||||||||||
| Integration of Econ Scenario Development | ||||||||||||||||||||||||||||||
| Planning (Methodology Planning, Whiteboarding, Pseudo Coding, etc.) | ||||||||||||||||||||||||||||||
| Import 3rd Party Econ Curves * (dependent on 3rd party or in-house) | ||||||||||||||||||||||||||||||
| Build economic data API | ||||||||||||||||||||||||||||||
| New capital markets model * (dependent on 3rd party or in-house) | ||||||||||||||||||||||||||||||
| Build VARs/chain equation * (dependent on 3rd party or in-house) | ||||||||||||||||||||||||||||||
| Full yield curve * (dependent on 3rd party or in-house) | ||||||||||||||||||||||||||||||
| Sample Development | ||||||||||||||||||||||||||||||
| Identify stand-alone Plans and Sponsors | ||||||||||||||||||||||||||||||
| Develop Bundled Plan Logic | ||||||||||||||||||||||||||||||
| Data Edits and Quality Metrics | ||||||||||||||||||||||||||||||
| Solutioning KPIs | ||||||||||||||||||||||||||||||
| Define Operational KPIs | ||||||||||||||||||||||||||||||
| Validate Business Rules and Operational KPIs | ||||||||||||||||||||||||||||||
| Solutioning Modeling Outputs | ||||||||||||||||||||||||||||||
| Cumulative Rates | ||||||||||||||||||||||||||||||
| Identify Model Output for Exhibits | ||||||||||||||||||||||||||||||
| Configure Actuarial Calculation Exhibits | ||||||||||||||||||||||||||||||
| Incorporate 5500 Data Comparison | ||||||||||||||||||||||||||||||
| Develop/Test Drill Down Review Capability | ||||||||||||||||||||||||||||||
| Additional Outputs | ||||||||||||||||||||||||||||||
| Front-End Interface Development | ||||||||||||||||||||||||||||||
| Design Wireframes | ||||||||||||||||||||||||||||||
| Develop User Interface | ||||||||||||||||||||||||||||||
| Validating User Interface | ||||||||||||||||||||||||||||||
| Output Visualization Development | ||||||||||||||||||||||||||||||
| Create Projections Report Dashboard | ||||||||||||||||||||||||||||||
| Create dashboard view of Geographic Heat Map | ||||||||||||||||||||||||||||||
| Create core actuarial results exhibits | ||||||||||||||||||||||||||||||
| Create custom report capabilities | ||||||||||||||||||||||||||||||
| Showcase Modeling and Operational KPIs | ||||||||||||||||||||||||||||||
| Logging | ||||||||||||||||||||||||||||||
| Log intermediate calculations | ||||||||||||||||||||||||||||||
| Log Operational KPIs | ||||||||||||||||||||||||||||||
| Support Establishment of Production Cloud Environment | ||||||||||||||||||||||||||||||
| Support Production Environment Provisioning | ||||||||||||||||||||||||||||||
| Migrate Data into Production Environment | ||||||||||||||||||||||||||||||
| Testing | ||||||||||||||||||||||||||||||
| Model Governance Validation | ||||||||||||||||||||||||||||||
| System Testing | ||||||||||||||||||||||||||||||
| User Acceptance Testing | ||||||||||||||||||||||||||||||
| Stress Testing | ||||||||||||||||||||||||||||||
| Parallel Testing | ||||||||||||||||||||||||||||||
| Documentation | ||||||||||||||||||||||||||||||
| Model Documentation | ||||||||||||||||||||||||||||||
| System Documentation | ||||||||||||||||||||||||||||||
| Training | ||||||||||||||||||||||||||||||
| Actuarial Team Python Training | ||||||||||||||||||||||||||||||
| TPIMS System Training | ||||||||||||||||||||||||||||||
| Transition to O&M | ||||||||||||||||||||||||||||||
| Post Production Monitoring and Stablization | ||||||||||||||||||||||||||||||
| R&D Containers |
Activity Dictionary
PIMS Transformation Activity Dictionary
ID Task Description Dependencies
| 1 | Transformation Planning (OR Planning, Model Governance, etc.) | - Identify and resolve pre-deployment cross-program, people, process, and technology gaps related to the transformed PIMS functionality to be deployed | |||
| - Establish a model governance, controls, and testing policy that will guide the calibration, back testing, review, and implementation of new models in the transformed PIMS | N/A | ||||
| 2 | Establish Development Cloud Infrastructure | Establish the Microsoft Azure Cloud Infrastructure for the Transformed PIMS to be developed | N/A | ||
| 2.1 | Set up Data Storage (installing configuration) | Install and configure the NoSQL database in Azure for the PIMS data to be stored | |||
| 2.2 | Set up Computational Platform | Install and configure the distributed computing platform for the Transformed PIMS in Azure | |||
| 2.3 | Set up a Central Code Repository | Set up a central code repository in Azure for users and developers to collaborate in one place | |||
| 2.4 | Set up CI/CD Pipeline | Set up a Continuous Integration (CI) and Continuous Delivery (CD) pipeline to enable developers to deliver code changes more frequently and reliably | |||
| 2.5 | Set up User Accounts | Assign roles to PIMS users in the Azure Active Directory | |||
| 3 | Implement Baseline Security Controls | 2 - Establish Development Cloud Infrastructure | |||
| 3.1 | Comply with Risk/Enterprise Security Framework | Implement security controls that aligns with PBGC's risk/enterprise security framework | |||
| 3.2 | Integrating to Enterprise LDAP | Enable the ability for PIMS users to authenticate using their existing PBGC user accounts | |||
| 4 | Implement Database | Implementing Database activity includes creating schema and fields for database | |||
| 4.1 | Create Data Model | Design the schema of PIMS data that makes necessary data elements needed for the model available | |||
| 4.1 | Populate with Sample Data | Load database with synthetic data to validate design | |||
| 5 | Data Migration | ||||
| 5.1 | Integrate with On-Premises Environment | Enable the ability of PBGC's on-premises systems to communicate with the newly established Azure development environment | |||
| 5.2 | Integrate with Third-Party to Load Data | Enable the ability for data from third-party vendors to be loaded into the newly established Azure development environment | |||
| 5.3 | Create Synthetic Data | Create a repository of programmatically generated data that is similar to production data for the purposes of development | |||
| 5.4 | Load Synthetic Data | Ingest synthetic data within development environment for use during model development | |||
| 6 | Testing | ||||
| 6.1 | Infrastructure/Environment Integration Testing | Validate the development environment's ability to communicate with PBGC's on-premises systems | |||
| 7 | Create PV Model | N/A for Model Planning Stages | |||
| 7.1 | Planning | Methodology planning, process whiteboarding, pseudo coding, and other pre-model development activities | |||
| 7.2 | Create Core PV Engine | Develop coding and calculation structure to calculate actuarial liability, project assets and contributions, and implement bankruptcy model outcomes to determine PBGC termination liability. Core Model Build Includes Pseudocode, Development, and Unit Testing | Model Development Stages: |
●5 - Data Migration ●7.1 - Planning
| 7.3 | Implement/Test New Sample Bundling Method | Evaluate sample of bundled plan calculations to validate valuation coding. | |
| 7.4 | Active | Develop liability calculation engine for active participants. | |
| 7.5 | Terminated Vested (TV) | Develop liability calculation engine for terminated vested participants. | |
| 7.6 | Retiree | Develop liability calculation engine for in-pay participants. | |
| 7.7 | Plan Level Calculations | ||
| 7.7.1 | Program Statutory Minimum Funding Calculations | Develop model coding to calculate shortfall and waiver amortization amounts, smoothed assets, minimum required contributions, and PBGC premiums. | |
| 7.7.2 | Add (+) Refine Plan Asset Projection Methodology | Develop model coding to project assets using plan-specific asset allocation information from Schedule R. | |
| 7.7.3 | Add (+) LDI Modeling | Develop model coding to reflect implicit plan-specific LDI strategies, as well as determine standard plan termination probability. | |
| 7.7.4 | Add (+) VRP Risk-Based Premium Capability | Develop adaptable coding structure that builds in parameterization capability for PBGC premium calculation, to allow for risk-based premium adjustments based on a range of inputs (current asset allocations, LDI position, etc.) | |
| 7.7.5 | Add (+) Binary & Probabilistic BK Model | Develop model coding structure and parameterization to accommodate dual binary and probabilistic bankruptcy methodologies, based on plan type and/or modeling scenario. | |
| 7.7.6 | Add (+) Calibration Improvements for PBGC Trusteed Liability | Implement streamlined calibration process for PBGC trusteed plan liability, using output from ASD's IPVFB system. | |
| 7.7.7 | Add (+) PBGC Asset Projection Methodology | Develop model coding and parameterization to project PBGC assets based on a range of possible investment strategies. | |
| 7.8 | ….Additional Enhancements To Be Determined.... | Development of supplementary calculations which may be identified as part of the implementation | |
| 8 | Bankruptcy Modeling | N/A for Model Planning Stages | |
| 8.1 | Planning | Methodology planning, process whiteboarding, pseudo coding, and other pre-model development activities | |
| 8.2 | Create Credit Rating Transition Model | Utilizing firm financial data and credit rating history, develop a credit rating transition rating matrix to forecast bankruptcy probabilities | Model Development Stages: |
●5 - Data Migration ●8.1 - Planning
| 8.3 | Create Correlations of Transitions to Econ | Create transition rating sensitivities to economic indicators in order to stress bankruptcy probabilities over the 10,000 paths | |
| 8.4 | Create Time-0 BK model * (dependent on Rating Coverage) | For sponsors without a risk rating, develop a methodology to assign a time-0 starting risk rating | |
| 9 | Integration of Econ Scenario Development | N/A for Model Planning Stages | |
| 9.1 | Planning | Methodology planning, process whiteboarding, pseudo coding, and other pre-model development activities | |
| 9.2 | Import 3rd Party Econ Curves * (dependent on 3rd party or in-house) | Develop processes to ingest 3rd party economic scenarios into the PIMS data universe and incorporate them as inputs into the process | Model Development Stages: |
●5 - Data Migration ●9.1 - Planning
| 9.3 | Build economic data API | Enable the ability for data from third-party economic simulation vendors to be loaded into the newly established Azure development environment through Moody's API calls | |
| 9.4 | New capital markets model * (dependent on 3rd party or in-house) | Develop in-house asset and equity return model | |
| 9.5 | Build VARs/chain equation * (dependent on 3rd party or in-house) | Develop in-house economic scenario generator to produce 10,000 stochastic paths for a stochastic SE PIMS run | |
| 9.6 | Full yield curve * (dependent on 3rd party or in-house) | Stochastically model the full Treasury yield curve - dependent on potential 3rd party data provider | |
| 10 | Sample Development | New Sampling Building Method assumes access to data as well as time for stakeholder reviewer | 5 - Data Migration |
| 10.1 | Identify stand-alone Plans and Sponsors | Work with PRAD to identify which plans to model individually | |
| 10.2 | Develop Bundled Plan Logic | Identify applicable bundle groupings to capture sufficient level of granularity for PIMS modeling. Determine how to effectively compile bundled data components using available electronic and/or OCR-accessible data. | |
| 10.3 | Data Edits and Quality Metrics | Develop set of business rules to measure data quality and perform standard data edits | |
| 11 | Solutioning KPIs | 7.2 - Create Core PV Engine | |
| 11.1 | Define Operational KPIs | Design the performance indicators that will be used to determine the state of TPIMS operations | |
| 11.2 | Validate Business Rules and Operational KPIs | Gain stakeholder approval of defined business rules and operational KPIs | |
| 12 | Solutioning Modeling Outputs | ●7.2 - Create Core PV Engine |
●8 - Bankruptcy Model ●9 - Integration of Econ Scenario Development
| 12.1 | Cumulative Rates | Design scripts to calculate cumulative bankruptcy and claim rates from scenario outputs, as well as other KPIs necessary for reporting | |
| 12.2 | Identify Model Output for Exhibits | Map model outputs to existing results exhibits in the Projections Report and design scripts to format output data to be more effectively utilized by reporting software to create these exhibits | |
| 12.3 | Configure Actuarial Calculation Exhibits | Develop plan-level actuarial calculation exhibits, showing detail of liability development, asset projections, and funding calculations. | |
| 12.4 | Incorporate 5500 Data Comparison | Determine how to effectively compare back against original Form 5500 actuarial results, for validation of model results. | |
| 12.5 | Develop/Test Drill Down Review Capability | Develop multiple levels of actuarial results exhibits to facilitate drill-down review capability. | |
| 12.6 | Additional Outputs | Development of supplementary outputs which may be identified as part of the implementation | |
| 13 | Front-End Interface Development | 10 - Solutioning KPIs | |
| 13.1 | Design Wireframes | Develop visual guides that represents the skeletal framework of the transformed PIMS system | |
| 13.2 | Develop User Interface | Develop method in which PIMS users will interact with the transformed PIMS Model to perform analysis | |
| 13.3 | Validating User Interface | Gain stakeholder approval of the proposed user interface to confirm that it meets system requirements. | |
| 14 | Output Visualization Development | 13.1 - Design Wireframes | |
| 14.1 | Create Projections Report Dashboard | Design an executive-level graphical user interface that displays various projection metrics performed by the Transformed PIMS | |
| 14.2 | Create dashboard view of Geographic Heat Map | Design a geographic heatmap with the ability to observe and drill-down on state-specific exposures | |
| 14.3 | Create core actuarial results exhibits | Design visualizations that capture core outputs, including those in the Projections Reports and key charts/metrics in TA and OMB requests | |
| 14.4 | Create custom report capabilities | Design the data summaries that will be produced for various stakeholders to provide a detailed review of the Transformed PIMS analysis | |
| 14.5 | Showcase Modeling and Operational KPIs | Gain stakeholder approval on modeling and operational KPIs that will be used to provide insight into the modeling and operational status of the transformed PIMS system | |
| 15 | Logging | ||
| 15.1 | Log intermediate calculations | Create records of math functions within a formula that is carried forward into another calculation | 7.2 - Create Core PV Engine |
| 15.2 | Log Operational KPIs | Create records for environmental events that provides insight into the state of operations of the PIMS model | 2 - Establish Development Cloud Infrastructure |
| 16 | Support Establishment of Production Cloud Environment | 2 - Establish Development Cloud Infrastructure | |
| 16.1 | Support Production Environment Provisioning | Provide necessary input and information about the transformed PIMS specification to the IT Team responsible for provisioning the production instance for the PIMS model. | |
| 16.2 | Migrate Data into Production Environment | Load live data into the production instance of the PIMS model | |
| 17 | Testing | N/A | |
| 17.1 | Governance Validation | Perform model testing/validation steps to confirm that model components that have been developed performed as expected. | |
| 17.2 | System Testing | Conduct System Testing on the integrated, transformed PIMS to evaluate the end-to-end system compliance with the specified requirements | |
| 17.3 | User Acceptance Testing | Verify the transformed PIMS through end users to validate the end to end business flow with real-world scenarios | |
| 17.4 | Stress Testing | Test that the system can manage the load it receives | |
| 17.5 | Parallel Testing | Test the Transformed PIMS against the current PIMS to validate results and identify differences between the two systems | |
| 18 | Training | ||
| 18.1 | Actuarial Team Python Training | Train actuarial modelers in TPIMS's programming language | N/A |
| 18.2 | TPIMS System Training | Train users on TPIMS operations, functionality, and interfaces | 7 - Create PV Model |
14 - Output Visualization Development
| 19 | Documentation | ||
| 19.1 | Model Documentation | Methodology whitepapers and formal documentation of modeling components | ●7 - Create PV Model |
●8 - Bankruptcy Model ●9 - Integration of Econ Scenario Development
19.2 System Documentation System architecture and supporting infrastructure documentation ●2 - Establish Development Cloud Infrastructure ●5 - Data Migration ●19 - Support Establishment of Production Cloud Environment 20 R&D Containers Implement Application Containers (separate from development environment) ●7 - Create PV Model ●8 - Bankruptcy Model ●9 - Integration of Econ Scenario Development
Minimum Viable Product
PIMS Transformation Minimum Viable Product
| Transformed PIMS (TPIMS) MVP | Subsequent Enhancements | |||||
| Activity | Description | Activity | Description | |||
| Development Environment for TPIMS | ||||||
| (including PIV authentication) | Establish Azure Cloud Infrastructure with appropriate security controls for TPIMS to be developed | Option Pricing Bankruptcy Model | Implementation of bankruptcy model using option pricing theory | |||
| PV Model | Develop core calculation engine to determine PBGC termination liability and exposure | Stochastic Mortality | Develop model to stochastically project mortality rates | |||
| New Bankruptcy Model | Transformed model forecasting future institutional default | Partnering Cash Flow Model | Create parallel calculation engine driven by plan-level liability cash flows | |||
| Integration of Economic Scenario Development | Stochastically forecast 10,000 economic simulations | Enhanced Security Features | Implement encryption and Role-based access control features | |||
| Full Yield Curve | Creation of model to forecast full Treasury yield curve | Advanced Storage Features | Develop data archiving and backup procedures and timelines | |||
| New Sample and Bundle Development | Identify and bundle groups of plans to capture sufficient level of granularity for TPIMS modeling | |||||
| Key Performance Indicators | Determine performance indicators that will determine state of TPIMS operations | |||||
| Modeling Outputs | Determine how TPIMS analysis will be delivered to users | |||||
| Enhanced Logging | Establish traceability between TPIMS component outputs and the data provided | |||||
| Graphical User Interface for User Interaction | Create user friendly interaction mechanism for TPIMS results | |||||
| Cloud Production Environment for Transformed PIMS | Establish Azure Cloud Infrastructure for Production TPIMS to operate within | |||||
| R&D Containerization | Create independent R&D environments for testing for TA requests as needed (separate from development environment) |
File details come from the government source that posted it. Updated .