Specific Order Processes and Requirements Sample Clauses

Specific Order Processes and Requirements. 1. Distributor will order Software from SAP using and filling out completely such forms and minimum order requirements as SAP may prescribe from time to time and must comply with any then-current order process for the specific Software product. Where applicable, Distributor agrees to use the electronic means provided by SAP for placing orders. 2. With regard to each Software order for an End User, Distributor must provide SAP with: a) the name and address of the Open Ecosystem Partner who will distribute the Software to the End User; b) the name and address of the End User for whom the Software was ordered; c) details of the Software ordered for the Open Ecosystem Partner, including, without limitation, the product and country version as well as the number of users for each Software product; d) details of any SAP Delivered Support agreement concerning the specific End User; e) Distributor’s contact and billing information; and f) any other data required by SAP in any then-current order process for the specific Software, Maintenance Services or both. 3. Orders and confirmations are binding, non-cancellable, non-revocable and non-transferable once submitted to SAP. All orders are subject to acceptance by SAP. 4. SAP will accept the Software order by the same means or by performing the Software order. 5. SAP reserves the right to decline Software orders if the Software is intended to be used on computers, operating and database management systems that SAP considers to be not suitable for use with the Software.
Sample 1Sample 2Sample 3See All (43)
AutoNDA by SimpleDocs
Specific Order Processes and Requirements. 1. Partner will order Software from SAP using and filling out completely such forms and minimum order requirements as SAP may prescribe from time to time and must comply with any then-current order process for the specific Software product. Where applicable, Partner agrees to use the electronic means provided by SAP for placing orders. 2. With regard to each Software order for an End User, Partner must provide SAP with: a) the name and address of the End User for whom the Software was ordered; b) details of the Software ordered for the End User, including, without limitation, the product and country version as well as the number of users for each Software product; c) details of any SAP Delivered Support agreement concerning the specific End User; d) Partner’s contact and billing information; and e) any other data required by SAP in any then-current order process for the specific Software, Maintenance Services or both. 3. Orders and confirmations are binding, non-cancellable, non-revocable and non-transferable once submitted to SAP. All orders are subject to acceptance by SAP. 4. SAP will accept the Software order by the same means or by performing the Software order. 5. SAP reserves the right to decline Software orders if the Software is intended to be used on computers, operating and database management systems that SAP considers to be not suitable for use with the Software.
Sample 1Sample 2Sample 3See All (29)
Specific Order Processes and Requirements. 1. Partner and SAP will enter into End User specific Order Forms for the Software, covering the license and (where applicable and authorized) Maintenance Services under the VAR Delivered Support Model. To this respect, Partner will send its order for Software and (where applicable and authorized) Maintenance Services from SAP from SAP using and filling out completely such forms and minimum order requirements as SAP may prescribe from time to time and must comply with any then-current order process for the specific Software product. Where applicable, Partner will use the electronic means provided by SAP for placing orders and for executing Order Forms. 2. With regard to each Software order for an End User, Partner must provide SAP with: a) the name and address of the End User for whom the Software was ordered; b) details of the Software ordered for the End User, including, without limitation, the product and country version as well as the number of users for each Software product; c) details of any SAP Delivered Support agreement concerning the specific End User; d) Partner’s contact and billing information; and e) any other data required by SAP in any then-current order process for the specific Software, Maintenance Services or both. 3. SAP is free to accept the order and issue an Order Form offering to Partner. In particular, SAP reserves the right to decline the order if the Software is intended to be used on computers, operating and database management systems that SAP considers to be not suitable for use with the Software.
Sample 1Sample 2Sample 3See All (20)
Specific Order Processes and Requirements. 1. Partner will order Software from HASHCASH using and filling out completely such forms and minimum order requirements as HASHCASH may prescribe from time to time and must comply with any then-current order process for the specific Software product. Where applicable, Partner agrees to use the electronic means provided by XXXXXXXX for placing orders. 2. With regard to each Software order for an End User, Partner must provide HASHCASH with: a) the name and address of the End User for whom the Software was ordered; b) details of the Software ordered for the End User, including, without limitation, the product and country version as well as the number of users for each Software product; c) details of any HASHCASH Delivered Support agreement concerning the specific End User; d) Partner’s contact and billing information; and e) any other data required by HASHCASH in any then-current order process for the specific Software, Maintenance Services or both. 3. Orders and confirmations are binding, non-cancellable, non-revocable and non-transferable once submitted to HASHCASH. All orders are subject to acceptance by XXXXXXXX. 4. HASHCASH will accept the Software order by the same means or by performing the Software order. 5. HASHCASH reserves the right to decline Software orders if the Software is intended to be used on computers, operating and database management systems that HASHCASH considers to be not suitable for use with the Software.
Sample 1
Specific Order Processes and Requirements. 1. Distributor will order Software from HASHCASH using and filling out completely such forms and minimum order requirements as HASHCASH may prescribe from time to time and must comply with any then-current order process for the specific Software product. Where applicable, Distributor agrees to use the electronic means provided by XXXXXXXX for placing orders. 2. With regard to each Software order for an End User, Distributor must provide HASHCASH with: a) the name and address of the Partner who will distribute the Software to the End User; b) the name and address of the End User for whom the Software was ordered; c) details of the Software ordered for the Partner, including, without limitation, the product and country version as well as the number of users for each Software product; d) details of any HASHCASH Delivered Support agreement concerning the specific End User; e) Distributor’s contact and billing information; and f) any other data required by HASHCASH in any then-current order process for the specific Software, Maintenance Services or both. 3. Orders and confirmations are binding, non-cancellable, non-revocable and non-transferable once submitted to HASHCASH. All orders are subject to acceptance by XXXXXXXX. 4. HASHCASH will accept the Software order by the same means or by performing the Software order. 5. HASHCASH reserves the right to decline Software orders if the Software is intended to be used on computers, operating and database management systems that HASHCASH considers to be not suitable for use with the Software.
Sample 1

