Www.transportation.ohio.gov



Path 1 Project Public Involvement Path 1 projects are simple maintenance projects, such as roadway resurfacing, culvert replacements, or guardrail installation. Path 1 projects have few or no right-of-way or utility impacts and do not necessitate many PI efforts beyond those completed during the STIP process. PI Meetings are typically not necessary for Path 1 projects; However, consultation with specific ODOT offices or Stakeholders may be necessary, depending on the project. For instance, if there are maintenance of traffic concerns or if there is some minor local controversy. Typically, the STIP process and sometimes press releases and PNLs will be the only PI necessary for these projects.Please consult with District Environmental staff during project initiation for assistance with determining the appropriate project path and for developing a scope and budget for public involvement activities. Templates and examples for the below requirements and considerations can be found in the Public Involvement Toolbox.REQUIREMENTSEnsure project is listed on STIP and that any PI performed during the STIP process is incorporated into the NEPA decisionProjects must be listed on the STIP/TIP and the next phase of development must be fully funded and included in the STIP/TIP to meet fiscal constraint requirements.? For projects with no STIP ID and that the next phase/authorization (PE Detail Design, RW phase, or CO phase) is using 100% state and/or local funds, please insert a comment on the STIP reference line for environmental clearance indicating that the next phase is “non-federal 100% [Insert state or local, as applicable] funded and is fiscally constrained.”? The District may then proceed with environmental document approval.The use of Statewide Line Items (SLI) is excellent as it greatly speeds up the process, however, we must have the reference ID number to meet the requirements. It’s not acceptable to just say a project meets the SLI criteria. It must be proven it meets the SLI criteria by being approved and included in the STIP and applicable TIPs. If the project is SLI eligible, it must receive a STIP SLI Group Reference ID, which is found on the View Phase tab in Ellis, before NEPA is approved.? NEPA may not be approved until this happens. Please refer to the STIP process document for the specific process to be followed. To document this requirement has been met:The STIP Reference ID number, Statewide Line Item number, or Damage Survey Report number must be added to Item 4 – STIP Reference # on the C1/C2 tab in EnviroNet. (Please refer to the STIP process document for the specific process to be followed.) It is not necessary to upload documentation to the project file in EnviroNet. Ensure Project Information is published on ODOT Website (Construction Plan, Work Plan, etc.)Ensure project information and one point of contact is listed on the ODOT website in a location that is easy for the public to find. This can be achieved by posting the district annual work plan, the annual construction plan, a list of upcoming projects, a dedicated project website, etc. When project data is entered into Ellis it is also automatically populated into ODOT’s Transportation Information Mapping System (TIMS), ODOT’s web-based project management system. To document this requirement has been met:It is not necessary to upload documentation to the project file in EnviroNet.Issue Public Notifications, as appropriate if impacts and/or detoursPublic notification beyond the STIP process and the website posting of the annual construction plan is not typically necessary for Path 1 projects since they are simple projects with no new right-of-way acquisitions and very little or no impacts. However, there may be instances where additional public notification might be necessary. For instance, if the project involves road closures/detours or if the project proposes to resurface an existing road with several access points or that is in front of an elementary school. Public notifications to those who are likely to be temporarily inconvenienced by the project is strongly recommended.Public notifications may be in the form of a press release, website posting, social media posting, flier, public notification letter, etc., and may be provided to those who could potentially be impacted by the project (such as access restrictions, right-of-way takes, etc.). To document this requirement has been met:The project description must include information about what was done, including MOT details – whether traffic will be maintained/detoured, etc.Include detour information, if known, or indicate that MOT is not known at this timePublic notification(s) uploaded to project file in EnviroNetInclude details regarding where the information was distributed, such as a mailing list, location of where fliers were posted/distributed, etc.Initiate Contact with Emergency and Public Services (EMS, Police, Fire, Schools, Hospitals, Local Floodplain Administrator, MPOs, RTAs, Etc.) during Planning or PE Phases of PDP (during NEPA) if detours and/or roadway restrictions are anticipated that may cause substantial traffic disruptionsContact with emergency and public services must be initiated during Planning or Preliminary Engineering if detours or roadway restrictions are anticipated that may result in substantial impacts to these resources (Such as emergency response times or bus route schedules, etc.). Contact to provide updates must be maintained throughout project development and construction. It is up to each ODOT district to develop a contact list and reach out to these entities to determine their preferred method of contact and/or dissemination of information. It may also be necessary to notify adjacent counties, especially if closures or detours have the potential to impact their roads. Examples of projects where coordination is not required may include rural two-lane maintenance/resurfacing projects, traffic signal maintenance projects, ditch maintenance, berm repairs, pothole patching, etc. that only require daily lane restrictions and will maintain two-way traffic utilizing a flagger. Backups for these types of projects are minimal and emergency services vehicles always take priority and are waved through the construction zone as quickly as possible. To document this requirement has been met:The project description must include a statement that PI activities during NEPA included initiation of MOT discussions with public and emergency services. Include details regarding this contact, including MOT details, etc.State whether traffic will be maintained/detoured, etc.Include detour information, if applicable/known, or indicate that MOT is not known at this timeUpload supporting documentation to the project file in EnviroNet including details regarding who was contacted and how they were communicated withMay include copies of correspondence, mailing list, phone log, etc.Floodplain findings must be posted to the ODOT websiteTo confirm and document all Public Involvement Requirements have been met:Select the appropriate dropdown for “Box 59. Public Involvement” on the C1/C2 tab which states, “Minimum PI Requirements Met; No Minor Public or Agency Controversy on Environmental Grounds.”ADDITIONAL CONSIDERATIONSConsult with Stakeholders, as necessaryStakeholder consultation may be needed if there are maintenance of traffic concerns or if some minor local controversy exists. Typical stakeholders might include the County Engineer, Service Director, Mayor, City Council, Township Trustees, fire, police, schools, businesses, historical society, transit providers, large employers in or adjacent to the project area, etc. To document stakeholder consultation:If stakeholder consultation occurs, supporting documentation must be uploaded to the project file in EnviroNet. Include details regarding who was contacted and how they were communicated withMay include copies of correspondence, mailing list, phone log, etc.DOCUMENTATIONODOT is required to retain project files and general administrative files related to NEPA responsibilities and provide evidence that all minimum PI requirements have been met. Every related decision-making document must be included in ODOT’s online environmental project file system, EnviroNet. To insure PI documentation requirements are being met, all PI activities must be documented and the materials must be uploaded to the project file in EnviroNet as they are developed, per the ODOT NEPA File Management and Documentation Guidance and ODOT’s Categorical Exclusion Guidance, which includes an appendix outlining the minimum documentation required for each level of environmental document.POST-NEPAIssue Public Notifications – Ensure standard plan notes are executed to publicly disclose:Construction schedule/updatesRoad closures and detoursPost-NEPA public notifications must adhere to the requirements in the ODOT Construction and Materials Specifications Manual (614 – Maintaining Traffic) and in the ODOT Traffic Engineering Manual (642-8 – Item 614, Maintaining Traffic (Notice of Closure Sign)). These notifications are usually requested by the contractor through the ODOT Project Manager and disseminated by the District Public Information Officer. These notifications may be in the form of a press release, public notification letter to those impacted by the project (such as access restrictions, right-of-way takes, etc.), social media posting or website posting, etc.To document post-NEPA notifications:It is not necessary to upload documentation to EnviroNet for Post-NEPA public notifications unless the notification is the result of and/or related to a specific Environmental Commitment. If the post-NEPA notification is the result of and/or related to a specific Environmental Commitment, documentation that proves the Environmental Commitment was met must be uploaded to the project file in EnviroNet. ................
................

In order to avoid copyright disputes, this page is only a partial summary.

Google Online Preview   Download