Minutes Week 40 06-October

stan_koprowski

Meeting Information

Date:  October 06, 2017

Time: 9:00-10:00 AM EST

Location: T4092

When it's time,  join the meeting

Meeting number (access code): 596 321 016
Meeting password: SX5PD33k

Invited Attendees:  Core Team (9 members)

• Todd Hoffman
• Tina DuBois
• Stan Koprowski
• Jeff Perkinson
• Ashley Prince
• Kathy Cobb
• Carol Gretz
• Jon Weisz
• Antoine Smith
• Deb Thompson

Happenings since Last Status Meeting

Team—

• Antoine and Tina confirmed changes created in Test environment can be promoted to
   Production environment
• Work order for D-Wise signed.  Contract dates valid until 12-31-17. Contract has 160 hours available.
• Request for new field in ORION-- Field Name: JOI, Data Type: Character, Length:18 was not granted.  Need to capture ORION opportunity id in SFDC.
• ORION API can accept attachments to notes field. Need to pull files to be used as attachments from SFDC.  DWise to create an API call to fulfill requirement.
• ORION team would like meet to discuss relaxing fields currently required by API that have default values, such as Contact ID (Stan will schedule after Discovery Summit).Class Diagram

   

ACTION ITEMS

Action Item	Responsible(s)	Due Date	Comments	Status
identify sales credit process to ensure SFDC in sync with Invoice Cur	Carol		This needs additional details on intention behind request. Not sure if I scribed this action item properly.  Thoughts??	New
Identify process for JMP with respect to systems of record-- SITE ID Territory ID (Source: suggestion to use SAS data set on one-drive that updates ORION and GIDB with changes?? Account Name	Antoine / Tina / Carol			New
Review feasibility of auto-naming string for account name based on four (4) existing SFDC fields Account name Quantity Product Offering Opportunity Type				New
Develop SAS program to copy all current account names to AKA names overwriting any existing AKA names If account name matches AKA name lock record, otherwise update Opportunity strings in local language	Antoine / JonW			New
Review SAS program flow and logic pertaining to territory mapping	Antoine / Jon W			New
Identify any tasks, effort needed and update project plan as necessary	Stan			New
Find definition of GIDB site. What makes up a site? What is an account? What is a contract?	Carol / Kathy			New
Demo upgrade process and mark it as closed won to demonstrate what happens in SFDC?	Tina	10/13?		New
D-Wise work order: modify begin and end dates  arrange for support / maintenance of macros / APIs	Antoine / Stan			New
Review GIDB data dictionary items with SFDC Identify 10 data fields that will be used to overwrite SFDC data fields Flow chart use cases notify process cancelled sites assess impact and risks	Antoine / Tina / Stan			New

 

Upcoming Milestones

• Review options for promotion of SFDC test changes to production environment
• Begin development of API to handle attachments.  All standard upgrade opportunities will require attachments.

• Kick-off the week of Jan 15, 2018--worldwide JMP process?  

  Target: January 14, 2018 

  Deadline: January 5, 2018 demo of it working in sandbox, fully tested, included in demo is US, Malaysia, Japan, China

Open Issues

 

Action Item	Responsible(s)	Due Date	Comments	Status
Set up SFDC development sandbox environment accounts for: D-Wise Stan Koprowski Jeff Perkinson	Antoine / Tina			Open
Set up SFDC test environment accounts for: Kathy Cobb Ashley Prince Stan Koprowski Jeff Perkinson	Antoine / Tina			Open

 

Upcoming Events

• Work session--Continue to write test cases
• Work session--SFDC data discussion, task and effort planning

New Issues/Action Items

Tina: Send note to JMP staff letting them know we are modifying the default sites and moving  
         any existing site to the AKA site. Copy account name to AKA name based on site id when  
         one to one match of names.  Duplicates should be fixed by account owner. Antoine noted
        that 29 outside of US are duplicates and <100 within the US are duplicates.

Logic:

• if GIDB account you cannot edit the site #
• Lock siteid # so it is not editable.  

Future: Only editable by Business Operations and SFDC data managers

Validation rule:  not able to make closed as won on non-GIDB account

Scenario:

• account has been validated and an existing account is available For example, a customer that has analytics Pro and they now want to buy JMP they won’t have a site because they don’t have an account

A discussion around account validation and timing of when it occurs.

SFDC is matching to DUNS #; not accepted

"...shared responsibilities is no responsibilities."

Salespeople create an opportunity and validate account with ORION. Salespeople have read-only account in ORION

account validation

ID

which stage is account clean-up occurring?

stage 4?

stage 5: asks for paperwork; do not mark as closed until invoice is paid

commissions sitting in a SAS data set on a SAS server backed up daily; sales people have no visibility into it.  No change process available with commission reporting in ordinate amount of time spent on calculations of commissions.  Need clear feedback mechanism of who should know the account and who should know the deal? invoicing to paying. 

commission part is desperately needed

validate account

setinitname 

Clean if name is not in SFDC

Allow edit of AKA field name to be editable after being locked

SAS thinks of an account with many sites and many MLAs. A site is generally the product but not always. A satellite account is where users are located for the licensed product. 

 

Related entities?

• setinit# 
• Product offering
• operating system (OS)
• SID
• DUNS #
• supplement

System of record is GIDB currently matching on DUNS number

• develop relational models for account, contract, and site

Project related--

Reminder to everyone to continue to add documents and post questions to the pertinent board as needed.