U.S. Department of Education: Promoting Educational Excellence for all Americans

ADvance - Person Data Management Program (PDM)

Exhibit 300: Capital Asset Plan and Business Case Summary
Part I: Summary Information And Justification

Section A: Overview

  1. Date of submission: May 29, 2008
  2. Agency: 018
  3. Bureau: 45
  4. Name of this Capital Asset: ADvance - Person Data Management Program (PDM)
  5. Unique Project (Investment) Identifier: 018-45-01-06-01-3010-00
  6. What kind of investment will this be in FY2010? Planning
  7. What was the first budget year this investment was submitted to OMB? FY2009
  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: The ADvance - Person Data Management Program is a key next step in realizing Federal Student Aid's modernization and integration efforts. The ADvance program has focused its effort around the essential first step in the student aid life cycle and its impact to business functions and needs across phases of the student aid life cycle, namely the creation, maintenance, access, storage and viewing of "person" information. The ADvance-PDM program will implement key components within the FSA Target State Vision. These key components are the Person Record Management System, Personal Identification Number (PIN) system Re-engineering, Integrated Student View, and the Operational data Store. (1) Person Record Management Service (PRMS): The PRMS is a centralized system of record for Person data for all Federal Student Aid Application systems. PRMS faciliates reducing the use of Social Security numbers. This system will originate and help maintain a new identifier that will replace Social Security Numbers to comply with Congressional mandate. (2) PIN Re-engineering: Re-engineer the PIN database to make it an enterprise asset that is aligned with our security architecture. (3) Integrated Student View (ISV): ISV will create an enterprise service utilizing the enterprise Portal asset and infrastructure to allow for current, consistent, comprehensive and accurate views of student data. Delivering this functionality will leverage recent advancements and implementations of the enabling infrastructure facilitating an enterprise service oriented architecture (SOA). (4) Operational Data Store (ODS): The ODS will be used to store, manage, and access operational data to support Integrated Student View and to facilitate convenient, reliable, and efficient usage of enterprise operational data. ODS is a key dependency in reengineering NSLDS.
  9. Did the Agency's Executive/Investment Committee approve this request? yes
    1. If "yes," what was the date of this approval? Aug 30, 2007
  10. Did the Project Manager review this Exhibit? yes
  11. Contact information of Program/Project Manager?
Name  
Phone Number  
E-mail  
    1. What is the current FAC-P/PM (for civilian agencies) or DAWIA (for defense agencies) certification level of the program/project manager? Senior/Expert/DAWIA-Level 3
  1. Has the agency developed and/or promoted cost effective, energy efficient and environmentally sustainable techniques or practices for this project. no
    1. Will this investment include electronic assets (including computers)? yes
    2. Is this investment for new construction or major retrofit of a Federal building or facility? (answer applicable to non-IT assets only) no
      1. If "yes," is an ESPC or UESC being used to help fund this investment? yes
      2. If "yes," will this investment meet sustainable design principles? [Not answered]
      3. If "yes," is it designed to be 30% more energy efficient than relevant code? [Not answered]
  2. Does this investment directly support one of the PMA initiatives? yes
    Eliminating Improper Payments
    Financial Performance
    1. Briefly and specifically describe for each selected how this asset directly supports the identified initiative(s)? Federal Student Aid currently determines relies on National Student Loan Data System (NSLDS) for determining eligibility. Untimely and inaccurate information in the NSLDS will cause erroneous and overpayment of federal student aid to applicants. This initiative will reduce the number of overpayments by accurately identifying aid recipients thus eliminating duplicate payments and payments to students that are not entitled to financial aid.
  3. Does this investment support a program assessed using the Program Assessment Rating Tool (PART)? (For more information about the PART, visit www.whitehouse.gov/omb/part.) no
    1. If "yes," does this investment address a weakness found during a PART review? [Not answered]
    2. If "yes," what is the name of the PARTed program? [Not answered]
    3. If "yes," what rating did the PART receive? [Not answered]
  4. Is this investment for information technology? yes

For information technology investments only:

  1. What is the level of the IT Project? (per CIO Council PM Guidance) Level 2
  2. In addition to the answer in 11(a), what project management qualifications does the Project Manager have? (per CIO Council PM Guidance) (1) Project manager has been validated as qualified for this investment
  3. Is this investment or any project(s) within this investment identified as "high risk" on the Q4-FY 2008 agency high risk report (per OMB Memorandum M-05-23)? yes
  4. Is this a financial management system? no
    1. If "yes," does this investment address a FFMIA compliance area? [Not answered]
      1. If "yes," which compliance area: [Not answered]
      2. If "no," what does it address? [Not answered]
    2. 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 A-11 section 52 [Not answered]
  5. What is the percentage breakout for the total FY2010 funding request for the following?
