Local Commands

42Q Home > Tools > Local Commands

 

 

 

Tools Shop Floor Data Collection Operations Manual Revision G Work Instruction 

 

This Work Instruction is 42Q's corporate standard. This document is under revision control. The latest revision is located on Intranet. Once printed it is an uncontrolled copy. All alterations to this work instruction require approval. Contact the IT Global Education and Training Department to submit suggested alterations and or updates.

This edition applies to SFDC Version 6.1 and all subsequent releases and modifications until otherwise indicated in new revisions.

 

Table of Revisions

Date:	Author:	Description:
6/23/04	Karen Ellington	Initial release of document to website.
8/4/04	Karen Ellington	Added status 36 to Unit Status Definitions section. General edit and format clean up.
1/06/09	Keith Fuqua	Added SFDC3 specific items, new commands, features, and updates.
01/22/10	Keith Fuqua	Batch processing, Employee validation, new commands & features.
10/29/10	Keith Fuqua	Table cleanup, document corrections.
06/17/11	Keith Fuqua	Updates for SFDC 5.22.02 – SFDC 6.0.
07/02/12	Eric Moldenauer	Updates for SFDC 6.1.

 

Introduction

This document provides instruction and support for the operation of the Shop Floor Data Collection (SFDC) PC System.

The data configuration for SFDC PC is handled within the Manufacturing Data System (MDS), which is a complete factory automation system. The SFDC System uses barcode scanning, both manual and automated, to monitor and control a single product line or an entire plant. It can be used with the Statistical Process Control / Statistical Quality Control (SPC/SQC), or order entry systems. MDS makes communication between these systems possible.

SFDC provides a wide range of data storage and analysis tasks, making communication between data collection and corporate management more solid. Reports available include the following:

• Work-In-Process
• Current and Previous Shift Yields
• Delinquent Units
• Unit History
• Current Shift Defects
• Historical Defects

NOTE: For information on off-line reporting through MDS, see the SOP-5-I-MDS0019-C MDS Reports Generator. Available off-line reports include Component Activity, Container/Lot, Old Age and Sick Units, Manual Move, and Shop Order Operation History, as well as the reports shown in the list above.For information on reporting through MESR (MESWeb) please refer to MESWeb documentation.

Some of the standard features are as follows:

• Flow control
• Tracking sub-products (components or subassemblies)
• User-defined prompts
• Manual “move to“ functions
• Block of serial number moves
• Product and sub-product (component or subassembly) verification
• View serial number history
• Unit history comments
• On-screen display of communication status between SFDC and Data Collection Stations and between SFDC and the plant server network
• Attributes
• Shop Order
• Containerization

 

The SFDC PC

The SFDC PC is a Linux based server, and does not have a GUI (Graphical User Interface) running on the console itself. All operations are through the command line interface. After logging into the console, there base menu will be displayed. Each item in the menu is discussed below.

• sfdc help – Displays the base menu.
• sfdc -v – Displays the current version of SFDC software.
• netdc -v – Displays the Device Manager version.
• Individual SFDC commands - Type sfdc followed with a space and then the command. (STOP, START, RESTART, TEST, DNLD, CONFIG)
• dnld – Displays the SFDC download commands menu.

1. sfdcdnld – Downloads SFDC configuration from MDS.
2. emvdnld – Downloads Employee Validation configuration from MDS.
3. spcdnld – Downloads SPC configuration from MDS.
4. downdata all – Downloads all WIP serial information from MDS.
5. downdata [startdate] [enddate] – Downloads WIP serial information from MDS for the specified date range.

1. sampdown – Downloads Sample Plan configuration from MDS.
2. defectguidnld – Downloads Defect/Repair GUI configuration from MDS.
3. sfdcdnld empty – Performs an empty download, clearing out current configuration from the SFDC PC. Useful if changing the SFDC PC configuration from one line to another.
4. attribdnld – Downloads Attribute Definition configuration from MDS.

NOTE: The listed commands can all be run from the command line in addition to running from the menu.

• YUM commands – YUM is the method for installing, updating, downgrading, software packages in versions 5.12.02 and higher. The SFDC Install command should never be used in these version, as it corrupts the YUM configuration, requiring reinstallation from CD. Please see the YUM CD manual documentation for further information on the capabilities and usage of the YUM commands.
• taskmenu – Displays the command line task scheduler menu. SFDC tasks can be scheduled to run at a set future date and time. In SFDC V6.1 and higher, up to 30 reoccurring tasks may be scheduled.

1. Create Task – Creates a scheduled task from the displayed list of available tasks for execution at a future date and time. (NOTE: As futures tasks become available, the list of available tasks will be updated.)
2. Edit Task – Displays a list of currently scheduled tasks. Allows editing of a scheduled task's date and time. (NOTE: A scheduled task cannot be changed to a different task. Only the date and time can be modified. To change a task, delete the current scheduled task and create a new task.)
3. Delete Task – Displays a list of currently scheduled tasks. Allows deletion of the displayed scheduled tasks.
4. View Task – Displays a list of currently scheduled tasks.

• toolmenu - Displays a list of routine maintenance items.

1. Reindex tables – Used to re-index all the tables in the local database. This tool should be run once a month. Re-indexing the tables will increase overall performance on the SFDC PC, especially on high volume machines.
2. Vacuum database – Cleans up records that are no longer WIP on the SFDC PC. A background vacuum db task runs daily and is configured in sfdc config.
3. Backup SFDC – Creates a local backup of locally configured files and some data tables to the /home/mfguser/backups/ directory on the SFDC PC. The backup files can then be backed up to the MDS server using the Backup to MDS tool. This provides a way of backing up configuration performed on the local PC, as well as backing up tables storing data that is only used by SFDC, prior to an upgrade or other scheduled event. The backed up files and tables include Configure Workstation, AutoSFDC device control, Defect & Repair GUI Top 5 calculations and Repair Notes, Tasks, Wip & Yield data.
4. Restore SFDC – Restores the files and tables previously backed up to /home/mfguser/backups/ to the appropriate directories.
5. Backup SPC data – Creates a local backup of SPC data to the /home/mfguser/backups directory. The backup files can then be backed up to the MDS server using the Backup to MDS tool. This provides a way of backing up production SPC data prior to an upgrade or other scheduled event.
6. Restore SPC data – Restores SPC data previously backed up to /home/mfguser/backups/ to the appropriate directories. When used with the Restore from MDS tool, this provides a way of restoring production SPC data after an upgrade or other scheduled event.
7. Delete old data – Deletes old data in the local database such as serial numbers that are no longer in WIP.
8. Backup to MDS – Bundles all files and tables in /home/mfguser/backups/ together, create a tar (tape archive) file, and then upload it to the MDS server using FTP. When used with the Backup SFDC and Backup SPC data tools, this provides a way of uploading all necessary backup files and tables to the MDS server prior to an upgrade or other scheduled event.
9. Restore from MDS – Downloads previously uploaded tar file from the MDS server to the local SFDC PC, then untar (un-archive) it to the /home/mfguser/backups/ directory as well as their appropriate directories. This provides a way of restoring all locally configured files and tables after an upgrade or other scheduled event.

• timeconfig – Used to configure the timezone on the SFDC PC.
• Reboot and Shutdown commands.

 

The SFDC PC Index

The SFDC PC application is Java based and therefore can be accessed via a web browser. Typically, access to the SFDC PC is performed using a web browser. To access the SFDC PC Index page, enter the IP address of the SFDC PC. The main Index page for the SFDC PC will be displayed. The index will contain different buttons to access different functions on the SFDC PC. Some or all of the listed applications below can be displayed, depending upon the version of SFDC software running on the SFDC PC and the software installed. A means of returning to the SFDC PC Index page is also included in all the different GUI screens. Clicking on the SFDC logo in the upper left corner will return you to the Index page. If you are logged into a device in an application such as the Data Collector GUI, or the Batch Process GUI, if you click on the SFDC logo to return to the Index page, you are logged out of the device and returned to the Index page.

• Local Web
• Command GUI
• AutoSFDC XML
• Data Collector GUI
• SPC Web – removed in SFDC 6.0
• Defect GUI – removed in SFDC 6.0
• TWIST – added in SFDC 6.1
• Batch Process GUI

Each menu item is discussed in detail in the following sections.

 

SFDC Local Web

The Local Web page is where all the normal SFDC data is accessed. There are 6 Menu tabs that display the bulk of the SFDC information. To the right of the Menu tabs, the SFDC PC NetUserID is displayed. The IP address that is displayed is the IP address of the machine currently connected to the SFDC PC, meaning the user’s IP address. The MDS server name is also displayed. Along the bottom of the main window is the local time at the plant, the date, the current shift, Network and SFDC status indicators. Network Status is critical for troubleshooting the system. It displays the network status between the SFDC PC and the plant server. If the Network Status displays a DOWN condition, certain SFDC operations are not functional. Some SFDC operations rely on immediate response from the server. Communication between SFDC PC and data collectors may be very slow during a DOWN condition.

All this information is displayed in every screen or menu.

Note: Beginning in version 5.12.01, you can sort the displayed data, in ascending or descending format, in the following 4 screens, Work In Progress, Serial Number, Current Yield, and Current Defects by clicking on a heading.

Note: In SFDC 6.0 and higher, a new OPTIONS line allows for password protecting access to the SFDC Local Web page. Please see the SFDC Setup Data Editor Quick Reference for more information.

 

Work-In-Process

The Work-In-Process screen displays product quantities at the listed stations. On the left side of the screen, a Product: drop down menu is available to select a specific product number to filter by. A Station Summary Display check box is also available which will change the WIP display to only stations and summary quantities.

 

Serial Number Display

The Serial Number Display screen displays all active serial numbers in alphanumeric order. The display includes the serial number, the product number, serial number quantity (typically 1 unless the serial number is a batch serial number), the present location, and a Last Activity Scan flag. This flag signifies that a unit has not been scanned for the length of time specified in the Miscellaneous Setup table in the database. On the left side of the screen, a Workstation and Product: drop down menu is available to select a specific workstation and or product number to filter by. A Shop Order Mode check box is also available which will change the Serial Number display to be based upon Shop Orders. The Product: drop down menu will change to Shop Order: to allow filtering by specific shop order. A serial number entry field is also available to search for a specific serial number or to display the history of a serial number. Links are also available to Move a range of units, post a comment to a range of units, or to format a report for printing.

 

Post a Comment to a Range of Units

Select Post a comment to a range of units. The User Password, Employee ID, Enter Lowest serial number, Highest serial number, Comment key-ins display. Key in the information for each field, then click on the Comment button. A verification message displays. Press the OK buttonto accept.

 

Move a Range of Units

Select Move a range of units. The User Password, Employee ID, Enter Lowest serial number, Highest serial number, Reason for Move key-ins display. Product, From Workstation, New Workstation drop down menus display. Key in the information for each field, and select the correct information from the drop down menus, then click on the Move button. A verification message displays. Press the OK buttonto accept the move.

The Serial Number Display updates to show the units at the new location.

Clicking on a serial number in the main display will bring up the unit history of that particular serial number. The left menu changes to the options available for that particular serial number.

 

Move Unit

Select Move unit. The User Password, Employee ID, Reason for Move key-ins display. TheNew Workstation drop down menu displays. Key in the information for each field, and select the correct information from the drop down menu, then click on the Move Unit button. A verification message displays. Press the OK buttonto accept the move.

The Serial Number Unit History Display updates to show the unit at the new location. A Manual Move activity is recorded in the unit history.

 

Add Comment to a Unit

Select Post a comment to a range of units. The User Password, Employee ID, Comment key-ins display. Key in the information for each field, then click on the Comment button. A verification message displays. Press the OK buttonto accept.

 

Change Unit Serial Number

Select Change unit serial number. The User Password, Employee ID, New Serial Number key-ins display. Key in the information for each field, then click on the Change button. A verification message displays. Press OK to accept the serial number change.

NOTE: The change is logged in the history of the old serial number, and the old serial number leaves the Serial Number display. The new serial number takes all historical data from the old unit and the old serial number is recorded as part of the unit history.

 

Change Unit Product Number

Select Change Unit Product Number. The User Password, Employee ID key-ins display. The New Product Number drop down menu displays. Key in the information for each field, select the new product number from the drop down menu, then click on the Change button. A verification message displays. Press OK to accept the change.

As units are completed or pass to Online Line Hold, the serial numbers are removed from the SFDC local database.

 

Current Shift Yields

The Current Shift Yields screen displays quantities of each product type scanned at all stations. Also displayed are the quantity of units tested, passed and the yield percentage for each product. On the left side of the screen, a Product: drop down menu is available to select a specific product number to filter by. A Work station/Process Summary check box is available which will change the Yield display to stations and an overall summary yield. A Process View check box is also available which will change the Yield display to display by process, rather than Workstation.

 

Current Shift Defects

The Current Shift Defects screen displays the number of products that have failed at any listed station. The display includes station, product type, and defect code, description and a total quantity. On the left side of the screen, a Product: drop down menu is available to select a specific product number to filter by.

 

Historical Yield / Defects Report

The Report Parameters key-in displays. Key in From date, To date, and Shift. Date format should be MM-DD-YYYY, where MM is the month, DD is the day, and YYYY is the year. Click on either the Yield or Defects Button to select the type of report to display.

 

Administration Menu

In order to access the Admin menu, an Administrator Password must first be entered. Initially, the Input Device Status is displayed. In the left Menu are buttons for Input Device Status (current displayed), NetDC Device Status, System Log Displays, View Defect Code, Set / Change User Password, and Set / Change Admin Password. Selecting an item on the left display will display the default screen information in the main window.

Each menu item is discussed in detail in the following sections.

 

Input Device Status

In the main window, the PCC boards and subsequent ports are displayed. Clicking on any board/port will bring up the Data Collector Device status for that particular board and port. The Device number, Location Name, Status, and communication counters are displayed. Enable / Disable buttons, along with a checkbox to the right, allow individual devices to be selected and either Enabled or Disabled. The Left Menu changes, displaying the following options in addition to the Admin Section Menu: Refresh Report, Reset Device Statistics, Enable All Devices, Disable All Devices, Enable Selected Devices, and Disable Selected Devices.

Data Collector status settings are as follows:

• OK Communicating properly
• NO RESPONSE Configured but not communicating
• DISABLED Configured but disabled from the SFDC PC
• NOT CONFIGURED Not listed in the Scanner Table

 

Disable

Select a location, checking the box to the far right, then click on Disable. The screen updates to show the location as DISABLED. Communication testing is verified by communicating with one data collector at a time. Disabling all but the first station allows continuous communication with the one station. Adding one data collector at a time simplifies installation. DISABLE should also be used when a new data collector is installed, but the hardware has not.

NOTE: Disable data collectors that are not active. If they are not disabled, errors occur in processing, which will slow the scanning on that port.

 

Enable

Select a location, checking the box to the far right, then click on Enable. The screen updates to show the location as ENABLED.

Use the right check boxes to select individual or multiple devices, then use the Enable / Disable Selected Devices links in the left menu to change their status all at once. The Refresh Report link will refresh the main display, after changes have been made. Reset Device Statistics zeros or clears all the communication counts for all devices displayed.

 

NetDC Device Status

In the main window, by default, only the Online NetDC devices are displayed. At the top are two buttons for selecting either Online or All devices. DEVICE ID, LOCATION, STATUS, VERSION (firmware) MAC ADDRESS, NETDC IP address, and COM PORT INFORMATION are also displayed. Selecting the All button will display all online and offline configured devices. Clicking on the NetDC IP address with connect you to that device.

 

System Log Displays

In the main window, by default, the SFDC Setup file is displayed. This is the setup.txt file is created by the Setup Editor in MDS. The Left Menu displays a Log File drop down menu, which is used to select the type of log to display. Also available are a Refresh Status link and a Print Report link and the Admin Section Menu items.

In the Log File drop down, the following logs are available: SFDC System, SFDC Setup, NetDC, Database, ScanLog, and SFDCDNLD Log. Select the type of log you wish to view, and the main window will update, displaying the chosen log. Use the Refresh Status link to update the display in the main window.

 

View Defect Code

In the main window, by default, the entire list of available defect codes is displayed. Above this list, on the right is total count of defect codes. A field to enter a specific defect code, along with the Go button, provides search capabilities. 25 defect codes are displayed in a page. Below the main window is count of the total number of pages, along with links to select a particular page of defect codes. A page entry field is also available.

NOTE: Various SFDC features can change the historical record of a product permanently. Required passwords protect the system and prevent unauthorized changes or shutdowns. If activated, a password is required for the following:

 

Tasks:

• Manual Move Unit (Serial Number Display)
• Manual Move Range (Serial Number Display)
• Change Serial Number (Serial Number Display)
• Change Product Number (Serial Number Display)
• Post a Comment to a Unit (Serial Number Display)
• Post a Comment to a Range (Serial Number Display)

 

Set / Change User Password

The User password provides a level of protection against unauthorized changes to serial number or WIP. The tasks this password are used to perform are:

• Manual Move a Unit
• Manual Move a Range of Units
• Change Serial Number
• Change Product Number
• Posting a Comment to a Unit or a Range of Units.

In the main window are three fields, Old Password, New Password, New Password Again. Enter the Old Password, enter the New Password. Re-enter the New Password to confirm it. Click on the Change Password button to change the password. A message will display below to confirm the password change was successful.

 

Set / Change Admin Password

The Admin password is used to control various operations on the SFDC PC. Mainly it is used to control access to the Admin Menu items and the functions within. It is also the password that allows an SFDC admin to log into the SFDC PC remotely to perform operations such as a download, stopping or starting the SFDC service, etc. In the main window are three fields, Old Password, New Password, New Password Again. Enter the Old Password, enter the New Password. Re-enter the New Password to confirm it. Click on the Change Password button to change the password. A message will display below to confirm the password change was successful.

 

Configure Workstation

The Configure Workstation menu is used to create customized workstation description labels for use with the Data Collector GUI and Batch Process GUI applications. By default, there is no configuration. To create an entry, click the Add button, enter a Device Number and Description, then click on the Save button. A well thought out naming convention will be helpful in grouping like workstation descriptions. Follow the same process to create additional entries. Create as many entries as needed. There may be multiple entries for the same device number to allow for different descriptions for a multipass device. Edit the configuration by selecting the device, using the check-box, and click the Edit button. Make the desired changes, then click the Save Button. To cancel, click the Cancel button. Delete a configuration by selecting the desired device, using the check-box, and click the Delete button. The Upload button is used to save already created configuration file to the /home/mfguser directory on the SFDC PC. An SFDC Administrator can then use the Local SFDC Configuration Backup function to backup the configuration file to the MDS server. This prevents having to recreate this configuration when installing a new version of SFDC software. It is also possible to use FTP to pull the file from this directory to save it elsewhere. The Download button is used to load a configuration file previously saved in the /home/mfguser directory.

NOTE: When a new version of SFDC software is installed from CD, the entire hard drive is wiped out. If saving a configuration file in the /home/mfguser/ directory, be sure to backup the configuration file using SFDC Configuration Backup, or by FTP and saving in another location off the SFDC PC, else it will be lost.

