1 / 24

Ohio Transportation and Engineering Conference Session 58 - October 29, 2014

Public Involvement: A Process Renewed Kevin E. Davis Office Of Environmental Services Ohio Department of Transportation. Ohio Transportation and Engineering Conference Session 58 - October 29, 2014. Revitalization Was Needed. Original PI Manual developed in 2001

Download Presentation

Ohio Transportation and Engineering Conference Session 58 - October 29, 2014

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript


  1. Public Involvement:A Process RenewedKevin E. DavisOffice Of Environmental ServicesOhio Department of Transportation Ohio Transportation and Engineering Conference Session 58 - October 29, 2014

  2. Revitalization Was Needed • Original PI Manual developed in 2001 • The appropriate level of PI not always commensurate • Enough effort given to say we did something • PI only initiated when controversy arose • Underserved populations not always included • Comments ignored or treated with condescension • No formal training Ohio Transportation and Engineering Conference – Session 58– October 29, 2014

  3. Changing the Mindset • Not us vs. them • Does not necessarily stop a project • PI doesn’t start with a meeting • PI not just dependent on impacts • Being inclusive and providing feedback is good! Ohio Transportation and Engineering Conference – Session 58– October 29, 2014

  4. PI Matters • Required by NEPA • Communities have a vested interest in shaping transportation decisions • Discover, address, and mitigate potential impacts to quality of life and day-to-day activities • Enhances decision-making • Stakeholder and public input is valued • Early and continuous engagement • Concerns can be raised and addressed • Alternate perspectives can be given Ohio Transportation and Engineering Conference – Session 58– October 29, 2014

  5. Instill Core Principles • Plan and prepare with diligence • Demographic diversity and inclusion • Collaborative and shared learning • Transparency and trustworthiness • Be proactive • Sustain engagement • Participatory culture Ohio Transportation and Engineering Conference – Session 58– October 29, 2014

  6. Bottom Line Ohio Transportation and Engineering Conference – Session 58– October 29, 2014

  7. Integrating NEPA • Identify and document potential impacts to the human and natural environment • Acquaint with or be made aware of key stakeholders or members of the public • Balance transportation, stakeholder, public, and environmental resource needs Ohio Transportation and Engineering Conference – Session 58– October 29, 2014

  8. PI/PDP Relationship • Projects categorized as one of five paths • Each path advances through five phases • PI is “right-sized” to support decision-making • Part of each phase • Provides flexibility • Ensures appropriate PI activities are conducted Ohio Transportation and Engineering Conference – Session 58– October 29, 2014

  9. Planning • PI begins here! • PI from TIP/STIP development is factored in • Analysis determines type of project or solution needed to solve existing transportation problem • High level planning and development • Stakeholders and the public are provided preliminary information on the need for a transportation project • Opportunities to provide input at the onset assists in the development of viable transportation solutions • A wide range of input and decisions may exist Ohio Transportation and Engineering Conference – Session 58– October 29, 2014

  10. Planning • Specific details regarding impacts not known • An overview of potential social, economic, and environmental impacts is presented • Conducting outreach during this stage is critical • Can make or break project development • Strategic outreach • Understand community needs • Residents, businesses, industries, etc. Ohio Transportation and Engineering Conference – Session 58– October 29, 2014

  11. Preliminary Engineering • Process of collecting more detailed information begins • First level technical and environmental studies • Feasible alternatives developed • Stakeholder consultation initiated, as needed • Contact with property owners initiated, as needed • Public notifications/PI activities, as needed • PI activities during this phase may include presenting feasible alternatives to stakeholders and the public Ohio Transportation and Engineering Conference – Session 58– October 29, 2014

  12. Environmental Engineering • Detailed analysis conducted on feasible alternatives • May have a preferred alternative at this point • Technical and environmental data • High level of design (Stage 1/maybe Stage II) • Concentrate on stakeholder and public needs • Higher level of interaction • PI activities become more focused during this phase • Public notifications/PI activities, as needed • May include stakeholder and public meetings Ohio Transportation and Engineering Conference – Session 58– October 29, 2014

  13. Final Engineering/Construction • Completing detailed design for preferred alternative • Stage 3 plans • ROW acquisition begins • Majority of PI activities have been completed • Status updates provided, as needed • Resource specific PI activities may occur • Section 106, Noise PI, Aesthetic Design • Resource specific PI process is slightly different • Obtain input to enhance decision-making Ohio Transportation and Engineering Conference – Session 58– October 29, 2014

  14. PI Strategy • Avoid oversimplify the need for PI • Every project requires some level of PI • Do not do more than what is reasonably required • Be flexible – know when to elevate the level of PI • Be proactive (not just reactive) • Consider community needs appropriately as a project progresses Ohio Transportation and Engineering Conference – Session 58– October 29, 2014

  15. Level of PI • Minimum requirements integrated into the PDP • Assures appropriate PI is conducted • Project-by-project • Not interpreted to mean each project will only require the minimum • Ensures legal requirements are met • Enhances decision-making • Commensurate with a project’s type and complexity • Anticipated impacts and unusual circumstances may elevate the level of PI needed Ohio Transportation and Engineering Conference – Session 58– October 29, 2014

  16. Path 1 - Minimum PI • Traditional maintenance type actions • No right-of-way (ROW) or utility impacts • Include PI conducted per the STIP process • List active projects on district website • Provide contact information • Provide public notifications • Standard plan notes executed by the contractor • Construction schedule coordination, detours, roadway closures, etc. Ohio Transportation and Engineering Conference – Session 58– October 29, 2014

  17. Path 2- Minimum PI • Involve minor ROW acquisitions • Culvert/bridge replacements • Turn lanes, shoulders, simple widening • Property Owner Notification • ROW impacts and access restrictions • Counts as a PI activity • Potential stakeholder consultation • Maintenance of traffic concerns • Minor local controversy • Provide appropriate public notifications Ohio Transportation and Engineering Conference – Session 58– October 29, 2014

  18. Path 3 - Minimum PI • More complex type projects • Broader range of technical issues and impacts • Utility relocationsand ROW acquisition • Increased involvement with property owners • Stakeholders more involved • Increased emphasis on public notifications • Press release • PIO involvement • Project updates via fliers, emails, • Public meetings, as appropriate Ohio Transportation and Engineering Conference – Session 58– October 29, 2014

  19. Path 4/5 - Minimum PI • High level and complex roadway/structure work • Adding capacity • Substantial utility relocationsand ROW acquisition • Higher level involvement with property owners • Higher level of stakeholder consultation • Higher level of public notifications • Press releases more numerous and specific • Local media attention • Multiple project updates via different mediums • Use of social media more prominent • Public meetings and public hearings Ohio Transportation and Engineering Conference – Session 58– October 29, 2014

  20. Renewed Process • Level of PI dependent on project type and complexity • Identified stakeholders stay involved • Issues and concerns are addressed • Establish early and continuous communication with stakeholders and the public • Understand and address diverse concerns, needs, values, interests, and desires of the community • Consider needs of underserved populations • Conduct PI in accordance with Title VI Ohio Transportation and Engineering Conference – Session 58– October 29, 2014

  21. A Renewed Process • Identify the means, methods, and opportunities to solicit and gather input during decision-making • What regulatory steps to follow • Who should be involved • How to deliver the message effectively • Updated PI Manual approved in June 2014 • Minimum PI requirements defined • Underserved population outreach better defined • Emphasis on how/when to conduct PI Ohio Transportation and Engineering Conference – Session 58– October 29, 2014

  22. PI Training • Part of the Project Manager Training Program • Internal to ODOT • First class was held on August 5, 2014 • Three additional classes next year • Online registration via OES training webpage • Developing a second-tier class • The “how-to” of PI • More hands on and interactive Ohio Transportation and Engineering Conference – Session 58– October 29, 2014

  23. PI Relief Center • Kevin E. Davis • Environmental Supervisor - OES Policy • 614-752-2788 • Kevin.Davis@dot.state.oh.us Ohio Transportation and Engineering Conference – Session 58– October 29, 2014

More Related