IE 11 Not Supported

For optimal browsing, we recommend Chrome, Firefox or Safari browsers.

Card-Catalog-Level Data Work Underway in Kentucky

Hiring a chief data officer last year helped kick off some transformational data work in the commonwealth of Kentucky, according to Chief Information Officer Chuck Grindle. Here, he outlines their progress so far.

Kentucky CIO Chuck Grindle
Government Technology
Last year, Kentucky joined the growing ranks of states that have a chief data officer. And as Chief Information Officer Chuck Grindle explained at the annual NASCIO conference in October, bringing Krishna Mohan Mupparaju on board has set the state on a path toward understanding each of the state's 2,400 databases at a granular level.

Early work included the development of an agreement that defines how agencies can share their data. But Grindle is quick to point out that it's more about governing how that data is shared. "That's not a carte blanche," he said. "It gives you the parameters of how you share data amongst agencies."

On the legislative side, lawmakers are also working on advancing open data sharing policies, as well as making cabinet-level agencies stewards of their public-facing data using a common platform, Grindle said. As of October, he reported that about half of the state's 11 cabinet secretaries had signed off on the approach.

A nearly 30-year veteran of the U.S. Army, Grindle, appointed by Gov. Matt Bevin, is still in place as CIO as of press time. But the recent election of Andy Beshear as governor could mean a new IT leader for the state. Beshear, son of former Kentucky Gov. Steve Beshear, will take office next month.
 

Government Technology editor Noelle Knell has more than 15 years of writing and editing experience, covering public projects, transportation, business and technology. A California native, she has worked in both state and local government, and is a graduate of the University of California, Davis, with majors in political science and American history. She can be reached via email and on Twitter. Follow @GovTechNoelle
Special Projects
Sponsored Articles
  • How the State of Washington teamed with Deloitte to move to a Red Hat footprint within 100 days.
  • The State of Michigan’s Department of Technology, Management, and Budget (DTMB) reduced its application delivery times to get digital services to citizens faster.

  • Sponsored
    Like many governments worldwide, the City and County of Denver, Colorado, had to act quickly to respond to the COVID-19 pandemic. To support more than 15,000 employees working from home, the government sought to adapt its new collaboration tool, Microsoft Teams. By automating provisioning and scaling tasks with Red Hat Ansible Automation Platform, an agentless, human-readable automation tool, Denver supported 514% growth in Teams use and quickly launched a virtual emergency operations center (EOC) for government leaders to respond to the pandemic.
  • Sponsored
    Microsoft Teams quickly became the business application of choice as state and local governments raced to equip remote teams and maintain business continuity during the COVID-19 lockdown. But in the rush to deploy Teams, many organizations overlook, ignore or fail to anticipate some of the administrative hurdles to successful adoption. As more organizations have matured their use of Teams, a set of lessons learned has emerged to help agencies ensure a successful Teams rollout – or correct course on existing implementations.