In SFDC v6.1 or higher, the ability to sort by Device Number or Description has been added. To sort, click on the Device Number or Description header title. This is helpful when many devices have been configured. The most recent sort order will be the order in which devices are displayed in the GUI applications.

 

SFDC Command GUI

The Command GUI web page is a web-based interface for use by the SFDC Admin or other authorized user. This interface provides menu based administration commands to handle all the day to day operations on the SFDC PC. Access to the administration commands is controlled by only allowing access by logging in using the Universal Login.

Initially, in the main window the Status of SFDC, Tomcat, and Apache are displayed. On the top of the page are drop down menu items for various functions. These are Status, SFDC Application, Tomcat, Apache, and Logout. Passing the pointer over the menu items will display the lower level items.

Each menu item is discussed in detail in the following sections.

 

Status

The Status menu has one drop down item. This is also called Status and returns the main window back to displaying the status of SFDC, Tomcat, and Apache.

 

SFDC Application

The SFDC Application menu contains all the commands that are used to manage the SFDC PC. These are Start, Stop, Restart, Nodata, and SFDC Config.

Start

Start is used to start the SFDC service if it is not running. The RESTART command will perform the same function but also includes stopping the service.

Stop

Stop is used to stop the SFDC service. This is typically done to perform subsequent operations such as an upgrade to resolve a problem that might have occurred.

Restart

Restart is used to stop and start the SFDC service. This is typically required when an SFDCDNLD command is run, which can occur without stopping SFDC. In order for the downloaded changes to take effect, the SFDC service must be stopped and restarted. Restart can also be used in place of the Start command to start the SFDC service, once it has been stopped.

Nodata

The Nodata command is used to remove all the local WIP information from the local database on the SFDC PC. Nodata is not recommended unless a specific reason requires it. All Yield and Defect information is also deleted from the SFDC PC. After a Nodata command has been run, each serial number scanned into SFDC requires that the unit information be pulled from the MDS server. This can drastically slow down production, as each serial number must be retrieved from the MDS server when it is scanned the first time.

SFDC Config

The SFDC Config command is used to configure the SFDC PC. When launched, the user will be prompted for the following items:

• MDSUSER
• MDSHOST
• MDSIP
• MEASIP
• MEASDB
• SAVE_DATA_DAYS
• AUTO_DEL_TIME
• DB_VACUUM_TIME
• IP FILTER Y/[N]
• MULTI_THREAD Y/[N]

MDSUSER = SFDC PC name (pXXdcX)

MDSHOST = MDS Server name (pXXlsX or pXXasX)

MDSIP = MDS Server IP address (xxx.xxx.xxx.xxx)

MEASIP = SFDC Measurement Server IP address (xxx.xxx.xxx.xxx) The prompt is displayed as part of sfdc config in version 6.1 and higher.

MEASDB = SFDC Measurement Server database name (CPR) The prompt is displayed as part of sfdc config in version 6.1 and higher.

SAVE_DATA_DAYS = 7 by default. This defines the number of days worth of data to store in the local db for status 20 and 25 units. It also defines the number of days to retain Finished units history in the local db.

Note: In SFDC version 6.1 and higher, a second number defines the number of days worth of data to store in the local db for all other statuses. Add a comma after the first number to define the second value (For example: 21,7).

SAVE_DATA_DAYS=x,y

• Delete any wip units (Status 20, 25) older than "x" days
• Delete any non-wip units (Status 26,27,28,29,30,63) older than "y" days.
• If only one value is defined, system will use the same number of days for all unit statuses.

AUTO_DEL_TIME = Time of day to move units from local db to MDS db. This time should be during a break or downtime when production is not running to minimize impacting performance. Time of day to remove Finished units from the local db (based on SAVE_DATA_DAYS parameter).

DB_VACUUM_TIME = Time of day to rebuild the indexes in the local database and optimize the machine. This is similar to a defragmentation operation in a Windows computer. This time should be during a break or downtime when production is not running to minimize impacting performance. It should also be different from the AUTO_DEL_TIME, so as not to interfere with that operation.

IP FILTER Y/[N] = Enables/Disables (default) access control to the SFDC through AutoSFDC XML. Please refer to the AutoSFDC Client section for further information about controlling access to SFDC through AutoSFDC XML. The prompt is displayed as part of sfdc config in version 5.21 and higher.

MULTI_THREAD Y/[N] = Available in SFDC 6.0 and higher. Default setting is No. Enabling will allow SFDC to create multiple socket connections to MDS when needed. Please see the section on multi-threading for more information.

SFDC Install

The SFDC Install command is only in versions of SFDC from 5.12 and earlier.

NOTE: In versions 5.12.02 and greater, do not use the SFDC Install command. YUM is the preferred method of performing installations, upgrades, etc. Using SFDC Install will corrupt YUM and will require reinstallation from CD to correct.

 

SFDC Download

The SFDC Download menu contains all the commands that are used to download configuration and other data to the SFDC PC. These are SFDCDNLD, SFDCDNLD Empty, Downdata ALL, Downdata [start date], EMVDNLD, SPCDNLD, SAMPLEDNLD, ATTRIBUTEDNLD and DEFECTGUIDNLD.

SFDCDNLD

The SFDCDNLD command is used to download configuration changes made in MDS to the local database on the SFDC PC. This is done through a proxy. SFDCDNLD can be run without stopping the SFDC service. This allows production to continue to run while the download is performed. Once the SFDCDNLD command has completed, a Restart command is used put the downloaded changes into effect, minimizing the amount of downtime required for changes to be made to the system.

SFDCDNLD Empty

The SFDCDNLD Empty command performs an empty download, clearing out current configuration from the SFDC PC. Useful if changing the SFDC PC configuration from one line to another.

Downdata ALL

The Downdata ALL command is used to retrieve all the WIP serial numbers and information from the MDS server. This is typically required if an upgrade was performed to SFDC, as the local database is typically updated with a new database. Downdata does not run by proxy, therefore it requires that the SFDC service be stopped in order to download the WIP data. Depending upon the amount of WIP, this operation can take a significant amount of time, thereby requiring SFDC to be down for the duration.

Downdata [start date]

The Downdata [start date] command is used to retrieve the WIP serial numbers and information from the MDS server for specified date range. This is typically necessary if an upgrade was performed to SFDC, and only a portion of the MDS data is to be downloaded to the local database. Downdata does not run by proxy, therefore it requires that the SFDC service be stopped in order to download the WIP data. Depending upon the amount of WIP, this operation can take a significant amount of time, thereby requiring SFDC to be down for the duration.

EMVDNLD

The EMVDNLD command is used to download Employee Validation configuration changes made in MDS to the local database on the SFDC PC. This is done through a proxy. EMVDNLD can be run without stopping the SFDC service. This allows production to continue to run while the download is performed. Once the EMVDNLD command has completed, any changes will take effect immediately, alleviating any SFDC downtime. Unlike SFDCDNLD, the SFDC service does not need to be stopped and restarted for the changes to take effect. EMVDNLD does not download any SFDC configuration changes, only those made with the Employee Validation module in MDS. See SOP-5-I-MDS0003-C MDS Employee Validation user guide for more information.

Note: In version 6.1 and higher, the SFDC version is sent to MDS upon emvdnld so that it knows which version is requesting the EV records. If the version sent is not 6.1 or higher, MDS 14-5 does not send part-key values in the empval records. (The version information is not used by MDS versions prior to 14-5.) Also in version 6.1 and higher, a successful download is verified prior to overwriting existing configuration to alleviate problems caused if/when the appserver is stopped, or interrupted, while an emvdnld is running.

SPCDNLD

The SPCDNLD command is used to download SPC configuration from MDS to the local database on the SFDC PC.

SAMPLEDNLD / SAMPDOWN

The SAMPLEDNLD menu runs the SAMPDOWN command, which is used to download Sampling Configuration changes made in MDS to the local database on the SFDC PC. This is done through a proxy. SAMPDOWN can be run without stopping the SFDC service. This allows production to continue to run while the download is performed. Once the SAMPDOWN command has completed, any changes will take effect the next time the SAMPLE command is run. Unlike SFDCDNLD, the SFDC service does not need to be stopped and restarted for the changes to take effect. SAMPDOWN does not download any SFDC configuration changes, only those made within the Sampling Plan Configuration module in MDS. See the Sampling Plan Configuration section of the SOP-5-I-MDS0009-C RA1 MDS SFDC Configuration for more information.

ATTRIBUTEDNLD / ATTRIBDNLD

The ATTRIBUTEDNLD menu runs the ATTRIBDNLD command, which is used to download Attribute Definition configuration from the MDS server to the local database on the SFDC PC. This is done through a proxy. ATTRIBDNLD can be run without stopping the SFDC service. This allows production to continue to run while the download is performed. Once the ATTRIBDNLD command has completed, a Restart command is used put the downloaded changes into effect, minimizing the amount of downtime required for changes to be made to the system. ATTRIBDNLD does not download any SFDC configuration changes, only those made to the Attribute Definition module in MDS. See the Attribute Definition section of the SOP-5-I-MDS0009-C RA1 MDS SFDC Configuration for more information.

DEFECTGUIDNLD

The DEFECTGUIDNLD command is used to download Defect/Repair GUI configuration from MDS to the local database on the SFDC PC. Downloaded configuration for the Defect/Repair GUI is available immediately without restarting the SFDC service.

 

Tomcat

The Tomcat menu has three commands, Start, Stop, and Restart. These commands function in the same manner as the comparable SFDC Application commands. These commands are used for controlling the Tomcat application, which handles all the web based applications such as AutoSFDC XML, the Data Collector GUI, the Command GUI, and SPC Web. In order for these applications to function, Tomcat must be up and running.

 

Apache

The Apache menu has three commands, Start, Stop, and Restart. These commands function in the same manner as the comparable Tomcat commands. The Apache application is the code that handles all the web server functionality. This software allows for Web access and in conjunction with Tomcat, allows for all the different SFDC applications to run.

 

Task Scheduler

The Task Scheduler is designed to allow SFDC tasks such as downloads, restarts, etc. to be scheduled in advance and run, without user intervention. This allows tasks to be run when production is down, and the SFDC admin is not present. The Task Scheduler menu has four commands, Create Task, Edit Task, Delete Task, and View Task. A list of the available tasks that can be scheduled is provided. This list will be updates as tasks become available for use. A command line task scheduler is also available and can be run from the command prompt.

NOTE: If a scheduled task is running when another scheduled task is to start, the task will be delayed and run once the first task has been completed.

Create Task

The Create Task button is used to define the task to be scheduled and the date and time to run it. To schedule a task, click on the task scheduler menu button, then select Create Task. The Create Scheduled Task window will be displayed. A table of tasks available to be scheduled is displayed. At the bottom of the screen are three fields, Task to Schedule, Task Date, and Task Time. Enter the task number to schedule in the Task to Schedule field. Clicking in the Task Date field will bring up a calendar. Select the date for the task to run. You can also manually enter the date in the Task Date field. Clicking in the Task Time field will bring up a clock. Select the hour to run the task by moving the hour hand to the appropriate hour. Select the minute by holding the CTRL key and moving the minute hand to the appropriate position on the clock. Clicking on the AM/PM will toggle the setting. The time can also be entered manually in 24 hour time.

Note: In SFDC V6.1 and higher, up to 30 reoccurring tasks may be scheduled. Select Daily, Weekly or Monthly from the "Repeats" field. Select After __ occurrences (define the number of occurrences) or On [enter yyyy-mm-dd] from the "Ends" field.

To schedule the task, click on the Submit button. To cancel task scheduling, click on Cancel.

Edit Task

The Edit Task button is used to edit the time or date for a task that is already scheduled. To edit a scheduled task, click on the Task Scheduler button then select Edit Task. The Edit Scheduled Task window will be displayed. A list of scheduled tasks is displayed.

NOTE: A scheduled task cannot be changed to another task. Only the date and time can be modified. Delete the task and create a new scheduled task.

At the bottom of the screen is a Task # field. Enter the task number from the list to modify. Click in the Task Date field to change the scheduled date. Click in the Task Time field to change the scheduled time. After making the necessary changes, click on the Submit button for the changes to take effect. To cancel the changes, click on the Cancel button.

Delete Task

The Delete Task button is used to delete a scheduled task. To delete a scheduled task, click on the Task Scheduler button then select Delete Task. The Delete Scheduled Task window will be displayed. A list of scheduled tasks is displayed. Below the list is a Task # field. Enter the task number from the list, for the scheduled task to delete. To delete the task, click on the Submit button. To cancel the deletion, click on Cancel.

View Task

The View Task button is used to view all scheduled tasks. To view a scheduled task, click on the Task Scheduler button then select View Task. The View Scheduled Task window is displayed. A list of scheduled tasks is displayed. If there are more tasks scheduled than fits in the window, there will be a scroll bar on the right side move up or down in the list.

 

Logout

To exit the Command GUI, click on the Logout button on the menu bar and select Exit. The screen will return to the main login window.

 

AutoSFDC XML

The AutoSFDC XML application is a Java application that runs on the SFDC PC. This application allows for direct data entry to SFDC without having to use a physical data collector. AutoSFDC XML is typically used by testers or test equipment to provide data collection information directly to SFDC, eliminating the need for a user to enter test data into SFDC. AutoSFDC XML also allows software emulators to interface with SFDC as another data collection interface. A software emulator is a program that replicates a physical data collector, but runs on a computer. Please refer to the Data Collection section for more information regarding emulators.

NOTE: Access to the AutoSFDC XML GUI module is password controlled. The administrator password is required.

After clicking on the AutoSFDC XML button on the Index page, the AutoSFDC XML page is displayed. The version of software running is displayed in the header. There are four menu items available. See below for detailed descriptions of each menu button.

Service

Click on the Service menu to display the service information log. There is no configurable setting under this menu, only information.

Scan Log

The Scan Log menu item displays a Scan Log of current scanning activity recorded since the last restart of the AutoSFDC service or since the last SFDC service restart. This information is the listed requests and responses received for all device numbers accessing SFDC through AutoSFDC XML.

AutoSFDC Client

The AutoSFDC Client button is used to launch an application that allows for access control to the SFDC PC through the AutoSFDC XML application. Access can be controlled by IP Address, MAC ID, and Unit number, or a combination of these. Please refer to the AutoSFDC XML Access Control Instructions for further information on configuring AutoSFDC XML to limit access.

NOTE: In order to gain access to the access control application, a profile must exist in MDS and the user must have the profile assigned in order to configure the application.

Upon clicking on the AutoSFDC Client button, Java Web Start will launch and download the application. A Login page will be displayed. Upon successfully logging in, a window similar to jMDS will be presented and the Access Control module will be listed. Despite the appearance, this application is running on the SFDC PC, not the MDS server.

A configuration file is created when using the access control application. Running the SFDC Backup maintenance tool will create a copy of the file, autosfdc_device_control, in the /home/mfguser/backups/ directory. This can then be stored off the SFDC PC so as not to have to re-enter the information after an upgrade.

Access Control Off/On

The Access Control button is used to turn access control through AutoSFDC XML on and off. There is also a command line prompt for access control, to enable or disable, as part of the sfdc config command. Clicking the button will enable or disable the access control, depending upon the current state.

• Access Control Off = Disabled

• Access Control On = Enabled

The button states the current status of the access control program.

NOTE: Enabling or turning the access control program on will effectively limit all access to the SFDC PC through AutoSFDC. Only IP addresses or MAC Addresses that have been configured will be able to access SFDC through AutoSFDC. Do not enable until configuration is setup to allow access.

To return to the Index page, click on the red SFDC text in the top left of the header.

 

Data Collector GUI

The Data Collector GUI web page is a web-based emulator interface for use by any SFDC user. This interface provides a simple means of entering data directly into SFDC without a physical data collector, or having to install and configure a standalone software emulator program. Upon clicking on the Data Collector GUI, a login screen is displayed. A workstation field is displayed allowing for the selection of the workstation to use. By default, only device numbers that are available are displayed. The SFDC Admin can create custom labels for the workstations, allowing more useful description information to be displayed. The drop down list displays all available or configured workstations. A language field is also available to select a language from the drop down menu.

Upon launching the Data Collector GUI, three menu buttons, OPERATOR, HELP, and EXIT, are displayed. By default, the Operator window is displayed. The Device ID: is displayed in the top field. The history field is used to display the current SFDC prompt and responses to the commands. At the bottom is a Data Entry field for entering data into the interface. Log into the workstation by entering or scanning an employee number into the Data Entry field. When done working in the workstation, the user should log out of the workstation using the LOGOUT command. To switch to a different workstation, click on the EXIT menu, and the application will return to the login screen.

NOTE: Configuration of the custom workstation descriptions is performed through the ADMIN menu on the SFDC Web page.

 

SPC Web

The SPC Web application provides statistical process control capabilities within SFDC. This is an application that requires installation, in versions of SFDC prior to 5.21. Configuration of SPC is performed through the SPC configuration module in MDS. In order for the SPC Web application to work, all the SPC configuration and code must be installed and present. Refer to the SPC Users guide for additional detail regarding SPC functionality and operation.

NOTE: Access to the SPC Web application is password controlled. The administrator password is required.

After clicking on the SPC Web button on the Index page, the SPC page is displayed. The version of software running is displayed in the header. There are two menu items available. See below for detailed descriptions of each menu button.

 

Service

Click on the Service menu to display the service information log. There is no configurable setting under this menu, only information.

 

SPC Client

The SPC Client button is used to launch the SPC application on the SFDC PC. NOTE: In order to launch the SPC application, a profile must exist in MDS and the user must have the profile assigned in order to use the application.

Upon clicking on the SPC Client button, Java Web Start will launch and download the application. A Login page will be displayed. Upon successfully logging in, a window like jMDS will be presented and the SPC module will be listed. Despite the appearance, this application is running on the SFDC PC, not the MDS server. Refer to the SPC Users guide for additional details on using the application. To return to the Index page, click on the red SFDC text in the top left of the header.

NOTE: The SPC Client button has been removed from the SFDC Index page in version 6.0. All maintenance for SPC is performed in the MES Portal.

Defect GUI

NOTE: The Defect GUI has been removed from the SFDC PC in versions 6.0 and higher, as all development of this application has been moved to the MES Portal. Please refer to the documentation on the MES Portal for more information regarding advanced defect and repair capabilities.

The Defect GUI is an application that is being developed for defect and repair logging. Debug functionalities are also being developed which include a Knowledge base and the ability to display a CAD drawing, when available, for easier part identification and as a troubleshooting aide.

Upon clicking on the Defect GUI, a login screen is displayed. A workstation field is displayed allowing for the device number or unit number to be entered. Only device numbers with configuration are displayed. Configuration is managed in MDS within the SFDC GUI Administrator module. Upon entering a character, a drop down menu will be display to allow scrolling and selecting a particular device number. You can also continue to enter characters directly into the Workstation field. A Badge field is also displayed. Enter/Scan your employee number into the field. A language field is also available to select a language from the drop down menu, to display the interface in.

Beginning with SFDC version 5.21, there are only two modules available in the Defect GUI. The first is the Record & Repair Defect screen. The second is the Knowledge Database. What modules are available at a particular device number are controlled by configuration in the SFDC GUI Administrator module.

 

