Minutes Week 39 29-September

stan_koprowski

 

Meeting Information

Date:  September 29, 2017

Time: 9:00-10:00 AM EST

Location: T4092

When it's time,  join the meeting

Meeting number (access code): 595 417 823

Meeting password: 6qQcZn58

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

• Kathy Cobb, Ashley Prince and Stan met multiple times to continue developing the business use cases related to upgrades. 
• Tina and Antoine have started to make some updates to Salesforce to accomodate the changes necessary to push standard paperwork upgrade opportunities to ORION COMIT. 
• Antoine and Stan have started working through the program files provided by D-Wise which utilize HTTP requests from SFDC and ORION

Upcoming Milestones

• Review options for promotion of SFDC test changes to production environment
• Modify Work order for D-Wise

Open Issues

How to gather requirements for Japan, Asia Pacific and rest of world?

 

Upcoming Event

Work session--BUC standard paperwork, BUC non-standard paperwork, BUC EIS Upgrade PO, scenario and user story sessions

Work session--SFDC data discussion, task and effort planning

  

New Issues/Action Items

Team—

• Discussion around the movement of changes from various SFDC environments.  SFDC sandbox environments contain cut of production data.  Need to ensure changes created in Test can be promoted to production.
• Discussion on site id, territory id, and account names and which systems would be used for the systems of record.
• Stan shared a quick review of the existing SAS macros and HTTP requests from SFDC
• Tina shared some tasks and efforts that would be required by SFDC to accoomodate new data items and changes
• Tina shared a prototype of how related sites for an single DUNS account could be managed in SFDC

Action Items:

1. Antoine / Tina: review options for promotion of changes from SFDC Test to SFDC Production
2. Antoine / Tina: set up SFDC development sandbox environment accounts for:
   • D-Wise
   • Stan Koprowski
   • Jeff Perkinson
3. Antoine / Tina: set up SFDC test environment accounts for:
   • Kathy Cobb
   • Ashley Prince
   • Stan Koprowski
   • Jeff Perkinson
4. Invoice Cur:  Carol to identify sales credit process to ensure SFDC in sync with Invoice Cur.  This needs additional details on intention behind request. Not sure if I scribed this action item properly.  Thoughts??
5. Antoine / Tina/ Carol: 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
6. Review feasibility of auto-naming string for account name based on four (4) existing SFDC fields
   • Account name
   • Quantity
   • Product Offering
   • Opportunity Type
7. Antoine / JonW: 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
8. Antoine / Jon W: review SAS program flow and logic pertaining to territory mapping
9. Stan: Request new field in ORION-- Field Name: JOI, Data Type: Character, Length:18
10. Stan: Identify any tasks, effort needed and update project plan as necessary
11. Ashley / Kathy: Continue to identify data quality checks pertaining to upgrade BUCs
12. Antoine / Stan: D-Wise work order:
    • modify begin and end dates 
    • arrange for support / maintenance of macros / APIs
13. Antoine/Tina/Stan: 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

Project related--

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