Phase 1: Budget, Finance, and Procurement Module Implementation
The Luma project team held Business Process Redesign sessions from November 2019 to January 2020. These sessions brought together 280 state experts representing 48 agencies to discuss
what the current state processes are and
why. That information was compared with industry best practices to create a map of the processes that will be used during system configuration for Luma. The Luma project team has released these process maps for a statewide review!
Download the file and navigate to specific process maps through the Table of Contents or bookmarks.
PLEASE KEEP IN MIND: Business processes are similar to a roadmap, telling the Luma system the successful path to get from a process starting point to the destination. The roadmap shows all of the tasks necessary to get from point A to point B but does not dictate HOW those tasks can be accomplished. We are all eager to see how the Luma system will support the State's business activities. The software system has robust configuration capabilities that provide options to select the best fit for statewide needs. Communications around how the system operates will be developed and delivered in conjunction with the configuration of the Luma system.
Due to the complexities of government budgeting, our software provider Infor CloudSuite offered a partnership with Sherpa Government Solutions. Sherpa is a boutique public sector budgeting software and consulting firm founded in 2004.
The budgeting solution moves the State’s budget development processes into a single system, including revenue and expenditure planning, cost allocation, base budget development (technical adjustments), agency decision packages, budget office review, reporting, analysis, scenario building, performance monitoring, and budget monitoring. In doing so, the budget module provides:
Infor Financials will help improve business transparency and strengthen financial discipline with proven functionality covering core financial management, budgetary control, project and grant accounting, and cash management. As part of the Infor Financials foundation, we deliver a flexible, configurable chart of account structure to accommodate our customers’ needs. Infor provides the ability to define multiple hierarchical rollups for each COA element. We define which hierarchy is used for processing (i.e. budgetary control) and can define as many others as needed for internal, external and regulatory needs.
System Integration Testing is a cycle testing cycle that the Luma project team will utilize to test business processes work as designed across integrated forms, reports, interfaces, and data conversions within Luma. The intention of different testing cycles allows the team to test discrete functionality first, then progress through to end-to-end business scenario testing.
System Integration Testing (SIT) 1 & 2 will begin fall 2020. SIT will involve agency personnel and seeks to test the end to end functionality of the Luma system including all Forms, Reports, Integrations, Conversions, Enhancements, Workflows, COA build-outs, and configurations. It attempts to confirm that the system performs as designed.
Agencies were selected to participate in System Integration Testing Cycle 1 based on the following set of criteria:
As the Luma project team continues into the System Integration Testing Cycle 2 more agencies will be included in testing. This ramp-up of participation will continue into User Acceptance Testing.
User Acceptance Testing (UAT) is an end-to-end test of all business processes ensuring day-to-day business operations can be completed within the Luma system. UAT will begin in Spring 2021. In UAT, a broader group of state agency users will follow scenarios to test the functionality of the Luma system.
User Acceptance Testing (UAT) will begin in spring 2021. In UAT, a broader group of state agency users will follow scenarios to test the functionality of the Luma system. UAT is the system "dress rehearsal" and will confirm if the State is ready to move the ERP into the production environment and go-live.
Confirm that the application and business processes are able to support ‘Day-in-the-Life’ business functions.
Confirm data migration from legacy systems to Luma is accurate and meets the business needs.
Use a subset of the integration tests to confirm that the configuration supports end-to-end processing.
Validate security configurations and integrations are production-ready.
Validate that Interfaces and the Reports are providing the expected user experience.
Confirm compliance with policies and procedures.