Record & Repair Defect

Clicking on this button in the menu bar, a screen is displayed that looks somewhat like an emulator window. To begin, enter a serial number in the Serial Number field and click on the Retrieve button. The DC Status box displays information just like a data collector. If the serial number entered is at the correct location, the Menu Selection prompt will be displayed, and the part number field will display the part number of the entered serial number. Revision will also be displayed, if available. If the entered serial number is not at the correct location, a flow error will be displayed in the DC status box, followed by the Serial Number? prompt.

Once the Menu Selection? prompt is displayed, new defect and repair information can be recorded against the serial number. Two fields are always mandatory, the defect and reference designator. Other fields can be configured in the SFDC GUI Administrator module to be mandatory. Mandatory fields are indicated with a red “*” to the right of the field. To record a defect, click in the Defect box and enter the first character of a valid defect code. A fuzzy search capability exists and all matching defect codes will be listed. As you continue to enter characters, the list becomes shorter. Select the defect code to record against the serial number.

NOTE: Defect and Repair codes are managed in the SFDC GUI Administrator module. The defect and repair codes can be controlled using this configuration tool. Only those codes defined in the configuration will be displayed in the GUI.

A repair can be recorded at the same time a defect is recorded, by clicking on the Repaired: YES radio button. If NO is selected, then the Repair Code, Repair Note, and Last Repair Note fields are inactive. Clicking in the Repair Code field, again, a fuzzy search capability exists and as characters are entered, matching codes will be displayed in the drop down menu. After selecting a Repair Code, the Repair Note field can be used to enter notes about the repair. This information is what is used to make up the “Knowledge Base”. Also, if there was a previously recorded Repair Note, this will be displayed in the Last Repair Note field.

After all the information has been entered, click on the Record button to record the defect and repair information. The defect and repair information will be recorded against the serial number. The screen will also reset, allowing for additional defects and repairs to be entered. Clicking the Reset button will perform a “RESET” the same as at a data collector location. All entered information will be cleared from the fields. Clicking the End button will send an END command to SFDC. If a recorded defect was not repaired, the unit will fail to the appropriate location, as determined by the SFDC route. If all defects recorded were repaired, the unit will pass to the next location in the SFDC route. The serial number field will be blank and the DC Status field will be at the Serial Number? prompt. Clicking on the Release button will send a RLSE command to SFDC. The serial number will be released at the current scanning location. The serial number field will be blank and the DC Status field will be at the Serial Number? prompt. The Unit History button will open another window or tab and display the SFDC Unit History report.

 

Knowledge Database

Clicking on the Knowledge Database button in the menu bar will bring up the Knowledge Database screen. The only mandatory field is the Part Number field. Other fields that can be used for search criteria are Reference Designator, Defect Code, Repair Code, and Note. A starting and ending date can be selected. There is also a checkbox to Show Deleted Defect Notes. Enter the appropriate data and click on the Search button. Any matching records will be displayed. Clicking on the headers will change how the data records are organized.

 

Exit

Clicking on the Exit menu button will log out of the current location and return to the login screen for the Defect GUI, where another device number / operator number can then be entered.

Batch Process GUI

The Batch Process GUI is an application that provides a web page interface to perform Batch Processing operations. The functions that are available in the GUI are Create Batch, Split Batch, Merge Batch, Remove Unit/All Units, Add Component, and Add Sub Attribute. The GUI screens make it easier to identify the individual unit serial numbers that are in batches, and eliminates the need for running the batch commands at a data collector or through an emulator.

• Batch process allows for a batch serial number (module select type 7) to be created and unit serial numbers added to the batch.
• Unit serial numbers are tracked components of the batch serial number.
• The only tracked components of a batch serial number are the unit serial numbers. SFDC processing is performed using the batch serial number, and all activities are done against the batch serial number.
• Unit serial number processing cannot be “mixed” with batch processing. In order to perform a unique operation to an individual unit, the batch must be split into a batch of one and the individual unit added to the batch. Processing then occurs on the batch serial number.
• Batch serial numbers can be split into smaller batches, or merged to combine small batches of units into a larger batch.
• Upon completion of a batch, all the individual units are removed from the batch and moved to completed status. The batch serial number is marked as “Batch_OLDID”, status 63, and is no longer used again.
• Reporting capabilities have been created for MESWeb to allow all activities performed at the batch level to be reflected in the unit history.
• By default, the maximum batch size is 150 units.
• The batch serial number and unit serial numbers are the same part number.
• Shop orders are created for the unit serial numbers, not batch serial numbers.
• Unit serial numbers are created at the time the shop order is released.
• Multiple batch serial numbers can be created for a single shop order, but only unit serial numbers from a single shop order can be associated to a batch serial number. Mixing between shop orders, even for the same part number, is not allowed.
• Batch serial numbers can be manually created of generated from an algorithm. If using an algorithm to create a batch serial number, the algorithm type must be “general”.
• Split Batch serial numbers are expected to be in the format (parent_sn-nn) where parent_sn is the Source (parent) batch serial number and nn represents an incrementing number (01, 02, 03…).
• Batch serial number label printing is available in the GUI. A “BATCHLABEL” macro must be configured in the Setup Data Editor for print capabilities.

Upon clicking the Batch Process GUI icon in the Index page, a login screen is displayed. A workstation field is displayed allowing for the device number or unit number to be entered. Upon entering a number, a drop down menu will be display to allow scrolling and selecting a particular device number. You can also continue to enter characters directly into the Workstation field. A Badge field is also displayed. Enter/Scan your employee number into the field. A language field is also available to select a language from the drop down menu, to display the interface in.

After logging in, the main Batch Process GUI screen is displayed. Operations are selected from the main menu bar. The active workstation is displayed in red, on the right side of the menu bar.

 

Create Batch

To create a new batch serial number and associate unit serial numbers to the batch serial number, click on the Create Batch button on the menu bar. The Create Batch screen is displayed. Click in the Shop Order field and enter the first character(s) of a shop order to create a batch serial number for. A “fuzzy search” displays all matching shop orders for the entered characters. Select the shop order to create a batch serial number for.

NOTE: Only released shop order with unit serial numbers not associated to a batch will be available for use. Shop orders that do not have available units are not displayed.

Once a shop order has been selected, the available unit serial numbers are displayed in the box under the shop order. A label under the left box displays the number of unit serial number available in the Shop Order. This value only updates after a batch serial number has been created and units are associated to the batch serial number. On the top right side of the screen are the Batch Serial Number fields. A batch serial number can be created manually, or though the use of an algorithm. There is a check box to use an algorithm and a box to supply the algorithm number. If the algorithm check box is checked, the batch serial number field becomes inactive, not allowing for manual serial number entry. Manually enter a batch serial number, or check the algorithm check box and enter a valid algorithm number. The large box on the right displays the unit serial numbers to be added to the batch serial number. A label under the box displays the current count of unit serial numbers in the box.

NOTE: If manually creating batch serial numbers, SERIAL INPUT line(s) must exist in the SFDC Setup Data Editor to define serial masking and part number assignment.

There is also a print button to print out the Batch Serial Number on a label.

NOTE: In order to print a batch serial number label, a “BATCHLABEL” macro must be defined in the SFDC Setup Data Editor. The Macro command specifies the label type and print queue to use for printing a label. Refer to the Label Printing section of the SOP-5-I-MDS0009-C RA1 MDS SFDC Configuration for Label printing configuration.

In the middle of the screen are left and right arrow buttons. The double arrow buttons move all unit serial numbers from left to right, or right to left, depending upon the button. Individual or multiple unit serial numbers can be selected and moved using the single arrow buttons. Below the arrow buttons is a box to enter a batch quantity. Entering a number in this field, then selecting either Ascending or Descending and clicking on the single right arrow button, will associate the specified number of units from the shop order to the batch serial number.

NOTE: The batch quantity value cannot exceed the maximum batch size, or the number of units available in the shop order.

Once a batch has been defined in the GUI, clicking on the Commit button will create the batch serial number and add the defined unit serial numbers to the batch serial number in SFDC. As long as the Commit button has not been clicked, the batch has not been created and any changes can be made. There is also a Commit & End button. Clicking this creates the batch serial number, associates the unit serial numbers to the batch serial number and passes the batch serial to the next location, as defined by the SFDC route. To cancel creating a batch, click on the Cancel button. The View History button will display the SFDC Batch Serial Number unit history.

Split Batch

To split a batch serial number and associate unit serial numbers from the parent batch serial number to a new split batch serial number, click on the Split Batch button on the menu bar. The Split Batch screen is displayed.

NOTE: A batch serial number can be split into smaller batches, but at least 1 unit serial number must remain in the original batch. A split batch serial number cannot be created for a quantity equal to or greater than the parent batch serial number quantity.

In the top left of the screen is a field to select the Source (parent) Batch Serial Number. Click in the Source Batch Serial Number field and enter the first character(s) of a batch serial number. A “fuzzy search” displays all matching batch serial numbers for the entered characters. Select a parent batch serial number to split into a smaller batch quantity.

NOTE: Only batch serial numbers at the location(s) associated to the workstation currently logged into are displayed.

After selecting a batch serial number, the unit serial numbers attached to the batch serial number are displayed in the box on the left. A label is displayed under the box, defining the quantity of units in the batch serial number. On the top right side of the screen are the Target Batch Serial Number fields. A batch serial number can be created manually, or though the use of an algorithm. There is a check box to use an algorithm and a box to supply the algorithm number. If the algorithm check box is checked, the batch serial number field becomes inactive, not allowing for manual serial number entry. Manually enter a batch serial number, or check the algorithm check box and enter a valid algorithm number.

NOTE: The expectation for split batch serial numbers is to have the format (parent_sn-nn). The parent batch serial number makes up the first part of the split batch serial number, followed by a “-“ (hyphen) and then ascending number (01, 02, 03, …) for each split. If using an algorithm to create split batch serial numbers, the algorithm must be of type general and must be configured correctly to use the parent batch as a value, along with a constant (-) and incrementing number.

The large box on the right displays the unit serial numbers to be added to the split batch serial number(s). A label under the box displays the current count of unit serial numbers in the box.

NOTE: If manually creating split batch serial numbers, SERIAL INPUT line(s) must exist in the SFDC Setup Data Editor to define serial masking and part number assignment.

In the middle of the screen are left and right arrow buttons. Individual or multiple unit serial numbers can be selected and moved using the single arrow buttons. Below the arrow buttons is a box to enter a batch quantity. Entering a number in this field, then selecting either Ascending or Descending and clicking on the right arrow button, will associate the specified number of units from the Source Batch Serial Number to the Split Batch Serial Number(s).

Also on the top right is a check box to create multiple split batch serial numbers and a field to enter the quantity of split batches. Checking the multiple box and entering a value in the quantity field, will trigger the specified number of split batch serial numbers to be created, associating the unit serial numbers in the right box to the split batch serial numbers. For example: If 10 unit serial numbers are in the right split batch serial number box, and the quantity entered for the multiple quantity is 5, each split batch serial number will have two unit serial numbers associated to it. Creation of the Split Batch Serial Number(s) only takes place when the Commit button is clicked. There is also a print button to print out the Batch Serial Number on a label. To cancel the creation of a Split Batch Serial Number(s), click the Cancel button. The View History button will display the SFDC Batch Serial Number unit history.

NOTE: In order to print a batch serial number label, a “BATCHLABEL” macro must be defined in the SFDC Setup Data Editor. The Macro command specifies the label type and print queue to use for printing a label. Refer to the Label Printing section of the SOP-5-I-MDS0009-C RA1 MDS SFDC Configuration for Label printing configuration.

Merge Batch

To merge a batch serial number and associate unit serial numbers to a parent batch serial number, click on the Merge Batch button on the menu bar. The Merge Batch screen is displayed.

NOTE: The merge batch serial number command will only allow batch serial numbers from the same shop order to be merged. The location of the parent batch and the batch to be merged into the parent must be the same. There is no limit on the number of units that can be merged into a parent batch.

In the top left of the screen is a field to select the Source Batch Serial Number. Click in the Source Batch Serial Number field and enter the first character(s) of a batch serial number. A “fuzzy search” displays all matching batch serial numbers for the entered characters. Select a source batch serial number to merge into a larger batch quantity.

NOTE: Only batch serial numbers at the location(s) associated to the workstation currently logged into are displayed.

After selecting a batch serial number, the unit serial numbers attached to the batch serial number are displayed in the box on the left. A label is displayed under the box, defining the quantity of units in the batch serial number. On the top right side of the screen is the Target Batch Serial Number field. Click in the Target Batch Serial Number field and enter the first character(s) of a batch serial number. A “fuzzy search” displays all matching batch serial numbers for the entered characters. In the middle of the screen is a double right arrow button. Clicking on the right arrow button, will associate all the unit serial numbers from the Source Batch Serial Number to the Target Batch Serial Number. To complete the merge of the source batch serial number to the target batch serial number, click the Commit button. To cancel the merge of the source batch serial number to the target batch serial number, click the Cancel button.

 

Remove Unit / All Units

To remove a unit serial number or all unit serial numbers from a batch serial number, click on the Remove Unit button on the menu bar. The Remove Unit / All Units screen is displayed.

NOTE: Do not remove a unit to process individually. Split a batch and move the individual unit to a new batch serial number.

In the top left of the screen is a field to select the Batch Serial Number. Click in the Batch Serial Number field and enter the first character(s) of a batch serial number. A “fuzzy search” displays all matching batch serial numbers for the entered characters. Select a batch serial number to remove a unit or all units from.

NOTE: Only batch serial numbers at the location(s) associated to the workstation currently logged into are displayed.

After selecting a batch serial number, the unit serial numbers attached to the batch serial number are displayed in the box on the left. A label is displayed under the box, defining the quantity of units in the batch serial number. On the top right side of the screen is the Target Location field. Click in the Target Location field and enter the first character(s) of a location. In the middle of the screen are left and right arrow buttons. The double arrow buttons move all unit serial numbers from left to right, or right to left, depending upon the button. Individual or multiple unit serial numbers can be selected and moved using the single arrow buttons.

NOTE: Removing all units from a batch serial number will cause the batch serial number to be marked at status 63 (Old BatchID) and it will not longer be able to be used.

At the bottom of the screen are fields to enter a Defect Code and/or a Comment. Neither is required, but it is useful for providing information as to why a unit or units were removed from a batch. To complete the removal of a unit or units from a batch serial number, click the Commit button. To cancel the removal of a unit or units from the batch serial number, click the Cancel button.

 

Add Component (Add Unit)

To add a component (unit serial number) to a batch serial number, click on the Add Component button on the menu bar. The Add Component screen is displayed.

NOTE: Adding a component to a batch serial number is adding a unit serial number from a specified location to the batch serial number. The GUI screen utilizes the ADCMP3 command to perform this operation, allowing a unit serial number, at a location to be added into a batch. The unit serial number must be the correct part number.

In the top field, click in the Batch Serial Number field and enter the first character(s) of a batch serial number. A “fuzzy search” displays all matching batch serial numbers for the entered characters.

NOTE: Only batch serial numbers at the location(s) associated to the workstation currently logged into are displayed.

Select a batch serial number to add a unit serial number to. Unit serial numbers already added to the batch serial number will be listed in the table. In the next field select the Source Location where the unit serial number to be added is located. Click on the Add button and a new line in the table will be created. Enter the Serial Number of the unit serial number to add, enter the Reference Designator (UNITSN), and the Component Part Number. Click on the Save button to add the unit serial number to the batch.

NOTE: The Reference Designator for all unit serial numbers in a batch is UNITSN. The part number of the added Unit serial number must be the same as the part number of the batch serial number.

To cancel the addition of the unit serial number to the batch serial number, click on the Cancel button.

Add Sub Attribute

To add or replace an attribute for a unit serial number attached to a batch serial number, click on the Add Sub Attribute button on the menu bar. The Add / Replace Sub Attribute screen is displayed.

NOTE: An attribute table must exist to define the attribute names, masks, and group name (optional). The attribute table must be configured for a specific part number and it must be created for a location. The location does not have to be used in a route.

In the top left of the screen is a field to select the Batch Serial Number. Click in the Batch Serial Number field to select a batch serial number.

NOTE: Only batch serial numbers at the location(s) associated to the workstation currently logged into are displayed.

In the top right of the screen is a Command field. This is used to select the subatt command. There are four options:

SUBATT – Adds all attributes for the current part number.

SUBATT.LOC – Adds defined attributes for the current part number at a specified location.

SUBATT.GROUP – Adds attributes for the current part number matching the specified group name.

SUBATT.LOC.GROUP- Adds attributes for the current part number, at a specified location, matching the specified group name.

Depending upon the command selection, the Location and Group fields may be selectable. If using a command with the LOC parameter, select the location of the attribute table to use in the drop down menu. If using a command with the GROUP parameter, select an attribute group name, from the drop down menu.

After selecting the required items, select a unit serial number from the drop down list of Unit Serial Numbers. To add attribute values, click on the Add button. The Attribute Prompt and Attribute Name fields will be populated for the required attributes and the Attribute Data fields will be available to add attribute data for each available attribute definition.

NOTE: The attribute data must match the attribute data mask defined in the configuration.

To save the attribute data entered into the data field(s), click on the Save button. A message “Add Attribute successfully” will be displayed. In order to Replace and attribute, attribute data must exist already for the unit serial number. Click the Replace button. The Attribute Data fields will then be available to enter new attribute data. Click on the Save button to update the changes. Clicking on Cancel button will revert back to the original values.

 

Exit

To logout out or leave the current workstation, click on the Exit button in the menu bar. The Login screen will then be displayed, allowing the user to switch to a different workstation, if required.

Attributes

Attribute definitions are maintained in SFDC Configuration through MDS. See the Attribute Definition Maintenance section of the SFDC Configuration Manual for more information.

Attributes can be added to a serial number with the Add Attribute command (ATTADD) or Add Attribute by Group Name (ATTADDGRP). Attributes can be removed and replaced using the Remove Attribute command (ATTREMOVE) or Clear Attribute (CLEARATTRIBUTE). For definitions and descriptions for these commands, see the SFDC Generic Custom Command Appendix. These commands are executed as !!1 commands (per the command appendix), but are local SFDC commands in version 5.22 and higher.

For SFDC Version 5.22 and higher: The following local SFDC commands are available: ATTADD, ATTADDGRP, ATTREMOVE, CLRATT, and VERATT. These commands eliminate the need to execute the !!1 commands in MDS. Refer to the individual command descriptions in this document for more information.

Defect / Repair GUI (MES Portal)

Additional development of the Defect and Repair GUI has been moved to the MES Portal, in order to be able to add additional functionality. In order to utilize the Defect and Repair GUI functionality, an SFDC PC must be configured in the MES Portal and must be running SFDC 6.0 or higher.

The Defect and Repair GUI portlet provides for the following functionalities.

