Glossary Definition of common language and terms Definition Description Example  Activation Activation is the process of generating a license file based on an entitlement certificate.   A license can be created for the entitlement lines / products on  the entitlement. A partial activation can be performed. For each activation a fulfillment record will be created. Activation record Is identical to an entitlement line. Consists of a unique id for activation purpose. View on entitlement line from activation perspective. Consolidation License consolidation is the generation of a single license file during the activation process for several or all licenses of an entitlement certificate. A consolidated license file for all licenses of an entitlement certificate is much easier to handle; thus license consolidation is the default. Counted License A counted license is controlled by the license server, so that only the specified licensed quantity can be used at a time. All hardware and software feature licenses are counted licenses. The opposite of a counted license is an uncounted license. Only the licenses of some software tools are uncounted. Demo License Demo licenses are available to equip Advantest hardware equipment that we consign to customers for demonstration purposes.  Demo licenses are also available for customer owned systems, to demonstrate specific system features that are controlled with a license, which the customer hasn’t purchased yet. Demo licenses are always… -term, i.e. time-limited to either 30-days or 12-months - Node-locked , so that they can be used only on one specific system / workstation . Emergency License An emergency license is a short-term license that Advantest provides to support customers who have a license that has not expired, but is not functioning due to network or license server issues.  An emergency license has an expiration period of 10 days .  Entitlement An entitlement represents the customers’ rights to use specific licensed system capabilities. An entitlement acts as a container for the license products purchased in a single purchase order. Consists of an entitlement id, a customer and entitlement lines = license products. Entitlement ID Unique identifier for a specific entitlement. Can be found on the Entitlement Certificate. Required for all sorts of licensing related activities, e.g. for the activation process (e.g. used by customer/CE/AE for logging in to Flexera’s Flexnet Operations Module). Entitlement line Equals a specific license product. Consists of an activation id, a product number, the number of entitled copies (= quantity) and some other items related to the product (e.g. expiration date). Entitlement Certificate Is a document (HTML and/or paper copy) that is unique for each entitlement. Is the legal proof of an entitlement. Is shipped together with the hardware product delivery as paper copy (if applicable), or sent by email for eDeliveries. Contains information about entitlement lines / license products. ERP ERP stands for Enterprise Resource Planning , which is an integrated business management software system. Advantest’s ERP system is Oracle. All Advantest sales orders are booked in Oracle. Orders that include licenses are automatically loaded into the Flexnet Operations Module (FNO), i.e. our License Management System. Expiration Date Is the date after which the respective license or to be exact, the respective fulfillment line will no longer be valid. The expiration date is part of the FlexNet Publisher Authorization Code, i.e. part of the license file for every single fulfillment line. Feature Describes a technical functionality enabled by a license file. Consists of a name (= license string / string name) and a version number, e.g. Protocol_Aware_SOC, Version 1.0. Every feature of a license product has a specific count, i.e. quantity that can be used simultaneously. FlexNet Publisher Authorization Code Is the character string created during the License Activation Process for installation on a computer running a FlexNet Publisher License Server.  A FlexNet Publisher Authorization Code defines a specific range of Software Features or Hardware Feature values, an Expiration Date for the Feature License, and the quantity of such Feature Licenses. Floating A floating license can be shared between all test systems (or workstations) that are connected via the same network. Opposite of a node-locked license. FNO Stands for Flexnet Operations Module. Is our License Management System. All Oracle license orders are loaded into FNO with an automated order load (AOL). In FNO the entitlement certificate is generated before it is sent out to customers. All key transactions through the lifecycle of licenses is done and/or recorded in FNO, e.g. license activation, re-hosting, renewal, return, transfer. Fulfillment record Describes an item that is created on each fulfillment of an activation record. An activation record can be linked to more than one fulfillment record, if a partial activation has occurred. Consists of a fulfillment id, the attributes related to the activation, the license file. License A license allows the use of a specific hardware or software capability. License Model A license model defines licensing characteristics that determine how, when, and where a license product can be used. Defines the commercial attributes of a license (e.g. floating, node locked, 30-days, per-session…). Consists of a name, a description, and a number of commercial license attributes. License Product Describes an item that consists of a set of features. Consists of a product name (= product number), a description, a version number, an associated license model and a set of features and their quantities.   Node-locked  A node-locked license cannot be shared between different test systems (or workstations), but can be used only on a dedicated test system serial-number or on a dedicated workstation MAC-address. Perpetual Perpetual licenses grant use rights that are unlimited in time, however the related license files / activation records need to be renewed annually.  Permanent Permanent licenses grant use rights that are unlimited in time. Different to perpetual licenses, the license files for permanent licenses do not to be renewed on an annual basis. Re-hosting Re-hosting is the process of moving a license from one host / license server to another host . Renewal All perpetual hardware and software feature licenses have to be renewed annually, since the license file (= the fulfillment records) that has been generated during the activation process will expire on January 31st of the respective following year. With each renewal, new fulfillment records will be created. The expiry date of these new fulfillment records will again be the January 31st of the respective following year. The new fulfillment records that are generated during the renewal do not only extend the expiry date, but also update the versions of all licenses that have a new revision. During the annual renewal process, re-hosting of licenses (= move of licenses from host A to host B) is possible. Apart from that, re-hosting is also possible throughout the year following a re-hosting request process (note: fees may apply). The License Renewal Process has to be completed between January 1 and January 31 of every year. Old Fulfillment records cannot be deleted, i.e. they still will be visible in the License Management System. Term License Term licenses grant a use right that is time limited. Typical durations for term licenses are 30-days, 6-months and 12 months. Term licenses expire after the respective entitlement period is over. Trade License Licenses that customers purchase and thus own are trade licenses. Practically all hardware and software feature trade licenses are perpetual and floating. Return A license return involves removing of license rights from a specific entitlement certificate / entitlement line items. License returns of trade licenses are possible only on an exceptional basis, usually only in conjunction with complete V93000 system trade-ins or buy -backs. Uncounted License The opposite of a counted license => see above. The licensed quantity of a certain license product is not controlled (= counted) by a license server, i.e. an unlimited quantity of a licensed feature can be used in parallel. Example for an uncounted license: S&S tools package.