frd x el_arate_ea_researchtool

Information Technology

Functional Requirements Document

xELArate EA Research Tool

Revision #: 1.0

Last Revised: Sep-18-2013

PPM #: 113327 PPM Link: http://ppmprod-app1.vmware.com:8080/itg/project/ViewProject.do?projectId=63926

Requested By: WW Customer Operations

Author: Ajith Kethireddy

http://ppmprod-app1.vmware.com:8080/itg/project/ViewProject.do?projectId=63926

http://ppmprod-app1.vmware.com:8080/itg/project/ViewProject.do?projectId=63926

Error! Unknown document property name.Error! Unknown document property name.Error!

Unknown document property name.xELArate Release 1 of 69

Functional Requirement Document

VMware CONFIDENTIAL

Table of Contents

Table of Contents ......................................................................................... 2

1. EXECUTIVE SUMMARY ........................................................................ 4

2. GOALS & OBJECTIVES ........................................................................ 4

3. SCOPE ................................................................................................ 4

4. PROPOSED SYSTEM SUMMARY ........................................................... 6

4.1 Business Requirements.................................................................... 6

4.2 Post November Requirements .......................................................... 6

4.3 Out of scope Requirements .............................................................. 7

4.4 Assumptions and Constraints ........................................................... 8

4.5 Risks ............................................................................................. 8

5. SOLUTION DESIGN ........................................................................... 10

5.1 To-Be High Level Flow ................................................................... 10

5.2 E2E Rule Execution and Result Categorization .................................. 17

5.2.1 E2E Rule Execution ....................................................................... 17

5.2.2 Result Categorization .................................................................... 18

5.3 Display and Manage Research Results ............................................. 20

5.4 Rules .......................................................................................... 28

5.4.1 Eligibility ..................................................................................... 28 5.4.1.1 To-Be Flow ......................................................................................................28 5.4.1.2 Steps .................................................................................................................28

5.4.2 Saved EA ..................................................................................... 29 5.4.2.1 To-Be Flow ......................................................................................................29 5.4.2.2 Steps .................................................................................................................29

5.4.3 Orders ......................................................................................... 31 5.4.3.1 To-Be Flow ......................................................................................................31 5.4.3.2 Steps .................................................................................................................31

5.4.4 DUNs .......................................................................................... 34 5.4.4.1 To-Be Flow ......................................................................................................34 5.4.4.2 Steps .................................................................................................................35

5.4.5 Cases .......................................................................................... 35 5.4.5.1 To-Be Flow ......................................................................................................35 5.4.5.2 Steps .................................................................................................................36

5.4.6 Quotes ........................................................................................ 37 5.4.6.1 To-Be Flow ......................................................................................................37 5.4.6.2 Steps .................................................................................................................37

5.4.7 Contacts ...................................................................................... 39

Error! Unknown document property name.Error! Unknown document property name.Error!

Unknown document property name.xELArate Release 1 of 69


VMware CONFIDENTIAL

5.4.7.1 To-Be Flow ......................................................................................................39 5.4.7.2 Steps .................................................................................................................39

5.4.8 Addresses .................................................................................... 41 5.4.8.1 To-Be Flow ......................................................................................................41 5.4.8.2 Steps .................................................................................................................41

5.4.9 Email Domain ............................................................................... 42 5.4.9.1 To-Be Flow ......................................................................................................42 5.4.9.2 Steps .................................................................................................................42

5.4.10 Company Master........................................................................... 44 5.4.10.1 To-Be Flow ......................................................................................................44 5.4.10.2 Steps .................................................................................................................44

5.4.11 Normalized Name ......................................................................... 46 5.4.11.1 To-Be Flow ......................................................................................................46 5.4.11.2 Steps .................................................................................................................46

5.5 Retrieve and Manage Saved EA Relationships ................................... 47

Wireframe-IB-ELA-14 ................................................................................ 47

............................................................................................................... 49

Wireframe-IB-ELA-15 ................................................................................ 49

Wireframe-IB-ELA-16 ................................................................................ 50

Wireframe-IB-ELA-17 ................................................................................ 53

5.6 Application configuration ............................................................... 55

5.6.1 Setup Rules ................................................................................. 55

Wireframe-IB-ELA-18 ................................................................................ 55

5.6.2 Setup Profiles ............................................................................... 58

Wireframe-IB-ELA-19 ................................................................................ 58

5.6.3 User Preferences .......................................................................... 59

Wireframe-IB-ELA-20 ................................................................................ 59

5.7 Tracking & Omniture Requirements ................................................. 60

5.8 System Diagrams & Architecture .................................................... 61

5.9 Business Intelligence (BI) & Reporting Requirements (optional) .......... 64

Appendix B: Document Change History ...................................................... 65

Appendix C: Open and Closed Issues.......................................................... 65

Appendix D: Glossary/ Definitions ............................................................. 67

Appendix E: Related Documents/References ............................................. 67

Appendix F: Project Team .......................................................................... 67

Appendix G: Review and Sign-off ............................................................... 69

Error! Unknown document property name.Error! Unknown document property name.Error! Unknown document

property name.xELArate – EA Research Tool of 69


VMware CONFIDENTIAL

1. EXECUTIVE SUMMARY

The EA research tool’s purpose is to assist users in determining which EA’s belong to a ‘customer’.

Multiple VMware teams, partners, and large customers routinely expend effort to research which EA’s belong to a given customer.

Today, several internal/externally facing EA lookup tools exist, but they all require users to enter imprecise search criteria (name or email domain) and then use their knowledge of VMware data and business rules to try and interpret the customer EA relationships.

This has proven to be, at best, inefficient; and at worst inaccurate and error prone. In the IB ELA project (which is sponsoring this tool), almost 20% of the IB ELA quotes undergo revisions due to inaccurate list of EA’s supplied for the IB pull. In addition, teams such as GSS licensing routinely spend multiple hours assisting the field with EA research on quotes where the customer is questioning the IB listed on the quote.

2. GOALS &OBJECTIVES

The EA research tool will be designed to emulate much of the expertise that a VMware expert would employ to determine an accurate customer EA list. The end result will be that VMware teams involved with manual EA research and eventually Partners and Customers will have a tool that will significantly optimize this effort.

The new EA Research tool will:

1) Automatically research VMware data sources to gather a list of potential EA’s associated to the ‘customer’.

2) Automatically evaluate and prioritize those EA’s to rank the EA’s which are most likely associated to the customer. Also allow the user to adjust those EA’s based on customer interaction.

3) Save the results for future use, so that subsequent EA research needs for that customer will be minimized.

3. SCOPE

Description Comment

In Scope

EA research tool (launch-able from VMStar, BI

Dashboard, Admin Portal as well as standalone)

to produce a prioritized list of EA’s associated to

that VMStar account/that EA.

Integration of VMStar, MyVMware, and Oracle

and other data sources to be used in the

research.

One tool searches all data sources

Integration with the new customer master EA Research tool will leverage the EA




VMware CONFIDENTIAL

system. relationships stored in that system.

Functionality to save/manage EA relationships to

support future transactions.

Allow different business functions to manage

their EA/customer relationships (Support, Sales,

Partner, or VMware corporate, each may have a

different view of the EA to account relationship.)

Ability to select EA’s to launch the new one-click

view (Quotable Assets View) to display all

products that are quotable along with their

details

Out of Scope – 1st release (November)

EA data cleanup Data errors, EA merge/split tools, and EA

governance will not be impacted by this project.

Feedback to Customer Master on changes to

customer hierarchy based on saved EA

relationships.

This is an important activity, but will need to be a

process created under a separate initiative.

Partner, customer implementations The tool will be designed to anticipate

customer/partner usage, but this will not be

implemented in phase 1.




VMware CONFIDENTIAL

4. PROPOSED SYSTEM SUMMARY

4.1 Business Requirements

Link to BRD

:https://vmshare.vmware.com/it/pmo/Tier%201%20Project/IB%20ELA/Shared%20Documents/1.%20SD

LC%20Documents%20-%20Release%201/1.%20Define/BRDs/IBELA_BRD-EA_ResearchTool_v1.2.docx

Note : All requirements otherwise called out in section 4.2 or 4.3 will be delivered for November

4.2 Post November Requirements

BR # Description Comments

6.01 Application Setup/Configuration

User Preferences

Even though application configuration (setup

rules, setup profiles) is documented in the FRD.

This may not be delivered for November and

hence for any changes that are required, we

would need to work with IT (pre and post

production) to make any configuration related

changes.

6.17 Categories: Company Master, Saved EAs, DUNS, etc

Users can click/hover on any match criteria to drill down

into the rule/data that is involved in making the match.

Need further analysis of the details that need to be

shown for each category and then find a viable

solution that is not complex and does not require

the maintenance of huge set of individual rules to

be stored.

6.12 Note (System Generated)

Contains a note that the system generates using specific

rules. The intent of this note is to give advice to users about

which may help the user determine the overall usefulness

of the EA.

A.1.1.1 The following items in this requirement

need complex logic to be built and

hence will be delivered in the next

releases.

√ If there have been any merges, or LATF‟s for

the EA; display LATF (IN) for licenses transferred

in; display LATF out (if licenses were transferred

out).

https://vmshare.vmware.com/it/pmo/Tier%201%20Project/IB%20ELA/Shared%20Documents/1.%20SDLC%20Documents%20-%20Release%201/1.%20Define/BRDs/IBELA_BRD-EA_ResearchTool_v1.2.docx





VMware CONFIDENTIAL

Logging of Rule Matching Process A.1.1.2 Will need detailed requirements from Biz

. Some of it is available, will need to

build few more and find the right

database to host this data without

impacting performances

Application that can take an admin user step-by-step for

each sub-rule

Will need detailed requirements from Biz and then

analysis of these requirements to

4.3 Out of scope Requirements


1.05 One-click view (Refine Results)

When the user has used the one-click view to display IB,

they should be able to invoke the EA Research tool to help

refine results.

Will not be fulfilled as written here. We no longer

have „One click View‟. A link to EA research tool

be available to be launched from „Quotable assets

view‟. Just a simple link to EA research tool with a

blank state.

4.2.1 Hoovers : It would be desirable if there could be a search of

the Hoover‟s data to determine any other subsidiary/parent

names associated with the VMStar Account or EA.

Based on the feedback, Hoovers is a subsidiary of

D&B and helps in analyzing the D&B data. As we

are already using D&B data and using our own

analysis in creating a VMware hierarchy, the

thought is that this might not be needed. If proven

otherwise, we will need to buy new hoovers

license and use it in future enhancement

4.10.1 License Key : Supplied license key matches EA number. This is no longer required based on the other rules

that are being run and the direction that research

is based on either an Account ID or an EA number

7.03 Ability to View and Manage Saved EA relationships in

VMStar.

View and managing Saved EA‟s will be available

thru the EA research tool. User can click on the

tool button in VMStar and see the Saved EA




VMware CONFIDENTIAL

relationships

7.07 (VMStar) System prompts sales rep to confirm save EA

relationship when opportunity status is changed.

Users can change the status of the saved EA

relationships as required thru the tool

6.12 Note (System Generated)

Contains a note that the system generates using specific

rules. The intent of this note is to give advice to users about

which may help the user determine the overall usefulness

of the EA.

The following items in this requirement cannot be

fulfilled as ACF‟s / iACF‟s are attached to the case

and not to the EA itself.

√ Display any information if the EA contains

ACF‟s, iACF‟s, non-std LATF.

4.4 Assumptions and Constraints


4.8.1 VMSTAR Normalized Name equals EA Name Normalized

Name

Company master currently does not maintain a EA

normalized name and hence a workaround of using

the normalized name of the parties that form the

EA will be used.

Hence the requirements in 4.8.3 & 4.8.4 will not

performed as well as these will no longer be

required.

4.5 Risks

Requirement Issue Impact

Single Sign-On from BI,

SFDC to EA research tool

A.1.1.3 Single sign-on capability is being evaluated

and has not been confirmed yet

A.1.1.4 Users will need to sign-on to the EA

research tool again from these invocation

points using Horizon / VPN




VMware CONFIDENTIAL

Address Rule A.1.1.5 DEV has performance concerns on running of

this rule as this involves string based matching.

They would evaluate this rule during the

implementation phase. If it comes out to be a

big SLA, we will have to remove the rule.

A.1.1.6 This is a Deep rule and „Want‟ from biz. At

the same time the number of EA‟s that

this might independently produce (other

than UUID / DUNs / Company Master

rule) are minimal and hence the risk would

be acceptable




VMware CONFIDENTIAL

5. SOLUTION DESIGN

5.1 To-Be High Level Flow

FR Number FR Description BR Number FR-IB-ELA-01 The following are the various ways a user can access the IB-ELA Research Tool

1) VMStar Account page 2) VMStar Account Plan page 3) VMStar Opportunity 4) VMStar Tab 5) BI Dashboard 6) Admin Portal 7) Standalone portal – Currently accessible to internals only

1.01, 1.02, 1.03, 1.04, 1.05, 1.06, 1.07

Wireframe-IB-ELA-01

