License Type Description Sample Clauses

License Type Description. Admin User A specific individual identified by a valid e-mail address who has received a unique user name and password to access the Subscription Services and who may only use the following capabilities of 1) for Cloud Admin Users, the Talend Management Console: user management, user group management, roles management, subscriptions, engine management, operations and monitoring, scheduling, and environment management for administration purposes, 2) for Software Admin Users, the Talend Administration Center (TAC): user management, user group management, licensing, server management, Job and ESB conductors, log server, and Activity Monitor Console for administration purposes. API The main unit of work provisioned in Talend API Designer and Talend API Tester applications. Talend API Designer refers to this unit of work as an “API”, an “API definition” or an “API contract”. Talend API Tester’s unit of work is also called a “project”, a “test project” or an "API test project”. Copies of existing APIs are counted towards the total usage. Cloud Engine A runtime (either production or non-production) Node capable of executing Customer workloads through the Cloud Service. Concurrent Admin User A specific individual identified by a valid e-mail address who is logged on at any given point in time to a single Repository who (a) may use any of the capabilities of the Cloud or Software version of Talend Data Catalog or (b) may only use the following capabilities of the TAC: user management, user group management, licensing, server management, Job and ESB conductors, log server, and AMC for administration purposes. Concurrent Consumer User A specific individual identified by a valid e-mail address who is logged on at any given point in time to a single Repository who may only use the capabilities granted by the “Consumer User” role in the Cloud or Software version of Talend Data Catalog. Concurrent User A specific individual identified by a valid e-mail address who is logged on at any given point in time to a single Repository. Engine Token The unit of measure assigned to Customer’s ability to configure and run either a Cloud Engine or a Remote Engine instance. Each instance will require a fixed amount of Engine Tokens to run, as specified in the Order Form. Customer may redeem their Engine Tokens towards any combination of Cloud or Remote Engine instances, so long as Customer does not exceed the total number of Engine Tokens purchased. Any Microservices Generated Code de...
Sample 1Sample 2Sample 3See All (4)
AutoNDA by SimpleDocs
License Type Description. Licensed Users The number of Authorized Users who may access the Learning Services shall be: (1) The quantity set forth on the Order Form; (2) Equivalent to the sum of (a) the number of Named Users, (b) the number of Talend Data Catalog Concurrent Consumer Users, (c) two (2) times the number of Talend Data Catalog Concurrent Admin Users, and (d) ten (10) times the number of all Concurrent Users excluding Talend Data Catalog Concurrent Users; or (3) Unlimited, provided that Customer has purchased a Learning Services subscription applicable to all Software and Cloud users and Customer’s annual fees for all Subscription Services exceeds $200,000 (USD). Named User A specific individual identified by a valid e-mail address who can access the Cloud Service or Software regardless of whether the individual is actively logged into a Cloud Service data center or a Talend Administration Center, as applicable, at any point in time. Non-Production Runtime Non-Production Server Customer may use the Software for any non-production purpose, including as part of a Warm Backup, in a development environment for proof of concept, quality-assurance, or other testing purposes (“Non- Production Runtime” or “Non-Production Server”). Per Node Limitation Customer may use the Software for up to the total number of Nodes specified in an Order Form. Per Core Limitation Customer may use the Software for up to the total number of Physical Cores, Virtual Cores, or Container Cores specified in an Order Form, based on Customer’s use within (i) a Physical Machine, (ii) a Virtual Machine, or (iii) a Software Container. Customer may not split a single license between a Physical Machine and a Virtual Machine or Software Container. Customer may split a single license across multiple Virtual Machines or Software Containers, so long as Customer does not exceed the Per Core Limitation for each license. Any Microservices Generated Code derived or produced from the Software that is licensed under a Per Core Limitation may only be deployed, used, copied or stored within a Virtual Machine, Physical Machine or Software Container for which a license of the Software has been purchased, subject to the limitations set forth above.
Sample 1
License Type Description. Named User A specific individual identified by a valid e-mail address who can access the Cloud Service or Software regardless of whether the individual is actively logged into a Cloud Service data center or a Talend Administration Center, as applicable, at any point in time. Non-Production Runtime Non-Production Server Customer may use the Software for any non-production purpose, including as part of a Warm Backup, in a development environment for proof of concept, quality-assurance, or other testing purposes (“Non- Production Runtime” or “Non-Production Server”). Per Node Limitation Customer may use the Software for up to the total number of Nodes specified in an Order Form. Per Core Limitation Customer may use the Software for up to the total number of Physical Cores, Virtual Cores, or Container Cores specified in an Order Form, based on Customer’s use within (i) a Physical Machine, (ii) a Virtual Machine, or (iii) a Software Container. Customer may not split a single license between a Physical Machine and a Virtual Machine or Software Container. Customer may split a single license across multiple Virtual Machines or Software Containers, so long as Customer does not exceed the Per Core Limitation for each license. Any Microservices Generated Code derived or produced from the Software that is licensed under a Per Core Limitation may only be deployed, used, copied or stored within a Virtual Machine, Physical Machine or Software Container for which a license of the Software has been purchased, subject to the limitations set forth above.
Sample 1

