The central theme of Mobile World Congress 2014 for me was clearly Connected Living. I’ve been attending Mobile World Congress for quite some time — 2006 was my first, the year that it moved to Barcelona from Cannes. And, this year felt different. No longer did the event feel dominated by handset manufacturers and equipment providers. Mobile World Congress is no longer a telecom event; it is clearly a mobile event. Mobility has penetrated every industry and every aspect of life, and that diversity is now clearly felt at the show. The large presence of car manufacturers and the buzz around Facebook indicate a definitive changing of the guard. That shift is ongoing. The proliferation of connected devices, the explosion of over-the-top services and the rise of the data economy will continue to shape the industry. But for me, this year I felt excitement around our new connected lives.
As we all learned as kids, it's nice to share. That holds true for public sector organizations as well, particularly in tough times. Public sector organizations don't have the privilege of dialing back on scope in challenging economic times. In fact, when the going gets tough, government organizations often have to kick into high gear. And that was the case with state unemployment insurance (UI) programs in the US, which saw spikes in applications when the economy slumped. But in most states the technology infrastructure wasn’t up to the task.
Legacy systems were on life-support... Colorado’s 25-year-old COBOL-based mainframe systems continued to process unemployment insurance claims, but it was increasingly difficult and costly to find the "doctors" to keep it alive. They had to bring developers out of retirement to maintain it. State officials knew it was only a matter of time before they had to pull the plug on their system.
…and just weren’t up to the task. Not only did the “look and feel” leave a lot to be desired, the legacy system failed to deliver. The system ran processes in batch mode, meaning that data was typically collected over a period of time (daily, weekly, or monthly) and processed into the system at the end of the period. Daily downtime for processing excluded the possibility of 24-hour availability or even extended hours. The delays and lack of availability frustrated end users who wanted or needed real-time or near-real-time information to make decisions.