SFDC(Account,

Account Plan, Opportunity, Vmstar Tab

New EA Research

Portal

User can save the results

User enters additional account

names or EA’s as search

criteria (if required)

EDW

Initiate research to gather EA’s

based on Saved EA , Order/Bookings,

Contacts, E-mail Domain,

Normalized Names,

Company Master , etc

User shown EA’s in groups of

strong match, probable,

possible along with the criteria that was used

find this (match) the EA

XXVM

User selects 1 or more EA’s and selects

‘Show Quotable

Assets’

Need to search for additional

EA’s

Yes

Punch out to BI dashboard as a

single sign-on. Pass EA’s selected to BI.

End

NoBI Dashboard

Admin Portal




VMware CONFIDENTIAL

Wireframe-IB-ELA-02

Wireframe-IB-ELA-03

Wireframe-IB-ELA-04




VMware CONFIDENTIAL

Wireframe-IB-ELA-05

FR Number FR Description BR Number FR-IB-ELA-03 For the Account detail page layouts that are associated with record type “End

Customer Accounts”, add a new button called “EA Research Tool” as shown in Wireframe-IB-ELA-01

1.01

FR-IB-ELA-03.1 In the Account Plan detail page add a new button called “EA Research Tool” as shown in Wireframe-IB-ELA-02

1.02

FR-IB-ELA-03.2 For the Opportunity detail page layouts that are associated with record type “Managed Sales Opportunity”, add a new button called “EA Research Tool” as shown in Wireframe-IB-ELA-03

1.03

FR-IB-ELA-03.3 Create a tab in VMSTAR called “EA Research Tool”. The tab should be visible to all profiles in VMSTAR. Include the tab in the “Sales” and “Call Center” app to provide easy navigation for the sales users.

1.06

FR-IB-ELA-03.4 In the new BI Dashboard that is specific for „Quotable Assets‟, add a new link called „EA Research Tool‟. This will be available in all the 4 tabs available. Check Wireframe-IB-ELA-04 for details

1.04, 1.05

FR-IB-ELA-03.5 In the EA detail page of admin portal, a new button called „EA research Tool‟ would be available for all users that can access the page. Check Wireframe-IB-ELA-05 for details

1.07

FR-IB-ELA-03.6 Users should have the capability to go to the EA research tool directly. All internal users that currently have AD access will be able to login using their existing AD credentials

1.0

FR-IB-ELA-04 When users click on the “EA Research Tool” button from any of the launch points, the tool will be launched in a new window.

1.01, 1.02, 1.03, 1.04, 1.05, 1.06, 1.07

FR-IB-ELA-04.1 The following information should be provided to the EA Research Tool if launched 1.01, 1.02,




VMware CONFIDENTIAL

from VMSTAR

1. User ID of the user launching the tool

2. First/Last Name of the user

3. SFDC profile Name of the user

4. Name of the SFDC Account from which the tool was launched

5. Customer ID of the SFDC Account from which the tool was launched

6. Opportunity ID if launching from Opportunity page

Note: Technical team should evaluate to integrate the portal page in vmstar within an iFrame with the SFDC tabs at the top and the sidebar to the left and the SFDC footer at the bottom.

1.03, 1.06

FR-IB-ELA-04.2 The following information should be provided to the EA Research Tool if launched from BI Dashboard



1.04, 1.05

FR-IB-ELA-04.3 The following information should be provided to the EA Research Tool if launched from Admin Portal



3. EA Number from which the tool was launched

4. EA Name from which the tool was launched

1.07

FR-IB-ELA-05 Access to the EA lookup tool is restricted to users that currently have access toVMStar, BI Dashboard, Admin Portal No additional restrictions needed. Anybody that has the link from the source system (Admin Portal, SFDC, BI Dashboard) will have access to the EA research portal. For internal users, there is no restriction once you can access the system. All data will be available. Note : Could leverage AD group for this

8.02

FR-IB-ELA-06 User should not be asked to sign-in again (single sign-on) if they are accessing the EA research tool from any of the launch points Note : Single Sign-on is not possible for Admin Portal as it uses a different type of technology for deriving access than others and hence will require the additional sign-on

1.01, 1.02, 1.03, 1.04, 1.05, 1.06, 1.07

FR-IB-ELA-07 A xELArate profile would be attached to each user that is logging into the EA research tool. This will be determined based on the SFDC Profile to xELArate profile mapping that will be created. When a user logs in, we would check if they have a SFDC profile and if yes, we would find the related xELArate profile from the mapping table and assign as the user profile. If an SFDC profile does not exist for the user or if a SFDC profile to xELArate profile mapping does not exist or if a SFDC profile to xELArate profile mapping exists but rules are not defined , then the we will default to „Others‟ (default) profile We need to derive the same xELArate profile consistently irrespective of where they are logging in. ex : SFDC, BI Dashboard, Admin Portal, Standalone Current values for xELArate profile are 1) Sales 2) GSS / License Compliance 3) Renewals 4) Others Note: An initial load of SFDC profile to xELArate profile will be required.

6.02




VMware CONFIDENTIAL

Wireframe-IB-ELA-06

FR Number FR Description BR Number FR-IB-ELA-02 When launching the tool from any of the following pages, the VMStar Account-ID +space

+VMStar Account Name that the user started out from will be defaulted and can be deleted from the listif the user chooses to

1) VMStar Account page 2) VMStar Account Plan page 3) VMStar Opportunity

2.01

FR-IB-ELA-02.1 When launching the tool from Admin portal, the EA Number+space +EA Name that the user started out from will be defaulted and can be deleted from the list if the user chooses to

2.02

FR-IB-ELA-02.2 Information that pops up on a hover will be provided where an „i‟ icon is shown and a link to a KB article will be required where ever a „?‟ is shown

6.0

FR-IB-ELA-08 Once the user lands on the EA research tool, they can enter additional VMStar Account ID‟s or EA Numbers by using on the „EA/VMStar Account Lookup‟ only. User cannot enter an input parameter directly. Clicking on the „EA/VMStar Account Lookup‟ button will open an overlay where the user can enter search criteria like order number, contract number, license key, party name, etc to find additional VMStar account-ID or EA‟s that can then be used as input criteria to perform the research itself

6.05, 6.07




VMware CONFIDENTIAL

Wireframe-IB-ELA-07

FR Number FR Description BR Number FR-IB-ELA-08.1 The top of the page will have the following labels

„Add additional Account EA Names to be Researched‟ and next to that will be an additional label „Use if there are additional subsidiary name(s) to be added or if the initial EA research is missing EA‟s‟

6.07

FR-IB-ELA-08.2 A new lookup with the label „Search Criteria‟ will be available. This LOV will contain the following fields and will provide results related to a VMStar Account or EA VMStar Account

1) VMStar Account Number 2) VMStar Account Name

EA

3) EA Number 4) EA Name 5) Sales Order Number 6) License Key 7) Contract Number 8) EA SU/PC Domain 9) Party Name 10) EA User Domain 11) Instance Number

User should be able to select one of the above search criteria

2.04, 2.05, 2.06, 2.07, 2.08, 2.09, 2.11

FR-IB-ELA-08.3 User should be able to enter an alpha numeric value including special characters in the search string field and click on the „Search‟ button (enabled only if „Search Criteria‟ , „Search String‟ and minimum 3 characters without counting the „%‟ are entered)

2.04, 2.05, 2.06, 2.07, 2.08, 2.09, 2.11

FR-IB-ELA-08.4 If user selects the search criteria of „VMStar Account Number‟ and provides a string related to that, then clicking on the „Search‟ button will search SFDC for an account number that matches the VMStar Account Numberprovided and returns the VMStar

2.03




VMware CONFIDENTIAL

Account Number and VMstar Account Name related to that. An exact search will be made for the input provided

FR-IB-ELA-08.5 If user selects the search criteria of „VMStar Account Name‟ and provides a string related to that, then clicking on the „Search‟ button will search SFDC for account names that match the VMStar Account name provided and returns the VMStar Account Number and VMstar Account Name for each of the matches found. User can include „%‟ to perform a wild card search. Minimum 3 chars (not counting %) are required for search.

2.03

FR-IB-ELA-08.6 If user selects the search criteria of „EA Number‟ and provides a string related to that, then clicking on the „Search‟ button will search EMS for an EA that matches the EA number provided and returns the EA Number and EA Name related to that. An exact search will be made for the input provided

2.03

FR-IB-ELA-08.7 If user selects the search criteria of „EA Name‟ and provides a string related to that, then clicking on the „Search‟ button will search EMS for all EA‟s that match the EA name provided and returns the EA Number and EA Name for each of the matches found. User can include „%‟ to perform a wild card search. Minimum 3 chars (not counting %) are required for search.

2.03

FR-IB-ELA-08.8 If user selects the search criteria of „Sales Order Number‟ and provides a string related to that, then clicking on the „Search‟ button will search EMS for an EA that is related to the sales order number provided and returns the EA Number and EA Name related to that. An exact search will be made for the input provided

2.04

FR-IB-ELA-08.9 If user selects the search criteria of „License Key‟ and provides a string related to that, then clicking on the „Search‟ button will search EMS for an EA that is related to the License Key provided and returns the EA Number and EA Name related to that. An exact search will be made for the input provided

2.05

FR-IB-ELA-08.10 If user selects the search criteria of „Contract Number‟ and provides a string related to that, then clicking on the „Search‟ button will search EBS for an EA that is related to the owner party of the contract number provided and returns the EA Number and EA Name related to that. An exact search will be made for the input provided

2.06

FR-IB-ELA-08.11 If user selects the search criteria of „EA SU/PC Domain‟ and provides a string related to that, then clicking on the „Search‟ button will search EMS for all EA‟s where the super user or procurement contact have the same domain as the domain provided and returns the EA Number and EA Name related to that. User can include „%‟ to perform a wild card search. Minimum 3 chars (not counting %) are required for search.

2.07

FR-IB-ELA-08.12 If user selects the search criteria of „Party Name‟ and provides a string related to that, then clicking on the „Search‟ button will search EBS for parties that match the party name provided and returns the EA Number and EA Name for each of the matches found. User can include „%‟ to perform a wild card search. Minimum 3 chars (not counting %) are required for search.

2.08

FR-IB-ELA-08.13 If user selects the search criteria of „EA User Domain‟ and provides a string related to that, then clicking on the „Search‟ button will search EMS for all EA‟s where atleast 1 user has the same domain as the domain provided and returns the EA Number and EA Name related to that. User can include „%‟ to perform a wild card search. Minimum 3 chars (not counting %) are required for search.

2.09

FR-IB-ELA-08.15 If user selects the search criteria of „Instance Number‟ and provides a string related to that, then clicking on the „Search‟ button will search EBS for an EA that is related to the owner party of the instance number provided and returns the EA Number and EA Name related to that.

2.11




VMware CONFIDENTIAL

An exact search will be made for the input provided

FR-IB-ELA-08.16 All the results will be shown in the space available and user should be able to scroll up or down to see the full results. User should then be able to select one or more EA‟s or Accounts from the results using the check boxes available in the beginning of each record. A select All check will also be available that selects all the results available.

6.07

FR-IB-ELA-08.17 User should be able to click on the „Add‟ button (only enabled if atleast 1 record is selected) to move the selected records to the right and into the appropriate section. If the results are related to an Account Name & Number then they will be moved to the „VMstarAccount Numbers to be researched‟ section and if the results are related to an EA Name & Number then they will be moved to the „EA Numbers to be researched‟ section Each record on the right hand side will be displayed as a single column using the Number + Space + Name format A maximum of 15 records can be added to each section

6.07

FR-IB-ELA-08.18 Each record on the right hand side will be individually selected or multiple records can be selected by using the Ctrl or Shift keys. Once selected, the records can be removed from the right hand side by clicking on the delete button at the bottom.

6.07

FR-IB-ELA-08.19 User should be able to enter a different search criteria and search for new set of results to be added to the research list

6.07

FR-IB-ELA-08.20 Once the research list is finalized, user can either click on the „Cancel‟ button which will close the overlay and does not take any of the EA‟s or Accounts selected to the research page. User can click on the „Ok‟ button to close the overlay and take the EA‟s or Accounts selected to the research page. The list of EA‟s or Accounts selected will be added to any existing list of research parameters already available.

6.07

FR-IB-ELA-08.21 If the total count of EA‟s or Accounts exceeds 15 then the following error message will be shown at the top of the page. „You have reached max. limit count of 15 for EA. Please remove and submit.‟ The user can then select and delete any additional records.

6.07

FR-IB-ELA-09 The first Account ID or EA Number entered (or defaulted) will be marked as the primary (denoted with an asterisk next to it). This will then be used as key for saving the results. User should have the capability to change the primary to any of the input parameters entered.

2.02

FR-IB-ELA-09.1 User should have the capability to select between the standard and deep option based on a radio button. By default, the standard option will be selected. If „Standard‟ is selected, only those match rules / match sub-rules that are marked as standard will be run If „Deep‟ is selected, all match rules / match sub-rules that are marked as „Standard‟ and „Deep‟ will be run. Basically all the rules that are enabled for the profile will be run.

3.02

FR-IB-ELA-10 Once the required input criteria (Account-ID‟s or EA Numbers) are entered, user should be able to click on the „Research Accounts‟. This button is only enabled when atleast 1 account-id or EA number is entered.

6.06

FR-IB-ELA-11 A spinning wheel or loading icon should be shown in the results section from the time user clicks on „Research Accounts‟ to the time the actual results are shown.