Hardware 0
Software 6
Services 94
Other 0
  1. 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? yes
  2. Contact information of individual responsible for privacy related questions:
Name  
Phone Number  
Title  
E-mail  
  1. Are the records produced by this investment appropriately scheduled with the National Archives and Records Administration's approval? no
  2. Does this investment directly support one of the GAO High Risk Areas? no

Section B: Summary of Spending

  1.  

Table 1: SUMMARY OF SPENDING FOR PROJECT PHASES
(REPORTED IN MILLIONS)
(Estimates for BY+1 and beyond are for planning purposes only and do not represent budget decisions)
  PY-1 and earlier PY 2008 CY 2009 BY 2010 BY+1 2011 BY+2 2012 BY+3 2013 BY+4 and beyond Total
Planning: 0.37 0.85 0 1.8          
Acquisition: 0 0 8.59 9          
Subtotal Planning amp; Acquisition: 0.37 0.85 8.59 10.8          
Operations & Maintenance: 0 0 0 0.36          
TOTAL: 0.37 0.85 8.59 11.16          
Government FTE Costs 0.34 0 8 13.7          
Number of FTE represented by Costs: 3 0 1 2          
  1. Will this project require the agency to hire additional FTE's? yes
    1. If "yes", How many and in what year? Two additional FTE's in 2008
  2. If the summary of spending has changed from the FY2009 President's budget request, briefly explain those changes: The changes in the Summary of Spending reflect a newer model in which the work for the PRMS will be awarded and phases, thereby redistributing the expenditure.

Section D: Performance Information

