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 »December 01, 2006 — CIO —
Can this relationship be saved? That was one of the questions in the mind of Mike Hmel, FedEx Ground’s senior vice president of IT and CIO, as he prepared for a meeting with Sun Microsystems.
The IT department at FedEx Ground was struggling to develop a transportation management system (TMS) using what was a new technology in 1998—Sun Microsystems’ Java software. The TMS would help determine the most efficient and cost-effective way for the $5.3 billion company to move its tractors, trailers and dollies among its 29 hubs and more than 500 pickup/delivery terminals. As such, it would be the backbone of the Pittsburgh-based FedEx Corp. subsidiary.
But the multimillion-dollar development effort was "stuck in the mud," according to Hmel. Implementing the software was far more complicated than Hmel had expected. Java was more than a programming language: It was a technology that would have a profound impact on FedEx Ground’s IT infrastructure, requiring a shift from two-tiered client/server computing environments to multitiered Web-based computing environments. It also demanded a new approach to application development. What’s more, FedEx Ground’s IT department wound up having to buy more products to support the development of the TMS. Consequently, the relationship between Sun and FedEx Ground grew strained, which didn’t make resolving the problems any easier.
Tired of the impasse his company had reached in its development efforts, Hmel was meeting with Sun to address the issues and come up with a plan for completing the transportation management system. "Sun was a trusted business partner at the time. We had a lot of their equipment, people and services at FedEx Ground," says Hmel. "We had some problems with their hardware, and they had problems supporting us with the TMS. We made a real effort to work with Sun, but [the relationship] never got better."
Eventually, the TMS was completed, and it saved FedEx Ground $100,000 a day in staffing and administrative costs and helped shave a day off the time it takes the company to move shipments in many of its shipping lanes.
But the experience of struggling to deploy new, complicated technology made Hmel realize that he needed to maintain more constructive relationships—partnerships, really—with his most important technology providers if he was going to get the help he needed to deploy such expensive, mission-critical applications in this brave new world of open systems and Internet-based computing.
"We were getting into much bigger [IT] projects [at the time] with more impact on the company. We couldn’t afford failures," says Hmel.