Stakeholder Meetings. The Engineer shall provide support personnel and exhibits for meetings with Stakeholders. The Stakeholders will be determined by the State in cooperation with the Engineer. Exhibits for the stakeholder meetings can be the same as those used for public meetings. The Engineer shall be responsible for handling the logistics of these meetings and providing minutes of the meeting and a list of attendees.
Stakeholder Meetings. The purpose of the stakeholder meetings will be to evaluate the efficacy of the collaborative relationship and review its processes as necessary to improve or correct any procedures/practices and efficiently identify and resolve the issues.
Stakeholder Meetings. We already have identified stakeholders through the Regional Transit Feasibility Study, and will work with MPO staff to expand that list. Possible stakeholders include staff from local cities, both counties, the MPO, Xxxxxxxxx Air Force Base, organizations identified in the 2013 Coordinated Plan (e.g., the Good Samaritan Society/Senior Companions, Black Hills Works, Disabled American Veterans, etc.), and other organizations that are providing services (e.g., Chairlift, Feeding South Dakota, Regional Health, etc.). We will also reach out to senior centers, disability advocates, social service agency staff, or other organizations serving low-income residents, non-English speakers, and minority populations. Through these various stakeholder activities, we anticipate that interaction will result in the following: ▪ Provision of useful and relevant information about local transportation programs and unmet transportation needs ▪ Sharing results of previous planning efforts or documentation of unmet needs ▪ Representation of a range of interests to ensure broad-based participation in the planning process ▪ Provision of comments and input from the group's stakeholders at major milestones of the project ▪ Participation in public outreach efforts ▪ Provision of comments, and confirmation of project planning assumptions
Stakeholder Meetings. These meetings can be conducted individually or in a small group setting, and can be in-person or via teleconference. Initial stakeholder meetings should take place prior to the development of design concepts, and will allow the Alta team to incorporate stakeholder concerns in the design process. Supplemental stakeholder meetings may be necessary during the conceptual design phase. • Open Streets: Where greater community interest is anticipated workshops or open houses provide an opportunity for the project team to engage with property owners, residents, and other corridor users to engage in the public process and influence the design components. Where appropriate and authorized by the city, we will utilize a more informal process that invites the public to gather at the site to experience the street and provide feedback. We assume up to five (5) public open house/open streets events will occur. As part of the Public Outreach and Development Strategy (Task 2.1), we will work with City of Bend staff and the TAC to identify timing for each meeting. Task 3: Data Collection & Reporting Kittelson will collect data in advance of the concept development process at each project site to create and justify the concept plans. The data will be documented in a manner that enables use as a measure of effectiveness of safety in a “Before” and “After” project completion comparison.
Stakeholder Meetings. Alta will work with City of Bend staff to identify key stakeholders along each corridor. Alta will schedule and attend up to 24 face-to-face or teleconference meetings with identified stakeholders. These meetings can be conducted individually or in a small group setting. Facilitating engagement early – before a concept is developed – will allow the Alta team to successfully incorporate design treatments to address concerns in the design where possible and instill a positive stakeholder process and the general buy-in of the business community. Assumptions • Up to 8 individual or small group meetings will be conducted with stakeholders along the 3rd Street corridor. • Up to four (4) individual or small group meetings will be conducted with stakeholders along the Greenwood East corridor. • Up to eight (8) individual or small group meetings will be conducted with stakeholders along the Greenwood West corridor. • Up to four (4) individual or small group meetings will be conducted with stakeholders along the Colorado Avenue corridor. • Meetings will occur on-site in Bend or virtually via teleconference. Deliverables • Stakeholder meeting notes
Stakeholder Meetings. Alta will work with City of Bend staff to identify key stakeholders. Alta will schedule and attend up to three (3) face-to-face or teleconference meetings with identified stakeholders. These meetings can be conducted individually or in a small group setting. Facilitating engagement early – before a concept is developed – will allow the Alta team to successfully incorporate design treatments to address concerns in the design where possible and instill a positive stakeholder process and the general buy-in of the business community. Assumptions • Up to three (3) individual or small group meetings will be conducted. • Meetings will occur on site in Bend or virtually via teleconference. • Stakeholder meetings for the Orchard District and Mountain View Neighborhood projects will be coordinated with corridor stakeholder meetings, Task 4.2. Deliverables • Stakeholder meeting notes
Stakeholder Meetings. WT will provide a list of potential key stakeholders. Utilizing available database information provided by Wichita Transit, the Consultant team establishes a stakeholder database for future campaign outreach efforts. This initial list serves as the mailing list for the Stakeholder Focus Groups (see below). It will include contact information for up to 100 contacts. (The stakeholder groups below will be refined based upon the Driving Issues, Goals and Objectives Workshop.) • residents • businesses & economic development groups • special interest groups, homeowner organizations & community organizations • agencies & officials • transportation advocates & environmental groups The Consultant team will conduct five small group discussions over a one-day period, to talk with key stakeholders about their specific issues and ask them what outreach messages and products they find useful. Each meeting will be one-hour in length with no more than twenty participants each. The Consultant team will develop a short list of general and specific questions to use during the discussion to gather information about transit issues. This gives the Team and Wichita Transit the subjective feedback on key questions, but in a methodology that can be sorted in different ways to find common ground and great ideas for message development.
Stakeholder Meetings. To better understand community goals and objectives, the CONSULTANT will facilitate up to three (3) focus group meetings early in the planning process with stakeholders identified by the TOWN. Stakeholder meetings may include property owners, business owners, elected officials, public agency staff, and other interested groups.
Stakeholder Meetings. Xxxxxx will attend up to four stakeholder meetings, listening to concerns and communicating the City’s value engineering efforts. Stakeholder meetings are assumed to be held with the Port of Skamania County and affected industries, and the Waste Water Clarifiers group.
Stakeholder Meetings. The purpose of the stakeholder meetings will be to evaluate the efficacy of the collaborative relationship and review its processes as necessary to improve or correct any procedures/practices and efficiently identify and resolve PROJECT issues. Date: July 23, 2012 UTILITY OWNER: Time Warner Agreement No: Task Order No: 0000000 00001 Project Title: California High-Speed Rail Project GENERAL This TASK ORDER supplements and amends the Construction Contract and Master Agreement. The purpose of this TASK ORDER is to authorize the FACILITY WORK for UTILITY OWNER. Each FACILITY that requires relocation will be handled under a separate subtask of this TASK ORDER.
