Content and approval of Work Plans Sample Clauses

Content and approval of Work Plans. (a) Aurizon Network will develop, in consultation with the User Committee, a Work Plan for each Stage which sets out in reasonable detail: (1) the Capacity Increment, and the scope of the Extension which is to be investigated to achieve the Capacity Increment; (2) a schedule of the Services to be undertaken during the Stage(including the date for commencement of the Services for that Stage (if applicable) and the date by which the Services the subject of the Stage are to be completed); (3) the standard, consistent with industry standards, to which each of the matters set out in Schedule 6 will be addressed during the Stage; (4) a budget for the Services to be undertaken during the Stage; (5) the matters to be included in the Report, including (A) details on the scope, standard and design of the Extension, including the performance standards and capacity analysis on which that design has been prepared (together with copies of an static and dynamic modelling results and any other technical or engineering studies, advices or reports on which the Report is based); (B) an outline of the procurement methodology for the Extension works; (C) a schedule for the construction and completion of the Extension; (D) the scope of the Extension which is to be investigated during that Stage (which must be sufficient to achieve the Capacity Increment); and (E) an estimate of the costs of constructing and completing the Extension to the level of definition specified in the relevant definition for the Stage; (6) any Supply Chain Operating Assumptions developed under the Access Undertaking; (7) any formatting and presentation requirements for the Report; (8) identifying any Authority Approvals which will be required to be obtained during the performance of the Services the subject of the Stage; and (9) such other matters as are required to be addressed by the User Committee, and which otherwise conforms with the relevant definition of each Stage. (b) Aurizon Network agrees that the matters to be included in the Report under clause 3.1(a)(5) for the Feasibility Stage must be of sufficient detail and in such form as to: (1) enable the ‘scope of works’, ‘target cost’, ‘target schedule’ and ‘procurement methodology’ in a Construction Funding Agreement to be populated; and (2) ensure that the Report completed for the Feasibility Stage is based on industry standards sufficient to ensure that the Report is bankable. (c) Aurizon Network agrees that the Report for each Stage will reflec...
AutoNDA by SimpleDocs

