Lesson

Reach out to a broad range of stakeholders and deploy early the projects that demonstrate easy-to-see benefits to build momentum for agency’s ITS program.

Chattanooga Area Regional Transportation Authority's experience in deploying transit ITS


November 2009
Chattanooga,Tennessee,United States


Background (Show)

Lesson Learned

The Chattanooga Area Regional Transportation Authority's (CARTA) SmartBus ITS program offers valuable guidance on stakeholder outreach for implementing ITS at a mid-size transit agency. CARTA recognized the importance of stakeholder involvement early in its ITS program. Accordingly, a key element in its ITS deployment was the development of a project-specific deployment plan, with the last chapter of each being devoted to outreach. Lessons learned from CARTA’s stakeholder outreach are narrated below:
  • Identify key stakeholders and classify them in interest groups. CARTA’s outreach plan for each project involved consulting with three stakeholder groups and receiving input on their interest areas:
    • The Council of Managers. The Enterprise Center and its Council of Managers are responsible for the Chattanooga Regional ITS Architecture. CARTA regularly participated in meetings with the Enterprise Center to coordinate CARTA ITS plans with the regional plan.
    • CARTA Staff. For each ITS Deployment, CARTA formed a team with representation from all departments that was involved with operating and maintaining the system once deployed. This team helped provided information about current processes and procedures, defined requirements for the deployment, and helped identify how current processes and procedures would be modified after the deployment.
    • The General Public. While CARTA did not typically directly involve members of the general public in its development process, the agency did recognize the need in its deployment plans to publicize the changes to passengers and to educate passengers on how to use new services and features provided by the ITS technologies.
  • Reach out to a broad range of employees, including those skeptical of ITS. Reaching out to a broad range of employee-stakeholders, including those skeptical of ITS, can improve the final product and its level of acceptance. To receive feedback on plans for the deployment of onboard systems, CARTA formed ITS Oversight Committees, which included paid time for employees to participate in committee meetings. These committees included union representatives and many drivers, as well as several employees who had preconceived negative opinions regarding these particular technologies. These committees provided useful recommendations regarding the ITS rollout, and this approach also resulted in better buy-in for the ITS deployments among those employees.
  • Be sensitive to technology upgrade readiness of the agency’s various divisions of transit service operations. CARTA was sensitive to stakeholder needs when it changed the timing for introducing the flex-route operations management software. CARTA originally planned to begin using the software to support these services in 2006, in conjunction with the rollout of new operations management software for fixed-route and paratransit operations. However, feedback from flex-route dispatchers indicated that the planned system could not efficiently support dispatch services until an overall CAD/AVL (computer aided dispatch / automatic vehicle location) system was available to provide real-time bus location information. In response to these concerns, CARTA delayed this deployment and made plans to include acquisition of alternative flex-route operations management software incorporating additional software features to better satisfy user needs.
  • Search for easy-to-implement projects, which will produce easy-to-see benefits and create momentum for ITS deployment. An important facet of managing stakeholders’ expectation is the sequencing of projects so that successful demonstrations and observable benefits occur regularly. These demonstrations can help maintain program momentum in two ways. First, they build enthusiasm for ITS by regularly providing benefits to stakeholders - stakeholders that are benefiting from ITS are more likely to continue to support it. Second, they help build confidence that ITS will be deployed successfully and, once deployed, will generate benefits. With this in mind, CARTA chose to deploy first those ITS projects which could be completed in a relatively short time and would generate easy-to-see benefits:
    • The data warehouse project was completed in 2004 and immediately simplified a number of internal reporting functions. This was a particularly important step because the data warehouse benefited senior CARTA management by providing them with improved visibility into CARTA operations.
    • The "tricoder" system for recording vehicle fuel, oil, and other liquid usage, deployed in 2005, saved time by simplifying a manual process. This system was relatively easy to deploy because it required little integration with other systems and it saved CARTA staff the time each day that had been used to transcribe manual fuel usage data.
    • The CARTA EVDO (Evaluation-Data Optimized) network, deployed in 2007, was needed to support data communications between CARTA vehicles and CARTA Headquarters. While designing this network, CARTA noted that it could purchase EVDO modems for vehicles with a built-in router and Wi-Fi. This allowed the agency to provide wireless Internet service to passengers at essentially no cost over the cost of the required data communications network. And, the benefit to passengers – free Internet service – was easily observable.
  • Monitor the projects proactively to identify benefits. CARTA's ITS staff were aware of the need to demonstrate the benefits being achieved through the ITS technologies being deployed. The project-specific deployment plans included a section on monitoring and evaluation that described the types of benefits anticipated and how those benefits might be identified. And, CARTA ITS staff monitored the systems to identify benefits. For example, when the ITS program’s evaluation team discussed free Wi-Fi usage with CARTA, CARTA staff accessed monitoring screens that allowed them to identify the number of users presently accessing the Wi-Fi system.
CARTA gave high importance to stakeholder outreach and developed an outreach plan for each ITS project – a practice that allowed CARTA to receive feedback from customers and employees and facilitated their buy-in. CARTA had sequenced the deployment such that the ITS projects that were anticipated to offer early and visible benefits were implemented first, thus, generating stakeholders’ confidence in ITS. Overall, CARTA’s proactive pursuit of reaching out to stakeholders and demonstrating to them the ITS’s benefits served the agency well in its planning and deployment of ITS.


Lesson Comments

No comments posted to date

Comment on this Lesson

To comment on this lesson, fill in the information below and click on submit. An asterisk (*) indicates a required field. Your name and email address, if provided, will not be posted, but are to contact you, if needed to clarify your comments.



Source

A Case Study on Applying the Systems Engineering Approach: Best Practices and Lessons Learned from the Chattanooga SmartBus Project

Author: Haas, R.; E. Perry; J. Rephlo

Published By: U.S. DOT Federal Highway Administration

Source Date: November 2009

URL: http://ntl.bts.gov/lib/32000/32600/32672/index.htm

Other Lessons From this Source

Lesson Contacts

Lesson Analyst:

Firoz Kabir
Noblis
202-863-2987
firoz.kabir@noblis.org


Rating

Average User Rating

0 ( ratings)

Rate this Lesson

(click stars to rate)



Notes

Lesson of the Month for January, 2011 !


Lesson ID: 2010-00551