Course Title: Keycode Retrieval System (KRS) – Authorization Code Functionality Course Number: KR203 Issue: 1.1 Paper Authorization codes Electronic Authorization codes Numeric Authorization codes

"This session falls under the confidentiality agreement and therefore is subject to non-disclosure" Also note - any specific details shown in the training such as company names or pricing, are examples for training purposes only, and do not represent accurate data. The screen captures shown in the training may vary slightly from the screens in the current version of the tool.

Course Aims & Objectives Understand the difference between Paper Auth Codes and Electronic Auth Codes Understand the benefits of using eAuth Codes Understand the PO History Report Understand how to generate keycodes via eAuth Codes using PO’s Understand how to generate keycodes using Paper or Numeric Auth Codes Understand how to retrieve keycodes generated from Auth Codes The eAuth Code functionality exists within KRS in support of several different products. For each product the eAuth Code functionality is the same. The KRS functionality and screens is similar regardless of which KRS product the user is working with.

Course Chapters Part 1: Authorization Code Overview Paper vs Electronic vs Numeric Auth Codes Auth Codes and Dist of Record eAuth Code Admin Overview eAuth Code Benefits and Process Part 1: Authorization Code Overview Part 2: Generate Keycodes using Numeric or Paper Auth Codes Part 3: Generate Keycodes via eAuth Code using PO‘s

Authorization Overview All registered KRS users have the ability to generate keycodes using the Auth Codes (electronic and/or paper). No Admin access is required! Paper Authorization Codes - are merchandise software licenses purchased via a Purchase Order (with or without Enterprise Configurator (EC)) that is fulfilled by shipment of a paper document KRS is used to access the purchased Auth Code licenses and assign them to a System ID to generate a keycode Electronic Authorization Codes, or eAuth Codes - are merchandise software licenses purchased via a Purchase Order (with or without EC) that is electronically fulfilled by KRS eAuth Codes have no physical components. KRS is used to access the purchased eAuth Code licenses and assign them to a System ID to generate a keycode Distributors use Purchase Orders (PO’s) to Generate Keycodes in KRS Resellers use Numeric Auth Codes (in lieu of PO’s) to generate Keycodes, as they do not have access to their distributors PO’s on KRS Distributors must convert the eAuth Codes to Numeric Auth Codes and provide them to the Resellers

eAuthorization Codes: Paper Authorization Codes: Paper vs. Electronic – Process Differences eAuthorization Codes: Unique Orderable Part #s Not physically shipped to the Partner Stored electronically on KRS Accessed using the Partner PO or Avaya Sales Order # Notification of electronic codes posted and available for a particular PO on KRS: EDI customers via 856 or via email notification as assigned by the eAuth Code Administrator Paper Authorization Codes: Unique Orderable Part #s Sheet of paper listing authorization codes shipped Partner receives receipt of shipment Paper work lost = authorization codes lost (no database stored at Avaya to recover them)

eAuth Code Benefits Reduced time to receive Auth Codes (no shipping, duty, handling) Never lose or misplace authorization codes (true traceability & accountability) Ability to automatically produce keycodes without manually typing in each authorization code (search by PO) Ability to quickly determine available Auth Codes for keycode generation Ability to perform inventory reports Ability to assign a partial or complete PO to a particular system Ability to utilize both Numeric Auth Codes and multiple PO’s for a single keycode transaction for one system Faster Lead times & NO more paper work!!

Auth Codes by product & Distributor of Record All KRS users can generate Keycodes from PO’s and/or with eAuth Codes The user’s company will automatically become the Distributor of Record for the new keycode. eAuth Code Licenses are offered for all products on KRS, except: MPS, MC 3100, CallPilot 100/150/Mini, Norstar CS 1000 - offers eAuth Codes as an option for merchandise ordering only for CS 1000 Rls 5.0 and above (paper Auth Codes not available for CS 1000): All KRS user’s can generate a keycode for a CS 1000 site ID using an eAuth Code (no special access is required). eAuth Codes must be used for license expansions on unsupported system releases (ex. Rls 5.0 and 5.5, as of April 2011) BCM 200/400, BCM50 and BCM450 - option to order paper or eAuth Codes eAuth codes are available to support BCM systems with the Linux OS BCM 50 / BCM 450 – all releases BCM 200/400 – Minimum Rls 4.0 eAuth Codes have different part numbers than their equivalent paper Auth Codes

