Common use of License Type Description Clause in Contracts

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 derived or produced from use of the Cloud Service may only be deployed, used, copied or stored within a Remote Engine for which a license of the Software has been purchased. Interactive User A user that may search, read, write and delete master data, using the native web user interface in the Software, including participation in workflow processes. 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.