Lifecycle Sample Clauses

Lifecycle. 1.15.1. The Contractor may be required to provide long term maintenance in relation to the ECMs, ensuring the continued delivery of the energy performance for the full project term. The service should balance the requirements of the EnPC (including handback requirements) for the economic life of assets against the value for money of the project as a whole.
AutoNDA by SimpleDocs
Lifecycle. Customer is obliged to abide to Luware’s lifecycle and shall request installation of updates at least immediately after every 2nd major new release.
Lifecycle. Anchore Enterprise versions are numbered with an X.Y format where X represents the major version and Y represents the minor version. Support Services are available effective immediately upon the release of a new Generally Available (“GA”) major version of the Software, and such Support Services will be in effect for a period of either (i) eighteen (18) months after the applicable release date of such major version or (ii) six (6) months after the release date of the next major version, whichever period is longer. As part of Support Services, Anchore may provide minor version maintenance and other Updates during the period that the applicable major version is in effect. In order to continue receiving Support Services after any minor version release of Anchore Enterprise, Customer shall promptly update to such minor version. Anchore will provide supported upgrade paths between major versions of Anchore Enterprise as they become available.
Lifecycle. Subscriber may order Publicly-Trusted End-Entity Certificates with lifecycles equal to the lesser of: (i) the maximum lifecycle allowed by the CPS or Industry Standards, (ii) the lifecycles stated on the Order Form, or (iii) the remaining Service Term rounded up to a whole year. Sectigo may modify Certificate lifecycles as necessary to comply with changes in Industry Standards, third parties chained to Sectigo’s Root CA Certificates, Sectigo’s auditors, and Application Software Suppliers.
Lifecycle. Anchore Enterprise versions are using a semantic versioning format (x.y.z) where X represents the major version, Y represents the minor version, and (optionally) Z represents a patch version. Support Services are available effective immediately upon the release of a new Generally Available (“GA”) major version of the Software (“Generally Available Software”), and such Support Services will be in effect for a period of either (i) eighteen (18) months after the applicable release date of such major version or (ii) six (6) months after the release date of the next major version, whichever period is longer. As part of Support Services, Anchore may provide minor and patch updates during the period that the applicable major version is in effect. Anchore will provide supported upgrade paths between major versions of Anchore Enterprise as they become available.
Lifecycle. Xxx et. al. (2001) define the SLA life cycle in three phases (Figure 4). Firstly, the creation phase, in which the customers find service provider who matches their service requirements. Secondly, the opera- tion phase, in which a customer has read-only access to the SLA. Thirdly, the removal phase, in which SLA is terminated and all associated configuration information is removed from the service systems.
Lifecycle. SIEMonster may release new versions of the Software at any time. SIEMonster’s support commitments under this Exhibit cover the version of the Software that is current on the date of Product purchase and subsequent versions provided to Customer as part of Support until the later of (i) the release of a second subsequent major version, or (ii) one year from the release of the major version of which that version is a part. For example, if the version of the Software that is current as of the date of Product purchase is version 4.5, SIEMonster’s support commitments under this Exbihit shall continue until the later to occur of the release of version 6, or one year from the release of version 4. End of Exhibit C Exhibit D Professional Services
AutoNDA by SimpleDocs
Lifecycle how shall be ensured the adequacy of the document before distribution.
Lifecycle. The lifecycle of a document includes the publishing (proofreading, peer review, authorization, printing), the versioning and the workflow involved on this two processes. Concerning peer reviewing as a general rule: • Baseline documents shall be peer reviewed (verification process) by a group of people knowledgeable on the subject and those interfacing with the system/process described in the document. As default the peer review is done by the QUACO PMT or one of its members. • Non Baseline documents peer review process is generally managed by the author. In particular for the Tender Documents (Baseline Documents) • The JTEC reviews the Prior Information Notice, the draft Invitation to Tender, the draft Subcontracts, as prepared by the Lead Procurer in accordance with the laws applicable to it and the Specific PCP Requirements and submit to the STC all above documents for approval Concerning Authorization the process is adapted to the type of document. As a general rule: • For Baseline documents, the STC gives the Final approval of technical and contractual specifications for the PCP tender, Approval of tender selection and Management of knowledge (IPR), dissemination & exploitation documents. The Project Coordinator always approve all Baseline Documents. • For Non Baseline documents the process depends mainly on the type of document, but are mainly approved by the WP Leader. Every time there is a change in the lifecycle of a document a new version of the document shall be created. Changes are traced by the revision index. The revision index will increase by 0.1 for minor changes. In case of major changes will be the first digit that will be moved to the next integer.
Lifecycle. The current record of operation without any service is 18 years. The prior record was 16 years. Consumers have proven they can extend their systems life by running the system at least one time per week. Rather than not using the system at all for months and months. The timer can be programmed to run based on day-of-week. Example, program the timer to go ON at 1pm every Friday and OFF at 1:10pm. In keeping with ReadyTemp’s tradition of “industry first’s” we offer printable signage. We strongly recommend downloading placing the below signage in clear sight of water heater and water main / meter or any / all shut-off valves that directly affect the homes water supply. Doing so alerts person(s) that a recirculation system is installed on the property and must be turned off or power unplugged before shutting off water supply. We also recommend protecting signage with document protector or covering with clear tape to protect from moisture. Half-page sized printouts can be downloaded at: xxx.xxxxxxxxx.xxx/XXXX_XXXXXX_XXXXXXX_XXXXX_XXXXX.xxx Own a “TANK” water heater? Download our Water Heater Purge Table at xxxx://xxx.XxxxxXxxx.xxx/water-heater-purge-table.pdf Purging a quart from your water heater every 3 months helps prevent sediment buildup in your water heater making it last longer and run more efficient INSTALLATION INSTRUCTIONS To ensure proper installation of your OPTIMIZER-3000 unit, please read the instruction sheet completely before proceeding. Your READYTEMP unit is fully assembled upon delivery. Remove unit from the shipping container and examine the contents for any visible damage. Write the unit’s Serial number on the warranty / registration card on the last page of this manual.
Time is Money Join Law Insider Premium to draft better contracts faster.