Finalization and Conference Room Checkpoints Sample Clauses

Finalization and Conference Room Checkpoints. The purpose of the Finalization Workshop for each grouping is to work down the open configuration gaps (the Gap Analysis Punch List ‐ those items remaining after the Gap Analysis workshops), driving closure of the Gap Analysis activity for each group. The Finalization Workshops are time‐boxed (as defined in the Project Schedule) and require dedicated time from the Health District and Accela project teams to rapidly close the open gaps for each grouping. New items identified during the Finalization Workshop outside of the Punch List must be completed within the established time box for the Finalization Workshop. If the new item cannot be completed within the established time box, the Change Control process is triggered. When the Gap Analysis Punch List is resolved, the Health District Responsible Expert will sign the Deliverable Acceptance Document, documenting finalization of the solution configuration. To promote information sharing outside of the day‐to‐day project team following the Finalization Workshop, the Health District’s Responsible Expert will demonstrate the work‐in‐ progress software to key stakeholders during a Conference Room Checkpoint. The demonstration will cover 1‐3 application types that demonstrates the solution from end‐to‐end. Finalization Workshop expectations: Accela will run a Configuration Report from the Civic Platform showing the details of the record’s tailored configuration. The Health District team will review, test and confirm the tailored solution, enabling the teams to move to the next scheduled project activity. Solution changes (requests for configuration or customization outside the available solution tailoring framework) are deferred for review as per the Change Control process defined in the Project Management Plan. Conference Room Checkpoint expectations: Accela will collaborate with the Health District users to select scenarios that should be demonstrated to peers and executive sponsors in a Conference Room Checkpoint meeting. Health District staff will lead a Conference Room Checkpoint meeting to demonstrate the completed solution configuration to peers and executive sponsors. Once the Conference Room Checkpoint is conducted and confirmed, the teams will move to the next scheduled project activity. Output:  Finalized tailored solution ready for Develop stage Accela Responsibilities: Close out agreed upon action items from the Punch List to support the Finalization Workshop Assist the Health District’s Responsible ...
AutoNDA by SimpleDocs

Related to Finalization and Conference Room Checkpoints

  • Program Management 1.1.01 Implement and operate an Immunization Program as a Responsible Entity

  • Project Management Plan 1 3.4.1 Developer is responsible for all quality assurance and quality control 2 activities necessary to manage the Work, including the Utility Adjustment Work.

  • STATEWIDE CONTRACT MANAGEMENT SYSTEM If the maximum amount payable to Contractor under this Contract is $100,000 or greater, either on the Effective Date or at any time thereafter, this section shall apply. Contractor agrees to be governed by and comply with the provisions of §§00-000-000, 00-000-000, 00-000-000, and 00- 000-000, C.R.S. regarding the monitoring of vendor performance and the reporting of contract information in the State’s contract management system (“Contract Management System” or “CMS”). Contractor’s performance shall be subject to evaluation and review in accordance with the terms and conditions of this Contract, Colorado statutes governing CMS, and State Fiscal Rules and State Controller policies.

  • PERFORMANCE MANAGEMENT SYSTEM 5.1 The Employee agrees to participate in the performance management system that the Employer adopts or introduces for the Employer, management and municipal staff of the Employer.

  • Project Management Project Management Institute (PMI) certified project manager executing any or all of the following: • Development of Project Charter • Development of project plan and schedule • Coordination and scheduling of project activities across customer and functional areas • Consultation on operational and infrastructure requirements, standards and configurations • Facilitate project status meetings • Timely project status reporting • Address project issues with functional areas and management • Escalation of significant issues to customers and executive management • Manage project scope and deliverable requirements • Document changes to project scope and schedule • Facilitate and document project closeout

  • Configuration Management The Contractor shall maintain a configuration management program, which shall provide for the administrative and functional systems necessary for configuration identification, control, status accounting and reporting, to ensure configuration identity with the UCEU and associated cables produced by the Contractor. The Contractor shall maintain a Contractor approved Configuration Management Plan that complies with ANSI/EIA-649 2011. Notwithstanding ANSI/EIA-649 2011, the Contractor’s configuration management program shall comply with the VLS Configuration Management Plans, TL130-AD-PLN-010-VLS, and shall comply with the following:

  • Quality Management System Supplier hereby undertakes, warrants and confirms, and will ensue same for its subcontractors, to remain certified in accordance with ISO 9001 standard or equivalent. At any time during the term of this Agreement, the Supplier shall, if so instructed by ISR, provide evidence of such certifications. In any event, Supplier must notify ISR, in writing, in the event said certification is suspended and/or canceled and/or not continued.

  • Program Monitoring and Evaluation (c) The Recipient shall prepare, or cause to be prepared, and furnish to the Association not later than six months after the Closing Date, a report of such scope and in such detail as the Association shall reasonably request, on the execution of the Program, the performance by the Recipient and the Association of their respective obligations under the Legal Agreements and the accomplishment of the purposes of the Financing.”

  • Construction Phase Services 3.1.1 – Basic Construction Services

  • 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.

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