Implementation, Timeline, and Licenses Sample Clauses

Implementation, Timeline, and Licenses. Provide your company’s timeline to meet the needs of this proposal with an implementation date of July 1, 2013. Include copies of any licenses required of the proposer(s) to fulfill this Contract. Copies of the licenses may be provided any time prior to implementation date.
AutoNDA by SimpleDocs

Related to Implementation, Timeline, and Licenses

  • Project Implementation The Borrower shall:

  • Software License Agreement 1) Customers acquiring software licenses under the Contract shall hold, use and operate such software subject to compliance with the Software License Agreement set forth in Appendix D of this Contract. No changes to the Software License Agreement terms and conditions may be made unless previously agreed to between Vendor and DIR. Customers may not add, delete or alter any of the language in Appendix D; provided however, that a Customer and Vendor may agree to additional terms and conditions that do not diminish a term or condition in the Software License Agreement, or in any manner lessen the rights or protections of Customer or the responsibilities or liabilities of Vendor. Order Fulfiller shall make the Software License Agreement terms and conditions available to all Customers at all times. 2) Compliance with the Software License Agreement is the responsibility of the Customer. DIR shall not be responsible for any Customer’s compliance with the Software License Agreement. If DIR purchases software licenses for its own use under this Contract, it shall be responsible for its compliance with the Software License Agreement terms and conditions.

  • Sublicense Agreements Sublicenses under this Section 2.3 shall be granted only pursuant to written agreements, which shall be subject to and consistent with the terms and conditions of this Agreement. Such Sublicense agreements shall contain, among other things, provisions to the following effect: 2.3.2.1 all provisions necessary to ensure Licensee’s ability to comply with Licensee’s obligation under or not violate the provisions of Sections 4.4, 4.5, 4.6, 5.1, 5.3, 5.4, 8.1 and 11.1; 2.3.2.2 a section substantially the same as Article 9 (Indemnification), which also shall state that the Indemnitees (as defined in Section 9.1) are intended third party beneficiaries of such Sublicense agreement for the purpose of enforcing such indemnification; 2.3.2.3 in the event of termination of the license set forth in Section 2.1.1 above (in whole or in part (e.g., termination of the license as to a Licensed Product or in a particular country)), any existing Sublicense shall terminate to the extent of such terminated license; provided, however, that, for each Sublicensee, upon termination of the license, if the Sublicensee is not then in breach of the Sublicense agreement such that Licensee would have the right to terminate such Sublicense agreement, such Sublicensee shall have the right to obtain a license from Harvard on the same terms and conditions as set forth herein, which shall not impose any representations, warranties, obligations or liabilities on Harvard that are not included in this Agreement, provided that (a) the scope of the license granted directly by Harvard to such Sublicensee shall be coextensive with the scope of the license granted by Licensee to such Sublicensee, (b) if the Sublicense granted to such Sublicensee was non-exclusive, such Sublicensee shall not have the right to participate in the prosecution or enforcement of the Patent Rights under the license granted to it directly by Harvard and (c) if there are more than one Sublicensee, each Sublicensee that is granted a direct license shall be responsible for a pro rata share of the reimbursement due under Section 6.2.3 of this Agreement (based on the number of direct licenses under the Patent Rights in effect on the date of reimbursement); 2.3.2.4 the Sublicensee shall only be entitled to sublicense its rights under such Sublicense agreement on the terms set forth in this Section 2.3; and 2.3.2.5 the Sublicensee shall not be entitled to assign the Sublicense agreement without the prior written consent of Harvard, except that Sublicensee may assign the Sublicense agreement to a successor in connection with the merger, consolidation or sale of all or substantially all of its assets or that portion of its business to which the Sublicense agreement relates; provided, however, that any permitted assignee agrees in writing in a manner reasonably satisfactory to Harvard to be bound by the terms of such Sublicense agreement.

  • End User License Agreement This work is licensed under a Creative Commons Attribution-NonCommercial-NoDerivs 3.0 Unported License. xxxx://xxxxxxxxxxxxxxx.xxx/licenses/by-nc-nd/3.0/ You are free to: Share: to copy, distribute and transmit the work Under the following conditions: Attribution: You must attribute the work in the manner specified by the author (but not in any way that suggests that they endorse you or your use of the work).

  • Proposed Policies and Procedures Regarding New Online Content and Functionality By October 31, 2017, the School will submit to OCR for its review and approval proposed policies and procedures (“the Plan for New Content”) to ensure that all new, newly-added, or modified online content and functionality will be accessible to people with disabilities as measured by conformance to the Benchmarks for Measuring Accessibility set forth above, except where doing so would impose a fundamental alteration or undue burden. a) When fundamental alteration or undue burden defenses apply, the Plan for New Content will require the School to provide equally effective alternative access. The Plan for New Content will require the School, in providing equally effective alternate access, to take any actions that do not result in a fundamental alteration or undue financial and administrative burdens, but nevertheless ensure that, to the maximum extent possible, individuals with disabilities receive the same benefits or services as their nondisabled peers. To provide equally effective alternate access, alternates are not required to produce the identical result or level of achievement for persons with and without disabilities, but must afford persons with disabilities equal opportunity to obtain the same result, to gain the same benefit, or to reach the same level of achievement, in the most integrated setting appropriate to the person’s needs. b) The Plan for New Content must include sufficient quality assurance procedures, backed by adequate personnel and financial resources, for full implementation. This provision also applies to the School’s online content and functionality developed by, maintained by, or offered through a third-party vendor or by using open sources. c) Within thirty (30) days of receiving OCR’s approval of the Plan for New Content, the School will officially adopt, and fully implement the amended policies and procedures.

  • License Agreements (a) Each Borrower and Guarantor shall (i) promptly and faithfully observe and perform all of the material terms, covenants, conditions and provisions of the material License Agreements to which it is a party to be observed and performed by it, at the times set forth therein, if any, (ii) not do, permit, suffer or refrain from doing anything that could reasonably be expected to result in a default under or breach of any of the terms of any material License Agreement, (iii) not cancel, surrender, modify, amend, waive or release any material License Agreement in any material respect or any term, provision or right of the licensee thereunder in any material respect, or consent to or permit to occur any of the foregoing; except, that, subject to Section 9.19(b) below, such Borrower or Guarantor may cancel, surrender or release any material License Agreement in the ordinary course of the business of such Borrower or Guarantor; provided, that, such Borrower or Guarantor (as the case may be) shall give Agent not less than thirty (30) days prior written notice of its intention to so cancel, surrender and release any such material License Agreement, (iv) give Agent prompt written notice of any material License Agreement entered into by such Borrower or Guarantor after the date hereof, together with a true, correct and complete copy thereof and such other information with respect thereto as Agent may request, (v) give Agent prompt written notice of any material breach of any obligation, or any default, by any party under any material License Agreement, and deliver to Agent (promptly upon the receipt thereof by such Borrower or Guarantor in the case of a notice to such Borrower or Guarantor and concurrently with the sending thereof in the case of a notice from such Borrower or Guarantor) a copy of each notice of default and every other notice and other communication received or delivered by such Borrower or Guarantor in connection with any material License Agreement which relates to the right of such Borrower or Guarantor to continue to use the property subject to such License Agreement, and (vi) furnish to Agent, promptly upon the request of Agent, such information and evidence as Agent may reasonably require from time to time concerning the observance, performance and compliance by such Borrower or Guarantor or the other party or parties thereto with the material terms, covenants or provisions of any material License Agreement. (b) Each Borrower and Guarantor will either exercise any option to renew or extend the term of each material License Agreement to which it is a party in such manner as will cause the term of such material License Agreement to be effectively renewed or extended for the period provided by such option and give prompt written notice thereof to Agent or give Agent prior written notice that such Borrower or Guarantor does not intend to renew or extend the term of any such material License Agreement or that the term thereof shall otherwise be expiring, not less than sixty (60) days prior to the date of any such non-renewal or expiration. In the event of the failure of such Borrower or Guarantor to extend or renew any material License Agreement to which it is a party, Agent shall have, and is hereby granted, the irrevocable right and authority, at its option, to renew or extend the term of such material License Agreement, whether in its own name and behalf, or in the name and behalf of a designee or nominee of Agent or in the name and behalf of such Borrower or Guarantor, as Agent shall determine at any time that an Event of Default shall exist or have occurred and be continuing. Agent may, but shall not be required to, perform any or all of such obligations of such Borrower or Guarantor under any of the License Agreements, including, but not limited to, the payment of any or all sums due from such Borrower or Guarantor thereunder. Any sums so paid by Agent shall constitute part of the Obligations. (c) No Borrower or Guarantor shall assign, sell, mortgage, lease, transfer, pledge, hypothecate, grant a security interest in or lien upon, encumber, grant an exclusive or non-exclusive license relating to any Intellectual Property, or otherwise dispose of any Intellectual Property, in each case without the prior written consent of Agent, except that any Borrower or Guarantor may, after written notice to Agent, grant a non-exclusive license relating to any Intellectual Property to another Borrower or Guarantor in the ordinary course of business.

  • Development Plans Shipper has provided Gatherer with a report attached hereto as Exhibit D (the “Current Development Plan”) describing in detail, as of January 1, 2017, the planned development, drilling, and production activities to take place with respect to Dedicated Production for the applicable Development Period. The information contained in the TERMS IN THIS EXHIBIT HAVE BEEN REDACTED BECAUSE CONFIDENTIAL TREATMENT FOR THOSE TERMS HAS BEEN REQUESTED. THE REDACTED MATERIAL HAS BEEN FILED SEPARATELY WITH THE SECURITIES AND EXCHANGE COMMISSION, AND THE TERMS HAVE BEEN MARKED AT THE APPROPRIATE PLACE WITH TWO ASTERISKS (**). Current Development Plan is broken out on a Subsystem-by-Subsystem basis and, with respect to the first three Years covered by the Current Development Plan, on a Quarter-by-Quarter basis, and with respect to the remaining Years covered by the Current Development Plan, on a Year-by-Year basis. The Current Development Plan attached hereto has been approved by the Parties. (a) From time to time during each Year of the Term, the Parties shall meet to discuss the planned development, drilling, and production activities that Shipper expects to take place with respect to Dedicated Production for the then-applicable Development Period. Shipper and Gatherer shall each make their respective representatives available to participate in such meetings and discussions. No later than August 1 of each such Year, Shipper shall provide (or cause to be provided) to Gatherer a proposed update of the then-currently agreed Development Plan, prepared on the same basis as the Current Development Plan and describing in detail the planned development, drilling, and production activities to take place with respect to Dedicated Production for the then-applicable Development Period (any such update, an “Updated Development Plan” and, together with the Current Development Plan, each, a “Development Plan”). Notwithstanding anything herein to the contrary, in no event shall Gatherer be required to agree to any Updated Development Plan and corresponding updated Gathering System Plan that contains a Committed Build-Out that (i) has a corresponding Target Completion Date that occurs after the end of the Initial Term, and (ii) Gatherer, in its sole discretion, does not wish to approve. (b) Each proposed Development Plan shall include information as to the following, in each case, broken out on a Subsystem-by-Subsystem basis and, with respect to the first three Years covered by such Development Plan, on a Quarter-by-Quarter basis, and, with respect to the remaining Years covered by such Development Plan, on a Year-by-Year basis: (i) all Xxxxx that, as of the date such Development Plan was delivered, are currently in existence and (A) the production therefrom is being delivered into the Gathering System, or (B) are awaiting connection to the Gathering System; (ii) the Xxxxx that are expected to be drilled during the time period covered by such Development Plan (each such Well reflected in such Development Plan, a “Planned Well”), and the estimated timing of the drilling of such Planned Xxxxx; (iii) forward-looking production estimates for the applicable time period covered by such Development Plan for all Shipper Gas (A) that Shipper reasonably and in good faith believes will become owned or Controlled by Shipper during the time period covered by such Development Plan, and/or (B) that will be produced from (I) in the aggregate, all Xxxxx then-existing and (II) in the aggregate, any Planned Xxxxx included in such Development Plan (such collective estimates described in subsections (A) and (B), both with respect to a particular Quarter and an entire Year, the “Dedicated Production Estimates”); TERMS IN THIS EXHIBIT HAVE BEEN REDACTED BECAUSE CONFIDENTIAL TREATMENT FOR THOSE TERMS HAS BEEN REQUESTED. THE REDACTED MATERIAL HAS BEEN FILED SEPARATELY WITH THE SECURITIES AND EXCHANGE COMMISSION, AND THE TERMS HAVE BEEN MARKED AT THE APPROPRIATE PLACE WITH TWO ASTERISKS (**). (iv) forward-looking estimates for the applicable time period covered by such Development Plan of the aggregate volumes of those Shipper Injected Liquids that Shipper intends to Tender to the Injection Points hereunder to receive the System Services (such estimates, both with respect to a particular Quarter and an entire Year, the “System Liquids Estimates” and, together with the Dedicated Production Estimates, the “System Production Estimates”); (v) (A) each new receipt point (including the location thereof) proposed by Shipper with respect to the System Production Estimate reflected in such Development Plan (each such receipt point, including those located at the site of a Planned Well, a “Planned Receipt Point”), (B) each Receipt Point at which Shipper expects to Tender Shipper Gas and/or Shipper Injected Liquids reflected in such Development Plan into the Gathering System, and (C) the estimated portion of the System Production Estimate contained in such Development Plan that Shipper expects to Tender at each such Receipt Point and Planned Receipt Point; (vi) the earliest date on which each Planned Well included in the Development Plan is estimated to be completed and producing, which date shall not be earlier than three Months after the January 1st that is immediately subsequent to the date that the Development Plan that initially reflected such Planned Well was delivered to Gatherer hereunder; (vii) the anticipated characteristics of the production from the Xxxxx and Planned Xxxxx reflected in such Development Plan (including liquids content and gas and liquids composition) and the projected production volumes and production pressures applicable thereto; provided that Shipper may utilize the existing and historical production information from similarly situated Xxxxx; (viii) (A) each new delivery point (including the location thereof) proposed by Shipper with respect to the System Production Estimate reflected in such Development Plan (each such delivery point, a “Planned Delivery Point”), (B) each Delivery Point at which Shipper expects Shipper Gas produced from the Xxxxx and Planned Xxxxx reflected in such Development Plan to be redelivered to Shipper, (C) each Delivery Point at which Shipper expects any Drip Liquids allocated to Shipper in accordance with this Agreement and/or Shipper Injected Liquids to be redelivered to Shipper, and (D) the estimated portion of the System Production Estimate contained in such Development Plan that Shipper expects to be redelivered to Shipper at each such Delivery Point and Planned Delivery Point; (ix) any (A) proposed revision to the then-existing Dedicated Area and/or any then-existing Dedicated Contract and/or (B) any new contract that Shipper proposes to be a Dedicated Contract; and (x) other information reasonably requested by Gatherer that is relevant to the design, construction, and operation of the Gathering System, including (A) any Subsystem Extension proposed by Shipper, (B) the relevant Receipt Point, Planned Receipt Point, Delivery Point and Planned Delivery Point facilities applicable to such TERMS IN THIS EXHIBIT HAVE BEEN REDACTED BECAUSE CONFIDENTIAL TREATMENT FOR THOSE TERMS HAS BEEN REQUESTED. THE REDACTED MATERIAL HAS BEEN FILED SEPARATELY WITH THE SECURITIES AND EXCHANGE COMMISSION, AND THE TERMS HAVE BEEN MARKED AT THE APPROPRIATE PLACE WITH TWO ASTERISKS (**). Development Plan, and (C) any treating, processing, or liquids handling facilities proposed by Shipper that may be required for any Shipper Gas and/or Shipper Injected Liquids to meet applicable Downstream Facility specifications at the Delivery Points.

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

  • Implementation Plan The Authority shall cause to be prepared an Implementation Plan meeting the requirements of Public Utilities Code Section 366.2 and any applicable Public Utilities Commission regulations as soon after the Effective Date as reasonably practicable. The Implementation Plan shall not be filed with the Public Utilities Commission until it is approved by the Board in the manner provided by Section 4.9.

  • Project Implementation Manual The Recipient, through the PCU, shall: (i) take all action required to carry out Parts 1.1, 1.3, 1.4, 2, 3.1(b), 3.2, 3.3 and 4 (ii) of the Project in accordance with the provisions and requirements set forth or referred to in the Project Implementation Manual; (ii) submit recommendations to the Association for its consideration for changes and updates of the Project Implementation Manual as they may become necessary or advisable during Project implementation in order to achieve the objective of Parts 1.1, 1.3, 1.4, 2, 3.1(b), 3.2, 3.3 and 4(ii) of the Project; and (iii) not assign, amend, abrogate or waive the Project Implementation Manual or any of its provisions without the Association’s prior agreement. Notwithstanding the foregoing, if any of the provisions of the Project Implementation Manual is inconsistent with the provisions of this Agreement, the provisions of this Agreement shall prevail and govern.

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