Related to License Type Description

  • SERVICE LEVEL DESCRIPTION The Fund Accounting Agreement is hereby amended by deleting the Service Level Description attached thereto and replacing it in its entirety with the Service Level Description attached hereto.

  • License Type Your license to a Product will be under a Named User or CPU license type, as specified on an order. Each Named User license to a Product entitles a Named User to access and use that Product in one production environment and up to two non-production environments. Each CPU license to a Product entitles you to assign the Product to a single CPU in one production environment and up to two non-production environments, for use in support of an unspecified number of Named Users.

  • Service Description 2.1 General

  • Task Description This task includes activities associated with permit-required monitoring conducted in accordance with the conditions specified by state or federal regulatory agencies. All monitoring tasks must be located within or adjacent to the Project area and follow the Department’s Regional Coastal Monitoring Program and FWC's marine turtle and shorebird monitoring programs. Guidance for monitoring of nearshore resources is available in the Department's Standard Operation Procedures For Nearshore Hardbottom Monitoring Of Beach Nourishment Projects. The Local Sponsor must submit work products directly to the appropriate state or federal regulatory agencies in accordance with permit conditions to be eligible for reimbursement under this task, unless otherwise directed.

  • Service Descriptions Credit Card processing services: Global Direct’s actions to the appropriate card associations and/or issuers (e.g., Visa, MasterCard, Diners, Discover); settlement; dispute resolution with cardholders’ banks; and transaction-related reporting, statements and products. Debit/ATM Processing Services: Global Direct has connected to the following debit card networks (“Networks”): Accel, AFFN, Interlink, MAC, Maestro, NYCE, Pulse, Star, and Tyme. Global Direct will provide Merchant with the ability to access the Networks that Global Direct has connected to for the purpose of authorizing debit card transactions at the point of sale from cards issued by the members of the respective Networks. Global Direct will provide connection to such Networks, terminal applications, settlement and reporting activities. EBT Transaction Processing Services: Global Direct offers electronic interfaces to Electronic Benefits Transfer (“EBT”) networks for the processing of cash payments or credits to or for the benefit of benefit recipients (“Recipients”). Global Direct will provide settlement and switching services for various Point of Sale transactions initiated through Merchant for the authorization of the issuance of the United States Department of Agriculture, Food and Nutrition Services (“FNS”) food stamp benefits (“FS Benefits”) and/or government delivered cash assistance benefits (“Cash Benefits, ”with FS Benefits, “Benefits”) to Recipients through the use of a state-issued card (“EBT Card”). With respect to Visa and MasterCard products, Merchant agrees to pay and Merchant's account(s) will be charged pursuant to Section 5 of this Agreement for any additional fees incurred as a result of Merchant's subsequent acceptance of transactions with any Visa or MasterCard product that it has not elected to accept.

  • System Description The wet detention basin is designed to trap 80% of sediment in runoff and maintain pre-development downstream peak flows. The basin has two forebays (smaller ponds) located at the low end of two grass xxxxxx. In addition to runoff conveyance, the grass xxxxxx also allow infiltration and filtering of pollutants, especially from smaller storms. The forebays are each 4 feet deep. They are connected to the main pool by 18 and 24-inch metal pipes that outlet onto a rock chute. The forebays will trap coarse sediments in runoff, such as road sands, thus reducing maintenance of the main basin. The main pool will trap the finer suspended sediment. To do this, the pond size, water level and outlet structures must be maintained as specified in this Agreement (see Figures 1, 2 and 3). The main basin receives runoff from a 67.1 acre drainage area (41.2 acres within the subdivision and 25.9 acres off-site drainage coming from the east). During high rainfall or snow melt events, the water level will temporarily rise and slowly drain down to the elevation of the control structure. The water level is controlled by a 12-inch concrete pipe extending through the berm in the northwest corner of the basin (see Figures 1 and 3). On the face of the 12-inch pipe, there is metal plate with a 3-inch drilled hole (orifice) with stone in front of it. This orifice controls the water level and causes the pond to temporarily rise during runoff events. Washed stone (1- 2” diameter) is placed in front of the orifice to prevent clogging. High flows may enter the grated concrete riser or flow over the rock lined emergency spillway. “As-built” construction drawings of the basin, showing actual dimensions, elevations, outlet structures, etc. will be recorded as an addendum(s) to this agreement within 60 days after [Municipality Name] accepts verification of construction from the project engineer.

  • Project Description In two or three brief sentences, provide a concise description of your exhibition. Include the subject matter, type of objects to be included (paintings, sculpture, manuscripts, etc.), those responsible for organizing the exhibition, and catalogue author(s).

  • Work Description T-804 Opening Roads - Removal of closure devices, cleaning ditches, removing berms, and blading the traveled-way T-811 Closing Roads - Entrance treatment for 150' cross-rip; debris block (slash, earth, berm, rocks, etc.) + seed + water bar T-811 Closing Roads - Water bar frequency per BMPs for remainder of road T-811 Closing Roads - Engineering Rep. or Construction Inspector must be notified prior to performing closeout ple S am 76P Single Lane / Level 1 76 0.00 Ending 0.30

  • Product Description The lead products covered by this Settlement Agreement is limited to following Amazon Identification Number (ASIN) B07Y35S3M9, with the description, "DEVMO 63/37 Tin Lead Rosin Core Flux 0.8mm Diameter Soldering Solder Wire 100g Reel," which was offered for sale by the Settling Entity on xxxxxx.xxx, hereinafter the “Product” or “Products.”

  • License Types (a) A Team License shall mean a subscription license that provides a limited number of licenses to a set amount of developers for a named Customer. Customer must procure enough active licenses for each individual who has Programmatic Access. A Team License only grants rights to a named Customer and does not extend any right, in any form, to any parent or subsidiary company of Customer. A Team License cannot be used as a floating license. (b) A Project License shall mean a subscription license which covers one named Customer application. The license fees are based on the total number of developers working on a named project, regardless of whether such developers are directly using the Licensed Product. For the purposes of pricing and license administration, a “Project Group” is deemed to be a distinct Customer software team within a Customer’s business unit that works towards a distinct business purpose for the benefit of a single application. Customer is required to identify the name of each such Project Group to Syncfusion; such name must be unambiguous in nature. It is acknowledged and agreed by Customer that each identified Project Group shall exist for a valid business purpose and not just as a means for consolidating software licenses to minimize license fees that are otherwise due. If, in the sole opinion of Syncfusion, multiple Customer teams would each individually meet the above definition of a Project Group, such multiple teams shall not be combined for the purpose of consolidating licenses under a single Project Group. Customer is responsible for providing information about each such Project Group to Syncfusion. By entering into this Agreement, Customer represents that after the effective date, it will not withhold information that Syncfusion requires to properly license each such Project Group, and further agrees that any misrepresentation in this regard constitutes a material breach of this Agreement. (c) A Division License shall mean a subscription license which will cover one named Division and allow for development work on more than one project within such Division. A Division shall mean a business unit within Customer’s organization that works towards a distinct business purpose. Customer is required to identify the name of such Division to Syncfusion; such name must be unambiguous in nature. License fee determinations will be at the sole discretion of Syncfusion and be based on such factors including, but not limited to, Customer’s Division size, developer count, and the scope of the Division’s business purpose. By entering into this Agreement, Customer acknowledges that it is responsible for providing information about the named Customer Division to Syncfusion sufficient for Syncfusion to price the Division License, and Customer represents that it will not withhold information that Syncfusion requires to properly license each such named Customer division, and further agrees that any misrepresentation in this regard constitutes a material breach of this Agreement. (d) A Global License shall mean a subscription license for all development for a named Customer, where the license fees are based on the overall size of a named Customer. A Global License only grants rights to a named Customer and does not extend any right, in any form, to any parent or subsidiary company of Customer. (e) A Retail License shall mean a single named user, non-transferable license to use the Licensed Product. Retail Licenses will only made available to Customers in Syncfusion’s sole discretion and only when the number of such End-Users is finite and readily ascertainable. Accordingly, Syncfusion will make a determination as to whether or not the provision of Retail Licenses is appropriate under the circumstances applicable to any given Customer, and Syncfusion reserves the right, in its sole discretion, to refuse to make available Retail Licenses to a Customer and instead require a given Customer to procure a Project License, Division License, or Global License as circumstances dictate. A Retail License only grants rights to a named Customer and does not extend any right, in any form, to any parent or subsidiary company of Customer.

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