# Presentation: 360653

## e-Payroll Status

- January 5, 2004

## Overview

**Project Status **
**High Level Schedule**
**Cost Estimates**
**Key Communication Events**
**Issues/Concerns**
**Recommendations**

## Project Status 

**Data Conversion Activities    **
**NPPS to FPPS Data Conversion and Clean-up**
- NPPS bi-weekly production file transmissions to DOI established since August 2003
- Supports DOI mapping of NPPS to FPPS data elements
- Data mapping and clean-up activities targeted for completion by February 2004
**NPPS Historical Data Conversion (FPPS Data Mart)**
- NASA responsible for data mapping and writing program for converting historical data to FPPS data mart
- 6 years of Payroll data and all HR data (approximately 20 years) to be converted
- Data mapping for NPPS history files approximately 60% complete
**Interface and Reports Development**
**41 Interface Control Documents (ICDs) Under Development**
- ICDs document NPPS to FPPS Data mart mapping for Agency, Common, and Center interface development activities
- ICDs approximately 50% complete
- Targeted for completion by March 2004
**78 Report Control Documents (RCDs) Under Development**
- IPO will provide standard RCDs to be used to capture reporting requirements
- Targeted for completion by March 2004
** **

## Project Status (cont’d)

**Functional Gaps**
**Total gaps reduced from 38 to 22**
- 12 Regulatory
- 10 Business Practice
**Impact Assessments Made by DOI and Initial Change Requests (CRs) Generated**
- Hours to work
- Feasibility of implementing by cut-over
**SSL Requirements**
- High-level requirements load testing conducted mid December 2003
- Agreement from DOI to meet NASA requirements for SSL received late December 2003

## High Level Schedule

**Notes:**
The Summary Status shall be reported for the month.  For purposes of this chart, the “month”, or “M”, is the period between the last MSR and the current MSR.  Please utilize the criteria on this page for reporting summary status.

The intent of this chart is to provide an overall status of the project.

NOTE:  Any red or yellow assessment requires an explanation.

The Integration Project Office (IPO) summary status shall reflect cost/schedule/technical status for each active project.

## Cost Estimate*

**	****	****	****          **_**FY04 Cost Basis**_**	**** ****	****	****	**
**Program (Corporate G&A)****	****	****	****	****   8,441K**
**         ****Civil Servants****	****	****	****994K**
**	****   ****Contractors****	****	****	****             2,072K  **
**	****   ****DOI Conversion Cost****	****          ****	****             2,909K  **
**	****   ****Other (Travel, Training, Reserves)           1,897K****	**
** ****O&SS****	****	****                ****	**** ****	****569K**
**Centers  (Centers G&A)     ****	****	****	****	****  **_**15,778K**_
**	****	**
**TOTAL****	****	****      ****	****	****	****                 24,219K****	****	****            **
***Currently under review by Program Office**

## Key Communication Events 

**November 2003**
**Data calls to Centers for e-Payroll budget submission validation**** **
**December 1 - 3**
**FPPS Training Overview/Approach (provided by DOI staff)**
**Preliminary training schedule completed**
**December 10 - 11**
**Budget Guidance Workshop**
**December 20**
**DOI Management Staff Briefing to e-Payroll Steering Committee **
- Response to functional gaps (see Back-up)
- Workload requirement assessed
- NASA business practice gaps cannot be implemented within planned implementation timeframe (August 8, 2004), due to competing resources required for DOT implementation
- 3 implementation schedule options proposed
- NASA response to DOI regarding “must have” CRs, due January 8
- DOI reassessment of implementation schedule to follow
- Agreement to meet NASA’s requirement for SSL
- DOI follow-up on providing a data mart test environment that can be used by NASA for interface and report development, due January 5 (critical path task)

**Notes:**
Reduces risk of inability to provide inter-agency collaboration where needed
environment challenge of finding resources that can support and upgrade the software products

## Issues/Concerns

- 	** **
**Open Issues**
**FPPS data mart test environment needed for interface and reports development, early January**
- Impacts critical path tasks
- Conducted meetings with DOI for resolution by mid-January
**Decision on “must have” business practice gap resolutions**
- Preliminary assessment made in preparation for response to DOI
- High-impact gaps should be pursued for resolution by cut-over due to unacceptable work-arounds  (2 identified)
- Awards interface (processing of awards in FPPS via batch interface)
- Elimination of printing of gender on the SF-50
-  Determined to be regulatory
**Implementation of Standardized Awards System within the scope of e-Payroll**
- Decision pending completion of business case and DOI’s ability to implement existing CR associated with awards interface
**Concerns**
**Ongoing Legacy System Changes Contend for Resources Needed for E-Payroll Implementation**
- NASA Flexibility Act 2003
- Retroactive Pay Adjustment for annual pay increase
- Changes to Overtime pay rules (exempt employees)
- SES pay changes
**	**

## Recommendations

**Press for resolution of NASA’s “must have” business practice CRs by cut-over**
**2 identified**
** ****Press for adjustment of NASA’s e-Payroll implementation date to March 2005, due to the following:**
**Additional time needed by DOI for resolving “must have” CRs **
**Lack of FPPS data mart test environment for interface and reports development**
**Development of programs to convert historical data to FPPS data mart (previously a DOI task)**
**OPM mandated regulatory changes to NPPS**
**Fiscal year end, pay year end, and pay year begin activities **

## Backup

**	****	****	****	****	**** ****	**
**    ****	****	****	****            **

- BACKUP

## DOI Assessment      (NASA Business Practice Gaps) 

**Notes:**
Reduces risk of inability to provide inter-agency collaboration where needed
environment challenge of finding resources that can support and upgrade the software products

## DOI Assessment     (NASA Business Practice Gaps) 

**Notes:**
Reduces risk of inability to provide inter-agency collaboration where needed
environment challenge of finding resources that can support and upgrade the software products

## DOI Assessment      (NASA Business Practice Gaps) 

**Notes:**
Reduces risk of inability to provide inter-agency collaboration where needed
environment challenge of finding resources that can support and upgrade the software products

## DOI Proposed Implementation Schedule Options 

**	**_**Option**_**	****	**_**NASA**_**	****	**_**DOT**_**	****	**_**FAA**_
**	****Current****	****	****August 04****	****May 04****	****	****October 04**
**	****A****	****	****	****September 04****	****April 05****	****	****October 05**
**	****B****	****	****	****August 04****	****October 04****	****July 05**
**	****C****	****	****	****August 04****	****October 04****	****October 05**
_**Options**_
**	****A – All NASA requirements completed by implementation (September 04)**
**	****B -  NASA business practice requirements completed after implementation (no later than October 05)**
**	****C -  NASA business practice requirements completed by October 05  **
**	**

**Notes:**
Reduces risk of inability to provide inter-agency collaboration where needed
environment challenge of finding resources that can support and upgrade the software products

## Issues Summary

- Data for interfaces must be captured from two different systems.
- More than one system of record.