## NASA E-Payroll {#nasa-e-payroll .sub-heading}

## HR Subgroup Requirements {#hr-subgroup-requirements .sub-heading}

## July 22 - 25, 2003 {#july-22---25-2003 .sub-heading}

##  {#section .sub-heading}

## [Need to include gaps, workarounds, and information on CRs.]{.mark}  {#need-to-include-gaps-workarounds-and-information-on-crs. .sub-heading}

##  {#section-1 .sub-heading}

<table>
<colgroup>
<col style="width: 5%" />
<col style="width: 8%" />
<col style="width: 6%" />
<col style="width: 20%" />
<col style="width: 5%" />
<col style="width: 0%" />
<col style="width: 6%" />
<col style="width: 0%" />
<col style="width: 6%" />
<col style="width: 13%" />
<col style="width: 10%" />
<col style="width: 8%" />
<col style="width: 9%" />
</colgroup>
<thead>
<tr class="header">
<th><h2 id="item-number" class="GIP-HEADING-2">Item<br />
Number</h2></th>
<th><h2 id="processes-item" class="GIP-HEADING-2">Processes/<br />
Item</h2></th>
<th><p><strong>Standardize or</strong></p>
<p><strong>Status Quo</strong></p></th>
<th><strong>Recommendation</strong></th>
<th><strong>NASA Systems Impact</strong></th>
<th colspan="2"><strong>HR/<br />
Payroll Functional Integration</strong></th>
<th colspan="2"><strong>Gap</strong></th>
<th><strong>Comments</strong></th>
<th><strong>Solution/Next Steps</strong></th>
<th><strong>Party Responsible</strong></th>
<th><strong>Status</strong></th>
</tr>
</thead>
<tbody>
<tr class="odd">
<td colspan="13"><p id="general-requirements" class="heading">General
Requirements</p></td>
</tr>
<tr class="even">
<td><h2 id="section-2" class="GIP-HEADING-2">1.</h2></td>
<td><h2 id="sf52s" class="GIP-HEADING-2">SF52s</h2></td>
<td>Standardize</td>
<td><ol type="a">
<li><p>The system shall allow 52s to be used for all processes, other
than Awards and Mass Actions such as: Transfers, Furlough, Perf Ratings,
FEHB, TSP, WIGs, Tenure, and Realignment/Reorganization.</p></li>
<li><p>The system shall print NASA Title and OPM Title on 52s.</p></li>
<li><p>The system shall allow users to be able to pull a NASA title from
a list of NASA title codes. The system shall include a table of NASA
titles based on an associated two-digit title code.</p></li>
</ol>
<blockquote>
<p><strong>Gap</strong>: See DOI Gap 34, 23</p>
<p><strong>Workaround</strong>: NASA will have to manually input this
into organizational title on any new PD after implementation of
FPPS.</p>
<p><strong>CR</strong>: CR has been written and is being reviewed. This
is being included in the Impact Statement being written for the NASA
Classification Code. (9/25/03)</p>
</blockquote></td>
<td>Yes</td>
<td colspan="3">Yes</td>
<td>Yes</td>
<td><ol type="a">
<li><p>SF-52's are not required for all transactions to be processed via
FPPS.</p></li>
<li><p>Use of 52s in Awards system is dependent on Awards system
interface decision.</p></li>
<li><p>FPPS provides the ability to route 52s though HQ for SESs. The
1669 will be a source of data for input into the SF52 process. HR
E-Payroll team worked with HQ to approve this process. Form 1669 will
not be eliminated.</p></li>
<li><p>Both OPM and NASA title need to be printed on 52. FPPS provides
OPM Title and Org title. Org title will be the NASA title, and this
needs to be tied to the NASA title code.</p></li>
</ol></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="odd">
<td><h2 id="section-3" class="GIP-HEADING-2">2. </h2></td>
<td><h2 id="sf50" class="GIP-HEADING-2">SF50</h2></td>
<td>Standardize</td>
<td><ol type="a">
<li><p>The system shall print NASA Title and OPM Title on 50s.</p></li>
<li><p>The system shall not require the completion of Block 25 (gender)
on the 50. The system shall blank or delete the information for Block 25
on the SF50. <strong>Gap</strong>: See DOI Gap 32.</p></li>
</ol>
<blockquote>
<p><strong>Workaround</strong>: Since the system does print gender in
block 25, NASA will white out block 25 on all printed SF50s.</p>
<p><strong>CR</strong>: Terri Robinson is working on the impact
statement. (9/25/03)</p>
</blockquote></td>
<td>Yes</td>
<td colspan="3">No</td>
<td>Yes</td>
<td><ol type="a">
<li><p>Due to FPPS limitations, printing of the Comp level on the 50 has
been dropped as a requirement.</p></li>
<li><p>By using organizational title for the NASA title, both titles
will be able to be printed on the SF50. The resolved a gap between FPPS
and the need to print both titles on the SF50.</p></li>
</ol></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="even">
<td><h2 id="section-4" class="GIP-HEADING-2">3. </h2></td>
<td><h2 id="distributions" class="GIP-HEADING-2">Distributions</h2>
<h2 id="of-paper-50s-52s" class="GIP-HEADING-2">of Paper 50s,
52s</h2></td>
<td>Standardize</td>
<td><ol type="a">
<li><p>The system shall allow for the printing and routing of 52s and
50s to multiple and various printer designations and types.</p></li>
</ol></td>
<td>No</td>
<td colspan="3">No</td>
<td>No</td>
<td><ol type="a">
<li><p>Routing of information is flexible and DOI’s system provides that
capability.</p></li>
<li><p>3 copies of the 50 are automatically printed. One copy of the 52
is automatically printed.</p></li>
</ol></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="odd">
<td><h2 id="section-5" class="GIP-HEADING-2">4. </h2></td>
<td><h2 id="workflow-flexibilities" class="GIP-HEADING-2">Workflow
Flexibilities</h2></td>
<td>Standardize</td>
<td><ol type="a">
<li><p>The system shall allow flexibilities in how work is completed
with each position, from Center to Center, and from process to
process.</p></li>
</ol></td>
<td>No</td>
<td colspan="3">No</td>
<td>No</td>
<td><ol type="a">
<li><p>Documents and actions can be routed across Centers. Routing is
based on security profile.</p></li>
</ol></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="even">
<td><h2 id="section-6" class="GIP-HEADING-2">5. </h2></td>
<td><h2 id="electronic-signatures" class="GIP-HEADING-2">Electronic
Signatures</h2></td>
<td>Standardize</td>
<td><ol type="a">
<li><p>The system shall request, accept, and use electronic signatures
in the 50, 52 processes.</p></li>
</ol></td>
<td>No</td>
<td colspan="3">No</td>
<td>No</td>
<td><ol type="a">
<li><p>DOI has received approval from OPM to use electronic signatures.
(Signatures are based on user access profiles.)</p></li>
</ol></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="odd">
<td><h2 id="section-7" class="GIP-HEADING-2">7. </h2></td>
<td><h2 id="eex" class="GIP-HEADING-2">EEX</h2>
<h2 id="section-8" class="GIP-HEADING-2"></h2></td>
<td>Standardize</td>
<td><ol type="a">
<li><p>The system shall accommodate the use of EEX. NASA will require
mandatory use of EEX for all available functions.</p></li>
</ol></td>
<td>Yes</td>
<td colspan="3">Yes</td>
<td>No</td>
<td><ol type="a">
<li><p>DOI does not use EEX’s capability for W-2s.</p></li>
<li><p>Union issues exist for Ames and Goddard if this is made
mandatory. These issues are being worked at the HQ level.</p></li>
<li><p>NASA will have the option of including TALX in EEX.</p></li>
</ol></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="even">
<td><h2 id="section-9" class="GIP-HEADING-2">10. </h2></td>
<td><h2 id="reporting" class="GIP-HEADING-2">Reporting</h2></td>
<td></td>
<td><ol type="a">
<li><p>The system shall collect data for reporting on total FTE, FTP FTE
information.</p></li>
<li><p>The system shall allow NASA to continue reporting FTE data the
same way it is reported now.</p></li>
</ol></td>
<td>Yes</td>
<td colspan="3">No</td>
<td>No</td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="odd">
<td><h2 id="section-10" class="GIP-HEADING-2"></h2></td>
<td><h2 id="system-accessibility" class="GIP-HEADING-2">System
Accessibility</h2></td>
<td></td>
<td><ol type="a">
<li><p>The FPPS system shall be accessible to both Mac and PC
users.</p></li>
</ol></td>
<td>Yes</td>
<td colspan="3">No</td>
<td>Yes</td>
<td><ol type="a">
<li><p>Citrix may resolve this issue.</p></li>
</ol></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="even">
<td colspan="13"><h2 id="employee-status">Employee Status</h2></td>
</tr>
<tr class="odd">
<td><h2 id="section-11" class="GIP-HEADING-2">11. </h2></td>
<td><h2 id="accessions-process" class="GIP-HEADING-2">Accessions
Process</h2>
<h2 id="section-12" class="GIP-HEADING-2"></h2></td>
<td>Standardize</td>
<td><ol type="a">
<li><p>The system shall accommodate the new NASA Workforce Flexibilities
Act of 2003, such as for Term Appointments where not-to-exceed date can
be 6 years.</p></li>
</ol>
<blockquote>
<p><strong>Gap</strong>: See DOI Gap 43</p>
<p><strong>Workaround</strong>: To be determined, based on legislative
requirements.</p>
<p><strong>CR</strong>: To be determined, based on legislative
requirements.</p>
</blockquote>
<ol start="2" type="a">
<li><p>Pending legislation, the system shall accommodate data elements
and process requirements resulting from the NWFA 2003 for the accessions
and bonuses process.</p></li>
</ol>
<blockquote>
<p><strong>Gap</strong>: See DOI Gap 43</p>
<p><strong>Workaround</strong>: To be determined, based on legislative
requirements.</p>
<p><strong>CR</strong>: To be determined, based on legislative
requirements.</p>
</blockquote>
<h2 id="section-13" class="GIP-HEADING-2"></h2></td>
<td>Yes</td>
<td colspan="2">Yes</td>
<td colspan="2">Yes</td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="even">
<td><h2 id="section-14" class="GIP-HEADING-2">12. </h2></td>
<td><h2 id="federal-service-comp-date" class="GIP-HEADING-2">Federal
Service Comp Date</h2></td>
<td>Standardize</td>
<td><ol type="a">
<li><p>The system shall allow HR, rather than managers, to originate the
change to federal service comp date and print the SF50.</p></li>
</ol></td>
<td>No</td>
<td colspan="2">No</td>
<td colspan="2">No</td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="odd">
<td><h2 id="section-15" class="GIP-HEADING-2">13. </h2></td>
<td><h2 id="inter-center-transfer-process"
class="GIP-HEADING-2">Inter-Center Transfer Process</h2></td>
<td>Standardize</td>
<td><ol type="a">
<li><p>The system shall enable users to move and track an employee from
one Center to another.</p></li>
<li><p>The system shall not require HR to enter an employee into the
system as a new hire when the employee transfers into their Center from
another Center.</p></li>
<li><p>The system shall provide the ability for Centers to know when one
of their employees has left for another Center.</p></li>
</ol>
<blockquote>
<p><strong>Gap</strong>: See DOI Gap 59</p>
<p><strong>Workaround</strong>: A NASA employee with high-level agency
access will provide a query to the Centers. This workaround may be
unacceptable.</p>
<p><strong>CR</strong>: Needs to be written.</p>
</blockquote></td>
<td>Yes</td>
<td colspan="2">Yes</td>
<td colspan="2">Yes</td>
<td><ol type="a">
<li><p>A Tickler Code is generated when a SPO to SPO move happens. The
Tickler Code is sent to the Losing Center.</p></li>
</ol></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="even">
<td><h2 id="section-16" class="GIP-HEADING-2">15. </h2></td>
<td><h2 id="placement-in-non-pay-status" class="GIP-HEADING-2">Placement
in Non-Pay Status</h2></td>
<td>Standardize</td>
<td><ol type="a">
<li><p>The system shall accommodate SF52s originating outside of the HR
office for placement in non-pay status.</p></li>
<li><p>The system shall automatically adjust WIG dates for
LWOP.</p></li>
</ol></td>
<td>Yes</td>
<td colspan="2">Yes</td>
<td colspan="2">No</td>
<td><ol type="a">
<li><p>Most FPPS clients use standard OPM letter that allows employees
to designate what they want to do with health, etc. while on
LWOP.</p></li>
<li><p>If LWOP is over 30 days, both the 52 and 50 are required. If it
is less than 30 days, it is documented in the time-keeping system. This
is the same as the current process.</p></li>
</ol></td>
<td></td>
<td><ol type="a">
<li></li>
</ol></td>
<td></td>
</tr>
<tr class="odd">
<td><h2 id="section-17" class="GIP-HEADING-2">16. </h2></td>
<td><h2 id="return-to-duty" class="GIP-HEADING-2">Return to
Duty</h2></td>
<td>Standardize</td>
<td><ol type="a">
<li><p>The system shall prepare a Tickler report based on a return to
duty date.</p></li>
</ol></td>
<td>No</td>
<td colspan="2">Yes</td>
<td colspan="2">No</td>
<td><ol type="a">
<li><p>FPPS generates all actions on NTE dates that are put into the
systems.</p></li>
<li><p>FPPS automatically generates a 52 to the SPO for that employee.
FPPS automatically moves it into your working queue.</p></li>
</ol></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="even">
<td><h2 id="section-18" class="GIP-HEADING-2">19. </h2></td>
<td><h2 id="termination-by-rif" class="GIP-HEADING-2">Termination by
RIF</h2></td>
<td>Standardize</td>
<td><ol type="a">
<li><p>The system shall generate retention registers with NASA class
code with sort.</p></li>
</ol>
<blockquote>
<p><strong>Gap</strong>: See DOI Gap 35</p>
</blockquote>
<p><strong>Workaround</strong>: NASA will have to produce the retention
register manually.</p>
<blockquote>
<p><strong>CR</strong>: Needs to be written.</p>
</blockquote>
<ol start="2" type="a">
<li><p>The system shall conduct terminations with individual 52s and in
mass.</p></li>
</ol></td>
<td>No</td>
<td colspan="2">No</td>
<td colspan="2">Yes</td>
<td><ol type="a">
<li><p>A BRIO report can be developed to run the register.</p></li>
</ol></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="odd">
<td><h2 id="section-19" class="GIP-HEADING-2">20. </h2></td>
<td><h2 id="resignation-process" class="GIP-HEADING-2">Resignation
Process</h2></td>
<td></td>
<td><ol type="a">
<li><p>The system shall capture a reason for an employee’s resignation
and their departure destination.</p></li>
</ol>
<blockquote>
<p><strong>Gap</strong>: See DOI Gap 13</p>
<p><strong>Workaround</strong>: NASA will use a manual tracking
process.</p>
<p><strong>CR</strong>: Needs to be written.</p>
</blockquote></td>
<td>Yes</td>
<td colspan="2">Yes</td>
<td colspan="2">Yes</td>
<td><ol type="a">
<li><p>DOT submitted an impact statement to add separation codes to
FPPS. NASA will use DOT functionality if it is implemented.</p></li>
</ol></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="even">
<td><h2 id="section-20" class="GIP-HEADING-2">23. </h2></td>
<td><h2 id="expiration-in-term-of-appointment"
class="GIP-HEADING-2">Expiration in Term of Appointment </h2></td>
<td>Standardize</td>
<td><ol type="a">
<li><p>The system shall generate an action automatically based on a
not-to-exceed date of temp appointment.</p></li>
</ol></td>
<td>No</td>
<td colspan="2">Yes</td>
<td colspan="2">No</td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="odd">
<td><h2 id="section-21" class="GIP-HEADING-2">24. </h2></td>
<td><h2 id="co-op-tracking-process" class="GIP-HEADING-2">Co-op Tracking
Process</h2></td>
<td>Standardize</td>
<td><ol type="a">
<li><p>The system shall allow Centers using co-op fields to track return
to duty date and return to school date.</p></li>
<li><p>The system shall allow Centers using co-op fields to track future
year of degree and allow the degree year to be greater than the current
education year.</p></li>
</ol>
<blockquote>
<p><strong>Gap</strong>: See DOI Gap 15, 24</p>
<p><strong>Workaround</strong>: Create an agency unique sub-system or a
manual tracking system.</p>
<p><strong>CR</strong>: A CR requiring these changes was written and
submitted by Dept of Education. The original CR submitted by DOE did not
meet all of NASA’s criteria. An amendment to allow use of the fourth
educational data field needs to be written.</p>
</blockquote>
<ol start="3" type="a">
<li><p>The system shall provide the ability to identify co-op
conversions uniquely against NASA accepteds.</p></li>
</ol></td>
<td>Yes</td>
<td colspan="2">Yes</td>
<td colspan="2">Yes</td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="even">
<td><h2 id="section-22" class="GIP-HEADING-2">25. </h2></td>
<td><h2 id="change-in-tenure-process" class="GIP-HEADING-2">Change in
Tenure Process</h2></td>
<td>Standardize</td>
<td><ol type="a">
<li><p>The system shall automatically generate tenure actions.</p></li>
</ol></td>
<td>No</td>
<td colspan="2">No</td>
<td colspan="2">No</td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="odd">
<td><h2 id="section-23" class="GIP-HEADING-2">26. </h2></td>
<td><h2 id="accessions-of-non-paid-employees"
class="GIP-HEADING-2">Accessions of Non-Paid Employees</h2></td>
<td>Standardize</td>
<td><ol type="a">
<li><p>The system shall be capable of tracking non-paid employees in the
system, using an accessions process. (Fund Source 41 IPA’s)</p></li>
</ol>
<blockquote>
<p><strong>Gap</strong>: See DOI Gap 49</p>
<p><strong>Workaround</strong>: NASA will need to develop an agency
specific system</p>
<p><strong>CR</strong>: This has been written and includes regulatory
requirements.</p>
</blockquote></td>
<td>Yes</td>
<td colspan="2">No</td>
<td colspan="2">Yes</td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="even">
<td><h2 id="section-24" class="GIP-HEADING-2">28. </h2></td>
<td><h2 id="npps-cancellation-and-corrections"
class="GIP-HEADING-2">NPPS Cancellation and Corrections</h2></td>
<td>Do Not Standardize</td>
<td><ol type="a">
<li><p>The system shall provide the option to correct the last action or
to go back to original transaction to correct the error, per GPPS. (The
GPPS allows this to happen either way.)</p></li>
</ol></td>
<td>Yes</td>
<td colspan="2">Yes</td>
<td colspan="2">No</td>
<td><ol type="a">
<li><p>SF50 is required to be sent to DOI for pay corrections to actions
outside of FPPS.</p></li>
</ol></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="odd">
<td><h2 id="section-25" class="GIP-HEADING-2">30. </h2></td>
<td><h2 id="name-change-process" class="GIP-HEADING-2">Name Change
Process</h2></td>
<td>Standardize</td>
<td><ol type="a">
<li><p>The system shall require that names be entered and used as they
appear on the social security card.</p></li>
<li><p>The system shall allow users to leave the middle name field blank
if the employee does not have a middle name.</p></li>
<li><p>The system shall convert anyone who has NMN or NMI to “blank” in
FPPS.</p></li>
</ol></td>
<td>No</td>
<td colspan="2">No</td>
<td colspan="2">No</td>
<td><ol type="a">
<li><p>Middle initials and middle names can be included in
FPPS.</p></li>
</ol></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="even">
<td colspan="13"><h2 id="benefits">Benefits</h2></td>
</tr>
<tr class="odd">
<td><h2 id="section-26" class="GIP-HEADING-2">31. </h2></td>
<td><h2 id="thrift-savings-plan" class="GIP-HEADING-2">Thrift Savings
Plan</h2></td>
<td>Standardize</td>
<td><ol type="a">
<li><p>The system shall accommodate the use of EEX. NASA will require
mandatory use of EEX, when possible.</p></li>
<li><p>The system shall allow BRIO reports to be created to identify
employees who are newly eligible to participate in open season.</p></li>
</ol></td>
<td>Yes</td>
<td colspan="2">Yes</td>
<td colspan="2">No</td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="even">
<td><h2 id="section-27" class="GIP-HEADING-2">32. </h2></td>
<td><h2 id="leave" class="GIP-HEADING-2">Leave</h2></td>
<td>Payroll Requirement</td>
<td><ol type="a">
<li><p>The system shall track leave.</p></li>
<li><p>The system shall accommodate exceptions for individual employees
that should not receive advance leave.</p></li>
</ol>
<blockquote>
<p><strong>Gap:</strong> See DOI Gap 5.</p>
<p><strong>Workaround:</strong> NASA to send POD memo to reduce
available advance sick leave balance. NASA will have to track this
manually<strong>.</strong></p>
<p><strong>CR:</strong> None.</p>
</blockquote></td>
<td>No</td>
<td colspan="2">Yes</td>
<td colspan="2">Yes</td>
<td><ol type="a">
<li><p>This needs to be included in the Payroll list of requirements.
(See DOI Gap 5)</p></li>
</ol></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="odd">
<td><h2 id="section-28" class="GIP-HEADING-2">33. </h2></td>
<td><h2 id="physicians-comparability-allowance-process"
class="GIP-HEADING-2">Physician’s Comparability Allowance
Process</h2></td>
<td>Standardize</td>
<td><ol type="a">
<li><p>The system shall be able to pay PCA by both percentage and flat
rate.</p></li>
</ol>
<blockquote>
<p><strong>Gap</strong>: FPPS does not process PCA by percentage. See
DOI Gap 58</p>
<p><strong>Workaround</strong>: KSC will convert PCA percentages to flat
rates.</p>
<p><strong>CR</strong>: None required.</p>
</blockquote></td>
<td>Yes</td>
<td colspan="2">Yes</td>
<td colspan="2">No</td>
<td>FPPS does not carry PCA percentages.</td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="even">
<td><h2 id="section-29" class="GIP-HEADING-2">34. </h2></td>
<td><h2 id="federal-employee-health-benefits-fehb"
class="GIP-HEADING-2">Federal Employee Health Benefits (FEHB)</h2></td>
<td>Standardize</td>
<td><ol type="a">
<li><p>The system shall accommodate the use of EEX. NASA will require
mandatory use of EEX, when possible.</p></li>
<li><p>The system shall accommodate the continued use of manual
processes for some activities.</p></li>
</ol></td>
<td>No</td>
<td colspan="2">Yes</td>
<td colspan="2">No</td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="odd">
<td><h2 id="section-30" class="GIP-HEADING-2">35. </h2></td>
<td><h2 id="home-marketing-incentive-hmi" class="GIP-HEADING-2">Home
Marketing Incentive (HMI)</h2></td>
<td>Standardize – Process belongs to Payroll.</td>
<td><ol type="a">
<li><p>The system shall process HMI through the Central Travel Office
(CTO) not NPPS/FPPS.</p></li>
</ol>
<blockquote>
<p><strong>Gap</strong>: FPPS is not capable of processing HMI.</p>
<p><strong>Workaround</strong>: This gap was resolved by processing HMI
through CTO.</p>
<p><strong>CR</strong>: None required.</p>
</blockquote></td>
<td>Yes</td>
<td colspan="2">Yes</td>
<td colspan="2">No</td>
<td><ol type="a">
<li><p>Two options for ensuring the system provided the capability to
pay Home Marketing Incentives were explored. The two options were:
Option 1: Submit a CR to DOI to add a NASA specific nature of action
code (NOAC). Option 2: Pay through IFM with JSC developing an interface
(W-2 required for either option).</p></li>
<li><p>There is a gap between this process and SAP process
workflows.</p></li>
</ol></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="even">
<td colspan="13"><h2 id="performance">Performance</h2></td>
</tr>
<tr class="odd">
<td><h2 id="section-31" class="GIP-HEADING-2">37. </h2></td>
<td><h2 id="performance-data-process" class="GIP-HEADING-2">Performance
Data Process</h2></td>
<td>Standardize</td>
<td><ol type="a">
<li><p>The system shall allow performance ratings to be input into it
through mass actions by organization.</p></li>
<li><p>The system shall automatically generate the rating of record. For
those automatically generated, the system shall generate a “3” into the
system. The system shall allow every Center to choose their own
effective date. Exceptions will be changed on an individual basis
(SESs).</p></li>
</ol>
<blockquote>
<p><strong>Gap</strong>: See DOI Gap 16.</p>
</blockquote>
<p><strong>Workaround</strong>: Option 1: Develop a BRIO query to build
a flat file that can be uploaded to FPPS. Option 2:Another possible
change is to use DOI mass change. (This will not require a CR.)</p>
<blockquote>
<p><strong>CR</strong>: A CR will be required for option 1.</p>
</blockquote></td>
<td>Yes</td>
<td colspan="2">No</td>
<td colspan="2">Yes</td>
<td><ol type="a">
<li><p>Performance patterns used: A and H. H is used for SESs. Levels
used for H are 1-5. A is used for everyone else. Levels used for pattern
as are 1, 3.</p></li>
<li><p>NASA has authorization to use all other performance patterns
(i.e., b, c, d, e, f, g).</p></li>
<li><p>Automated process does not cover SESs.</p></li>
<li><p>Process is standardized on rating update annually based on last
performance rating effective date.</p></li>
</ol></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="even">
<td colspan="13"><h2
id="nasa-unique-transactions-and-data-elements">NASA Unique Transactions
and Data Elements</h2></td>
</tr>
<tr class="odd">
<td><h2 id="section-32" class="GIP-HEADING-2">38. </h2></td>
<td><h2 id="nasa-unique-transaction-codes" class="GIP-HEADING-2">NASA
Unique Transaction Codes</h2>
<h2 id="noac" class="GIP-HEADING-2">(NOAC)</h2></td>
<td>Standardize</td>
<td><ol type="a">
<li><p>The system shall provide a consistent approach for documenting
details related to transactions.</p></li>
<li><p>The system shall use standard NOACs. A sample of current NOACs
used are 920, 925, 930C or 930U, 931, 932, 939, and 991.</p></li>
<li><p>The system shall provide flexibility to process an individual
type of NOAC with or without a 52 and to print the 52 when needed. The
system shall use the 52 as the standard to print and file
details.</p></li>
<li><p>The system shall accept approval signatures, but the system shall
not require approval signatures.</p></li>
<li><p>The system shall allow it to vary from NOAC to NOAC as to whether
or not a 52 is required.</p></li>
<li><p>The system shall include NASA-specific NOACs: 987,988,
989.</p></li>
</ol>
<blockquote>
<p><strong>Gap</strong>: See DOI Gap 65.</p>
<p><strong>Workaround</strong>: None.</p>
<p><strong>CR</strong>: Impact statement has been written.</p>
</blockquote></td>
<td>Yes</td>
<td colspan="2">Varies from NOAC to NOAC</td>
<td colspan="2">Yes</td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="even">
<td><h2 id="section-33" class="GIP-HEADING-2">39. </h2></td>
<td><h2 id="tickler-dates-process" class="GIP-HEADING-2">Tickler Dates
Process</h2></td>
<td>Standardize</td>
<td><ol type="a">
<li><p>The system shall retain current Tickler fields and
dates.</p></li>
<li><p>The system shall retain data for the current Tickler fields and
dates.</p></li>
<li><p>The system shall offer the same ticklers and tickler dates as
those currently used. Specific ticklers include: Follow up code,
details, appt, LWOP.</p></li>
</ol>
<blockquote>
<p><strong>Gap</strong>: Closed.</p>
<p><strong>Workaround</strong>: Cetners have agreed to use current FPPS
capabilities.</p>
<p><strong>CR</strong>: None required.</p>
</blockquote>
<ol start="4" type="a">
<li><p>The system shall include “Service Agreement Dates” as a Tickler.
Examples of required service agreement level dates include: retention
bonus, relocation bonus, Redesignation bonus, and student
loans.</p></li>
</ol>
<blockquote>
<p><strong>Gap</strong>: See DOI Gap 64</p>
<p><strong>Workaround</strong>: This information will have to be tracked
manually.</p>
<p><strong>CR</strong>: An impact statement has been</p>
</blockquote>
<p>The system shall include a tickler for PCA.</p>
<blockquote>
<p><strong>Gap</strong>: See DOI Gap 64.</p>
<p><strong>Workaround</strong>: This information will have to be tracked
manually.</p>
<p><strong>CR</strong>: An impact statement has been written.</p>
</blockquote></td>
<td>No</td>
<td colspan="2">No</td>
<td colspan="2">Yes</td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="odd">
<td><h2 id="section-34" class="GIP-HEADING-2"><mark>40.</mark></h2></td>
<td><h2 id="nasa-unique-data-elements" class="GIP-HEADING-2"><mark>NASA
Unique Data Elements</mark></h2></td>
<td><mark>Standardize</mark></td>
<td><ol type="a">
<li><p><mark>The system shall accommodate NASA unique data elements such
as duty status, employee number, pos type, NASA SCD, admin level,
etc.</mark></p></li>
<li><p><mark>The system shall maintain NASA unique fields where values
are Center unique. Centers use different values. (See Req
#12)</mark></p></li>
<li><p><mark>The system shall make available for use Employee
Number.</mark></p></li>
<li><p><mark>The system shall provide the NASA class code and NASA title
on the FPPS position screen.</mark></p></li>
<li><p><mark>The system shall provide a non-pay indicator field or
“employee indicator” field</mark></p></li>
<li><p><mark>The system shall enable NASA to get a transaction that
creates a profile for a person that is set through a non-pay
status.</mark></p></li>
<li><p><mark>The system shall store UUPIC numbers. This is a 9-character
field. (Gap)</mark></p></li>
</ol>
<p><mark></mark></p></td>
<td><mark>Yes</mark></td>
<td colspan="2"><mark>Yes</mark></td>
<td colspan="2"><mark>Yes</mark></td>
<td><ol type="a">
<li><p><mark><del>Teresa’s work will help to identify these data
elements.</del></mark></p></li>
<li><p><mark><del>Award Budget Code Field is used in NPPS. One Center
would like to use FPPS field “Cost Center”.</del></mark></p></li>
<li><p><mark><del>Centers use Employee Number in NPPS for local systems
to avoid use of social security number.</del></mark></p></li>
<li><p><mark><del>Employee number is used by the job labor system. If no
employee number is used, employees will not get
paid.</del></mark></p></li>
<li><p><mark>Employee number is used to log into TSC.</mark></p></li>
<li><p><mark>PDM automatically generates numbers.</mark></p></li>
<li><p><mark><del>Drug testing program codes have been provided to
DOI.</del></mark></p></li>
</ol></td>
<td><ol type="a">
<li><p><mark><del>Review information received from Teresa’s
group.</del></mark></p></li>
<li><p><mark><del>Review unique fields and identify what information
needs to be retained.</del></mark></p></li>
<li><p><mark><del>Determine if it is possible to use FPPS field “Cost
Center”.</del></mark></p></li>
</ol>
<p><mark></mark></p></td>
<td><ol type="a">
<li><p><mark><del>NASA HR</del></mark></p></li>
</ol></td>
<td><mark></mark></td>
</tr>
<tr class="even">
<td><h2 id="section-35" class="GIP-HEADING-2"></h2></td>
<td><h2 id="date-of-current-grade" class="GIP-HEADING-2">Date of Current
Grade</h2></td>
<td></td>
<td><ol type="a">
<li><p>Users need to be able to use the date an individual entered a
current grade in the “date position established” field.</p></li>
</ol>
<blockquote>
<p><strong>Gap</strong>: See DOI Gap 70</p>
<p><strong>Workaround</strong>: Investigating the possibility of using
date position established.</p>
<p><strong>CR</strong>: It is to be determined whether a CR and impact
statement are needed.</p>
</blockquote></td>
<td>No</td>
<td colspan="2">Yes</td>
<td colspan="2">Yes</td>
<td><ol type="a">
<li><p>“Date position established” is a conversion issue.</p></li>
<li><p>Date of current grade is a computed date.</p></li>
</ol></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="odd">
<td><h2 id="section-36" class="GIP-HEADING-2"></h2></td>
<td><h2 id="position-type" class="GIP-HEADING-2">Position Type</h2></td>
<td></td>
<td><ol type="a">
<li><p>The system shall provide the capability to distinguish employee
type indicated by NASA data element position type.</p></li>
</ol>
<blockquote>
<p><strong>Gap</strong>: See DOI Gap 38</p>
<p><strong>Workaround</strong>: NASA will use the FPPS special program
identifier (SPID). NASA additions to current FPPS SPID table will be
sent to DOI.</p>
<p><strong>CR</strong>: None needed.</p>
</blockquote></td>
<td>?</td>
<td colspan="2">?</td>
<td colspan="2">?</td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="even">
<td><h2 id="section-37" class="GIP-HEADING-2"></h2></td>
<td><h2 id="fte-line-item" class="GIP-HEADING-2">FTE Line Item</h2></td>
<td></td>
<td><ol type="a">
<li><p>The system shall store and retrieve FTE line item
information.</p></li>
</ol>
<blockquote>
<p><strong>Gap</strong>: See DOI Gap 51</p>
<p><strong>Workaround</strong>: Call FPPS help desk to have them resolve
a line item on the 113G.</p>
<p><strong>CR</strong>: None needed.</p>
</blockquote></td>
<td>No</td>
<td colspan="2">No</td>
<td colspan="2">No</td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="odd">
<td><h2 id="section-38" class="GIP-HEADING-2"></h2></td>
<td><h2 id="position-description" class="GIP-HEADING-2">Position
Description </h2></td>
<td></td>
<td><ol type="a">
<li><p>The system shall allow a vacant position to be retained.</p></li>
</ol></td>
<td>Yes</td>
<td colspan="2">No</td>
<td colspan="2">No</td>
<td><ol type="a">
<li><p>Type an “R” to retain a position number on a vacant position
description.</p></li>
</ol></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="even">
<td><h2 id="section-39" class="GIP-HEADING-2"></h2></td>
<td><h2 id="educational-data" class="GIP-HEADING-2">Educational
Data</h2></td>
<td></td>
<td><ol type="a">
<li><p>The system shall provide the ability to capture up to four
instances of educational data that includes degree level, school,
academic discipline, and GPA.</p></li>
</ol>
<blockquote>
<p><strong>Gap</strong>: See DOI Gap 24</p>
<p><strong>Workaround</strong>: Create an agency unique sub-system or a
manual tracking system.</p>
<p><strong>CR</strong>: A CR requiring these changes was written and
submitted by Dept of Education. NASA is waiting on approval of this
CR.</p>
</blockquote></td>
<td>?</td>
<td colspan="2">?</td>
<td colspan="2">?</td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="odd">
<td colspan="13"><h2 id="pay-elements">Pay Elements</h2></td>
</tr>
<tr class="even">
<td><h2 id="section-40" class="GIP-HEADING-2">41. </h2></td>
<td><h2 id="wig-process" class="GIP-HEADING-2">WIG Process</h2></td>
<td>Standardize</td>
<td><ol type="a">
<li><p>The system shall automatically reset WIG Due Dates and erase
excess LWOP records.</p></li>
<li><p>The system shall automatically generate within-grade
actions.</p></li>
<li><p>The system shall provide a report that lists employees with LWOP
or excess LWOP, or those who are getting or should get a WIG.</p></li>
<li><p>The system shall include the notice to supervisors as an optional
feature, not a mandatory feature.</p></li>
<li><p>The system shall allow two Centers to send WIG notices to
Supervisors.</p></li>
<li><p>The system shall allow NASA to store the date of the next within
grade increase.</p></li>
</ol>
<blockquote>
<p><strong>Gap</strong>: See DOI Gap 14</p>
<p><strong>Workaround</strong>: NASA will run a report of the data
needed from the datamart.</p>
<p><strong>CR</strong>: A CR is being written. If NASA does not get this
change to the system, an agency solution will have to be programmed to
support NEBs.</p>
</blockquote></td>
<td colspan="2">Yes</td>
<td>No</td>
<td colspan="2">Yes</td>
<td><ol type="a">
<li><p>FPPS stores the date of the last increase, not the projected
WIG.</p></li>
<li><p>Electronic WIG notification is generated 7 pay periods in
advance. These are forwarded to approving managers. A denial
automatically generates an 888 Denial.</p></li>
</ol></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="odd">
<td><h2 id="section-41" class="GIP-HEADING-2">44. </h2></td>
<td><h2 id="pay-changes-process-quality-step-increase"
class="GIP-HEADING-2">Pay Changes Process: Quality Step
Increase</h2></td>
<td>Standardize</td>
<td><ol type="a">
<li><p>If there is an Awards Interface, the system shall have the
capability to handle QSI through that interface rather than the 52
process.</p></li>
</ol>
<blockquote>
<p><strong>Gap</strong>:</p>
<p><strong>Workaround</strong>:</p>
<p><strong>CR</strong>:</p>
</blockquote></td>
<td colspan="2">?</td>
<td>No</td>
<td colspan="2">Yes</td>
<td><ol type="a">
<li><p>Use SF52s to request and justify QSI. Capture information in
notes section of SF52.</p></li>
</ol></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="even">
<td><h2 id="section-42" class="GIP-HEADING-2">45. </h2></td>
<td><h2 id="mass-pay-increase" class="GIP-HEADING-2">Mass Pay
Increase</h2></td>
<td>Standardize</td>
<td><ol type="a">
<li><p>The system shall processes Mass Pay Increase actions.</p></li>
<li><p>The system shall generate a 52 for reemployed annuitant, retained
pay, AD, SL, ST, CA. SPO will have to input the salary.</p></li>
<li><p>For retained pay, the system shall generate them automatically,
but the system shall require NASA HR to approve them.</p></li>
</ol></td>
<td colspan="2">Yes</td>
<td>No</td>
<td colspan="2">No</td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="odd">
<td><h2 id="section-43" class="GIP-HEADING-2">47.</h2></td>
<td><h2 id="allowances-and-differentials"
class="GIP-HEADING-2">Allowances and Differentials</h2></td>
<td>Standardize</td>
<td><ol type="a">
<li><p><em>Note</em>: FPPS processes allowance and differentials as
listed in Chapter 17 of the Guide to Processing Personnel
Actions.</p></li>
</ol></td>
<td colspan="2">No</td>
<td>No</td>
<td colspan="2">No</td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="even">
<td><h2 id="section-44" class="GIP-HEADING-2 unnumbered">48.</h2></td>
<td><h2 id="pay-for-critical-positions"
class="GIP-HEADING-2 unnumbered">Pay for Critical Positions</h2></td>
<td>Standardize</td>
<td><ol type="a">
<li><p>The system shall accommodate the NASA Workplace Flexibilities Act
2003.</p></li>
</ol>
<blockquote>
<p><strong>Gap</strong>:</p>
<p><strong>Workaround</strong>:</p>
<p><strong>CR</strong>:</p>
</blockquote>
<ol start="2" type="a">
<li><p>The system shall be able to grant to 10 employees’ pay levels
equivalent to that of the VP of the USA.</p></li>
</ol>
<blockquote>
<p><strong>Gap</strong>:</p>
<p><strong>Workaround</strong>: NASA will have to create a manual
adjustment to??</p>
<p><strong>CR</strong>: A CR will be written once the legislation
passes.</p>
</blockquote></td>
<td colspan="2">Yes</td>
<td>Yes</td>
<td colspan="2">Yes</td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="odd">
<td><h2 id="section-45" class="GIP-HEADING-2">49. </h2></td>
<td><h2 id="competitive-promotions-and-reassignments"
class="GIP-HEADING-2">Competitive Promotions and Reassignments</h2></td>
<td>Standardize</td>
<td><ol type="a">
<li></li>
</ol></td>
<td colspan="2">No</td>
<td>No</td>
<td colspan="2">No</td>
<td><ol type="a">
<li></li>
</ol></td>
<td><ol type="a">
<li><p>.</p></li>
</ol></td>
<td></td>
<td></td>
</tr>
<tr class="even">
<td colspan="13"><h2 id="bonus-and-awards">Bonus and Awards</h2></td>
</tr>
<tr class="odd">
<td><h2 id="section-46" class="GIP-HEADING-2"><mark>51.</mark>
</h2></td>
<td><h2 id="awards-process" class="GIP-HEADING-2"><mark>Awards
Process</mark></h2></td>
<td><mark>Standardize</mark></td>
<td><ol type="a">
<li><p><mark>The system shall process OPM award actions and NASA unique
award actions. (See “NASA Unique Transaction Codes”, or
NOACs)</mark></p></li>
<li><p><mark>The system shall process monetary and non-monetary
awards.</mark></p></li>
<li><p><mark>The system shall accommodate NASA award data fields such as
award type and retain this information in the Personnel Master records.
(See “NASA Unique Data Elements”)</mark></p></li>
<li><p><mark>The system shall provide a Mass Awards
capability.</mark></p></li>
<li><p><mark>The system shall accommodate NASA awards reporting
requirements. The system shall provide agency reporting where data is
captured and presented in a consistent format.</mark></p></li>
</ol></td>
<td><mark>Yes</mark></td>
<td colspan="2"><mark>Yes</mark></td>
<td colspan="2"><mark>Yes</mark></td>
<td><ol type="a">
<li><p><mark>All data currently is not captured in a consistent
format.</mark></p></li>
<li><p><mark>Use 52 notes section to distinguish awards and to capture
additional information.</mark></p></li>
</ol></td>
<td><ol type="a">
<li><p><mark><del>l</del></mark></p></li>
</ol></td>
<td><ol type="a">
<li><p><mark><del>Reporting requirements: HQ,
Centers.</del></mark></p></li>
</ol></td>
<td><mark></mark></td>
</tr>
<tr class="even">
<td><h2 id="section-47" class="GIP-HEADING-2"></h2></td>
<td><h2 id="awards-system" class="GIP-HEADING-2">Awards System</h2></td>
<td>Standardize</td>
<td><ol type="a">
<li><p>If one Awards system is not implemented, they system shall handle
multiple Awards interfaces.</p></li>
<li><p>The ICB Awards shall require an interface with the FPPS system,
regardless of whether or not one, multiple, or no Awards systems are
interfaced with FPPS. Note: ICB Awards could use the same format as that
used by others.</p></li>
<li><p>The system shall provide a streamlined process for entering
future awards data, if possible. Option 1: Create an interface with FPPS
with required awards data that has been identified by Mike Hill. Option
2: Manually input all awards.</p></li>
</ol>
<blockquote>
<p><strong>Gap</strong>:</p>
<p><strong>Workaround</strong>:</p>
<p><strong>CR</strong>:</p>
</blockquote></td>
<td>Yes</td>
<td colspan="3">Yes</td>
<td>Yes</td>
<td><ol type="a">
<li><p>If DOI is able to establish an awards interface, than the
interface to FPPS will have to include awards cost elements.</p></li>
<li><p>Consider implementing one Agency Awards System</p></li>
</ol></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="odd">
<td><h2 id="section-48" class="GIP-HEADING-2">52. </h2></td>
<td><h2 id="inventions-and-contributions-awards-process"
class="GIP-HEADING-2">Inventions and Contributions Awards
Process</h2></td>
<td>Standardize</td>
<td><ol type="a">
<li><p>The system shall be automatically updated with awards
information.</p></li>
<li><p>The system shall automatically send email notifications to
personnel offices.</p></li>
<li><p>The system shall automatically maintain a history file.</p></li>
<li><p>The system shall provide Center-specific reports.</p></li>
<li><p>The system shall interface with ICB. (See Item 8.)</p></li>
<li><p>The system shall interface awards data with the TechTrac system.
(This is related to action item #33.)</p></li>
</ol>
<blockquote>
<p><strong>Gap</strong>:</p>
<p><strong>Workaround</strong>:</p>
<p><strong>CR</strong>:</p>
</blockquote></td>
<td>Yes</td>
<td colspan="2">Yes</td>
<td colspan="2">Yes</td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="even">
<td><h2 id="section-49" class="GIP-HEADING-2">53. </h2></td>
<td><h2 id="bonus" class="GIP-HEADING-2">Bonus </h2></td>
<td>Standardize</td>
<td><ol type="a">
<li><p>The system shall accommodate all bonuses listed in Chapter
29.</p></li>
</ol></td>
<td>No</td>
<td colspan="2">Yes</td>
<td colspan="2">No</td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="odd">
<td><h2 id="section-50" class="GIP-HEADING-2">54. </h2></td>
<td><h2 id="ses-bonus-process" class="GIP-HEADING-2">SES Bonus
Process</h2></td>
<td>Standardize</td>
<td><ol type="a">
<li><p>The system shall accept SES Bonus actions through the Awards
Interface. (Wait for decision on Awards System.) (Gap – See HR
Req-1)</p></li>
<li><p>The system shall allow HR to originate these actions. Different
routing actions will be needed depending on the dollar amount of the
bonus. (Wait for decision on Awards System.) (Gap – See HR
Req-1)</p></li>
</ol></td>
<td>Yes</td>
<td colspan="2">No</td>
<td colspan="2">Yes</td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
</tbody>
</table>

  ---------------------- ------- -------------- -------- ---------- --------- ------- -------- ---------- ---------- --------- -------------
  **e-PAYROLL CONCEPT OF                                                                                                       
  FUTURE OPERATIONS (HR                                                                                                        
  PROCESS)**                                                                                                                   

  ** **                  ** **   ** **          **\"AS   ** **      ** **             ** **    ** **      **\"TO     ** **     ** **
                                                IS\"**                                                    BE\"**               

  **PROCESS**                    **Initiating   **HR**   **Center   **CPO**           **RO**   **HR       **Center   **LPO**   **NBC/POD**
                                 Office**                PR**                                  (Center    PR**                 
                                                                                               SPO)**                          

  **General                                                                                                                     
  Requirements**                                                                                                               

  **SF52s**              ** **   **X**          **X**    ** **      ** **     ** **   **X**    **X**      ** **      ** **     ** **

  **SF50**               ** **   ** **          **X**    ** **      ** **     ** **   ** **    **X**      ** **      ** **     **X**

  **Distributions of     ** **   **X**          **X**    **X**      **X**     ** **   **X**    **X**      ** **      ** **     **X**
  Paper 50s, 52s**                                                                                                             

  **Electronic Route     ** **   ** **          ** **    ** **      ** **     ** **   **X**    **X**      ** **      ** **     **X**
  Paths**                                                                                                                      

  **Electronic           ** **   ** **          ** **    ** **      ** **     ** **   **X**    **X**      ** **      ** **     ** **
  Signatures**                                                                                                                 

  **EEX**                ** **   ** **          **X**    **X**      **X**     ** **   ** **    **X**      ** **      ** **     **X**

  **Reporting**          ** **   ** **          **X**    ** **      ** **     ** **   ** **    **X**      ** **      ** **     ** **

  **Employee Status**                           ** **    ** **      ** **     ** **            ** **      ** **      ** **     ** **

  **Accessions Process**         **X**          **X**    **X**      **X**     ** **   **X**    **X**      **X**      ** **     **X**

  **Federal Service Comp         ** **          **X**    ** **      ** **     ** **   ** **    **X**      ** **      ** **     ** **
  Date**                                                                                                                       

  **Inter-Center                 **X**          **X**    **X**      **X**     ** **   **X**    **X**      ** **      ** **     **X**
  Transfer Process**                                                                                                           

  **Placement in Non-Pay         **X**          **X**    **X**      **X**     ** **   **X**    **X**      ** **      ** **     **X**
  Status**                                                                                                                     

  **Return to Duty**             **X**          **X**    **X**      ** **     ** **   **X**    **X**      **X**      ** **     ** **

  **Termination by RIF**         ** **          **X**    ** **      ** **     ** **   ** **    **X**      ** **      ** **     **X**

  **Resignation                  **X**          **X**    **X**      **X**     ** **   **X**    **X**      **X**      ** **     **X**
  Process**                                                                                                                    

  **Departure                    **X**          **X**    ** **      ** **     ** **   ** **    **Future   ** **      ** **     ** **
  Reason/Destination**                                                                         CR**                            

  **Expiration in Term           ** **          **X**    **X**      **X**     ** **   ** **    **X**      ** **      ** **     ** **
  of Appointment**                                                                                                             

  **Co-op Tracking               ** **          **X**    ** **      ** **     ** **   ** **    **X**      ** **      ** **     ** **
  Process**                                                                                                                    

  **Change in Tenure             ** **          **X**    ** **      ** **     ** **   ** **    **X**      ** **      ** **     ** **
  Process**                                                                                                                    

  **Accessions of                **X**          **X**    ** **      ** **     ** **            **X**      ** **      ** **     ** **
  Non-Paid Employees**                                                                                                         

  **Cancellation and             ** **          **X**    **X**      **X**     ** **   ** **    **X**      ** **      **X**     **X**
  Corrections**                                                                                                                

  **Name Change                  ** **          **X**    ** **      ** **     ** **   ** **    **X**      ** **      ** **     ** **
  Process**                                                                                                                    

  **Benefits**                                  ** **    ** **      ** **     ** **            ** **      ** **      ** **     ** **

  **Thrift Savings       ** **   ** **          **X**    **X**      **X**     ** **   ** **    **X**      **X**      ** **     **X**
  Plan**                                                                                                                       

  **Leave**              ** **   **X**          **X**    **X**      **X**     ** **   **X**    **X**      ** **      ** **     **X**

  **Physician's          ** **   ** **          **X**    **X**      **X**     ** **   ** **    **X**      ** **      ** **     **X**
  Comparability                                                                                                                
  Allowance Process**                                                                                                          

  **Federal Employee     ** **   ** **          **X**    **X**      **X**     ** **   ** **    **X**      ** **      ** **     **X**
  Health Benefits                                                                                                              
  (FEHB)**                                                                                                                     

  **Home Marketing       ** **   ** **          **X**    ** **      ** **     ** **   ** **    **X**      ** **      ** **     ** **
  Incentive (HMI)**                                                                                                            

  **Performance:**                              ** **    ** **      ** **     ** **            ** **      ** **      ** **     ** **

  **Performance Data     ** **   ** **          **X**    ** **      ** **     ** **   ** **    **X**      ** **      ** **     ** **
  Process**                                                                                                                    

  **NASA Unique          ** **   ** **          ** **    ** **      ** **     ** **   ** **    ** **      ** **      ** **     ** **
  Transactions and Data                                                                                                        
  Elements**                                                                                                                   

  **NASA Unique          ** **   **X**          **X**    ** **      ** **     ** **   **X**    **X**      ** **      ** **     ** **
  Transaction Codes                                                                                                            
  (NOAC)**                                                                                                                     

  **Tickler Dates        ** **   ** **          ** **    ** **      ** **     ** **   **X**    **X**      ** **      ** **     ** **
  Process**                                                                                                                    

  **NASA Unique Data     ** **   ** **          **X**    ** **      ** **     ** **   ** **    **X**      ** **      ** **     ** **
  Elements**                                                                                                                   

  **Date of Current      ** **   ** **          **X**    ** **      ** **     ** **   ** **    ** **      ** **      ** **     ** **
  Grade**                                                                                                                      

  **Position Type**      ** **   ** **          **X**    ** **      ** **     ** **   ** **    ** **      ** **      ** **     ** **

  **FTE Line Item**      ** **   ** **          **X**    ** **      ** **     ** **   ** **    ** **      ** **      ** **     ** **

  **Position             ** **   **X**          **X**    ** **      ** **     ** **   **X**    **X**      ** **      ** **     ** **
  Description**                                                                                                                

  **Educational Data**   ** **   ** **          **X**    ** **      ** **     ** **   ** **    **X**      ** **      ** **     ** **

  **Pay Elements:**      ** **   ** **          ** **    ** **      ** **     ** **   ** **    ** **      ** **      ** **     ** **

  **WIG Process**        ** **   **X**          **X**    **X**      ** **     ** **   **X**    **X**      ** **      ** **     ** **

  **Pay Changes Process: ** **   **X**          **X**    ** **      ** **     ** **   **X**    **X**      ** **      ** **     ** **
  Quality Step                                                                                                                 
  Increase**                                                                                                                   

  **Mass Pay Increase**  ** **   ** **          **X**    ** **      **X**     ** **   ** **    ** **      ** **      ** **     **X**

  **Allowances and       ** **   **X**          **X**    **X**      **X**     ** **   **X**    **X**      ** **      **X**     **X**
  Differentials**                                                                                                              

  **Pay for Critical     ** **   **X**          **X**    **X**      **X**     ** **   **X**    **X**      ** **      ** **     **X**
  Positions**                                                                                                                  

  **Competitive          ** **   **X**          **X**    ** **      ** **     ** **   **X**    **X**      ** **      ** **     ** **
  Promotions and                                                                                                               
  Reassignments**                                                                                                              

  **Awards:**            ** **   ** **          ** **    ** **      ** **     ** **   ** **    ** **      ** **      ** **     ** **

  **Awards               ** **   **X**          **X**    **X**      **X**     ** **   **X**    **X**      ** **      ** **     **X**
  Process/Systems                                                                                                              
  -Inventions and                                                                                                              
  Contributions Awards                                                                                                         
  Process**                                                                                                                    

  **Bonus**              ** **   **X**          **X**    **X**      **X**     ** **   **X**    **X**      ** **      ** **     **X**

  **SES Bonus Process**  ** **   ** **          **X**    **X**      **X**     ** **   ** **    **X**      ** **      ** **     **X**
  ---------------------- ------- -------------- -------- ---------- --------- ------- -------- ---------- ---------- --------- -------------