# Presentation: 448768

## Project Management Information Improvement (PMI2)Process Team SIT TrainingJuly 25, 2005

## Agenda - Monday

| Welcome/Meeting Objectives/Introductions | Lisa Huzar | 2:00 – 2:10 |
| --- | --- | --- |
| Project Status | Tamara Fields | 2:10 – 2:15 |
| MdM Interface/Mitigation Plan | Tamara Fields | 2:15 – 3:15 |
| CRP Results | Vivian Liang | 3:15 – 3:20 |
| SIT Overview
SIT Scope & Approach
SIT Environment
SIT Participation
Center Legacy System Coordination
SIT Roles and Responsibilities
SIT Pass 1 & 2 Test Set/Plan
SIT Schedule | Vivian Liang
Chris Watson | 3:20 – 4:15 |
| Change Management Update | Tia Collins | 4:15 – 4:30 |
| Wrap/Up – Review Schedule for Week | Lisa Huzar
Vivian Liang | 4:30 – 4:45 |

**Notes:**
SIT Overview Charts

Overall Integrated Project Timeline
SIT Roles and Responsibilities
SIT Environment
SIT Rules
SIT Test Set/Plan
SIT Schedule

## Objectives	

- Communicate the following
- SIT Overview
- SIT Roles and Responsibilities
- SIT Environment
- SIT Rules
- SIT Test Set/Plan (Execution Log)
- SIT Schedule
- SIT Tools (Test Director)
- SIT Defect Process
- SIT Business Process Documentation Update
- Detailed content review of the Final Design
- Demo Design
- Execute transactional related design elements
- Review SIT training materials
- Job Aids
- User Procedures
- Test Plan Execution Logs

**Notes:**
All the critical test will be executed by the Data Structures & Cost Collection teams. They are doing the following/supplemental test for various reasons.
Test Director is the formal tool to collect test data to tie to requirements for audit purpose. Every test that we want a formal test will be in Test Director.  BW testers will need to Test Director.  

## SIT Ground Rules

- All SIT participants must attend SIT Training scheduled the week of July 25
- All PMI2 R/3 testing will take place in the PMI2 facility, Room 429
- Remote access will be available for BW testing; however, PMI2 Reporting Process Team members are encouraged to test in the PMI2 facility
- Center Legacy Systems that extract data from BW can be tested remotely
- BW remote testers should direct questions to their Process Team members
- SIT participants that are currently not Process Team members will now be considered project resources
- SIT participants may be requested to enter test transactions for multiple Centers

## Project Status

## Summary of Project Activities

- December 2004 - Project Approved
- January 3rd - Blueprint Started
- March 14th – PMI2 Blueprint Pass 1 Review
- March 29th – Call Letter Issued to request Process Team (Core and Extended)
- April 5th – PMI2 Preliminary Blueprint Review (PBR)
- April 26th – Process Team Kick Off
- May 11th – PMI2 Final Blueprint Review (FBR)
- PMI2 Phase I completed Blueprint Phase on May 13th
- May 16th - Realization Started & Conference Room Pilot (CRP) Start
- May 24th - Realization Kick Off
- June 21st & 22nd – Data Mapping Kick Off (Institutional & Mission Directorates)
- June 28th - Critical Design Review (CDR)
- July 1st – Conference Room Pilot (CRP) end
- July 5th – System Integration Test (SIT) start
- July 25th – Test Readiness Review (TRR)
- August 19th – PMII Draft Data Mapping Deliverable due (Institutional & Missions)
- Oct. 5th  – Tentative ORR (including Center Readiness Review)
- October – Go Live

## PMI2 Timeline (including CRCS & MdM Key Dates)

**FY05**

**June**

**July 1****st****: Conference Room **
**Pilot End**

- = Key Deliverable Dates

- Review by OCFO, OCE, Mission   Directorates, and Institutional Agency POCs

**June 28****th****: Critical**
**Design Review (CDR)**

**July 5****th****: SIT Pass 1 Start**

**July 21****st****: Tentative TRR**

**July 25****th****: SIT Pass 2 Start**

**Aug 19****th****: PMII Data **
**Mapping **
**Deliverable Due date**

**Sept. 26****th****: CRCS **
**Production Go-Live**

**Sept  2****nd****: Data Mapping **
**provides final **
**extract for CRCS Load**

**July**

**August**

**September**

**October**

**Oct . 10****th****: Final**
**Deliverable Automated **
**Load to SAP**

**Oct 17:  Tentative**
**SAP Go-Live**

**June 21****st**** – 22****nd****:  Data **
**Mapping Kick offs Mission**
**Directorates/Institutional**

**Aug 22****nd**** – 31****st****: OCE/OCFO **
**Final Review, Final Change **
**Request Disposition**

- July 22nd: SIT Pass 1 End

**Aug. 19****th****:  SIT Pass 2 End**

