Minnesota Department of Transportation

511 Travel Info

Highway 252/I-94 Environmental Review

Brooklyn Center, Brooklyn Park and Minneapolis

Project committee process

This is a diagram of the project committee process. The first three steps are to share information, collect and analyze data, and discuss assumptions. The fourth step is a draft document presented to the Technical Advisory Committee. Followed by revisions. Next coordination with Policy Advisory Committee, followed by revisions. Then engagement with other agencies, followed by revisions. Finally a recommendation from the policy advisory committee. More revisions and engagement with the general public. Conclusions are then reported by to the committees.
Project committee process flowchart.
Click graphic for larger version
.

Below is information regarding the various project committees and how they function in the larger Environmental Impact Statement (EIS) project process.

Technical documents that form the basis of the Scoping Decision Document are developed by project staff then reviewed by committee before review by the broader public.

  1. Share existing, background and reference information: MnDOT staff and consultant project team members review background and reference information collected during Phase 1 or provided by city and county project partners.
  2. Data collection and analysis: Project team members identify what new data is needed. For example, new traffic data can be collected on the interstate, entrance or exits ramps, or adjacent street network. The team collects and analyzes the data.
  3. Discuss assumptions and rough framework: The project team discusses any assumptions made in the analysis and starts to develop a rough framework of the technical document.
  4. Draft for Technical Advisory Committee: A draft is shared with the Technical Advisory Committee for review and comment. Engineering and planning staff from MnDOT, Federal Highway Administration, Hennepin County, the cities of Minneapolis, Brooklyn Center and Brooklyn Park along with other government entities serve on the Technical Advisory Committee. The committee provides technical advice to the project team.
  5. Revisions: The project team gathers feedback and revises the draft at each step in the process.
  6. Revisions: The project team presents information, receives feedback and revises the draft.
  7. Engagement with Cooperating and Participating Agencies: The draft is shared with the Cooperating and Participating Agencies as required under the National Environmental Policy Act. Cooperating agencies are Federal agencies with jurisdiction not including the lead agency. Participating agencies are those with an interest in the project. Their roles are defined by the Council on Environmental Quality which oversees the NEPA implementation. 
  8. Revisions: The project team presents information, receives feedback and revises the draft.
  9. Recommendations to Policy Advisory Committee: The project team presents the draft to the Policy Advisory Committee (PAC). The PAC consists of elected and appointed officials who guide policy and funding decisions, review recommendations from technical staff, provide input on public engagement and identify important community issues. Current PAC members include Federal Highway Administration Minnesota Division, Metropolitan Council Chair, county commissioners, mayor and city council members, and state senators and representatives.
  10. Revisions: The project team presents information, receives feedback and revises the draft.
  11. Engagement with Community and Broader Public: The project team presents the technical information to the public in both its technical document form and in plain language format. Online and in-person engagement opportunities will provide opportunities for the project team to learn from the community’s lived experiences.
  12. Revisions: The project team presents information, receives feedback and revises the draft.
  13. Report back to PAC; Continuing analysis and engagement as needed: The project team reports back to the PAC following the broader public engagement. Analysis, revision and further engagement continue. The technical information becomes a base for the Scoping Decision Document that also flows through the committee and public review cycles.

Meeting documents:

Policy Advisory Committee

The Policy Advisory Committee (PAC) is made up of elected and appointed officials from MnDOT, Hennepin County, FHWA, City of Brooklyn Park, City of Brooklyn Center, City of Minneapolis, and Metropolitan Council. Its role is to guide policy and funding decisions, review recommendations from technical staff, provide input on public engagement and identify important community issues. These policy decisions are then prepared for public consumption. The PAC meets approximately quarterly.

Membership
  • Minnesota Commissioner of Transportation
  • State Senators
  • State Representatives
  • Metropolitan Council Chair
  • Metropolitan Council Members
  • Hennepin County Commissioner
  • Brooklyn Center Mayor
  • Brooklyn Center Council Member
  • Brooklyn Park Council Members
  • Minneapolis Council Members
  • Federal Highway Division Administrator
  • MnDOT District Engineer
  • MnDOT District Area Manager
Technical Advisory Committee

The Technical Advisory Committee (TAC) provides leadership and guidance for resolution of technical issues related to project options and refinements considered as part of the DEIS. The TAC meets monthly to refine project elements to prepare for public engagement.

The TAC includes Hennepin County, City of Brooklyn Park, City of Brooklyn Center, City of Minneapolis, MnDOT, FHWA, Metropolitan Council, Metro Transit, and Project Consultants.