CBMS - Part 2
Thursday, April 10th, 2008[Continuing from Colorado Benefits Management System - Part 1]
OK, so who wins this chess game now that Bobby Fisher is dead? Well, it is complicated and very political. Depending on whom the Kings and Queens (state officials and foundations) listen to will dramatically affect the ultimate outcome.
If they choose wisely, I believe that everyone actually can win.
If they choose to continue to do business in the same manner as in the recent past …choosing EDS to do CBMS and other large high-cost professional services vendors to do CSTARS (motor vehicle registration), Genesis (unemployment insurance), and SCORE (voter registration and election system) … the outcome will most certainly be another train wreck. (see references and links below).
No use crying over spilled milk (or spent taxpayers money), and since I can’t do anything about the past, my optimistic side is focused on devising a win-win solution for the known problems relating to the CBMS front end (these problems revolve around the CBMS application completion process). My vision will dramatically simplify and improve the application process for virtually all the various benefits programs, including those of CBMS.
The solutions we are able to quickly deploy will allow for state officials to save face (by keeping the back end of CBMS intact) and will drastically reduce costs for the counties while allowing them to better serve their clients and manage their caseloads. The non-profits will be happy and continue to help the needy and counties with collaborative outreach and applications completion assistance.
But best of all, the solutions allow the needy to receive the benefits they qualify for more timely, and children will get fed! (I am assuming of course that the back end of CBMS isn’t flawed as well. If it is also flawed, well then, at least the State won’t have the front-end users and counties to blame anymore.)
I had the opportunity to get a tour of the Jefferson County (Colorado) Division of Human Services facility yesterday, and it was certainly eye opening and alarming. I believe more strongly now than ever that the people tasked with delivering the benefit services are incredibly hardworking and passionate people. Their goal is to do the best they can with the tools they have. It is one thing to talk about how bad CBMS is. It is another thing to actually see the wasted hours and expense each county is strapped with because the CBMS front end is so inefficient. CBMS is clearly not working, and if I hear a state official say “CBMS is completely fine. It’s the users that are messing up the applications,” I may have to scream!
The Better Way
So, as I mentioned, there is a better way. The Efficient Benefits Application Solution Service, or eBASS, uses the Efficient Forms Transaction Origination Platform and allows caseworkers and clients to quickly complete the applications for all the benefits a client qualifies for. In fact, the solution also quickly determines what programs a client qualifies for and then asks a series of logic-driven questions to gather the data required for all the various benefit programs. The solution forces required questions to be answered so applications are in good order.
One of the most important benefits of eBASS is the way that all benefit program applications can be completed in one sitting from any authorized caseworker, or authorized non-profit caseworker. While CBMS may handle food stamps, TANF, Medicaid and several other programs, it does not handle all the programs. Clients are forced to complete additional paperwork for various other programs like CCAP, LEAP, pre-school assistance, or other county-specific assistance programs, costing them time and costing taxpayers money. The eBASS interview streamlines this application process and completes all the appropriate applications. This benefit is simply not offered by any other provider, and I do not believe any other provider is even contemplating this feature, even though so much of the data gathered on one app is need for every other app.
While there are many key features of the eBASS solution, that isn’t really the point. I will continue to post on this subject from time-to-time and will keep you informed at how we are making out in our quest to help solve the front-end problems in CBMS.
More Reading
If you are interested, check out one of the many articles on the State of Colorado’s troubles with large scale software projects:
Fix it or Ditch it?
By Andra Coberly, Fort Collins Now
January 30, 2008
Steven R. Nickerson © The Rocky
New system to register motor vehicles just the latest to misfire for state (note: link may be down. Here’s a copy of the original)
By Ann Imse, Rocky Mountain News
May 16, 2007
• CBMS: Colorado Benefits Management System, developed by EDS at a cost of $223 million. It fouled up welfare benefits and left poor people without critical cash.The federal government has demanded an $11 million sanction for money that CBMS incorrectly paid out in food stamps.
• Genesis: Developed by Accenture under a $40.8 million contract with the state Department of Labor to track unemployment insurance. The state said the system had a 20 percent error rate. The two sides agreed to cancel the contract. Colorado paid Accenture $27 million.
• SCORE: Statewide Colorado Registration and Election system, developed by Accenture under a $10.5 million contract. When Accenture missed a federal deadline for completion of the new statewide voter registration database, the secretary of state canceled the contract and hired a different company to do the job.
• ERP: Enterprise Resource Planning system was developed by SAP at a cost of $38 million to track Colorado Department of Transportation finances, personnel and project management. About 3,300 employees had their payroll checks messed up up last winter. The system continues to be altered and staff are getting extra training.

