Estimated Delivery Date (EDD) Calculation Explanation

Search Optifacts User Documentation

Table of Contents (on this page)


Introduction

This document explains how the Estimated Delivery Date is calculated and also shows what tables we use.

Procedure

Programs

$CWD/progs/ofdemon (update to use tt_ststop table)

$CWD/progs/edd

$CWD/progs/edd_report

Tables

  1. The edd_acct table is where each account’s cut-off time is entered. Any job coming in after the cut-off time starts counting from the next day.
  2. The edd_cal table is where the lab enters what days and hours they work. The days worked can either be Y (full day), H (half day), or N (don’t work).
  3. The edd_courier table is where each courier’s pickup time gets entered. Any job expected after the pickup time gets 1 day added to the time.
  4. The edd_ctrl table is the control table to find the length of time needed for the lens.
  5. The edd_liteups table is where each lite-up entered gets a length of time needed.
  6. The grp_style table allows you to enter a name set with specific criteria and use that name set in the edd_ctrl table.
  7. The grp_rx table allows you to enter a name set with specific criteria and use that name set in the edd_ctrl table.
  8. The grp_mat table allows you to enter a name set with specific criteria and use that name set in the edd_ctrl table.
  9. The grp_color table allows you to enter a name set with specific criteria and use that name set in the edd_ctrl table.

Where are the Menu Options Located?

From the Optifacts main menu:

Select Option 3 – Editor Utilities and press enter.

Select Option 13 - Estimated Delivery Date and press enter.

Here you have two options, either the editor or reports. 

  • The editor menu has the menus for all of the tables above to use for this project.
  • The reports are on the EDD tables only listed above.

How the Calculation Gets Done

  1. The job gets entered into the system.
  2. Take the entered time and compare it against the cut-off time for this account. If the time is under the cut-off time, start counting the days from today.  If the entered time is above the cut-off time, start counting the days from the next day instead of today.
  3. If there is NO cut-off time for an account, the program will ‘NOT’ continue to estimate the date.
  4. Next, the program goes to the edd_liteup table. It searches through each lite-up the job has turned on and adds the appropriate time for each one. It looks for a specific account entry first and then tries account ‘0’.
  5. Then we go to the edd_ctrl control to see what type of job it is. It starts with the highest number first and works its way down until it finds a match.  It does each eye separately.  Once it finds a match, it looks to see if any lite-ups are in the record.  If there are lite-ups in the entry, and the lite-up is on, it overrides the value from the edd_liteups table.  If it is a split job and the value for each eye is different, the computer selects the longest time. 

Special Note:  The style, material, and color fields use both name sets and regular Optifacts codes.  The program tries to find a group name set first, and if not there, it looks for the regular Optifacts code, and if that fails, it goes to all Optifacts codes.  An example is: ‘SV’ for a Single Vision lens.  The program looks for ‘SV’ as a group name set, and then it looks for ‘SV code,’ and finally, it looks for all style codes.

6. Now that we have the time needed, we go to the calendar to find out the date. The program looks at each day to see if the lab works and finds the estimated date for job completion.

7. Once the date gets found, the program puts a record in the job_data table with the date. This record allows you to print the date on the work ticket and invoice.

The edd_liteups table holds, by account ship-to, the amount of time it takes for each lite-up.  The program first looks at the specific account and then falls back to account ‘0’ for any remaining lite-ups.

The edd_ctrl table controls the rest of the days/time calculations.  The lens specs lines can contain a group name set for that group table, a specific code (like SV or P for lens styles), or an ‘*’ for all.  The lite-ups section is for exceptions to the edd_liteups table.  You can over-ride a date/time from the edd_liteups table that might take longer because of a particular style of lens.  An example is that a flat-top might take 3 days for Crizal, but a single vision might only take 2 days for Crizal.



To view and download these instructions as a PDF file, click on the following document image.

Did you know?...
Optifacts is now utilizing a help-desk ticket system to better serve your emailed support needs and have your requests assigned to a team member that can support you best.
Please consider emailing your support requests to support@optifacts.com rather than individual addresses for more efficient support.
You may also log in to your account at https://rxuniverse.atlassian.net/servicedesk/customer/portal/12 to submit your requests directly and see the status of any currently open tickets your lab may have.
If you are in need of immediate support, please call the support desk directly at (800)  678-4322 during business hours of 8 am to 5 pm CST/CDT, Monday through Friday.  

Optifacts, Inc.   Suite 100 - 18 Riverside Ave. S.   Sartell MN 56377

Phone: (800) 378-4322   Phone: (320) 258-3559   Fax: (320) 258-3880

Email: sales@olsssystems.com   Email: support@optifacts.com

Optifacts Service Desk: http://support.optifacts.com 
Click Here to Find Out More About Us