Performance Information Table
Fiscal Year Strategic Goal(s) Supported Measurement Area Measurement Grouping Measurement Indicator Baseline Target Actual Results
2008 Goal 3, Objective 2: Deliver federal student aid to students and parents effectively and efficiently Customer Results User Requirements Percentage of identified key Federal Student Aid stakeholders who were actively involved in defining detailed requirments for the PIN Re-engineering. (PIN Re-engineering). 66% 90% Report due 09/2008
2008 Goal 3, Objective 2: Deliver federal student aid to students and parents effectively and efficiently Customer Results Accuracy of Service or Product Delivered Stakeholder that were actively involved in defining detailed requirements for the Integrated Student View (ISV) 66% 90% Report due 09/2008
2008 Goal 3: Objective 2: Deliver federal student aid to students and parents effectively and efficiently. Customer Results User Requirements Percentage of identified key Federal Student Aid stakeholders who were actively involved in defining detailed requirements for the Person Record Management Service (PRMS). 66% 95% Report due 09/2008
2009 Goal 3: Objective 2: Deliver federal student aid to students and parents effectively and efficiently. Technology Integration Establish Proof of Concept (POC) for PRMS using enterprise standards/ infrastructure. (PRMS) that uniquely identifies individuals from their initial contact with FSA through financial aid lifecycle & how solution manages/maintains uniqueness. Baseline to be establised in deliverable due 140 days after contract award Meets Criteria Due 9/2009
2009 Goal 3: Objective 2: Deliver federal student aid to students and parents effectively and efficiently. Customer Results Lifecycle/Change Management Percentage of requirments artifacts produced per Requirements Management Plan for PRMS. (PRMS) 0% 90% of artifacts as identified as appropriate for the current stage or phase Report due 9 months after contract award
2009 Goal 3, Objective 2: Deliver federal student aid to students and parents effectively and efficiently. Processes and Activities Lifecycle/Change Management Percentage of requirements artifacts produced per Requirments Management Plan for PIN Re-engineering. 0% 90% of artifacts as identified as appropriate for the current stage or phase Report due 9 months after contract award
2009 Goal 3: Objective 2: Deliver federal student aid to students and parents effectively and efficiently. Processes and Activities Accuracy of Service or Product Delivered Percentage of requirements captured in requirements artifacts that have been validated through an IV&V process for accuracy and completeness. (PRMS) 0% 90% Due 09/2009
2009 Goal 3, Objective 2: Deliver federal student aid to students and parents effectively and efficiently. Processes and Activities Accuracy of Service or Product Delivered Percentage of requirments captured in requirements artifacts that have been validated through an IV&V process for accuracy and completeness for PIN Re-engineering. (PIN Re-engineering) 0% 85% of requirements identified as appropriate for the current stage or phase Due 09/2009
2009 Goal 3, Objective 2: Deliver federal student aid to students and parents effectively and effieciently. Processes and Activities Lifecycle/Change Management Percentage of requirements artifacts produced per Requirements Management Plan for ODS. (ODS) 0% 90% of artifacts as identified as appropriate for the current stage or phase Due 9/2009
2009 Goal 3, Objective 2: Deliver federal student aid to student sand parents effectively and efficiently. Mission and Business Results User Requirements Percentage of identified key Federal Student Aid stakeholders that were actively involved in defining detailed requirements for the Operational Data Store. (ODS) 66% 90% Due 09/2009
2010 Goal 3, Objective 2: Deliver federal student aid to students and parents effectively and efficiently Processes and Activities User Requirements Percentage of Requirements artifacts completed per the Requirements Management Plan for ISV 0% 90% of artifacts as identified as appropriate for the current stage or phase Due 09/2010
2010 Goal 3, Objective 2: Deliver federal student aid to students and parents effectively and efficiently. Technology Internal Data Sharing Number of Applications pulling data for use in production from the ODS for views or reports 0 1 Due 09/2010
2010 Goal 3: Objective 2: Deliver federal student aid to students and parents effectively and efficiently. (PRMS) Customer Results System Development Percentage of baselined artifacts validated in production. 0 85% Due 09/2010
2010 Goal 3, Objective 2: Deliver federal student aid to students and parents effectively and efficiently. Customer Results Integration Percentage of active Students/Borrowers authenticated using the new PIN token. (PIN Re-engineering) 0% 25% Due 09/2010
2010 Goal 3, Objective 2: Deliver federal student aid to students and parents effectively and efficiently Customer Results Data Reliability and Quality Percentage of Data that has been profiled and cleansed being fed into the ODS 0% 85% Due 09/2010
2010 Goal 3: Objective 2: Deliver federal student aid to students an parents effectively and efficiently. Processes and Activities Accuracy of Service or Product Delivered Percentage of requirements captured in requirements artifacts that have been through an IV&V process for accuracy and completeness for PIN Re-engineering. (PIN Re-engineering) 0% 90% Due 09/2010
2010 Goal 3, Objective 2: Deliver federal student aid to students and parents effectively and efficiently Processes and Activities Lifecycle/Change Management Percentage of requirements artifacts produced per Requirements Management plan for ISV 0% 100% 100%
2010 Goal 3, Objective 2: Deliver federal student aid to students and parents effectively and efficiently Processes and Activities Accuracy of Service or Product Delivered Percentage of requirements captured in requirements artifacts that have been validated through an IV&V process for accuracy and completeness for ISV. 0% 90% Due 09/2010
2010 Goal 3: Objective 2: Deliver federal student aid to students and parents effectively and efficiently. Mission and Business Results Integration Number of Major Applications that have adopted the use of PRMS. (PRMS) 0 1 major application Due 09/2010
2010 Goal 3: Objective 2: Deliver federal student aid to students and parents effectively and efficiently. Mission and Business Results Integration Percentage of Active Students/Borrowers assigned a Enterprise Identifier. (PRMS) 0 25% Due 09/2010
2010 Goal 3, Objective 2: Deliver federal student aid to students and parents effectively and efficiently Mission and Business Results Internal Data Sharing Number of Applications feeding data to the ODS in production 0 1 09/2010
2011 Goal 3: Objective 2: Deliver federal student aid to students and parents effectively and efficiently. Technology Integration Number of Major Applications that have adopted use of the PRMS. (PRMS) 1 2 09/2011

Section F: Enterprise Architecture (EA)

  1. Is this investment included in your agency's target enterprise architecture? yes
    1. If "no," please explain why? [Not answered]
  2. Is this investment included in the agency's EA Transition Strategy? yes
    1. If "yes," provide the investment name as identified in the Transition Strategy provided in the agency's most recent annual EA Assessment. ADvance - Transition Strategy updates will be provided in the next annual EA Assessment.
    2. If "no," please explain why? [Not answered]
  3. Is this investment identified in a completed and approved segment architecture? yes
    1. If "yes," provide the six digit code corresponding to the agency segment architecture. The segment architecture codes are maintained by the agency Chief Architect. For detailed guidance regarding segment architecture codes, please refer to http://www.egov.gov/. 206-000