• Advanced defect recording with PTS integration for component validation. An entered reference designator is validated against the BOM in PTS, in order to insure that the component exists.
• Advanced repair recording with PTS integration for validation of replacement component validation. Based upon the reference designator, the component is validated against the BOM in PTS. A Material Barcode field is included in order to validate the replacement component, insuring the correct part number, manufacturer, valid data code, etc. are used.
• CAD file display, based upon scanned serial part number. GenCAD file is currently the only supported format. Portlet for uploading and managing uploaded CAD files is provided. Multiple layers of the CAD drawing can be displayed using a list of selectable check boxes.
• Component look up in CAD drawing by reference designator. Reference designator specified as part of a recorded defect or repair is automatically displayed, but using Recorded or Repaired switches. Reference designator can also be looked up prior to defect/repair recording.
• Web service link to SFDC Measurement for displaying parametric records for an entered serial number. The Measurement server must be configured in MES Portal in order for records to be accessed. All available records found for the scanned serial number, are displayed.
• Top 5 defects and repairs based upon part number of scanned serial number. Display is based upon defects/repairs entered by the GUI in the Portal. Historical data from SFDC is not used. Chart display or list of defect/repair codes with description.
• Tech Notes field for recording of troubleshooting information. Search capability also exist for Tech Notes.

 

Employee Validation

The Employee Validation capabilities of SFDC are designed to handle process control through the validation of employee numbers and passwords that have specified certification for a specified process or processes. Employees are configured in the system, processes to be controlled by Employee Validation are defined and then certificates are created with associated class or classes and the training duration is specified. All configuration is performed in MDS and then downloaded to the SFDC PC, using the emvdnld (Employee Validation download) command. When enabled, EV checks an employee number when logging into any device with a controlled process, validates the employee password, and certifications that are not expired, that the employee is assigned to. If a serial number is scanned at a controlled process, and the employee has the required certification, the serial number is allowed to be acted upon. If the employee does not have the required certification, an error is displayed. Locations without EV control allow for normal SFDC scanning. Multipass devices which have both EV controlled processes and non-controlled processes, require an employee to be in the EV system in order to log into the multipass device, and perform non-controlled processes.

Options Lines

There are 4 option lines that can be configured as part of the setup data editor for the SFDC PC. All other Employee Validation configuration is done through the Employee Validation module in MDS.

• OPTIONS EMPVAL VALIDATION=YES - This options line enables Employee Validation on the SFDC PC. In order to correctly control processes, a successful emvdnld command has to run in order for the EV configuration to be downloaded to the SFDC PC. This is not part of the standard sfdcdnld. If not used, or set to NO, there is no change in processing.

• OPTIONS EMPVAL_PROD PRODUCT=pbm - This option line is used to specify a product mask (pbm) for products to be controlled by Employee Validation. The mask can be a specific part number, somewhat specific to limit control to a group of products, or made generic to include all part numbers. This option line is mandatory. If EV is to be used, some kind of product mask must be defined and the option line enabled. PRODUCT=pbm is mandatory. Where pbm is the product MASK defining the product number to be controlled by Employee Validation.
  • This options line has been enhanced in SFDC 6.1 for use with the new Part/Process Certificates in MDS 14-5. There are new tables that tie a certificate to a part number, product family or customer code. The pbm should be generic to include all part numbers (i.e. PRODUCT=@.(19)@) when using the new Part/Process Certificates, as the part number(s) defined for the process are included in the class and certificate records downloaded from MDS 14-5. If not using the new Part/Process Certificates in MDS 14-5, or higher, the standard product mask rules apply.

• OPTIONS EMPVAL_LOGOUT AUTO_LOGOUT_SHIFTEND=YES - This option line is optional and if enabled, will automatically logout all devices that have an Employee Validation controlled process assigned. The logout time is determined by the shifts defined in the Miscellaneous Configuration module in MDS.

• OPTIONS EMPVAL_LOGOUT GLOBAL_TIME=300 - This option line is optional and if enabled, will automatically logout all devices that have an Employee Validation controlled process assigned. After the defined amount of time has passed without any activity (scanning) has passed the device will be logged out. The time value is in seconds.

High Level Command Control

When using Employee Validation in SFDC v6.1, with MDS 14-5, it is possible to restrict the use of multiple predefined “high level” SFDC commands. When High Level Command Control is enabled, the use of the predefined local commands is restricted from use by the “Operator” employee type (defined by employee in MDS 14-5 and higher). The Trainer, Supervisor and Debug/Rework employee types are able to run all commands without restriction. Restriction is enforced when commands are run manually, as well as by an AUTOCMD and MACRO. There are no restrictions when a predefined command is run by MDS in a !!command.

A default file (included in the SFDC package) stored on the local SFDC PC contains the predefined commands. The predefined commands are as follows: CHGID, CHGPN, CHGRV, RCRPR, RMCMPALL, RMCMP, RPCMD2, MOVE.

High Level Command Control functionality is disabled by default and requires an administrator to enable it to restrict the use of high level commands. To enable this control, edit the /sfdc3/sfdcinit file on the SFDC PC to HIGH_LEVEL_COMMAND=YES. When disabled (HIGH_LEVEL_COMMAND=NO) there is no restriction placed on the predefined commands.

 

HPU/Cycle Time

The HPU/Cycle Time functionality, when enabled, sends time stamp information to MDS to store. This data is replicated to MESWeb to allow for reporting capabilities. Data is collected for every process name. There is a single options line defined in the Setup Data Editor which controls whether the HPU/Cycle time data collection is enabled or not, and includes a product mask for defining which products data is collected for. The product mask can be specific to limit the product to a single product, less specific to allow for a group or products, or generic to allow all products to be included.

OPTIONS HPU ENABLE=YES PRODUCT=@.(19)@

NOTE: This functionality is only available in SFDC version 5.22 or greater.

Time stamp information is sent to MDS at the initial scan of a serial number, when the RLSE (release) command is entered, when a RESET command is entered, or for PASS, FAIL, and MOVE operations.

NOTE: If a scanning location does not have an assigned process name, then time stamp information will not be collected. All time stamp information is gathered by process name.

The primary usage for the HPU/Cycle Time functionality is to collect production cycle time data, by part number for all processes. Reports can be generated in MESWeb to show actual and average process cycle times by part number. Data is collected for “hands on” time, when a serial number is being operated upon, but is also collected for the entire time a serial number is in a process, supplying “unattended” time. The information can be used by plants for quoting purposes, cycle time improvement analysis, and automated process cycle time measurements.

 

Multi-threading

Multi-threading is a new feature added in SFDC 6.0. It requires the MDS be at 14-4 or higher. Multi-threading, when enabled, creates multiple socket connections to MDS when required. Typical operation between the SFDC and MDS server requires only a single socket connection. When multi-threading is enabled, and the default socket connection (socket1) is busy, SFDC will create multiple socket connections to MDS in order to continue process transactions in a timely fashion, rather than waiting for the current socket connection to become available. The majority of transactions will continue to be processed using the initial socket connection and unused socket connections will be killed, after a period of inactivity. Multi-threading provides a far greater communication throughput between the SFDC PC and MDS server, using the existing hardware.

 

MFG Hold

With the release of MDS version 14-4, a new comment field was added in the MFG Hold configuration screen. The Comment field allows a comment to be stored, as to why the MFG Hold is being created. In SFDC 6.0 and higher, this new comment field is used by SFDC to automatically add a comment to any scanned serial number that is affected by the MFG Hold. The comment data is the comment stored in the comment field in MDS. If the comment field is blank, then no comment will be recorded against scanned serial numbers affected by the MFG Hold.

 

Non-Serialized Batch Processing

In SFDC 6.0, the ability to batch and process non-serialized units has been developed. All non-serialized batch processing is handled by shop orders. A shop order is released for a non-serialized batch. MDS creates a batch serial number using the shop order number. By default, the batch size is equal to the shop order quantity. All SFDC scanning is performed by scanning the shop order number.

In MDS, in Part Maintenance, insure that the non-serialized part number exists. No serial number algorithm should be assigned to the part. Insure that the “create skeletons” check box is not checked. The quantity field is 1 by default. If the dpart.qty field = 1, then MDS will use the shop order release quantity as the batch quantity. If the dpart.qty field > 1 then this is used to defined the batch quantity. For example, if dpart.qty=100, then batches will be created in quantities of 100.

When releasing the shop order in MDS, there is a check box for a non-serialized batch. This check box should be checked. This tells MDS to create the batch serial numbers based upon the shop order. Either a full or partial release can be performed. Per the dpart.qty rules defined above, if dpart.qty = 1 then the batch quantity will be the release quantity. This is true also if a partial release is performed and the quantity releases is less than a defined batch quantity. The serial number generated will be the shop order number. Subsequent batch serial numbers are in the format shop_order_number-nnn.

All SFDC scanning is done by scanning the shop order number, regardless of the number of batch serial numbers created or that exist. Scanning of individual batch serial numbers is not required. If there is only a single batch serial number at any location, SFDC scanning works just like any individual unit scanning. If there are multiple batch serial numbers at a scanning location, or released and ready to be started, SFDC will display the “Batch QTY?” prompt. Depending upon the quantity entered, SFDC will split a batch, if the entered quantity is less that a batch quantity. If the quantity is some multiple of batch quantities, then the batches will be merged together. Scanning END passes the entered quantity forward to the next location. If a single batch is at a scanning location, and only a portion of the batch is to be passed forward, a “manual” split must be performed. This is accomplished using the SPLTNBSN command. Refer to the command specifics in this document for more information.

Recording defects works in a similar fashion. At the Menu Selection? prompt, scanning the record defect command (RCDFC) will prompt for defect code, then defect quantity. Defect quantity in non-serialized batch is the number of units that fails for the entered defect code, not the number of defects on a particular unit. For example, if the batch serial number contains 10 units, and the defect quantity is enter as 2, then 2 units will be split off into a separate batch and failed. The user has the ability to repair the units at the time the defect is logged, preventing the defect units from being split off into a separate batch, and failing to the fail to location defined in the route.

Repairs work the same way. When repairing a defect against a batch serial number, the user will be prompted for quantity. If the entered value is less than the batch quantity, another split will occur, leaving the remaining quantity at the fail location.

With Oracle interfaced orders, WIP moves and completions are reported on the quantity in the batch when it passes through a mapped location or to finished status.

With Non-serialized batch processing comes some configuration rules that must be followed. Because all scanning is done using just the shop order number, these rules are required in order for SFDC to work correctly.

• Only a single source location can be used in a route step. Accepting from more than one source location is not allowed because SFDC cannot determine which batch to use, assuming there are batches in each source location.
• Multi-pass device numbers are not allowed for route locations used in non-serialized batch routes. SFDC cannot determine which location to perform the scan operation if there are batch serial numbers at multiple locations and those locations are assigned to a single device number.
• Starting multiple batch serial numbers (status 15) requires that only valid batch quantities are entered to the Batch Qty? prompt. The Invalid Entry message will be displayed, if the entered quantity does not match a batch or combination of batch serial number quantities. This only applies to status 15 batch serial numbers.
• All scanning should be done using just the shop order number. No scanning of the individual batch serial numbers (shop_order_number-nnn) should occur.
• The OPTIONS SHOW_SDE_LOC ENABLE=YES option line should be enabled and downloaded to the SFDC PC.

 

Shop Order

Shop orders are created and maintained in SFDC Configuration through MDS. See the Shop Order Control Usage manual for more information.

When a serial number is scanned, the system checks to see if it is part of an existing shop order. The unit is updated as required by the MDS configuration.

Shop order assignment is recorded in the serial data table and can be seen when using the View History function. See View History in the Data Collection section.

A unit shop order can be changed (if permitted) by using the Change Shop Order (CHGSO) custom command. For definition and description of this command, see the

SFDC Generic Custom Command Appendix

 

Containerization and Lot Tracking

Containerization tracks the placement of serial numbers in a container, box, or carton. SFDC supports only one level of container or lot. A unit can be assigned to both a lot and a container. MDS can be used to provide multiple levels of containerization.

If a container is opened at a data collector, any serial number scanned is assigned to the open container serial number, provided the container is not full and the unit serial number has the following:

• No outstanding defects
• Part number
• Revision

By default, the units in a container must have the same revision if any and the same product type or part number. Container quantities are defined by part number. Once a unit is containerized, it cannot be scanned at any other data collector unless it has been removed from the container.

NOTE: In SFDC version 5.22 and higher, the option to allow multiple revisions of the same part number to be added to a container exists. Use the following OPTIONS line to control or ignore revision when adding to a container.

OPTIONS CNTNR_CHECK REVISION=YES/NO

NOTE: The first unit added to a container or lot determines the revision of all units allowed.

Containerization assumes that the containerization module is used at a location that passes to the Complete Location (Finished Status). In other words, the containerization data collector must pass to a location with a Finished Status (30).

Lot Tracking tracks the assignment of unit serial numbers to lots. While a lot is open at a data collector, any serial numbers scanned at this data collector are attached to the lot serial number if the units have not failed and meet all lot requirements. Lot requirements include having the same revision if any and the same product number and finishing the product‘s assigned route. The lot cannot be at maximum quantity.

There are two methods of Containerization and Lot Tracking - pre-printed serial numbers and automatically generated serial numbers.

NOTE: An open container has a status of 34 and a closed container has a status of 35.

 

Setup Information

The following information is required to setup Containerization and/or Lot Tracking:

- Information by part number for units boxed with SFDC Containerization.

• COPICS Part Number
• Box or lot capacity by part number.
• Revision if required.

- Considerations for formatting and station location.

• Container or lot serial number format. Recommend B(10)n.
• Box (container) label formatting and printing requirements.
• Packing list (if needed) formatting and printing requirements.
• Lot serial number listing formatting and printing requirements.
• Scanning location.
• Printing method such as print server, serial drop, or with SFDC data collector.

 

Command Barcodes

The following barcodes are used for both pre-printed and automatically generated serial numbers.

• NEWCNTNR or NEWLOT - Creates and opens a new container or lot.
• OPENCNTNR or OPENLOT - Opens an existing container or lot.
• CLOSECNTNR or CLOSELOT - Closes an open container or lot.
• RMVFRMCNTNR or RMVFRMLOT - Removes a serial number from an open container or open lot.

 

Sample Workflows

The following sample workflows can be updated depending on whether performing Containerization or Lot Tracking. Refer to the Command Barcodes section for the correct barcode to use. In some cases, the prompts may be different also.

NOTE: Container type is always 100. Lot type is always 99.

 

Creating and Filling a New Container

Prompt:	Serial Number?
Action:	Scan NEWCNTNR.
Prompt:	Container Type?
Action:	Scan the container-type barcode if not included as a macro in the NEWCNTNR barcode. Example macro with container type included: NEWCNTNR$100
Prompt:	Product Number?
Action:	Scan the product number barcode for the product being boxed if it was not included as a macro in the NEWCNTNR barcode or the container type barcode. Example macro combining all three steps: NEWCNTNR$100$COPICSPART# If running preprinted container serial numbers, place a pre-printed container serial number barcode label on the box.
Prompt:	Container Num? If running automatically generated container serial numbers, this prompt is not displayed.
Action:	Scan the container serial number barcode. If running automatically generated container serial numbers, scan a command to print the container serial number label. This barcode is important should the container need to be closed and reopened before the final label and packing slip print.
Prompt:	Serial Number?
Action:	Scan serial number barcode on units being boxed. When finished, scan END if the station is not configured to end automatically.

 

Closing an Open Container

Prompt:	Serial Number?
Action:	When the container is full, scan CLOSECNTNR. NOTE: The Systems Department recommends that any printing required be done at this point with macro barcodes combines with CLOSECNTNR. For example: !!2BOXGENZ.$CLOSECNTNR

 

Opening an Existing Closed Container

Prompt:	Serial Number?
Action:	Scan OPENCNTNR.
Prompt:	Container Num?
Action:	Scan the container serial number barcode on the box.

 

Removing a Unit from a Container

Prompt:	Serial Number?
Action:	Scan RMVFRMCNTNR.
Prompt:	S/N to Remove?
Action:	Scan the serial number barcode for the unit being removed from the container.

NOTE: The RMVFRMCNTNR barcode must be scanned before each unit serial number to be removed from the container.

 

Creating and Assigning Serial Numbers to a New Lot

Prompt:	Serial Number?
Action:	Scan NEWLOT.
Prompt:	Product Number?
Action:	Scan the product number barcode for the product type (type is 99 for Lots) being added to the Lot if it was not included in the macro in NEWLOT or the lot type barcode. Example macro combining both steps: NEWLOT$COPICSPART#
Prompt:	Lot Num?
Action:	Enter the lot serial number. Note: A keyboard is useful for this step. For automatically generated lot serial numbers, this prompt is not displayed.
Prompt:	Serial Number?
Action:	Scan the serial number barcode on units being tracked within the lot.

 

Data Collection

There are several methods for entering data into the Shop Floor Data Collection system. There are physical data collectors. These are the CS9400 Data Collector, which communicates via serial communication to the PCC card installed in the SFDC PC and the NetDC, which is the new generation of data collector, that communicates to SFDC over Ethernet. AutoSFDC is an application that allows for direct communication to SFDC via TCP/IP communication. Typically AutoSFDC is used to allow a tester to communicate data collection information directly without an operator having to enter the data into the system. AutoSFDC also allows the use of a software emulator which is a program that replicates a physical data collector, but runs on a computer. There are a couple stand-alone emulator programs used by various plants. They are designed to run on a Windows computer and are an application that is installed and configured to talk to a specific SFDC PC and device number. There is also a Data Collector GUI built into SFDC. This is a web-based application that is run using a web-browser. The advantage to this application is that any machine with a web browser can use it, therefore it is not limited to the Windows operating system. In addition, there is no application to install. Because the application is hosted on the SFDC PC, the only configuration is selecting the device id or unit number. This is done when logging into the application.

The standard data collection procedure for any workstation is as follows:

• Physical data collectors are normally left on. If using a physical data collector that is off, turn on the data collector. A prompt displays on the LCD.
• Emulators must first be launched, as they are a program.. Launch the emulator program, select the device id or unit to log data into. A prompt will not be displayed on the screen until an action is taken. Physical data collectors “poll” for communication to the SFDC PC, therefore they receive a response from the SFDC, thereby allows a prompt to be displayed. A carriage return or Enter command will initiate communication with the SFDC PC, and a prompt will be displayed.
• Enter the requested data item. Scan a single barcode, scan several barcodes from the Alpha-Numeric barcode keypad, or type in the data using the keyboard (101key).

° SFDC validates the data and displays the next prompt. There are several ways of knowing whether the scanner has read the barcode:

° A beep issues from the scanner.° The green decode light appears.° The laser light turns off.° The scanner displays that the operation was performed and it is waiting for the next operation.

 

• If SFDC rejects the data, it displays an error message on the LCD/Display and redisplays the original prompt.

[[File:]]

The following subsections describe the standard data collection commands and their prompts and error messages.

Employee Login and Logout

Employee Login is a required task when the system is first turned on, restarted, or an operator previously logged out. Logout removes the employee ID number from the current data collection location. The location returns to the Employee Login prompt.

 

Prompt:	Employee No.?
Action:	Enter employee number (4-12 numeric characters) **
Prompt:	Password?
Action:	Enter password.

  **

By default, the employee number must be 4-12 numbers. If the EMPLMASK option is configured, or the DEVICE NUM lines have EMPLOYEE or EMPLMASK entries, the 4-12 characters can be alphanumeric.

