# Presentation: 167384

**Kansas City Customer Advisory Board**
**June 7, 2006**

***Will Your Agency be Ready?***

**Notes:**
FMS had not changed the accounting process for more then the past 25 years.  Using the Central Accounting System known as STAR
We felt that we needed to look at this basic process and see if we can improve it.
Due to accelerated reporting (3 day close, etc)
The GWA Modernization Project is one of FMS’ top priorities.  It will impact not only the way the Government will do accounting, but will impact all of the systems we use to collect and disburse Government funds.

Overview
The Governmentwide Accounting and Reporting Modernization (GWA) Project addresses:
 the central accounting and reporting functions and processes associated with
budget execution, 
accountability, and 
cash/other asset management. 
This includes the collection and dissemination of financial management and accounting information 
from and to federal program agencies. 
It also includes the business processes in FMS that are related to ledger accounting for each:
 appropriation, 
fund, and 
receipt account's Fund Balance with Treasury (FBWT), 
General Ledger accounting for the cash and monetary assets of the Government, 
and the preparation of the Monthly Treasury Statement and the U.S. Government Combined Statement and Appendix. 

In addition, GWA will improve information timeliness and accuracy to support improved financial analysis and decision-making.

## Massive redesign of Federal Government Central Accounting process

Affects every federal agency; over 1,700 reporting locations (domestic and foreign)

Changes over 40 years of agency business practices

Many system interfaces

**Affects every federal agency; over 1,700 reporting locations (domestic and foreign)**
**Changes over 40 years of agency business practices**
**Many system interfaces**

**What is the GWA Modernization Project?**

## Current Reporting Flow

- COMBINED
- STATEMENT,
- SOD,
- Undisbursed, etc

- Federal
- Program
- Agencies

- Source
- Systems

- S
- T
- A
- R

- 224, 1219/1220, 1218/1221, etc. .(monthly)

- Payments
- Collections
- GOALS II, FRB
- CASHLINK (ATS),
- IPAC etc.

- Transactions (daily)

- G2

- State, DOD, monthly reporting

- GWA

- Account
- Statement

- Reclassify

**Current Reporting Flow**

## Future GWA Reporting Flow

**Future GWA Reporting Flow**

- Federal
- Program
- Agencies

- Source
- Systems

- S
- T
- A
- R

- Reclassification

- Payments
- Collections
- GOALS II, FRB
- CASHLINK (ATS),
- IPAC etc. (sent daily)

- MTS,
- COMBINED
- STATEMENT,
- Account Statement,
- etc

- Transactions classified daily

- GWA

##  GWA Modernization – Time for Change

** ****GWA Modernization – Time for Change**

**  ****Evolution – What have we grown into?**
- The current accounting and reporting process has become Inefficient, Outdated, and Untimely. (IOU)
-   **Present Day Requirements –  Time to pay off the IOU.**
- Accelerated Reporting Requirements
- President’s Management Agenda - Scorecard
- Audited Financial Statements
-   **The Future – Unknown....But we’ll be ready.**
- Consolidated, web-based system for the collection, processing, reporting, and storage of all financial information.

**Notes:**
Evolution:
 - Over the years we have tallied up an enormous IOU with our Agencies.
 - Reference the current way of doing business to highlight the inadequacy of our current practices:
 - Inefficient – Two Step Classification
 - Outdated – Why, in an internet based business world do our users have to utilize multiple financial systems to both report and obtain their financial information?
			GOALS II / IAS
			CASHLINK
			IPAC
			RFC Agency Link
 - Untimely – Reference the delays associated with our current reporting processes (Undisbursed/SOD)

Present Day Requirements:  We are now forced to pay off this IOU
 - Elaborate on some of the major initiatives that sparked and continue to drive the development of the GWA System
	Accelerated Reporting – The original and primary driver.
	President’s Management Agenda – Scorecard – this is on the mind of all Federal Financial Managers.  GWA will help them to meet the requirements of the Agenda while simultaneously improving their scores.
	Audited Financial Statements – Movement from annual to quarterly  perhaps even monthly (Also may mention the inherent benefits to the daily, monthly, quarterly, annual reconciliation processes that feed the financials)

The Future:
 - Discuss the original goal of GWA to be the “one stop shop” for all Financial Reporting needs

