OnDemand Solution Package Use Sample Clauses

OnDemand Solution Package Use. During the Subscription Term, subject to the terms and conditions of the Agreement (including Usage Limits stated in the Order Form) and payment of all fees when due, for each OnDemand Solution Package to which Customer subscribes, Ariba (i) grants Customer a non-exclusive, non-transferable right to allow Registered Users to access the associated Site solely for support of Customer's internal business operations, and (ii) shall provide the Enablement Services included in the applicable OnDemand Solution Package. Registered User accounts cannot be shared or used by more than one individual. Customer shall be solely responsible for connection of Customer's computers to a telecommunications service that provides Internet access in a secure manner. All rights not expressly granted to Customer are reserved by Ariba.
AutoNDA by SimpleDocs

Related to OnDemand Solution Package Use

  • EPP query-­‐command RTT Refers to the RTT of the sequence of packets that includes the sending of a query command plus the reception of the EPP response for only one EPP query command. It does not include packets needed for the start or close of either the EPP or the TCP session. EPP query commands are those described in section 2.9.2 of EPP RFC 5730. If the RTT is 5-­‐times or more the corresponding SLR, the RTT will be considered undefined.

  • ODUF Pack Rejection 6.4.1 Image Access will notify BellSouth within one (1) business day of rejected packs (via the mutually agreed medium). Packs could be rejected because of pack sequencing discrepancies or a critical edit failure on the Pack Header or Pack Trailer records (e.g., out-of-balance condition on grand totals, invalid data populated). Standard ATIS EMI error codes will be used. Image Access will not be required to return the actual rejected data to BellSouth. Rejected packs will be corrected and retransmitted to Image Access by BellSouth.

  • Loop Provisioning Involving Integrated Digital Loop Carriers 2.6.1 Where Xxxx has requested an Unbundled Loop and BellSouth uses IDLC systems to provide the local service to the End User and BellSouth has a suitable alternate facility available, BellSouth will make such alternative facilities available to Xxxx. If a suitable alternative facility is not available, then to the extent it is technically feasible, BellSouth will implement one of the following alternative arrangements for Xxxx (e.g. hairpinning): 1. Roll the circuit(s) from the IDLC to any spare copper that exists to the customer premises. 2. Roll the circuit(s) from the IDLC to an existing DLC that is not integrated. 3. If capacity exists, provide "side-door" porting through the switch. 4. If capacity exists, provide "Digital Access Cross Connect System (DACS)- door" porting (if the IDLC routes through a DACS prior to integration into the switch). 2.6.2 Arrangements 3 and 4 above require the use of a designed circuit. Therefore, non- designed Loops such as the SL1 voice grade and UCL-ND may not be ordered in these cases. 2.6.3 If no alternate facility is available, and upon request from Xxxx, and if agreed to by both Parties, BellSouth may utilize its Special Construction (SC) process to determine the additional costs required to provision facilities. Xxxx will then have the option of paying the one-time SC rates to place the Loop.

  • MOTION FOR PRELIMINARY APPROVAL The Parties agree to jointly prepare and file a motion for preliminary approval (“Motion for Preliminary Approval”) that complies with the Court’s current checklist for Preliminary Approvals.

  • Response to Demand Letter Within 10 days after the receipt of the Demand Letter, RMC shall either: (a) cure the breach to OIG’s satisfaction and pay the applicable Stipulated Penalties or (b) request a hearing before an HHS administrative law judge (ALJ) to dispute OIG’s determination of noncompliance, pursuant to the agreed upon provisions set forth below in Section X.E. In the event RMC elects to request an ALJ hearing, the Stipulated Penalties shall continue to accrue until RMC cures, to OIG’s satisfaction, the alleged breach in dispute. Failure to respond to the Demand Letter in one of these two manners within the allowed time period shall be considered a material breach of this CIA and shall be grounds for exclusion under Section X.D.

  • PRELIMINARY APPROVAL OF SETTLEMENT Promptly upon execution of this Stipulation, Lead Plaintiffs will move for preliminary approval of the Settlement, certification of the Settlement Class for settlement purposes only, and the scheduling of a hearing for consideration of final approval of the Settlement, which motion shall be unopposed by Defendants. Concurrently with the motion for preliminary approval, Lead Plaintiffs shall apply to the Court for, and Defendants shall agree to, entry of the Preliminary Approval Order, substantially in the form attached hereto as Exhibit A.

  • Escrow Format Specification Deposit’s Format. Registry objects, such as domains, contacts, name servers, registrars, etc. will be compiled into a file constructed as described in draft-xxxxx-xxxxxxx-registry-data-escrow, see Part A, Section 9, reference 1 of this Specification and draft-xxxxx-xxxxxxx-dnrd-objects-mapping, see Part A, Section 9, reference 2 of this Specification (collectively, the “DNDE Specification”). The DNDE Specification describes some elements as optional; Registry Operator will include those elements in the Deposits if they are available. If not already an RFC, Registry Operator will use the most recent draft version of the DNDE Specification available at the Effective Date. Registry Operator may at its election use newer versions of the DNDE Specification after the Effective Date. Once the DNDE Specification is published as an RFC, Registry Operator will implement that version of the DNDE Specification, no later than one hundred eighty (180) calendar days after. UTF-8 character encoding will be used.

  • Preliminary Approval Order “Preliminary Approval Order” means the order of the Court preliminarily approving this Settlement Agreement.

  • ODUF Packing Specifications 6.3.1 A pack will contain a minimum of one message record or a maximum of 99,999 message records plus a pack header record and a pack trailer record. One transmission can contain a maximum of 99 packs and a minimum of one pack.

  • Software Use Case Red Hat Enterprise Linux Developer Suite Subscription Services for Red Hat Enterprise Linux Developer Suite are available for Development Purposes only.

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