NOTE: If the Employee Login prompt is not displayed, scan LOGOUT to logout the previous employee.

When both employee number and password are validated in SFDC, SFDC proceeds to the Get Serial Number task.

If incorrect data is entered at either prompt, the data collector displays the following messages:

 

Error Message:	Invalid Entry
Meaning:	The employee number was not recognized or the password was invalid.
Error Message:	Login failed
Meaning:	The employee number or password was not acceptable.

 

Custom Commands

Custom commands can be executed using two methods:

At the Menu Selection prompt:

These commands operate against the current scanned serial number. This type of command has a barcode consisting of the characters !!1 (referred to as bang-bang-one) followed by the name of the custom command. The name may be followed by a period and one or more parameters. Parameters are separated by a period. For example:

!!1ATTREMOVE.c_remove.a_name

At the Serial Number prompt:

These commands do not check product flow against a route. A custom command issued at the Serial Number prompt consists of the characters !!2 (referred to as bang-bang-2) followed by the name of the custom command and any required parameters. For example:

!!2ATTREMOVE.c_remove.a_name

Refer to the SFDC Generic Custom Command Appendix and Master Command List for descriptions and usage of these commands.

Serial Number Prompt

Serial Number is a required task when the last entry received was END. SFDC also required a serial number after logging in if the SFDC PC was restarted. SFDC only recognizes serial numbers in the formats defined in Setup Data Editor of SFDC Configuration.

 

Prompt:	Serial Number?
Action:	Enter one of the following: The serial number label on the unit being processed One of the special barcode commands designed to scanned at the serial number prompt The special LOGOUT code

If the LOGOUT code is entered, SFDC returns to Employee Login.

If a special command is scanned, the data collector returns to the Serial Number prompt after processing the command.

If creating a new serial number record, the following prompts may display on the LCD if required by product configuration:

 

Prompt:	Product Number?
Action:	Enter the product number of the unit being processed. NOTE: This is required if the serial number format is not defined for single product usage in the SFDC Configuration.
Prompt:	Bds/Panel= nnn?
Action:	Enter YES to accept the displayed value of boards on the panel, or enter the correct number of boards for the panel.

When all required data is entered, SFDC proceeds to the Add Subassemblies or Menu Selection task.

If incorrect data is entered at any prompt, the data collector displays the following messages:

 

Error Message:	Invalid Entry
Meaning:	The entered data was invalid.
Error Message:	Serial Not Found
Meaning:	The entered serial number is not in the database of active units.

Error Message:	Network Is Down
Meaning:	SFDC is unable to communicate with the network database server
Error Message:	Flow Error- xxxx
Meaning:	The entered serial number should be at the location indicated by xxxx, not at this workstation.
Error Message:	Login Timeout
Meaning:	Time between scans exceeded timeout length as defined in the SFDC Configuration.
Error Message:	No Route Assigned
Meaning:	The entered serial number is not assigned to a route.
Error Message:	Status Error
Meaning:	The entered serial number has a status unacceptable for scanning.
Error Message:	In Use At xxxx
Meaning:	The entered serial number is in use at another location.
Error Message:	Archived Serial#
Meaning:	The entered serial number has been archived.

 

Menu Selection

Menu Selection provides access to several standard subcommands in SFDC. Each of these subcommands is discussed below.

 

Prompt:	Menu Selection?
Action:	Enter one of the menu selections described in the sections that follow or a custom selection designed specifically for that location.

SFDC proceeds to the next task for the Menu Selection entered.

If incorrect data is entered at the Menu Selection prompt, the data collector displays the following messages:

 

Error Message:	Invalid Entry
Meaning:	The entered data was invalid.

 

Add Comment (ADCOMMENT)

The Add Comment command adds a comment to a serial number at a data collection location. After scanning the ADCOMMENT barcode, SFDC prompts for Comment Text. The comment can be up to 88 characters in length.

 

Add Components (ADCMP)

The Add Components command adds components when one or more was not installed during the initial Add Components process. When this command is scanned, SFDC compares the entry with the Assembly Table. If all components are installed, SFDC returns to the Menu Selection prompt. This command must be used at the station configured in the assembly table.

 

Prompt:	< Defined in Assembly Maintenance>?
Action:	Enter the identifying number of the component to add, NEXT, or MENU.

NOTE: The prompts displayed are configured in SFDC Assembly Maintenance. See the SFDC Configuration Manual for more information.

If NEXT is entered, SFDC skips this component and proceeds to the next one or goes on to the Menu Selection task.

If MENU is entered, SFDC goes to the Menu Selection prompt.

If a valid component is entered, SFDC records the component. If more components need to be added at this location, SFDC displays the prompt for the next component. Otherwise, it proceeds to the Menu Selection prompt.

If incorrect data is entered at any prompt, the data collector displays the following messages:

 

Error Message:	Invalid Entry
Meaning:	The entered data was invalid.
Error Message:	Unit Not Valid
Meaning:	The component to be added is tracked and not in the correct location.

 

Add Component 2 (ADCMP2)

The Add Component 2 command adds components without assembly records. Inputs needed are reference designator, component part number, and component ID. A new component ID record is created without regard to assembly records.

NOTE: This command cannot be used for tracked components.Also, if there was an existing component record with the same referencedesignator, it is marked as REPLACED, even if it were associated with an assembly record.

There are two ways to run this command:

• At the Menu Selection prompt, enter ADCMP2. The following prompts display:

 

Prompt:	Ref Designator?
Action:	Enter the reference designator for the component (up to 22 characters).
Prompt:	Component Part#?
Action:	Enter the component part number (up to 22 characters) or N/A if there is no part number associated with the component.
Prompt:	Component ID?
Action:	Enter the component ID (up to 22 charaters)

• At the Menu Selection, enter the following macro command line: ADCMP2$rrrrrrrr$ppppppp$iiiiiiiiii where rrrrrrrr is the reference designator, ppppppp is the part number (or N/A), and iiiiiiiiii is the component ID.

 

Add Tracked Component (ADCMP3)

The Add tracked component command is not a batch specific command. It can be used with unit serial number processing as well as batch processing. The ADCMP3 command can perform two different operations, add or replace. The add functionality is used in batch processing to add a unit serial number to an existing batch. While the replace functionality will work with batch processing, it is not recommended to use this command for replacing a unit serial number (See the Note below). The replace functionality is used in unit processing where a tracked component needs to be replaced from a specified location, without an assembly table to control the addition of the component. The add functionality in unit processing is to add a new tracked component with the entered reference designator.

NOTE: Use of the ADCMP3 command in batch processing has some very specific implications. In batch processing, the only tracked components in the batch are the unit serial numbers. All unit serial numbers have the same reference designator (UNITSN). If the R – Replace option is used in batch processing, only the first unit serial number will be replaced, because the command replaces the component id of the first matched reference designator. When the R – Replace option is used the replaced tracked component is placed at the location where the operation was performed.

 

Prompt:	Serial Number?
Action:	Enter the batch serial number.
Prompt:	Menu Selection?
Action:	Enter the ADCMP3 command.
Prompt:	Add or Replace Comp?
Action:	Enter A to add a tracked component or R to replace an existing tracked component.
Prompt:	Ref Designator?
Action:	Enter a reference designator for the component. If the A (add) option was selected, a new component will be added with the specified reference designator. In batch processing, the reference designator prompt is not displayed because all tracked components have the same reference designator (UNITSN). Unit S/N n/n will be displayed followed by the Location? prompt. The first n represents the current batch quantity and the second n represents the new quantity after the addition. If the R (replace) option was entered, the command will look for the first matching reference designator and replace the component id with the new entered component id. If a matching reference designator cannot be found, the component id will be added, with the specified reference designator.
Prompt:	Location?
Action:	Enter a valid location name (XXXX) where the tracked component is to be added.
Prompt:	Component ID?
Action:	Enter the component id (serial number) of the tracked component to add
Prompt:	Menu Selection?
Action:	The tracked component has been added to the active serial number. Entering END will pass the active serial number to the next location defined in the route. Entering RLSE will leave the active serial number at the current location. All normal SFDC operations can now be performed.

SFDC will prompt for the required pieces of information in order to create the split batch and assign unit serial numbers based upon the specified parameter. If incorrect data is entered at any prompt, the data collector displays the following messages:

 

Error Message:	Invalid Entry
Meaning:	The entered value does not match the required data.
Error Message:	Invalid Location
Meaning:	The entered location is not a valid location.
Error Message:	Wrong Location
Meaning:	The component id entered could not be found at the specified location.

 

Apply MEO (ADMEO)

The Apply MEO command attaches a Manufacturing Engineering Order (MEO) number to the unit at its current location. It is permanently recorded in the Unit History and cannot be removed.

 

Prompt:	MEO Number?
Action:	Enter the MEO number (1 to 20 alphanumeric characters) or the special MENU barcode.

If an MEO number is entered, SFDC records the MEO and returns to the Menu Selection prompt.

If MENU is entered, SFDC returns to the Menu Selection prompt.

If incorrect data is entered at any prompt, the data collector displays the following messages:

 

Error Message:	Invalid Entry
Meaning:	The entered data item was less than 1 or more than 20 characters, or it was not the MENU barcode.

 

Add Attribute (ATTADD)

The Add Attribute command adds attributes for the current location or process name to the active serial number. Configuration must be setup in MDS for either the location or process name. The attribute definition in MDS does not have to have a specified part number. All attribute names defined in the attribute definition will be prompted for.

NOTE: This command is only available in SFDC version 5.22 or greater. Earlier versions of SFDC must use the !!1 MDS version of the command.

 

Prompt:	Serial Number?
Action:	Scan/Enter a serial number.
Prompt:	Menu Selection?
Action:	Scan/Enter the ATTADD command
Prompt:	All attribute names listed in the attribute definition for the current location/process name are prompted for.
Action:	Scan/Enter attribute values for each prompted attribute name.
Prompt:	No Attribute Needed Menu Selection?
Action:	Scan/Enter a next SFDC command.

If incorrect data is entered at any prompt, the data collector displays the following messages:

 

Error Message:	Invalid Attribute Value!
Meaning:	The entered attribute data did not match the attribute data mask as defined in the SFDC Configuration. See the SFDC Configuration Manual for more information.

 

Add Attribute by Group (ATTADDGRP)

The Add Attribute Group command adds only attributes that match the group name. The attribute definition must be at the current location or process name where the active serial number is scanned. Configuration must be setup in MDS for either the location or process name. The attribute definition in MDS does not have to have a specified part number. Only attribute names that match the specified group name in the attribute definition will be prompted for.

NOTE: This command is only available in SFDC version 5.22 or greater. Earlier versions of SFDC must use the !!1 MDS version of the command.

NOTE: The format for an attribute name which include a group name is:

Group_name|attribute_name (the group name and attribute name are separated using the “|” pipe character).

NOTE: To automate the attaddgrp command, use the “$” command as a separator (ATTADDGRP$group_name).

 

Prompt:	Serial Number?
Action:	Scan/Enter a serial number.
Prompt:	Menu Selection?
Action:	Scan/Enter the ATTADDGRP command
Prompt:	Group Name?
Action:	Scan/Enter a Group Name
Prompt:	All attribute names matching the group name are prompted for.
Action:	Scan/Enter attribute values for each prompted attribute name.
Prompt:	No Attribute Needed Menu Selection?
Action:	Scan/Enter a next SFDC command.

If incorrect data is entered at any prompt, the data collector displays the following messages:

 

Error Message:	Invalid Attribute Value!
Meaning:	The entered attribute data did not match the attribute data mask as defined in the SFDC Configuration. See the SFDC Configuration Manual for more information.

NOTE: If the entered group name does not match any defined group name in the attribute definition, the “No Attribute Needed” message is displayed followed by the Menu Selection prompt.

 

Remove Attribute (ATTREMOVE)

The Remove Attribute command removes only one attribute at a time. The command will, by default, expect replacement attribute data to be entered. To remove the attribute data and not replace it, the RMVATT command is scanned/entered when the prompt for the new attribute data is displayed.

NOTE: This command is only available in SFDC version 5.22 or greater. Earlier versions of SFDC must use the !!1 MDS version of the command.

NOTE: To automate the attribute remove command, use the “$” command as a separator (ATTREMOVE$attribute_name$RMVATT).

 

Prompt:	Serial Number?
Action:	Scan/Enter a serial number.
Prompt:	Menu Selection?
Action:	Scan/Enter the ATTREMOVE command
Prompt:	Attribute?
Action:	Scan/Enter an Attribute Name (must include the group name, if there is one “group_name|attribute_name”) or scan NEXT to step through though added attributes until the prompt for the attribute name to remove is displayed.
Prompt:	The attribute name prompt is displayed.
Action:	Scan/Enter a replacement attribute value for the prompted attribute name, or scan/enter the RMVATT command to remove the attribute data without replacing.
Prompt:	Replaced (if replacement attribute data entered) Removed (if RMVATT command entered) Menu Selection?
Action:	Scan/Enter a next SFDC command.

If incorrect data is entered at any prompt, the data collector displays the following messages:

 

Error Message:	Invalid Attrib!
Meaning:	The entered attribute name did not match any attribute names defined in the SFDC Configuration. See the SFDC Configuration Manual for more information.
Error Message:	Invalid Attribute Value!
Meaning:	The entered attribute data did not match the attribute data mask as defined in the SFDC Configuration. See the SFDC Configuration Manual for more information.

 

Change Serial Number (CHGID)

The Change Serial Number command changes the serial number of a unit at the data collector. The new serial number must not yet exist in the db, and must be a valid format for the unit product type as defined in SFDC Configuration.

 

Prompt:	New Serial No.?
Action:	Enter the new serial number.

If a valid serial number is entered, SFDC changes the serial number and records the change in the unit history. The old serial number will have just an ‘old serial number’ activity in its history.

If incorrect data is entered at any prompt, the data collector displays the following messages:

 

Error Message:	Invalid Serial#
Meaning:	The entered serial number was not valid for the unit‘s product type as defined in SFDC Configuration. See the SFDC Configuration Manual for more information.

 

Change Product Number (CHGPN)

The Change Product Number command changes the product number of a unit at the data collector. The new product number must be a valid product number as defined in the SFDC Part Table.

 

Prompt:	New Product #?
Action:	Enter the new product number.

If a valid product number is entered, SFDC changes the product number and records the change in the unit‘s history.

If incorrect data is entered at any prompt, the data collector displays the following messages:

 

Error Message:	Invalid Prod #
Meaning:	The entered product number was not valid for the unit product type as define in SFDC Part Table.

 

Change Revision (CHGRV)

The Change Revision command changes the revision number of a unit at the data collector. The new product revision must match either the ASKFORREV parameter or the REVISION parameter as defined in SFDC Configuration. See the SFDC Configuration Manual for more information.

 

Prompt:	New Revision?
Action:	Enter the new rrevision.

If a valid revision number is entered, SFDC changes the revision number and records the change in the unit history.

If incorrect data is entered at any prompt, the data collector displays the following messages:

 

Error Message:	Wrong Revision
Meaning:	The entered data did not match the revision mask set by the ASKFORREV parameter or the specific revision set by the REVISION parameter.

In SFDC version 6.0 and greater, there is an OPTIONS line, OPTIONS CHGRV_ADMEO_ADCOMM ADMEO=YES/NO ADCOMMENT=YES/NO that will allow for automatically running the ADMEO and/or ADCOMMENT commands as the result of a CHGRV command. This functionality allows a deviation or ECO number to be recorded (ADMEO) and/or a reason (ADCOMMENT) for why the revision change was performed.

Clear Attribute (CLRATT)

The Clear Attribute command can remove one or more attributes at a time. The command supports the use of the “*” wildcard character for matching multiple attribute names, including group names. The command has 1 parameter, L or R, which either leaves attribute data matching the supplied attribute name(s) or removes attribute data matching the supplied attribute name(s).

NOTE: This command is only available in SFDC version 5.22 or greater. Earlier versions of SFDC must use the !!1 MDS version of the command.

NOTE: To automate the clear attribute command, use the “$” command as a separator (CLRATT$L/R$attribute_name*).

 

Prompt:	Serial Number?
Action:	Scan/Enter a serial number.
Prompt:	Menu Selection?
Action:	Scan/Enter the CLRATT command
Prompt:	Operation R or L?
Action:	Scan/Enter R to remove attribute data for matching attribute names or L to leave attribute data for matching attribute names.
Prompt:	Attribute?
Action:	Scan/Enter an Attribute Name (must include the group name, if there is one “group_name|attribute_name”), or enter a “group_name*” to include all attribute names for a particular name. The “*” wildcard character can be used to match multiple attribute names.
Prompt:	OK Menu Selection?
Action:	Scan/Enter a next SFDC command.

If incorrect data is entered at any prompt, the data collector displays the following messages:

NOTE: An error message will not be displayed if an attribute name that does not exist is entered. The command will attempt to remove a matching attribute value, but if nothing is matched, then nothing is removed.

 

Error Message:	Invalid Entry
Meaning:	The entered value does not match the required data.

 

Create Batch Serial Number (CR8BSN)

The Create Batch Serial Number command creates a new Batch (module select type 7) serial number for a shop order. Unit serial number association is also preformed. The part number assigned to the batch serial number is the same as the Unit serial number. Unit serial numbers are tracked components to the batch serial number. All unit serial numbers have the same reference designator (UNITSN).

NOTE: The command will be active until the batch serial number has been successfully created and unit serial numbers assigned. Successful batch creation will result in the Menu Selection prompt being displayed.

 

Prompt:	Serial Number?
Action:	Enter the CR8BSN or CR8BSN.algorithm# command. The algorithm # is optional. If not provided, the assumption is that the Batch Serial Number will be created manually. If the algorithm parameter is provided (algorithm # =>20000, type general), the MDS serial number generator will create a serial number based upon the algorithm definition and provide the serial number to the CR8BSN command
Prompt:	Shop Order?
Action:	Enter the Shop Order which contains the unit serial numbers to add to the batch serial number. The shop or is checked to insure it is released and has unit serial numbers available (assigned to the shop order) that can be associated to the batch serial number.
Prompt:	Batch Quantity?
Action:	Enter the number (1-150) how many unit serial numbers the batch serial number will contain. There is a hard limit of 150 units for a maximum batch size. There is also an OPTIONS_MAX_BATCH_QTY line that can be defined by the system administrator to control the maximum batch size, but it cannot exceed 150.
Prompt:	Batch S/N?
Action?	Enter the Batch Serial Number to create. This prompt is only displayed if the CR8BSN command is entered without an algorithm #. The entered serial number is validated against SERIAL INPUT lines in the Setup Data Editor. The command will display Batch S/N if the value is valid.
Prompt:	Auto Comp YES/NO?
Action:	Enter YES to have the command automatically assign unit serial numbers from the Shop Order to the batch serial number. Enter NO to manually add unit serial numbers to the batch serial number.
Prompt:	Unit S/N n/n Unit Serial Number?
Action:	This prompt will only be displayed if NO was entered to the previous prompt. The first line displays the unit serial number in the batch (n/n) and the second value (n/n) is the batch quantity. Enter a Unit Serial Number from the Shop Order to add to the batch. The prompt will repeat, with the (n/n) value updating until the required number of Unit Serial Numbers has been added to the batch.
Prompt:	Menu Selection?
Action:	The batch has been successfully created and the unit serial numbers assigned to the batch. Entering END will pass the batch serial number to the next location defined in the route. Entering RLSE will leave the batch serial number at the current location. All normal SFDC operations can now be performed.