3.03

5.2 E2ERule Execution and Result Categorization

5.2.1 E2E Rule Execution




VMware CONFIDENTIAL

FR Number FR Description BR Number FR-IB-ELA-13 For all Account-id‟s or EA numbers provided, first run the following standalone rules and

their sub-rules if enabled and collect EA‟s that are match the criteria along with the strength (strong or weak)

1) Saved EA 2) DUNs 3) Orders 4) Cases 5) Historic Quotes 6) Contacts 7) Address

4.0

FR-IB-ELA-14 For the EA‟s gathered thru the above rules and the Account id/s or EA numbers entered as input, run the following cumulative rules and their sub-rules if enabled

1) Email Domain 2) Company Master 3) Normalized Names

4.0

FR-IB-ELA-15 Collect the full list of unique EA‟s from the standard rules and cumulative rules as a single list along with strengths and other attributes

4.0

FR-IB-ELA-16 For each EA in the list determine the category that the EA should be listed in based on the below rules

5.01

5.2.2 Result Categorization

For all Account ID’s / EA Numbers provided as

input

Collect EA’s and their

strengths using Saved EA rules


strengths using DUNS rules


strengths using Contacts rules

Collect all EA’s from standard rule &

cumulative rules as a single list along

with match criteria and strengths


strengths using Order rules


strengths using Case rules


strengths using Quote rules


strengths using Address rules


strengths using Email Domain

rules


strengths using Normalized Name rules


strengths using Company

Master rules

Show results on portal

Collect full list of EA’s found so far

using standard rules. Use the input

parameters as well

Run categorization rules for each

EA




VMware CONFIDENTIAL

FR Number FR Description BR Number FR-IB-ELA-17 Step 1: Check if the EA is matched based on either Saved EA Relationship or Domain

Match or Normalized Name Match or Customer Masterand the strength of the match is equal to„S‟ (strong). If a match is not made, skip to the next step If a match is made, then check if a „S‟ (strong) match is made based on any other rule excluding the initial rule. If a match is made, then set the category for the EA to „Strong Match‟, else skip to the next step

5.01

FR-IB-ELA-18 Step 2: Check if the EA is matched in any 3 rules with a strength of „S‟ (strong). If a match is made, set the category for the EA to „Strong Match‟. Else skip to the next step

5.01

FR-IB-ELA-19 Step 3: Check if the EA is matchedin any 2rules with a strength of „S‟ (strong). If a match is made, set the category for the EA to „Probable Match‟. Else skip to the next step

5.01

FR-IB-ELA-20 Step 4: Check if the EA is matched in atleast 1non transaction based rules (transaction based rule = cases, orders, or quotes) with a strength of „S‟ (strong) and is matching 3 additional rules with a strength of „W‟ (weak) . If a match is made, set the category for the EA to „Probable Match‟. Else skip to the next step

5.01

FR-IB-ELA-21 If a category is not determined based on any of the steps, set the category for the EA to 5.01

Is the EA matched based on (Saved

EA Relationship or Domain Match or Normalized Name Match or Customer Master)

and strength = S

Is the EA match strength = S in atleast 1 other matching rule

Categorize EA as

‘Strong Match ’

Is the EA match strength = S in any 3 matching rules

Yes Yes

NoNo

Yes

Is the EA match strength = S in any 2 matching rules

Yes

Categorize EA as

‘Probable Match ’

Is the EA match strength = S in 1 non-transaction matching rule

Is the EA match strength = W in any

3 matching rules

Categorize EA as

‘Possible Match ’

No

No

Yes

Yes

No

No

Display EA’s in categories along with EA details, Match Criteria, Match Strength

For each unique EA collected based on all matching rules, perform the next

steps




VMware CONFIDENTIAL

„Possible Match‟.

FR-IB-ELA-22 Display results in the results section based on the categories determined along with the

count of records in each category 6.08a, 6.08b

5.3 Display and Manage Research Results

Wireframe-IB-ELA-08

FR Number FR Description BR Number FR-IB-ELA-23 Following column names will be shown to the user for each EA that is gathered and in

the order specified below

1) EA Name 2) EA Number

3) Country(s) - Display the 2 digit ISO code of countries (separated by „,‟) associated to the EBS party/party sites that make up the EA. The first 5 codes will be displayed after which an ellipsis (…) will be shown. User can hover/click on the ellipsis to see the full list of country codes

4) EA Comments (Notes) – System generated comments based on additional rules that provide additional information about the EA (ex : No Active IB, Federal / Personal Account, ELA contract, etc). Check requirement FR-IB-ELA-24.1 below for details

5) Sites - Show the number of unique sites (city + country combination) associated to the EBS Parties which make up the EA. Ex : A „unique‟

6.09, 6.10, 6.11, 6.12, 6.13, 6.15, 6.16, 6.16.1,




VMware CONFIDENTIAL

site is a city + country combination within the EA. If party 1 has a site at 101 Main Street, City A, NZ; and party 2 has a site at 345 A Street, City A, NZ; then only one site will be counted.

6) Customer Domain - For each party associated to the EA find all unique domains that are associated to the contacts in EBS. The first 3domains will be displayed separated by a „,‟ and a new line after which an ellipsis (…) will be shown. User can hover/click on the ellipsis to see the full list of country codes

7) SU Name – Super User Name 8) SU Email Address – Super User Email Address 9) PC Name – Procurement Contact Name 10) PC Email Address – Procurement Contacts Email Address

FR-IB-ELA-23.1 EA Comments (Notes) field is available for each EA and will be populated based on the below logic. All the rules will be executed and if a condition in the rule is met then the appropriate comment will be added to the existing comments by using „,‟ (coma) as a separator. The first 3 comments will be displayed after which an ellipsis (…) will be shown. User can hover / click on the ellipsis to see the full list of comments

1) Check if there is atleast 1 active IB associated to the EA. If not, add the note „No Active IB‟ to the EA comments field

2) If the EA is of the Type = Person then add the note „Individual Account‟ 3) If the EA is of the segment = Federal then add the note „Federal Account‟ 4) If the EA has an ELA contract that is currently active then add the note „Active

ELA‟ 5) If the EA has an active contract of the type MCS or BCS, then add the note

„Active MCS / BCS‟ 6) If a different EA has been merged into this EA, then add the note „EA

<Victim_EA> Merged‟ 7) If an LATF has been made into this EA, then add the note „LATF (IN) from

<Source_EA> „ 8) If an LATF has been made from this EA, then add the note „LATF (OUT) from

<Target_EA> „

6.12

FR-IB-ELA-23.2 User can double click on any of values in „Country‟, „Sites‟, and „Customer Domains ‟to display additional details. Derive all the parties that belong to an EA and their respective site details. Domain column will have all the unique domains that belong to the sites contacts. There will be 1 row for each Address Line 1, City, Postal Code and Country combination of a party.

1) Party Number : Each row will have the EBS party number that is part of this EA 2) Party Name : The party name associated to each party number 3) Domain(s) : All the unique domains that belong to the sites contacts 4) Address Line 1 : Address Line 1 that corresponds to the sites location 5) City : City that corresponds to the sites location 6) Postal Code : Postal Code that corresponds to the sites location 7) Country : Country that corresponds to the sites location

Check Wireframe below for reference

6.11, 6.13, 6.15




VMware CONFIDENTIAL

Wireframe-IB-ELA-09

FR Number FR Description BR Number FR-IB-ELA-24 All the primary matching rules that currently exist will be displayed as individual columns

along with the strength where a match is made

1) Company Master 2) Saved EA 3) DUNs 4) Orders / Bookings 5) Cases 6) Historical Quotes 7) Email Domain 8) Normalized Name 9) Contacts 10) Address 11) Manual Add

6.17

FR-IB-ELA-27 Each EA shown in results section will have a check box available at the end. User can select 1 or more checkboxes. A select all box would be available at the top which enables the users to select all the EA‟s. Users should still be able to uncheck or check individual EA‟s as needed. Unchecking the select all box will unselect all current selections including any that were manually selected. This checkbox will determine which EA‟s will be deleted / saved / show quotable assets

6.18

FR-IB-ELA-27.1

„Add Accounts‟, „Delete Selected Accounts‟, „Save‟ buttons will be shown at the bottom. These buttons are always anchored to the bottom of the window and the user does not have to scroll down to view or act on these buttons.

7.01, 7.02

FR-IB-ELA-25 User should be able to select 1 or more EA‟s from the results using the check boxes and click on the „Delete Selected Accounts‟ button (only enabled when atleast 1 EA is selected). Clicking on the button will show a confirmation box as a pop-up which has

7.01, 7.02




VMware CONFIDENTIAL

„Confirm‟ and „Cancel‟. Clicking on „Confirm‟ will delete all the EA‟s selected from the results section, whereas the cancel or close of the pop-up will not delete the EA‟s and they will continue to be shown in the results

FR-IB-ELA-26 User should be able to click on the „Add Accounts‟ to add an EA to the list. User will be prompted to enter an EA number value in a new overlay which will also have an OK and Cancel buttons. Any number entered and submitted will be validated against the active list of EA‟s available. If an active EA is not found then a message „Value entered does not belong to a valid EA‟. The user should be able to provide a new value if they wish or cancel the add operation. Once a valid EA is found, then the EA will be added to the list under the „Strong Match‟ category. Other composite values of the EA (countries, notes, sites, etc) should also be derived and displayed. Following list of attributes should be available for this record.

1) EA Name 2) EA Number 3) Country(s) 4) EA Comments (Notes) 5) Sites 6) Customer Domain 7) SU Name 8) SU Email Address 9) PC Name 10) PC Email Address 11) Manually Added flag in the match criteria section will be set to „x‟

7.01, 7.02

FR-IB-ELA-28 Once the EA selection/s have been made using the check boxes in the end, user can click on the „Show Quotable Assets‟ button (only enabled if atleast 1 EA is selected). Whenever the user clicks on the „Show Quotable Assets‟ button, before launching the Quotable Assets window a confirmation screen will be shown which asks the users if they want to save the current result set before continuing.

6.19

Wireframe-IB-ELA-10




VMware CONFIDENTIAL

FR Number FR Description BR Number FR-IB-ELA-28.1 User will be shown an overlay as displayed above with the following details

A header that reads as follows will be shown : „You will now be directed to a new window that shows the quotable assets. Would you like to save the EA‟s that are currently shown before going to the quotable assets window ?‟ 2 buttons „Save EA‟s and continue‟ and „Continue without saving‟ will be shown A note will be shown at the bottom of the window that reads as follows „Note : The research window will still be available in the background and you can continue your research in that window‟ If the user clicks on „Continue without saving‟ then the overlay will be closed and a new window will be opened for the BI Dashboard. If the user clicks on the „Save EA‟s and continue‟, the save operation is initiated based on the next few requirements.

7.01

FR-IB-ELA-28.2 The Account ID or the EA number that is marked as primary in the input parameters will be used as the key for saving the relationship. This primary Key along with the users profile (Sales, Others, etc) will become the unique identifier for the relationship. If a saved relationship exists for the account ID or EA number and profile combination, then user should be provided a choice of either replacing the full list or add any new EA‟s to the existing list. If a saved relationship doesn‟t exist, then all the EA‟s that are currently shown to the user will be saved for the unique key combination

7.01, 7.04

Wireframe-IB-ELA-11

FR Number FR Description BR Number FR-IB-ELA-28.3 The overlay (that displayed the user the choice to save) will be refreshed and the above

screen will be shown to the user.

7.01, 7.05




VMware CONFIDENTIAL

A header will be displayed as follows „A saved EA list already exists for the <<key type> : <key value>> and <profile value>profile combination. Would you like to add your EA‟s to this existing list or replace the existing list with your EA‟s.‟ The following 3 buttons would be displayed. „Add to existing List‟, „Replace existing list‟, „Continue without saving‟. A footer will be displayed as follows „Note: If you plan to replace the existing list with your list, be mindful of the fact that other users that saved / using the existing list will lose their data.‟ If user clicks on „Add to existing list‟, then all EA‟s from the result set that are currently not available in the existing list will be added to the list. If user clicks on „Replace existing list‟, then all EA‟s from the existing list will be deleted and all EA‟s from the new result set will be added to the list. In both the cases the status of the existing relationship will be flipped to „Interim‟ status.The date and time stamp of the save will be marked along with a comment of „System save based on quotable assets view‟. The user that clicked on the show quotable assets view will be marked as the user that performed the last save. If the user clicks on the „Continue without saving‟, the save operation is aborted and user will be taken to BI Dashboard.

FR-IB-ELA-29 The following list of attributes will be saved for each EA 1) EA Name 2) EA Number 3) Manual Add 4)

7.01, 7.02

FR-IB-ELA-30 If the user chooses to continue without saving, the BI dashboard will be launched in a separate window. If the user choose to save the EA‟s (Add / Replace), then the BI Dashboard is launched in a separate window only after the save operation is successfully completed. The EA‟s that have been selected in the EA research tool will be passed as parameters to the BI Dashboard. The BI dashboard should not ask the user for a sign-on. BI Dashboard should take the EA‟s passed as input parameters and show the quotable assets related to these EA‟s by default (without the user clicking on search or other buttons)and in the format that is appropriate for the user‟s profile.

6.19, 7.01

