Search Optifacts User Documentation
Table of Contents (on this page)
Introduction
This document provides instructions for printing production process flags on the work ticket.
Procedure
Coming soon.....
To identify production processes for a job, the appropriate Job Routing Reasons or Group Controls and Track Stages need to be entered and met, and a Custom Configuration setting needs to be enabled.
.
.
.
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 to display the Custom Configuration Editor window.
- Type “A” to add a new record.
- Fill in all the information as per the example below pressing enter after each field.
Enable the following Custom configuration.
PERFORM: Query Next Previous View Add Update Remove Table Screen ...
Searches the active database table. ** 1: cust_cfg table**
CUSTOM CONFIGURATION EDITOR
--------------------------------------------------
Calling Program: [LAYOUT ]
Field Name: [SAVE GROUP NAMES ]
Enabled: [Y]
Character Setting:
[ ]
Float Setting: [ ]
Integer Setting: [ ]
Comment: [Saves Group Names from Routing in job_data table. ]
- Press Escape to save the data
- Type E to exit.
Group Controls
From the Optifacts main menu:
- Type 3 – Editor Utilities and press enter.
- Type 11 – Job Routing Menu and press enter.
- Type 14 – Group Control Menu and press enter to display the Optifacts Group Control Menu.
- Using options 4 through 11 on this menu, set up groups of accounts, materials, styles, lite-ups, colors, etc, and then use the Group Control Editor to assign them to a Group Name.
┌─────────────────────────────────────────┐
│ OPTIFACTS │
│ GROUP CONTROL MENU │
│─────────────────────────────────────────│
│ │
│ 1) User Definition Table. │
│ 2) Group Control Editor. │
│ 3) Add New Name Set. │
│ 4) Group Account Table. │
│ 5) Group Frame Table. │
│ 6) Group Rx Table. │
│ 7) Group Lite Ups Table. │
│ 8) Group Style Table. │
│ 9) Group Material Table. │
│ 10) Group Color Table. │
│ 11) Coat Codes Table. │
│ 12) Exit to Menu. │
│ │
│ Select Option: [ ] │
│ │
└─────────────────────────────────────────┘
Menu Option 2 - Group Control Editor
The important field to note is the Control Name Set which will be used in the Track Stages Editor. Again, this name set will need to start with the letters “PF” to indicate it is a Product Family with Production Processes. Please note: Only one Product Family can be assigned to a lens at a time. Many groups and stages can be assigned to a job, but only one can start with the letters “PF” in order for it to print on the work ticket.
PERFORM: Query Next Previous View Add Update Remove Table Screen ...
Shows the next page of the form. ** 1: grp_ctrl table**
Control Name Set [PF GLASS] Priority [999760 ]
Table 1 [grp_mat ]
Table 1 Name Set [GLASS ]
Not 1 Name Set [ ] AND/OR [AND]
Table 2 [grp_style ]
Table 2 Name Set [SEMIFIN ]
Not 2 Name Set [ ] AND/OR [ ]
Parenthesis around Name Set 1 and Name Set 2 [ ]
Table 3 [grp_color ]
Table 3 Name Set [WHITE ]
Not 3 Name Set [ ] AND/OR [ ]
Parenthesis around Name Set 2 and Name Set 3 [ ]
Job Routing Reasons
From the Optifacts Main Menu:
- Type 3 – Editor Utilities and press enter.
- Type 11 – Job Routing Menu and press enter.
- Type 8 – Route Reason and Control Editor and press enter to display the Job Routing Reason and Control Editor window.
- Type “A” to add a new record.
Enter in the reasons you want to route the job to the track stages. The important field to note here is the Group Name Set which matches the Control Name set in the Group Control Editor. This will be used in the Track Stages Editor. . For a group to be considered a definition for a Production Process, the Group Name Set will need to start with the letters “PF” to indicate that it is for a Product Family. Any other combination of letters and numbers are allowed after the “PF” indicator.
PERFORM: Query Next Previous View Add Update Remove Table Screen ...
Adds a row to the active database table. ** 1: rte_mgr table**
JOB ROUTING REASON AND CONTROL MANAGER
Priority: [999750 ]
Origination Site ID: [ ] Group Trigger 1: [ ]
Condition ID: [GLASS ] Group Trigger 2: [ ]
Destination Site ID: [ ] Group Name Set: [PF GLASS ]
Comments: [ ]
Commercial Brand Name: [ ]
Lite-Up (num): [ ] [ ] (Lite-ups: NOT the number viewed on screen)
Lite-Up (bit): [ ] [ ] (Lite-ups: NOT the number viewed on screen)
Fld Name frm Job Def: [ ]
Fld Value for Fld Name: [ ]
[ ]
Uncut: [ ] Company Code: [ ]
Finished Only: [ ] Branch Code: [ ]
Industrial: [ ] Territory Code: [ ]
Account Number: [ ]
Ship-To Code: [ ]
- Press Escape to save the data.
- Type “E” to exit.
Track Stages
The Group Name (starting with “PF”) used in the Job Routing Reasons will be used in the “GROUP NAME” field in this table. There are two levels: Stages and Steps. Each Group can have more than one Stage and each Stage can have more than one Step. If the job should be stopped and warned if not following the stages/steps in order, “Required” should be set to ‘Y’, otherwise set to ‘N’.
From the Optifacts Main Menu:
- Type 7 – Tray Track and press enter.
- Type 12 – Tray Track configuration and press enter.
- Type 11 - Track Stages Editor and press enter to display the Configure Track Stop Stages window.
- Type “A” to add a new record.
PERFORM: Query Next Previous View Add Update Remove Table Screen ...
Searches the active database table. ** 1: tt_stages table**
CONFIGURE TRACK STOP STAGES
GROUP NAME: [ ]
---------------------------------------------------------------
Stage: Number: [ ] Required (Y/N): [ ]
Name: [ ]
Time: [ ] Cost: [ ]
---------------------------------------------------------------
Step: Number: [ ] Required (Y/N): [ ]
Name: [ ]
Time: [ ] Cost: [ ]
---------------------------------------------------------------
Track Station: [ ]
---------------------------------------------------------------
- First decide which stages need controls.
Example: Glass Jobs
- Should first go through Surfacing.
- Then should go through Inspection.
- Then should go through AR Coating.
- Then should go through the Out Coating station.
- Then should go through the Frame Received Station.
- Then should go through the Edging Process.
The following examples show the various stages and steps that a job could go through.
PERFORM: Query Next Previous View Add Update Remove Table Screen ...
Shows the next row in the Current List. ** 1: tt_stages table**
CONFIGURE TRACK STOP STAGES
GROUP NAME: [GLASS ]
---------------------------------------------------------------
Stage: Number: [1 ] Required (Y/N): [Y]
Name: [SURFACING ]
Time: [10 ] Cost: [2.5 ]
---------------------------------------------------------------
Step: Number: [1 ] Required (Y/N): [Y]
Name: [BLOCKER ]
Time: [2 ] Cost: [2.0 ]
---------------------------------------------------------------
Track Station: [1011 ] BLOCKER
---------------------------------------------------------------
PERFORM: Query Next Previous View Add Update Remove Table Screen ...
Shows the next row in the Current List. ** 1: tt_stages table**
CONFIGURE TRACK STOP STAGES
GROUP NAME: [GLASS ]
---------------------------------------------------------------
Stage: Number: [1 ] Required (Y/N): [Y]
Name: [SURFACING ]
Time: [10 ] Cost: [2.5 ]
---------------------------------------------------------------
Step: Number: [2 ] Required (Y/N): [Y]
Name: [GENERATOR ]
Time: [8 ] Cost: [0.5 ]
---------------------------------------------------------------
Track Station: [2010 ] GENERATOR
---------------------------------------------------------------
PERFORM: Query Next Previous View Add Update Remove Table Screen ...
Shows the next row in the Current List. ** 1: tt_stages table**
CONFIGURE TRACK STOP STAGES
GROUP NAME: [GLASS ]
---------------------------------------------------------------
Stage: Number: [1 ] Required (Y/N): [Y]
Name: [SURFACING ]
Time: [ ] Cost: [ ]
---------------------------------------------------------------
Step: Number: [3 ] Required (Y/N): [Y]
Name: [INSPECTION ]
Time: [ ] Cost: [ ]
---------------------------------------------------------------
Track Station: [2011 ] QA SURFACING
---------------------------------------------------------------
PERFORM: Query Next Previous View Add Update Remove Table Screen ...
Shows the next row in the Current List. ** 1: tt_stages table**
CONFIGURE TRACK STOP STAGES
GROUP NAME: [GLASS ]
---------------------------------------------------------------
Stage: Number: [1 ] Required (Y/N): [Y]
Name: [SURFACING ]
Time: [ ] Cost: [ ]
---------------------------------------------------------------
Step: Number: [4 ] Required (Y/N): [Y]
Name: [OUT SURFACING ]
Time: [ ] Cost: [ ]
---------------------------------------------------------------
Track Station: [2012 ] OUT SURFACING
---------------------------------------------------------------
PERFORM: Query Next Previous View Add Update Remove Table Screen ...
Shows the next row in the Current List. ** 1: tt_stages table**
CONFIGURE TRACK STOP STAGES
GROUP NAME: [GLASS ]
---------------------------------------------------------------
Stage: Number: [2 ] Required (Y/N): [Y]
Name: [AR COATING ]
Time: [ ] Cost: [ ]
---------------------------------------------------------------
Step: Number: [1 ] Required (Y/N): [Y]
Name: [AR COATING ]
Time: [ ] Cost: [ ]
---------------------------------------------------------------
Track Station: [2510 ] AR COATING
---------------------------------------------------------------
PERFORM: Query Next Previous View Add Update Remove Table Screen ...
Shows the next row in the Current List. ** 1: tt_stages table**
CONFIGURE TRACK STOP STAGES
GROUP NAME: [GLASS ]
---------------------------------------------------------------
Stage: Number: [2 ] Required (Y/N): [Y]
Name: [AR COATING ]
Time: [ ] Cost: [ ]
---------------------------------------------------------------
Step: Number: [2 ] Required (Y/N): [Y]
Name: [INSPECTION ]
Time: [ ] Cost: [ ]
---------------------------------------------------------------
Track Station: [2511 ] QA AR COATING
---------------------------------------------------------------
PERFORM: Query Next Previous View Add Update Remove Table Screen ...
Shows the next row in the Current List. ** 1: tt_stages table**
CONFIGURE TRACK STOP STAGES
GROUP NAME: [GLASS ]
---------------------------------------------------------------
Stage: Number: [2 ] Required (Y/N): [Y]
Name: [AR COATING ]
Time: [ ] Cost: [ ]
---------------------------------------------------------------
Step: Number: [3 ] Required (Y/N): [Y]
Name: [OUT COATING ]
Time: [ ] Cost: [ ]
---------------------------------------------------------------
Track Station: [2512 ] OUT AR COATING
---------------------------------------------------------------
PERFORM: Query Next Previous View Add Update Remove Table Screen ...
Shows the next row in the Current List. ** 1: tt_stages table**
CONFIGURE TRACK STOP STAGES
GROUP NAME: [GLASS ]
---------------------------------------------------------------
Stage: Number: [3 ] Required (Y/N): [Y]
Name: [FRAME ]
Time: [ ] Cost: [ ]
---------------------------------------------------------------
Step: Number: [1 ] Required (Y/N): [Y]
Name: [FRAME DEPT ]
Time: [ ] Cost: [ ]
---------------------------------------------------------------
Track Station: [2610 ] FRAME REC’D
---------------------------------------------------------------
PERFORM: Query Next Previous View Add Update Remove Table Screen ...
Shows the next row in the Current List. ** 1: tt_stages table**
CONFIGURE TRACK STOP STAGES
GROUP NAME: [GLASS ]
---------------------------------------------------------------
Stage: Number: [4 ] Required (Y/N): [Y]
Name: [EDGING ]
Time: [ ] Cost: [ ]
---------------------------------------------------------------
Step: Number: [1 ] Required (Y/N): [Y]
Name: [TRACING ]
Time: [ ] Cost: [ ]
---------------------------------------------------------------
Track Station: [2810 ] TRACER
---------------------------------------------------------------
PERFORM: Query Next Previous View Add Update Remove Table Screen ...
Shows the next row in the Current List. ** 1: tt_stages table**
CONFIGURE TRACK STOP STAGES
GROUP NAME: [GLASS ]
---------------------------------------------------------------
Stage: Number: [4 ] Required (Y/N): [Y]
Name: [EDGING ]
Time: [ ] Cost: [ ]
---------------------------------------------------------------
Step: Number: [2 ] Required (Y/N): [Y]
Name: [LAYOUT ]
Time: [ ] Cost: [ ]
---------------------------------------------------------------
Track Station: [2811 ] LAYOUT
---------------------------------------------------------------
QUERY: ESCAPE queries. INTERRUPT discards query. ARROW keys move cursor.
Searches the active database table. ** 1: tt_stages table**
CONFIGURE TRACK STOP STAGES
GROUP NAME: [GLASS ]
---------------------------------------------------------------
Stage: Number: [4 ] Required (Y/N): [Y]
Name: [EDGING ]
Time: [ ] Cost: [ ]
---------------------------------------------------------------
Step: Number: [3 ] Required (Y/N): [Y]
Name: [EDGER ]
Time: [ ] Cost: [ ]
---------------------------------------------------------------
Track Station: [2812 ] EDGER
---------------------------------------------------------------
PERFORM: Query Next Previous View Add Update Remove Table Screen ...
Shows the next row in the Current List. ** 1: tt_stages table**
CONFIGURE TRACK STOP STAGES
GROUP NAME: [GLASS ]
---------------------------------------------------------------
Stage: Number: [5 ] Required (Y/N): [Y]
Name: [INSPECTION ]
Time: [ ] Cost: [ ]
---------------------------------------------------------------
Step: Number: [1 ] Required (Y/N): [Y]
Name: [INSPECTION ]
Time: [ ] Cost: [ ]
---------------------------------------------------------------
Track Station: [2900 ] QA FINISHING
If there is more than one tray track station that will complete the step required (example: more than one edger), it can be added as an identical record with just the station number changed.
ADD: ESCAPE adds new data. INTERRUPT discards it. ARROW keys move cursor.
Adds new data to the active database table. ** 1: tt_stages table**
CONFIGURE TRACK STOP STAGES
GROUP NAME: [GLASS ]
---------------------------------------------------------------
Stage: Number: [4 ] Required (Y/N): [Y]
Name: [EDGING ]
Time: [ ] Cost: [ ]
---------------------------------------------------------------
Step: Number: [3 ] Required (Y/N): [Y]
Name: [EDGING ]
Time: [ ] Cost: [ ]
---------------------------------------------------------------
Track Station: [2812 ] EDGER
---------------------------------------------------------------
ADD: ESCAPE adds new data. INTERRUPT discards it. ARROW keys move cursor.
Adds new data to the active database table. ** 1: tt_stages table**
CONFIGURE TRACK STOP STAGES
GROUP NAME: [GLASS ]
---------------------------------------------------------------
Stage: Number: [4 ] Required (Y/N): [Y]
Name: [EDGING ]
Time: [ ] Cost: [ ]
---------------------------------------------------------------
Step: Number: [3 ] Required (Y/N): [Y]
Name: [EDGING ]
Time: [ ] Cost: [ ]
---------------------------------------------------------------
Track Station: [2820 ] EDGER
---------------------------------------------------------------
These are the fields that are used for the Production Processes:
The Stage Number is the Sort Order which indicates what order the processes will print on the RX work ticket.
QUERY: ESCAPE queries. INTERRUPT discards query. ARROW keys move cursor.
Searches the active database table. ** 1: tt_stages table**
CONFIGURE TRACK STOP STAGES
GROUP NAME: [PF GLASS ]
---------------------------------------------------------------
Stage: Number: [1 ] Required (Y/N): [Y]
Name: [SURFACING ]
Time: [ ] Cost: [ ]
---------------------------------------------------------------
Step: Number: [1 ] Required (Y/N): [Y]
Name: [S ]
Time: [ ] Cost: [ ]
---------------------------------------------------------------
Track Station: [2010 ] SURFACING
---------------------------------------------------------------
The Stage Name will not print, but can be used as a descriptor for this record.
PERFORM: Query Next Previous View Add Update Remove Table Screen ...
Shows the next row in the Current List. ** 1: tt_stages table**
CONFIGURE TRACK STOP STAGES
GROUP NAME: [PF GLASS ]
---------------------------------------------------------------
Stage: Number: [2 ] Required (Y/N): [Y]
Name: [AR COATING ]
Time: [ ] Cost: [ ]
---------------------------------------------------------------
Step: Number: [2 ] Required (Y/N): [Y]
Name: [A ]
Time: [ ] Cost: [ ]
---------------------------------------------------------------
Track Station: [2510 ] AR COATING
---------------------------------------------------------------
The Step Number is not used but can also be used as a descriptor for this record.
QUERY: ESCAPE queries. INTERRUPT discards query. ARROW keys move cursor.
Searches the active database table. ** 1: tt_stages table**
CONFIGURE TRACK STOP STAGES
GROUP NAME: [PF GLASS ]
---------------------------------------------------------------
Stage: Number: [4 ] Required (Y/N): [Y]
Name: [EDGING ]
Time: [ ] Cost: [ ]
---------------------------------------------------------------
Step: Number: [4 ] Required (Y/N): [Y]
Name: [E ]
Time: [ ] Cost: [ ]
---------------------------------------------------------------
Track Station: [2812 ] EDGER
---------------------------------------------------------------
The Step Name is the code that is used to print on the work ticket.
QUERY: ESCAPE queries. INTERRUPT discards query. ARROW keys move cursor.
Searches the active database table. ** 1: tt_stages table**
CONFIGURE TRACK STOP STAGES
GROUP NAME: [PF GLASS ]
---------------------------------------------------------------
Stage: Number: [5 ] Required (Y/N): [Y]
Name: [INSPECTION ]
Time: [ ] Cost: [ ]
---------------------------------------------------------------
Step: Number: [5 ] Required (Y/N): [Y]
Name: [I ]
Time: [ ] Cost: [ ]
---------------------------------------------------------------
Track Station: [2900 ]
---------------------------------------------------------------
Example:
For a job assigned to the group PF GLASS, it would use these records.
QUERY: ESCAPE queries. INTERRUPT discards query. ARROW keys move cursor.
Searches the active database table. ** 1: tt_stages table**
CONFIGURE TRACK STOP STAGES
GROUP NAME: [PF GLASS ]
---------------------------------------------------------------
Stage: Number: [1 ] Required (Y/N): [Y]
Name: [SURFACING ]
Time: [ ] Cost: [ ]
---------------------------------------------------------------
Step: Number: [1 ] Required (Y/N): [Y]
Name: [S ]
Time: [ ] Cost: [ ]
---------------------------------------------------------------
Track Station: [2010 ] SURFACING
---------------------------------------------------------------
The Stage Name will not print, but can be used as a descriptor for this record.
PERFORM: Query Next Previous View Add Update Remove Table Screen ...
Shows the next row in the Current List. ** 1: tt_stages table**
CONFIGURE TRACK STOP STAGES
GROUP NAME: [PF GLASS ]
---------------------------------------------------------------
Stage: Number: [2 ] Required (Y/N): [Y]
Name: [AR COATING ]
Time: [ ] Cost: [ ]
---------------------------------------------------------------
Step: Number: [2 ] Required (Y/N): [Y]
Name: [A ]
Time: [ ] Cost: [ ] ---------------------------------------------------------------
Track Station: [2510 ] AR COATING
---------------------------------------------------------------
The Step Number is not used but can also be used as a descriptor for this record.
QUERY: ESCAPE queries. INTERRUPT discards query. ARROW keys move cursor.
Searches the active database table. ** 1: tt_stages table**
CONFIGURE TRACK STOP STAGES
GROUP NAME: [PF GLASS ]
---------------------------------------------------------------
Stage: Number: [4 ] Required (Y/N): [Y]
Name: [EDGING ]
Time: [ ] Cost: [ ]
---------------------------------------------------------------
Step: Number: [4 ] Required (Y/N): [Y]
Name: [E ]
Time: [ ] Cost: [ ] ---------------------------------------------------------------
Track Station: [2812 ] EDGER
The Step Name is the code that is used to print on the work ticket.
QUERY: ESCAPE queries. INTERRUPT discards query. ARROW keys move cursor.
Searches the active database table. ** 1: tt_stages table**
CONFIGURE TRACK STOP STAGES
GROUP NAME: [PF GLASS ]
---------------------------------------------------------------
Stage: Number: [5 ] Required (Y/N): [Y]
Name: [INSPECTION ]
Time: [ ] Cost: [ ]
---------------------------------------------------------------
Step: Number: [5 ] Required (Y/N): [Y]
Name: [I ]
Time: [ ] Cost: [ ]
---------------------------------------------------------------
Track Station: [2900 ]
---------------------------------------------------------------
The values that would print in the Production Processed field would then be:
S A E I
SURFACING, AR COATING, EDGING, INSPECTION
Entering a Job
From the Optifacts main Menu:
- Type 4 - Run Layout and press Enter.
Enter a job as normal in Layout that fits the criteria for a Track Stop Stages group as entered in the steps above.
Click here to return to the top of the page.