SFDC will prompt for different pieces of information in order to create the batch and assign unit serial numbers to the batch. If incorrect data is entered at any prompt, the data collector displays the following messages:

 

Error Message:	S.O. Not Found
Meaning:	The entered Shop Order is not found, not released, or does not have unit serial numbers available to attach to a batch.
Error Message:	Wrong Quantity
Meaning:	The entered batch quantity exceeds the hard limit or the maximum batch quantity defined by the OPTIONS_MAX_BATCH_QTY line.
Error Message:	ALG NOT DEPLOYED
Meaning:	The algorithm entered is not deployed in production.
Error Message:	Remaining QTY nnn
Meaning:	The entered batch quantity exceeds the number of units available in the Shop Order. The value displayed is the remaining number of units available.
Error Message:	Invalid Batch SN
Meaning:	The entered batch serial number value does not match input masking defined in the Setup Data Editor.
Error Message:	BSN Exist
Meaning:	The entered batch serial number already exists.
Error Message:	Invalid Entry
Meaning:	The entered value does not match the required data.
Error Message:	Invalid Unit SN
Meaning:	The entered unit serial number is not associated to the shop order.

 

End

The End command terminates the current transaction and moves the unit to the next Pass or Fail location.

 

Measure Key (MEASKEY)

The MEASKEY command records a measurement activity, and displays ‘KEY: activity-key’ so that the data in the tester can be tied to a specific activity for the unit. Normally used through AutoSFDC.

 

Merge Batch Serial Number (MERGBSN)

The Merge Batch Serial Number command combines or merges a batch serial number to a parent batch serial number. Unit serial numbers are moved from the merged batch serial number to the parent batch serial number.

NOTE: The merge batch serial number command will only allow batch serial numbers from the same shop order to be merged. The location of the parent batch and the batch to be merged into the parent must be the same. There is no limit on the number of units that can be merged into a parent batch.

 

Prompt:	Serial Number?
Action:	Enter the parent batch serial number.
Prompt:	Menu Selection?
Action:	Enter the MERGBSN command.
Prompt:	Enter Batch S/N?
Action:	Enter the batch serial number to be merged into the parent batch.
Prompt:	+n/n Merged
Action:	This prompt will be displayed after a successful merge. The first n will display how many units were moved from the batch serial number being added to the parent batch. The second n displays the total number of units in the parent batch after the merge.
Prompt:	Menu Selection?
Action:	The merge batch has been successfully performed and the unit serial numbers moved to the parent batch. Entering END will pass the batch serial number to the next location defined in the route. Entering RLSE will leave the batch serial number at the current location. All normal SFDC operations can now be performed.

SFDC will prompt for the required pieces of information in order to merge the specified batch serial number into the parent batch serial number. If incorrect data is entered at any prompt, the data collector displays the following messages:

 

Error Message:	Invalid Entry
Meaning:	The entered value does not match the required data.
Error Message:	Invalid Batch SN
Meaning:	The entered batch serial number was not part of the same shop order or in the wrong location.

 

Move

The Move command moves the scanned unit to a location other than the normal workflow. This subcommand does not appear on the standard SFDC barcode menu because it can cause errors in system functionality. In version SFDC 6.0 and greater, a new OPTIONS line, OPTIONS DISABLE MOVE CMD=YES PASSWORD=xxxxxxxxxxxx, is available to disable the use of MOVE by operators. A configured password will allow for a normal move operation. The options line does not disable any moves performed as the result of a custom command, or by the system, as part of normal operation.

 

PTS Record Defects (PRCDFC)

The PTS Record Defects command records all defects for the scanned unit. The defects are recorded permanently in the unit history. Reference designator and replacement component information are validated in PTS, as part of the defect recording. This prevents a reference designator that does not exist for the part number of the scanned serial number from being entered. If Repaired? = YES, then replacement component validation is also performed in PTS.

NOTE: Defect Codes are maintained using either SFDC Configuration or SPC/SQC. For further information on maintaining defect codes, see the SFDC Configuration Manual.

 

Prompt:	DefCode or Menu?
Action:	Enter a valid defect code or the MENU code. SFDC returns to the Menu Selection prompt on MENU code.
Prompt:	Defect Quantity?
Action:	Enter the total number (1-999) of times this defect appears for this unit. SFDC returns to the Menu Selection prompt on MENU code.
Prompt:	Ref Des or N/A?
Action:	Enter the reference designator (1-20 alphanumeric characters) for the defective component or the N/A code. SFDC skips to the Repaired prompt below on N/A code.
Prompt:	Pin 1?
Action?	Enter the starting pin location (0-4 characters) for the component. Scan ENTER for no entry.
Prompt:	Pin 2?
Action:	Enter the ending pin location (0-4 characters) for the component. Scan ENTER for no entry.
Prompt:	Surface?
Action:	Enter the side (0 or 1 character) for the defective assembly. Scan ENTER for no entry.
Prompt:	Repaired?
Action:	Enter YES, NO, or repair code.
Prompt:	Material Barcode?
Action:	Enter the valid PTS material bar code for the replacement component.
Prompt:	The Part Number? for the entered material bar code is displayed.
Action:	Enter YES, if the part number is correct, or NO if the displayed part number is not correct.
Prompt:	The Manufacturer? for the entered material bar code is displayed.
Action:	Enter YES, if the displayed Manufacturer information is correct, or NO if incorrect.
Prompt:	The Lot Code? for the entered material bar code is displayed.
Action:	Enter YES, if the displayed Lot Code information is correct, or NO if incorrect.
Prompt:	DefCode or Menu?
Action:	Enter a valid defect code or the MENU code. SFDC returns to the Menu Selection prompt on MENU code..

SFDC records the entered information in the unit history then returns to the DefCode or Menu prompt. If a repair was entered, it is recorded to the specified defect.

If incorrect data is entered at any prompt, the data collector displays the following messages:

Error Message:	Invalid Entry
Meaning:	The entered data is invalid. Check character limitations for key-ins.

 

PTS Record Repairs (PRCRPR)

The PTS Record Repairs command lists non-repaired defects for the unit. Reference designator and replacement component information are validated in PTS for the part number of the scanned serial number. If the unit has no non-repaired defects, SFDC returns to the Menu Selection prompt.

NOTE: Repair Codes are maintained using either SFDC Configuration or SPC/SQC. For further information on maintaining defect codes, see the SFDC Configuration Manual.

Prompt:	llllllll ddddd?
Action	Enter YES, NO, NO FAILURE FOUND, an appropriate repair code, or MENU. llllllll is the reference designator of the defectivecomponent. ddddd is the defect description. If MENU is entered, SFDC returns to Menu Selection. If YES is entered, the command verifies that the displayed defect is repaired. The repair is recorded in the unit history. A Repair Code can be entered in the place of YES to detail how the repair was performed. If NO is entered, the command passes over the displayed defect. The defect remains in the defect list. If NO FAILURE FOUND is entered, the command records that the defect could not be verified. The defect is removed from the defect list and the status is recorded in the unit history.
Prompt:	The Material Barcode? prompt is displayed.
Action:	Enter a valid PTS material bar code for the correct replacement component for the reference designator that was recorded as part of the defect logging.
Prompt:	The "Part Number?" of the scanned material bar code is displayed.
Action:	Enter YES, if the part number is correct, or NO if the displayed part number is not correct.
Prompt:	The "Manufacturer?" for the entered material bar code is displayed.
Action:	Enter YES, if the manufacturer information is correct, or NO if incorrect.
Prompt:	The "Lot Code?" for the entered material bar code is displayed.
Action:	Enter YES, if the lot code information is correct, or NO if incorrect.
Prompt:	Menu Selection? will be displayed if there are no other unrepaired defects. Otherwise, the next defect will be displayed.

If incorrect data is entered at any prompt, the data collector displays the following messages:

 

Error Message:	Invalid Entry
Meaning:	The entered data is invalid.

 

Record Defects (RCDFC)

The Record Defects command records all defects for the scanned unit. The defects are recorded permanently in the unit history.

NOTE: Defect Codes are maintained using either SFDC Configuration or SPC/SQC. For further information on maintaining defect codes, see the SFDC Configuration Manual.

 

Prompt:	DefCode or Menu?
Action:	Enter a valid defect code or the MENU code. SFDC returns to the Menu Selection prompt on MENU code.
Prompt:	Defect Quantity?
Action:	Enter the total number (1-999) of times this defect appears for this unit. SFDC returns to the Menu Selection prompt on MENU code.
Prompt:	Ref Des or N/A?
Action:	Enter the reference designator (1-20 alphanumeric characters) for the defective component or the N/A code. SFDC skips to the Repaired prompt below on N/A code.
Prompt:	Pin 1?
Action?	Enter the pin location (0-4 characters) for the component. Scan ENTER for no entry.
Prompt:	Pin 2?
Action:	Enter the pin location (0-4 characters) for the component. Scan ENTER for no entry.
Prompt:	Surface?
Action:	Enter the side (0 or 1 character) for the defective assembly. Scan ENTER for no entry.
Prompt:	Defpart or N/A?
Action:	Enter the part number for the defective component (up to 22 alphanumeric characters) or the N/A code. See next section on Customized Record Defects.
Prompt:	Manufacturer?
Action:	Enter the manufacturer for the defective component (up to 6 alphanumeric characters).
Prompt:	Mfr Lot Code?
Action:	Enter the manufacturer lot code for the defective component (up to 12 alphanumeric characters).
Prompt:	Repaired?
Action:	Enter YES, NO, or repair code.

SFDC records the entered information in the unit history then returns to the DefCode or Menu prompt. If a repair was entered, it is recorded to the specified defect.

If incorrect data is entered at any prompt, the data collector displays the following messages:

 

Error Message:	Invalid Entry
Meaning:	The entered data is invalid. Check character limitations for key-ins.

 

Customized Record Defects

To reduce the scanning sequence of defects, SFDC has customized MENU barcodes. These barcodes skip unused steps in standard Record Defect entry. At the Defcode or Menu prompt, scan a customized barcode. Only the prompts required for the barcode are displayed. No data entry is required for the prompts not displayed. The table below shows how to create a customized process of recording defects.

Character Position Prompt Displayed

• Character 1: R
• Character 2: D DefCode or Menu?
• Character 3: Q/N Defect Quantity?
• Character 4: Q/N RefDes or N/A?
• Character 5: Q/N Pin 1?
• Character 6: Q/N Pin 2?
• Character 7: Q/N Surface?
• Character 8: Q/N DefPart or N/A?
• Character 9: Q/N Manufacturer?
• Character 10: Q/N Mfr Lot Code?
• Character 11: Q/N/Y Repaired?

Characters 1 and 2 are fixed characters and cannot be changed.

Characters 3-11 are defined as follows:

• Q Display the defined prompt to request the information.
• N Do not display the defined prompt.
• Y Do not display the defined prompt as the defect is repaired. Used at character 11 position only.

If N/A or Enter is scanned at the prompts, some of the other prompts may not be necessary and are not displayed automatically.

 

Record Defects Sub-assembly (RCDRSA)

The Record Defects sub-assembly command records a defect and repair against a tracked sub-assembly. It will not record defects against sub components that are non-tracked.

NOTE: This is a “one shot” command meaning that the recording of a defect and repair must all happen all in one command. It is not possible to record a defect against a sub component and not repair it. If the defect is not repaired, the transaction is voided, and the defect is not logged against the sub assembly.

 

Prompt:	Reference designator + component_id?
Action	Enter MENU, YES, NO, NEXT, SUBLVL or Reference designator. YES – A defect is to be logged against the displayed component / subcomponent. The DefCode or Menu? prompt will be displayed. NO / NEXT – A defect is not to be logged against this reference designator and show the next assembly component/unit in the same level. MENU - Ignore this command and go to Menu Selection? prompt. SUBLVL – When the reference designator + component-id of a tracked component that has an attached sublevel component is displayed, scanning the SUBLVL command will drop to the subcomponent level and the first assembly component reference designator + component_id will be displayed. Use YES, NO / NEXT, Reference designator to select the correct subcomponent to log a defect/repair against. Reference Designator - Go to the tracked component / unit for the entered reference designator in the displayed level. RESET - RESET data collector and go to Login in validation
Prompt:	DefCode or Menu?
Action:	Enter defect code, NO or MENU. If NO is entered, SFDC will return to nextReference designator + component_id? If a valid defect code is entered, the Ref Des or N/A? prompt will be displayed.
Prompt:	Ref Des or N/A?
Action:	Enter the reference designator (1-20 alphanumeric characters) for the defective component or N/A.. SFDC skips to the Repaired? prompt below on N/A code.
Prompt:	Repaired?
Action:	Enter YES, NO, or repair code. If YES is entered. The defect code will be recorded in the defect list, and will be marked as repaired. The repair will be recorded in the unit history. A Repair Code can be entered in place of YES to detail how the repair was performed. If NO is entered, the defect code will not be recorded in the defect list.

If MENU is entered, SFDC returns to Menu Selection.

If incorrect data is entered at any prompt, the data collector displays the following messages:

 

Error Message:	Invalid Entry
Meaning:	The entered data is invalid. Check character limitations for key-ins.

 

Record defect to the top level serial number

Options line: This option line is to allow the SFDC admin to have the defect code that is logged against a sub assembly component also logged against the top level serial number.

OPTIONS SUB_RCDDEF RECORD_TOPLEVEL_DEFECT = YES/NO

NOTES:

The same defect code, reference designator information and repair logged against a sub assembly component will be recorded against the top level serial number. For example: If the defect code 0101 was logged against a sub assembly component and the Ref Des location provided was U1 and YES was recorded as the repair, this would also be reflected in the top level serial number unit history.

 

Custom_Defect_Code

Options line: This option line is to allow the SFDC admin to set a certain defect code for the specified workstation in order to avoid recording an incorrect defect code(s) by the production operator.

 

  OPTIONS CUSTOM_DEFECT_CODE CODE = CODE1, [CODE2, [CODE3], xxx] {PRODUCT = pbm} {LOC = [LOC1, [LOC2], LOCx]}

 

Format:

 

CODE=CODE1, CODE2, …CODEx	Where CODE is the defect or repair code(s) that will be limited for use.
PRODUCT=pbm	Optional. Where pbm is the product MASK defining the product number which be limited. No PRODUCT means all products number will be limited. A product number who has special characters same as MASK DEFINING can be used with “” (quotations) masks placed.
LOC=LOC1,LOC2, …, LOCx	Optional. Where Loc is the location where the operation will be limited to. No LOC means all location can be used.

NOTES:

Multiple OPTIONS lines can be used in setup editor and the first pbm match will be used for a product number

A product number which has special characters that might be mistaken for MASK DEFINING characters, can be used with “” (quotations) masks placed around the mask. For example: SFDC. 100. The . (dot) is a special character reserved for MASK DEFINING. “” (quotations) placed around the mask means product number SFDC.001 will be limited for CUSTOM_DEFECT_CODE.

Scanning a CUSOM_DEFECT_CODE defined for a unit, will record the defect code into the local database and MDS will return to MENU SELECTION. If PRODUCT and LOC have been matched but defect code could not match, SFDC will prompt ‘Invalid Entry’ and ignore the defect code, then return to the MENU SELECTION prompt.

Example

 

Example 1	OPTIONS CUSTOM_DEFECT_CODE CODE=0101, 0102 PRODUCT=SFDC 001 LOC=SMTO
Meaning	At the SMTO workstation a product number SFDC 001 will only use 0101 or 0102 defect codes.
Example 2	OPTIONS CUSTOM_DEFECT_CODE CODE=0101, 0102 LOC=SMTO
Meaning	At the SMTO workstation only 0101 and 0102 defect codes can be used.

 

Record Repairs (RCRPR)

The Record Repairs command lists non-repaired defects for the unit. If the unit has no non-repaired defects, SFDC returns to the Menu Selection prompt.

NOTE: Repair Codes are maintained using either SFDC Configuration or SPC/SQC. For further information on maintaining defect codes, see the SFDC Configuration Manual.

Prompt:

llllllll ddddd?

Action

Enter YES, NO, NFF, an appropriate repair code, or MENU. llllllll is the reference designator of the defective component. ddddd is the defect description. If MENU is entered, SFDC returns to Menu Selection. If YES is entered, the command verifies that the displayed defect is repaired. The repair is recorded in the unit history. A Repair Code can be entered in the place of YES to detail how the repair was performed. If NO is entered, the command passes over the displayed defect. The defect remains in the defect list. If NFF ("No Fault Found" or "No Failure Found") is entered, the command records that the defect could not be verified. The defect is removed from the defect list and the status is recorded in the unit history.

If incorrect data is entered at any prompt, the data collector displays the following messages:

 

Error Message:	Invalid Entry
Meaning:	The entered data is invalid.

Release (RLSE)

The Release command releases a scanned unit at its station. The unit remains at this station until it is passed, failed, or moved.

 

Prompt:	Variable
Action:	No action required.

SFDC returns to the Serial Number prompt.

 

Remove Component (RMCMP)

The Remove Component command removes a component from a unit. Prompts display for each component. If the unit has no components, SFDC returns to Menu Selection.

 

Prompt:	Variable
Action:	Enter YES, NO, NEXT, or MENU. If YES is entered, SFDC removes the displayed component and returns to Menu Selection. If NO or NEXT is entered, SFDC prompts for the next component or returns to Menu Selection. If MENU is entered, SFDC returns to Menu Selection.

If incorrect data is entered at any prompt, the data collector displays the following messages:

 

Error Message:	Invalid Entry
Meaning:	The entered data is invalid.

 

Remove Component 2 (RMCMP2)

The Remove Component (RMCMP2) command removes a component id for a serial number. The command is entered at the Menu Selection prompt.

 

Prompt:	Remove comp_id?
Action:	Enter component id or MENU.

If a valid component id is entered, SFDC removes it from the displayed component and returns to Menu Selection.

If MENU is entered, SFDC returns to Menu Selection.

If incorrect data is entered at any prompt, the data collector displays the following messages:

 

Error Message:	Invalid Entry
Meaning:	The entered data is invalid.

 

Remove All Components (RMCMPALL)

The Remove All Components command removes all components associated with the unit.

 

Prompt:	No prompt.
Action:	No action required.

SFDC removes all components and returns to Menu Selection.

 

Remove All Units from Batch (RMVALLUNIT)

The Remove All Units from Batch command allows for all unit serial numbers to be removed from the batch serial number.

NOTE: Empty batch serial numbers are not left as WIP in SFDC. Batch serial numbers also cannot be “reused”. Whenever a batch is emptied, the batch serial number will have the status changed to 63 and will reflect “Batch_OldID”.

 