## GWA Key Goals/Objectives

**Eliminate the two step classification process**
- 	    Capture the Treasury Account Symbol (TAS) and Business 	Event Type Code (BETC) at the earliest possible time for 	agency payment, collection and intragovernmental transactions 	and post directly to the fund balance with treasury.
**Provide timely and accurate accounting information**
**Eliminate redundant reporting**

**Notes:**
Currently all collections, payments and intragovernmental transactions are reported at the Agency Location Code level on a daily basis.  Then, classifications to a Treasury Account Fund Symbol are reported monthly on the FMS 224.

The GWA Modernization Project will allow agencies to classify to a TAS/BETC on a daily basis at the initiation of a collection, payments or IPAC transaction.

FMS will provide agencies with timely information on an account statement that will be updated daily.  Agencies will be able to reconcile their fund balance with Treasury on a daily basis.

Explain 2 step (provide timing and accurate reporting / capture information at time of transaction verses at end of month)

Eliminate 224 and sod

Replace 6653 with daily account statement

## Fundamental Changes to the current process
Developed a New Database
Developing the infrastructure to Support GWA Players
ATM, Account Statement, CAFÉ, P224, SAM, IPAC, Collections, Payments
Automated Enrollment – User-based Access Control
Phase in GWA Players
Authority Transactions, IPAC, Payments, and Collections
Streamline GWA’s Architecture
Provide Agencies with GWA initiated Account Statement
Support NTDO GWA Players
Fully Replace Legacy Accounting System

- Developed a New Database
- Developing the infrastructure to Support GWA Players
- ATM, Account Statement, CAFÉ, P224, SAM, IPAC, Collections, Payments
- Automated Enrollment – User-based Access Control
- Phase in GWA Players
- Authority Transactions, IPAC, Payments, and Collections
- Streamline GWA’s Architecture
- Provide Agencies with GWA initiated Account Statement
- Support NTDO GWA Players
- Fully Replace Legacy Accounting System

**How is GWA going to accomplish this?**

**Notes:**
Fundamental Changes – 3 Major Ones that tie into the overall objectives of the Project mentioned on the prior slide
	-  TAS / BETC
	-  Account Statement
	-  Elimination of Redundant Reporting through implemented components and core functionality (TAS/BETC, IPAC Changes, P-224)

New Database
	-  Consolidation of STAR Database, enhanced to handle new data (TAS/BETC, Reporters), based at TWAI
	-  New GWA Oracle database 
		-  Enhanced for flexibility, reporting capability, and performance

New Infrastructure for Players
	-  Components/Modules implemented sequentially to provide phasing in of players and functions

Phase in GWA Players
	-  Permits transition by function, feeder system, and reporting mechanism

Streamline Architecture – Overall new web interface for users
	-  TWAI – Consolidation of functionality to web based portal
	-  Enterprise Single Sign-On – seamless integration of access controls to various FMS systems (FMS-Portal)

Account Statement – GWA Initiated
	-  Daily refreshed information from TWAI-based GWA database
	-  Will facilitate the creation of the GWA Unofficial Account Statement in 2007 providing immediate benefit to GWA Players

NTDO Players
	-  2+ years
	-  Conversations with DOD are occurring

Replace STAR

## User Enrollment

- Web-based user enrollment – links available on the GWA website and will be available on the GWA System login page by the end of this month
- Certifying supervisors must be enrolled first paper process
- User enrollment time frame has been reduced from 2-3 weeks to 2-3 days
- Agency users will also be able to reset their own passwords
- All Account Statement users are currently in the user provisioning system
- Current Release1 users (approx. 1200) will start enrolling for ATM beginning in June.

## TAS Definition

- Acronym for Treasury Account Symbol (TAS)
- The receipt, appropriation, expenditure and other fund account symbols and titles as assigned by the Department of the Treasury
- A 27-character field – with 24 currently identified characters
- Supercedes 21 position TAS and any other suggested formats

**   ****GWA Standard Transaction Classification**

**Notes:**

27 field = 7 concatenated (all fields joined, no blank spaces) field of 7 separate elements