eAuth Code Process Keycode Retrieval Partner System (KRS) Partners use PO# to access electronic Auth Codes in KRS Resellers use Numeric Auth Codes from their Distributor Both Partners and Resellers provide the SYSTEM ID to generate a new system keycode Partner Keycode Retrieval System (KRS) Partner requires additional S/W Licenses PO is posted & activated on KRS for use On CRD, Email** is sent to Partner indicating the PO is activated*on KRS for use **Email occurs only when the eAuth Code Admin uses Email Notification EDI Partners will also receive 856 Partner places order for eAuth SW licenses Avaya Order Management Purchase Order is processed on CRD* and features are fulfilled to KRS *CRD: Customer Required Date on the PO

eAuth Code Administration E-Auth Code Administrators are critical as they notify users within their company when a PO has become available on KRS for generating keycodes PO History Reports Allows Users & eAuth Code Admins to generate a report which shows license consumption Inventory Reports Allows eAuth Code Admins to generate a report which lists POs in their inventory Return Credit Reports Allows eAuth Code Admins to generate a return credit report which deactivates the Auth Codes purchased on a PO. Report is required as proof of returned eAuth Codes. Manage Email Notification Allows eAuth Code Admins to set up a list of recipients that will receive an Email notification whenever a purchase order is posted (“activated”) on KRS for generating keycode licenses from the purchased eAuth Codes Manage Admin Users Allows the Primary eAuth Code Admin to set up additional secondary administrator user (SAU) access within their company account Numeric Authorization Codes (Distributors only) Allows Distributor eAuth Code Admin to generate numeric authorization codes that can be used by Resellers like paper Auth Codes to generate keycodes Refer to ‘eAuth Code Administration” training for further details

Purchase Order History Report All users have access to Purchase Order History Report Shows eAuth Code licenses ordered and used by PO# Numeric Auth Code Histories by PO# are viewable for users with Distributor privileges Select <Purchase Order History Report> from left menu, under “eAuth Code Management” Enter the PO # and select <Search> Select <Download Report> button to download the report if desired 2. 1. 3.

Details of the PO History Report Sample report in which the PO has not been used – all items are Type = CR = credit LINE NUMBER: Line Number on the PO TYPE: CR = Credit, DB = Debit CATEGORY: Applied to System from PO = Used on a System ID shown in Column G Generate Numeric Auth Code = Feature converted to an Auth Code Reset from Auth Code Kxxxxxxxx = previously used portion was reset by Avaya Support CR – Credited from Original PO Purchase

Generating Keycodes from Auth Codes All regular KRS users have the ability to generate keycodes using Paper or Electronic/Numeric Auth Codes. No Admin access is required! eAuth Codes are accessed using the Purchase Order number used to purchase the s/w licenses The process for Paper Auth Codes and Numeric Auth Codes in KRS are the same eAuth Codes are converted to Numeric Auth Codes by Distributors for use by Resellers Explain defn of terms

Generate Keycode 3. 4. 5. Log-in to KRS – www.avaya.com/ebizn (Americas & Asia) www.avaya .com/ebizu (EMEA) www.avaya.com/krs (Direct - Global) Select “Product Family” For CS 1000 - Select <Generate Keycode> from the left menu For BCM – “Generate Keycode” page will default when BCM Product selected Enter the “System ID” - System Id’s are not case sensitive – no wild card searches Select <Continue>

Generate Keycode … Paper, Numeric, or eAuth Codes Add Numeric Auth Codes and Paper Auth Codes in this section and / or Add eAuth Codes by PO in this section Users can mix and match Auth Codes types A Reseller could add some licenses from Paper Auth Codes and some by Numeric Auth Codes A Partner could add some licenses from Paper Auth Codes and some by eAuth Codes (ie by PO)

Course Chapters Part 1: Authorization Code Overview Part 2: Generate Keycodes using: Numeric Auth Codes – Resellers only Paper Auth Codes Part 3: Generate Keycodes via eAuth Code using PO‘s

