1 / 56

Steering Committee Meeting Sunflower Project Statewide Financial Management System Update

Steering Committee Meeting Sunflower Project Statewide Financial Management System Update. May 14, 2010. Today’s Topics. Project status and activities – Kent Setting Expectations – Kent Change control – Peggy Cutover Strategy – Peggy Remaining Scope, Data Warehouse,

gudrunt
Download Presentation

Steering Committee Meeting Sunflower Project Statewide Financial Management System Update

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript


  1. Steering Committee MeetingSunflower ProjectStatewide Financial Management System Update May 14, 2010

  2. Today’s Topics • Project status and activities – Kent • Setting Expectations – Kent • Change control – Peggy • Cutover Strategy – Peggy • Remaining Scope, Data Warehouse, Agency Reporting Needs, Executive Dashboards, End User Testing, Production Support Model and Agency Interactions – Gary • Production Support Model – Gary • Shared Service Center – Pam Fink • Training Update – Connie • Agency Readiness and Up Coming Events – Connie

  3. Project Timeline Go-live for SHARP II Go-live for SMART Testing Phase Cutover Phase March April May June July End Interface Testing Load Budgets Close STARS Data Conversion Operational Readiness Testing End User Training Load SMART and SHARP with Production Values Agency Report Development End User Testing

  4. Status of Defects and Fixes With over 98% of all testing complete, defect fixes are trending in the right direction… Approximately 75% of remaining defects are “medium” and “low”

  5. Status of Defects and Fixes Regression testing is well underway Approximately 75% of remaining defects are categorized as “medium” and “low”

  6. Project Status and Activities - Finance Team • Fixing defects • Regression testing • Cut-over activities • Supporting Dress Rehearsal and Operational Readiness Testing • Loading configuration values • Testing financial data in data warehouse • Supporting Help Desk and Training – as needed • Developing job aids and business process maps • Agency reports • Policies and procedures • CAN briefings • Working with agencies, e.g. cash management, allocations

  7. Project Status & Activities – Enterprise Readiness Team • Completing remaining three web-based training courses • Web-based training in progress (2,000+ students) • Instructor-lead training in full swing (2,348+ students) • Help desk training support staff trained and being tested in ORT • Monthly Change Agent Network meetings (CAN #12 held yesterday) • May monthly newsletter published • Meeting with agencies to discuss agency readiness; met with 23 agencies over past month • Deployed training sandbox

  8. Project Status & Activities – Tech Team • Fixing defects • Completing final mods; almost all mods now assigned to State • Completing performance testing and final tuning • Assisting agencies with data conversion cutover • Beginning work on agency reports • Supporting ORT using Production Support Model • Continuing to load approximately 5,000 end users for Go-Live security (core users and employee self-service for Time and Labor and Travel and Expense modules)

  9. Project Status & Activities – Central Systems • Adding an enhancement to an IBARS interface • Continue testing Regents payroll files as part of ORT

  10. Project Status & Activities – Miscellaneous • One more monthly data conversion workshop in June • Building out Shared Service Center • Completed developing production support processes (with DISC) including roles and responsibilities during transition and will use during ORT • Continue knowledge transfer with central agency personnel (DISC, A&R and DoP) • Size of project team continues to decrease as Accenture staff roles off and some State staff take jobs with agencies

  11. Setting Expectations

  12. Expectations Setting – Features and Functionality • So far this project has gone very well relative to other similarly large and complex projects • But, we have not been without bumps in road: • Several agencies would like different workflow configurations that more closely match what they are doing now The software can accommodate many workflow routings but for “go-live” we could only provide several standard routings; there will be opportunities in the future to evaluate adding additional workflows • Training requirements for some agencies’ supervisory roles may be excessive Supervisors who simply approve travel requests or vouchers (but cannot make changes) may not need to know GL; the curriculum will be reviewed and some of the requirements (for certain roles) scaled back

  13. Expectations Setting – Features and Functionality • Agencies would have liked to practice end-to-end transaction processing in a fully configured environment including agency values, workflow and security • Due to the complexity of configuring and maintaining multiple environments and the timeline we are all working towards, we are not able to provide • As delivered by Oracle, the data warehouse has data spread across multiple areas which are difficult to link in a single report • Project team enhancing several key subject areas in the data warehouse such as AP, AR and GL to make agency ad-hoc reporting easier; there will be incremental releases of these enhancements after Go-Live

  14. Expectations Setting – Support • Despite tens of thousands of hours of testing by our team and agencies there will be issues that will need to be fixed at Go-Live • There are many points of failure for a transaction from an agency interface or on-line entry, through multiple modules, through security, workflow budget checking, to the desired outcome, e.g. check/ACH or deposit • We will need to address issues as they arise collaboratively • The first step is attempting to resolve the issue is for end-users to use the tools provided (job aids, training materials, UPK) • Knowledgeable personnel at your agency are critical as a 1st line of support • For escalation to the Help Desk – provide good descriptions of the issue and the urgency • Be patient, but not too patient; if it is a critical transaction or reporting issue and it is not being attended to in a timely manner then use the reply feature within the Help Desk Software to communicate and convey the critical nature of your incident to the analyst assigned to your ticket

  15. Expectations Setting – Productivity Impact BEYOND OCTOBER: “I’m learning how to use more advanced features of SMART to meet agency business challenges; I’m excited!” MAY/JUNE “I can do this task in 10 minutes” AUGUST - OCTOBER: “I know SMART better and shortcuts; I’m back to where I was; I can do this task in 10 minutes” END of JULY/AUGUST: “I’m learning SMART and starting to get comfortable; this might just work” PRODUCTIVITY TIME JULY/AUGUST: “This takes me 2x -3x longer than the way we used to do it; I’m confused and frustrated”

  16. Change Control

  17. Change Control Change orders approved since last Steering Committee meeting

  18. SMART Cutover Strategy

  19. High-level Cutover Timeline May June July August 06/29 Last day for Agencies to send interface transactions in STARS; 07/06 last day for direct entry (2010 transactions) into STARS Load Purchase Orders/ Encumbrances into SMART Load Appropriation & Op Budgets into SMART STARS Shutdown SMART Go-live Agency Data Conversion & Validation SHARP Cutover Preparation & Administrative Activities SOKI Shutdown 07/01 Agencies enter 2011 Transactions in SMART 06/23 Go-live for Time and Labor and SHARP II open to all users 07/06 Last day for Agencies to Enter Deposits in SOKI

  20. Cutover Stages Performance Testing identifies batch and on-line process that do not complete within an acceptable time.  Performance issues are not uncommon in large implementations of PeopleSoft.  There are various remedies for addressing performance issues and there is an experienced team from Accenture working on performance tuning.  Performance testing has been on-going for two months and is expected to continue until the end of May. End User Testing Completed! 30 agencies executed 486 scripts in 12 days! (approximately 40 scripts per day) It took a great effort on the part of the agency users and the Project subject matter experts to get all this work completed in the short time allotted. In spite of network problems and power outages, they got it done. THANK YOU! Dress Rehearsal – a full sequence of cutover activities executed in the same time windows, i.e. 24x7 and weekends – is complete. Learnings from this activity have been built into the Cutover Checklist.

  21. Cutover Stages (continued) Operational Readiness Testing Began May 10th and simulates operations in the production environment and day-to-day processing, including: help desk, batch scheduling, and select interfaces. This is a three week exercise that ends May 28th. Deployment is the set up of the SMART system and will run from June 1st through July 30th

  22. Key Agency FinalConversion Dates Final Data Conversion Files Due Dates: Pre Go-Live • June 4– Customer File (Task ID 302) • June 4 – Projects File (Task ID 306) • June 11 – Purchasing Contracts File (Task ID 305) • June 16– Asset File (Task ID 303) • Capital assets received between 6/16/10 and 6/30/10 will need to be entered online in SMART after Go-Live. Agencies should retain a log of their assets from this time period and may use the Asset Data Entry Template to enter them into SMART. FINAL CONVERSION MEETING – June 14th 2:00-3:00 DSOB Auditorium Post Go-Live • July 16 – Pending Items File (Task ID 304) • July 16 – SMART closes at 2:00 PM for conversion of STARS balances and encumbrances

  23. Key Interface Dates Interface Dates for agency-facing interfaces: • June 7 – Begin daily execution of INF01 – Vendor Download (Task ID 307) • From June 5 to June 30, all new vendors will needed to be added by Accounts and Reports in STARS. Starting July 1, agencies can add vendors in SMART. • June 8 – Begin daily execution of INF15 – ChartField Extract (Task ID 308) • June 28 – Begin bi-weekly execution of INF42 – Time & Labor Interface • July 1 – All other agency interfaces begin (Task ID 292)

  24. Year End Processing • Informational Circular No. 10-A-014 is available on the A&R website • Provides dates for closing FY2010 and beginning FY2011 • http://www.da.ks.gov/ar/infocirc/fy2010/Ic10a014.htm • All FY2011 transactions must be processed in SMART • FY2010 transactions must be processed in STARS • STARS and SOKI will not accept FY2011 transactions • Closing Dates • STARS will close on July 6, 2010 • Payment vouchers must be entered by noon • DA118s and DA107s must be entered by 6PM • The cutoff for FY2010 dataset transactions into STARS is noon on June 29 • SOKI will close on July 6, 2010

  25. Year End Processing (continue) • Contact A&R with questions about: • Closing FY2010 • FY2010 transactions inSTARS and SOKI Contact Randy Kennedy at 785.296.2125, Randy.Kennedy@da.ks.gov • Contact the SMART HelpDesk with questions about: • Opening FY2011 • FY2011 transactionsin SMART

  26. Remaining Scope, Data Warehouse, Agency Reporting Needs, Executive Dashboards, End User Testing, Production Support Model and Agency Interactions

  27. Test Sequence & Schedule Functional Team Dev. Team Interface Team Conversion Team Technical Team All Teams * Extensions granted to specific agencies beyond 3/15

  28. Remaining Scope Elements in Design or Build • Three remaining Tech work units • Two functional mods in review cycle • One report • Several new (minor) CRs added to scope based on testing • Additional reports (for agencies) will continue to be designed, built and tested using State resources over next two months

  29. Vulnerability Assessment and Penetration Test • Ensure SMART and SHARP are secure from unauthorized access by State employees, the public and hackers • Project team and DISC participated in vendor selection and have been supporting exercise for past three weeks • Performed external and internal scans of network • Performed review of code modifications • Preliminary findings: • State has one of the “tightest” network security environment’s that the vendor has ever seen • No “show stoppers” have been identified

  30. End User Testing • End User testing conducted for four weeks in April for SMART and SHARP • Conducted in test lab • Twenty-nine agencies participated • 486 test scripts executed!

  31. End User Testing Big THANKS to agencies for participating! • Seventy-eight defects identified and logged by agency testers • All but six defects have been resolved • State team members supported agencies during testing

  32. Reporting - SMART • Reporting in SMART will be accomplished with several reporting tools and options • Each option has specific capabilities and can be correlated to specific report request types • Production • PS On-line Inquiries • Custom and Delivered SMART Reports • Custom and Delivered SMART Queries • Data Warehouse • Agency Access to SHARP Data HR and Payroll • Super Subject Areas for Fiscal Data (AP, AR, GL or PO) • Delivered Subject Areas • Delivered Set of Executive/Management Dashboards

  33. Reporting - Production • Production reporting options are run by agencies in SMART, data is same day and available for all modules. Queries and Reports are created centrally with dynamic prompts • On-line Inquiry, over 100 • Often used for quick ad hoc answers such as what is the check number of a particular payment • In some modules there are on-line inquiry tools that provide an opportunity to search for transaction level detail which can be exported to excel • Query, delivered and custom • Used for quick ad hoc answers • Used to retrieve a rows of transactional data that does not need to be pre-formatted • Can be exported to Excel, html, pdf and csv • Reports, delivered and custom, over 150 (includes queries) • Used for daily, weekly or monthly reports requiring a consistent format • Can be exported to Excel, html, pdf and csv

  34. Data Warehouse – State Expectations Provide agencies with ad-hoc assess to all of their transactional data Provide analytical capabilities to summarize and analyze aggregate transactional data, i.e. trends Provide executive and management dashboards that (with a minimal number of “clicks”) answer important management questions to support decision-making

  35. Data Warehouse Enhancements Production Source Systems Data Warehouse HCM Mart FIN Mart SHARP SA 2 SA 1 FIN Mart SA 3 SMART SA n SCM Mart Data from SHARP and SMART is Extracted, Transformed and Loaded into the data warehouse Each Mart in the Data Warehouse contains multiple subject areas As delivered, data cannot be consolidated to meet agencies’ ad-hoc needs Multiple reports are required to answer basic transactional questions

  36. Data Warehouse Enhancements FIN Mart FIN Mart SA 2 SA 1 Consolidated & Modified SA SA 3 SA n SA n • Project will create 3 - 5 enhanced subject areas (SA) • This will provide consolidated data which can be accessed by agencies using the DW reporting/query tools for agencies’ ad-hoc access to their data

  37. Data Warehouse Enhancements – Proposed Cost • Estimated cost to modify 3 Subject Areas • Approx 240 hrs ($47K) per custom subject area = $141K • Previously approved modifications: • CR163 approved at last SC meeting for up to $50K • Approved/unspent = $55K • Accenture contributes approx $50K State gets a custom data warehouse for no add’l $ • If State elects to modify a 4th Subject Area, Accenture will contribute $25K (50%) • If State elects to modify a 5th Subject Area, the State will be responsible for the total cost ($50K)

  38. Reporting – Data Warehouse • Data Warehouse reporting options using BI Answers, data is as of prior day. Report requests and dashboards can be created by agencies • Agency Access to SHARP Data HR and Payroll • Report on analytics • Headcount total by Department ID • Total Comp time paid by Department ID • OT hours and earnings by job code • Agency Access to SMART Fiscal Data • Report on analytics such as • Outstanding Accounts Payable • Expenditures for top 10 vendors • Deposit / receipts amounts • Delivered Set of Executive/Management Dashboards • Dashboards provide key analytics for agency leadership and fiscal officers by day, week or month

  39. Preliminary Design of Agency Executive Dashboards Workforce Compensation & Agency Payroll Financial Administration & Fiscal Management Workforce Profile • Fund balance as of <date> • Change in Fund balance <at beginning and ending of accounting period> • Budget vs. expenditures by Fund/BU • Expenditures by <fund, BU, Dept_ID, program, project/activity, account> • Top five expenditures against a <fund> in a given <accounting period> • Outstanding A/P and encumbrances • Expenditures for top 10 vendors over <month/year/etc> • Total pending amount per vendor • # of AP matching exceptions approved for payment • # of out-of-state travel events by employee and amount over <month/year/etc> • # of in-state travel events by employee and amount over <month/year/etc> • Outstanding travel authorizations • Outstanding cash advances <date, employee, Dept ID> • Expenses incurred by airfare, car rental, lodging, meals • Deposit/receipts amounts, payment ID, customer, Item ID, date • Receivables balance by customer and amt • Project/activity budget vs. actual • Revenue booked to a project by sponsor incl Fund/BU/Program • Employee hrs billed to a project/activity • Expenditures billed (in GL) but not collected • All leave hrs charged <pay period> vacation, sick, comp, shared leave, etc per employee • Leave balances for employees and how close to max • Employees w/ leave w/o pay in <pay period> • Total comp time by Dept ID • Vacation, sick, comp time payouts by Dept ID & employee • Total hrs worked <pay period> by Dept ID, employee compared w/ last <pay period> • Total payroll for <month> compared w/ last qtr, last year, by Dept ID, project/activity • Earnings, deductions, taxes by employee for <pay period>, or date range • Total earnings, Regular, OT, and all other earnings by Dept ID, job code, employee by <pay period> • Number of hours charged during <pay period> to a project/activity/source type and TRC by Dept ID and employee • Total Gross Pay by employee <pay period> by Dept ID • Number of hours charged by project/activity/source type and TRC by Dept ID and employee • OT hours and earnings by job code • OT hours & earnings by Dept ID , project/activity by <pay period> and by employee • OT or comp time in last <pay period> by employee • OT by Dept ID and employee for <pay period> compared with last year • Employees currently participating in health insurance coverage and @ what levels (for budgeting) • Total KPERS deductions (employee and employer contribution) by year by Dept ID • # of employees in union • Headcount total, by Dept ID (class & unclass) • Employees by location by Dept ID • Employees by age, ethnicity, gender, length of service • FTE over/under FTE Limitation • Filled & vacant position w/ incumbents • Personnel actions (hires, terms, rehires, retirements, transfers, promotions and demotions) within the agency (Dept ID) over past <month> • List of job openings opened and closed during the last quarter • Turnover by job class & by reason code • List of retirement eligible employees over next <year> • Employees by annual salary • Avg salary by class and unclass and by Dept ID Draft • Can be provided with currently planned subject areas • Will require modification/enhancement to subject area

  40. Reporting Strategy & Approach Steps – Task ID 265 Sunflower Project Team has met with all agencies to review critical reporting gaps For agencies with similar reporting gaps, reports are being designed and developed centrally to economize After attending training in mid-May agencies will be able to develop agency-specific reports in the data warehouse – report development environment will be available in late-May but will be lacking data Critical agency reports needed for Go-Live will (in most cases) be developed by the Sunflower Project; this will place additional and unplanned work on the reports development team

  41. Production Support Model

  42. Agency Interactions • KPERS • Successfully completed two weekly parallel tests • Successfully completed one monthly parallel test with 2nd in process during ORT • KDOT – resolving reporting gaps • Aging/KHPA/DOL – completing configurations for allocations

  43. SMART Shared Services Center

  44. SMART Service Center • Service Center: Filling the need for Small Agencies • Training • Professional Accounting Staff • The Success of the “It’s not an all or nothing” Approach • Safety net for small agencies • 32 Agencies Participating in Service Center • 20 agencies are fully participating • State Library • Board of Pharmacy • Board of Accountancy • Board of Cosmetology • Many other agencies…

  45. SMART Service Center • 11 agencies are participating in select modules • Office of the Securities Commission • Animal Health Department • Behavioral Sciences Regulatory Board • Governmental Ethics Board • INK participation • Staffing the Service Center • Service Center Kick-off for participating agencies held May 4, 2010 • Pre-Go Live Activities • Team meetings • Agency meetings • Transition for Agencies • Steady State

  46. Training Update

  47. End User Training Session Averages Week of May 3, 2010 through May 7, 2010 Average for: ResultsEvaluation of Course Content 3.97 out of 5 Evaluation against Course Objectives 3.97 out of 5 Evaluation of Instructor 4.27 out of 5 • Although scores were high there is opportunity for improvement, e.g. • Instructor paced the class well and offered her time after the session was over. Easy to follow guide and information. • Felt the instructor rushed thru the course - hard to follow along with instructions. Got lost more than once.

  48. Web-Based Training

  49. SMART Support & Agency Updates

  50. SMART Support The SMART Help Desk went live on Monday, May 10th! All questions or incidents related to SMART should now be routed to the SMART Help Desk. SMART Help Desk analysts will be available during the hours of 8:00 a.m. to 5:00 p.m. Monday through Friday. The Help Desk’s hours of operation will be expanded closer to go-live. Utilize the Sunflowerfms@da.ks.gov email only for Agency Go-live Readiness Checklists, role mapping updates, or if specifically directed to in Sunflower Project emails. All other communication should be directed to the SMART Help Desk.

More Related