Prompt:	Serial Number?
Action:	Enter the batch serial number.
Prompt:	Menu Selection?
Action:	Enter the RMVALLUNIT command.
Prompt:	Location?
Action:	Enter the location to put the removed unit serial number.
Prompt:	Serial Number?
Action:	All unit serial numbers have been removed from the batch serial number. As the batch is now empty, the batch serial number will have the status changed to 63 and will reflect “Batch_OldID”.

SFDC will prompt for the required pieces of information in order to remove all the unit serial numbers from the batch serial number. If incorrect data is entered at any prompt, the data collector displays the following messages:

 

Error Message:	Invalid Entry
Meaning:	The entered value does not match the required data.
Error Message:	Invalid Location
Meaning:	The entered location is not valid.

 

Remove Unit from Batch (RMVUNIT)

The Remove Unit from Batch command allows for an individual unit to be removed from the batch serial number.

NOTE: Empty batch serial numbers are not left as WIP in SFDC. Batch serial numbers also cannot be “reused”. Whenever a batch is emptied, the batch serial number will have the status changed to 63 and will reflect “Batch_OldID”.

 

Prompt:	Serial Number?
Action:	Enter the batch serial number.
Prompt:	Menu Selection?
Action:	Enter the RMVUNIT command.
Prompt:	Location?
Action:	Enter the location to put the removed unit serial number.
Prompt:	Unit Serial Number?
Action:	Enter a Unit Serial Number to be removed from the batch serial number.
Prompt:	DefCode or Menu?
Action:	Enter a valid defect code or MENU. The defect code is optional and is to allow for a reason for removing the unit from the batch to be recorded. If a defect code is logged, the unit history will reflect a “Fail to xxxx” operation.
Prompt:	Comment Text?
Action:	Enter a comment to note why the unit is being removed from the batch serial number or MENU.
Prompt:	Menu Selection?
Action:	The unit serial number is removed from the batch serial number. Entering END will pass the batch serial number to the next location defined in the route. Entering RLSE will leave the batch serial number at the current location. All normal SFDC operations can now be performed.
Prompt:	Serial Number?
Action:	If the Serial Number? prompt is displayed instead of the Menu Selection? prompt, this means that the last unit has been removed from the batch serial number and the batch is now empty. The batch serial number will have the status changed to 63 and will reflect “Batch_OldID”.

SFDC will prompt for the required pieces of information in order to remove the unit from the batch serial number. If incorrect data is entered at any prompt, the data collector displays the following messages:

 

Error Message:	Invalid Entry
Meaning:	The entered value does not match the required data.
Error Message:	Invalid Location
Meaning:	The entered location is not valid.
Error Message:	Invalid Unit SN
Meaning:	The entered unit serial number is not attached to the batch serial number.

 

Replace Component (RPCMP)

The Replace Component command replaces a removed component.

 

Prompt:	Variable.
Action:	Enter YES, NO, NEXT, or MENU. If NO or NEXT is entered, SFDC prompts for the next removed component or returns to Menu Selection. If MENU is entered, SFDC returns to Menu Selection.
Prompt:	—Prompt defined in Assembly record“
Action:	Enter the id number of the new component or MENU.

If a valid component id number is entered, SFDC makes the replaces the component in the unit and returns to Menu Selection.

If incorrect data is entered at any prompt, the data collector displays the following messages:

 

Error Message:	Invalid Entry
Meaning:	The entered data is invalid.
Error Message:	Unit Not Valid
Meaning:	The component entered is tracked. It is in the wrong location.

 

Replace Component 2 (RPCMP2)

The Remove Component command replaces a component id for a serial number.

 

Prompt:	Replace comp_id?
Action:	Enter component id or MENU. If MENU is entered, SFDC returns to Menu Selection.
Prompt:	“Prompt defined in Assembly record”
Action:	Enter the id number of the new component or MENU. If a valid component id is entered, SFDC replaces it and returns to Menu Selection. If MENU is entered, SFDC returns to Menu Selection.

If incorrect data is entered at any prompt, the data collector displays the following messages:

 

Error Message:	Invalid Entry
Meaning:	The entered data is invalid.
Error Message:	Unit Not Valid
Meaning:	The component entered is tracked. It is in the wrong location.

 

Remove/Replace Sub Component (RPSCMP)

The Remove/Replace Subcomponent command removes and replaces a sub-assembly component from the Top Level serial number. The command initially will display the first level of components attached to the Top Level serial number.

NOTE: This is a “one shot” command meaning that the removal and replacement of a subcomponent happens all in one command. It is not possible to remove a subcomponent, replacing the subcomponent at a later time.

 

Prompt:	Reference designator + component_id?
Action:	Enter MENU, YES, NO, NEXT, SUBLVL or Reference designator. YES - The displayed component / subcomponent will be replaced. NO / NEXT - Don’t replace this reference designator and show next assembly component/unit in the same level. MENU - Ignore this command and go to Menu Selection? prompt. SUBLVL – When the reference designator + component-id of a tracked component that has an attached sublevel component is displayed, scanning the SUBLVL command will drop to the subcomponent level and the first assembly component reference designator + component_id will be displayed. Use YES, NO / NEXT, Reference designator to select the correct subcomponent. Reference Designator - Go to the tracked component / unit for the entered reference designator in the displayed level. RESET - RESET data collector and go to Login in validation
Prompt:	Reference designator of assembly table in sub unit? (This message will show scan YES)
Action:	Scan target replaced component / unit
Prompt:	Menu Selection?
Action:	Scan SFDC command
Action:	Scan valid reference designator

If incorrect data is entered at any prompt, the data collector displays the following messages:

 

Error Message:	Invalid Entry (This message maybe show after scan reference designator)
Meaning:	The entered data is invalid. Check character limitations for key-ins.
Error Message	Replaced Not Allowed
Meaning	Target replacement component is not matched with removed component. Check the assembly table, tracked unit, S/N format of target component

Options line: This option line allows the SFDC admin to place the removed subcomponent to certain location.

OPTIONS SUB_REMV {PRODUCT=pbm} LOC=LOC1

Format:

 

PRODUCT=pbm	Optional. Where pbm is the product MASK defining the product number which be limited. No PRODUCT means all products number will be limited. A product number who has special characters same as MASK DEFINING can be used with “” (quotations) masks placed.
LOC=LOC1	Where Loc is the location where the removed component is to be placed.

NOTES:

Multiple OPTIONS lines can be used in the setup editor and the first pbm match will be used for a product number.

A product number which has special characters that might be mistaken for MASK DEFINING characters, can be used with “” (quotations) masks placed around the mask. For example: SFDC. 100. The . (dot) is a special character reserved for MASK DEFINING. “” (quotations) placed around the mask means product number SFDC.001 will be limited for SUB_REMV.

Example:

 

Example 1	OPTIONS SUB_REMV PRODUCT=ASSEMBLYPN(3)n LOC=COMP
Meaning	When product format is ASSEMBLYPN (3) n that sub removed/replaced unit will move to COMP location.
Example 2	OPTIONS SUB_REMV LOC=COMP
Meaning	sub removed/replaced unit will move to COMP location

 

Reset (RESET)

The RESET command exits the current transaction and returns back to Employee prompt without passing the unit to the next station. Will not back out any transactions already processed, such as components added or defects recorded.

 

Reset Error (RESETERROR)

The Reset Error command clears an error from a data collector if the STOP_ON_ERROR option is being used in Setup Data Editor. If anything else is scanned, the data collector beeps ten times and redisplays the same error message.

NOTE: For more information, see the STOP_ON_ERROR discussion in the SFDC Setup Editor Quick Reference.

 

Sample command (SAMPLE.sample_plan)

The SAMPLE command replaces the !!1sample command that is run on the MDS server. The command is now called locally on the SFDC PC, allowing sampling to be run even when the connection to the MDS database is down.

The sampdown.sh SFDC administration command is issued on the SFDC PC, in order to download the sample_master and sample_plan tables to the SFDC PC. New sample master plans, individual sample plans, modifications to existing sample plans are all performed in MDS. In order for the updates to take effect, they must be downloaded to the SFDC PC through the sampdown.sh command.

NOTES:

The sampdown.sh download runs through a proxy, therefore stopping the SFDC service is not required (same as sfdc dnld) and does not require that the SFDC service be restarted in order for changes to take effect. The next time the SAMPLE command is called (executed), all changes / additions will be available.

The SAMPLE command cannot be called alone. The command must include 1 or more sample plans names.

Example:

At the MENU SELECTION prompt, SAMPLE.PLAN1 or SAMPLE.PLAN1.PLAN2 can be entered. SAMPLE does not work like the MOVE command, where it can be entered separately, followed by a location name. MACROS or AUTOCMD lines can be created in the setup editor to call individual or multiple sample plans, in the same fashion as the !!1sample command.

 

Split Batch Serial Number (SPLTBSN)

The Split Batch Serial Number command splits a parent batch serial number into smaller batches by creating a new Batch serial number and moving unit serial numbers from the parent batch to the new batch serial number. There command has a mandatory parameter used to define how unit serial numbers are removed from the parent batch serial number and added to the new batch. The parameter can be one of the following characters (A/D/R/E/M). The definition of the parameter characters are as follows: A – Ascending, D – Descending, R – Recent (most recent activity), E – Earliest (oldest activity), M – Manual. The parameter is used to define how to remove unit serial numbers from the parent batch and associate to the new split batch serial number. The split batch command supports manual serial number entry and automatic serial number creation using an algorithm. See the NOTE below regarding using an algorithm.

NOTE: If using an algorithm to create the split batch serial number(s), the algorithm format must be xxxxxx-nnn, where xxxxxx matches the parent serial number length, followed by a constant “-“ and then a number sequence. The split batch serial number command will send the parent batch serial number to the serial number generator to use in the algorithm. The format will be the parent batch serial number followed by a “-“ and nnn. The algorithm # =>20000, and of type general.

NOTE: When using the M – Manual parameter, only a single split batch can be performed.

 

Prompt:	Serial Number?
Action:	Enter the parent batch serial number.
Prompt:	Menu Selection?
Action:	Enter the SPLTBSN.A/D/R/E/M or SPLTBSN. A/D/R/E/M.algorithm# command. The x parameter is mandatory. The algorithm # is optional. If not provided, the assumption is that the Split Batch Serial Number will be created manually. If the algorithm parameter is provided, the MDS serial number generator will create a serial number based upon the algorithm definition and provide the serial number to the SPLTBSN command Refer to the above NOTE in regards to the algorithm format required.
Prompt:	Split Qty MAX=n?
Action:	The n value is the parent batch quantity. Enter the number (quantity) of unit serial numbers that the split batch serial number will contain. NOTE: The split batch quantity must be less than the parent batch quantity.
Prompt:	Single Split?
Action:	Enter YES or NO. YES indicates that only a single split batch serial number will be created. NO indicates to perform multiple splits, based upon the split quantity entered, until the parent batch serial number contains less than or equal to the split batch quantity. This prompt is not displayed if the M – Manual parameter was entered.
Prompt:	Batch S/N?
Action?	Enter the Batch Serial Number to create. This prompt is only displayed if the CR8BSN command is entered without an algorithm #. The entered serial number is validated against SERIAL INPUT lines in the Setup Data Editor. If the response to the Single Split? prompt was NO, the Batch S/N? prompt will repeat until the required number of split batch serial numbers has been entered (Splitting a batch of 10 into batches of 2 will require 4 split batch serial numbers, leaving 2 units in the parent batch).
Prompt:	n Units Remaining
Action:	The n value is the number of units remaining in the parent batch serial number. This message is displayed after performing the split(s).
Prompt:	Unit Serial Number?
Action:	This prompt is only displayed when the M – Manual parameter is used. Enter a Unit Serial Number from the parent batch serial number to add to the batch. This prompt will repeat until the required number of Unit Serial Numbers has been added to the batch.
Prompt:	Menu Selection?
Action:	The split batch has been successfully created and the unit serial numbers assigned to the batch. Entering END will pass the batch serial number to the next location defined in the route. Entering RLSE will leave the batch serial number at the current location. All normal SFDC operations can now be performed.

SFDC will prompt for the required pieces of information in order to create the split batch and assign unit serial numbers based upon the specified parameter. If incorrect data is entered at any prompt, the data collector displays the following messages:

 

Error Message:	Invalid Entry
Meaning:	The entered value does not match the required data.
Error Message:	Invalid Unit SN
Meaning:	The entered unit serial number is not associated to the shop order.
Error Message:	ALG NOT DEPLOYED
Meaning:	The algorithm entered is not deployed in production.
Error Message:	NO DASH IN ALG
Meaning:	The algorithm does not contain a “-“ in the format. Refer to the NOTE: above detailing the algorithm format required for use by the split batch command.

 

Split Normal (SPLTN)

The Split Normal command is used only in locations where normal operation is to split multi-board panels.

If the unit cannot be split, SFDC displays the Cannot Split message and returns to Menu Selection.

If the unit is already completely split, SFDC displays the No Splits Left message and returns to Menu Selection.

If the unit has outstanding defects, SFDC displays the Defects Exist message and returns to Menu Selection.

If the unit can be split, the following prompts display:

 

Prompt:	Split ID nnn?
Action:	Enter the new serial number for the board being split from the panel. Enter MENU to return to Menu Selection. nnn is an incremental number reflecting the number of splits performed on this board.

If a valid serial number is entered and no errors display, SFDC creates a record for the new board serial number and lowers the quantity for the panel serial number. If more splits are needed for this panel (quantity is not zero), SFDC prompts for Split ID nnn.

If the panel is completely split, SFDC displays PASS bds to xxxx, where xxxx is where the boards were moved. SFDC then returns to the Serial Number prompt.

 

Error Message:	Invalid Entry
Meaning:	The entered data is invalid.
Error Message:	Duplicate Serial
Meaning:	The serial number entered has already been used.
Error Message:	Network Is Down
Meaning:	SFDC cannot communicate with the network database plant server and cannot perform the split.

 

Split Non-Serialized Batch Number (SPLTNBSN)

In SFDC 6.0, the ability to batch and process Non-Serialized Units has been developed. All Non-Serialized Batch processing is handled by Shop Orders. A Shop Order is released for a Non-Serialized Batch. MDS creates a Batch Serial Number using the Shop Order number. By default, the batch size is equal to the Shop Order quantity. All SFDC scanning is performed by scanning the Shop Order number.

The Split Non-serialized Batch command splits a Batch Serial Number into smaller batches by creating a new Batch Number with a consecutive counter, ex. Batch-001.
If a single batch is at a scanning location, and only a portion of the batch is to be passed forward, a “manual” split must be performed. This is accomplished using the SPLTNBSN command.

 

Prompt	Serial Number
Action	Enter the Non-Serialized Batch Number
Prompt	Menu Selection?
Action:	SPLTNBSN
Prompt:	Split Qty? (MAX=n)
Action:	The n value is the parent batch quantity. Enter the number (quantity) of Units that the new Split Batch (Batch-00x) will contain. NOTE: The split batch quantity must be less than the parent batch quantity.
Prompt	Menu Selection?
Action	The Split Batch has been successfully created. Entering END will pass the Batch Serial Number to the next location defined in the route. Entering RLSE will leave the Batch Serial Number at the current location. All normal SFDC operations can now be performed.

Split Partial (SPLTP)

The Split Partial command is used only in locations where normal operation is to split multi-board panels.

If the unit cannot be split, SFDC displays the Cannot Split message and returns to Menu Selection.

If the unit is already completely split, SFDC displays the No Splits Left message and returns to Menu Selection.

If the unit can be split, the following prompts display:

 

Prompt:	Split ID nnn?
Action:	Enter the new serial number for the board being split from the panel. Enter MENU to return to Menu Selection. nnn is an incremental number reflecting the number of splits performed on this board.
Prompt:	Bds/Panel = 1
Action:	Enter YES to accept the default value or enter the correct number of boards removed from the panel.

SFDC creates a new serial number record for the new board(s) (or subpanel) and lowers the quantity for the panel serial number. If a bds/panel number greater than one is entered, the new serial number is assumed to be a panel to be further split.

If the panel is completely split, SFDC returns to the Serial Number prompt. Otherwise, SFDC returns to Menu Selection.

If the panel is not completely split and it is necessary to keep it in its current location, scan RLSE to release the unit. The panel remains at its current location, and the boards pass to the next location defined in the SFDC Configuration Route table. See Product Routing Manager in the SFDC Configuration Manual for more information.

If incorrect data is entered at any prompt, the data collector displays the following messages:

 

Error Message:	Invalid Entry
Meaning:	The entered data is invalid.
Error Message:	Duplicate Serial
Meaning:	The serial number entered has already been used.
Error Message:	Network Is Down
Meaning:	SFDC cannot communicate with the network database plant server and cannot perform the split.

 

MDS, Part Maintenance

In MDS, in Part Maintenance, ensure that the Non-Serialized Part Number exists. No Serial Number algorithm should be assigned to the part. Ensure that the “create skeletons” check box is not checked. The quantity field is 1 (one) by default. If the dpart.qty field = 1, then MDS will use the Shop Order release quantity as the batch quantity. If the dpart.qty field > 1 then this is used to defined the batch quantity. For example, if dpart.qty=100, then batches will be created in quantities of 100. When releasing the Shop Order in MDS, there is a check box for a Non-Serialized Batch. This check box should be checked. This tells MDS to create the Batch Serial Numbers based upon the Shop Order. Either a full or partial release can be performed. Per the dpart.qty rules defined above, if dpart.qty = 1 then the batch quantity will be the release quantity. This is true also if a partial release is performed and the quantity release is less than a defined batch quantity. The Serial Number generated will be the Shop Order number. Subsequent Batch Serial Numbers are in the following format: shop_order_number-nnn.

SFDC Scanning

All SFDC scanning is done by scanning the Shop Order Number, regardless of the number of Batch Serial Numbers created or that exist. Scanning individual Batch Serial Numbers is not required. If there is only a single Batch Serial Number at any location, SFDC scanning works just like any individual unit scanning. If there are multiple Batch Serial Numbers at a scanning location, or released and ready to be started, SFDC will display the Batch QTY? prompt. Depending upon the quantity entered, SFDC will split a batch, if the entered quantity is less than a batch quantity. If the quantity is some multiple of batch quantities, then the batches will be merged together. Scanning END passes the entered quantity forward to the next location. If a single batch is at a scanning location, and only a portion of the batch is to be passed forward, a “manual” split must be performed. This is accomplished using the SPLTNBSN command. Refer to the command specifics in this document for more information.

Recording Defects

Recording defects works in a similar fashion. At the Menu Selection? prompt, scanning the record defect command (RCDFC) will prompt for Defect Code, then Defect Quantity. Defect Quantity in Non-Serialized Batch is the number of units that fails for the entered Defect Code, not the number of defects on a particular unit. For example, if the Batch Serial Number contains 10 (ten) units, and the Defect Quantity is entered as 2 (two), then 2 units will be split off into a separate batch and failed. The user has the ability to repair the units at the time the defect is logged, preventing the defect units from being split off into a separate batch, and failing to the “fail to location” defined in the route.

Repairs