FR-IB-ELA-31 User should still be able to perform additional research or filter EA results in the EA research tool and select a different set of EA‟s and click on the show quotable assets view to launch the BI dashboard for the new set of EA‟s in a new window

6.19

FR-IB-ELA-32 Users should be able to filter the results by using either of the criteria

1) Filter by country : Show all EA‟s where the Country column has atleast 1 of the country codes provided as filter. Multiple values can be entered by using a Comma as separator. If multiple values are entered, an „OR condition should be applied between the values entered

2) Filter by domain : Show all EA‟s where the domain columns has atleast 1 of the domain‟s provided as filter. Multiple values can be entered by using a Comma as separator. If multiple values are entered, an „OR condition should be applied between the values entered

3) Filter by name including a contains filter : Show all EA‟s where the EA name column matches the name provided including a capability for wildcard search. Multiple values can be entered by using a Comma as separator. If multiple values are entered, an „OR condition should be applied between the values entered

4) Filter for any rule matches (i.e.DUNS, Company Master matches) : Show all EA‟s where the match rule/s selected have an S or W

6.08c




VMware CONFIDENTIAL

If multiple filters (country, domain, etc) are set, then an „AND‟ condition will be applied between the different filters. A clear all filters button should be available which will clear all the filters and refresh the results and show all the data. (any EA‟s that are specifically removed using the remove/delete capability will not be part of the results even after filters are removed, but at the same time, any EA‟s that were manually added should be shown as part of the filtered result set)

FR-IB-ELA-33 User should have the capability to export to CSV by clicking on the „Export Results‟ link (enabled only if atleast 1 record is available in results) the CSV will only have the results that are currently shown to them on the portal. If any filters have been applied, EA‟s belonging to the filters should not be shown in export. An „Export All‟ link will also be available that exports all results by ignoring the filters that have been set. The list of EA‟s retrieved and all related details fields should be exported. The prioritization levels (strong, probable, and possible) should be moved to Excel columns and the results sorted based on these columns. The order would be Strong, Probable, possible.

6.08d

FR-IB-ELA-33.1 User can select 1 or more EA‟s and click on the „Save EA results‟ button (only enabled if atleast 1 EA is selected) Upon clicking the „Save EA Results‟ button, user will be provided a choice of saving the result against an opportunity or quote

7.01

Wireframe-IB-ELA-12

FR Number FR Description BR Number FR-IB-ELA-33.2 User will be shown an overlay as displayed above with the following details

A header that reads as follows will be shown : „Would you like to save the results for a specific transaction ?. If yes, enter the related opportunity ID or the quote ID‟ 2 fields with a radio button capability will be available. „No‟ and „Yes‟. Default selection is „No‟. If „Yes‟ is selected, the user will then be able to select the label „Opportunity ID‟ or „Quote ID‟ or „Case Number‟ from an LOV and then enter its respective value. The value

7.01




VMware CONFIDENTIAL

that can be entered can be an alpha-numeric value with special characters. The default selection is „Opportunity ID‟. When „Opportunity ID‟ is selected, the value column will become a LOV that also allows new values to be entered. The list of values shown in the LOV will be all the open opportunity ID‟s in SFDC that are associated to accounts that are inturn associated to the user. If the user landed here after initiating the research from the VMStar Opportunity page, then the related opportunity should be defaulted. A comments field will be provided that can accommodate upto 300 characters including special characters User will be provided a „Submit‟ button (enabled only when a min of 10 characters are entered in comments field) that they can click once the desired values are entered.

FR-IB-ELA-33.3 The Account ID or the EA number that is marked as primary in the input parameters will be used as the key for saving the relationship. This primary Key along with the users profile (Sales or Others) will become the unique identifier for the relationship. If a transaction specific ID (Optty ID / Quote ID/Case number) is entered, then it will be used as an additional attribute in creating the unique key If a saved relationship exists for the unique key combination, then user will be provided a choice of either replacing the full list or add any new EA‟s to the existing list, else the full list of EA‟s selected would be saved for the unique key combination

7.01

Wireframe-IB-ELA-13

FR Number FR Description BR Number FR-IB-ELA-33.4 The overlay (that displayed the user the choice to save) will be refreshed and the above

screen will be shown to the user. A header will be displayed as follows „A saved EA list already exists for the <<primary key type> : <key value>>, <<secondary key type> : <key value>> and <profile value> profile combination. Would you like to add your EA‟s to this existing list or replace the existing list with your EA‟s.‟ The following 3 buttons would be displayed. „Add to existing List‟, „Replace existing list‟, „Cancel Save‟.

7.01




VMware CONFIDENTIAL

A footer will be displayed as follows „Note: If you plan to replace the existing list with your list, be mindful of the fact that other users that saved / using the existing list will lose their data.‟ If user clicks on „Add to existing list‟, then all EA‟s from the result set that are currently not available in the existing list will be added to the list and the users lands back on the EA results page. If user clicks on „Replace existing list‟, then all EA‟s from the existing list will be deleted and all EA‟s from the new result set will be added to the list and the users lands back on the EA results page. In both the cases the status of the existing relationship will be flipped to „Interim‟ status. The date and time stamp of the save will be marked along with the commentsentered by the user. The user that is performing this operation will be marked as the user that performed the last save. If the user clicks on the „Cancel Save‟, the save operation is aborted and user will be taken to EA results page.

FR-IB-ELA-33.5 The following list of attributes will be saved for each EA 1) EA Name 2) EA Number 3) Manual Add

7.01

5.4 Rules

5.4.1 Eligibility

5.4.1.1 To-Be Flow

5.4.1.2 Steps

FR Number FR Description BR Number FR-IB-ELA-33.6 For each Match rule or sub-match rule, check if the rule is eligible for the user profile and

user selected option (standard / deep) 6.01

FR-IB-ELA-33.7 Check if the rule is enable for the users profile, if not, do not execute the match rule or 6.01

Is rule enabled for users profile

Do not execute ruleYes

Rule eligible for type (standard / deep) selected

Yes

Eligibility

Continue Rule execution

No

No




VMware CONFIDENTIAL

sub-match rule and skip to the next rule

FR-IB-ELA-33.8 If the above validation is a pass, then check if the type selected by the user (deep or standard) matches the type defined for rule or sub-match rule , if matching execute rule, else skip to the next rule If user selected „Standard‟ : Execute all rules that are defined as Standard If user selected „Deep‟ : Execute all rules that are defined as Standard and Deep

6.01

5.4.2 Saved EA

5.4.2.1 To-Be Flow

Start

Search in saved EA relationships table where the account

ID is the primary key

Profile (Sales, Renewals, etc) of

relationship ?

Different from users profile

Same as the users profile

Set Saved EA flag as ‘W’ (Weak)

Relationship status ?

For each Account ID entered

Set Saved EA flag as ‘S’ (Strong)

Certified

Interim

Return all unique EA’s with the

strength set to the highest found.

Gather all EA’s in each of the

relationships found

For each of the EA’s found (There will be duplicates from different profiles), follow the below steps

For each EA Number entered

Search in saved EA relationships table where the EA Number is the primary key or just part of the relationship

If a match is found, find other relationships where

the EA’s in this relationship are marked as primary

EligibilityEligibility




VMware CONFIDENTIAL

5.4.2.2 Steps

FR Number FR Description BR Number FR-IB-ELA-34 For each Account id or EA number entered perform the following steps 4.03, 4.04

FR-IB-ELA-35 Account ID Rule (Standard): If an Account ID is entered and eligible to be executed, then search in the saved relationships table for all saved searches where the Account ID is marked as a primary. For each saved relationship found, create a list of the EA‟s and their profile as output and for each unique EA‟sfind other relationships where this EA is the primary key.For each saved relationship found, add the EA‟s and their profile to the list Note: Only those relationships that do not have a secondary key will be taken into consideration.

4.03

FR-IB-ELA-35.1 EA Number Rule (Standard): If an EA number is entered and eligible to be executed, search for all saved relationships where this EA is either the primary key or part of the saved EA‟s list. Add all EA‟s and their respective profiles to the EA list Note: Only those relationships that do not have a secondary key will be taken into consideration.

4.04

FR-IB-ELA-36 For each EA found (including duplicates), perform the next set of steps. If no EA‟s are found then end of this rule Check if the users profile matches the profile of the saved EA relationship. If it matches, perform next step, else set the „Saved EA Flag‟ strength for the EA to „W‟ (weak) If the status of the saved EA relationship is „Certified‟, set the „Saved EA Flag‟ strength for the EA to „S‟ (strong). Else, If the status of the saved EA relationship is „Interim‟, set the „Saved EA Flag‟ strength to „W‟ (weak) Return all unique EA‟s collected with Saved EA rule and set the „Saved EA Flag‟ strength set to the highest gathered for an EA

4.03, 4.04




VMware CONFIDENTIAL

5.4.3 Orders

5.4.3.1 To-Be Flow

5.4.3.2 Steps

FR Number FR Description BR Number FR-IB-ELA-37 For each Account id or EA number entered perform the following steps 4.3.1,

4.3.2, 4.3.3, 4.3.4

FR-IB-ELA-38 VMStar Contacts to Orders Rule (Standard): If an Account IDis entered and rule is eligible to be executed, Find other accounts that match normalized account name + Country. For each account found, get all the associated contacts from VMStar. Remove all contacts with domains like „Gmail‟

4.3.2

Start

Check if EA's UCM account

normalized names = Normalized SFDC

Account name

Set Order flag as ‘S’ (Strong)

Domain of order sold to/licensed to

contact = domain of any EA user

Account ID / EA Number provided ?

Find all orders associated to the EA

EA #

Account ID

Match

No

Set Order flag as ‘W’ (Weak)

No

Match


highest strength found.

Find other accounts that match

normalized account name + Country

For each Account found

For each order, Find associated EA

Number for EMS

For each Account found, get all

associated contacts in SFDC

Remove contacts with domains like

‘Gmail’ (Eloqua rules).

For each remaining contact


number

More than 1 VMStar contact has the same email domain as

the primary domain associated to EA

Yes

No

Find orders where the contact is marked as aSold-to / Licensed-to

contact

For each order, get the Sold-to /

Licensed-to contact For each contact

Find orders where the contact is marked as aSold-to / Licensed-to

contact


number

For each order found, get the

associated Sold-to / Licensed-to contact

Is either of the order

contacts marked as a contact in SFDC

Account

No

End of this search

Find associated UUID and then fetch

the related party ( account)

Find all associated orders in SFDC

Find all orders where the account has played any part

(Bill-To, Ship-To, Deliver-To, etc)

Check if EA's UCM account

normalized names = Input EA’s UCM

account normalized name

Yes

No

Eligibility

Eligibility

Eligibility

Eligibility

Eligibility




VMware CONFIDENTIAL

List of Email domains to be excluded:

For each remaining contact, find orders in EBS where the contact is marked as the Sold-To or the License-To (stored in DFF) contact For each order found, get the associated EA number from EMS. If found, check if the EA primary users email domain is the also available as an email domain on the more than 1 VMStar contact If found set the strength of the „Order Flag‟ to „S‟ (strong) , else set it as „W‟ (weak)

FR-IB-ELA-39 VMStar Orders to Contacts Rule (Deep): If an Account ID is entered and rule is eligible to be executed, Find other accounts that match normalized account name + Country. For each account found, get all the orders associated to the account in VMStar(SFDC). For each order found, get the Sold-To or the License-To contact and check if the contact is marked as one of the SFDC accounts contacts. If not found, find orders in EBS where the contact is marked as the Sold-To or the License-To (stored in DFF) contact, else end of this sub-rule For each order found, get the associated EA number from EMS. If found, check if the EA primary users email domain is the also available as an email domain on the more than 1 VMStar contact If found set the strength of the „Order Flag‟ to „S‟ (strong) , else set it as „W‟ (weak)

A.1.1.7 4.3.4

FR-IB-ELA-39.1 VMStar UUID to Orders Rule (Standard): If an Account ID is entered and rule is eligible to be executed, Find other accounts that match normalized account name + Country. For each account found, Find associated UUID and then fetch the related party ( account) . For each party / account found, Find all orders where the account has played any part (Bill-To, Ship-To, Deliver-To, etc). For each order found, get the associated EA number from EMS. If found, check if the EA primary users email domain is the also available as an email domain on the more than 1 VMStar contact If found set the strength of the „Order Flag‟ to „S‟ (strong) , else set it as „W‟ (weak)

4.3.1

A.1.1.8 FR-IB-ELA-40

A.1.1.9 VMStar Orders to EA Rule(Standard): If an Account ID is entered and rule is eligible to be executed, Find other accounts that match normalized account name + Country.

A.1.1.10 For each account found, get all the orders associated to the account in VMStar(SFDC). For each order found, get the associated EA number from EMS. If found, check if the EA‟s UCM account normalized name is the same as the normalized name of the SFDC account. If matching set the strength of the „Order Flag‟ to „S‟ (strong) , else check if the Domain of order sold to/licensed to contact matches the domain of any user in the EA. If matching set the strength of the „Order Flag‟ to „S‟ (strong) , else set it as „W‟ (weak)

4.3.1

FR-IB-ELA-41 EA Number Order to Contacts Rule (Standard): If an EA Number is entered and rule is eligible to be executed, Find all orders that are associated to the EA in EMS. For each order found, get the Sold-To and License-To contacts from EBS and for each of the

