1. OFFICE OF FINANCIAL MANAGEMENT 0 Office of Financial Management Office of Financial Management BASS Budget Officers May 1, 2002

2. OFFICE OF FINANCIAL MANAGEMENT 1 Agenda 1.Status of BASS Spring 2002 Release. 2.BASS Next Steps 3.Salary Projection System 4.Performance Measures 5.Allotments Planning 6.Development Schedule

3. OFFICE OF FINANCIAL MANAGEMENT 2 Status of BASS Spring 2002 Release  BDS Significant improvements in the BASS Reporting System (BRS) BDS Reports: BDS 1 and BDS 3 modifications complete. Two new reports: Recommendation Summary Report and the Fund and FTE Detail Report in testing phase. Development of a Multi-Year Decision Package. Supports 6 year transportation plan and bow wave preparation. Two new MYP reports in development phase.

4. OFFICE OF FINANCIAL MANAGEMENT 3  BDS Improved Decision Package priority setting. Implemented Decision Package and Version locking. Feature to close one Decision Package and open another in a single step. Ability to select a fund or object code from list without first entering an invalid one. Various bug fixes.  PMTES New B11 report format. Added functionality to run B11 report for agency internal measures. Status of BASS Spring 2002 Release (Continued)

5. OFFICE OF FINANCIAL MANAGEMENT 4  CBS – production release in Mid-May Improved overall performance. Eliminated CBS C100 and integrated new Excel C100 summary information. The new Excel C100 is now available on the OFM web site at http://www.ofm.wa.gov/capitalforms/excel inst.htm Support for Project ID editing and improved Project priority setting. Improved legislative district coding. Status of BASS Spring 2002 Release (Continued)

6. OFFICE OF FINANCIAL MANAGEMENT 5 BASS Next Steps  Modifications and enhancements to BASS Data Release System. Ability to release 2 nd Year Estimates.  Access to AUTO through Fortress.  Implementation of hardened passwords for BASS usage.  Implementation of server load balancing.  Single sign-on pilot participation.  Salary Projection System prototype.

7. OFFICE OF FINANCIAL MANAGEMENT 6 Salary Projection System (SPS) Targets:  Deliver a prototype for evaluation in Fall 2002.  Deliver a production system with core features in June 2003.

8. OFFICE OF FINANCIAL MANAGEMENT 7 Salary Projection System (SPS) (Continued) Risks: Requirements validationDOP Data Warehouse data issues Meeting unique business requirements Collective Bargaining Core release featuresResources for design/development New development may not be more usable than current BPS1 New technology opportunities Customer understanding of salary projection process and training needs

9. OFFICE OF FINANCIAL MANAGEMENT 8 Salary Projection System (SPS) (Continued) Customer Prioritization Exercise Completed Customers ranked features based on: Relative benefit if feature included Relative penalty if feature omitted BASS team ranked features based on: Relative cost of developing Relative risk in developing and testing

10. OFFICE OF FINANCIAL MANAGEMENT 9 Results: Top Ranked Features Salary Projection System (SPS) (Continued)

11. OFFICE OF FINANCIAL MANAGEMENT 10 Results: Top Ranked Features Salary Projection System (SPS) (Continued)

12. OFFICE OF FINANCIAL MANAGEMENT 11 Salary Projection System (SPS) (Continued) Position Listing

13. OFFICE OF FINANCIAL MANAGEMENT 12 Salary Projection System (SPS) (Continued) Position List and Copy Filtering

14. OFFICE OF FINANCIAL MANAGEMENT 13 Salary Projection System (SPS) (Continued) What agencies can do to verify that the design will meet unique business requirements:  Participate in “Use Case” development workshop  Evaluate SPS prototype using developed use cases

15. OFFICE OF FINANCIAL MANAGEMENT 14 Performance Measures Current Picture : Agency PM business processes are at different states of maturity. PMTES is a compliance tool to submit measures to OFM. Agencies want to improve their performance management reporting capability. Agencies vary widely in the degree of integration of budget, planning and performance measurement. Agencies use a variety of tools to report performance – most common tool is Excel.

16. OFFICE OF FINANCIAL MANAGEMENT 15 Performance Measures (Continued) Next Steps - OFM will be discussing strategies in the following areas: Flexible tools for reporting Common coding Improved cost accounting  Connecting measures to dollars  For activities

17. OFFICE OF FINANCIAL MANAGEMENT 16 Allotments Planning Where are we? OFM has started discussions on the vision for a new Allotment System. Identified problem areas of the current allotment process. Decision was made to step back and take a look at what the objectives of the allotment process should be. First Step – OFM will begin internal discussions to define objectives for the allotment process.

18. OFFICE OF FINANCIAL MANAGEMENT 17 Development Schedule

19. OFFICE OF FINANCIAL MANAGEMENT 18 Next Meeting September 18, 2002 1:30-5:00 p.m. Point Plaza 1st Floor Training Room ____________________________________