Context Sensitive Solutions Technical Assistance: Idaho Transportation Department
Outcomes and Recommendations
After the conclusion of the workshop, the questions developed by the workshop participants were reviewed and analyzed in context with the original purpose of the workshop. Questions were reworded, combined, or eliminated and a new set of questions were developed. As part of this analysis, the following documents were reviewed to ensure the questions were aligned with ITD guides and manuals:
Context Sensitive Solutions Guide;
Practical Solutions for Highway Design;
Guide to Public Involvement for Programs, Planning & Projects;
Project Outreach Planner;
Roadway Design Manual; and
Corridor Planning Guidebook.
The review and analysis resulted in post-workshop recommendations that integrated a series of guiding questions throughout each project delivery stage, and modifying the project charter to require revisiting the questions, would be a streamlined way to enhance ITD decision making processes. The charter must be completed by every project manager to advance a project, and it provides a perfect mechanism to tie in ITD’s existing guidance. To understand how the charter should be altered, it is important to first understand ITD’s project delivery pipeline.
ITD’s project delivery pipeline is described differently among the various guides and manuals mentioned above. ITD’s Project Charter Instructional Manual describes the project life cycle in five phases: planning, evaluation, development, implementation, and operations. These phases are illustrated below.
Figure 1: ITD project life cycle. Source: ITD Project Charter Instructional Manual
The Project Charter Instructional Manual further subdivides each of the last four phases into four stages: initiation; planning; execution, monitor, and control; and closure. Incorporating these phases and stages in the ITD project life cycle can be outlined in the following way:
Planning
Evaluation
Initiation
Planning
Execution
Closure
Development
Initiation
Planning
Execution
Closure
Implementation
Initiation
Planning
Execution
Closure
Operations
Initiation
Planning
Execution
Closure
The project charter is first mandated in the evaluation phase, specifically during the execution stage, and while not stated, the charter presumably will not be written until a specific planning concept is destined for the Idaho Transportation Investment Program (ITIP). ITD may wish to consider developing a CSS public involvement plan that is coordinated with the public, and finalized before the project charter is finalized. In this way, commitments and ideas that can affect the project scope can be addressed before substantial ITD funds are invested and potentially affected by a project having to be revised and redone.
To ensure that ITD project managers understand when in their delivery process to ask the questions developed during the workshop, processes from other ITD manuals, as shown below, were incorporated with new steps indicated in bold text.
Planning
Long range planning
Corridor planning (undertaken when there are complex issues and need for a bundle of solutions in a particular corridor)
Develop initial public involvement plan
Evaluation
Initiation
Planning
Develop initial scope, schedule and budget
Execution
Develop project charter
ITIP documentation
Incorporate results of early steps public involvement plan
Closure
Development(design, right-of-way (ROW), utilities, environmental analysis and documentation)
Initiation
Update public involvement plan
Update project charter
Planning
Review Practical Solutions for Highway Design guide as part of identifying opportunities for flexibility
Execution
Preliminary design
Final design
Closure
Lessons learned
Implementation (Construction)
Initiation
Planning
Execution
Closure
Operations
Initiation
Planning
Execution
Closure
Lessons learned
The questions originally drafted during the workshop were refined and incorporated into an expanded project life cycle, as shown below. Any life cycle phase or stage without a question beside it was determined not to require any associated questions.
Planning
Long range planning (Recommendation: If the answer is yes to any of the first two questions, ITD planning staff should consult with the District Engineer and evaluate the value of starting a Corridor Planning Study, as prescribed in the Corridor Planning Guidebook)
Have we identified the specific elements of the proposed solution that have independent utility, and have we determined which ones can be implemented in phases to spread out the project costs over time and to implement simpler improvements sooner?
In the planning process, did ITD and its partners evaluate whether the local network serves some of the identified user needs better than the proposed project?
What is this corridor’s role in the network?
How can the local street network be better utilized to accomplish some of the project’s needs?
Would an investment of state or federal funds into the local system accomplish some of the project needs at a lower cost or lesser impact?
Has the regional transportation plan (if any) been analyzed to determine whether there are non-ITD options that could better accomplish project needs?
If any of the above is possible, does the public involvement plan describe how ITD could educate the community members on options within their jurisdiction that they could implement? Does it help them identify funding?
Have we looked at and analyzed all long-term plans and how they affect the local community as well as the emerging ITD project?
What are the travel modes that will be impacted? Who are the other users (e.g., shoppers on a main street)? What are their specific needs?
Have we identified who the current and future users are, based on land use and development changes? (Note: future users will generally relate to changes in the community identified in review of their long-term plans, or by considering potential growth patterns identified by the community, rural planning organization (RPO) or a metropolitan planning organization (MPO)).
What are the users’ current and future needs?
What are safety concerns for each user?
If competing user needs emerge, has a process been created for facilitating dialogue between those users?
Corridor planning
Have we looked at and analyzed all long-term plans and how they affect the local community, as well as the emerging ITD project?
Have we set the parameters for how we will evaluate the specific elements of the proposed solution that have independent utility?
Have we consulted the ITD Context Sensitive Solutions Guide in the process of defining the various contexts?
Have we asked the ITD public involvement coordinator to use the POP to help us define the public involvement plan for defining and developing solutions for the community contexts?
Have we established a template for identifying and rolling out simpler project improvements that will not cost a lot of money and could begin to address issues in the corridor?
In the planning process, did ITD and its partners evaluate whether the local network serves some of the identified user needs better than the proposed project?
What is this corridor’s role in the network?
How can the local street network be better utilized to accomplish some of the project’s needs?
Would an investment of state or federal funds on the local system accomplish some of the project needs at a lower cost or lesser impact?
Has the regional transportation plan (if any) been analyzed to determine whether there are non-ITD options that could better accomplish project needs?
If any of the above is possible, does the public involvement plan describe how ITD could educate the community on options within their jurisdiction that they could implement? Does it help them identify funding?
Have we identified the mechanism/process for predicting and evaluating future land use and development changes?
If the proposed project is in an MPO coverage area, have we asked the MPO to take the lead on land use projections?
If the proposed project is in an MPO coverage area, have we consulted with the MPO about whether there is value in providing land use planning support for the communities?
If the project is not in an MPO, or if the MPO is not included to conduct land use planning, has the district engineer consulted with ITD planning personnel about providing land use planning support?
Develop initial public involvement plan.
Evaluation
Initiation
Planning
Does the public involvement plan prescribe a dialogue with members of the community to:
Identify community-specific communication needs? In other words, have we asked them how they want to be communicated with?
Identify their perspective on project constraints?
Identify their goals that could be taken into consideration for the ITD project?
Effectively communicate ITD’s vision for purpose and need?
Did the public involvement plan identify the full realm of stakeholders?
Was the Project Web App, as specified on page 35 of the Project Charter Instructional Manual, used to create this list?
Did the public relations person update the district stakeholder list?
Did we identify which tools/processes we should use to communicate with our stakeholders?
For large-scale projects, does the public involvement plan analyze whether ITD should establish a community advisory committee to discuss the details of the project (e.g., needs, expectations, timeliness, impacts, risks, etc.)?
Execution
If it was determined during the planning phase that there are sub-elements of the project that have independent utility and that should progress on different schedules, have they been entered the ITIP separately?
Were the constraints identified by the community included in the initial charter?
Does the charter describe:
The community goals (if any) that have been decided to be incorporated into the ITD project?
Feasible project changes that could support the long-term goals of the community, and have they been reflected in the scope of the project?
Have we gathered all information needed to set a preliminary scope and budget (see page 20 of the Project Charter Instructional Manual)?
Have we worked with the public involvement coordinator to revise the public involvement plan to:
Document any community goals, constraints or other elements that will not be addressed by the project?
Document the community’s acceptance (or not) of ITD project goals?
Document potential project changes and how they were shared with the community?
Determine whether a strategy has been developed for effectively using existing area transportation committees?
Closure
Lessons learned
What did we do well? Sample topics:
Communication
Flexibility
Schedule
Multi-jurisdiction/disciplinary
Economic impacts
Others
What could we have done differently? Sample topics:
Communication
Flexibility
Schedule
Multi-jurisdiction/disciplinary
Economic impacts
Others
Have we shared lessons learned in the lessons learned library?
Development
Initiation
Have we consulted the public involvement coordinator to review/update the public involvement plan?
Have we updated the project charter?
Planning
Have we reviewed the Practical Solutions for Highway Design guide in preparation for applying flexibility in design?
Execution
Before start of preliminary design
Have opportunities for flexibility in design been identified in the establishment of design standards in the project charter, to dovetail ITD’s identified purpose and need with those of the community? Has the Practical Solutions for Highway Design guide been applied?
Via the public involvement plan, has the community been advised of those things they may have to do to support flexibility on the part of ITD?
At the end of preliminary design, have we updated the scope and budget as the project progresses through scoping and design, and community engagement?
After preliminary design
Have we undertaken a constructability analysis – as specified in the ITD Roadway Design Manual section 310.01 – in coordination with the district’s construction staff?
Have we analyzed the nuances of construction access, circulation, and whether we have left the property owner with an uneconomic remainder?
Have we analyzed issues such as wetland protection and other environmental or historical issues?
Have we analyzed and coordinated any maintenance and operations issues?
Have we considered the potential cumulative and indirect impacts on the stakeholders?
All of the above questions should be revisited to determine whether the preliminary design that will provide the basis for final design and ROW acquisition addresses all previously noted commitments and questions. For federally funded projects, these questions can be addressed in the environmental documents and/or environmental re-evaluation.
Closure
Lessons Learned
What did we do well? Sample topics:
Communication
Flexibility
Schedule
Multi-jurisdiction/disciplinary
Economic impacts
Others
What could we have done differently? Sample topics:
Communication
Flexibility
Schedule
Multi-jurisdiction/disciplinary
Economic impacts
Others
Have we shared lessons learned in the lessons learned library?
Implementation (Construction)
Initiation
Have we reviewed the project charter, in consultation with the district engineer and the public involvement coordinator, to determine the ramifications for construction?
Planning
Execution
Closure
Lessons Learned
What did we do well? Sample topics:
Communication
Flexibility
Schedule
Multi-jurisdiction/disciplinary
Economic impacts
Others
What could we have done differently? Sample topics:
Communication
Flexibility
Schedule
Multi-jurisdiction/disciplinary
Economic impacts
Others
Have we shared lessons learned in the lessons learned library?
Operations
Initiation
Planning
Execution
Closure
Lessons Learned
What did we do well? Sample topics:
Communication
Flexibility
Schedule
Multi-jurisdiction/disciplinary
Economic impacts
Others
What could we have done differently? Sample topics:
Communication
Flexibility
Schedule
Multi-jurisdiction/disciplinary
Economic impacts
Others
Have we shared lessons learned in the lessons learned library?
ITD Planning Services Action Items
A conference call was held with Ted Mason, Sonna Lynn Fernandez, and Lori Porreca on January 4, 2017 to review a preliminary draft of this report and ensure that the recommendations provided above are aligned with ITD’s needs. The ITD staff members on the call assured that they were, and indicated that progress has already been made since the workshop in terms of establishing how existing guides, manuals, and processes will be altered to enhance CSS and public involvement outreach efforts. The table below summarizes the action items identified by ITD’s Planning Services Section and outlines accomplishments and/or the potential timeframe for incorporation as of January 2017.
CSS ACTION ITEMS
Action
Progress
Include or modify ITD’s project charter with CSS/public involvement references
Include a link to the POP within the project charter and add a box for staff to include the POP score.
Planning Services will include this request in the 2017 project charter release.
Make the stakeholder schedule inclusive through development and make sure it is included in the charter as considerations as we flow through the project development process – not just in the planning phase.
Planning Services will include this request in the 2017 project charter release and reference CSS/public involvement considerations throughout the Project Charter Guidebook.
The Guidebook will also reference the POP and encourage staff to use the program for stakeholder identification, CSS/public involvement strategies and preliminary budget estimates.
Create a section within the project charter that allows staff to list potential stakeholders.
A “Stakeholder Identification” box was already available in older versions of the project charter but was very confusing because it referenced ITD staff as stakeholders, not specifically the general public.
Planning Services will add a section within the 2017 project charter release that specifically asks for staff to identify general public and other stakeholders that may have an impact on the project.
Planning Services will continue to encourage staff to use the POP for stakeholder identification and consideration.
Planning Services will include additional reference to the POP within the Project Charter Guidebook.
Create a section that asks for the potential process to engage stakeholders.
Planning Services will not include this in the project charter. However, the POP does include a section that allows staff to identify and select (via a checklist) ways that the department will engage stakeholders.
Planning Services will include additional reference to the POP within the Project Charter Guidebook.
Add a section that the project manager can capture “lessons learned” in the charter.
A “lessons learned” library is already available. Planning Services will ensure that staff knows where this library is located as well as how to add and retrieve “lessons learned” information.
Planning Services will include additional “lessons learned” references within the Project Charter Guidebook.
Update the Project Charter Guidebook with CSS/public involvement component
Early 2017, Planning Services will deploy Microsoft Project 2016. At the same time, a restructured project charter will also be released that reflects ITD’s organizational and project delivery process changes.
The 2017 Project Charter Guidebook will be available to District staff at the time of the ITIP Roadshow in mid-January.
Planning Services will ensure that the Guidebook is easy for staff to find and access.
As requested, Planning Services will work with other areas of the department to create a section in the Charter Guidebook that identifies the types of agreements that are available, what they are used for, the process to have one completed and the SME to talk with.
Planning Services is in the process of creating a public involvement website which should be deployed in April 2017.
This website will include information on CSS activities and how staff can incorporate stakeholder involvement into the planning, project development, and construction processes.
This website will also be referenced in the updated Project Charter Guidebook.
The POP, the Guide to Public Involvement, the Communications Portal, lessons learned library, stakeholder identification processes, and other public involvement tools will be available at this website.
Make the Project Management Academy accessible and more user friendly
During 2016 and throughout 2017, Planning Services will be developing an interactive Project Management Academy.
Planning Services is actively working to provide a variety of project management on-demand/web-training modules that will allow ITD staff to take training at their own pace.
Planning Serves will work closely with ITD’s Training Section in 2017 to put these modules on the ITD Learning Hub as soon as they become available. In addition to project management courses, Planning Services will also provide public involvement and communication training.
Planning Services will use “The Transporter” and email notifications of what is available from the Project Management Academy.
Planning Services is researching how MPOs/FHWA can also to have access to the Project Management Academy so they can know and understand what the department’s processes are as well as to learn about project management activities to use in their agencies.
Develop a community engagement document
Stakeholders reiterated during the CSS workshop that they are unsure how to interact with the department.
Several stakeholders requested that the department develop a community engagement document that is for stakeholder education and for ITD staff to hand out to people, groups, and agencies on how they can engage or get involved with ITD; when they should participate in the decision-making process; identify the process to address public expectation; identify how can stakeholders can partner with ITD; and what they can comment on.
ITD will establish a Citizen’s Advisory Committee (with ITD staff and various stakeholders) to establish this document and create a Public Involvement Toolbox for citizens. Planning Services will create a checklist of questions to open a dialogue for their involvement. The following have already stated that they would like to be a part of the Committee (others to be identified later):
Deanna Smith – Idaho Smart Growth; Julia Oxarango-Ingram – Southern Idaho Rural Development Agency; Lori Porreca, FHWA; and Glenn Miles, KMPO
By May 2017, Planning Services will create and maintain on ITD’s website a “Citizen’s Communication” portal where stakeholders can make comments, access information and other important documents.
In addition, our stakeholders stated that they would like to know how they can access ITD grants (Rural Transportation Assistance Program (RTAP), Transportation Alternatives Program (TAP), etc.) when they are available. This will also be included in the “Citizen’s Communication” portal.
Publicize available public involvement tools
Planning Services is currently in the process of developing a public involvement website that will become a one-stop-shop for all CSS/public involvement tools and documents.
The website should be ready in April 2017. As soon as it is ready, Planning Services will conduct half-day training sessions at each District on what is available.
Develop a stakeholder identification list
Planning Services will see how they can create a drop-down/searchable list of potential external stakeholders (city, county, state/federal agencies, MPOs, economic agencies, tribes, interest groups, etc.) for project managers to consider when developing their charter.
In addition to the list, information will also include approximate timeframes needed for interaction.
This will be available later in 2017 on the communication website.
Consolidate CSS/public involvement plans and documents
By early 2018, Planning Services will work with others in the department to identify all plans and documents (CSS, Design Manual, Guide to Public Involvement, etc.) that contain public involvement information and consolidate into one location to reduce the amount of time it takes to find things.
Planning Services and other appropriate staff will ensure that all of the documents correlate and that there is no conflicting information/rules. It has been requested that there is a search engine as well.
ITD will begin working immediately with others to create a CSS/public involvement “best practices” site.
Best practices will be located on the communication webpage when it is available.
Use IPLAN as an information site
Planning Services in conjunction with GIS will work over the next year to enhance IPLAN to enable staff and citizens get data and project information.
Planning Services is currently in the process of creating a planning library on IPLAN that contains planning documents in one location. This is anticipated to be available in mid-2018.
This will include as many federal, state, regional, local, MPO, and other planning documents as possible.
Using IPLAN, staff, other agencies, and citizens will be able to search for planning documents easily.
District staff will assist Planning Services in getting community plans into the database and maintaining the information.