The main difference is the elimination of standard subclasses. This means that FPAs will report an account symbol, without having to report subclassification of that account based on explicit transaction types (such as borrowings, investments, funds held outside treasury). Instead of the transaction type being reported as a standard subclass on the account symbol, it will be reported as a business event separate from the account symbol. For example, if you invest in Treasury securities, you currently report subclass 88 on your account symbol: (88) 20x1234. In the GWA environment, you will report the account symbol 20x1234 and a separate business event type code (BETC) of INVTSEC.

The subclass field will continue to be used for those TAS in which there is a unique meaning or a unique need for subclassification that is NOT based on transaction types.

In addition, the department/agency codes are currently only 2 digits, but we are allowing for the expansion to 3 digits in the future. 

## BETC Definition

- Acronym for Business Event Type Code
- An 8-character code that indicates the type of activity being reported (e.g. receipt, disbursement, etc)
- BETC determines the transaction effect on the Treasury Account Symbol’s FBWT.
- BETC replaces transaction codes and standard sub-classes but at a more intuitive level of detail

** ****GWA Standard Transaction Classification**** ****(cont)**

**Notes:**
standard sub-classes  
not unique to agencies 
 identified/set by FMS

Gross Disbursement   DISB
Gross Disbursement for Budget Clearing Accounts   DISBBCA

What is a BETC?
The BETC is an 8 character code used in the GWA system to indicate the type of activity being reported, such as payments, collections, borrowings etc. This code must accompany the Treasury Account Symbol (TAS) and the dollar amounts in order to classify the transaction against the fund balance with Treasury.

BETC in effect replaces the transaction codes and standard sub-classes that are currently used on the central accounting reports, such as those used on the Statements of Transactions (FMS Form 224) and the Undisbursed Ledger and Trial Balance Reports (FMS Forms 6653 and 6654).

How many are there?
There are approximately 250 BETCs currently identified in the GWA system. About half of those BETCs are related to Non-Expenditure, Borrowing, and Warrant transactions. Since those types of transactions are processed directly in the GWA system through their applicable GWA modules, those BETCs are automatically assigned behind the scenes within each GWA module.
The other half of the BETCs are related to Payment and Collection transactions. Those BETCs will be reported through interfacing systems, such as IPAC. This means that agencies will be required to provide those payment and collection BETCs when reporting transactions through the interfacing systems. 
What are the BETCs agencies need to know?
Click here to display BETCs applicable for payments and collections. The explanation of each column follows:
BETC: the 8 character code identifying the business event.
Business Events/Activity Types: the title or short description of the business event type code. These titles will appear in the Account Statement, Transaction level screens. The intent is to provide a better, more intuitive description of the transaction being displayed, as opposed to the current numeric codes.
Debit/Credit Impact on TAS: determines whether the BETC will have an increase effect (Credit) or a decrease effect (Debit) on the TAS' fund balance with Treasury.
Account Statement Category: tells which category a BETC would be displayed within the Account Statement (AS) application. These categories parallel or tie back to the same line items on the original Undisbursed Trial Balance Report (SF 6654), with one exception -- the Net Disbursements on the SF 6654 is now broken out between Gross Disbursements and Offsetting Collections on the AS.
Undisbursed Trans Code (TC) and Subclass (SC): codes that are used in the current processing of transactions via Treasury's central accounting system (STAR) and currently being presented on the Undisbursed Ledger Report (SF 6653). These 2 columns are presented as a crosswalk between each new BETC in GWA to its corresponding old TC and SC in STAR. 

## Shared Accounting ModuleSAM

**Notes:**
Begins implementation of overall concept.

Pilots and first players will be ALC’s that only report IPAC activity

Easy implementation/proof of concept. 

Firms up the infrastructure that we’re building

##  SAM

-     to all transactions entering the GWA System
-   **Developed to assist agencies** in complying with GWA
-     standard transaction classification
-   **GWA will provide** SAM with a table of **valid TAS/BETCs**
-   **Agencies will define** in SAM valid TAS/BETCs for:
-  Default rules and
-  Classification (Ckey) translations

** ****SAM**

##  SAM

**CAFE will send SAM transactions with:**
-  TAS/BETCs or
-  CKeys
**SAM will:**
- Validate TAS/BETC or
- Derive valid TAS/BETC from Ckey or
- Default a valid TAS/BETC
- Return transactions to GWA w/valid TAS/BETC.
- Provide valid TAS/BETC reference lists for Agencies

