You might also be interested in:

• Measure On-Time Performance Case Study Presentation at MWUG, October 10, 2017
  On-time performance is one of the key ingredients for customer satisfaction and loyalty. Tris Hopkins shares how Carlisle Brake & Friction partnered with 32 Soft to build an online dashboard that uses real-time QAD data to track and analyze delivery performance trends, uncover and measure buried drivers for delays, react quickly to missed shipments, and develop better decisions to reach their targets.
• Additional Webinars

Questions from the webinar

	How do you calculate late delivery and can you change the criteria?
All of our solutions come with in-depth consultation regarding the situations and needs of your company. We work very closely with you to define the criteria that drives the information displayed in the graph and fine-tune it to match what you want to measure in your environment.
	Is the website set up and hosted at my facility?
Yes, it is. The application can also be hosted outside if you prefer. The deployment of the application is very straightforward. If you are using one of the latest versions of QAD, you run the .NET UI application on your tomcat. The dashboard is just another application on the same tomcat, so no extra hardware or software is required.
	Can you address issues in customer schedules where partial shipments are made and how does that accumulate and determine whether the order is early, on-time or late?
It is your team’s decision how you want to interpret and define what is considered on-time or late. We will work with you to define what you want to measure for your environment and will fine-tune the application to your needs.
	Can this be installed on our QAD 2015 EE system?
Yes, this works on any Standard or Enterprise edition.
	Please explain how the Data Loader defines the reason codes. Does it work with actual QAD data or with user defined data fields?
QAD has a Reason Code Maintenance program where you can maintain sets of codes for all kinds of areas. You create a set of codes for on-time performance. Dedicated people will use the Data Loader to classify and assign late reason codes to late orders and upload that data back to the system. These late order records are captured and maintained in a cache table (custom table) outside of standard QAD structure. However, they are accessible through QAD functionality and use a .NET UI browse to query the records. The dashboard has an Excel export function built into the trend graph that can be used to download the details of these late orders for further analysis.

 

Join our mailing list to stay informed about our webinars