nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Risk Register Salesforce2COMIT

stan_koprowski

Update schedule

Risk ID

Risk Description

Likelihood

Project Impact

Risk Rank

Risk Category

Contingency Plan

Risk Trigger

Comment

Site #s not correct in Salesforce

data quality

Are splits handled consistently?

data quality

Global Data Protection Regulation (GDPR)

0.10

Legal / Regulatory

European Regulation becoming law in May 2018

http://it.na.sas.com/prj/GDPR/default.aspx

Personal information as it relates to serial # and shrinkwrap (actually to any personal data)

not an issue if customer clicks the agreement.

Challenge: If customer asks for their information to be removed. Can we show which systems have their information?

ORION monthly updates

Update schedule http://sww.sas.com/gapspt/estars/whats_new/

add salesforce to dependency
notification

INVCURR updates

Add salesforce to dependency
notification

Territory changes

dependency with ORION. Getting changes into the SAS IT queue as soon as possible will be critical

GIDB site assignments

dependency with ORION. Getting changes into the SAS IT queue as soon as possible will be critical

technical prototypes with sandbox environments

0.8

sandbox environments might behave differently from production
Might not have sandbox environments available for all systems

Comments

kathycobb

Hi Stan, This is a great chart! Please add 2 additional risks:

1. Orion has monthly new releases. We need to ensure we can maintain Salesforce2COMIT with enhancements and changes. Here is the link to the Orion Release Dates and Notes: http://sww.sas.com/gapspt/estars/whats_new/

2. INVCURR can have updates and changes made by SAS that can impact JMP but they can forget that JMP uses the system differently and they fail to advise JMP of the changes. For example: earlier this year they made changes to the country makeup of their GEO Divisions so different variables were created which impacted Operations Commissions reporting. Here is a link to the SAS Geography Taxonomy information http://kmc.sas.com/bicc/SAS%20Global%20Standards/Geo/Geography%20Taxonomy.aspx

kathycobb

Hi Stan, please add 2 more risks:

Territory Changes - Operations needs notification as early as possible to request updates from the Orion Team as we are put in a queue with all of the SAS Requests. We do not have any control on how long it can take for updates to occur which will affect the quality of the data.

GIDB Site Assignments - Operations needs notification as early as possible to request updates from the Orion Team as we are put in a queue with all of the SAS Requests. We do not have any control on how long it can take for updates to occur which will affect the quality of the data.

Thanks! Kathy

stan_koprowski

Thanks Kathy,

I added the above risks. And some comments. Depending on your browser you might need to scroll right in the table to see the comments.

Stan