Lesson

Plan for success of an ICM project by developing a knowledgeable and committed project team that can provide oversight, direction, and necessary reviews.

Lessons from the ICM Implementation Guide


February 2012
Nationwide; United States


Background (Show)

Lesson Learned

Developing and deploying an ICMS is not a trivial exercise. When establishing goals and objectives for developing a successful ICM project and planning for success, it is vital that the project team be knowledgeable and committed and that the managing agency be able to successfully assemble the team. Lessons to managing the team successfully include:
  • Confirm project responsibility, commitment and expertise. ICM project teams need to be committed to the process, provide the correct project expertise (e.g., systems engineering, software and hardware design and integration, communications, etc.), take ownership of the work products, and see the work products through to successful completion. It is imperative that all stakeholders take responsibility for their part in the project and play an active role in providing successful outcomes. Key activities that can seem time-consuming but provide significant benefit later in the project include: the definition of the current corridor and system assets (both physical and data), identification of corridor needs, and the development of a common vocabulary among partners to describe existing systems and proposed capabilities.
  • Obtain buy-in from all stakeholders. Before proceeding with the development of an ICMS, it is essential that the stakeholders be able to describe why the proposed system is needed and what the goals of the ICMS are.
  • Manage project procurements, costs, schedules, and risk to reduce the impact that multiple tasks have on a large project. Multiple procurements from multiple agencies are a challenging endeavor. If, as a part of the ICM project, one of the stakeholder agencies slips schedule or misses requirements in selection and procurement, this can affect the project as a whole. Procuring systems prematurely (prior to defining the requirements) could significantly impact the cost and schedule of the project.
  • Develop an acronym and terminology list that includes common definitions. When working with multiple agencies, it was found that terminology and acronyms can differ in definition. Developing an acronym and terminology list that includes common definitions improves coordination and communication.
  • Provide concrete project guidance. Make sure project guidance is concrete so the contractor is not confused or getting mixed messages. There should be a unified message when providing guidance. Developing a Project Management Plan and documenting all stakeholder roles and responsibilities is essential for project success.



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

Integrated Corridor Management: Implementation Guide and Lessons Learned

Author: Gonzalez, Paul: Dawn Hardesty; Greg Hatcher; Michael Mercer; Michael Waisley Noblis, Inc. 3150 Fairview Park Drive Falls Church, VA 22042 703-610-2000

Published By: U.S. DOT Federal Highway Administration

Source Date: February 2012

Other Reference Number: Report No. FHWA-JPO-12-075

URL: http://ntl.bts.gov/lib/47000/47600/47670/FHWA-JPO-12-075_FinalPKG_508.pdf

Other Lessons From this Source

Lesson Contacts

Lesson Analyst:

Cheryl Lowrance
Noblis
202-863-2986
cheryl.lowrance
@noblis.org


Rating

Average User Rating

0 ( ratings)

Rate this Lesson

(click stars to rate)


Lesson ID: 2014-00667