Related to Specific Order Processes and Requirements

  • DATA ESCROW REQUIREMENTS Registry Operator will engage an independent entity to act as data escrow agent (“Escrow Agent”) for the provision of data escrow services related to the Registry Agreement. The following Technical Specifications set forth in Part A, and Legal Requirements set forth in Part B, will be included in any data escrow agreement between Registry Operator and the Escrow Agent, under which ICANN must be named a third-­‐party beneficiary. In addition to the following requirements, the data escrow agreement may contain other provisions that are not contradictory or intended to subvert the required terms provided below.

  • Customer Requirements Customer will be required to maintain complex passwords for their User accounts where applicable. For any such passwords LightEdge will provide a secure URL that any User can access to change passwords. All User passwords are set to a ninety (90) day password expiration schedule by default. LightEdge is not responsible for unexpected use of Services whether by ex-employees, compromised User passwords or any other misuse of Customer accounts. Customer shall be responsible for all costs incurred by such unexpected use of Service. Customer shall be fully responsible for providing to LightEdge at Customer’s own expense and in a timely manner the following: - All security for its Services and systems used or accessible in connection with Service; - Cooperative testing of all Customer-provided hardware, software, and Services for compatibility with Service; - Designating an Authorized Contact(s) to be the point of contact to interface with LightEdge Technical Support; - All cabling necessary to support Service; and - Physical and remote management access to any and all Servers onto which Service is installed.

  • Specific Requirements compensation insurance with statutory limits required by South Dakota law. Coverage B-Employer’s Liability coverage of not less than $500,000 each accident, $500,000 disease-policy limit, and $500,000 disease-each employee.

  • Software Requirements 7 Developer shall prepare the Project Schedule using Oracle’s Primavera P6.

  • Forecasting Requirements 19.5.1 The Parties shall exchange technical descriptions and forecasts of their Interconnection and traffic requirements in sufficient detail necessary to establish the Interconnections necessary for traffic completion to and from all Customers in their respective designated service areas.

  • Design Requirements The DG Facility shall be installed in compliance with Wisconsin Administrative Code Chapter PSC 119.

  • ORDERING REQUIREMENTS Eligible Purchasers shall order Goods and/or Services from this Contract, consistent with the terms hereof and by using any ordering mechanism agreeable both to Contractor and Purchaser but including, at a minimum, a purchase order. When practicable, Contractor and Purchaser also shall use telephone orders, email orders, web- based orders, and similar procurement methods (collectively “Purchaser Order”). All Purchase Orders must reference the Contract number. The terms of this Contract shall apply to any Purchase Order and, in the event of any conflict, the terms of this Contract shall prevail. Notwithstanding any provision to the contrary, in no event shall any ‘click-agreement,’ software or web-based application terms and conditions, or any other agreement modify the terms and conditions of this Contract.

  • Technical Requirements 4.5.3.1 Tandem Switching shall have the same capabilities or equivalent capabilities as those described in Telcordia TR-TSY-000540 Issue 2R2, Tandem Supplement, June 1, 1990. The requirements for Tandem Switching include but are not limited to the following: 4.5.3.1.1 Tandem Switching shall provide signaling to establish a tandem connection; 4.5.3.1.2 Tandem Switching will provide screening as jointly agreed to by <<customer_short_name>> and BellSouth; 4.5.3.1.3 Where applicable, Tandem Switching shall provide AIN triggers supporting AIN features where such routing is not available from the originating end office switch, to the extent such Tandem switch has such capability; 4.5.3.1.4 Where applicable, Tandem Switching shall provide access to Toll Free number database; 4.5.3.1.5 Tandem Switching shall provide connectivity to Public Safety Answering Point (PSAP)s where 911 solutions are deployed and the tandem is used for 911; and 4.5.3.1.6 Where appropriate, Tandem Switching shall provide connectivity for the purpose of routing transit traffic to and from other carriers. 4.5.3.2 BellSouth may perform testing and fault isolation on the underlying switch that is providing Tandem Switching. Such testing shall be testing routinely performed by BellSouth. The results and reports of the testing shall be made available to <<customer_short_name>>. 4.5.3.3 BellSouth shall control congestion points and network abnormalities. All traffic will be restricted in a non-discriminatory manner. 4.5.3.4 Tandem Switching shall process originating toll free traffic received from <<customer_short_name>>’s local switch. 4.5.3.5 In support of AIN triggers and features, Tandem Switching shall provide SSP capabilities when these capabilities are not available from the Local Switching Network Element to the extent such Tandem Switch has such capability.

  • Purchase Order Requirements Customers shall use a Request for Quote per section 287.056(2), Florida Statutes, when making purchases off of this State Term Contract. Customers shall issue Request for Quotes to at least 25 vendors approved to provide IT Staff Augmentation services in accordance with section 287.0591(5), Florida Statutes. Customers shall order services from the Request for Quote via a Purchase Order with the Customers’ selected Contractor. The terms of the Purchase Order shall not conflict with the terms and conditions established by this Contract. In accepting a Purchase Order, the Contractor recognizes its responsibility for all tasks and deliverables contained therein, warrants that it has fully informed itself of all relevant factors affecting accomplishment of the tasks and deliverables and agrees to be fully accountable for the performance thereof.

  • License Requirements The Hotel’s alcoholic beverage license requires that the Hotel shall: (i) request proper identification (photo ID) of any person of questionable age and refuse alcoholic beverage service if the person is either under age or proper identification cannot be produced, and (ii) refuse alcoholic beverage service to any person who, in the Hotel’s judgment, appears to be intoxicated; and (iii) instruct its personnel to avoid encouraging patrons to consume alcoholic beverages (commonly referred to as “over-pouring”).

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