Technical Work Group/Stakeholder Meeting and Workshops Sample Clauses

Technical Work Group/Stakeholder Meeting and Workshops. District and Consultant key staff and subconsultants as determined necessary and appropriate by Consultant, subject to DPM approval, will coordinate and attend periodic Technical Work Group (TWG)/Stakeholder meetings and workshops with District staff, stakeholders, and regulatory and resource agencies, as needed, to review and discuss progress of the work. For each meeting or workshop, the Consultant shall prepare the meeting agenda, presentations, and notes and submit them for review by the District. Consultant shall incorporate review comments and shall submit final meeting documents to the DPM no later than 30 days before the date of the workshop. Consultant shall prepare meeting minutes and notes to document the outcomes of each Workshop.
Sample 1
AutoNDA by SimpleDocs

Related to Technical Work Group/Stakeholder Meeting and Workshops

  • Construction Progress Meetings The Design Professional shall attend Construction Progress Meetings periodically held by the Contractor at the Site on a schedule determined by the Contractor. The Design Professional shall review the minutes of the meeting and provide his written comments to the minutes to the Owner and Contractor within seven calendar days after receipt of the meeting minutes.

  • ROAD WORK PHASE APPROVAL Purchaser shall obtain written approval from the Contract Administrator upon completion of each of the following phases of road work:  Drainage installation  Subgrade compaction  Rock compaction SUBSECTION RESTRICTIONS

  • Information Technology Enterprise Architecture Requirements If this Contract involves information technology-related products or services, the Contractor agrees that all such products or services are compatible with any of the technology standards found at xxxxx://xxx.xx.xxx/iot/2394.htm that are applicable, including the assistive technology standard. The State may terminate this Contract for default if the terms of this paragraph are breached.

  • Synchronisation Commissioning and Commercial Operation 8.1 The Developer shall provide at least forty (40) days advanced preliminary written notice and at least twenty (20) days advanced final written notice to ESCOM of the date on which it intends to synchronize the Power Project to the Grid System.

  • SUPPLIER PUBLICATIONS 4.1 Any marketing materials in relation to this Framework Agreement that that Supplier produces must comply in all respects with the Branding Guidance. The Supplier will periodically update and revise such marketing materials.

  • Technical Proposal The technical proposal may be presented in free format. It shall not exceed ten pages, not counting the CVs. It shall respect the following page limit and structure: • Technical methodology (max. 7 pages) • Quality management (max. 1 page) • Project management (max. 1 page) • Resource management (proposal (max. 1 page) + CVs of experts)

  • Drug and Alcohol Testing – Safety-Sensitive Functions A. Employees required to have a Commercial Driver’s License (CDL) are subject to pre-employment, post-accident, random and reasonable suspicion testing in accordance with the U.S. Department of Transportation rules, Coast Guard Regulations (46 CFR Part 16) or the Federal Omnibus Transportation Employee Testing Act of 1991. The testing will be conducted in accordance with current Employer policy.

  • Synchronization, Commissioning and Commercial Operation 4.1.1 The Power Producer shall give at least thirty (30) days written notice to the SLDC and GUVNL, of the date on which it intends to synchronize the Power Project to the Grid System.

  • Access Toll Connecting Trunk Group Architecture 9.2.1 If CBB chooses to subtend a Verizon access Tandem, CBB’s NPA/NXX must be assigned by CBB to subtend the same Verizon access Tandem that a Verizon NPA/NXX serving the same Rate Center Area subtends as identified in the LERG.

Time is Money Join Law Insider Premium to draft better contracts faster.