Repairs work the same way. When repairing a defect against a Batch Serial Number, the user will be prompted for quantity. If the entered value is less than the batch quantity, another split will occur, leaving the remaining quantity at the fail location. With Oracle-interfaced orders, WIP moves and completions are reported on the quantity in the batch when it passes through a mapped location or to finished status.

Configuration Rules

With Non-Serialized Batch processing comes some configuration rules that must be followed. Because all scanning is done using just the Shop Order Number, these rules are required in order for SFDC to work correctly.

• Only a single source location can be used in a route step. Accepting from more than one source location is not allowed because SFDC cannot determine which batch to use, assuming there are batches in each source location.
• Multi-pass device numbers are not allowed for route locations used in Non-Serialized Batch routes. SFDC cannot determine which location to perform the scan operation if there are Batch Serial Numbers at multiple locations and those locations are assigned to a single device number.
• Starting multiple Batch Serial Numbers (status 15) requires that only valid batch quantities are entered to the Batch Qty? prompt. The “Invalid Entry” message will be displayed if the entered quantity does not match a batch or combination of Batch Serial Number quantities. This only applies to status 15 Batch Serial Numbers.
• All scanning should be done using just the Shop Order Number. No scanning of the individual Batch Serial Numbers (shop_order_number-nnn) should occur.
• The OPTIONS SHOW_SDE_LOC ENABLE=YES option line should be enabled and downloaded to the SFDC PC.

Add Sub Attribute (SUBATT)

The Add sub attribute command is used to add attributes to a unit serial number while it is attached to a batch serial number.

NOTE: An attribute table must exist for the part number (of the unit serial number) at a location. The location does not have to be used in a route.

Calling the SUBATT command can be performed in 4 different ways. Here is the methods and requirements:

• SUBATT – SFDC will prompt for all attribute names at the current location, if an attribute definition exists for the current part number.
• SUBATT.LOC – SFDC will prompt for the location of the attribute definition. All attribute names found in an attribute definition for the current part number, at the specified location, will be prompted for.

• SUBATT.GROUP – SFDC will prompt for Group Name. Matching attribute names found in an attribute definition for the current part number, at the current location, will be prompted for.
• SUBATT.LOC.GROUP – SFDC will prompt for the location of the attribute definition and Group Name. Matching attribute names found in an attribute definition for the current part number, at the specified location, will be prompted for.

 

Prompt:	Serial Number?
Action:	Enter the batch serial number.
Prompt:	Menu Selection?
Action:	Enter the SUBATT.param command.
Prompt:	Location or Group Name?
Action:	Enter a valid location for where there is an attribute definition, or enter a valid Group Name for a set of attribute names.
Prompt:	Unit Serial Number?
Action:	Enter a unit serial number that is attached to the scanned batch serial number.
Prompt:	Attribute_prompt?
Action:	Enter an attribute data value. The value must match the defined mask. If there are multiple attribute names, SFDC will prompt for each attribute name, until all attributes have been supplied. Once all attributes have been added, the “No Attribute Needed” message is displayed.
Prompt:	Next Unit SN?
Action:	Enter another unit serial number to add attributes to, or the MENU command to exit the SUBATT command.
Prompt:	Menu Selection?
Action:	Entering END will pass the active batch serial number to the next location defined in the route. Entering RLSE will leave the active batch serial number at the current location.

NOTE: If an attribute definition is not found at the current or specified location, or a matching group name is not found, the “No Attribute Needed” message will be displayed.

SFDC will prompt for the required pieces of information in order to add the attribute data to the unit serial numbers based upon the specified parameter. If incorrect data is entered at any prompt, the data collector displays the following messages:

 

Error Message:	Invalid Entry
Meaning:	The entered value does not match the required data.
Error Message:	Invalid Location
Meaning:	The entered location is not a valid location.
Error Message:	Invalid Attribute Value
Meaning:	The entered value does not match the attribute value mask.

 

Verify Attribute (VERATT)

The Verify Attribute command is used to check for the existence of attribute data. The command has a number of parameters listed below.

• Fail to Location: This parameter is used to specify a location to move the serial number to, if the verification fails. N/A can be entered to use the default fail to location defined in the SFDC route. Using N/A will result in a FAIL activity recorded against the serial number.
• Defect Code: Valid defect code to log against the serial number if verification fails.
• Type: Verification type

ALL (or no vertype param) - validate that the unit has all attributes that are setup for the top level part number.

PROC - validate that the unit has all attributes that are setup for the top level part number and assigned the process name 'DATA LOAD'; only one process can be checked.

LIST - validate that the unit has each of the attribute names that you pass in the parameter list.

NOTE: This command is only available in SFDC version 5.22 or greater.

NOTE: To automate the verify attribute command, use the “$” command as a separator (VERATT$fail2loc$defcode$type$).

 

Prompt:	Serial Number?
Action:	Scan/Enter a serial number.
Prompt:	Menu Selection?
Action:	Scan/Enter the VERATT command
Prompt:	Fail to Location?
Action:	Scan/Enter a valid location name, or enter N/A to use the default fail to location defined in the SFDC route.
Prompt:	Defect Code?
Action:	Scan/Enter a valid defect code.
Prompt:	Select Option?
Action:	Scan/Enter a verification type - ALL, PROC, or LIST.
Prompt:	ALL = Serial Number? PROC = Process Name? LIST = Qty for Listing?
Action:	If ALL was entered, verification was run and the serial number either passed or failed. For PROC, enter a Process Name where an attribute definition exists to check, or for LIST, enter a quantity of attribute names to specify (1, 2, 3, …)
Prompt:	Attribute? (The Attribute? prompt is displayed for each attribute name, as specified by the QTY for Listing number. For example if 3 were entered as the quantity, the command will prompt for 3 attribute names.)
Action:	Scan/Enter attribute names for each Attribute? prompt.

If incorrect data is entered at any prompt, the data collector displays the following messages:

NOTE: An error message will not be displayed if an attribute name that does not exist is entered. The command will attempt to remove a matching attribute value, but if nothing is matched, then nothing is removed.

 

Error Message:	Invalid Entry
Meaning:	The entered value does not match the required data.
Error Message:	Invalid Loc= xxxx
Meaning:	The entered location (xxxx) does not match a location value in the database.
Error Message:	Invalid Defcode= xxxx
Meaning:	The entered defect code (xxxx) does not match any defect code in the database.
Error Message:	Invalid Type= xxxx
Meaning:	The entered type (xxxx) does not match the valid types (ALL, PROC, LIST).

 

Verify Component (VERCMP)

The Verify Component command verifies that all components have been added. It compares the reference designator and component part number fields of a component record with the same fields in an assembly record to determine if all components are entered.

If any components are missing, the command displays a Missing Components message and optionally records a defect in order to fail the unit. Also the command lists the reference designators of missing component on a terminal or printer attached to the data collector. For more information, see the MISSING_COMP_DEFCODE discussion in the SFDC Configuration Manual.

 

View Components (VWCMP)

The View Components command displays components in the unit history.

 

Prompt:	Variable
Action:	Enter NEXT or MENU. If NEXT is entered, SFDC displays the next component for the unit. If MENU is entered, SFDC returns to Menu Selection.

If incorrect data is entered at any prompt, the data collector displays the following messages:

 

Error Message:	Invalid Entry
Meaning:	The entered data is invalid.

 

View Defects (VWDFC)

The View Defects command displays defects in the unit history.

 

Prompt:	llllllll ddddd?
Action:	Enter NEXT or MENU. llllllll is the reference designator of the defective component. ddddd is the defect description. If NEXT is entered, SFDC displays the next non-repaired defect for the unit. If MENU is entered, SFDC returns to Menu Selection.

If incorrect data is entered at any prompt, the data collector displays the following messages:

 

Error Message:	Invalid Entry
Meaning:	The entered data is invalid.

 

View History (VWHST)

The View History command displays the unit history.

NOTE: This command requires a CRT (ASCII Terminal) or serial printer connection to the data collector. All records will be displayed or printed, depending on the connection.

 

Macro Barcodes

SFDC optimizes barcode scanning with Macro Barcodes. These specialized barcodes minimize scanning by incorporating multiple Menu Selection scans into one barcode. This capability decreases scanning time on the production line. A Macro Barcode is created by imbedding a dollar sign ($) between normal Menu Selection commands.

Macro Barcode Examples

Example 1

The standard process to end a Record Defect command is to scan MENU followed by END. A customized barcode can incorporate both commands into one barcode. The Macro Barcode would be MENU$END.

Example 2

Create a Macro Barcode that records a standard defect with no reference designator required. By including the customized Record Defect process, initial test failures could be entered with one scan only. The Macro Barcode would look as follows:

RDNNNNNNNNN$xxxx$MENU$END

Where xxxx is a valid defect code.

The barcode in example 2 automatically records the imbedded defect, ends the process, and fails the unit to the designated location. See Customized Record Defects for more information.

Example 3

This example uses two Macro Barcodes.To record a defect, enter the defect code, determine if the unit is repaired, and end the process, the following barcodes can be used:

Barcode 1:

RDNQNNNNNNQ

This barcode allows the operator to enter the appropriate defect code, enter the reference designator, and enter yes, no, or a valid repair code for the repaired status.

Barcode 2:

MENU$END

This barcode automatically ends the process and either passes or fails the unit based on the unit status.

Example 4

Create a Macro Barcode that moves products to an alternate location at the end of a defect code process. The barcode would look as follows:

MENU$MOVE$zzzz

Where zzzz is a location defined in SFDC Configuration.

This barcode automatically ends the Record Defect process and moves the unit to the designated location with an In Repair status.

Example 5

SFDC has the ability to pause during the processing of a Macro Barcode command that waits for data collector input. The pause is generated by using a double-dollar sign ($$) within the Macro Barcode.

RDNNNNNNNNN$$MENU$END

This Macro Barcode executes the Record Defect command then waits for the defect code to be scanned or entered from the data collector before executing the MENU and END commands.

 

Macro Barcode Error Messages

Error messages generally associated with commands imbedded within a Macro Barcode will display normally. However, the following error message is particular to Macro Barcodes:

 

Error Message:	Prog Not Found
Meaning:	SFDC cannot identify the barcode. This is generally a scanning misread.

 

Error and Prompt Messages

Default prompt, error, and informational messages are displayed by SFDC. The lists below show the default messages.

Customized prompt and error messages can be configured in SFDC Configuration within MDS. For more information on creating custom prompts and error messages, see Configuring Error and Prompt Messages in the SFDC Configuration Manual.

 

Default Prompts

Maximum size is 16 characters, including extra provided in a message, such as the first 4 characters of a location name:

 

Number	Prompt Text
1	Product Number?
2	Serial Number?
3	DefCode or Menu?
4	RefDes or N/A?
5	DefPart or N/A?
6	Manufacturer?
7	Mfr Lot Code?
8	Split ID?
9	HOLD or NOHOLD?
10	Hold Station ID?
11	Menu Selection?
12	Sub Serial?
13	Workstation ID?
14	Lot Quantity?
15	New Comp ID?
16	MEO Number?
17	New Serial No.?
18	Bds/Panel=
19	Unused
20	Unused
21	Unused
22	Unused
23	Employee No.?
24	Repaired?
25	New Status?
26	Password?
27	New Product #?
28	Defect Quantity?
29	Pin 1?
30	Pin 2?
31	Surface?
32	Container Type?
33	Lot Number?
34	Container Num?
35	S/N to Remove?
36	Remove comp_id?
37	Replace comp_id?
38	Revision?
39	New Revision?
40	Comment Text?
41	Ref Designator?
42	Component Part#?
43	Component ID?
44	Variable.
45	?Prompt Defined In Assembly Record?
46
47
48
49
50	Next Serial?
51	Cmd End
52	Added
53	Removed
54	Replaced
55	Sample Name?
56	S/N to Sample?
57	Shop Order #?
58	Batch S/N Qty=
59	BSN:
60	Unit S/N
61	Location ?
62	Add Or Replace Comp?
63	Enter Batch SN?
64	Units Merged
65	Split Qty MAX=
66	Split Model A/D/R/E/M?
67	Units Remaining
68	Print Label/Menu?
69	Unit Serial Number?
70	Auto Comp YES/NO?
71	Batch Qty?
72	Merged
73	Single Split?
74	Replace Attribute?
75	Group Name?
76	Next Unit SN?
77	URL Name?
78	PTS Function?
79	Get S/N?
80	Attribute?
81	Operation
82	Qty For Listing?
83	Process Name?
84	Select Option?

 

Default Error Messages

Maximum size is 16 characters, including extra provided in a message, such as the first 4 characters of a location name:

 

Number	Prompt Text
1	Duplicate Serial
2	Serial Not Found
3	Invalid Entry
4	Flow Error
5	Unit is on HOLD
6	Unit Not Valid
7	Network Is Down
8	Cannot Split
9	No Splits Left
10	Defects Exist
11	Network Problem
12	System Error
13	Move Not Allowed
14	Login Failed
15	Login Timeout
16	Invalid Serial #
17	Can‘t Perform Op
18	Invalid Prod No.
19	No Route Assigned
20	Status Error
21	Prog Not Found
22	In UseAt ….
23	Lot Open
24	Container Open
25	No Lot Config
26	No Container Cfg
27	Duplicate Lot
28	Duplicate Cntnr
29	Lot Not Found
30	Cntnr Not Found
31	No Lot Open
32	No Cntnr Open
33	Has Lot Number
34	Has Cntnr Number
35	Wrong Product
36	Archived Serial #
37	Not a component
38	Lot is full
39	Container full
40	Wrong Revision
41	Wrong Location
42	Wrong Status
43	Not Managed
44	Duplicate Id
45	Replace Not Allowed
46	EmpVal Login Err
47	EmpVal Proc Err
48	No Attribute Needed
49	Invalid Attribute Value
50	No Attribute Assigned
51	No Attribute
52	Upload Attribute Fail
53	EmpVal Pwd Err
54	Param Error!
55	Invalid Sample!
56	Sample Loc Error
57	No Select
58	S.O. Not Found
59	S.O. Is Closed
60	Wrong Quantity
61	Create BSN Failed
62	Not a Batch SN
63	Add or Replace Comp?
64	Batch S/N is Null
65	Batch S/N is Full
66	Wrong Shop Order
67	Invalid Batch SN
68	Split Model Error -
69	Invalid Unit SN
70	BSN Exist
71	Invalid Location
72	Invalid S.O.
73	Remaining QTY
74	Invalid Group Name
75	Invalid URL
76	Invalid Flow at PTS
77	Parameter Error!
78	Cmd End
79	No Attributes!
80	Invalid Attrib!
81	Not Assigned!
82	Can’t Remove!
83	Invalid Loc=
84	FAILLOC STAT=
85	Invalid Defcode!
86	Invalid Defcode=!
87	Invalid Type=
88	Missing Attribute List!
89	Missing Process!
90	Limit 1 Process!

 

Default Informational Messages

Number	Prompt Text
1	Address and station name
2	SYSTEM SHUTDOWN
3	PASS bds to
4	PASS to
5	FAIL to
6	MOVE to
7	LOT Information
8	CONTAINER Information
9	Missing Component

 

Unit Status Definitions

The following table provides a list of available unit status settings and their definitions (if available). See Locations Maintenance in the SFDC Configuration Manual for more information.

 

Unit Status (Numeric Value)	Definition (if available)
Released (10)	Refers to Travelers being finalized.
Traveler Printed (15)	Used when a Traveler for a serial number is printed. Also used for Shop Order status when a serial number is assigned to a Shop Order but not scanned at an SFDC location yet.
On the Line (20)	Used at any location that is a part of the normal manufacturing process or product flow.
In Repair (25)	Used at any location that is not considered part of the normal manufacturing process. In creating routes, any unit with a defect is failed to a location with an In Repair status. Unless overridden by an Option setting in Setup Data Editor, the unit continues to have this status until all defects are repaired. A unit cannot be manually moved from a Data Collection Location with an In Repair status to a location with On the Line status. A unit cannot pass from this status to a Finished status.
Outside Processing (26)	Same as On the Line Hold, but this status is used to define units that require outside processing. When a unit has this status, the serial record is removed from the SFDC PC and stored on the plant server. It does not appear as part of the SFDC Work-In-Process report, but it does appear on the MDS WIP report.
In Repair Outside Processing (27)	Combines the In Repair Hold status with the secondary functions of the Outside Processing status. This status is used to define units that require repair at an outside processing location.
On the Line Hold (28)	Same as On the Line with the added ability to allow the unit to move from one SFDC PC to another within the same database. Also used to move from one route to another. When a unit has this status, the serial record is removed from the SFDC PC and stored on the plant server. It does not appear as part of the SFDC Work-In-Process report, but it does appear on the MDS WIP report.
In Repair Hold (29)	Combines the In Repair status with the secondary functions of the On Line Hold status.
Finished (30)	Defines the unit as complete. Unless the product will be installed into an upper level assembly, the route ends by passing a unit to a location with a Finished status. Neither SFDC nor MDS WIP reports include Finished status locations.
Container Open (34)
On Skid - Container Close (35)
In Container (36)	SFDC internal use status, not used in serial table.
In Transit (37)	Obsolete
Shipped (40)
Temporary Ship Status (45)
CRM Received  (46)	CRM Received & Holding
CRM Released  (47)	CRM Released for Processing.
CRM RESERVED  (48)	CRM Reserved (future use).
CRM Finished  (49)	CRM Processing Finished.
Killed (50)	Used to kill a serial number not to be shipped. Adapted for use in SFDC. When used, the serial number cannot be scanned by SFDC.
Killed (51)	Killed Manually.
Killed RBF (52)	Killed with Back Flush or Reverse Back Flush.
Pulled (55)	Another form of killed status, which can be assigned to a unit only by moving it to a location at this status.
Killed (56)	Killed without Reverse Back Flush.
CRM Restart New (57)
CRM Restart Used (58)
Unit Component (60)	Defines a unit when it is a tracked component and has not been properly removed from the Top Level assembly. Requires a special Option line to be scanned again.
Unit Old ID (62)	Defines a serial number that was changed to another serial number. All history is moved to the new serial number.
Batch Old ID (63)	Defines a batch serial number that no longer has unit serial numbers attached (empty batch sn). Empty batch serial numbers cannot process in SFDC. Once a batch serial number has had all unit serial removed, it cannot be used again.
Unit Skeleton (64)	Defines a unit serial number used for temporary copies of a real serial number.
Not DB of Record (70)	Defines a unit which has been transferred to a remote MDS db with the Data Transfer program.

 

 

Table of Revisions

Date:	Author:	Description:
6/23/04	Karen Ellington	Initial release of document to website.
8/4/04	Karen Ellington	Added status 36 to Unit Status Definitions section. General edit and format clean up.
1/06/09	Keith Fuqua	Added SFDC3 specific items, new commands, features, and updates.
01/22/10	Keith Fuqua	Batch processing, Employee validation, new commands & features.
10/29/10	Keith Fuqua	Table cleanup, document corrections.
06/17/11	Keith Fuqua	Updates for SFDC 5.22.02 – SFDC 6.0.
07/02/12	Eric Moldenauer	Updates for SFDC 6.1.

Date	Author	Title	Version	Change Reference
03/31/14	Dane Parker	Technical Writer	v 1.0	Document Creation.