Generate Keycode using Numeric Auth Code or Paper Auth Code *** AUTHORIZATION NUMERIC CODES *** =========================================================== CREATED DATE:                                 2011-06-29 10:20:27 ----------------------------------------------------------- PURCHASE ORDER #:      TESTCS1K-03 NORTEL ORDER # (COEO):            TESTCS1K-SO-03 ALTERNATE ORDER #:     TESTCS1K-SAP-03 CUSTOMER:                       Avaya Inc (617101) AUTHCODE         QTY        PEC                        FEATURE PKG    A857129737        2              NTE906HC           1 Enh ACD Agent eAuth License A702996486        3              NTE906FC            1 Enh Basic IP Set eAuth Lic Generate Keycode using Numeric Auth Code or Paper Auth Code 1. Identify Numeric Auth Code as sent by Distributor (or Paper Auth Code) Enter the Numeric or Paper Auth Code Select <Add> to add the Auth Code to the keycode 2. 3.

Generate Keycode using Numeric Auth Code or Paper Auth Code KRS validates that the Auth Code is available for use. The full quantity must be consumed in the keycode (no partial quantities). Use the check box only to <Remove> an Auth Code. Enter more numeric or paper Auth Codes if desired and select the <Add> button. A check is not required to add Auth Codes. Select the <Go to Summary> button when ready to generate the keycode. 1. 2. 3. Note: at this point a PO# could also be entered in the lower section of the screen (Click <Go To PO>). Refer to section 3 of the training for eAuth Code details

Generate Keycode using Numeric Auth Code or Paper Auth Code KRS validates the features selected for applicability on the system ID Once the features are validated, KRS presents a summary of the new keycode contents under “System Profile”, and highlights the changes Select <Generate Keycode> to complete the generation process – the keycode will be displayed on the “Retrieve Keycode” page where it can be viewed and downloaded 1. 2.

Generate Keycode Numeric Auth Code or Paper Auth Code Once KRS obtains the generated keycode, it will be automatically retrieved and displayed for the user on the standard “Retrieve Keycode” page. Use the standard download buttons at the bottom of the page, to download the keycode – refer to CS 1000 or BCM training for more details 1.

Course Chapters Part 1: Authorization Code Overview Part 2: Generate Keycodes Using Numeric or Paper Auth Codes Part 3: Generate Keycodes via eAuth Code using PO‘s

Generate Keycode – enter PO Find the PO by entering one of: Avaya Sales Order# Customer Purchase Order # Alternate/Other Order # (ex. NPSO) PO #’s are not case sensitive Select the <Go to PO> button to display the PO details (as shown on next slide) 1. 2.

Generate Keycode using PO – Select Licenses The PO details are displayed in a table format Enter Quantity desired for each line item in the “Qty Taken” column To apply the entire Purchase Order, select <Add All> Select <Continue> 1. Note: BCM 200/400 will not warn if Qty Taken > Qty Available 3. 2.

Generate Keycode using PO – Accept Licenses KRS confirms the licenses selected from the PO To accept the licenses select the <Continue> button – KRS will return to step 2 to allow licenses to be added from additional PO’s <Cancel> will start over with System ID selection 1. 2.

Licenses added by Paper Auth Codes Licenses added by PO (eAuth) Generate Keycode using PO – Add more POs or <Go To Summary> KRS returns to Step 2 to allow additional licenses to be added to the Keycode, if desired. They may be added by using a Paper Auth Code. Enter the next PO and select <Go to PO> and/or Enter the Paper Auth Code and select <Add> Select the <Go to Summary> button when ready to generate the Keycode – KRS validates the selected licenses for applicability (see next slide) Licenses added by Paper Auth Codes 2. 1. Licenses added by PO (eAuth) 3.

Generate Keycode using PO – Review Summary and Generate Keycode Once the licenses are validated,** KRS presents a summary of the new keycode contents, and highlights the changes ** KRS validates the selected licenses for applicability (ie. service level etc.). No engineering rule validations are done on the system ID. Select <Generate Keycode> to complete the generation process 1. 2.

Generate Keycode using PO – View and Download the Keycode Once KRS obtains the generated keycode, it will be automatically retrieved and displayed for the user on the standard “Retrieve Keycode” page. Use the <Download Envelope> and <Download Keycode> buttons to download the keycode 1.

Thank You