## IPAC Impact

**Notes:**
Begins implementation of overall concept.

Pilots and first players will be ALC’s that only report IPAC activity

Easy implementation/proof of concept. 

Firms up the infrastructure that we’re building

## IPAC – Agency Impact

- IPAC added new fields to collect both the sender and receiver TAS/BETC on every detail record
- All IPAC transactions will be required to have both sender and receiver TAS/BETC’s
- A TAS/BETC list for IPAC is available on the IPAC/GWA web pages
- F Accounts are not Valid for use in IPAC; exceptions for 3880 and 3887.

**Notes:**
Pilot agencies have been selected and will be ready to test the GWA Way early next year.

One ALC from:
	Fed Finance
	BPD
	GPO
	IRS

2Q06 – Required for both partners when one is  GWA Player
3Q06 – Required for all 

## IPAC – Agency Impact

- Must work with your trading partners – Now
- Pilots – Effective May 1, 2006
- All Agencies – Effective August 1, 2006.
- Transition to a Single TAS format instead of the 6+ formats available today – TBD
-  F-Account Issue

**Notes:**
Pilot agencies have been selected and will be ready to test the GWA Way early next year.

One ALC from:
	Fed Finance
	BPD
	GPO
	IRS

2Q06 – Required for both partners when one is  GWA Player
3Q06 – Required for all 

## Partial 224Agency Implementation

**Notes:**

Allow easy implementation for agencies and still capture information FMS needs.
Web based environment  vs.  GOALS on Citrix boxes via Secure ID

Will allow agencies to become GWA reporters and report only sections that are not being reported the GWA way.

Provides incentive and return on investment to GWA Players

## Partial 224

**Web based application**
- Ability to turn off sections of the P224
- Provides for reclassification capability by using only section I of the P224**.**
**    ****GWA Reporters by:**
- ALC
- Source system
- Categories

**Notes:**
This is what we want to focus on today – is the P224
Report sections remain the same.

Reporters – are agencies that report proper GWA Classification by System:  Intro gov = IPAC, Collections = Cashlink

BY SOURCE SYSTEM:
ALC  REQUIREMENT -  (Milissa will go over)  IMPORTANT need to know which ALC is GWA reporter/not a reporter

SOURCE SYSTEM:  IPAC (Intragovernmentals)  Section 2
 Collections  (All CashlinkII) – Section 3  List from Requirement Document
Payments – Section 2
 Classification and Reclassification of Transactions – Section 1

The transactions that are reported the GWA way – do NOT get reported on the partial 224

Categories 
Turn off sections as needed 

Categories: 7 next slide

AND which transactions are GWA transactions

## Partial 224  (cont.)

- GWA Reporter Categories
- 1.    Intragovernmental Only
- Collections Only
- Payments Only
- Intragov and Collections
- Intragov and Payments
- Payments and Collections
- Full GWA Reporter:  Intragov, Collections & Payments

**Notes:**
WALK THRU CHART - Refer them to the chart in their vendor information package – Page 2.

Very important – new requirement to be able to accommodate each category for each ALC that becomes a GWA Reporter

Review each category (turning off)

Section I – problem can double report thru “classification” function if txn are reported the GWA way and counted thru GWA system AND Partial 224.

When we test with Vendors, All Categories will be tested

## Reporting Scenario

**ALC #1  =  GWA REPORTER – Intra-governmental**
- Transactions are classified with TAS/BETC when submitted
- Transaction posted thru GWA to STAR
- IPAC Transactions will not be reported on P224
- Report Payments – section II
- Report Collections – section III
- Report Section I for Payments & Collections classification ONLY
- 	and any reclassified transactions (incl. IPAC)
**ALC #2 =   NON-GWA Reporter **
- Transaction will need TAS/BETC when submitted
- Transaction posted to STAR
- Agency will still classify on their SF224 at end of month
- Continue to use current 224

**Notes:**

GWA will track REPORTER

REPORTER

GWA – w/TAS- BETC

NON – current way of reporting transactions

GWA will create 224 for IPAC and send to legacy system (interim process)

