Deliverable Creation and Review Process Sample Clauses

Deliverable Creation and Review Process 
AutoNDA by SimpleDocs

Related to Deliverable Creation and Review Process

  • Review Process A/E's Work Product will be reviewed by County under its applicable technical requirements and procedures, as follows:

  • Deliverables Upon satisfactory completion of the work authorization, the Engineer shall submit the deliverables as specified in the executed work authorization to the State for review and acceptance.

  • Performance Improvement Process 9.5.1 The purpose of the Performance Improvement Process is to remedy or mitigate the impact of a Performance Factor. The Performance Improvement Process may include: a requirement that the Hospital develop an Improvement Plan; or an amendment of the Hospital’s obligations as mutually agreed by the parties.

  • Claims Process (1) In order to seek payment from the Settlement Amount, a Class Member must submit a completed Claim Form to the Administrator, in accordance with the provisions of the Plan of Allocation, on or before the Claims Bar Deadline and any Class Member who fails to do so shall not share in any distribution made in accordance with the Plan of Allocation unless the relevant court orders otherwise as provided in section 18.4.

  • Order Coordination and Order Coordination-Time Specific 2.1.9.1 “Order Coordination” (OC) allows BellSouth and Global Connection to coordinate the installation of the SL2 Loops, Unbundled Digital Loops (UDL) and other Loops where OC may be purchased as an option, to Global Connection’s facilities to limit end user service outage. OC is available when the Loop is provisioned over an existing circuit that is currently providing service to the end user. OC for physical conversions will be scheduled at BellSouth’s discretion during normal working hours on the committed due date. OC shall be provided in accordance with the chart set forth below.

  • Required Procurement Procedures for Obtaining Goods and Services The Grantee shall provide maximum open competition when procuring goods and services related to the grant-assisted project in accordance with Section 287.057, Florida Statutes.

  • Project/Milestones Taxpayer develops and manufactures various products for use in the defense, aerospace and security industries. In consideration for the Credit, Taxpayer agrees to expand its operations at various locations throughout California, including El Segundo, Redondo Beach, Palmdale, Sunnyvale, Woodland Hills, Azusa and Rancho Xxxxxxxx. As part of its expansion, Taxpayer will invest in manufacturing equipment, computer and electrical equipment and make tenant improvements to the above facilities. Additionally, Taxpayer will hire full-time employees as part of its expansion (collectively, the “Project”). Further, Taxpayer agrees to satisfy the milestones as described in Exhibit “A” (“Milestones”) and must maintain Milestones for a minimum of three (3) taxable years thereafter. In the event Taxpayer employs more than the number of Full- time employees, determined on an annual full-time equivalent basis, than required in Exhibit A, for purposes of satisfying the “Minimum Annual Salary of California Full-time Employees Hired” and the “Cumulative Average Annual Salary of California Full-time Employees Hired,” Taxpayer may use the salaries of any of the Full-time employees hired and retained within the required time period. For purposes of calculating the “Minimum Annual Salary of California Full-time Employees Hired” and the “Cumulative Average Annual Salary of California Full-time Employees Hired,” the salary of any full-time employee that is not employed by the taxpayer for the entire taxable year shall be annualized. In addition, Xxxxxxxx agrees that any full-time employee hired after the effective date of this agreement that is a “qualified full-time employee” (as defined in RTC section 23636) shall be excluded from the calculation of the net increase of full-time employees required by this Agreement if Taxpayer claims the credit allowed by RTC section 23636.

  • The Performance Improvement Process (a) The Performance Improvement Process will focus on the risks of non- performance and problem-solving. It may include one or more of the following actions:

  • Proposing Integration Activities in the Planning Submission No integration activity described in section 6.3 may be proposed in a CAPS unless the LHIN has consented, in writing, to its inclusion pursuant to the process set out in section 6.3(b).

  • Change Management Process If Customer or Oracle requests a change in any of the specifications, requirements, Deliverables, or scope (including drawings and designs) of the Professional Services described in any Statement of Work, the party seeking the change shall propose the applicable changes by written notice. Within forty-eight (48) hours of receipt of the written notice, each party’s project leads shall meet, either in person or via telephone conference, to discuss and agree upon the proposed changes. Oracle will prepare a change order describing the proposed changes to the Statement of Work and the applicable change in fees and expenses, if any (each, a “Change Order”). Change Orders are not binding unless and until they are executed by both parties. Executed Change Orders shall be deemed part of, and subject to, this Addendum. If the parties disagree about the proposed changes, the parties shall promptly escalate the change request to their respective senior management for resolution.

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