Per Device Subscription Basis Sample Clauses

Per Device Subscription Basis. In consideration of payment in full of the monthly subscription fee (the “Subscription Fee”) for use of the Product, and subject to all the terms and conditions hereof, You will scan a patient’s driver’s license or insurance card by using the Product. And the Product will extract the information from these identification documents and send the information to Greenway’s PrimeSuite EHR software. Licensor hereby grants to You the right to access and use the Product only from Your desktop or laptop computer during the corresponding subscription period, as well as related materials such as documentation to the extent then available, all made available to You in conjunction with and under the terms and conditions of this Agreement.
AutoNDA by SimpleDocs

Related to Per Device Subscription Basis

  • Software Subscription Lifecycle During the life cycle of Red Hat Software, the scope of Software Maintenance and Support evolves and, after a number of years, we discontinue Software Maintenance and Support for older versions of Software. The details of the Software Maintenance and Production Support life cycle are set forth at xxxxx://xxxxxx.xxxxxx.xxx/support/policy/update_policies.html. If available, you may purchase Extended Update Support and/or Extended Life Cycle Support, as described in Exhibit 1.G, to extend your Subscription Services for certain versions of Software.

  • Software Subscription Use Case Red Hat Storage Server for On- Premise Red Hat Storage Server for On-Premise is intended to be used as a storage system and will be supported only when used as a storage node. Red Hat Storage Server is not supported on non- server hardware such as desktops or workstations. Red Hat Storage Server for On-Premise is intended for use on a dedicated System, Physical Node, Virtual Node or Virtual Guest; running other applications and/or programs of any type on the System, Physical Node, Virtual Node or Virtual Guest can have a negative impact on the function and/or performance of the Red Hat Storage Server and is not a supported Use Case. Each Red Hat Storage Server Subscription includes one Software Subscription to Red Hat Enterprise Linux Server and the Scalable File System Add-on, which are supported solely in connection with the use of Red Hat Storage Server. Red Hat Storage Server for Public Cloud Red Hat Storage Server for Public Cloud is intended to be used as a storage system and will be supported only when used as a storage node. When running in Amazon Web Services, an EC2 M1 Large dedicated instance is required in order to be supported. Running other applications and/or programs of any type on the same instance can have a negative impact on the function and/or performance of the Red Hat Storage Server and is not a supported Use Case. Each Red Hat Storage Server Subscription includes one Software Subscription to Red Hat Enterprise Linux Server and the Scalable File System Add-on, which are supported solely in connection with the use of Red Hat Storage Server. Red Hat Storage for Red Hat Enterprise Linux OpenStack Platform Red Hat Storage Server for Red Hat Enterprise Linux OpenStack Platform is intended to be used as a storage system with Red Hat Enterprise Linux OpenStack Platform and will be supported only when used as a storage node. Red Hat Storage Server is not supported on non-server hardware such as desktops or workstations. Red Hat Storage Server for Red Hat Enterprise Linux OpenStack Platform is intended for use on a dedicated Physical Node; running other applications and/or programs of any type on the Physical Node can have a negative impact on the function and/or performance of the Red Hat Storage Server and is not a supported Use Case. Each Red Hat Storage Server Subscription includes one Software Subscription to Red Hat Enterprise Linux Server and the Scalable File System Add-on, which are supported solely in connection with the use of Red Hat Storage Server.

  • Software Subscription The Term of any Software Subscription shall automatically renew for an additional Subscription License Term unless written notice of termination is given to the other Party three (3) months prior to the expiration of the then-current Term.

  • User Subscriptions Unless otherwise specified in the applicable Order Form, (i) Services are purchased as User subscriptions and may be accessed by no more than the specified number of Users, (ii) additional User subscriptions may be added during the subscription term at the same pricing as that for the pre-existing subscriptions, prorated for the remainder of the subscription term in effect at the time the additional User subscriptions are added, and (iii) the added User subscriptions shall terminate on the same date as the pre-existing subscriptions. User subscriptions are for designated Users and cannot be shared or used by more than one User but may be reassigned to new Users replacing former Users who no longer require ongoing use of the Services.

  • ADDITIONAL USER SUBSCRIPTIONS 3.1 Subject to clause 3.2 and clause 3.3, the Customer may, from time to time during any Subscription Term, purchase additional User Subscriptions in excess of the number set out in paragraph 1 of Schedule 1 and the Supplier shall grant access to the Services and the Documentation to such additional Authorised Users in accordance with the provisions of this agreement.

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

  • Subscription Service PROS warrants that during the Subscription Term, the Subscription Service will conform in all material respects to the functional specifications set forth in the Documentation. Customer's sole and exclusive remedy will be the deployment of a corrected version of the PROS software application that is the object of the Subscription Service, or provision of a workaround, provided however if PROS fails to provide such remedy after using commercially reasonable efforts, Customer may exercise its rights herein for breach of contract, including, but not limited to, termination pursuant to Section 10.2.

  • Purchase Order Duration Purchase orders issued pursuant to this State Term Contract must be received by the Contractor no later than close of business on the last day of the Contract’s term to be considered timely. The Contractor is obliged to fill those orders in accordance with the Contract’s terms and conditions. Purchase orders received by the Contractor after close of business on the last day of the State Term Contract’s term shall be considered void. Purchase orders for a one-time performance of contractual services shall be valid through the performance by the Contractor, and all terms and conditions of the State Term Contract shall apply to the single delivery/performance, and shall survive the termination of the Contract. Contractors are required to accept purchase orders specifying delivery schedules exceeding the contracted schedule even when such extended delivery will occur after expiration of the State Term Contract. For example, if a state term contract calls for delivery 30 days after receipt of order (ARO), and an order specifies delivery will occur both in excess of 30 days ARO and after expiration of the state term contract, the Contractor will accept the order. However, if the Contractor expressly and in writing notifies the ordering office within ten (10) calendar days of receipt of the purchase order that Contractor will not accept the extended delivery terms beyond the expiration of the state term contract, then the purchase order will either be amended in writing by the ordering entity within ten (10) calendar days of receipt of the contractor’s notice to reflect the state term contract delivery schedule, or it shall be considered withdrawn. The duration of purchase orders for recurring deliveries of commodities or performance of services shall not exceed the expiration of the State Term Contract by more than twelve months. However, if an extended pricing plan offered in the State Term Contract is selected by the Customer, the Contract terms on pricing plans shall govern the maximum duration of purchase orders reflecting such pricing plans. Timely purchase orders shall be valid through their specified term and performance by the Contractor, and all terms and conditions of the State Term Contract shall apply to the recurring delivery/performance as provided herein, and shall survive the termination of the Contract. Ordering offices shall not renew a purchase order issued pursuant to a State Term Contract if the underlying contract expires prior to the effective date of the renewal.

  • Management Subscriptions Table 1.6 below lists the Management Subscriptions offered by Red Hat and the Unit description that is used to measure your use of the Management Subscription(s). The End User License Agreement that governs your use of the Software is located at xxx.xxxxxx.xxx/xxxxxxxx/XXXXx. The Exhibits listed in Table 1.6 contain additional information concerning the scope of the Management Subscriptions and how Red Hat provides Subscription Services to you.

  • Subscription Terms Contractor grants to a Purchasing Entity a license to: (i) access and use the Service for its business purposes; (ii) for IaaS, use underlying software as embodied or used in the Service; and (iii) view, copy, upload and download (where applicable), and use Contractor’s documentation. No Contractor terms, including standard click through license or website terms or use of privacy policy, shall apply to Purchasing Entities unless such terms are included in this Master Agreement.

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