**Aug 22****nd****: SIT Pass 3/**
**Release 6.1 Pass 2 Start**

**Aug 31****st****:  Agency Account **
** ****Code Freeze**

**Oct  24:  Tentative**
**MdM Go-Live**

**Oct . 21****st****: Final**
**Deliverable Automated **
**Load to MdM**

**Aug 15****th****: Final Submission **
**of  Change Request**

**Sept 16****th****: SIT Pass 3/**
**Release 6.1 Pass 2 End**

**Sept 19****th**** – Sept 29****th****: **
**SIT Pass 4/**
**Release 6.1 Pass 3 **

**=**

## MdM Interface Update / Mitigation Plan

## Background

- PMI2 Team Recommended Deferring the MdM to SAP interface for October Go-Live during the CDR
- Requested approval of the Mitigation Plan Approach until Interface is Released for Production
- Recommended continued parallel interface development for earliest release possible
- Justification/Rationale
- Use Case documentation needed to be completed and approved on May 18th
- Unresolved Issues
- Incomplete Design
- Documentation based on assumptions
- Development needed to start by June 8th to meet delivery for SIT Pass 2
- Lack of Schedule Integration to support System Integration Test Coordination
- Per the OCFO DCFO, received approval of recommendation on July 1st

## MdM Interface Scope

- Central repository for NSM data elements
- Web-based tool to replace the current AWCS system
- All Project Structures and nomenclature will reside in the MdM and be passed to SAP R/3 for Fund Center and Project creation
- Current PMI2 assumption is to design the interface to build the following data elements
- Funds Center
- Project WBS Hierarchy
- Derivation Rules
- Validation Rules

## Interface Requirements

- PMI2 requires the following to complete Interface Design and Implementation
- Functional and Technical Design
- Agreement of the design approach for PMI2 attributes
- Tool Demo
- Use Case documentation completed and approved
- Interface Definition Agreement (IDA) completed and approved
- MdM timeline to integrate with PMI2 System Integration Test
- Establish schedule dependencies
- Environment Connectivity
- Technical confirmation of data exchange
- Testing and Verification of business rules and design
**Coordinated Test Execution and problem resolution**

## Auto Load Validation Process

- MdM and SAP Content and Technical Validation
- Data Mapping team will provide automated query validation of SAP and MdM extracted Master Data against Data Mapping Access database
- Auto Test Load Validation Plans (content and technical) need to be developed for SAP verification
- Data Structures team will provide a listing of content validation rules to ensure content loaded to SAP matches the Data Mapping Access Database.
- Compare number of records sent against number of records created
- Compare number of derivation rules created versus anticipated
- Data Structures team will provide a technical validation to ensure requirements are met in SAP
- Business Area ’01’ on Project Level 0
- MdM needs to provide Auto Test Load Validation Plan (content and technical)

## Post Go-Live Creation/Maintenance Process

| Option A | Assumptions | Process | Questions | Comments |
| --- | --- | --- | --- | --- |
| MdM System is Ready for October Release | SAP is not the System of Record

MdM system contains all requested/approved PMI2 attributes

Subject to the same guidelines or rules established by the interface | SR submitted to the Competency Center for creation/update (‘Business as Usual)
MdM System Administrator (equivalent) submits SR
MdM System owns the approval process
MdM still responsible for data validation
Nomenclature standards
7120.5c WBS Level 2 Standards
Confirmation of Status ‘Executable’
Competency Center only receives creation/updates from the MdM System Administrator and/or equivalent
 | Who submits the SR from the MdM System (System Administrator and/or Equivalent)? Who works creation/update issues from the Competency Center? | The PMI2 team will provide user procedures for managing new attributes |

## Post Go-Live Creation/Maintenance Process

| Option B | Assumptions | Process | Questions | Comment |
| --- | --- | --- | --- | --- |
| MdM is not Ready for October Release | SAP is not the System of Record

MdM system does not contain all requested/approved PMI2 attributes

Subject to the same guidelines or rules established by the interface
 | SR submitted to the Competency Center for creation/update
Agency still responsible for data validation
Nomenclature standards
7120.5c WBS Level 2 Standards
Confirmation of Status ‘Executable’
Centers not allowed to create SRs for Agency Controlled NSM Structure
Only Receives Updates from Agency Owner

 | Where is the System of Record Maintained for NSM Structure & Nomenclature without the MdM System? Does the Data Mapping Database stay as interim? If so, who maintains it and who owns it?

Who creates the SRs for the Comp Center? How does the Comp Center know the request approved and validated and coming from the correct owner of the data? | The PMI2 team will provide user procedures for managing new attributes
 |

## Conference Room Pilot (CRP) Results

## Conference Room Pilot (CRP) Overview

- A Conference Room Pilot is a working SAP prototype based on a selection of several key business processes and is used to validate the functionality and the design:
- It begins with setting up initial configuration components
- Continues with the detailed definition of business scenarios
- Scenarios are defined for the agency, using new processes and center input to ensure completeness
- Detailed configuration built on the “going-in position” defined by the organizational hierarchy definitions

## CRP Results 

| Status | Data Structures | Cost Collection |
| --- | --- | --- |
| Passed | 21 | 25 |
| Passed with Exception | 7 | None |
| Failed | 3 | None |
| Defects | I02462, I02463 | None |

- Total of 20 scenarios have been tested during CRP
- 56 execution logs defined and tested
- Multiple execution logs utilized to separate PY05 and prior vs. PY06 and forward processes
- Multiple execution logs utilized to separate complex scenarios
- Status
- Passed – Scenario passed with no issues
- Passed with Exception – SGL pro formas not confirmed by OCFO; testing based on PMI2 assumptions
- Failed – Agency process not defined by OCFO

## System Integration Test (SIT) Overview

## System Integration Test (SIT) Overview

- Formal set of integrated test activities incorporating all aspects of the business solution, including converted legacy data (where applicable)
- Business oriented, end-to-end test cases encompassing steps or functions of the business process, including exceptions and error processing
- Includes the following solution components:
- Agency systems (SAP and any remaining legacy applications)
- Agency business partners (HHS, Treasury, etc...)
- Custom development components (interfaces with other agency systems or business partners, custom reports / forms, and extensions)
- User Procedures and Job Aids
- SIT will be planned and performed by the PMI2 Process and Integration IPT Teams (with additional participation from Agency* *Core & Extended Process Team ) and will include Agency-level solution components
- Perform more formal and comprehensive business test scenarios than previous project test activities
- Test according to functional requirements (tracking utilizes RequisitePro), integration with general ledger, etc., where functional requirements will be mapped to flow charts and scenarios

## SIT Scope and Schedule

| Test Pass | Description | Timeline |
| --- | --- | --- |
| SIT Pass 1 | Integrated end-to-end business processes
 Limited Custom objects (RICEF) included
Testing will occur in T01 (copy of P01)
BW available for test verification | 7/5/2005 – 7/22/2005 |
| SIT Pass 2
 | Integrated end-to-end business processes
All available Custom objects (RICEF) included
Testing will occur in T01 (copy of P01 pre year-end)
BW available for test verification | 7/25/2005 – 8/19/2005 |
| SIT Pass 3
 | Integration with Release 6.1 Pass 2
All available Custom objects (RICEF) included
Testing will occur in S02 (P01 post year-end)
BW available for test verification | 8/22/2005 – 9/16/2005 |
| SIT Pass 4
 | Integration with Release 6.1 Pass 3
Testing will occur in X02 (P01 post year-end)
BW available for test verification | 9/19/2005 – 9/29/2005 |

## System Build Schedule

## Process IPT Test Documentation & Deliverables

- The Process IPT Team is responsible for developing several key documents and deliverables for System Integration Test
- Each document has its own distinct use, and each is related to the others
- Test Set
- Test Plan (Execution Log)
- Details the Test Steps and Transaction Codes, Expected Results, and Actual Results
- In addition to these test documents, the Process IPT remains responsible for maintenance of several other key deliverables
- Requirements
- Process/Sub-Process/Activity definitions
- White/Solution Papers
- Role Definitions – coordinated with Change Management team
- Inputs to Process Flows and Functional/Technical Designs
- Controlled through Competency Center Change Control processes
- Defect Documentation
- Configuration Rationale

**Notes:**
Our Objectives:
Describe the dynamics and process of change
Explain the role of a Change Agent within the Core Financial Project
Change is dependent on all of you.  We have no magic shoes that we can click together to bring about change.
Develop action items to support positive movement along the change curve
Yours?

## Documentation Change Control Process

- The PMI2 project will follow the Change Control process as defined by the IFMP Project Process.
- Any changes to requirements, activity definitions, and white papers must follow the project’s change control process
- A Lotus Notes Database entitled Rational Artifact Tracking (RAT) will be used to request base-lined documentation to be checked out from RequisitePro
- QA Team member receives notification of “check out”
- Only one check out allowed at one time for the same document
- Requestor makes changes with TRACK CHANGES feature “ON” and reattaches file in MDM
- When completed, select approver and send e-mail notification
- Only Sub-Team leads and QA Team have approval authorization
- When approved, QA Team member checks document into RAT and marks any new requirements

**Notes:**
Our Objectives:
Describe the dynamics and process of change
Explain the role of a Change Agent within the Core Financial Project
Change is dependent on all of you.  We have no magic shoes that we can click together to bring about change.
Develop action items to support positive movement along the change curve
Yours?

## Coordination with Integration IPT

- Integration IPT is responsible for the SIT tool sets, Application Development Documentation (Use Cases, Function/Technical Designs), and the Defect Process
- The Process IPT team will work with the Integration IPT team to blend the business, system, development, and technical aspects into a seamless, integrated whole
- The Integration IPT Quality Assurance (QA) is responsible for the Defect Process
- Any failed step that is encountered during test execution requires a defect to be logged
- Defects are created within TestDirector and associated directly to the failed step
- Each defect tracks the Status, Application (Process), User information, and a description
- The Test Defect is associated with a SIR in the Lotus Notes Methods Delivery Manager (MDM) to support the transport/migration process
- The defect is reviewed by Process and Integration IPT Leads and NASA counterpart
- The defect is assigned to the appropriate team member and worked according to the existing procedures

**Notes:**
Our Objectives:
Describe the dynamics and process of change
Explain the role of a Change Agent within the Core Financial Project
Change is dependent on all of you.  We have no magic shoes that we can click together to bring about change.
Develop action items to support positive movement along the change curve
Yours?

## SIT Participation

| Test Pass | Process and Integration IPT Teams | Core and Extended Process Team |
| --- | --- | --- |
| SIT Pass 1 | Responsible for executing all identified test scenarios (R/3 & BW) | No Participation |
| SIT Pass 2 & 3
 | Responsible for executing all identified test scenarios (R/3 & BW)
Provide support for SIT training scheduled week of 7/25
Provide functional support to Core/Extended team when on-site for testing | Attend SIT Training the week of 7/25 
No R/3 SIT testing allowed if the user does not attend scheduled SIT Training
Responsible for executing identified test scenarios (R/3 & BW) to support Center Legacy testing
May require executing the same scenarios multiple times to support test data creation for all Centers
All Testing by the Core/Extended Team must be On-Site
SIT Pass 2 On-Site Testing on the Week of 8/8 & 8/15
SIT Pass 3 On-Site Testing on the Week of 9/12
Optional On-Site Testing the Week of 9/5 (holiday week)
Responsible for testing the End User Procedures for SIT Pass 2 and 3 |
| SIT Pass 4 | Responsible for executing all identified test scenarios (R/3 & BW) | No Participation |

## Data Load / Set-Up

## Automated Load Background

- Per the OCFO DCFO approval on July 1st, the MdM to SAP interface is deferred for October Go-Live and the project will utilize the Mitigation Plan Approach until Interface is Released for Production
- One time initial automated loads will be utilized to create Fund Centers, Projects, and Derivation rules to support the creation of the PY06 NSM Structure in SAP
- Utilize the Deliverables created by the Data Mapping team to create the necessary extract files to support the automated loads
- Data Mapping Deliverable Includes
**Updated M3 document (Mission, Theme, Program, Project)**
**Project through WBS Level 7**
**Attributes for all levels of the NSM Structures (Mission – WBS Level 7)**
**PY05 and Prior Mapping to PY06 NSM Structure**
- As a result of this decision, the automated load process will be tested during SIT

## SIT Auto Load Strategy 

| Test Pass | Test Automated Load  | Test Data |
| --- | --- | --- |
| SIT Pass 1
 | Fund Centers Only  | Production Data: Institutional (Mission through Project)
Sample Data: Programmatic (Mission through Project) |
| SIT Pass 2
Pre Year-End
Production Copy | Fund Centers
Projects/WBS Elements
Derivation Rules
Cost Centers (attribute update only) | Production Data: Institutional and Mission (Mission through Project/WBS 7)
Sample data for Gaps |
| SIT Pass 3
Post Year-End
Production Copy
 | Fund Centers
Projects/WBS Elements
Derivation Rules
Cost Centers (attribute update only) | Production Data Only
Full Load of Production Data (confirm etc auto load of each item + functional and technical validation) |

## Mitigation Plan Automated Tool Options

| Master Data Area | Options |
| --- | --- |
| Derivation Rules | Custom ABAP
Script (i.e., eCATT, WinRunner, LoadRunner) |
| Funds Centers | SAP-delivered t-code FMSY (loads funds center data from a flat file)
Custom ABAP
Script
 |
| Projects | SAP-delivered LSMW project using BAPI or IDoc import techniques
Custom ABAP
Script |
| Cost Centers | SAP-delivered LSMW project using BAPI or IDoc import techniques
Custom ABAP
Script |

## Mitigation Plan Technical Recommendation

- As an implementation activity, the PMI2 team recommends Mercury WinRunner/QuickTest
-  One time use for Production Data Load / No reuse capability
-  Aggressive schedule and quick turnaround time required
-  Expertise within the team with this toolset
-  High Level logging can be implemented within the script
- Technology IPT is responsible for the initial load to production
**Any re-assessment of automated tool considerations after go-live would be the responsibility of the Competency Center**

## Data Mapping Extract File Listing for SAP Auto Load

| SAP Extract File |  |  |  |  |  |
| --- | --- | --- | --- | --- | --- |
| # | Data Mapping Extract Files from Access Database | Comments | SIT Pass 2 Due Date | SIT Pass 3 Due Date | Go-Live Due Date |
| 1 | SAP Extract: PY06 Projects for Creation |   | 22-Jul | 8/17/2005 | 10-Sep |
| 2 | SAP Extract: PY06 Fund Centers for Creation |   | 22-Jul | 8/17/2005 | 10-Sep |
| 3 | SAP Extract: PY06 Derivation Rules for Creation |   | 22-Jul | 8/17/2005 | 10-Sep |
| 4 | SAP Extract: PY05 & Prior Projects (WBS Elements) for Change  | Attribute Update:Mission, Theme, Program, Project, plus others as identifed in the MdM Attribute listing | 29-Jul | 8/17/2005 | 10-Sep |
| 5 | SAP Extract: PY05 & Prior Fund Center for Change  | Attribute Update:Mission, Theme, Program, Project | 29-Jul | 8/17/2005 | 10-Sep |
| 6 | SAP Extract: PY05 & Prior Cost Center for Change  | Attribute Update:Project | 29-Jul | 8/17/2005 | 10-Sep |
| 7 | BW ITD WBS PY05 & Prior Mapping to PY06 |   | 29-Jul | 8/17/2005 | 10-Sep |

## Center Legacy System Coordination

## Center Legacy System Approach

- PMI2 team held a telecom on June 15th with Centers to review potential impact of PMI2 design on Center Legacy Systems
- Reviewed PMI2 design
- Reviewed considerations of impact
- Requested Centers to provide the following
- Listing of the Center Legacy Systems that require modifications
- General Estimate on days required to complete the change
- General Concerns of the Center
- Required Functional Support from PMI2 to interpret change to Center Legacy Systems
- Provided the Centers the following documents to help facilitate impact assessment action
- Technical Questionnaire to aid Center Legacy System Assessment
- Template provided to provide the requested information in one format
- Requested assessment be returned by COB Friday, June 24th
- All Centers represented on initial call except DFRC & JPL (60+ attendees)
- Conducted additional call on July 8th with JPL and DFRC to collect same information by July 15th
- Held follow-up calls with each of the Centers to review results and incorporate findings into the PMI2 SIT Schedule

## Center Legacy System Testing 

- Center Implementation Point of Contact will have access to the PMI2 SIT environment
- The Centers are responsible for all Center Legacy System testing
- If the Center utilizes BW “pulls” or R/3 Reports for retrieving data from Core Financial to support Center Legacy Systems, they will have the same ability during  SIT Pass 2 and 3
- BW refreshed daily for SIT Pass 2 and 3 Clients
- Centers will need to review the SIT Pass 2 and 3 detailed schedules to understand when applicable data would be available for data pulls
- Dependencies on other test plans / sets have been identified and scheduled accordingly
- The PMI2 Process and Integration IPTs will perform interface testing for SIT Pass 2 and 3 for Core Financial approved Agency (i.e. Travel) and Center (i.e. SSC Reimbursable Roll-Up) interfaces
- Interfaces will be defined in the SIT Pass 2 and 3 schedules
- The PMI2 Process IPT team has identified the necessary scenarios and schedule to be executed to support test data creation for all Centers
- The Core and Extended Process Team is responsible for the execution of these scenarios

## Process IPT Roles & Responsibilities

## Process (Test) IPT Structure

**Notes:**
Our Objectives:
Describe the dynamics and process of change
Explain the role of a Change Agent within the Core Financial Project
Change is dependent on all of you.  We have no magic shoes that we can click together to bring about change.
Develop action items to support positive movement along the change curve
Yours?

## Process IPT Lead

- Overall responsibility for the Process IPT effort – tasks, deliverables, schedule, issues, interactions with other teams, etc...
- Performs day-to-day leadership of the overall test effort
- Ensures the delivery of a high-quality product that meets requirements and is completed on schedule and within the approved budget
- Identifies and obtains the appropriate resources (personnel, office space, supplies, tools, etc.)
- Establishes, monitors, and refines team organization structures and procedures to maximize efficiency and productivity
- Participates in the review & approval of  all Test Defects
- Ensures consistency and adherence to standards in Test Defect documentation & resolution
- Approves all team deliverables
- Coordinates interactions with Project Management and owns the issue resolution, status reporting and buy-in discussions with Project Management

## Process IPT Lead Continued

- Oversees all aspects of the System Integration Test effort
- Works directly with Competency Center QA and Release Management representatives for overall Release 6.1 coordination
- In conjunction with the QA team, coordinates all aspects of system defects, including assigning specific team members to complete system defect analysis, monitoring system defect resolution, retesting, and evaluating cross-team impacts
- Ensures participation of and coordination across functional areas and with other PMI2 and IPO teams

## Data Structures & Cost Collection (Test) Execution Lead

- Leads the day-to-day test planning and execution effort
- Ensures participation of and coordination across functional areas and with other PMI2 and IPO teams (as needed)
- Monitors and ensures adherence to test procedures and Test Defect documentation standards
- Reviews and validates/accepts documentation and deliverables of the Process IPT
- Coordinates the assignment of Test Sets/Plans with team members for planning completion
- Coordinates the assignment of Test Sets/Plans for execution.
- Monitors completion of the Test Sets/Plans in adherence to the SIT schedule
- Reviews and manages defects entered and associated with SIT

## Data Structures & Cost Collection (Test) Execution Lead Continued

- In conjunction with the QA team, monitors and tracks system defect and issue resolution, provides information to Process IPT Lead for status reporting, and supports communications with Project Management
- Serves as a “Point of Contact” for Process IPT Team Members during execution
- Ensures test set execution continues on schedule and monitors any delays or discrepancies

## Role and Responsibilities: Process IPT Test Team Member

- Participates in the execution and documentation of test sets and test plans, including participation in test sets/plans “owned” or coordinated by other team members
- Defines and documents test plans, including the mapping of requirements to test sets
- Creates or updates test plan results as part of test set execution and documentation
- Identifies and documents system defects according to team standards and processes
- Coordinates data definition and set-up in support of the SIT sets, ensuring that new and existing data is used appropriately
- Serves as a functional point of contact for the Application Fix Team.
- Coordinates updates with Change Management team for refinement of end-user role definitions and user procedures

## Role and Responsibilities: Process IPT Test Team Member

- Supports cross-team efforts, such as training development, application security, and mock conversion testing
- Applicable NASA team members will also leverage their deep business knowledge and serve as business subject matter experts (SMEs) across the entire testing effort
- Coordinates the involvement of NASA Functional Subject Matter Experts to ensure appropriate business/functional input and system considerations
- Completes the execution and documentation of test plans, including participation in test sets “owned” or coordinated by other team members

## Planning / Preparation Current Status

## SIT Planning / Preparation Status

- The Process IPT team has defined the Test Sets/Plans and Schedule for SIT Pass 1 and 2 (see Back-Up)
- Planning for SIT Pass 3 is in process to address testing of additional RIEF objects based upon the development schedule
- SIT Pass 1 -- Complete
- SIT Pass 2 – Scheduled to starts 7/25/2005, pending TRR Approval
- All of the Test Plans have been loaded in Test Director for SIT Pass 1
- All expected results have been updated
- Loading of the Test Plans for SIT Pass 2 are In Process
- All test plans scheduled for the first two weeks have been loaded

## SIT Pass 1 Revised Scope

- Per the approval/acceptance of the Critical Design Review (CDR), SIT Pass 1 Scope was re-aligned to accommodate the recent design changes to funds distribution
- Testing was concentrated on the following
- Funds Distribution Process
**New Validation Rules (including negative testing)**
**Including newly proposed design changes per the June 22****nd**** meeting at HQ**
- New Attributes for Fund Center master data
- New Attributes for Project/WBS master data
- Cost Assessments
- Test automated load of Fund Center Creation
- All other test scenarios successfully completed in CRP and were not impacted by changes to funds distribution were deferred to SIT Pass 2
- The only exception is the Working Capital Fund - NSSC Process which failed during CRP due to incorrect configuration of the SGL advance liquidation

## SIT Pass 1 Schedule Example

**SIT Pass 1 Schedule Example**

## SIT Pass 1 Test Plan Listing & Status

| Sort String | SIT Pass 1 Test Plan List | SIT Pass 1 NASA Owner | SIT Pass 1 Accenture Owner | Status |
| --- | --- | --- | --- | --- |
| Data Structures |  |  |  |  |
| DS01.01 | General Master Data Creation | Cynthia Smith | John Schremp | Passed |
| DS01.02 | Master Data Creation - Fund Center Extension | Cynthia Smith | Chris Krug | Passed with Exception |
| DS01.03 | Master Data Creation - Fund Center Auto Load | Cynthia Smith | Robert DamianBrian Kirchhoff | Passed |
| DS01.04 | Master Data Creation - Project Extension | Cynthia Smith | Robert Damian | Passed |
| DS01.05 | Master Data Creation - Derivation Rules | Cynthia Smith | Robert Damian | Passed |
| DS02.01 | Direct Programmatic Funding - PY05 | Cynthia Smith | John Schremp | Passed |
| DS02.02 | Direct Programmatic Funding - PY06 | Cynthia Smith | John Schremp | Passed |
| DS03.01 | Reimbursable Funding - PY05 | Cynthia Smith | Michelle Smith | Passed |
| DS03.02 | Reimbursable Funding - PY06 | Cynthia Smith | Michelle Smith | Passed |
| DS04.01 | Corporate G&A Funding - PY05 | Cynthia Smith | John Schremp | Passed |
| DS04.02 | Corporate G&A Funding - PY06 | Cynthia Smith | John Schremp | Passed |
| DS04.03 | Center G&A Funding - PY05 | Cynthia Smith | John Schremp | Passed |
| DS04.04 | Center G&A Funding - PY06 | Cynthia Smith | John Schremp | Passed |

## SIT Pass 1 Test Plan Listing & Status

| Sort String | SIT Pass 1 Test Plan List | SIT Pass 1 NASA Owner | SIT Pass 1 Accenture Owner | Status |
| --- | --- | --- | --- | --- |
| Data Structures |  |  |  |  |
| DS04.05 | Institutional Investment Funding - PY05 | Cynthia Smith | John Schremp | Passed |
| DS04.06 | Institutional Investment Funding - PY06 | Cynthia Smith | John Schremp | Passed |
| DS04.07 | Agency Fee for Services Funding - PY05 | Cynthia Smith | John Schremp | Passed |
| DS04.08 | Agency Fee for Services Funding - PY06 | Cynthia Smith | John Schremp | Passed |
| DS04.09 | Service Pool Funding - PY05 | Cynthia Smith | John Schremp | Passed |
| DS04.10 | Service Pool Funding - PY06 | Cynthia Smith | John Schremp | Passed |
| DS04.11 | Labor Pool Funding - PY05 | Cynthia Smith | John Schremp | Passed |
| DS04.12 | Labor Pool Funding - PY06 | Cynthia Smith | John Schremp | Passed |
| DS04.13 | Agency Service Pool Funding - PY06 | Cynthia Smith | John Schremp | Passed |
| DS05.01 | Generate SGL Reports | Cynthia Smith | Michelle Smith | Passed |
| DS08.01 | Investment Funding - PY05 | Cynthia Smith | Michelle Smith | Passed |
| DS08.02 | Investment Funding - PY06 | Cynthia Smith | Michelle Smith | Passed |
| DS09.01 | GAD Funding - PY05 | Cynthia Smith | Lauren Baker | Passed |
| DS09.02 | GAD Funding - PY06 | Cynthia Smith | Lauren Baker | Passed |
| DS10.01 | Miscellaneous Funding - CR PY05 | Cynthia Smith | Lauren Baker | Passed |
| DS10.02 | Miscellaneous Funding - Rescission PY05 | Cynthia Smith | Lauren Baker | Passed |
| DS10.03 | Miscellaneous Funding - CR PY06 | Cynthia Smith | Lauren Baker | Passed |
| DS10.04 | Miscellaneous Funding - Rescission PY06 | Cynthia Smith | Lauren Baker | Passed |

## SIT Pass 1 Test Plan Listing & Status

| Sort String | SIT Pass 1 Test Plan List | SIT Pass 1 NASA Owner | SIT Pass 1 Accenture Owner | Status |
| --- | --- | --- | --- | --- |
| Cost Collections |  |  |  |  |
| CC06.01 | Month end Processing-Cost Pool Allocations - PY05 | Cynthia Smith | Chris Watson | Passed |
| CC06.02 | Month end Processing-Cost Pool Allocations - PY06 | Cynthia Smith | Chris Watson | Passed |

## SIT Pass 1 Results

| Test Plan Summary | Passed | Passed with Exception | Deferred | Failed | Defect |
| --- | --- | --- | --- | --- | --- |
| Data Structures Test Plan Results | 29 | 1 | 1 | 0 | 4 |
| Cost Collection Test Plan Results | 2 | 0 | 0 | 0 | 0 |
| Total | 31 | 1 | 1 | 0 | 4 |

| Summary | # of Test Sets | # of Test Plans |
| --- | --- | --- |
| Data Structures | 10 | 31 |
| Cost Collection | 1 | 2 |
| Total | 11 | 33 |

## SIT Pass 1 Results

| Defect Title | Defect ID | Status | Priority | Technical Owner | Functional Owner |
| --- | --- | --- | --- | --- | --- |
| Master Data Creation_PY06- Create Fund Error | 2 | Retesting Complete | 1-Very High | Art Dunn | John Schremp |
| Funds Center Master Extension - incorrect error message | 3 | Retesting Complete | 2-High | Art Dunn | John Schremp |
| Funds Center Extension - Field Length and Type change | 4 | Retesting Complete | 3-Medium | Art Dunn | John Schremp |
| Funds Center Master Extension | 5 | New | 4-Low | Art Dunn | John Schremp |

## SIT Pass 2 Listing and Schedule(Go to Excel Document)

## Change ManagementTraining

## Training Curriculum Update

- The updated curriculum for PMI2 includes the following:

| Course | Delivery Method | Audience |
| --- | --- | --- |
| PMI2 Overview | Web-based | All Core Financial Roles
Project Managers
 All WebTADs users  |
| Funds Distribution Processing | Instructor Led | Agency Budget Maintainers Center Budget Maintainers  |
| PMI2/ALDS Information Delivery Overview  | Instructor Led | Reporting Super User Leads
 All BW users with standard BW query access  |
| Assessment Cycles | Instructor Led | Assessment Cycle Maintainer |
| Procurement Process Overview | Web-based | Procurement Community |

## Training Impacts to Existing Core Financial Courses

- Several existing Core Financial courses available on SOLAR will be updated to reflect impacts by PMI2

| Course | Delivery Method |
| --- | --- |
| General Overview Course |  |
| Core Financial Cross-Functional Overview (FI-FM-MM-CO Relationships)  | Web-Based |
| Purchasing Courses |  |
| PR Review Process  | Instructor Led  |
| Requisition Approval Processing 
 | Instructor Led |
| PR Review Process for Procurement Personnel  | Instructor Led |
| Bankcard Review Process  | Instructor Led |
| Bankcard Purchases & Desktop Receiving  | Web-Based |
| Requisitioning Basics  | Web-Based  |

## Training Material Development Timeline

| Training Task | Owner | Time Frame |
| --- | --- | --- |
| Training Curriculum distributed to Competency Center | PMI2 Training Lead | Week of July 25-29 |
| Training Detailed Course designs distributed to Competency Center  | PMI2 Training Lead
 | Beginning July 29 |
| PMI2 Overview course developed  | Competency Center | Month of August |
| Existed Core Financial Courses updated | Competency Center | Month of August |
| Training Materials (PMI2 Overview Course and CF Courses) are reviewed | PMI2 Training Lead
 | Throughout course development |
| Draft Training Communication Materials | PMI2 Training Lead

 | August 1-5 |
| Training Materials posted on SOLAR | Competency Center | TBD |
| Conduct PMI2/ALDS Information Delivery Train the Trainer  | Lisa Huzar with support from PMI2 Training Lead
 | August 29-September 2 |
| Rollout PMI2 Overview Course to Centers | PMI2 Training Lead
 | September 5-9 |
| Rollout Core Financial Courses to Centers | PMI2 Training Lead
 | September 19 |

## PMI2/ALDS Training Timeline

**PMI****2/ALDS ****Training Timeline**

- Training

- 8/22

- 8/26

- Training Development Team build of Training Data (TR2)

- 9/5

- 9/9

- Distribute PMII Overview Course to Center CM POCs

- 9/13-9/15

- ALDS Overview Course

-  10/28 Center Information Delivery Training continues (uses Production BW)

- 9/5-9/16

-  8/1 Begin Training Logistics Coordination (Training Rooms, trainers, # impacted end users)

- Center Development of Info Delivery Training (BWR)

- Training

- 8/22

- 8/26

- Training Development Team build of Training Data (TR2)

- 9/5

- 9/9

- Distribute PMII Overview Course to Center CM POCs

- 9/13-9/15

- ALDS Overview Course

-  10/28 Center Information Delivery Training continues (uses Production BW)

- 9/5-9/16

-  8/1 Begin Training Logistics Coordination (Training Rooms, trainers, # impacted end users)

- Center Development of Info Delivery Training (BWR)

- Centers deliver Training Communication

- 8/15-8/26

-  9/19 Rollout Updated CF Course to Centers

## Change ManagementProcess & Organization Alignment

## Performance Management ToolsEnd User Procedures - Status

- Impacted End User Procedures (EUPs)
- 22 existing EUPs require minor updates as a result of PMI2
- BE = 16
- Purchasing = 5
- Cost Management = 1
- 1 new EUP required for t-code BPACC - Create/Maintain Budget Derivation Rules
- EUP Development Status
- In Process = 9 (Developer is in process of updating/creating EUP)
- Complete = 0 (Team Lead approved; awaiting Change Mgmt review)
- In Revision = 0 (EUP failed a review; developer is revising EUP)
- Revision Complete = 14 (Change Mgmt approved; awaiting Functional Lead review)
- Approved = 0 (Functional Lead approved; EUP is ready for testing)

## Performance Management ToolsEnd User Procedures - Testing

- End User Procedures will be tested in SIT 2 (7/25 to 8/19) by NASA’s Core and Extended Process Teams
- Any defects/changes identified through the SIT execution will be retested as part of 6.1 Release Regression Test 1 (8/22 to 9/16)
- End User Procedures will be a part of the overall solution and are an important aspect of the overall test scope

**Notes:**
End User Procedures will be tested in SIT 2 (7/25 to 8/19) by NASA’s Core and Extended Process Teams
Week of 8/15
Any defects/changes identified through the SIT execution will be retested as part of 6.1 Release Regression Test 1 (8/22 to 9/16)
Week of 8/29
Week of 9/12

## Performance Management ToolsEnd User Procedures - Key Dates

| Activity | Responsible | Due Date |
| --- | --- | --- |
| SIT 1: |  |  |
| Develop EUPs and post in MDM for review | Process IPT | July 22, 2005 |
| Review & Approval | Process Sub-Team Leads, Change Management, and Functional Lead | As completed, on or before July 22 |
| Interim Hand Off to Competency Center (not tested) | Change Management | July 25 |
| SIT 2: |  |  |
| Validate EUPs | NASA Extended and Core Process Teams | Week of Aug 15 – 19 |
| Revise EUPs as needed and post in MDM for review/approvals | Process IPT | As completed, on or before Aug 19 |
| Review & Approval | Same as above | As completed, on or before Aug 22 |
| Interim Hand Off to Competency Center (tested) | Change Management | Aug 24 |
| SIT 3/6.1 Regression 1: |  |  |
| Re-test defects found during SIT 2 | NASA Extended Process Team | Sept 16 |
| Revise EUPs as needed and post in MDM for review/approvals | Process IPT | As completed, on or before Sept 16 |
| Review & Approval | Same as above | As completed, on or before Sept 21 |
| SIT 4/6.1 Regression 2: |  |  |
| End User Procedure Deliverable TIM | Change Management and COTR | Week of Sept 26 |
| Post Testing Phases: |  |  |
| Final Hand Off to Competency Center (approved deliverable) | Change Management | Sept 30 |
| EUPs made available to end users | Competency Center | Coinciding with Go Live |

## Performance Management ToolsJob Aids - Status

- Impacted Job Aids
- 8 existing Job Aids require major updates (All Cost Management)
- 5 New Job Aids required (All Budget Execution)
- 25 Expired Job Aids (All Cost Management)
- Job Aid Status
- Not Started = 12
- In Process = 0
- Complete = 1
- Approved = 0

**Notes:**
All inquiries here should be directed to Vivian or Joyce

## Performance Management ToolsRole Definitions - PMI2 Role Impacts

- Of the approximately 74 Core Financial roles assessed to date, the following are impacted by PMI2
- 24 existing Core Financial SAP roles
- 2 existing Bankcard roles
- 1 new Core Financial SAP role identified (Competency Center role)
- 0 expired roles identified
- Nature of role impacts is primarily changes to the data, not significant process changes to the actual role or role definition (e.g., description, activities, skills)
- 13 roles required role definition updates
- 8 were impacted by PMI2
- 5 were outdated since Core Financial
- Role security will be tested in SIT 2 and, if needed, SIT 3

**Notes:**
New role: MdM Interface Processor

## Performance Management ToolsRole Definitions - PMI2 Role Impacts

- Budget Execution
- Budget Administrator (Competency Center)
- Budget Maintainer
- Funds Reserver
- Project Administrator (Competency Center)
- Budget Report Processor
- MdM Interface Processor (New)
- SGL
- SGL Reconciliation Analyst
- External Information Generator
- Management Information Generator
- Purchasing
- Agency Buyer (Procurement)
- Center Buyer (Procurement)
- Outside Buyer (Procurement)
- Requisition Approver (Requisitioning)
- Requisitioner (Requisitioning)

- Cost Management (CM)
- Assessment Cycle Maintainer
- Contractor Cost Report (CCR) Administrator
- Contractor Cost Report (CCR) Analyst
- Cost Center Maintainer (Competency Center)
- Consumption Data Processor
- NSMS Purchasing Analyst
- NSMS Distribution Analyst
- BankCard
- Bankcard Holders
- Bankcard Approvers
- Account Payables
- Vendor Invoice Processor
- Account Receivables
- Reimbursable Manager
- Agency Surcharge Processor
- Sales Order Processor

- In addition, updated 5 existing Core Financial roles that were outdated:

- Project Planner - Budget Execution
- Journal Entry Processor – SGL
- Assessment Cycle Administrator - CM

- Agency Contractor Cost Report Administrator - CM
- Contractor Cost Report Processor - CM

**Notes:**
Bullet One - Other impacted areas include timecard recording, travel, and procurement

## Performance Management ToolsPosting Documents to OLQR

- Submit OLQR documentation via the SR process as attachments
- Submit batch requests per functional area (e.g., all BE EUPs in one SR)
- Use track changes feature on all existing documents (if possible)
- 2 week lead time requested for changes to OLQR
- Documents will be stored on OLQR development server until go live
- Freeze on all other updates to OLQR necessary (meaning all documents on development will be uploaded at once, not separately)
- OLQR POC: Cathy Webster

## SIT Training Agenda for the Week

## Agenda - Tuesday

| Procurement Top Concerns | Joyce Meyer | 9:00 – 10:00 |
| --- | --- | --- |
| Data Structures: Master Data – Fund Center | Cynthia Smith
John Schremp | 10:00 – 10:55 |
| Break |  | 10:55 – 11:05 |
| Data Structures: Master Data – Project/WBS | Cynthia Smith
Rob Damian | 11:05 – 12:00 |
| Lunch |  | 12:00 – 1:00 |
| Data Structures: Master Data – Derivation Rules | Cynthia Smith
John Schremp
Chris Krug | 1:00 – 1:45 |
| Data Structures: Fund Distribution – Agency | Cynthia Smith
John Schremp
Chris Krug (on call) | 1:45 – 2:45 |
| Break |  | 2:45 – 3:00 |
| Data Structures: Fund Distribution - Center | Cynthia Smith
John Schremp
Chris Krug (on call) | 3:00 – 4:00 |

**Notes:**
Show Power Point Standard Design Charts & then demo in SAP (display)
Walk them through a create 
Show them the job aid, user procedure, and Execution log
***Feedback on User Procedure, Must use the User Procedure – validation of changes

## Agenda - Wednesday

| FM/SGL Overview | Cynthia Smith
Chris Krug | 9:00 – 9:30 |
| --- | --- | --- |
| Procurement – Requisitions & Obligations | Cynthia Smith
Joyce Meyer
Vivian Liang (on call) | 9:30 – 10:30 |
| Break |  | 10:30 – 10:45 |
| Procurement – Requisitions & Obligations Continued | Cynthia Smith
Joyce Meyer
Vivian Liang (on call) | 10:45 -  11:15 |
| Cost Management – Cost (SES & GR & 533) | Cynthia Smith
Chris Watson | 11:15 – 12:00 |
| Lunch |  | 12:00 – 1:00 |
| Cost Management – Cost Assessments | Cynthia Smith
Chris Watson | 1:00 – 2:00 |
| Cost Management – Labor & Travel Overview Only | Cynthia Smith
Chris Watson | 2:00 – 2:30 |
| Break |  | 2:30 – 2:45 |
| Accounts Payable – Invoicing & Payment | Cynthia Smith
Doug Clark
Vivian Liang | 2:45 – 3:15 |
| Reimbursable | Cynthia Smith
Doug Clark
Vivian Liang | 3:15 – 4:00 |

**Notes:**
During Procurement – Show the user how to check the SGL for postings completed on the Req, Obligation, & Invoice

## Agenda - Thursday

| Information Delivery – R/3  & BW (ZNASA, etc) | Lisa Huzar | 9:00 – 11:00 |
| --- | --- | --- |
| SIT Tools & Defect Process
Test Director
Requisite Pro
RAT
ProVision | Gwen Diehl
 | 11:00 – 12:00 |
| Lunch |  | 12:00 – 1:00 |
| RIEF Overview (remaining objects) | Marla Lenox
Gwen Diehl
 | 1:00 – 1:30 |
| Center Legacy Systems Testing (Schedule) | Tamara Fields | 1:30 – 2:00 |
| Wrap Up/Next Steps 
Re-Review SIT Pass 2 Schedule
Process Core/Extended Team Travel Schedule | Lisa Huzar
Cynthia Smith
Vivian Liang | 2:00 – 2:30 |

## Appendix A:

**Appendix A:**
**Project Status**

## PMI2 Timeline

**Qtr 1**

**Qtr 4**

**Qtr 2**

**Qtr 3**

**Qtr 4**

**Qtr 1**

**FY2004**

**Qtr 2**

**Qtr 3**

**Qtr 4**

**Agency Go-Live**

**FY2006**

**FY2007**

**FY2005**

**Phase I – Agency-wide**

**Note:**
**Phase I – FY2006 Budget Structure & Technical WBS**
- Must be implemented on a year-end
**Phase II – WBS Expansion**
- Does not have to be implemented on a year-end.
- Assumption: Combined with SAP Version Update project

**Agency Go-Live**

**Phase II – Agency-wide**

**Notes:**

Current Schedule – Level 2-3 
	-Green boxes depict the phase that have occurred or are occurring presently.
	-Milestones should be included

##  Phase I Mid-Level Timeline

**Jan**

**FY05**

**Feb**

**Mar**

**May**

**Jun**

**Jul**

**Sep**

**Oct**

**Nov**

**Apr**

**Aug**

**Dec**

**Final Prep/**
**Go-Live**

**CRP**

**Communications & Change Mgmt**

**Realization**

**Test Case **
**Development**

**Design & **
**Data Mapping**

**Development  & **
**Unit Testing**

**Training**
**Deployment**

**Use Case Dev**

**Blueprint**

- = Workshop participation by OCFO

- = Review by OCFO & OCE

- = Decision point on OCFO Systems

**System Integration Test /**
**Regression Test**

**Production Support**

**Data Mapping**

##  Data Mapping Timeline

**FY05**

**June**

**July 4: Start Weekly POC**
** ****Data Mapping Team Call**

**June 6: Review Data**
**Mapping Approach with **
**OCE & OCFO **

- = Key Deliverable Dates

- = Review by OCFO & OCE

- = Stakeholder Deliverable Due Date

**June 22: Kickoff for **
**Mission Directorates**

**June 28****th****: Critical**
**Design Review (CDR)**

**July 12-14: HQ **
**Institutional Workshop**

**July 18: Mission Directorates**
**Science (2 day)**
**Space Ops (1 day)**

**July 25: Mission Directorates**
**Aeronautics (2 day)**
**ESMD (1 day)**

**Aug. 1****st****: Mission **
**Directorates **
**Deliverable Due Date**

**Aug. 5****th****:  Institutional **
**Center Level Unique **
**Deliverable Due Date**

**Aug 19****th****: PMII Data **
**Mapping **
**Deliverable Due date**

**Sept. 26****th****: CRCS **
**Production Go-Live**

**Sept  2****nd****: Data Mapping **
**provides final **
**extract for CRCS Load**

**July**

**August**

**September**

**October**

**Oct . 10****th****: Final**
**Deliverable Automated **
**Load to SAP**

**Oct 17:  Tentative**
**SAP Go-Live**

**July 15: Institutional **
**Agency Deliverable **
**Due Date**

**June 21: Kickoff for **
**Institutional**
** ****Mission Directorates**

**Aug 22****nd**** – 31****st****: OCE/OCFO **
**Final Review, Final Change **
**Request Disposition**

**July 18: Begin Center Level **
**Unique -Institutional**

**Aug. 10****th****:  Mission **
**Directorate Center Level **
**Deliverable Due Date**

**Aug 1st: Begin Center Level **
**Unique -Programmatic**

**Aug 31****st****:  Agency Account **
** ****Code Freeze**

**Oct  24:  Tentative**
**MdM Go-Live**

**Oct . 21****st****: Final**
**Deliverable Automated **
**Load to MdM**

**Aug 15****th****: Final Submission **
**of  Change Request**

## Appendix B:

**Appendix B:**
**Center Legacy System Impact Summary**

## Legacy Center Impact Assessment Summary of Results

| Center | Impacted | # of Systems Impacted | # of Objects | Comment |
| --- | --- | --- | --- | --- |
| AMES | Yes | 11 | 14 |   |
| DFRC |   |   |   | Not Responded |
| GRC | Yes | 17 | 17 |   |
| GSFC | Yes | 6 | 6 |   |
| HQ | Yes |  10 | 10 |   |
| JSC | Yes | 6 | 8 |   |
| JPL | Yes | 5 | 5 |  |
| KSC | Yes | 1 | 2 |   |
| LARC | Yes | 5 | 5 |   |
| MSFC | Yes | 3 | 3 |   |
| SSC | Yes | 5 | 7 |   |

## Legacy Center Impact Assessment Template Example

**Impact **
**Assessment**

**Listing**

## Appendix C: DCFO Requirement Response

## Appendix D:CRP Test Scenario Listing Results

## CRP Execution Log Listing

| Sort String | CRP Execution Log | NASA Owner | Accenture Owner | Status |
| --- | --- | --- | --- | --- |
| DS01.01 | Master Data Creation | Cynthia Smith | Michelle Smith | Passed |
| DS02.01 | Direct Programmatic Funding - PY05 | Cynthia Smith | John Schremp | Passed |
| DS02.02 | Direct Programmatic Funding - PY06 | Cynthia Smith | John Schremp | Passed with exception |
| DS03.01 | Reimbursable Funding - PY05 | Cynthia Smith | John Schremp | Passed |
| DS03.02 | Reimbursable Funding - PY06 | Cynthia Smith | John Schremp | Passed with exception |
| DS04.01 | Corporate G&A Funding - PY05 | Cynthia Smith | John Schremp | Passed |
| DS04.02 | Corporate G&A Funding - PY06 | Cynthia Smith | John Schremp | Passed with exception |
| DS04.03 | Center G&A Funding - PY05 | Cynthia Smith | John Schremp | Passed |
| DS04.04 | Center G&A Funding - PY06 | Cynthia Smith | John Schremp | Passed |
| DS04.05 | Institutional Investment Funding - PY05 | Cynthia Smith | John Schremp | Passed |
| DS04.06 | Institutional Investment Funding - PY06 | Cynthia Smith | John Schremp | Passed with exception |
| DS04.07 | Agency Fee for Services Funding - PY05 | Cynthia Smith | John Schremp | Passed |
| DS04.08 | Agency Service Pool Funding - PY06 | Cynthia Smith | John Schremp | Failed |
| DS04.09 | Service Pool Funding - PY05 | Cynthia Smith | John Schremp | Passed |
| DS04.10 | Service Pool Funding - PY06 | Cynthia Smith | John Schremp | Passed |
| DS04.11 | Labor Pool Funding - PY05 | Cynthia Smith | John Schremp | Passed |
| DS04.12 | Labor Pool Funding - PY06 | Cynthia Smith | John Schremp | Passed |

## CRP Execution Log Listing

| Sort String | CRP Execution Log | NASA Owner | Accenture Owner | Status |
| --- | --- | --- | --- | --- |
| DS05.01 | Generate SGL Reports | Cynthia Smith | Michelle Smith | Passed |
| DS06.01 | Working Capital Fund SEWP AR - PY05 | Cynthia Smith | Chris Krug | Passed |
| DS06.02 | Working Capital Fund SEWP Budget - PY05 | Cynthia Smith | Chris Krug | Passed |
| DS06.03 | Working Capital Fund SEWP Req to Pay - PY05 | Cynthia Smith | Chris Krug | Passed |
| DS06.04 | Working Capital Fund SEWP AR - PY06 | Cynthia Smith | Chris Krug | Passed |
| DS06.05 | Working Capital Fund SEWP Budget - PY06 | Cynthia Smith | Chris Krug | Passed with exception |
| DS06.06 | Working Capital Fund SEWP Req to Pay - PY06 | Cynthia Smith | Chris Krug | Passed |
| DS07.01 | Working Capital Fund NSSC | Cynthia Smith | Chris Krug | Failed |
| DS08.01 | Investment Funding - PY05 | Cynthia Smith | John Schremp | Passed |
| DS08.02 | Investment Funding - PY06 | Cynthia Smith | John Schremp | Passed with exception |
| DS09.01 | GAD Funding - PY05 | Cynthia Smith | John Schremp | Passed |
| DS09.02 | GAD Funding - PY06 | Cynthia Smith | John Schremp | Passed with exception |
| DS10.01 | Miscellaneous Funding - PY05 | Cynthia Smith | John Schremp | Passed |
| DS10.02 | Miscellaneous Funding - PY06 | Cynthia Smith | John Schremp | Failed |

## CRP Execution Log Listing

| Sort String | CRP Execution Log | NASA Owner | Accenture Owner | Status |
| --- | --- | --- | --- | --- |
| CC01.01 | Reimbursable Agreements Federal - PY05 | Cynthia Smith | Chris Watson | Passed |
| CC01.02 | Reimbursable Agreements Federal - PY06 | Cynthia Smith | Chris Watson | Passed |
| CC01.03 | Reimbursable Agreements Non-Federal - PY05 | Cynthia Smith | Chris Watson | Passed |
| CC01.04 | Reimbursable Agreements Non-Federal - PY06 | Cynthia Smith | Chris Watson | Passed |
| CC02.01 | Direct Accounts Receivable - PY05 | Cynthia Smith | Chris Watson | Passed |
| CC02.02 | Direct Accounts Receivable - PY06 | Cynthia Smith | Chris Watson | Passed |
| CC03.01 | Commercial Contract Supply - PY05 | Cynthia Smith | Joyce Meyer | Passed |
| CC03.02 | Commercial Contract Supply - PY06 | Cynthia Smith | Joyce Meyer | Passed |
| CC03.03 | Commercial Contract Service - PY05 | Cynthia Smith | Joyce Meyer | Passed |
| CC03.04 | Commercial Contract Service - PY06 | Cynthia Smith | Joyce Meyer | Passed |
| CC03.05 | Commercial Contract Supply & Service - PY05 | Cynthia Smith | Joyce Meyer | Passed |
| CC03.06 | Commercial Contract Supply & Service - PY06 | Cynthia Smith | Joyce Meyer | Passed |

## CRP Execution Log Listing

| Sort String | CRP Execution Log | NASA Owner | Accenture Owner | Status |
| --- | --- | --- | --- | --- |
| CC04.01 | Grants Processing - PY05 | Cynthia Smith | Joyce Meyer | Passed |
| CC04.02 | Grants Processing - PY06 | Cynthia Smith | Joyce Meyer | Passed |
| CC05.01 | IDIQ Contract - PY05 | Cynthia Smith | Joyce Meyer | Passed |
| CC05.02 | IDIQ Contract - PY06 | Cynthia Smith | Joyce Meyer | Passed |
| CC06.01 | Month end Processing-Cost Pool Allocations - PY05 | Cynthia Smith | Chris Watson | Passed |
| CC06.02 | Month end Processing-Cost Pool Allocations - PY06 | Cynthia Smith | Chris Watson | Passed |
| CC07.01 | Straight Line Accrual Processing - PY05 | Cynthia Smith | Chris Watson | Passed |
| CC07.02 | Straight Line Accrual Processing - PY06 | Cynthia Smith | Chris Watson | Passed |
| CC08.01 | FI Invoices - PY05 | Cynthia Smith | Joyce Meyer | Passed |
| CC08.02 | FI Invoices - PY06 | Cynthia Smith | Joyce Meyer | Passed |
| CC09.01 | Travel Processing - PY05 | Cynthia Smith | Joyce Meyer | Passed |
| CC09.02 | Travel Processing - PY06 | Cynthia Smith | Joyce Meyer | Passed |
| CC10.01 | De-obligate a COCD complete line item | Cynthia Smith | Joyce Meyer | Passed |

## Appendix D:Other SIT Details

## SIT Terminology

- Test Set
- A series of Test Plans linked together to represent an end-to-end business process
- Test Plan
- Represents specific business functionality to be tested.  All steps, expected and actual results are recorded within the Test Plan
- Defect
- A defect results when the actual results differ from the expected results.  Defects will be tracked directly in Test Director