4. Service Component Reference Model (SRM) Table :

Agency Component Name Agency Component Description FEA SRM Service Type FEA SRM Component Service Component Reused Internal or External Reuse? BY Funding Percentage
Component Name UPI
Advance PDM Integrated Student View (ISV) Provides an enterprise service to allow for current, consistent, comprehensive and accurate views of student data Content Management Content Publishing and Delivery Content Publishing and Delivery 018-45-01-06-01-0000-00 Internal 10
Advance PDM Integrated Student View (ISV) Provides an enterprise service to allow for current, consistent, comprehensive and accurate views of student data Knowledge Management Information Retrieval [Not answered] [Not answered] No Reuse 5
Advance PDM Integrated Student View (ISV) Provides an enterprise service to allow for current, consistent, comprehensive and accurate views of student data Knowledge Management Knowledge Distribution and Delivery [Not answered] [Not answered] No Reuse 5
Advance PDM Operational Data Store (ODS) Provides a service to store, manage, and access operational data in support of the Integrated Student View and to facilitate convenient, reliable, and efficient usage of enterprise operational data Data Management Data Mart [Not answered] [Not answered] No Reuse 5
Advance PDM Operational Data Store (ODS) Provides a service to store, manage, and access operational data in support of the Integrated Student View and to facilitate convenient, reliable, and efficient usage of enterprise operational data Data Management Enterprise Application Integration Enterprise Application Integration 018-45-01-06-01-1120-00 Internal 6
Advance PDM Operational Data Store (ODS) Provides a service to store, manage, and access operational data in support of the Integrated Student View and to facilitate convenient, reliable, and efficient usage of enterprise operational data Document Management Data Exchange Data Exchange 018-45-01-06-01-1120-00 Internal 10
Advance PDM Operational Data Store (ODS) Provides a service to store, manage, and access operational data in support of the Integrated Student View and to facilitate convenient, reliable, and efficient usage of enterprise operational data Reporting OLAP [Not answered] [Not answered] No Reuse 5
Advance PDM Operational Data Store (ODS) Provides a service to store, manage, and access operational data in support of the Integrated Student View and to facilitate convenient, reliable, and efficient usage of enterprise operational data Reporting Standardized / Canned [Not answered] [Not answered] No Reuse 5
Advance PDM Operational Data Store (ODS) Provides a service to store, manage, and access operational data in support of the Integrated Student View and to facilitate convenient, reliable, and efficient usage of enterprise operational data Search Query [Not answered] [Not answered] No Reuse 20
Advance PDM Person Record Management System (PRMS) Provides a centralized system of record for Person data for all Federal Student Aid Application systems Data Management Enterprise Application Integration Enterprise Application Integration 018-45-01-06-01-1120-00 Internal 10
Advance PDM Person Record Management System (PRMS) Provides a centralized system of record for Person data for all Federal Student Aid Application systems Development and Integration Data Exchange Data Exchange 018-45-01-06-01-1120-00 Internal 5
Advance PDM Person Record Management System (PRMS) Provides a centralized system of record for Person data for all Federal Student Aid Application systems Customer Relationship Management Contact and Profile Management [Not answered] [Not answered] No Reuse 5
Advance PDM Person Record Management System (PRMS) Provides a centralized system of record for Person data for all Federal Student Aid Application systems Management of Processes Business Rule Management [Not answered] [Not answered] No Reuse 5
Advance PDM PIN Re-engineering (PIN) Provides a secure user authentication infrastructure for web-based transactions, eliminating the need for separate processes for the verification of identity and electronic signatures Security Management Identification and Authentication Identification and Authentication 018-45-03-00-02-2050-00 Internal 4

 

5. Technical Reference Model (TRM) Table:

FEA SRM Component FEA TRM Service Area FEA TRM Service Category FEA TRM Service Standard Service Specification
Identification and Authentication Service Access and Delivery Service Requirements Authentication / Single Sign-on IBM Tivoli Identity Manger (TIM)
Data Exchange Service Platform and Infrastructure Database / Storage Database Oracle 10g
Enterprise Application Integration Service Access and Delivery Integration Enterprise Application Integration Websphere Business Integration Broker
Enterprise Application Integration Service Access and Delivery Integration Enterprise Application Integration IBM Process Server
Business Rule Management Component Framework Business Logic Independent Platform Websphere Business Integration Broker
Identification and Authentication Service Platform and Infrastructure Database / Storage Database Oracle 10g
Contact and Profile Management Service Interface and Integration Interface Service Description / Interface Web Services Description Language (WSDL)
Information Retrieval Service Interface and Integration Interface Service Description / Interface Web Services Description Language (WSDL)
Data Exchange Service Interface and Integration Interface Service Description / Interface Web Services Description Language (WSDL)
Data Exchange Service Platform and Infrastructure Database / Storage Database Oracle 10g
Data Exchange Service Interface and Integration Integration Service Discovery IBM WebSphere ESB UDDI
Data Exchange Service Interface and Integration Interface Service Description / Interface Web Services Description Language (WSDL)
Content Publishing and Delivery Service Access and Delivery Delivery Channels Internet Enterprise Portal-To be implemented
Data Exchange Service Access and Delivery Database / Storage Database Oracle 10g
Knowledge Distribution and Delivery Service Access and Delivery Delivery Channels Internet Enterprise Portal-To be implemented
Data Mart Service Platform and Infrastructure Database / Storage Database Oracle v8.1.7.4-To be implemented
OLAP Component Framework Data Management Reporting and Analysis Microstrategy Incorporated, Data Analysis Server, 7.5.4-To be implemented
Standardized / Canned Component Framework Data Management Reporting and Analysis Microstrategy Incorporated, Data Analysis Server, 7.5.4-To be implemented
Query Service Platform and Infrastructure Delivery Servers Web Servers IBM Corporation, zOS Version 7.1
  1. Will the application leverage existing components and/or applications across the Government (i.e., USA.Gov, Pay.Gov, etc)? no
    1. If "yes," please describe. [Not answered]

Part II: Planning, Acquisition And Performance Information

Section A: Alternatives Analysis

  1. Did you conduct an alternatives analysis for this investment? yes
    1. If "yes," provide the date the analysis was completed? Mar 28, 2008
    2. If "no," what is the anticipated date this analysis will be completed? [Not answered]
    3. If no analysis is planned, please briefly explain why: [Not answered]

2. Alternatives Analysis Results:

Alternative Analyzed Description of Alternative Risk Adjusted Lifecycle Costs estimate Risk Adjusted Lifecycle Benefits estimate
Alternative 1- New Technologies ADvance Person Data Management: (1) Person Record Management System (PRMS) (2) Personal Identification Number Re-Engineering (PIN) (3) Integrated Student View (ISV) (4) Operational Data Store (ODS) PRMS is a centralized system of record for Person data for all Federal Student Aid Application systems. PIN Re-engineering will redo the PIN database to make it an enterprise asset that is aligned with our security architecture. ISV will create and enterprise service using the enterprise Portal asset and infrastructure to allow for current consistent, comprehensive and accurate views of student data. ODS will be used to store manage and access operation data to support ISV. 145000 245.12
Alternative 2- New and Existing Technology Description. This model builds the PRMS and ODS, but integrates data resident in the new ODS with existing Federal Student Aid PIN capability and National Student Loan Data Store (NSLDS) student sites, and Student Aid on the Web (SAOTW) online information presentation. The ODS would be housed in a mainframe based environment, while PIN and PRMS would exist on a server. The legacy NSLDS student sites, however, would continue to reside on their existing mainframe, but SAOTW would be based on a server 238000 245.12
Alternative 3: New and Existing Technology 2: This model builds the PRMS and the ODS integrating data resident in the new ODS with a Re-engineered PIN infrastructure in a server -based environment. Federal Student Aid online information in mainframe-based NSLDS student sites as well as on the server based SAOTW website 175 245.12
Status Quo- Existing Technology : The combination of components that comprise existing systems use and use NSLDS student sites and Stuent Aid on the Web to provide Federal Student Aid information to pre applicants, applicants, and aid participants. National Student Loan Data System was established to provide a repository of information about Title IV aid recipients and their loans, grants, lenders, Guaranty Agencies (GA), servicers, and schools. As NSLDS has evolved since its implementation in 1994, it has become much more than an analytical and reporting system and now supports key operational requirements. NSLDS determines eligibility, calculates default rates, and supports financial management activities. 178.549 0
  1. Which alternative was selected by the Agency's Executive/Investment Committee and why was it chosen? Alternative 1: New Technology produces the optimum data management solution in a server-based environment. Alternative 1 satisfies the Congressional mandate in H.R. 4137 to ensure protection of Federal Student Aid participants' Social Security Numbers at the lowest life cycle cost. This model supports the Privacy Act of 1974 (as amended). An agency is required to establish appropriate administrative, technical and physical safeguards to insure the security and confidentiality of records and to protect against any anticipated threats or hazards to their security or integrity which could result in substantial harm, embarrassment, inconvenience, or unfairness to any individual on whom information is maintained. Life Cycle Benefit is depicted as uniform across the three alternatives to Status Quo as PRMS, as key component of PDM is new technology in all non-Status Quo alternatives. With combined LC Cost and Benefits, Alternative 1 is the optimum solution.
    1. What year will the investment breakeven? (Specifically, when the budgeted costs savings execced the cumulative costs.) 2015
  2. What specific qualitative benefits will be realized? In addition to cost avoidances from identity theft, alternative 1 also improves the accuracy and efficiency of multiple Federal Student Aid processes: It allows an enterprise method (student ID) to identify students so data from multiple stores within Federal Student Aid can be aggregated for viewing or research; presents a single, integrated student view with student aid status; manages address information consistently across the enterprise; allows PIN updates from the Central Processing System and other systems; Automates the process of linking results of Pell grant disbursements with applicant data; reduces incorrect identifiers submitted to Federal Student Aid systems resulting in invalid student/borrowers; reduces error files among the Common Origination and Disbursement (COD), Direct Loan Servicing System (DLSS), and National Student Loan Data System (NSLDS) due to identifier conflicts in NSLDS, provides identifier updates to all systems throughout the financial aid lifecycle.

