best practices for building mass md maintenance … · best practices for building mass md...
TRANSCRIPT
Best practices for building mass MD
Maintenance Solutions with Winshuttle
Israel Rosales| Winshuttle
WINSHUTTLE USER GROUP CONFERENCE | LAS VEGAS 2016 2
Which minion should you pick?
How many different scripts/templates for the same MD domain?
Too many, isn’t it?
WINSHUTTLE USER GROUP CONFERENCE | LAS VEGAS 2016 4
Problems
Too many excels with too many scripts
No real MD solution tool present
Roundtrip (create, download and modify) but no more
What about good MD mass Excel tools?• Complete and/or atomic operations
• One single Excel file
• AND EASY TO MODIFY (NO FRANKENSCRIPTS!!!)
WINSHUTTLE USER GROUP CONFERENCE | LAS VEGAS 2016 5
Solution (First iteration…)
One single Excel:
With different areas
And different scripts
WINSHUTTLE USER GROUP CONFERENCE | LAS VEGAS 2016 6
Build in short iterations
Steps for creation:
Define the format of the single Excel file
Create all the scripts with mapping according to single Excel file
Testing of each script without publishing
Publish the script
Improve by repeating from step 2 (sometimes 1 if format changes)
WINSHUTTLE USER GROUP CONFERENCE | LAS VEGAS 2016 7
Tips & Tricks
Think about the format and sections of the Excel
• Avoid reworks in Excel and scripts
• Leave blank hidden columns for future new fields
WINSHUTTLE USER GROUP CONFERENCE | LAS VEGAS 2016 8
Tips & Tricks
Perform 99% of the script testing WITHOUT publishing
• Avoid unpublishing and republishing after errors
• More efficient testing in smaller chunks
Create small/atomic scripts, not big scripts
• Easier to test, reuse, change or improve
• DO NOT CREATE A FRANKENSCRIPT!!!FrankenscriptToo ugly to touch
Script 1
Script 2
Script 3
Script 4
Script 2.1
WINSHUTTLE USER GROUP CONFERENCE | LAS VEGAS 2016 9
Tips & Tricks
Perform 99% of the script testing WITHOUT publishing
• Avoid unpublishing and republishing after errors
• More efficient testing in smaller chunks
Create small/atomic scripts, not big scripts
• Easier to test, reuse, change or improve
• DO NOT CREATE A FRANKENSCRIPT!!!Script 1
Script 2
Script 3
Script 4
Script 2.1
FrankenscriptToo ugly to touch
WINSHUTTLE USER GROUP CONFERENCE | LAS VEGAS 2016 10
First improvement
Let’s remove wrong executions by using conditions:
• Columns to control each script:
• Conditioning each script:
WINSHUTTLE USER GROUP CONFERENCE | LAS VEGAS 2016 12
Second improvement
Let’s simplify the interface:
• One single “intelligent” script
• And use of the “Chain scripts” functionality
WINSHUTTLE USER GROUP CONFERENCE | LAS VEGAS 2016 13
Available resources
Winshuttle Solution Accelerators @ Documentation Portal
http://support.winshuttle.com
WINSHUTTLE USER GROUP CONFERENCE | LAS VEGAS 2016 14
Available resources
Winshuttle Solution Accelerators @ Documentation Portal
http://support.winshuttle.com
WINSHUTTLE USER GROUP CONFERENCE | LAS VEGAS 2016 15
Available resources
Accelerators used today:
Bulk Material Management
http://winshuttle-help.s3.amazonaws.com/best-practices/winshuttle-best-practices-design-patterns-bulk-material-management.htm
WINSHUTTLE USER GROUP CONFERENCE | LAS VEGAS 2016 16
Available resources
Winshuttle Solution Accelerators @ Documentation Portal
http://support.winshuttle.com
WINSHUTTLE USER GROUP CONFERENCE | LAS VEGAS 2016 17
Other MD training during the WUG:
Thursday:
2:15 – 3:00 Active Governance of Master Data – An introduction
4:15 – 5:00 How to measure and continuously improve your Winshuttle workflow processes
Friday:
11:45 – 12:30 Updating Multiple Units of Measure – Excel How-To
2:45 – 3:30 Application Data Management versus Master Data Management