4.3.3

Email domains to be excluded from contacts.xlsx




VMware CONFIDENTIAL

distinct contacts find other orders in EBS which has these contacts marked as Sold-To or License-To. For each order found, get the associated EA number from EMS. If found, check if the EA‟s UCM account normalized name is the same as the input EA‟s UCM account normalized name. If same, set the strength of the „Order Flag‟ to „S‟ (strong), else set to „W(eak)‟ and move onto the next record.

FR-IB-ELA-41.1 From all the EA‟s collected for Order rules, Return unique EA‟s with the „Order Flag‟ strength set to the highest gathered for the EA

4.3.1, 4.3.2, 4.3.3, 4.3.4




VMware CONFIDENTIAL

5.4.4 DUNs

5.4.4.1 To-Be Flow

Start

Is there match based on Party DUNS or

Domestic Ultimate DUNS

Set DUNS flag as ‘W’ (Weak) for the EA


No

Set DUNS flag as ‘S’ (Strong) for the EA

Yes

Return all unique EA’s with the strength set to

the highest found.

Fetch the DUNS number on the VMStar account

Is a DUNS value available

Yes

No

Search EDW (not EBS) party data to see which parties have the same DUNS value and a EA number is available.

Where available fetch the EA #, Party DUNS, Domestic Ultimate DUNS and

Global Ultimate DUNS

Match based on Global ultimate

Eligibility




VMware CONFIDENTIAL

5.4.4.2 Steps

FR Number FR Description BR Number FR-IB-ELA-41.2 DUNs Rule (Standard): If an Account ID is entered and rule is eligible to be executed,

fetch the DUNs number associated to the VMStar account If a DUNS number is available, Search EDW (not EBS) party data to see which parties have the same DUNS value and the parties have a related EA number available. Where an EA is available fetch the EA #, Party DUNS, Domestic Ultimate DUNS and Global Ultimate DUNS If the SFDC DUNs to the party match is based on Party DUNS or Domestic Ultimate DUNS, then set the „DUNs Flag‟ strength to „S‟, else is the match is based on global ultimate set the strength flag „W‟ for the EA.

4.1.1

FR-IB-ELA-41.3 From all the EA‟s collected for Duns rule, Return unique EA‟s with the „DUNs Flag‟ strength set to the highest gathered for the EA

4.1.1

5.4.5 Cases

5.4.5.1 To-Be Flow

Start

Set Case flag as ‘S’ (Strong)


Find all users associated to the EA

EA #

Account ID

Set Case flag as ‘W’ (Weak)No

Yes

Return unique EA’s with the highest strength found.



For each Account found, find all associated cases in SFDC where

an EA is available. Do not consider any cases that are

related to the ‘Default Consumer Account’





For each remaining

contact

For each case that is found and has an EA

that is associated

Use the contacts email to find other cases that were logged with that email. Do not consider any cases that are related to the ‘Default

Consumer Account’

For each user, Find cases that were submitted by the user and have an EA # associated. Do not consider any cases that are related to the

‘Default Consumer Account’

For each unique EA found

Check if Normalized EA

Name = Normalized Account name

Yes

No

Domain of the primary case contact

occurs more than once on the VMStar account

contact list

Eligibility

Eligibility

Eligibility

Check if Normalized EA

Name = Input EA’s Normalized name

Yes

Domain of the primary case contact

occurs more than once on the input EA

user list

No

Yes

No




VMware CONFIDENTIAL

5.4.5.2 Steps

FR Number FR Description BR Number FR-IB-ELA-41.4 EA Users to Cases Rule (Standard): If an EA Number is entered and rule is eligible to be

executed, fetch all users associated to the EA and for each user, Find cases that were submitted by the user and have an EA # associated. Do not consider any cases that are related to the „Default Consumer Account‟ (There are about 11 such default accounts, exclude all) If an EA number is available, check if the EA‟s UCM party normalized name is the same as the input EA‟s UCM party normalized name. If yes, set the „Case Flag‟ strength to „S‟, else, check if the domain of the cases primary contact occurs more than once on the EA‟s user list. If yes, set the „Case Flag‟ strength to „S‟, else, set the flag to „W‟

4.4.3

FR-IB-ELA-41.5 VMStar account Contacts to Cases Rule (Deep): If an Account ID is entered and rule is eligible to be executed, fetch all the SFDC accounts based that have the same normalized name + country as the input account. For each account, find all the contacts and remove all contacts with domains like „Gmail‟. For each remaining contact, Find other cases that were submitted by the contact email and have an EA # associated. Do not consider any cases that are related to the „Default Consumer Account‟ (There are about 11 such default accounts, exclude all) If an EA number is available, check if the EA‟s UCM party normalized name is the same as the input account normalized name. If yes, set the „Case Flag‟ strength to „S‟, else, check if the domain of the cases primary contact occurs more than once on the accountscontacts list. If yes, set the „Case Flag‟ strength to „S‟, else, set the flag to „W‟

4.4.2

FR-IB-ELA-41.6 VMStar account to Cases Rule (Standard): If an Account ID is entered and rule is eligible to be executed, fetch all the SFDC accounts based that have the same normalized name + country as the input account. For each account, find all the cases submitted for the account and an EA is available. Do not consider any cases that are related to the „Default Consumer Account‟ (There are about 11 such default accounts, exclude all) If an EA number is available, check if the EA‟s UCM party normalized name is the same as the input account normalized name. If yes, set the „Case Flag‟ strength to „S‟, else, check if the domain of the cases primary contact occurs more than once on the accounts contacts list. If yes, set the „Case Flag‟ strength to „S‟, else, set the flag to „W‟

4.4.1

FR-IB-ELA-41.7 From all the EA‟s collected thru allCase rules, Return unique EA‟s with the „Case Flag‟ strength set to the highest gathered for the EA

4.4.1, 4.4.2, 4.4.3




VMware CONFIDENTIAL

5.4.6 Quotes

5.4.6.1 To-Be Flow

5.4.6.2 Steps

FR Number FR Description BR Number FR-IB-ELA-41.8 VMStar Account to Quotes Rule (Standard): If an Account ID is entered and rule is

eligible to be executed, fetch all the SFDC accounts based that have the same normalized name + country as the input account.

4.5.1

Start

Set Quote flag as ‘W’ (Weak)


Set Quote flag as ‘S’ (Strong)


the highest found.

Fetch all ELA header quotes that have the account ID

For each header quote found

Gather any EA # marked in the

‘Purchaser’s EA #’ column

Find the IB quote related to header

ELA quote by using the quote number in

‘IB Quote #’ field

Retrieve all the EA numbers from the ‘EA #’ field in the

quote detail

Check if Quote reached the validation

stages

Yes No

For each value found

For each EA # entered

Fetch all ELA header quotes where the EA # is available in the ‘Purchaser’s EA #’

column

Find all IB quotes where the EA is

available in ‘EA #’ field in the quote

detail

For each Header ELA

Quote found

Find IB Quote

Find IB Quote

For each IB quote found

Find the related header ELA quote by

using the quote number in ‘IB Quote

#’ field

Find header

EA

Find header

EA

Find Detail

EA

Find Detail

EA

Find other accounts that match normalized account name + Country


Check if it is a valid EA number




VMware CONFIDENTIAL

For each account, fetch all ELA header quotes that have the same account ID as the input account ID. For each header quote found perform both the steps

1) Find any EA marked in the „Purchasers EA#‟ field and check if it is a valid EA #. If it is a valid EA, check if the header quote has reached validation stages and if yes set the „Quote Flag‟ to „S‟, else set the flag as „W”

2) Find the IB quote related to header ELA quote by using the quote number in „IB Quote #‟ field. If found, retrieve all the EA numbers from „EA #‟ field in the quote detail. For each value found, check if it is a valid EA #. If it is a valid EA, check if the IB quote has reached validation stages and if yes set the „Quote Flag‟ to „S‟, else set the flag as „W”

FR-IB-ELA-41.9 EA Number to Quotes Rule (Standard): If an EA Number is entered and rule is eligible to be executed, perform all the steps for each EA entered as input.

1) For theEA, fetch all ELA header quotes where the EA is available in the „Purchaser EA #‟ field. For each header quote found, perform both the steps below

a. Check if the header quote has reached validation stages and if yes set the „Quote Flag‟ to „S‟, else set the flag as „W”

b. Find the IB quote related to header ELA quote by using the quote number in „IB Quote #‟ field. If found, retrieve all the EA numbers from „EA #‟ field in the quote detail. For each value found, check if it is a valid EA #. If it is a valid EA, check if the IB quote has reached validation stages and if yes set the „Quote Flag‟ to „S‟, else set the flag as „W”

2) Find all IB quotes where the input EA is available in the „EA#‟ field of the quote detail.For each IB quote found perform both the steps

a. Retrieve all other EA numbers from „EA #‟ field in the quote detail. For each value found, check if it is a valid EA #. If it is a valid EA, check if the IB quote has reached validation stages and if yes set the „Quote Flag‟ to „S‟, else set the flag as „W”

b. Find the related header ELA quote where the header quotes „IB Quote #‟ field is the same IB quote found. If found, find any EA‟s marked in the „Purchasers EA#‟ field and check if it is a valid EA #. If it is a valid EA, check if the header quote has reached validation stages and if yes set the „Quote Flag‟ to „S‟, else set the flag as „W”

4.5.1

FR-IB-ELA-41.10 From all the EA‟s collected thru all Quote rules, Return unique EA‟s with the „Quote Flag‟ strength set to the highest gathered for the EA

4.5.1




VMware CONFIDENTIAL

5.4.7 Contacts

5.4.7.1 To-Be Flow

5.4.7.2 Steps

FR Number FR Description BR Number FR-IB-ELA-42 For each Account id or EA number entered perform the following steps 4.6.1, 4.6.2,

4.6.3

FR-IB-ELA-43 VMStar Contact to EA SU Rule (Standard): If an Account ID is entered and rule is eligible to be executed, Find other accounts that match normalized account name + Country. For each account found, get all the associated contacts from VMStar. Remove all contacts with domains like „Gmail‟ For each remaining contact, find EA‟s in EMS where the contact is marked as a SU/PC or Folder Administrator on the EA. If the user is a SU / PC, set the „Contacts Flag‟ to „S‟ (strong), else if the user is a folder administrator, check if the normalized name of the EA is the same as the normalized

4.6.1

Start

Set Contacts flag as ‘S’ (Strong)


Find all users associated to the EA

EA #

Account ID

Set Contacts flag as ‘W’ (Weak)









For each remaining contact

User role on EA

SU/PC

Find EA’s where the contact is an user on the

account

For each user on the EA provided as input

Find other EA’s which this user has access to

Check if Normalized Account

Name = Normalized EA name

Folder Admin No

Check if Normalized Account

Name = Normalized EA name

Yes

Regular User

Yes

Any other VMStar contact has

the same email domain as this

contact

Yes

Set Contacts flag as ‘W’ (Weak)

Set Contacts flag as ‘S’ (Strong)

NoNo

Is the user SU / PC on

both the EA’s

No

Yes



For each EA found

Are the first 8 characters same on both

the EA’s

Yes

No

Is the email domain

occurring more than once on

both EA’s

Yes No

Eligibility

Eligibility

SU/PC or Folder Admin

SU/PC or Folder Admin

Eligibility




VMware CONFIDENTIAL

name of the account. If matching then set the „Contacts Flag‟ to „S‟ (strong) else set the „Contacts Flag‟ to „W‟ (weak).

FR-IB-ELA-43.1 VMStar Contact to EA User Rule (Deep): If an Account ID is entered and rule is eligible to be executed, Find other accounts that match normalized account name + Country. For each account found, get all the associated contacts from VMStar. Remove all contacts with domains like „Gmail‟ For each remaining contact, find EA‟s in EMS where the contact is marked as a user on the EA. If the user is a regular user, check if the normalized name of the EA is the same as the normalized name of the account. If matching, check if the any other VMStar contact has the same email domain as this contact (repeated more than once). Else set the „Contacts Flag‟ to „W‟ (weak). If more than 1 vmstar contacts has the same email domain, then set the „Contacts Flag‟ to „S‟ (strong) else set the „Contacts Flag‟ to „W‟ (weak).

4.6.2

FR-IB-ELA-44 EA User to other EA Rule (Standard): If an EA Number is entered and rule is eligible to be executed, Find all users that are associated to the EA in EMS. For each of the users, find others EA‟s that this user is associated to and for each EA found, check if the user is SU/PC on both the accounts. If yes, set the strength of the „Contacts Flag‟ to „S‟ (strong). Else, check if the first 8 characters are matching on both the EA‟s. If yes, set the strength of the „Contacts Flag‟ to „S‟ (strong) Else, check if an email domain is occurring more than onceon both the EA‟s. If yes, set the strength of the „Contacts Flag‟ to „S‟ (strong). Else set the „Contacts Flag‟ to „W‟ (weak).

4.6.3

FR-IB-ELA-44.1 From all the EA‟s collected for Contact rules, Return unique EA‟s with the „Contacts Flag‟ strength set to the highest gathered for the EA

4.6.1, 4.6.2, 4.6.3




VMware CONFIDENTIAL

5.4.8 Addresses

5.4.8.1 To-Be Flow

