QAD .NET UI – Keeping it Simple

1. QAD .NET UI – Keeping it Simple Stacy Elwood, BravePoint (with help from Bart Wardzinski, Lear Corporation) MWUG March 2010

2. Agenda • Introduction • Top Business Challenges • Process Maps • Browses • Browse Collections • Simplified/Configured Screens • Q & A • Next Steps

3. Implementing Common or Standard Processes The “Need for Speed” Knowledge Attrition Maintaining Data Integrity Staying current Budget Top Business Challenges

4. Process Maps Browses Browse Collections Simplified/Configured Screens How Lear and other companies are meeting these challenges with QAD .NET UI

5. Process Maps What they are: Visual process displays Contain links to necessary screens or reports Contain links to training materials Benefits: Reduce training time Promote common “ways of working” Promote enforcement of disciplines Daily tasks, weekly tasks, monthly tasks Ability to share “the big picture”

6. Example #1: Generic process maps Sample of a QAD provided “top level” map

7. Example #2: Lear’s “Roles Based” approach • Roles Based Process Map MAIN MENU • This MAIN MENU appears when users sign on • OBJECTIVE: Organize the process maps and tasks (daily, weekly, monthly, as-needed) into a Roles based format • BENEFIT: Reinforces training and reduces time searching for procedures related to business process

8. Example #3: Roles for functional areas Goal is to promote discipline by clearly showing “regular” tasks Daily task, weekly tasks , monthly tasks , and “as-needed” tasks

9. Example #4: Daily tasks for customer service Objective List the tasks (left hand column) Show boxes for each step Provide links to training materials Task Steps to accomplish each task Training …. TOOL Tip function to show brief text describing option

10. Swimlane objectives Show tasks done by multiple people Show sequence of tasks Show “hand-off” to next person Example #5: Applying the swimlane concept Additional Lear objective Reduce training time Links to training materials Links to potential problems

11. Links to training materials on Process Maps Objectives: Provide links to short, “task specific” training materials Provide training on potential problems to watch for

12. Browses Problem: Too many custom reports; too much paper Large portion of custom code is for reports Too many “ream size” reports Solution: Use Browses in place of reports Benefits for IT Single browse can replace multiple reports Benefits for users Ability to sort, filter, hide data Single click dump to Excel or PDF Higher productivity (less re-typing) More efficient to view data in electronic form “One Click” to update or correct the data

13. Browse – sample • Single browse can replace multiple reports (sorts, criteria, etc) • Single click extract to Excel and PDF • More efficient to review data on screen than printed (reduce re-typing) • One click go to update or correct the data

14. Browse Collections What they are: Browses linked together on one screen Benefits: Shows all the relevant data on the same screen Quick ‘drill-down’ to related information Create one version of the truth

15. Simplified/Configured Screens What they are: Screens tailored to match your business process Benefits: Fields that are not used can be hidden to save keystrokes Fields can be required Different templates allow sensitive information to be controlled by user group

16. Questions?

17. Keep everything in one place IT has fewer “one-off” requests to handle Share information Streamline your business Next Steps – Keep it Simple (KISS)

18. Thank You! Stacy Elwood selwood@bravepoint.com