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 »February 01, 2002 — CIO —
Construction technician Bill Young remembers when he had to load his truck each day with paper forms before he drove around central Michigan inspecting road construction sites for the Michigan Department of Transportation (MDOT). He had so many boxes "there was no room to even move," recalls Young, sporting a plaid flannel shirt and the deep tan he’s acquired working in the field for the past 12 years. Today, the only evidence of paperwork in his truck is a notebook computer mounted on the dash. "Now I’m like a one-man band," Young says. "It’s just my laptop and me."
Young is one of hundreds of technicians and inspectors from 37 MDOT offices, 120 local transportation agencies and 71 private companies in Michigan using FieldManager, a suite of road construction management software developed and co-owned by MDOT and Info Tech, a Gainesville, Fla.-based software company. It’s a groundbreaking system for a government agency and an industry that has changed little since 1909, when MDOT laid the first mile of concrete highway in the country.
Since the agency launched FieldManager in 1999, the system has enabled MDOT to eliminate a time-consuming, error-prone manual process for managing construction projects so that Michigan taxpayers get more, such as better roads and bridges, more quickly, for their money. FieldManager has also helped MDOT cope with an increase in its budget from $500 million to $1.5 billion a year since 1993, while cutting its staff from 5,000 to 3,000. An example of FieldManager’s impact: The M-6, a new 20-mile "beltline" being constructed south of Grand Rapids, in western Michigan, will be completed three years early, in 2005.
"FieldManager is consistent with my goal of putting more of our state’s transportation dollars into preserving our roads and less into administrative overhead," says MDOT Director Greg Rosine. Now others are following MDOT’s lead. FieldManager has been licensed by seven states, two Indian tribes and 223 private companies. "I see MDOT as a leader within its industry," says Doug Barker, CIO and vice president of The Nature Conservancy and one of four judges who honored MDOT with a 2002 Enterprise Value Award.
In the past, a field technician used to go to every work site with a printout of his required Inspector’s Daily Report. He would fill it out by hand, tracking thousands of work items and materials for each project -- everything from earth excavators to grout. At the end of the day he would hand the report in to the office. Assuming the handwriting was legible, the information on materials used, work completed and payments required would be copied and hand-tallied by as many as five people before the contractor got paid. MDOT needed an army of office workers to verify contractors’ work, and inspectors often could handle only one project per season. Larger projects required as many as 20 inspectors onsite each day. Today, MDOT rarely sends more than one field technician to a site. He enters data into a laptop and uploads it to FieldManager, either from the road or back at the office. Office technicians use the information to automatically generate payment estimates. Meanwhile, inspectors and office workers can get up-to-date reports on their projects to settle contractor disputes, amend contracts, check the status of budgets and make other routine administrative queries.