Fees for Internal Use—Deployment Solution Clause Samples

Fees for Internal Use—Deployment Solution. The license fee for a perpetual, Internal Use License of Deployment Solution (previously known as Altiris eXpress) under Section 3.1 shall be [*]. Upgrade Protection, as set forth in Section 8.2 of the Agreement, is not included in such license fee. The license fee is payable by HP at the end of each calendar quarter and is based on the number of nodes installed during such calendar quarter. If HP desires to receive Upgrade Protection for such licenses then HP shall pay an additional annual fee of [*] in advance of the annual Upgrade Protection coverage period. Altiris reserves the right to increase the license fee or annual Upgrade Protection fee effective [*].”
View Source

Related to Fees for Internal Use—Deployment Solution

  • Cost Responsibility for Interconnection Facilities and Distribution Upgrades 4.1 Interconnection Facilities 4.2 Distribution Upgrades

  • Availability of Verizon Telecommunications Services 3.1 Verizon will provide a Verizon Telecommunications Service to PNG for resale pursuant to this Attachment where and to the same extent, but only where and to the same extent that such Verizon Telecommunications Service is provided to Verizon’s Customers. 3.2 Except as otherwise required by Applicable Law, subject to Section 3.1 of this Attachment, Verizon shall have the right to add, modify, grandfather, discontinue or withdraw Verizon Telecommunications Services at any time, without the consent of PNG. 3.3 To the extent required by Applicable Law, the Verizon Telecommunications Services to be provided to PNG for resale pursuant to this Attachment will include a Verizon Telecommunications Service customer-specific contract service arrangement (“CSA”) (such as a customer specific pricing arrangement or individual case based pricing arrangement) that Verizon is providing to a Verizon Customer at the time the CSA is requested by PNG.

  • Registration Data Directory Services Until ICANN requires a different protocol, Registry Operator will operate a WHOIS service available via port 43 in accordance with ▇▇▇ ▇▇▇▇, and a web-­‐based Directory Service at <whois.nic.TLD> providing free public query-­‐based access to at least the following elements in the following format. ICANN reserves the right to specify alternative formats and protocols, and upon such specification, the Registry Operator will implement such alternative specification as soon as reasonably practicable. Registry Operator shall implement a new standard supporting access to domain name registration data (SAC 051) no later than one hundred thirty-­‐five (135) days after it is requested by ICANN if: 1) the IETF produces a standard (i.e., it is published, at least, as a Proposed Standard RFC as specified in RFC 2026); and 2) its implementation is commercially reasonable in the context of the overall operation of the registry. 1.1. The format of responses shall follow a semi-­‐free text format outline below, followed by a blank line and a legal disclaimer specifying the rights of Registry Operator, and of the user querying the database. 1.2. Each data object shall be represented as a set of key/value pairs, with lines beginning with keys, followed by a colon and a space as delimiters, followed by the value. 1.3. For fields where more than one value exists, multiple key/value pairs with the same key shall be allowed (for example to list multiple name servers). The first key/value pair after a blank line should be considered the start of a new record, and should be considered as identifying that record, and is used to group data, such as hostnames and IP addresses, or a domain name and registrant information, together. 1.4. The fields specified below set forth the minimum output requirements. Registry Operator may output data fields in addition to those specified below, subject to approval by ICANN, which approval shall not be unreasonably withheld.

  • YOUR BILLING RIGHTS - KEEP THIS NOTICE FOR FUTURE USE This notice tells you about your rights and our responsibilities under the Fair Credit Billing Act.

  • Updated Information Submission by Interconnection Customer The updated information submission by the Interconnection Customer, including manufacturer information, shall occur no later than one hundred eighty (180) Calendar Days prior to the Trial Operation. The Interconnection Customer shall submit a completed copy of the Electric Generating Unit data requirements contained in Appendix 1 to the LGIP. It shall also include any additional information provided to the Participating TO and the CAISO for the Interconnection Studies. Information in this submission shall be the most current Electric Generating Unit design or expected performance data. Information submitted for stability models shall be compatible with the Participating TO and CAISO standard models. If there is no compatible model, the Interconnection Customer will work with a consultant mutually agreed to by the Parties to develop and supply a standard model and associated information.