Search Optifacts User Documentation

Table of Contents (on this page)

Introduction

This document provides instructions for defining Redo Reasons. Redo reasons are used when a job is entered or relaunched from archive to be redone for warranty, non-adapt or other such reasons. Redo reasons are used in reporting to track redo activity by lab and the reasons for the redo.

Procedure

This is a multi-step process.

Step 1 - Verify that the Lite-ups exist.

From the Optifacts main menu:

Type 11 - Retail Transfer and press enter.

Type 14 - Report: Pricing Options Available and press enter.

The report will display on screen.

Scroll down using the page down or the down arrow key on your keyboard, until you find the Redo lite-ups. (The report is sorted alphabetically)

If you do not see the lite-ups, they will need to be created as follows:

Add/Edit Lite-up Options

From the Optifacts main menu:

Type 3 - Editor Utilities and press enter.

Type 4 - Pricing Database Editor and press enter.

Type 4 - Lite-up Options and press enter.

Type 1 - Add/Edit Lite-up Options and press enter.

The Add/Edit Lite-up Options screen displays.

Valid for (G) Glass, (P) Plastic,or ( * ) Both
- Type ( * ) asterisk for both and press enter.
Enter the lite-up number that you are going to use and press enter.

The screen will expand displaying the rest of the fields.

Enter all the data as shown in the following diagrams pressing enter past each field. We are using Lab Redo as an example. Refer to the Add/Edit Lite-up Options document for full instructions.
Are the Entries Correct (Y/N)?
- Type Y if correct and press enter
- Type N to return to the form.

Step 2 - Setup the Job Data Definition

Refer to the Defining Job Data Definition Fields document for full details on each field. We will show you some examples below, however your lab may have setup other redo reasons that would need to be setup using the same process as we describe below.

From the Optifacts main menu:

Type 3 - Editor Utilities and press enter.

Type 6 - Configuration Editor and press enter.

Type 7 - Edit Job Data Definitions and press enter.

The Prompt Configuration for Miscellaneous Job Related Data window displays.

Type A to add a new record.
Enter all the applicable data as per the diagrams below pressing enter past each field.
Press Escape to save the data.
Press E to exit the screen.

Lab Redo

Dr Redo

Non-Adapt Redo

Warranty Redo

You may also need to setup Warranty Card Info

Step 3 - Setup the Job Data Trigger

Refer to the Defining Job Data Triggers document for full details on each field. We will show you some examples below, however your lab may have setup other redo reasons that would need to be setup using the same process as we describe below.

From the Optifacts main menu:

Type 3 - Editor Utilities and press enter.

Type 6 - Configuration Editor and press enter.

Type 8 - Edit Job Data Triggers and press enter.

The Triggers to Cause Prompts for Miscellaneous Job Related Data window displays.

Type A to add a new record.
Enter all the applicable data as per the diagrams below pressing enter past each field.
Press Escape to save the data.
Press E to exit the screen.

Lab Redo

Dr Redo

Non-Adapt Redo

Warranty

Step 4 - Setup the Master Tray Tracking Stations

From the Optifacts main menu:

Type 7 - Tray Track and press enter.

Type 12 - Tray Track Configuration and press enter.

Type 1 - Master Station Number Setup and press enter.

The Master Station Number Setup screen displays.

Type Q for query.

Step 5 - Setup the Sub-Master Tray Tracking Stations

From the Optifacts main menu:

Type 7 - Tray Track and press enter.

Type 12 - Tray Track Configuration and press enter.

Type 2 - Sub-Master Station Number Setup and press enter.

The Sub-Master Station Number Setup screen displays.

Type Q for query.
Enter REDO REASON in Field Name and press escape to see if already exists.

If the entries exist, they should look like examples below.

If the entries do not exist, press A to add
Enter all the applicable data as per the examples below pressing enter past each field.
Press escape to save the data.
Type E to exit the screen.

The Reasons are setup in levels. The first level being the main reasons for the redo. The second, third, and so forth being another level, option or reason for each previous selections. The last selection needs to be setup as a Reason Description rather than an Option Name to make it the last selection that the operator needs to make.

For example:

In menu level 1, we have setup 4 options: (More options and reasons may be added depending on your need.)

Lab Error
Dr. Redo
Non-Adapt
Warranty

In our example,the operator would see 4 options in the first level: Lab Redo, Dr Redo, Non-Adapt and Warranty. They would make a selection from these options.

Let's say that the operator selected Lab Redo from the 4 available options shown above. We have setup up 4 more options under Lab Redo. This is now level 2 and the operator would make a selection from the 4 options in this level; Edging, Surfacing, Lenses and Frames.

The next step (which would be the last in the hierarchy) is to create the reason descriptions for each Redo Reason Option as shown in the above 4 diagrams.

We will say that the operator has chosen Surfacing from the 4 options and use that as our example. We have setup 3 reason descriptions for the Surfacing option which is now level 3, as shown in the following diagrams.

Once the operator makes a selection from the above 3 reason descriptions, this is the last selection that they will need to make.

Order Entry Redo Process

The following diagrams show the selections that the order entry operator would need to make using the above examples.

From the Pricing Options screen in order entry, they would need to choose the lite-up applicable to the type of Redo being processed. In our example we are using lite-up #77 Lab Redo.