Offering regional and national programs, CIO (and CSO) events bring together some of the most respected names and thought leaders in information technology and security. Presented by CIOs and other senior level executives, these invitation-only programs offer timely topics and strong networking. Learn More »
Webcast: In the Google Apps Cloud: How to Achieve Your Business Objectives
Dec 3rd, '09, 1 - 2 pm US/Eastern (GMT-5)
Join Council member Brent Hoag, Director, Global IT, at JohnsonDiversey, as he discusses the adoption of Google Apps which has helped meet four corporate goals; sustainability, simplification, increased employee productivity and global collaboration.
Webcast: Collaboration Initiatives: Benchmarks & Best Practices
Dec 15th, '09, 4 - 5 pm US/Eastern (GMT-5)
Join Council members Ruth Thorpe, VP & CIO at the U.S. Pharmaceutical Operations of Sanofi-Aventis, and Gary Kuyper, CIO at Bethany Christian Services, as they speak about their collaboration initiatives and experiences in how and why they chose the social networking and collaboration tools they are using and their business goals for collaboration, and facing culture change challenges.
Data Overview: Collaboration Initiatives Field Guide: Benchmarks & Best Practices
This appendix to the Council Field Guide provides an analysis which discusses benchmarks for collaboration IT implementation costs, adoption rates and payoffs. The overview identifies top IT and business goals and satisfaction rates for collaboration initiatives as well as best practices and lessons learned for implementing collaboration IT.
Learn more about the CIO Executive Council »August 02, 2007 — CIO —
Sometimes, the only thing more damaging than a terrible car accident on a major expressway is the thousands of cars whose passengers slow down to take in the misfortunes of their fellow motorists. Rubbernecking is the term, of course, and a group of engineering students and their professor at the University of Maryland have decided to do something about it: They're enabling a number of Washington, D.C.-area traffic agencies (and their disparate systems) to communicate with one another quickly, by standardizing their information through an open-source, PostgreSQL database and mapping system.
The ultimate goal: By looking at each other's data in real-time, the agencies can make intelligent decisions about how to quickly clear away accidents and make sure drivers have nothing to look at but the open road. The project is tapping into $1.9 million in federal funds.
"Up until now, all the agencies have been doing their own thing," says Michael Pack, laboratory director of the Clark School's Center for Advanced Transportation Technology Laboratory at the University of Maryland, where he and 45 engineering students have been working on the project.
In the D.C. area, there are four major traffic centers: Virginia, Maryland, D.C., the Washington Metropolitan Area Transit Authority, as well as many local county centers. All the centers are equipped with their own computer systems and method of monitoring traffic and accidents, using CCTV and road sensors to measure speed and the volume of cars. "If they think the accident is big enough, they'd pick up the phone and call someone in a neighboring jurisdiction to let them know about it, but it was generally hit or miss," Pack says.
So Pack and his group of engineers used an open-source database and an open-source mapping service from the University of Minnesota to take all the information from each agency's database, translate it into one easy format, and push it back to each agency so they can see each other's traffic information in real-time. In doing so, if an accident occurred in Maryland near the Virginia boarder, Virginia would be immediately alerted to it because Maryland's data is fed straight into its system, and vice versa.
Though Pack's group has created a Web-based version of the system that agencies are free to use, they also have the option of integrating the data back into their homegrown systems, should they feel wedded to it (which may happen in governmental IT from time to time). "The idea is not to have a second system so each of them has 20 monitors at each location," says Pack. "Everything is going to be pushed back into all their native systems."