5.4.8.2 Steps

FR Number FR Description BR Number FR-IB-ELA-44.2 VMStarAccount to Address Rule (Deep): If an Account ID is entered and rule is eligible

to be executed, find its Address Line1, City & Country. Search EBS for other sites that have the same address line 1, City & Country. If found, find the related parties and their related EA‟s. For each EA found, set the „Address Flag‟ to „S‟ (strong).

4.9.1

FR-IB-ELA-44.3 EA Number to Address Rule (Deep): If an EA Number is entered and rule is eligible to be executed, find its related parties and their related sites in EBS. For each site found, find the related Address Line1, City & Country. Search EBS for other sites that have the same address line 1, City & Country. If found, find the related parties and their related EA‟s. For each EA found, set the „Address Flag‟ to „W‟ (weak).

4.9.2

FR-IB-ELA-44.4 From all the EA‟s collected for Address rules, Return unique EA‟s with the „Address Flag‟ strength set to the highest gathered for the EA

4.9.1, 4.9.2

Start

For each EA Provided as input

Find the address line 1 + city + country

Search in EBS for other sites that have exactly

same address line 1 + city + country

Set Address flag as ‘S’ (Strong)

Set Address flag as ‘W’ (Weak)


For each SFDC Account ID Provided

as input

Find the parties and their related sites in

EBSFor every match found, find the related parties and their related EA’s

For each EA found

For each site found, Find other sites that

have the same address line 1 + city

+ country

For every match found, find the related parties and their related EA’s

For each EA found

Eligibility

Eligibility




VMware CONFIDENTIAL

5.4.9 Email Domain

5.4.9.1 To-Be Flow

5.4.9.2 Steps

FR Number FR Description BR Number FR-IB-ELA-45 VMstar Contact Email Domain to EA Rule (Standard): For each Account ID entered and

if the rule is eligible to be executed, get all the associated contacts from VMStar. Remove all contacts with domains like „Gmail‟. Also remove any contacts where the email domain is not occurring more than once. For each remaining contact, find EA‟s in EMS where the contacts email domain is matching the EA‟s primary user email domain. Once an EA is found match the first 8 characters of that EA‟sUCM party normalized name to first 8 characters of any EA‟sUCM party normalized name found so far based on all the rules that have been executed so far. If a match is found, then set the „Contacts Flag‟ to „S‟ (strong) else set the „Contacts Flag‟ to „W‟ (weak).

4.7.1

Start

For each Account ID

entered

Get all associated contacts in

SFDC

Remove contacts with domains like ‘Gmail’ (Eloqua rules) and

contacts that do not share their email domain with

atleast 1 other contact in the list

For each remaining

contact

Yes

Set Email Domain flag as ‘W’ (Weak)

Set Email Domain flag as ‘S’ (Strong)

No

Find EA’s whose primary email

domain is the same as this contacts email domain

First 8 characters of this

EA’s normalized name = First 8 characters of any other EA’s normalized

name

For each EA gathered thru this rule, check against EA’s gathered thru

other rules

Gather all EA’s with appropriate flag.

For each EA found based on all other rules executed till now and the input

parameters provided

No


EA’s normalized name = First 8 characters of any other

EA’s(gathered so far) normalized name

Find other EA’s whose primary email domain is the same as this EA’s primary email domain

For each EA found

Set Email Domain flag as ‘S’ (Strong)

Set Email Domain flag as ‘W’ (Weak)

Find EBS parties where the email domain of any contact (party/

account/ site/ site use level) is the same as

this EA’s primary email domain

For each party find

the related EA

First 8 characters of EBS parties normalized name = First 8

characters of any other EA’s(gathered so far)

normalized name

Yes

No

No

Yes


Account ID entered

Yes Eligibility

Eligibility

Eligibility




VMware CONFIDENTIAL

FR-IB-ELA-45.1 The following Email Domain matching Rules will be applied wherever we need to find target domains for a source domain Strip out everything before the @ sign from the source and target list. If the source domain does not has a „org‟, „edu‟, „net‟, ‟int‟, ‟gov‟ after the last „.‟ (dot) strip out the last dot and any characters after that from the source After all the required characters have been stripped from the source email, use that as the input string. Perform an exact match on the target domain/s after stripping out the last dot and any characters after that as long as the characters after the last dot are not equal to „org‟, „edu‟, „net‟, ‟int‟, ‟gov‟

FR-IB-ELA-46 Next set of rules should be performed for all the EA‟s that have been gathered so far based on all the rules executed and any input EA‟s provided

4.7.2, 4.7.3

FR-IB-ELA-47 EA Primary Email Domain Rule to other EA (Standard): For each EA found so far and if the rule is eligible to be executed, find other EA‟s whose primary contacts email domain

is the same as this EA‟s primary contacts email domainbut exclude EA‟s that have an EA_TYPE of „PERSON‟ from the target EA list For each EA found, check if the first 8 characters of the EA‟s UCM party normalized name matches with the first 8 characters of the EA‟s UCM party normalized name of any of the EA‟s found so far (based on all rules) If it matches, set the strength of the „Email Domain Flag‟ to „S‟ (strong). Else set the „Contacts Flag‟ to „W‟ (weak).

4.7.2

FR-IB-ELA-48 EA Primary Email Domain Rule to EBS parties (Deep): For each EA found so far and if the rule is eligible to be executed, find contacts (Party / Site / Site Uses Level) in EBS that have the same email domain as this EA‟s primary contacts email domain. Based on the contacts find the related EBS parties and their related EA‟s For each EA found, check if the first 8 characters of the EA‟s UCM party normalized name matches with the first 8 characters of the EA‟s UCM party normalized name of any of the EA‟s found so far (based on all rules) If it matches, set the strength of the „Email Domain Flag‟ to „S‟ (strong). Else set the „Contacts Flag‟ to „W‟ (weak).

4.7.3

FR-IB-ELA-48.1 From all the EA‟s collected for Email Domain rules, Return unique EA‟s with the „Email Domain Flag‟ strength set to the highest gathered for the EA

4.7.1, 4.7.2, 4.7.3




VMware CONFIDENTIAL

5.4.10 Company Master

5.4.10.1 To-Be Flow

5.4.10.2 Steps

FR Number FR Description BR Number FR-IB-ELA-48.2 VMstar Account to Company Master Rule (Standard): For each Account ID entered and

if the rule is eligible to be executed, provide the related UUID of the account as the input and check if a match is found based on the business approved VMware hierarchy. If a match is found, retrieve EA‟s for all the records in the hierarchy including the input

4.01

Start

Is the company master match found based on business

approved hierarchy

Set Saved EA flag as ‘W’ (Weak)

Account ID / EA #

Account ID

No

Set Company master flag as ‘S’ (Strong)

Yes


the highest found.

Provide the UUID related to the

Account ID as input to company master

Derive the UUID related to the EA # and provide the UUID’s as input to

company master

EA #

Retrieve unique EA’s for all the records in

the hierarchy including the input

EA

Retrieve unique EA’s for all the records in

the hierarchy including the input EA

Is the company master match found

based on default VMware hierarchy

Yes

End for this record/ begin search for

next recordNo





VMware CONFIDENTIAL

record. Set the „Company Master‟ flag to „S‟ for all of the EA‟s retrieved. If a match is not found, check if a match is found based on the default VMware hierarchy. If found, retrieve EA‟s for all the records in the hierarchy including the input record. Set the „Company Master‟ flag to „W‟ for all of the EA‟s retrieved. If no match is found, process the next record.

FR-IB-ELA-48.3 Next set of rules should be performed for all the EA‟s that have been gathered so far based on all the rules executed

4.02

FR-IB-ELA-48.4 EA Number to Company Master Rule (Standard): For each EA Number entered or gathered based on standard rules and if the rule is eligible to be executed, provide the UUID‟s of the all the sites that are attached to the EA‟s parties. For each UUID, check if a match is found based on the business approved VMware hierarchy. If a match is found, retrieve EA‟s for all the records in the hierarchy including the input record. Set the „Company Master‟ flag to „S‟ for all of the EA‟s retrieved. If a match is not found, check if a match is found based on the default VMware hierarchy. If found, retrieve EA‟s for all the records in the hierarchy including the input record. Set the „Company Master‟ flag to „W‟ for all of the EA‟s retrieved. If no match is found, process the next record.

4.02

FR-IB-ELA-48.5 From all the EA‟s collected for Company mater rules, Return unique EA‟s with the „Company Master‟flag strength set to the highest gathered for the EA

4.01, 4.02




VMware CONFIDENTIAL

5.4.11 Normalized Name

5.4.11.1 To-Be Flow

5.4.11.2 Steps

FR Number FR Description BR Number FR-IB-ELA-48.6 VMstar Account to Normalized Name Rule (Standard): For each Account ID entered and

if the rule is eligible to be executed, find the accounts normalized name. Check if account normalized names is equal to any EA‟s UCM party normalized name. If a match is found add all the EA‟s that have the same UCM party normalized name to the list and set the „Normalized Name‟ flag to „S‟ for all of the EA‟s. If a match is not found, check first 8 characters of the account normalized name is equal to first 8 characters of any other EA‟s UCM party normalized name. If a match is found add all the EA‟s that have the same UCM party normalized name to the list and set the

4.8.1

Start

For each EA found based on all other rules executed till now and the EA’s Provided as input

Find the related SFDC account

normalized name

Set Name flag as ‘S’ (Strong)

Set Name flag as ‘W’ (Weak)

No


For each Account ID Provided as input

Check if any EA's UCM account normalized names =

Normalized SFDC Account name

Find other EA’s that have the same UCM account normalized

name


EA’s UCM account normalized name = First 8 characters of

SFDC account normalized name

YesYes

End

No

Check if Exact match is found based on normalized

names

Yes


EA’s UCM account normalized name = First 8 characters of any other EA’s UCM account

normalized name

No

Yes

EndNo

Eligibility

Eligibility




VMware CONFIDENTIAL

„Normalized Name‟ flag to „W‟ for all of the EA‟s. If no match is found, process the next record.

FR-IB-ELA-48.7 Next set of rules should be performed for all the EA‟s that have been gathered so far based on all the rules executed

4.8.2

FR-IB-ELA-48.8 EA Number to Normalized Name Rule (Standard): For each EA Number entered or gathered based on standard rules and if the rule is eligible to be executed, find other EA‟s that have the same UCM party normalized name. If found, add all the EA‟s that have the same UCM party normalized name to the list and set the „Normalized Name‟ flag to „S‟ for all of the EA‟s. If not found, check if the first 8 characters of the input EA‟s UCM party normalized name is equal to first 8 characters of any other EA‟s UCM party normalized name. If the input EA type is not equal to „PERSON‟ then do not considerEA‟s of the type „PERSON‟ in the target list. However, if the input EA type is equal to „PERSON‟ then consider all EA‟s in the target list. If a match is found add all the EA‟s that have the same UCM party normalized name to the list and set the „Normalized Name‟ flag to „W‟ for all of the EA‟s. If no match is found, process the next record.

4.8.2

FR-IB-ELA-48.9 From all the EA‟s collected for Normalized Name rules, Return unique EA‟s with the „Normalized name‟ flag strength set to the highest gathered for the EA

4.8.1, 4.8.2

5.5 Retrieve and Manage Saved EA Relationships

Wireframe-IB-ELA-14

FR Number FR Description BR Number FR-IB-ELA-49 Saved EA relationships can be accessed by all users that currently have access to the

EA research tool. This will be a second tab on the EA research portal

7.02

FR-IB-ELA-50 User should be able to select either the VMStar Account ID (default) or the EA Number. Once selected they can enter the corresponding value. This can be analpha-numeric value. They can also click on the lookup to search and select the respective values. This is a mandatory value

7.02

FR-IB-ELA-50.1 If the user clicks on the „Lookup‟ button, a new overlay will be opened and will have the 7.02




VMware CONFIDENTIAL

capability to enter a name. The user can enter a wild card „%‟ in beginning and / or the end and will be required to enter a minimum of 3 characters before they can perform the name search. If the user selected „VMStar Account ID‟ before clicking on the lookup then the search will be made for SFDC account names that match the string provided. If the user selected „EA Number‟ before clicking on the lookup then the search will be made for EA names that match the string provided. User will be provided a list of Account / EA name and their respective Account ID / EA Number. User can choose 1 from the list and come back to the main page. The selected Account ID or EA Number will be populated in the value field

FR-IB-ELA-50.2 User should be able to provide a secondary value as additional search criteria. This can either be an Opportunity ID (default) or the Quote ID or Case Number. Once a search criteria is selected, the value column will become an LOV that also allows values to be entered by the user. The value that can be entered can be an alpha-numeric value and should be an existing opportunity ID or quote ID or SFDC case number in the Saved EA relationships table. This is an optional value

7.02

FR-IB-ELA-51 User should be able to select a user profile with which they want to search. By default the users profile should be selected. The list should contain other profiles currently available

7.04

FR-IB-ELA-51.1 The Status, Comments columns should be greyed out (or not displayed at all) and should not be allowed for selection as part of the saved EA relationship search.

7.02