## GWAAccount Statement

## The GWA Account Statement

**The GWA Account Statement**

**Definition:**
- An online, daily refreshed, query based application designed to provide each Federal Program Agency with a central location for retrieving information relating to its Fund Balances with Treasury.** **
**Objective:**
- Designed to assist Agencies with their reconciliation processes.
- Replaces the Monthly Undisbursed Ledgers and Trial Balance reports. (FMS – 6653, 6654, 6655)
- Effective June 30, 2006
**Benefits:**
- Access – Online at the Department level
- Timeliness – Refreshed daily
- Flexibility – Full query capability at both TAS and ALC level
- Clarity – Clear description of balance and transaction data

## The GWA Player

Membership Has Its Advantages

**Membership Has Its Advantages**

**Notes:**
Faster information
Reduced reporting 
More time to analyze problems
Cost savings due to reduced reconciliation problems
Improved data integrity (completeness) (IPAC example) – No SOD’s

## GWA Player

** **

**  ****GWA Available Components and User Benefits:**
- Account Statement
-   Daily Fund Balance with Treasury for reconciliation
- Release 1 (BPD)
-   Borrowing from Treasury
-   Non-Expenditure Transfers
-   Warrant Journal Vouchers
- IPAC – Daily consolidated file with TAS/BETC
-   Introduces Users to GWA reporting requirements
-   Begins to migrate reporting functionality to GWA (TWAI)
- Self Enrollment
-   Web based enrollment to GWA with password self-maintenance

**GWA Player**

**Notes:**
Account Statement:
	-  New enhancement that combines Gross Disbursements and Offsetting Collections into NET OUTLAYS figure for FACTS II Reporters
	-  Undisbursed sunset June 2006

Release 1:
	-  Transfer to TWAI as part of ATM in August 2006

IPAC Daily File:
	-  GWA (Café) accumulates daily information and executes month-end transmission to STAR on behalf of IPAC. 
	-  Transfer of data collection and transmission path to GWA
	-  No data validation

Self Enrollment
	-  Eliminates paper forms
	-  Decreases access waiting period
	-  Places control of password maintenance in user’s hands
	-  Decreases the role of FMS in the granting of access and places more responsibility in the hand’s of the Agencies (Supervisors)

## GWA Player – Second Quarter 2006

** **

**  ****GWA Available Components and User Benefits:**
- Shared Accounting Module (SAM) – Proof of Concept
-   IPAC TAS/BETC Validation with Pilot ALC’s
-   Public Website for downloading valid TAS/BETC file
- Official IPAC Pilot
-  FMS, IRS, GPO, BPD
-   No SF-224 submission
-   No Statements of Difference

**GWA Player – Second Quarter 2006**

**Notes:**
SAM – Proof of Concept
	-  Begin utilizing SAM for validation purposes.
	- SAM Available to GWA Users to obtain TAS/BETC download file for use in their internal systems and accounting shops

IPAC Pilot
	-  First test of the full cycle for GWA Player
	-  IPAC transactions with TAS/BETCs, validation
	-  No more 224 or SOD for Pilots

## GWA Player – Third Quarter 2006

** **

**  ****GWA Available Components and User Benefits:**
**GWA User – Official Implementation**
-   No SF-224 submission
-   No Statement of Differences
**Café 1.3 – Full Utilization**
-   Acceptance of daily transactions with TAS/BETC validation and processing
**Authority Transactions Module – August 2006**
-   Implements Warrant Journal Vouchers functionality
-   Transitions Release 1 components from BPD to TWAI
**Partial 224 Rollout to multifaceted Pilot ALC’s**
-   IPAC – New “GWA Way” of reporting
-   Payments/Collections – Old 224 reporting

**GWA Player – Third Quarter 2006**

**Notes:**
GWA User
	-  Doors open for non-pilot IPAC only ALC’s

Café 1.3 – Full Utilization
	-  Although it’s been in PROD since March, this is when the full functionality will begin to be used by non-Pilot ALC’s

ATM
	-  New Warrant JV functionality
	-  Gets us off BPD platform and consolidates GWA Production Components at TWAI

P-224 Rollout for ALC’s containing more than just Pilot ALC’s with IPAC only activity

## GWA Player – 2007

