Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 3 Next »

Search Optifacts User Documentation


Table of Contents (on this page)


Introduction

This document provides instructions for enabling the re-launch function and setting up a system to allow operators to launch a new job by looking up an original job through Quick Lookup or the Quick Lookup View of Archived Jobs.  Note: Re-launch must be configured before jobs will begin storing for later Re-launch and jobs previous to the date that Re-launch is set up will not be available for Re-launch. Tray Track must also be enabled.

Procedure

Custom Configuration

Enable the following custom configuration.

From the Optifacts main menu:

Type 3 – Editor Utilities and press enter.

Type 6 – Configuration Editor and press enter.

Type 6 – Edit Custom Configuration and press enter.

The Custom Configuration Editor displays.

  • Press Q to Query to search if the table you are looking for exists.

If the table does not exist:

  • Type A to add a new record.
  • Enter all the information as shown in the diagram below.
  • Press Escape to save the data.
  • Type E to exit.

Note: The Re-Launch feature can only be utilized on job run through layout starting from the date that the following configuration is enabled. Past jobs cannot be re-launched. Tray Track also needs to be set up.

If the following custom configuration is enabled, you will get asked to enter a tray number when the job is relaunched and we will go through auto lite-ups when the job is being processed.

Route Condition

Set up the following Job Routing Condition required to relaunch a job.

From the Optifacts main menu:

Type 3 - Editor Utilities and press enter.

Type 11- Job Routing Menu and press enter.

Type 9 – Route Conditions Control Editor and press enter.

The Job Routing Condition Control Manager displays.

  • Press Q to Query to search if the table you are looking for exists.

If the table does not exist:

  • Type A to add a new record.
  • Enter all the information as shown in the diagram below.
  • Press Escape to save the data.
  • Type E to exit.

Note: Do not attach this condition to a Destination Site.

Lite-up Controls

Set up lite-up controls to control which lite-ups will be eligible for re-launch.

Example: SUPPLY FRAME may not be appropriate on re-launched jobs, so you can store the OPTI2.8 file without SUPPLY FRAME lit even if it was lit on the original job.

From the RX Transfer Menu:

Type 10 – Route Conditions Lite-Up Editor and press enter.

  • Press Q to Query to search if the table you are looking for exists.

If the table does not exist:

  • Type A to add a new record.
  • Enter all the information as shown in the diagram below.
  • Press Escape to save the data.
  • Type E to exit.

Retail Transfer Field Location

Next you will need to set up the Lens Manufacturer Code in the Field Location Editor to interpret the manufacturer codes that will be stored with archived jobs. 

From the Optifacts Main Menu:

Type 11- Retail Transfer and press Enter.

Type 4 - Editor: Field Location and press Enter.

  • Press Q to Query to search if the table you are looking for exists.

If the table does not exist:

  • Type A to add a new record.
  • Enter all the information as shown in the diagram below.
  • Press Escape to save the data.
  • Type E to exit.

Note: Be sure to fill in the Field Notes, as well as the Starting and Ending Markers that appear in the lower portion of the screen.

Restart Calculations and Translay.

The Calculations Module and Translay program must be re-started.

From the Optifacts Main Menu:

Type 10 - Management Functions and press enter

Type 2 - Check Restart Optifacts Programs and press enter

Note: Only jobs that entered through layout from this point on will be available for re-launch. 


  • No labels