FR-IB-ELA-52 Once an Account ID or EA Number value has been entered the „Show Relationships‟ button is enabled, user should then be able to click on the „Show Relationships‟ button If an Account ID is entered, search for relationships where the primary key is equivalent to the input value and for the profile selected. If an EA Number value is entered, search for relationships that have that EA either as a primary key or even it is part of the relationship and the profile selected. In addition to the above, if a secondary value (opportunity / quote ID / case number) is entered then this also should be used as an „AND‟ condition to the search

7.02




VMware CONFIDENTIAL

Wireframe-IB-ELA-15

FR Number FR Description BR Number FR-IB-ELA-52.1 If multiple relationships exist for the input criteria, then show the list of all relationships.

Primary Key specific (tied only to the Account ID / EA number) will be shown in the „Account Related‟ section and relationships that have a secondary key (Opportunity ID or Quote ID or case number) will be shown in the „Transaction Related‟ section. User should be able to select 1 of them and click on „show selected relationship‟ button to see the results again to see the details of the record selected. If only a single relationship exists thendirectly show the details of the record that match the criteria.

7.02




VMware CONFIDENTIAL

Wireframe-IB-ELA-16

FR Number FR Description BR Number FR-IB-ELA-52.2 All the EA‟s in the relationship along with their attributes and the match criteria will be

shown to the user in the respective categories (strong, probable, and possible) as displayed. This would be similar to the research results.

If any of EA‟s in the saved relationship are no longer active, show the record in grey and hoover over the EA Number / Name will show a message of „EA is no longer Active‟ „Add Accounts‟ , „Delete Selected Accounts‟ , „Save‟ buttons will be shown at the bottom. These buttons are always anchored to the bottom of the window and the user does not have to scroll down to view or act on these buttons. At the same time Status, Comments, Last Updated by and Last Updated Time will also be shown. If this relationship has a secondary key but is not provided as input, then that secondary key will also be shown.

7.02

FR-IB-ELA-52.3 Each EA shown in results section will have a check box available at the end. User can select 1 or more EA‟s using these checkboxes. A select all box would be available at the top which enables the users to select all the

7.02




VMware CONFIDENTIAL

EA‟s. Users should still be able to uncheck or check individual EA‟s as needed. Unchecking the select all box will unselect all current selections including any that were manually selected. This check box will be used to control any Deletions and Show Quotable Assets

FR-IB-ELA-53 User should be able to select 1 or more EA‟s from the results using the check boxes and click on the „Delete Selected Accounts‟ button (only enabled when atleast 1 EA is selected). Clicking on the button will show a confirmation box as a pop-up which has „Confirm‟ and „Cancel‟. Clicking on „Confirm‟ will delete all the EA‟s selected from the results section, but the itself will not be deleted not from the relationships table whereas the cancel or close of the pop-up will not delete the EA‟s from results section and they will continue to be shown in the results

7.02

FR-IB-ELA-54 User should be able to click on the „Add Accounts‟ to add an EA to the list. User will be prompted to enter an EA number value in a new overlay which will also have a Submit and Cancel buttons. Any number entered and submitted will be validated against the active list of EA‟s available in EMS. If an active EA is not found then a message „Entered value is not a valid EA‟ will be displayed. The user should be able to provide a new value if they wish or cancel the add operation. Once a valid EA is found, the overlay is dismissed automatically and the EA will be added to the list under the strong match section but not to the relationships tables. Other composite values of the EA (counties, notes, sites, etc) should also be derived and displayed. Following list of attributes should be available for this record.

1) EA Name 2) EA Number

3) Country(s) - The 2 digit ISO code of countries associated to the EBS party/party sites that make up the EA.

4) Notes – System generated note based additional rules that provide information about the EA (ex : No Active IB, Federal / Personal Account, ELA contract, etc)

5) Sites - Show the number of unique sites (city + country combination) associated to the EBS Parties which make up the EA

6) Customer Domain - For each party associated to the EA find all unique domains that are associated to the contacts in EBS

7) SU Name – Super User Name 8) SU Email Address – Super User Email Address 9) PC Name – Procurement Contact Name 10) SU Email Address – Procurement Contact Email Address 11) Manually Added flag in the match criteria section will be set to „x‟

7.02

FR-IB-ELA-55 Once the selection/s have been made, user can click on the „Show Quotable Assets‟ button (only enabled if atleast 1 EA is selected). Whenever the „Show Quotable Assets‟ is clicked, the BI dashboard will be launched in a separate window (should not ask the user for saving the results). The EA‟s that have been selected in the EA research tool will be passed as parameters to the BI Dashboard. The BI dashboard should not ask the user for an additional sign-on BI Dashboard should take the EA‟s passed as input parameters and show the quotable assets related to these EA‟s by default (without the user clicking on search or other buttons) User should still be able to add or delete EA results in the Saved EA relationships tab and click on the show quotable assets view to launch the BI dashboard for the new set of EA‟s in a new window. They should also be able to go to the EA Research Tool Tab itself and perform additional research if needed.

7.02

FR-IB-ELA-56 If the user clicks on the „Save‟ button (check boxes do not apply in this case and all EA‟s currently shown should be saved), they should be shown an overlay that takes user thru the rest of the save related steps. Requirements laid out in „FR-IB-ELA-33.2‟, „FR-IB-ELA-33.3‟, „FR-IB-ELA-33.4‟ & „FR-IB-ELA-33.5‟ will apply

7.02, 7.05, 7.06




VMware CONFIDENTIAL

All the changes performed so far like Adding of EA‟s, Deletion of EA‟s, Change in relationship status, additions or changesof secondary keys should be committed to the relationship along with the user who submitted the transaction, comments entered, date and time stamp. If a secondary key is provided (new or changed) as part of the save anda relationship doesn‟t exist for the primary key + secondary key + profile combination, then a new EA relationships will be created for the combination and all the EA‟s currently shown to the user will be saved against that unique key combination

FR-IB-ELA-57 Export to CSV should be available as described in FR-IB-ELA-33 7.02

FR-IB-ELA-58 Filter conditions should be available as described in FR-IB-ELA-32 7.02

FR Number FR Description BR Number FR-IB-ELA-59 A „Publish EA list to primary account‟ button will be available in the header section. This

is only enabled if a secondary key is available for the saved EA relationship in the table (not just on UI) When user clicks on the button, an overlay will be shown as detailed below

7.02




VMware CONFIDENTIAL

Wireframe-IB-ELA-17

FR Number FR Description BR Number FR-IB-ELA-60 The top of the overlay will have the following header. „EA‟s from this list will be added to

the primary <<primary key> : <value>> list. These results are then available for any future research related to the primary account‟ „Add to primary list‟ and „Cancel‟ buttons will also be available. If use clicks on „Cancel‟ then user will land back on the Saved EA relationships page. If user clicks on the „Add to primary list‟ button, all the EA‟s that currently exist in this list but are not available in primary list are added to the primary list. The following message is then beshown at the bottom along with a „Close‟ button under the message. „A total of <# of unique EA‟s added to the list> EA‟s were added to the primary <<primary key> : <value>> list.‟ User can click on the „Close‟ button to close the overlay and land on the saved EA relationship page.

7.02

FR-IB-ELA-60.1 All Saved EA relationships that are created specifically for a deal (oppty/quote/case) are those that are created more than 365 days ago will be purged.




VMware CONFIDENTIAL

Any account specific saved EA relationships will not be purged




VMware CONFIDENTIAL

5.6 Application configuration

5.6.1 Setup Rules

Wireframe-IB-ELA-18

FR Number FR Description BR Number FR-IB-ELA-61 A new administration page should be available on the new xELArate portal to a smaller

subset of users. The subsetof users will be derived basedon a new AD group xELArate_Admin that will be maintained by Biz thru existing processes. The admin page will have 2 sections.

1) Setup Rules : Used to setup eligible match rules & reports per profile, Standard / Deep and the rules that will determine an EA‟s category (strong, probable, possible) 2) Setup Profiles. : Used to setup the respective xELA profile based on SFDC profile or an existing AD group.

6.01, 6.02, 6.04

FR-IB-ELA-62 Setup Rules section will have the following details Column 1 will show the header for quotable assets view and all thematching rules that are currently available. If sub-rules exist, then all the sub-rules will be available as some

6.01, 6.04




VMware CONFIDENTIAL

of the configurations are applicable only at the sub-rule level

FR-IB-ELA-63 Column 2 will provide the capability to configure the reports and match rules that are applicable for each profile. The column will be labeled as „Profile Based‟ An LOV will be available at the top which will show all the current available xELArate profiles in an alphabetical order A second LOV will be available next to the header „Quotable Assets View‟ in column 1. This LOV will show all the current available views for quotable assets. The value that is selected will be set for the profile and will be used when the user that is attached to this profile launches the „Show Quotable assets‟ from the research results page or saved EA relationships page Below these, a label „Perform‟ will be shown and under that and next to each match sub-rule or main match rule (if sub-rule is not present) an LOV will be available. This will contain the values „Yes‟ (enabled for the profile) and „No‟ (disabled for the profile). The default value is „Yes‟. Only the match rules / sub-match rules that have an „Yes‟ next to the rule will be applicable / run as part of the EA research for the users attached to the profile.

6.01, 6.04

FR-IB-ELA-64 Column 3 will be labeled as „Generic‟ and the configurations in this section are not based on a profile and are applicable for match rules / sub-match rules. An LOV will be available that corresponds to each match rules / sub-match rules will be available. The values in the LOV will be „Standard‟ and „Deep‟. The default value will be „Standard‟. This setting will then be used to differentiate which match rules / sub-rules will be run if the user selects Standard / Deep on the portal before clicking on the the research.

6.01, 6.04

FR-IB-ELA-65 Column 4 will be labeled as „Categorization Rules‟ and will be used to setup the rules that will be used to group the research results into Strong, probable, possible list. This is a generic rule and not specific for a profile. Users will be able to set the rules for the categories Strong & Probable. Everything that does not fall into this bucket will be categorized into the Possible bucket. Each category can have upto 5 distinct rules (ex : Rule#1, Rule#2) along with the order of execution. One rule will be available as a default and the priority for that is set to 1. Users can add additional rules (total of 5) by using the „Add Rule‟ button. Once the total rules reaches 5, the „Add Rule‟ button will be disabled and will only be re-enabled if one or more rules are deleted. Users can delete a rule by first selecting a rule using the checkbox next to the rule name / number and then clicking on the „Delete Rule‟ button (only enabled if atleast 1 checkbox is selected. All the information related to that rule will be deleted and will no longer be shown to the user. If the user selects all the current rules and clicks on the „Delete Rule‟, user will be shown an error message of „Cannot delete all rules, deselect one of the rules before you proceed.‟.User can close this message to land back on the admin page to make the necessary changes. An LOV will be available that corresponds to each match rule (not for match sub-rule). The list of values will contain „S‟ (strong), „W‟ (weak), „Any‟. The default value will be „Any‟ An Operator field with LOV will be available that corresponds to each rule and will contain the values „And‟ , „Or‟ . Default will be „Or‟. A „Count S‟ (strong) field will be available that corresponds to each rule and will have 2 corresponding fields. 1 will have the values „>‟ (greater than), „<‟ (less than) and „=‟ (equal to). The default for this is „>‟. The 2

nd field is a text box that takes a 2 digit

numeric value. A „Count W‟ (weak) field will be available that corresponds to each rule and will have 2 corresponding fields. 1 will have the values „>‟ (greater than), „<‟ (less than) and „=‟

6.01, 6.04




VMware CONFIDENTIAL

(equal to). The default for this is „>‟. The 2nd

field is a text box that takes a 2 digit numeric value.

FR-IB-ELA-66 The logic for deriving an EA‟s categorization is based on the following logic in the order that is defined below Out of the 2 categories for which the rules are defined, rules related to „Strong‟ will be executed first and then the rules related to „Probable‟ will be executed. Anything that doesn‟t fall into either of the 2 categories will be slotted into the „Possible‟ category. For each category (Strong, Probable) multiple rules can be defined and all rules will be executed in the priority defined until a match is found before moving onto the next rules that are specific for the next category. For each categorization rule, find the corresponding operator („And‟ or „Or‟) and get thematch rules marked with an „S‟ or „W‟. Ignore any match rules that are marked with „Any‟ and if all of them are marked with „Any‟ then directly jump to the step for counting strength. If the operator is „Or‟ then check if the strength that is found by the research for the match rule is the same as defined in the rule. If any of them is the same, then proceed to the next step else move onto the next rule / category If the operator is „And‟ then check if the strength that is found by the research for match rule is the same as defined in the rule. If all of them are the same, then proceed to the next step else move onto the next rule / category Check if a number is defined in the Count S and / or Count W text box. Only account for ones that have a count defined. Count the number of „S‟ or „W” that the research tool found for each EA at the match rule level (not the sub-rule level). If the „S‟ / „W‟ count matches the count (taking into consideration the „>‟ , „=‟, „<‟) definedin the rule , then slot the EA into the category specific for the rule, else move onto the next rule / category

6.01, 6.04

FR-IB-ELA-67 Any changes, additions, deletions are applied to the database only after the „Save Changes‟ button (enabled only if there is atleast 1 change) is clicked by the user, The user that submitted the change along with date/ time stamp of the last change should be tracked in the database.

6.01, 6.04




VMware CONFIDENTIAL

5.6.2 Setup Profiles

Wireframe-IB-ELA-19

FR Number FR Description BR Number FR-IB-ELA-68 „Setup Profiles‟ section will be used to create / maintain the mapping of existing

xELArate profile to an existing SFDC profile or AD group. „SFDC Profile to xELArate profile mapping‟ section will have a „SFDC Profile‟ column wit h a respective LOV. This LOV will have all the existing SFDC profiles. Any additions / changes / deletions to SFDC profiles should be reflected in this LOV.

6.02

FR-IB-ELA-69 User can select one of the existing profiles and the corresponding „xELArate Profile‟ is auto populated. If a value has not been set the then „None‟ will be shown else the corresponding xELArate profile value would be shown. The LOV should contain the following values

Sales

GSS

Renewals

Others

None User can select any of the values from the LOV. User should then be able to select a different SFDC profile at which time the related xELArate profile will be shown and they can make any required changes but the changes done to the previous profile will not be saved until the user specifically clicks on the „Save Changes‟. Note : An initial load of SFDC profile to xELArate profile will be made by IT based on an excel sheet of mappings that Biz creates. Hence the number of changes expected to be done thru the „Setup Profiles‟ section will be minimal.

6.02




VMware CONFIDENTIAL

5.6.3 User Preferences

Wireframe-IB-ELA-20

FR Number FR Description BR Number FR-IB-ELA-70 „User Preferences‟ will be available as a link in the EA research page next to the „Export

Results‟ and „Filter Results‟. A user clicking on the link will be shown an overlay as shown in the wireframe. The overlay will contain 2 sections

1) Select Match Rules 2) Select Filters