** **

**  ****GWA Available Components and User Benefits:**
- GWA “Unofficial” Account Statement
- Daily updated view of Fund Balance with Treasury showing impacts of “GWA Way” submitted transactions with TAS/BETC

**GWA Player – 2007**

**Notes:**
GWA Initiated View
	- Next day display of Fund Balance With Treasury impact of GWA Player reported activity

## GWA Player - Payments

**Modifications to SPS and PAM**
- 100 TAS/BETC’s per Payment - Tentative
- 100 TAS/BETC’s per Schedule – Tentative
**Routine to roll up Bulk File data by TAS and Amounts**.
**Out of Balance Reports**** **
**Aftermath**** **
**Level of Detail on Account Statement**
- Payment level or Schedule level
- Cost/Turnaround time

## The Cheat Sheet

- Sunset of the Undisbursed Application – June 30, 2006
- New User enrollment process – Available Now
- Valid TAS/BETC’s on all IPAC Transactions – August 1, 2006
- Must user Proper TAS/BETC
- Proper classification will be a must!!
- More control over TAS’
- Implementation of ATM – August 2006
- Look at upgrading your COTS Package or Modify your Legacy system
- Vendors have Passed first round of changes (P224)
- Valid TAS/BETC’s on all Payment Transactions – Begins mid 2007
- 100 TAS/BETC’s per Payment
- Valid TAS/BETC’s on Collection Transactions – 2008
- Implementation of GWA Initiated Account Statement - 2007
- Review your systems and process that are based on monthly processing and determine how to do business by reporting TAS/BETC’s daily on each transaction

## GWAMP Roll out Strategy

**Objective:**
- To transition Federal Agencies from their current month end classification process to a daily classification of all Payment, Collection and Intra-governmental transactions at the point of initiation.

**Notes:**
This strategy will provide a high level plan that will transition Federal Agencies from their current process for transaction classification from a monthly basis to a daily classification, point of initiation process.  IPAC will be the first feeder system which will require Treasury Account Symbol/ Business Event Type Code on each transaction.

## GWAMP Roll out Strategy

**  ****Background**
- Agencies use various Accounting packages to reconcile and report transactions.
- Education
- Single FMS integrated system to process all accounting transactions on a daily basis

**Notes:**
Depending on the agency, agencies use various accounting packages from COTS to home grown systems to support their accounting needs.  Will work with FISO to identify agencies currently using COTS packages and work with those agencies to bring them up as they upgrade their systems.
FMS, specifically GWA, will need to continue to work with the Federal Agencies, with the Agency Outreach group, to educate and assist in changing the way they currently process there transactions.  This will impact all the Payment, collection and Intra-governmental systems at FMS and thus, impact all the agencies using these systems.  It will be critical to the successful implementation and rollout to continue to meet with agencies throughout the process.  We are working with Regional Operations to identify the changes that will be necessary to payment systems to support GWA. 
The ultimate goals for GWA are to 1) eliminate the redundant reporting for agencies; 2) provide one location, Account Statement, that agencies can access to see their ongoing balance for all accounting transactions and to provide a real time tool for reconciling their Fund Balance With Treasury.  

## GWAMP Roll out Strategy

| Brief OMB | January 2006 |
| --- | --- |
| FISO Partial 224 Testing with Vendors | Jan. – April 2006 |
| Brief FMS Senior Management | March 2006 |
| Implement P224 and CAFÉ 1.3 | March 2006 |
| Brief OFAS | April 2006 |
| Brief GWAMP Partnership Council | April – May 2006 |
| Begin GWA/IPAC Pilot | May 2006 |
| Brief CFO Council | May 2006 |
| Identify Roll Out team | May 2006 |

