Technical Meetings definition

Technical Meetings has the meaning as set out in Section 11.4;

Split View

AI-Powered Contracts

Draft, Review & Redline at the Speed of AI

Get StartedSchedule a Demo

Technical Meetings. The CONSULTANT shall attend all technical meetings necessary to execute the Scope of Services of this contract. This includes meetings with DEPARTMENT and/or Agency staff, between disciplines and subconsultants, such as access management meetings, pavement design meetings, local governments, railroads, airports,, progress review meetings (phase review), and miscellaneous meetings. The CONSULTANT shall prepare, and submit to the DEPARTMENT’s Project Manager for review, the meeting minutes for all meetings attended by them. The meeting minutes are due within five (5) days of attending the meeting. Quality Assurance/Quality Control: It is the intention of the DEPARTMENT that design CONSULTANTS, including their subconsultant(s), are held responsible for their work, including plans review. Detailed checking of CONSULTANT plans or assisting in designing portions of the project for the CONSULTANT is not the intent of having external design consultants. The purpose of CONSULTANT plan reviews is to ensure that CONSULTANT plans follow the plan preparation procedures outlined in the Plans Preparation Manual, that state and federal design criteria are followed with the DEPARTMENT concept, and that the CONSULTANT submittals are complete. All subconsultant document submittals shall be submitted by the subconsultant directly to the CONSULTANT for their independent Quality Assurance/Quality Control review and subsequent submittal to the DEPARTMENT.

Technical Meetings means the meetings of the Technical Committee as set forth in Section IV below.

Examples of Technical Meetings in a sentence

• The CIO or IT Director is responsible for attendance at all Technical Meetings called by the State.

• The IS Coordinator is responsible for attendance at all Technical Meetings called by the State.

• Staff hours for other personnel attending Activity Technical Meetings are included in the meeting task for that specific Activity.

• The costs and approach of evaluating containment shall be discussed and agreed upon by representatives of Plaintiffs, ▇▇▇▇▇▇▇▇▇ and AISLIC at the monthly Technical Meetings, or determined by Cost Consultant.

• Includes only the Prime Consultant Project Manager's time for travel and attendance at Activity Technical Meetings and other meetings listed in the meeting summary for Task 3.6 on tab 3 Project General Task of the staff hour forms.

• Video and telephonic options will be provided for all Technical Meetings, though Technical Committee members are encouraged to attend in-person.

• The Non-Federal Parties agree to discuss and evaluate proposed Projects as early as possible, and nothing herein shall prevent or discourage communication among the members outside of the scheduled Technical Meetings.

• Normally, Project coordination Committee meetings will be called in association with Technical Meetings.

• Progress meetings will be held once a month as agreed with the Engineer and Technical Meetings will be on an ongoing basis as and when is deemed necessary by the Engineer.

• Monthly Technical Meetings shall be conducted between SpaceDev and University.

More Definitions of Technical Meetings

Technical Meetings. Includes meetings with COUNTY and/or Agency staff, between disciplines and subconsultants, such as management meetings, design meetings, local governments, railroad companies, progress review meetings (phase review), and miscellaneous meetings. The CONSULTANT shall prepare, and submit to the COUNTY’s Project Manager for review, the meeting minutes for all meetings attended by them. The meeting minutes are due within five (5) days of attending the meeting.

Technical Meetings. The CONSULTANT shall attend all technical meetings necessary to execute the Scope of Services of this contract. This includes meetings with VILLAGE and/or Agency staff, between disciplines and subconsultants. Quality Assurance/Quality Control: It is the intention of the VILLAGE that design CONSULTANTS, including their subconsultant(s), are held responsible for their work, including plans review. It is the CONSULTANT’s responsibility to independently and continually QC their plans and other deliverables. The CONSULTANT shall be responsible for the professional quality, technical accuracy and coordination of all surveys, designs, drawings, specifications and other services furnished by the CONSULTANT.

Technical Meetings. The CONSULTANT shall attend all technical meetings necessary to execute the Scope of Services of this contract. This includes meetings with CITY and/or Agency staff, between disciplines and subconsultants, such as access management meetings, pavement design meetings, local governments, railroads, airports,, progress review meetings (phase review), and miscellaneous meetings. The CONSULTANT shall prepare, and submit

Technical Meetings. The CONSULTANT shall attend a technical meeting prior the 60% plan submittal; prior to the 90% plan submittal; and one prior to the Final plan submittal. • Utility Coordination Meetings: The CONSULTANT shall attend two utility coordination meetings to be held within eighteen calendar days of the 60% and 90% design review submittals along with one field meeting. • Plans-in-hand Field Review: The CONSULTANT and the COUNTY shall meet at the project site after the 60% comments have been addressed. This field review is intended to ensure that all project issues and impacts are considered in the construction plans.