6.01

FR-IB-ELA-71 „Select Match Rules‟ will contain all the match rules that are applicable for the users profile. By default all the match rules are selected. User can then de-select some or all of the match rules. They can also select any of the match rules that were previously de-selected and click on the „Save Preferences‟ button to close the overlay. These match rules will be saved for the individual user and will be applied automatically whenever the user sees the EA research results (including the first time they set and the overlay is closed). Only those match rules (columns) that are selected will be shown to the user on the EA research results page Note: The EA research itself will still be done for these rules and the resultant EA‟s will be shown in the appropriate category.

6.01

FR-IB-ELA-72 „Select Filters‟ will contain all the filter conditions that are applicable to ‟Filter Results‟. User can then set one or more filters and click on the „Save Preferences‟ button to close the overlay. The filters that have been set will be saved for the individual user and will be applied automatically whenever the user sees the EA research results (including the first time they set and the overlay is closed).

6.01




VMware CONFIDENTIAL

5.7 Tracking & Omniture Requirements

FR Number FR Description BR Number FR-IB-ELA-73 For each transaction where a user logs into the EA Research Tool, we will need to log

the following 1) User 2) Entry Point ( Ex : VMstar Account, VMstarOppty, BI Dasboard, none) 3) Account ID / EA Number being pre-populated 4) xELArate profile

9.01

FR-IB-ELA-74 Launch context pop-up survey as user is browsing the EA Research Tool and gather feedback.

1) Application administrator should be able to frame specific questions to ask. 2) Application administrator should be able to configure the frequency for which a

survey would pop up to capture in-context feedback.

9.02

FR-IB-ELA-75 As users are searching for EA numbers or Account ID‟s (searching for input parameters) using the VMstar / EA Lookup feature, we will need to track the following

1) User 2) Account ID / EA Number if it is pre-populated 3) xELArate profile 4) The parameter selected(ex : Vmstar Account Name, Order Number, LK, etc) 5) The value provided as parameter

9.03

FR-IB-ELA-76 As users launch the research by clicking on the „Research Accounts‟ button , we need to track the following

1) User 2) Account ID / EA Number if it is pre-populated 3) xELArate profile 4) Additional Account ID‟s / EA Numbers used 5) Research Start Date & Time 6) Results returned in number of seconds 7) Number of results in each category (strong, probable, possible) 8) Number of results that match each rule (Saved EA, Company Master, etc) 9) Total Number of EA‟s returned

9.04, 9.05, 9.06

FR-IB-ELA-77 For the results returned, keep track of the following 1) User 2) Account ID / EA Number if it is pre-populated 3) xELArate profile 4) Filters used (Domain, Country, EA Name, etc) 5) Filter values provided 6) EA‟s added manually 7) EA‟s deleted from the result set 8) EA‟s for which Quotable assets was launched 9) Number of times drill down feature is launched

9.05, 9.07

FR-IB-ELA-78 For the results saved , keep track of the following when the user retrieves a saved relationship

1) User 2) Account ID / EA Number used to retrieve 3) Opportunity / Quote ID used to retrieve 4) xELArate profile 5) Number of times an EA is manually added to the saved list 6) Number of times an EA is manually deleted from the saved list 7) Number of times quotable assets is launched for the saved list

9.08




VMware CONFIDENTIAL

5.8 System Diagrams & Architecture

To-Be Solution Architecture




VMware CONFIDENTIAL




VMware CONFIDENTIAL

5.9 Business Intelligence (BI) & Reporting Requirements (optional)




VMware CONFIDENTIAL

Appendix B: Document Change History

Version No.

Date Name (Alias)

Description of Change

0.3 Jul-15-2013 Ajith Kethireddy

Initial Draft


Added BR Numbers related to each FR

Added Standard or Deep for each rule

Added Architecture diagrams in sections 5.8 & 5.9

Updated wireframe numbers

Added FR for email domain match - FR-IB-ELA-45.1

Updated FR-IB-ELA-33.2, 33.3 and the related wireframe to add the capability of „Case Number‟ as secondary key.

Updated FR-IB-ELA-50.2 and wireframes to include „Case Number‟ as additional input and changed the LOV logic

Updated other FR to include „Case Number‟ as a secondary key.


Updated FR-IB-ELA-33.2 to remove the requirement of validating the quote / opty / case entered.

Added risk related to Address Rule

Added requirement „FR-IB-ELA-60.1‟ for purging deal specific saves after 365 days

Added requirement „FR-IB-ELA-21.1‟ for showing input EA‟s in the output results

Added „Out-of-Scope Requirements‟ section

Added a requirement to the „Assumptions or Constraints‟Section 0.3 Jul-19-2013 Ajith

Kethireddy

Updated „FR-IB-ELA-52.1‟ and its related wireframe to have a new „Show selected relationship‟ button


Updated functional flow related to „Orders‟ rule based on DEV feedback

Updated Order Rules requirements „FR-IB-ELA-39, FR-IB-ELA-39.1, FR-IB-ELA-

40‟ to reflect the right functional flow.

Added BR „6.01‟ to out of scope section


Removed requirement „FR-IB-ELA-21.1‟ as we will never have an input EA that is not part of the results


Created new version

Added Post November requirements section

Added items to Open and Closed Issues 1.0 Aug-23-

2013 Ajith Kethireddy

Updated Email Domain Rule to remove person parties from target list

Updated Normalized Name Rule to remove person parties from target list

Updated the open / closed items section. Current tracking requriments are added to this.

1.0 Sep-18-2013

Ajith Kethireddy

Updated „FR-IB-ELA-08.18‟ to state the right way of deleting therecords selected in the lookup.

Updated „FR-IB-ELA-08.21‟ to state that a new overlay for error message is not required but the message will still be shown in the current lookup overlay

Appendix C: Open and Closed Issues

ID Issue Resolution Owner Target Date Status

1 EA Comments (Notes) - FR-IB-ELA-23.1 - Check if there is atleast 1 active IB associated

This requirement will be delivered for November but historical quotes related

Ram 7/30 Closed




VMware CONFIDENTIAL

to the EA. If not, add the note ‘No Active IB’ to the EA comments field

requirements‘FR-IB-ELA-41.8’, ‘FR-IB-ELA-41.9’, ‘FR-IB-ELA-41.10’ will be pushed out to December release

2 EA Comments (Notes) - FR-IB-ELA-23.1 - If the EA has an ELA contract that is currently active then add the note ‘Active ELA’

This requirement will be delivered for November but historical quotes related requirements ‘FR-IB-ELA-41.8’, ‘FR-IB-ELA-41.9’, ‘FR-IB-ELA-41.10’ will be pushed out to December release

Ram 7/30 Closed

3 EA Comments (Notes) - FR-IB-ELA-23.1 - If the EA has an active contract of the type MCS or BCS, then add the note ‘Active MCS / BCS’

This requirement will be delivered for November but historical quotes related requirements ‘FR-IB-ELA-41.8’, ‘FR-IB-ELA-41.9’, ‘FR-IB-ELA-41.10’ will be pushed out to December release

Ram 7/30 Closed

4 Tracking input criteria (account ID’s or EA numbers) used , parameters used to find input criteria and result counts for each transaction

Portal DEV team to provide feasibility / high level estimate DEV will not be able to provide tracking of specific values with the existing tools (ominiture) and will need to evaluate additionaltools. The evaluation will happen in later timeframe. Biz has raised ‘CR-00049818’ for addressing the tracking of specific valueslike account id and EA numbers. The current commitment to deliver tracking requirements is attached here

7/29 Closed

5 Application to display the data tracked to Admin users

Portal DEV team to provide feasibility / high level estimate This requirement will not be delivered as part of Novemberrelease. This will also need detailed requirement gathering. Biz has raised ‘CR-

00047882’ for tracking this.

7/29 Closed

Omniture tracking requirements.xlsx




VMware CONFIDENTIAL

Appendix D: Glossary/ Definitions

Term Definition

BRD Business Requirements Document. Document developed by business users to submit project requirements to Information Technology (IT).

EMS Entitlement Management System (Database supporting MyVMware)

EBS Enterprise Business System (Oracle)

ELA Enterprise License Agreement.

FRD Functional Requirements Document. Document developed by IT which specifies new applications/functions, or changes to existing applications/functions.

IB Install Base. The EBS module which tracks product serial numbers and the orders/contracts to which they are to be associated.

OEM Original Equipment Manufacturers. A sales channel we use to sell our products through vendors such as HP, Dell, IBM, etc.

OM Order Management. The EBS module which is used to create sales orders.

SC Service Contracts. The EBS module which maintains customer subscription and/or support contract information.

SME Subject Matter Expert

Process Area A business process within the VMware organization that is impacted by the current entitlements model and that is consequently being addressed by the Customer Entitlement Team

Business Capability A parameter within the umbrella of a business process that helps to define one of several activities that occur for that specific process

External User A contact/individual at the customer entity that will have right to use/access the entitlement or customer facing portals.

Internal User A VMware employee accessing internal systems/portals.

Quote Service Contract with the same contract number as the Active Contract, with a new Modifier with “Entered” status

EA Entitlement Accounts – this account is assigned in the EMS.

RTR Real Time Reporting

Entitlement Data Data which generate Install Base or License Entitlement records

Appendix E: Related Documents/References

Document Document Location

IBELA_BRD-EA_ResearchTool_v1.2


Appendix F: Project Team

Name Role

Matt Bingham FAST Solutions

Michael Shields FAST Solutions

Jitendra Dangi FAST Solutions

Sriganesh Subramaniam FAST Solutions

Manjiri Godbole FAST Solutions

Neeraj Kulkarni FAST Solutions




VMware CONFIDENTIAL

Aaron Pinto FAST Solutions

Omanakuttan Namboodiri FAST PMO

Paige Chong FAST PMO

Sandeep Kalkur FAST CSO

Jackie Dummett FAST CSO

Carla Leet FAST BI PM

Abhilash Mallikarjunaradhya FAST BI

David Aguilar FAST BI

Adella Chong FAST ACT

Pablo Castro FAST ACT

Ajith Kethireddy IT_Core

Shelly Sia IT_Core

Shailendra Kalapatapu IT_Core

Alisa Zhang IT_Core

Akshaya Lall IT_Core

Abhishek Padma IT_Core

Ram Mutupuru IT_Core

Joe Faghani IT_Core

Nagar Ramesh IT_Core

Amrish Desai IT_Core

Sujani Andra IT_Core

Srini Kulkarni IT_Core

Nick Seewer IT_Core

Michael Caulfield IT_Core

Sony Korlipara IT_Core

Sunder Vudhya IT_Core

Thirupati Panyala IT_Core

Narayana Ramini IT_Core

Aakanksha Bhardwaj IT_Core

Sanchita Tiwary IT_Core

Ram Mutupuru IT_Core

Sai Chakravarthy IT_Core

Bharat Thosar IT_Core

Hima Satoor IT_Core

Philip Pulimootil IT_Core

Mudit Agarwal IT_Core




VMware CONFIDENTIAL

Appendix G: Review and Sign-off

Below is a list of the required reviewers and approvers:

Name Role Contact Signoff Date

I have carefully assessed the Functional Requirements Document for the (System Name). This document

has been completed in accordance with the requirements of the VMware System Development Life Cycle

methodology. I fully accept the changes as needed improvements and authorize initiation of work to

proceed.

NAME & Signature DATE

IT Sponsor (Director Level or above)


IT Sponsor (Director Level or above)


Business Sponsor (Director Level or above)


Business Stakeholder (Director Level or above)


Business Stakeholder (Director Level or above)


IT Development Manager/Lead

frd x el_arate_ea_researchtool

Technology

ib ela project

ib ela quotes

manual ea research

customer ea relationships

accurate customer ea

research results235

ea lookup tools

setup rules57wireframeib