| | Exhibit 300 (BY2009) - Centers for Medicare and Medicaid Services CMS, Healthcare Integrated General Ledger Accounting System (HIGLAS)PART ONE
OVERVIEW
- 1. Date of Submission:
- 2008-02-04
- 2. Agency:
- 009
- 3. Bureau:
- 38
- 4. Name of this Capital Asset:
- CMS Healthcare Integrated General Ledger Accounting System (HIGLAS)
- 5. Unique Project Identifier:
- 009-38-01-01-01-1020-00
- 6. What kind of investment will this be in FY2009?
- Mixed Life Cycle
- 7. What was the first budget year this investment was submitted to OMB?
- FY2005
- 8. Provide a brief summary and justification for this investment, including a brief description of how this closes in part or in whole an identified agency performance gap.
- CMS is currently in the process of developing & implementing a single, integrated dual-entry accounting system. This accounting system, the Healthcare Integrated General Ledger Accounting System (HIGLAS), will replace the existing 52 separate accounting/payment systems for Medicare & Medicaid. HIGLAS represents the consolidation of 2 major CMS projects within the office of the CMS Chief Financial Officer. The first project, the Integrated General Ledger and Accounting System (IGLAS) project, was initiated to improve the accounting & financial management processes used by CMS's Medicare contractors to administer the Medicare Parts A & B programs. The second project was an effort to improve the agency's central administrative accounting & financial management processes. These 2 activities were combined into the HIGLAS project. The Federal Financial Management Improvement Act (FFMIA) requires each agency to implement and maintain financial management systems that comply substantially with federal financial management systems requirements, applicable federal accounting standards, and the U.S. Standard General Ledger at the transaction level. HIGLAS supports the U.S. Department of Health & Human Service's FFMIA compliance goals in having total CMS Payment Dollars on HIGLAS. At present, the total amount of CMS dollars accounted for in HIGLAS is at 50.7%. When CMS completes nationwide implementation of HIGLAS in FY 2011, the agency expects to achieve 100% FFMIA compliancy. To date, 9 Medicare Contractors have transitioned to HIGLAS. By the end of FY 2008, there will be a total of 14 Medicare Contractor sites using HIGLAS. In FY 2009, 7 additional sites will transition to HIGLAS. In October 2007, HIGLAS implemented administrative program accounting for federal Medicaid and State Children's Health Insurance Program (SCHIP) State grant payments. HIGLAS helps retain the CMS "clean opinion" on the federally mandated audit of CMS financial statements, as set forth under the Chief Financial Officer Act. Moreover, HIGLAS allows CMS to address the material weaknesses as identified by the 1998 DHHS-Office of the Inspector General financial statement audit of CMS. If HIGLAS is not fully funded then the transition schedule could be delayed, which in turn could have significant impact on meeting our FFMIA goal. In addition, lack of funding could have a negative impact on the Agency's clean opinion on the CFO Audit.
- 9. Did the Agency's Executive/Investment Committee approve this request?
- yes
- 9.a. If "yes," what was the date of this approval?
- 2007-06-26
- 10. Did the Project Manager review this Exhibit?
- yes
- 11.a. What is the current FAC-P/PM certification level of the project/program manager?
- TBD
- 12. Has the agency developed and/or promoted cost effective, energy-efficient and environmentally sustainable techniques or practices for this project.
- no
- 12.a. Will this investment include electronic assets (including computers)?
- yes
- 12.b. Is this investment for new construction or major retrofit of a Federal building or facility? (answer applicable to non-IT assets only)
- no
- 13. Does this investment directly support one of the PMA initiatives?
- yes
- If yes, select the initiatives that apply:
Initiative Name |
---|
Budget Performance Integration | Expanded E-Government | Financial Performance | Human Capital |
- 13.a. Briefly and specifically describe for each selected how this asset directly supports the identified initiative(s)? (e.g. If E-Gov is selected, is it an approved shared service provider or the managing partner?)
- HIGLAS supports Improved Financial Performance since it integrates all financial and administrative systems, thereby enabling cost accounting capabilities. HIGLAS supports Expanded Electronic Government, since it will eliminate 52 redundant and duplicative IT systems. It is a web-based system that automates internal processes to improve the federal governments' use of IT. HIGLAS also indirectly supports Human Capital and Budget Performance Integration initiatives.
- 14. Does this investment support a program assessed using the Program Assessment Rating Tool (PART)?
- yes
- 14.a. If yes, does this investment address a weakness found during the PART review?
- yes
- 14.b. If yes, what is the name of the PARTed program?
- 2003: CMS - Medicare Program
- 14.c. If yes, what rating did the PART receive?
- Moderately Effective
- 15. Is this investment for information technology?
- yes
- 16. What is the level of the IT Project (per CIO Council's PM Guidance)?
- Level 3
- 17. What project management qualifications does the Project Manager have? (per CIO Council's PM Guidance)
- (1) Project manager has been validated as qualified for this investment
- 18. Is this investment identified as high risk on the Q4 - FY 2007 agency high risk report (per OMB memorandum M-05-23)?
- yes
- 19. Is this a financial management system?
- yes
- 19.a. If yes, does this investment address a FFMIA compliance area?
- yes
- 19.a.1. If yes, which compliance area:
- Section 803 (a): Financial Management Systems, Federal accounting standards, and the U.S. Government Standard General Ledger at the transaction level.
- 19.b. If yes, please identify the system name(s) and system acronym(s) as reported in the most recent financial systems inventory update required by Circular A11 section 52.
- HIGLAS - CMS Healthcare Integrated General Ledger Accounting System
- 20. What is the percentage breakout for the total FY2009 funding request for the following? (This should total 100%)
Area | Percentage |
---|
Hardware | 11 | Software | 2 | Services | 78 | Other | 9 |
- 21. If this project produces information dissemination products for the public, are these products published to the Internet in conformance with OMB Memorandum 05-04 and included in your agency inventory, schedules and priorities?
- n/a
- 22. Contact information of individual responsible for privacy related questions.
Name | Maribel Franey | Phone Number | (410) 786-0757 | Title | Director, Privacy Compliance | Email | Maribel.Franey@cms.hhs.gov |
- 23. Are the records produced by this investment appropriately scheduled with the National Archives and Records Administration's approval?
- yes
- 24. Does this investment directly support one of the GAO High Risk Areas?
- yes
SUMMARY OF SPEND
- 1. Provide the total estimated life-cycle cost for this investment by completing the following table. All amounts represent budget authority in millions, and are rounded to three decimal places. Federal personnel costs should be included only in the row designated Government FTE Cost, and should be excluded from the amounts shown for Planning, Full Acquisition, and Operation/Maintenance. The total estimated annual cost of the investment is the sum of costs for Planning, Full Acquisition, and Operation/Maintenance. For Federal buildings and facilities, life-cycle costs should include long term energy, environmental, decommissioning, and/or restoration costs. The costs associated with the entire life-cycle of the investment should be included in this report.
All amounts represent Budget Authority
Note: For the cross-agency investments, this table should include all funding (both managing partner and partner agencies).
Government FTE Costs should not be included as part of the TOTAL represented. Cost Type | Py-1 & Earlier -2006 | PY 2007 | CY 2008 | BY 2009 |
---|
Planning Budgetary Resources | 18.390 | 0.000 | 0.000 | 0.000 | Acquisition Budgetary Resources | 316.240 | 42.292 | 34.869 | 35.681 | Maintenance Budgetary Resources | 67.055 | 79.024 | 110.287 | 127.313 | Government FTE Cost | 31.888 | 5.164 | 5.666 | 5.950 | # of FTEs | 167 | 44 | 44 | 44 |
- 2. Will this project require the agency to hire additional FTE's?
- no
- 3. If the summary of spending has changed from the FY2008 President's budget request, briefly explain those changes.
PERFORMANCE In order to successfully address this area of the exhibit 300, performance goals must be provided for the agency and be linked to the annual performance plan. The investment must discuss the agency's mission and strategic goals, and performance measures (indicators) must be provided. These goals need to map to the gap in the agency's strategic goals and objectives this investment is designed to fill. They are the internal and external performance benefits this investment is expected to deliver to the agency (e.g., improve efficiency by 60 percent, increase citizen participation by 300 percent a year to achieve an overall citizen participation rate of 75 percent by FY 2xxx, etc.). The goals must be clearly measurable investment outcomes, and if applicable, investment outputs. They do not include the completion date of the module, milestones, or investment, or general goals, such as, significant, better, improved that do not have a quantitative measure.- Agencies must use the following table to report performance goals and measures for the major investment and use the Federal Enterprise Architecture (FEA) Performance Reference Model (PRM). Map all Measurement Indicators to the corresponding Measurement Area and Measurement Grouping identified in the PRM. There should be at least one Measurement Indicator for each of the four different Measurement Areas (for each fiscal year). The PRM is available at www.egov.gov. The table can be extended to include performance measures for years beyond FY 2009.
Row | Fiscal Year | Strategic Goal Supported | Measurement Area | Measurement Grouping | Measurement Indicator | Baseline | Planned Improvement to the Baseline | Actual Results |
---|
1 | 2005 | Effective Management of Human Capital/Information Technology/Resources | Mission and Business Results | Reporting and Information | Number of material weaknesses cited in the financial audit | 3 | 0 | 1 | 2 | 2005 | Effective Management of Human Capital/Information Technology/Resources | Customer Results | Service Efficiency | Number of contractors that can produce standing reports and queries on demand, resulting in cost and time savings. | 2 | 4 | 4 | 3 | 2005 | Effective Management of Human Capital/Information Technology/Resources | Processes and Activities | Compliance | Support the U.S. Department of Health & Human Service's Federal Financial Management Improvement Act (FFMIA) compliance goal in having total CMS Payment Dollars on HIGLAS | 7.4% | 7.4% | 7.4% | 4 | 2005 | Effective Management of Human Capital/Information Technology/Resources | Technology | Availability | The number of Medicare contractors transitioned to HIGLAS, a certified general ledger accounting system. | 2 | 4 | 4 | 5 | 2006 | Effective Management of Human Capital/Information Technology/Resources | Mission and Business Results | Reporting and Information | Number of material weaknesses cited in the financial audit | 1 | 0 | 1 | 6 | 2006 | Effective Management of Human Capital/Information Technology/Resources | Customer Results | Service Efficiency | Number of contractors that can produce standing reports and queries on demand, resulting in cost and time savings. | 4 | 7 | 7 | 7 | 2006 | Effective Management of Human Capital/Information Technology/Resources | Processes and Activities | Compliance | Support the U.S. Department of Health & Human Service's Federal Financial Management Improvement Act (FFMIA) compliance goal in having total CMS Payment Dollars on HIGLAS | 7.4% | 47.7% | 49.4% | 8 | 2006 | Effective Management of Human Capital/Information Technology/Resources | Technology | Availability | The number of Medicare contractors transitioned to HIGLAS, a certified general ledger accounting system. | 4 | 7 | 7 | 9 | 2007 | Effective Management of Human Capital/Information Technology/Resources | Mission and Business Results | Reporting and Information | Number of material weaknesses cited in the financial audit | 1 | 0 | TBD | 10 | 2007 | Effective Management of Human Capital/Information Technology/Resources | Customer Results | Service Efficiency | Number of contractors that can produce standing reports and queries on demand, resulting in cost and time savings. | 7 | 10 | TBD | 11 | 2007 | Effective Management of Human Capital/Information Technology/Resources | Processes and Activities | Compliance | Support the U.S. Department of Health & Human Service's Federal Financial Management Improvement Act (FFMIA) compliance goal in having total CMS Payment Dollars on HIGLAS | 49.4% | 49.4% | TBD | 12 | 2007 | Effective Management of Human Capital/Information Technology/Resources | Technology | Availability | The number of Medicare contractors transitioned to HIGLAS, a certified general ledger accounting system. | 7 | 10 | TBD | 13 | 2008 | Effective Management of Human Capital/Information Technology/Resources | Mission and Business Results | Reporting and Information | Number of material weaknesses cited in the financial audit | 1 | 0 | TBD | 14 | 2008 | Effective Management of Human Capital/Information Technology/Resources | Customer Results | Service Efficiency | Number of contractors that can produce standing reports and queries on demand, resulting in cost and time savings. | 10 | 14 | TBD | 15 | 2008 | Effective Management of Human Capital/Information Technology/Resources | Processes and Activities | Compliance | Support the U.S. Department of Health & Human Service's Federal Financial Management Improvement Act (FFMIA) compliance goal in having total CMS Payment Dollars on HIGLAS | 49.4% | 62.2% | TBD | 16 | 2008 | Effective Management of Human Capital/Information Technology/Resources | Technology | Availability | The number of Medicare contractors transitioned to HIGLAS, a certified general ledger accounting system. | 10 | 14 | TBD | 17 | 2009 | Effective Management of Human Capital/Information Technology/Resources | Mission and Business Results | Reporting and Information | Number of material weaknesses cited in the financial audit | 1 | 0 | TBD | 18 | 2009 | Effective Management of Human Capital/Information Technology/Resources | Customer Results | Service Efficiency | Number of contractors that can produce standing reports and queries on demand, resulting in cost and time savings. | 14 | 21 | TBD | 19 | 2009 | Effective Management of Human Capital/Information Technology/Resources | Processes and Activities | Compliance | Support the U.S. Department of Health & Human Service's Federal Financial Management Improvement Act (FFMIA) compliance goal in having total CMS Payment Dollars on HIGLAS | 62.2% | 67.8% | TBD | 20 | 2009 | Effective Management of Human Capital/Information Technology/Resources | Technology | Availability | The number of Medicare contractors transitioned to HIGLAS, a certified general ledger accounting system. | 14 | 21 | TBD | 21 | 2010 | Effective Management of Human Capital/Information Technology/Resources | Mission and Business Results | Reporting and Information | Number of material weaknesses cited in the financial audit | 1 | 0 | TBD | 22 | 2010 | Effective Management of Human Capital/Information Technology/Resources | Customer Results | Service Efficiency | Number of contractors that can produce standing reports and queries on demand, resulting in cost and time savings. | 21 | 23 | TBD | 23 | 2010 | Effective Management of Human Capital/Information Technology/Resources | Processes and Activities | Compliance | Support the U.S. Department of Health & Human Service's Federal Financial Management Improvement Act (FFMIA) compliance goal in having total CMS Payment Dollars on HIGLAS | 67.8% | 96.8% | TBD | 24 | 2010 | Effective Management of Human Capital/Information Technology/Resources | Technology | Availability | The number of Medicare contractors transitioned to HIGLAS, a certified general ledger accounting system. | 21 | 23 | TBD | 25 | 2011 | Effective Management of Human Capital/Information Technology/Resources | Mission and Business Results | Reporting and Information | Number of material weaknesses cited in the financial audit | 1 | 0 | TBD | 26 | 2011 | Effective Management of Human Capital/Information Technology/Resources | Customer Results | Service Efficiency | Number of contractors that can produce standing reports and queries on demand, resulting in cost and time savings. | 21 | 23 | TBD | 27 | 2011 | Effective Management of Human Capital/Information Technology/Resources | Processes and Activities | Compliance | Support the U.S. Department of Health & Human Service's Federal Financial Management Improvement Act (FFMIA) compliance goal in having total CMS Payment Dollars on HIGLAS | 96.8% | 100% | TBD | 28 | 2011 | Effective Management of Human Capital/Information Technology/Resources | Technology | Availability | The number of Medicare contractors transitioned to HIGLAS, a certified general ledger accounting system. | 23 | 23 | TBD | 29 | 2012 | Effective Management of Human Capital/Information Technology/Resources | Mission and Business Results | Reporting and Information | Number of material weaknesses cited in the financial audit | 1 | 0 | TBD | 30 | 2012 | Effective Management of Human Capital/Information Technology/Resources | Customer Results | Service Efficiency | Number of contractors that can produce standing reports and queries on demand, resulting in cost and time savings. | 23 | 23 | TBD | 31 | 2012 | Effective Management of Human Capital/Information Technology/Resources | Processes and Activities | Compliance | Support the U.S. Department of Health & Human Service's Federal Financial Management Improvement Act (FFMIA) compliance goal in having total CMS Payment Dollars on HIGLAS | 100% | 100% | TBD | 32 | 2012 | Effective Management of Human Capital/Information Technology/Resources | Technology | Availability | The number of Medicare contractors transitioned to HIGLAS, a certified general ledger accounting system. | 23 | 23 | TBD |
Enterprise Architecture In order to successfully address this area of the business case and capital asset plan you must ensure the investment is included in the agency's EA and Capital Planning and Investment Control (CPIC) process, and is mapped to and supports the FEA. You must also ensure the business case demonstrates the relationship between the investment and the business, performance, data, services, application, and technology layers of the agency's EA. - 1. Is this investment included in your agency's target enterprise architecture?
- yes
- 2. Is this investment included in the agency's EA Transition Strategy?
- yes
- 2.a. If yes, provide the investment name as identified in the Transition Strategy provided in the agency's most recent annual EA Assessment.
- CMS Healthcare Integrated General Ledger Accounting System (HIGLAS)
- 3. Is this investment identified in a completed (contains a target architecture) and approved segment architecture?
- yes
- 3.a. If yes, provide the name of the segment architecture as provided in the agency’s most recent annual EA Assessment.
- Healthcare Integrated General Ledger Accounting
- 4. Identify the service components funded by this major IT investment (e.g., knowledge management, content management, customer relationship management, etc.). Provide this information in the format of the following table. For detailed guidance regarding components, please refer to http://www.whitehouse.gov/omb/egov/.
Component: Use existing SRM Components or identify as NEW. A NEW component is one not already identified as a service component in the FEA SRM.
Reused Name and UPI: A reused component is one being funded by another investment, but being used by this investment. Rather than answer yes or no, identify the reused service component funded by the other investment and identify the other investment using the Unique Project Identifier (UPI) code from the OMB Ex 300 or Ex 53 submission.
Internal or External Reuse?: Internal reuse is within an agency. For example, one agency within a department is reusing a service component provided by another agency within the same department. External reuse is one agency within a department reusing a service component provided by another agency in another department. A good example of this is an E-Gov initiative service being reused by multiple organizations across the federal government.
Funding Percentage: Please provide the percentage of the BY requested funding amount used for each service component listed in the table. If external, provide the funding level transferred to another agency to pay for the service. Row | Agency Component Name | Agency Component Description | Service Type | Component | Reused Component Name | Reused UPI | Internal or External Reuse? | Funding % |
---|
1 | Decision Support and Planning | Defines the set of capabilities that support the analyze information and predict the impact of decisions before they are made. | Business Intelligence | Decision Support and Planning | | | No Reuse | 14 | 2 | Credit / Charge | Defines the set of capabilities that support the use of credit cards or electronic funds transfers for payment and collection of products or services. | Financial Management | Credit / Charge | | | No Reuse | 14 | 3 | Debt Collection | Defines the set of capabilities that support the process of accounts receivable. | Financial Management | Debt Collection | | | No Reuse | 14 | 4 | Billing and Accounting | Defines the set of capabilities that support the charging, collection and reporting of an organization's accounts. | Financial Management | Billing and Accounting | | | No Reuse | 14 | 5 | Payment / Settlement | Defines the set of capabilities that support the process of accounts payable. | Financial Management | Payment / Settlement | | | No Reuse | 14 | 6 | Auditing | Defines the set of capabilities that support the examination and verification of records for accuracy. | Financial Management | Auditing | | | No Reuse | 14 | 7 | Internal Controls | Support the methods and procedures used by the organization to safeguard its assets, produce accurate accounting data and reports, contribute to efficient operations, and encourage staff to adhere to management policies and mission requirements | Financial Management | Internal Controls | | | No Reuse | 14 |
- 5. To demonstrate how this major IT investment aligns with the FEA Technical Reference Model (TRM), please list the Service Areas, Categories, Standards, and Service Specifications supporting this IT investment.
FEA SRM Component: Service Components identified in the previous question should be entered in this column. Please enter multiple rows for FEA SRM Components supported by multiple TRM Service Specifications.
Service Specification: In the Service Specification field, Agencies should provide information on the specified technical standard or vendor product mapped to the FEA TRM Service Standard, including model or version numbers, as appropriate. Row | SRM Component | >Service Area | Service Category | Service Standard | Service Specification (i.e., vendor and product name) |
---|
1 | Auditing | Service Platform and Infrastructure | Database / Storage | Storage | IBM Enterprise Storage Server | 2 | Billing and Accounting | Service Platform and Infrastructure | Database / Storage | Storage | IBM Enterprise Storage Server | 3 | Credit / Charge | Service Platform and Infrastructure | Database / Storage | Storage | IBM Enterprise Storage Server | 4 | Debt Collection | Service Platform and Infrastructure | Database / Storage | Storage | IBM Enterprise Storage Server | 5 | Internal Controls | Service Platform and Infrastructure | Database / Storage | Storage | IBM Enterprise Storage Server | 6 | Payment / Settlement | Service Platform and Infrastructure | Database / Storage | Storage | IBM Enterprise Storage Server | 7 | Decision Support and Planning | Service Platform and Infrastructure | Database / Storage | Storage | IBM Enterprise Storage Server | 8 | Auditing | Service Access and Delivery | Delivery Channels | Intranet | Medicare Data Center Network (MDCN) | 9 | Billing and Accounting | Service Access and Delivery | Delivery Channels | Intranet | Medicare Data Center Network (MDCN) | 10 | Credit / Charge | Service Access and Delivery | Delivery Channels | Intranet | Medicare Data Center Network (MDCN) | 11 | Debt Collection | Service Access and Delivery | Delivery Channels | Intranet | Medicare Data Center Network (MDCN) | 12 | Internal Controls | Service Access and Delivery | Delivery Channels | Intranet | Medicare Data Center Network (MDCN) | 13 | Payment / Settlement | Service Access and Delivery | Delivery Channels | Intranet | Medicare Data Center Network (MDCN) | 14 | Decision Support and Planning | Service Access and Delivery | Delivery Channels | Intranet | Medicare Data Center Network (MDCN) | 15 | Auditing | Service Access and Delivery | Delivery Channels | Virtual Private Network (VPN) | Medicare Data Center Network (MDCN) | 16 | Billing and Accounting | Service Access and Delivery | Delivery Channels | Virtual Private Network (VPN) | Medicare Data Center Network (MDCN) | 17 | Credit / Charge | Service Access and Delivery | Delivery Channels | Virtual Private Network (VPN) | Medicare Data Center Network (MDCN) | 18 | Debt Collection | Service Access and Delivery | Delivery Channels | Virtual Private Network (VPN) | Medicare Data Center Network (MDCN) | 19 | Internal Controls | Service Access and Delivery | Delivery Channels | Virtual Private Network (VPN) | Medicare Data Center Network (MDCN) | 20 | Payment / Settlement | Service Access and Delivery | Delivery Channels | Virtual Private Network (VPN) | Medicare Data Center Network (MDCN) | 21 | Auditing | Service Platform and Infrastructure | Database / Storage | Database | Oracle | 22 | Billing and Accounting | Service Platform and Infrastructure | Database / Storage | Database | Oracle | 23 | Credit / Charge | Service Platform and Infrastructure | Database / Storage | Database | Oracle | 24 | Debt Collection | Service Platform and Infrastructure | Database / Storage | Database | Oracle | 25 | Internal Controls | Service Platform and Infrastructure | Database / Storage | Database | Oracle | 26 | Payment / Settlement | Service Platform and Infrastructure | Database / Storage | Database | Oracle | 27 | Decision Support and Planning | Service Platform and Infrastructure | Database / Storage | Database | Oracle | 28 | Auditing | Component Framework | Data Management | Database Connectivity | Oracle | 29 | Billing and Accounting | Component Framework | Data Management | Database Connectivity | Oracle | 30 | Credit / Charge | Component Framework | Data Management | Database Connectivity | Oracle | 31 | Debt Collection | Component Framework | Data Management | Database Connectivity | Oracle | 32 | Internal Controls | Component Framework | Data Management | Database Connectivity | Oracle | 33 | Payment / Settlement | Component Framework | Data Management | Database Connectivity | Oracle | 34 | Decision Support and Planning | Component Framework | Data Management | Database Connectivity | Oracle | 35 | Auditing | Component Framework | Data Management | Reporting and Analysis | Oracle | 36 | Billing and Accounting | Component Framework | Data Management | Reporting and Analysis | Oracle | 37 | Credit / Charge | Component Framework | Data Management | Reporting and Analysis | Oracle | 38 | Debt Collection | Component Framework | Data Management | Reporting and Analysis | Oracle | 39 | Internal Controls | Component Framework | Data Management | Reporting and Analysis | Oracle | 40 | Payment / Settlement | Component Framework | Data Management | Reporting and Analysis | Oracle | 41 | Decision Support and Planning | Component Framework | Data Management | Reporting and Analysis | Oracle | 42 | Auditing | Service Platform and Infrastructure | Delivery Servers | Application Servers | Oracle Application Server | 43 | Billing and Accounting | Service Platform and Infrastructure | Delivery Servers | Application Servers | Oracle Application Server | 44 | Credit / Charge | Service Platform and Infrastructure | Delivery Servers | Application Servers | Oracle Application Server | 45 | Debt Collection | Service Platform and Infrastructure | Delivery Servers | Application Servers | Oracle Application Server | 46 | Internal Controls | Service Platform and Infrastructure | Delivery Servers | Application Servers | Oracle Application Server | 47 | Payment / Settlement | Service Platform and Infrastructure | Delivery Servers | Application Servers | Oracle Application Server | 48 | Decision Support and Planning | Service Platform and Infrastructure | Delivery Servers | Application Servers | Oracle Application Server | 49 | Decision Support and Planning | Service Access and Delivery | Access Channels | Web Browser | Windows Internet Explorer | 50 | Credit / Charge | Service Access and Delivery | Access Channels | Web Browser | Windows Internet Explorer | 51 | Debt Collection | Service Access and Delivery | Access Channels | Web Browser | Windows Internet Explorer | 52 | Billing and Accounting | Service Access and Delivery | Access Channels | Web Browser | Windows Internet Explorer | 53 | Payment / Settlement | Service Access and Delivery | Access Channels | Web Browser | Windows Internet Explorer | 54 | Auditing | Service Access and Delivery | Access Channels | Web Browser | Windows Internet Explorer | 55 | Internal Controls | Service Access and Delivery | Access Channels | Web Browser | Windows Internet Explorer | 56 | Decision Support and Planning | Service Access and Delivery | Access Channels | Web Browser | Windows Internet Explorer |
- 6. Will the application leverage existing components and/or applications across the Government (i.e., FirstGov, Pay.Gov, etc)?
- yes
- 6.a. If yes, please describe.
- This investment leverages: Financial Management (FM) Line of Business
PART TWO
RISK You should perform a risk assessment during the early planning and initial concept phase of the investment's life-cycle, develop a risk-adjusted life-cycle cost estimate and a plan to eliminate, mitigate or manage risk, and be actively managing risk throughout the investment's life-cycle.Answer the following questions to describe how you are managing investment risks. - 1. Does the investment have a Risk Management Plan?
- yes
- 1.a. If yes, what is the date of the plan?
- 2006-12-22
- 1.b. Has the Risk Management Plan been significantly changed since last year's submission to OMB?
- no
- 3. Briefly describe how investment risks are reflected in the life cycle cost estimate and investment schedule:
- Program risk management is an ongoing part of project management on the HIGLAS program. We have a very robust risk management capability in place that requires biweekly meetings with active participation spanning all aspects of the HIGLAS program. The systems integrator and CMS actively work together to identify, manage and track risks that could adversely impact the program. Costs associated with the risk capability are captured in individual task orders and included in the cost estimated throughout the lifecycle of HIGLAS. Due to the complexity of the HIGLAS program there are several identified areas of high risk. Schedule and cost risks are continously monitored and mitigated through our established processes. In some cases, scope and/or schedule must be adjusted to avert cost overruns. Risks associated with added functionality to HIGLAS are assessed and mitigation and/or contingency plans are developed as necessary. Risks relative to government mandates are managed within existing risk management processes.
COST & SCHEDULE
- 1. Does the earned value management system meet the criteria in ANSI/EIA Standard 748?
- yes
- 2. Is the CV% or SV% greater than ± 10%?
- no
- 3. Has the investment re-baselined during the past fiscal year?
- no
|
|
|