Interval for Refreshing Shop Floor:

 

When the user is in the Shop Floor module, and has information displayed on the screen (for example, the wip status of a work order), and if the user then leaves the screen up and alone to do another task (e.g., take a break for lunch), then the data represented by the screen may actually undergo changes by other employees. If the user does not use the screen in the meantime, when they return, the information on the screen would be incorrect (because someone else moved material). 


manexSQL performs a periodic update (refresh) to shop floor screens when the user has information displayed on the screen, but has not performed any functions in the meantime. The refresh rate is defaulted for every two and a half minutes. So, if the user has a work order tracking screen displayed with a work order showing wip, and does not perform any transaction for two and a half minutes, then manexSQL will automatically update the information on the screen. The refresh rate can be changed in the setup. However, the trade-off for shorter periods is increased network traffic, and setting too many workstations to be refreshed every few seconds will seriously impact the server’s ability to deliver data.


 


USE Work Order Check List:

 

This is a list to choose items to be included as a checklist for a product. The checklist is created in the Work Order Preparation List module. Examples of check lists could be: verify product revision, perform tooling setup, complete first article, deburring, or any other critical function for which the user wishes to have a verifiable record of being accomplished. The description of the checklist item can be a maximum of 20 characters in length.   


Note: in order to complete the Unreleased Work Order List a user must also have the Product Data Management (PDM) optional module.



Print Work Center Move Ticket When Transfer by Default:

 

Whenever a product is moved from one work center to another, the user has the option to print a move ticket (like a traveler) for each transaction. This move ticket may be printed and accompany the material to the next work center, and can identifying the work order, product date, work center, etc. The user may choose to turn this feature off by selecting the “Printer OFF” button in the setup. If the printer is turned on (“Printer ON”), then a sheet with the details will be printed for every product movement.

 


Print FGI Labels When Transfers to FGI by Default:

 

Whenever a product is moved from one work center to the WC called FGI (Finished Goods Inventory), the user has the option to print a move ticket (like a traveler) for each transaction. This move ticket may be printed and accompany the material to finished goods, identifying the work order, product date, WC, etc. The user may choose to turn this feature off by selecting the “Printer OFF” button in the setup. If the printer is turned on (“Printer ON”), then a sheet with the details will be printed for every product movement.

 

 

Print Work Instructions on Move Ticket:

 

If the user chooses to print move tickets, then they may also choose whether or not work instructions and work order notes are included in the printing. 

  

  

Pop up Default Printer Selection Dialog: 

if checked, a printer dialog box becomes active and visible in Shop Floor Tracking, and provides the option to choose from available printers to print from. 

 


When Checked Shop Floor Transfer by Qty/Un-checked - By Panels:


If the user chooses to identify material movement by quantity of product, then this option must be checked. If the user wishes to move material by the panel, sheet, or roll, they can uncheck this option. This requires the user to define such features in the product definition and the number of products contained in a panel/sheet/roll. Then, if this method is chosen, the user moves panels and manexSQL keeps track of the number of units.  
 

 

Bar Code Tracking:

 

If the user is tracking serial numbers through the production process, and is using the manexSQL bar code tracking module, then they have the option of defining a default method for picking up the bar-coded serial numbers. The following are the available options:

  1. Scan one serial number at a time, and collect those serial numbers for processing a transaction. 
  2. Enter the beginning and ending serial number of a series of serial numbers and allow manexSQL to fill in all of the serial numbers in between for processing a transaction.
  3. Manually enter the quantity of boards to be moved. 
    • If the boards are serialized, then a list of serial numbers is presented to the user from which to select the serial numbers being moved with the quantity of parts.

 

The user has the option to change any of these defaults at the time of entry. For more information, refer to the Shop Floor Tracking Management manual. manexSQL has barcode scan and print capability which is designed primarily for transfer of products in shop floor tracking and input of inspection data by serial number and defect code.


Installation: barcode shop floor tacking is an optional module; it is not a part of the core manexSQL MES modules.

  • Upon purchase of this module, manex will send a soft-key to activate the module
  •  After activation, Barcoding access for each user must be setup in the manexSQL Security module. Users with supervisor rights will automatically have access.
  • Each client workstation (individual PC) which will be printing reports, travelers, labels, serial tags, physical inventory tags and defect lists with barcoding, must have the font installed as an active Windows font.
  • If barcoding of serial numbers is desired, the serial number tracking must be setup in Shop Floor Tracking Defaults.

   

Specification:

  • manexSQL uses the Microsoft Truetype BC C39 Narrow Font. See Article #1225  for the installation procedure.
  • Use of a Y-Type keyboard-emulation scanner is supported by manexSQL. The scanner output goes into manexSQL via the keyboard-input cable. Barcode fields may be scanned or manually entered with the scanner installed.
  • Most scanners require ¼” of white space surrounding the bar code. Laser and inkjet printed labels must have adequate resolution, contrast, and clarity to print barcodes that are readable.
  • manexSQL recognizes a bar code by an asterisk (*) at the beginning and end of the barcoded field.

 

 

Serial Number Tracking Method:

 

At the beginning of manexSQL implementation, the user must decide a method for tracking serial numbers. This decision, once started, is irrevocable

The options to decide from are the following:

1, Do not use serial number tracking.
2, Serial Number will always be unique. 
  • This will insure that a serial number is unique throughout the company. Meaning that when it is used, it can never be used again, no matter the product.
3, Serial Number will be unique by product. 
  • This will allow duplicate serial numbers to be used throughout the company, but they must be unique for a given product. They can be used for other products, but never again for the same product.


If serial numbers not put to use, then the option will not appear when creating new part numbers within the ICM module.
If serial numbers are put to use, then the user will have the option, when creating parts within the 
ICM module, to either serialize the part or leave it un-serialized.
If serial numbers are used on a part, then the user must enter serial numbers in order to move product through the SFT for shipment.
The user will also need to define whether serial numbers are to be transferred by work center or by activity within a work center. 


For further detail on why the system enforces the uniqueness per product rule and will not base the uniqueness on SN that exist in the Qty at that time, see Article #2495.