State Software Discussion
June 17th, 45+ people attended the Munis Accounting Software demonstration by Tyler Technologies here at NEOnet and we learned a great deal more about this evolving situation.   The following are some items that caught my attention throughout the day. 

Tyler has 2,400 employees and serves 11,000 local government entities across the country.  They have approximately 700 employees dedicated to Munis support.  18 years ago they implemented Munis on a state wide basis in Kentucky’s 176 school districts taking 3 years to do so.  Akron and Columbus city schools have been using Munis for 5 years now and Berea is currently implementing it.  This experience would aid greatly in rolling Munis out to a group across Ohio in the future as Tyler has already hashed through ODE, ORC, SERS and STRS requirements. 

The plan that is evolving would most likely leverage ITC’s to aid in deployment.  Tyler Technologies would train and certify their own project teams.  ITC staff would function in primarily the same way that they do now for State Software.  The software itself could be centrally housed at the state or Tyler, housed at ITC’s or housed at individual districts.  Cost would be driven by ADM so smaller districts would pay less than larger districts.  As participation increases, costs would also decrease for the group as a whole.  None of the details have been completely worked out yet. 

The proposed suite of Munis modules would include the following: Accounting/GL, Accounts Payable, Budgeting, Project & Grant Accounting, Cash Management, Purchasing (Requisitions/Purchase Orders), eProcurement, Fixed Assets, Human Resource Management, Applicant Tracking, Payroll, Employee Self-Service, General Billing, Accounts Receivable, Munis Analytics, & Reporting, Tyler Content Manager, Tyler Forms Solution. 

A theoretical plan of attack for the state of Ohio is to be discussed in the next couple of weeks at a meeting between OASBO, MCOECN and Tyler. 

Expenditure Coding
Last week SSDT installed a patch that removes the validation requiring a building level OPU for certain functions from USAS until they can determine if/how this validation check will be applied in EMIS-R.  Specifically, the validation removed is the VALACT error “Building OPU required for this function.” which applies to the function codes 2110, 2121, 2131, 2141, 2151, 2171, 2211, 2221, 2231, and 2490.  This is not meant to imply that ODE will not validate these codes, however USAS will be deferring to ODE’s EMIS-R validations for this particular case.  Districts using these function codes should  review the function descriptions from the AOS manual and the “Expenditure Reporting Classification Chart” on ODE’s website (link below) to ensure they are using the best coding for their situation.

Meeting Reminders
The next NEOnet Board of Directors meeting is Tuesday July 8th at 9:00. 
The next Insurance Committee Meeting is Thursday, July 31st at 1:30.
The next Treasurers Operating Committee meeting is Thursday, August 21st from 12:00 to 2:00.


Fiscal Update