Government Technology

Colorado’s Aging Financial Reporting System Could Fail, Audit Finds



July 11, 2011 By

Colorado’s accounting and financial management system is on its last legs and there isn’t enough money or technical expertise to support it, according to an evaluation conducted by the Colorado Office of the State Auditor.

The audit — released Monday, July 11, titled Evaluation of the Sustainability of the Colorado Financial Reporting System — uncovered that the more than 20-year-old system is at an increasing risk of a partial or complete failure, chiefly because it hasn’t had a maintenance contract for 12 years and is instead being serviced by employees set to retire soon, with no viable replacement personnel available to fill the void.

The information comes as no surprise to technology officials in Colorado. Dara Hessee, chief of staff for the Governor's Office of Information Technology (OIT) in Colorado, said the first study regarding the sustainability of the Colorado Financial Reporting System (COFRS) was done in 1999, and the issue has been bantered about since then without resolution.

“We have been having discussions for many, many years about the stability of our financial management system,” said Hessee. “Unfortunately in prior years, there have been huge competing funding priorities, along with horrible budgetary concerns with the state.”

In addition to the financial difficulties, COFRS — which processed approximately $36 billion in state expenditures in fiscal 2010 — runs on the obsolete COBOL programming language. So while new technology professionals are hired in the state, those employees are likely unfamiliar with COBOL and unable to step into the shoes of those retiring that currently service the system.

“The word the auditor used was this would be a ‘career killer’ for someone coming out of college and wanting to work in IT,” Hessee said, who added that if COFRS crashed, it could take more than a week to get the data up and running on a backup system.

The evaluation also spotlighted some additional areas of concern with the financial reporting system, including:

  • COFRS cannot gather and process sufficient data to provide citizens with complete and transparent information, such as providing detailed governmental expenditure data to fully comply with the requirements of the Colorado Taxpayer Transparency Act.

  • COFRS doesn’t have the capability to support multiple business functions — such as payroll, human resources, procurement and inventory management — or provide managers with access to real-time information.
  • Colorado is among the few states in the nation that have not upgraded their primary financial management system to a more modern, integrated system.

Next Steps

Despite the audit’s negative findings, Hessee believed the evaluation would help kick-start discussions to make the maintenance and eventual replacement of COFRS a higher priority within the Colorado Legislature. She revealed that while this year’s legislative session was finished, agencies are currently compiling their budget requests for the 2012-2013 fiscal year, so it’s the right time to put together the fiscal plan to address COFRS’ shortcomings.

Hessee said once the budget numbers are ready, they go over to Gov. John Hickenlooper’s office, where he and his staff prioritize the requests and submit a budget in the fall to the state’s Legislature. The Legislature will ultimately determine the funding levels for agencies in a finalized budget.

“Because OIT and DPA [Colorado’s Department of Personnel and Administration] have been talking internally for a few years now about the concerns we have, this review provides an objective view into the situation and gives us a vehicle to talk about the issue publically with legislators,” Hessee said. “Getting the support of the Legislature in replacing the system is huge and probably the biggest hurdle.”

When asked what type of system the OIT was eyeing to replace COFRS, Hessee said that a plan has yet to be fully developed. She did say, however, that Colorado CIO Kristin Russell planned to work with the National Association of State Chief Information Officers and other partners to find the “most reliable, low-cost solution.”

For now, the focus is firmly on acquiring the funding to tackle the issues at hand with COFRS, Hessee said. She added that the system is “core and foundation” to state government operations in Colorado and the state can’t afford to wait any longer to do something about it.

“The chair of the Legislative Audit Committee said, ‘Good luck with the Direct Budget Committee.’ So there are multiple steps involved here,” Hessee said, alluding to a potential legislative battle. “But we can always point back to this objective third-party review that shows we’re at a tipping point with this system.”


You may use or reference this story with attribution and a link to
http://www.govtech.com/policy-management/Colorados-Aging-Financial-Reporting-System-Audit.html


| More

Comments

KSC    |    Commented July 12, 2011

Don’t blame the language (COBOL)! Languages like COBOL and RPG have been called dead by “educators” (not real world) since the 1980’s. But, they are still very active, there are more lines of code in COBOL and RPG today in the world than any other language. For the auditor to say “career killer” is wrong, shows the auditor may not have done the home work. There is very strong and stable career programming in COBOL. It is just not the path kids these days want to take, not the ‘cool’ thing. You can do the cool things in COBOL that you can in other languages. So you ask why, is the system in the shape it is in? Not being in the Colorado Financial IT department I cannot say for sure but I can make some assumptions. Management did not allow the developers to keep the system current. Management did not give the developers the tools to keep the system current. Management/Users did not encourage and push the developers to step out of their box and try something new. Developers did not push management and users to allow them to step out of that box. In the first paragraph, “…chiefly because it hasn’t had a maintenance contract for 12 years and is instead being serviced by employees set to retire soon, with no viable replacement personnel available to fill the void”. I am sure this was done to save money. It wants to put blame on the employees. Many systems run just fine without a maintenance contract and serviced by employees. If they are not filling the void, whose fault is that?

dan boucher    |    Commented July 12, 2011

I have never heard of such bull..... COBOl is not obsolete. We have a tool that can document all aspects of legacy systems (RIPPLE-TRAc). It is my guess, that poor management is the culprit. If you don't know what you got then you cannot possibly move to a new model.....

Phil Weber    |    Commented July 13, 2011

OK, COBOL is old but it does the job and does it well. The problem is not the language, it is the lack of maintaining it and keeping up to date. Colo has proven that with IT systems, it has had no clue. At least with Ritter centralizing control, something may get fixed. Next big step is to quit outsourcing. What a way for companies like EDS, IBM, to charge a fortune and take no responsibility. And three, buy something that already is a package working in one of the 49 other states. Colo is NOT unique.

Tom    |    Commented July 14, 2011

Let's get real. While you can maintain a legacy system written in COBOL this is not the smart thing to do. There are many COTS solutions available today that provide a future path for both functionality and technology advancements. It makes no sense for any government agency to remain on a legacy system assuming all the associated costs with maintaining these systems. Colorado is a clear example of what happens when a single IT department has the responsibility for maintaining a legacy system. Budgets no longer allow for keeping the staff needed to maintain these systems. It doesn't matter if COBOL is considered dead or not, it matters if you need to keep specific personnel on staff to maintain a single system. This is old thinking and not the direction for efficient IT departments.


Add Your Comment

You are solely responsible for the content of your comments. We reserve the right to remove comments that are considered profane, vulgar, obscene, factually inaccurate, off-topic, or considered a personal attack.