Related to Content and approval of Work Plans

  • Project Plans The Contractor: must carry out the Contractor's Activities in accordance with, and otherwise implement, the Project Plans; and for the purposes of subparagraph (i), must: prepare Project Plans based, where applicable, on the draft Project Plans lodged by the Contractor in its tender for the Contractor's Activities, and otherwise in accordance with the requirements of the Contract and submit them to the Contract Administrator so as to ensure that there is no delay or disruption to the Contractor's Activities and in any event no later than the number of days specified in the Contract Particulars after the Award Date for each Project Plan; not commence any of the Contractor's Activities to which any Project Plan applies, unless the Contract Administrator has had the number of days specified in the Contract Particulars for each Project Plan to review the Project Plan and has not rejected the Project Plan; if any Project Plan is rejected, submit an amended Project Plan to the Contract Administrator; in any event, finalise each Project Plan so as to ensure that there is no delay or disruption to the Contractor's Activities and in any event in accordance with the requirements of the Contract to the satisfaction of the Contract Administrator; after each Project Plan has been finalised: regularly review, update and amend each Project Plan in accordance with the process set out in each Project Plan (and otherwise at least on each anniversary of the Award Date); update or amend a Project Plan on request of the Contract Administrator; and continue to correct any defects in or omissions from a Project Plan (whether identified by the Contract Administrator or the Contractor), and submit an updated or amended Project Plan to the Contract Administrator, after which: the Contractor must continue to comply with the requirements of the then current Project Plan until the process in subparagraph (ii) has been completed in respect of the updated or amended Project Plan; and subsubparagraphs B - E will apply (to the extent applicable); and document and maintain detailed records of all: reviews, updates, amendments and submissions of each Project Plan; audits or other monitoring of each Project Plan; and training and awareness programs and communications provided to Contractor and subcontractor personnel in respect of each Project Plan (including each updated or amended Project Plan). The Contractor will not be relieved from compliance with any of its obligations under the Contract or otherwise at law or in equity as a result of: the implementation of, and compliance with, the requirements of any Project Plan; any direction by the Contract Administrator concerning a Project Plan or the Contractor's compliance or non-compliance with a Project Plan; any audit or other monitoring by the Contract Administrator or anyone else acting on behalf of the Commonwealth of the Contractor's compliance with a Project Plan; or any failure by the Contract Administrator, or anyone else acting on behalf of the Commonwealth, to detect any defect in or omission from a Project Plan including where any such failure arises from any negligence on the part of the Contract Administrator or other person.

  • Software License Terms (a) Software that is made available by a Provider to Recipient in connection with any Service (any such Software being referred to herein as “TSA-Licensed Software”) provided hereunder will be subject to the terms set forth in this Section 3.5 except as otherwise provided in the applicable Service Schedule. The Provider hereby grants to the Recipient a non-exclusive, non-transferable license to use, in object code form, any TSA-Licensed Software that is made available by the Provider pursuant to a Service Schedule. For the avoidance of doubt, the Provider that makes available any TSA-Licensed Software in connection with the provision of any Service retains the unrestricted right to enhance or otherwise modify such TSA-Licensed Software at any time, provided that such enhancements or other modifications do not disrupt the provision of such Service to the Recipient. (b) The Recipient may not exceed the number of licenses, agents, tiers, nodes, seats, or other use restrictions or authorizations, if any, specified in the applicable Service Schedule. Some TSA-Licensed Software may require license keys or contain other technical protection measures. The Recipient acknowledges that the Provider may monitor the Recipient’s compliance with use restrictions and authorizations remotely, or otherwise. If the Provider makes a license management program available which records and reports license usage information, the Recipient agrees to appropriately install, configure and execute such license management program. (c) Unless otherwise permitted by the Provider, the Recipient may only make copies or adaptations of the TSA-Licensed Software for archival purposes or when copying or adaptation is an essential step in the authorized use of TSA-Licensed Software. If the Recipient makes a copy for backup purposes and installs such copy on a backup device, the Recipient may not operate such backup installation of the TSA-Licensed Software without paying an additional license fee, except in cases where the original device becomes inoperable. If a copy is activated on a backup device in response to failure of the original device, the use on the backup device must be discontinued when the original or replacement device becomes operable. The Recipient may not copy the TSA-Licensed Software onto or otherwise use or make it available on, to, or through any public or external distributed network. Licenses that allow use over the Recipient’s intranet require restricted access by authorized users only. (d) The Recipient must reproduce all copyright notices that appear in or on the TSA-Licensed Software (including documentation) on all permitted copies or adaptations. Copies of documentation are limited to internal use. (e) Notwithstanding anything to the contrary herein, certain TSA-Licensed Software may be licensed under the applicable Service Schedule for use only on a computer system owned, controlled, or operated by or solely on behalf of the Recipient and may be further identified by the Provider by the combination of a unique number and a specific system type (“Designated System”) and such license will terminate in the event of a change in either the system number or system type, an unauthorized relocation, or if the Designated System ceases to be within the possession or control of the Recipient. (f) The Recipient will not modify, reverse engineer, disassemble, decrypt, decompile, or make derivative works of the TSA-Licensed Software. Where the Recipient has other rights mandated under statute, the Recipient will provide the Provider with reasonably detailed information regarding any intended modifications, reverse engineering, disassembly, decryption, or decompilation and the purposes therefor. (g) The Recipient may permit a consultant or subcontractor to use TSA-Licensed Software at the licensed location for the sole purpose of providing services to the Recipient. (h) Upon expiration or termination of the Service Schedule under which TSA-Licensed Software is made available, the Recipient will destroy the TSA-Licensed Software. The Recipient will remove and destroy or return to the Provider any copies of the TSA-Licensed Software that are merged into adaptations, except for individual pieces of data in the Recipient’s database. The Recipient will provide certification of the destruction of TSA-Licensed Software, and copies thereof, to the Provider. The Recipient may retain one copy of the TSA-Licensed Software subsequent to expiration or termination solely for archival purposes. (i) The Recipient may not sublicense, assign, transfer, rent, or lease the TSA-Licensed Software to any other person except as permitted in this Section 3.5. (j) The Recipient agrees that the Provider may engage a third party designated by the Provider and approved by the Recipient (such approval not to be unreasonably withheld) to audit the Recipient’s compliance with the Software License terms. Any such audit will be at the Provider’s expense, require reasonable notice, and will be performed during normal business hours. Such third party will be required to execute a non-disclosure agreement that restricts such third party from disclosing confidential information of the Recipient to the Provider, except to the extent required to report on the extent to which the Recipient is not in compliance with the Software License terms.

  • Preparatory Contract Negotiations Meetings Where operational requirements permit, the Employer will grant leave without pay to an employee to attend preparatory contract negotiations meetings.

  • Statement of Work The Statement of Work to which Grantee is bound is incorporated into and made a part of this Grant Agreement for all purposes and included as Attachment A.

  • Work Order (s) means a detailed scope of work for a Service required by Transnet, including timeframes, Deliverable, Fees and costs for the supply of the Service to Transnet, which may be appended to this Agreement from time to time.

  • Project Work Plan The Statement of Work is the formal document incorporated into the Grant. The Project Work Plan documents how the Grantee will achieve the performance measures outlined in the Grant. Changes to the Statement of Work require an amendment. Project Work Plans may be changed with written approval from PEI and the Grantee.

  • Research Plan The Parties recognize that the Research Plan describes the collaborative research and development activities they will undertake and that interim research goals set forth in the Research Plan are good faith guidelines. Should events occur that require modification of these goals, then by mutual agreement the Parties can modify them through an amendment, according to Paragraph 13.6.

  • Commercialization License Subject to the terms of this Agreement, including without limitation Section 2.2 and Theravance's Co-Promotion rights in Section 5.3.2, Theravance hereby grants to GSK, and GSK accepts, an exclusive license under the Theravance Patents and Theravance Know-How to make, have made, use, sell, offer for sale and import Alliance Products in the Territory.

  • Work Plans Tenant shall prepare and submit to Landlord for approval schematics covering the Tenant Improvements prepared in conformity with the applicable provisions of this Work Letter (the “Draft Schematic Plans”). The Draft Schematic Plans shall contain sufficient information and detail to accurately describe the proposed design to Landlord and such other information as Landlord may reasonably request. Landlord shall notify Tenant in writing within ten (10) business days after receipt of the Draft Schematic Plans whether Landlord approves or objects to the Draft Schematic Plans and of the manner, if any, in which the Draft Schematic Plans are unacceptable. Landlord’s failure to respond within such ten (10) business day period shall be deemed approval by Landlord. If Landlord reasonably objects to the Draft Schematic Plans, then Tenant shall revise the Draft Schematic Plans and cause Landlord’s objections to be remedied in the revised Draft Schematic Plans. Tenant shall then resubmit the revised Draft Schematic Plans to Landlord for approval, such approval not to be unreasonably withheld, conditioned or delayed. Landlord’s approval of or objection to revised Draft Schematic Plans and Tenant’s correction of the same shall be in accordance with this Section until Landlord has approved the Draft Schematic Plans in writing or been deemed to have approved them. The iteration of the Draft Schematic Plans that is approved or deemed approved by Landlord without objection shall be referred to herein as the “Approved Schematic Plans.”

  • Clinical Trials The studies, tests and preclinical and clinical trials conducted by or on behalf of, or sponsored by, the Company, or in which the Company has participated, that are described in the Registration Statement, the Time of Sale Disclosure Package or the Prospectus, or the results of which are referred to in the Registration Statement, the Time of Sale Disclosure Package or the Prospectus, were and, if still pending, are being conducted in all material respects in accordance with protocols, procedures and controls pursuant to, where applicable, accepted professional and scientific standards for products or product candidates comparable to those being developed by the Company and all applicable statutes, rules and regulations of the FDA, the EMEA, Health Canada and other comparable drug and medical device (including diagnostic product) regulatory agencies outside of the United States to which they are subject; the descriptions of the results of such studies, tests and trials contained in the Registration Statement, the Time of Sale Disclosure Package or the Prospectus do not contain any misstatement of a material fact or omit a material fact necessary to make such statements not misleading; the Company has no knowledge of any studies, tests or trials not described in the Disclosure Package and the Prospectus the results of which reasonably call into question in any material respect the results of the studies, tests and trials described in the Registration Statement, the Time of Sale Disclosure Package or Prospectus; and the Company has not received any notices or other correspondence from the FDA, EMEA, Health Canada or any other foreign, state or local governmental body exercising comparable authority or any Institutional Review Board or comparable authority requiring or threatening the termination, suspension or material modification of any studies, tests or preclinical or clinical trials conducted by or on behalf of, or sponsored by, the Company or in which the Company has participated, and, to the Company’s knowledge, there are no reasonable grounds for the same. Except as disclosed in the Registration Statement, the Time of Sale Disclosure Package and the Prospectus, there has not been any violation of law or regulation by the Company in its respective product development efforts, submissions or reports to any regulatory authority that could reasonably be expected to require investigation, corrective action or enforcement action.

Draft better contracts in just 5 minutes Get the weekly Law Insider newsletter packed with expert videos, webinars, ebooks, and more!