Implementation Approach – Infor Deployment Method Sample Clauses

Implementation Approach – Infor Deployment Method. Infor Deployment Method will be used as the overall governing methodology for all Project related work for the Licensee Project activities associated with implementing the scope described herein. It defines what is to be delivered during the Project, which party is responsible for that work, and how the work is to be performed.
AutoNDA by SimpleDocs

Related to Implementation Approach – Infor Deployment Method

  • Deployment Method You may only install the Products on servers and workstations under the control of your third-party service provider who hosts the Products on your behalf in a public cloud, and will deploy the Products only in the operating environment specified on the order. If the “Cloud Platform for AWS” operating environment is specified on the order, you may deploy the Products listed on the order solely in an Amazon Web Services environment, except for any Products which technically require deployment in a different operating environment. If the “Cloud Platform for Azure” operating environment is specified on the order, you may deploy the Products listed on the order solely in a Microsoft Azure environment, except for any Products which technically require deployment in a different operating environment. 4. 部署方式。您只能在代表您于公共云中托管产品的第三方服务提供商控制的服务器或工作站上安装产品,并且您将只在订单指定的操作环境中部署产品。如果订单上指定了“Cloud Platform for AWS”操作环境,您仅可以在Amazon Web Services 环境中部署订单上所列之产品,因技术要求必须被部署在其他操作环境中的产品除外。 如果订单上指定了“Cloud Platform for Azure”操作环境,则您仅可以在 Microsoft Azure 环境中部署订单上所列之产品,因技术要求必须被部署在其他操作环境中的产品除外。

  • Terminating Switched Access Detail Usage Data A category 1101XX record as defined in the EMI Telcordia Practice BR-010-200- 010.

  • Implementation Program 1. The Borrower shall:

  • Originating Switched Access Detail Usage Data A category 1101XX record as defined in the EMI Telcordia Practice BR-010-200- 010.

  • Procurement Method (a) Quality-Based Selection (b) Selection under a Fixed Budget

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

  • Purchase Order Flip via Ariba Network (AN) The online process allows suppliers to submit invoices via the AN for catalog and non- catalog goods and services. Contractors have the ability to create an invoice directly from their Inbox in their AN account by simply “flipping” the purchase order into an invoice. This option does not require any special software or technical capabilities. For the purposes of this section, the Contractor warrants and represents that it is authorized and empowered to and hereby grants the State and the third-party provider of MFMP the right and license to use, reproduce, transmit, distribute, and publicly display within the system the information outlined above. In addition, the Contractor warrants and represents that it is authorized and empowered to and hereby grants the State and the third-party provider the right and license to reproduce and display within the system the Contractor’s trademarks, system marks, logos, trade dress, or other branding designation that identifies the products made available by the Contractor under the Contract.

  • Joint Network Implementation and Grooming Process Upon request of either Party, the Parties shall jointly develop an implementation and grooming process (the “Joint Grooming Process” or “Joint Process”) which may define and detail, inter alia:

  • ODUF Control Data 6.5.1 Image Access will send one confirmation record per pack that is received from BellSouth. This confirmation record will indicate Image Access’s receipt of the pack and the acceptance or rejection of the pack. Pack Status Code(s) will be populated using standard ATIS EMI error codes for packs that were rejected by Image Access for reasons stated in the above section.

  • Specification and Service Levels The Specification sets out the Services that the Contractor has undertaken to provide. The Specification includes Service Levels setting out particular levels of service that the Contractor has undertaken to meet.

Time is Money Join Law Insider Premium to draft better contracts faster.