5. Federal Quantitative Benefits ($millions):

  Budgeted Cost Savings Cost Avoidance Justification for Budgeted Cost Savings Justification for Budgeted Cost Avoidance
PY-1 and Prior  
PY  
CY  
BY  
BY+1  
BY+2  
BY+3  
BY+4 and Beyond 70.5 245.12 Status Quo LCC less Alt 1 LCC Citizen Savings (HR 4137)
Total LCC Benefit 70.5 245.12 LCC = Life-cycle cost
  1. Will the selected alternative replace a legacy system in-part or in-whole? yes
    1. If "yes," are the migration costs associated with the migration to the selected alternative included in this investment, the legacy investment, or in a separate migration investment? Migration Investment
    2. If "yes," please provide the following information:

List of Legacy Investment or Systems
Name of the Legacy Investment or Systems UPI if available Date of the System Retirement
The investment will not result in the retirement of a full system [Not answered] Jan 1, 9999

Section B: Risk Management (All Capital Assets)

  1. Does the investment have a Risk Management Plan? yes
    1. If "yes," what is the date of the plan? Aug 29, 2008
    2. Has the Risk Management Plan been significantly changed since last year's submission to OMB? yes
    3. If "yes," describe any significant changes: No plan available last year.
  2. If there currently is no plan, will a plan be developed? [Not answered]
    1. If "yes," what is the planned completion date? [Not answered]
    2. If "no," what is the strategy for managing the risks? [Not answered]
  3. Briefly describe how investment risks are reflected in the life cycle cost estimate and investment schedule: The risks have been taken into consideration in the development of the schedule. Risks are also used in adjusting the lifecycle cost estimate.

Section C: Cost and Schedule Performance (All Capital Assets)

  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%? (CV%= CV/EV x 100; SV%= SV/PV x 100) no
    1. If "yes," was it the? [Not answered]
    2. If "yes," explain the causes of the variance: [Not answered]
    3. If "yes," describe the corrective actions [Not answered]
  3. Has the investment re-baselined during the past fiscal year? yes
    1. If "yes," when was it approved by the agency head? [Not answered]

4. Comparison of Initial Baseline and Current Approved Baseline:

Description of Milestone Initial Baseline Current Baseline Current Baseline Variance  
Planned Completion Date Total Cost ($M) Estimated Completion Date
Planned:Actual		 Total Cost ($M)
Planned:Actual		 Schedule:Cost
(# days:$M)		 Percent Complete
Person Record Management Service (including PIN Re-engineering) Jul 31, 2009 9.5 Jul 31, 2009 [Not answered] 9.5 [Not answered] [Not answered] [Not answered] 0
Integrated Student View (ISV) Dec 11, 2009 6.5 Dec 11, 2009 [Not answered] 6.5 [Not answered] [Not answered] [Not answered] 0
Operational Data Store (ODS) May 22, 2009 4.1 May 22, 2009 [Not answered] 4.1 [Not answered] [Not answered] [Not answered] 0

Return to OMB Exhibit 300 page