**Notes:**
GWA briefed Linda Combs Staff on January 6th on the GWA Project and the expectations.  Linda and her staff were supported of our effort and it tied very closely with Linda’s opinion of the changes needed.  Reporting and classifying transactions at the point of initiation helps support accelerated reporting and eliminates redundant reporting for agencies and moves towards eliminating the Statement of Differences.
We have been working closely with FISO and have had several sessions with the Vendors to ensure they understand and incorporate GWA requirements in their S/W to support the rollout of GWA.  To date, SAP has successfully tested and been certified with the other vendors scheduled to completed testing by the end of April 06.
Though FMS Senior management is well aware of the progress of the project, the project touches many area’s within FMS (FF, RO, Debt) and we need to ensure that everyone understands the timelines and the expectations of each group.  The Agency Outreach group has participants from each of these areas but we need to ensure we have buy off at the senior level.
With the Implementation of the Partial 224 and CAFÉ 1.3, we are now prepared to begin our proof of concept with the pilot agencies (BPD, GPO, IRS, FMS) and move them into production quickly after the successful pilot.  Partial 224 will be the transition tool agencies use instead of the current 224 to classify transactions not being classified to GWA on a daily basis and to reclassify erroneous transactions.  CAFÉ 1.3 provides the infra-structure to support the GWA IPAC players in production.
Need to ensure the OFAS in on board with our strategy for the roll out.  Today’s briefing may take the place of an official briefing.  In that case, we’re ahead of schedule.
Brief the GWAMP Partnership Council on the roll out strategy and identify any issues this may have for our customers.  We expect to have these meetings 3 times a year.
The IPAC Proof Of Concept or Pilot will begin on May 1st with our IPAC pilot agencies providing the TAS/BETC for both sender and receiver on all their IPAC transactions.  FMS will collect the daily transactions and at the end of the month will compare what is reported on the agencies 224 to what we have in GWA.  If after 2 months, we have a clean process we plan to move our pilot agencies into production.  At that point, those agencies will use the Partial 224 for reclassification only and will not longer have to report a 224 as GWA will be submitting their IPAC transactions to STAR for them.  We will at that point begin to accept other agencies to become GWA IPAC players and go thru a similar process.
It is critical to ensure that the CFO’s are aware of our roll out strategy to ensure that they are prepared to support our efforts.
We will need to identify and develop a diverse roll out team.  This team will need to have a single point of contact to provide direction but will need to include not only project members but also representatives from IPAC, the Payment and collection area’s as we move forward.  

## GWAMP Roll out Strategy

| Work with OMB/OFAS to develop letter to FPAs | May - June 2006 |
| --- | --- |
| Decommission Undisbursed applications (6653, 6654,6655 | June 2006 |
| AGA Presentation/FMS/GWA Agency Forums | June – August 2006 |
| Implement ATM; Decommission BPD IAS applications  | August 2006 |
| Update TFM Bulletin to coincide with OMB/OFAS letter to FPAs | August 2006 |
| Pilot and implement a mult. GWA player (IPAC GWA way, collections, payments old way. | Sept. – March 2007 |
| Continue Education  | September – May 2007 |
| Begin Payment Pilots | March 2007 |
| Complete IPAC GWA Roll Out for TDO’s | October 2007 |

**Notes:**
Linda Combs has agreed to work with us in supporting the implementation of the GWAMP effort.  With this in mind, we plan to begin working with Hans Heidenreich of Linda’s staff to begin developing a letter to agencies that will provide information, direction and support for the GWAMP effort.  The letter will need to ensure that agencies understand the importance of moving into the GWA environment as quickly as possible.  (See SAP email)
Undisbused (6653, 6654, 6655) will be retired on June 30th.  Agencies will use the Account Statement to reconcile their accounts.
As part of the education process, GWA will be speaking and exhibiting at various conferences and meetings during the summer.
With the implementation of the Authority Transfer Module (ATM) FMS will turn off the IAS application at BPD for Warrants, Net Expenditure Transfers, and Borrowings.  ATM will reside on the same platform as the other GWA applications, as well as, IPAC, ASAP, PAY.GOV, etc.
FMS will need to develop a TFM to provide direction and guidance to agencies for the new GWA reporting requirements.
After successfully implementing the IPAC pilot agencies, we have had discussions with these agencies about bringing on some of their other ALC’s that report IPAC the GWA way but Payments and Collections still on a monthly basis.  They have been very open to the possibility.
The current plan is to begin a payment pilot sometime in the 1st calendar quarter of 07. We have identified 4 pilot agencies ( RRB, NASA, OPM and Denali comm.) that have agreed to pilot.  
Though Aggressive, we hope to complete bringing up all the TDO IPAC agencies on GWA by the end of FY 07