How to create a Basic Route PN SN

 

 

 

Basic Flow

This document outlines how to create a very basic route according to the following steps:

1. Create Algorithm
2. Create PNs
3. Map PN to a Route
4. Add Attribute (Optional)
5. Create Shop Order (with PN)
6. Release SNs (for Shop Order)
7. Scan SNs

Prerequisites

All Devices, Locations, and Data Collectors are already configured.

Before you Begin

1. Station ID has to be linked to the Location you plan to use. (Our Example: Location: p99dcval1)
2. Check to make sure the Station ID you plan to use is Active.
3. Activate or Add a Station ID here: Administration > SFDC Admin > Device Maintenance.

Screenshot: Activate or Add Station ID

4. For this example, we are using VALIDATION as our Station ID.

Note: It's helpful to jot down the configurations on a post-it or notebook, as you will need to move between several portlets to get everything set up.

Create an Algorithm

 

1. Go to: Shop Floor Control > Configuration > Algorithm Tool
2. Select Create Algorithm
3. The next available Algorithm Number is automatically displayed. Use the dropdown if you'd like a different one. (Our Example: 20179: You will need this number to create PNs)
4. Select Type from dropdown. (Our Example: Shop Order Algorithm).
5. Select Add.
6. Select Element Type (Our Example: constant)
7. Add Element Name (Our Example is OLE: This means that the name of each SN will begin with OLE)
8. Select OK
9. Select Element Type again to define the second part of your algorithm. (Our Example is: sequence.)
10. Select Element Name. (Our Example is nn: This means that the sequence will contain 2 numbers together).
11. Fill in the Minimum/Maximum Values. This sets the beginning and ending SNs that can be assigned. (Our Example: 01-99). You could choose 00-99; 11-22; 01-09; etc.
12. Click OK.
13. Click Test Algorithm.

Test Algorithm

Screenshot: ''''TestAlgorithm

 

 

1. Enter the Starting SN (Our Example: OLE01)
2. Click Test Algorithm
3. System generates a list of SNs.
4. Click OK
5. You MUST test the algorithm to assign the SNs as Active (next step).
6. Tick Active.
7. Tick Enabled.
8. Click OK.

Screenshot: Create an Algorithm

 

Create Part Numbers (PNs)

 

SNs are linked to PNs. In order to release SNs, you must first create a PN. PNs are the foundation for traceability.

1. Go to: Shop Floor Control > Configuration > SFDC Configuration > Part Number

Screenshot: Part Number Icon

2. Add Part Number
3. Complete the Mandatory Fields:

• Part #: Enter a PN. (Our Example: OLE001)
• Description: Enter a Description Title. (Our Example: Documentation)
• SN Algorithm: (Our Example: 20179)
• Serialized Item: Tick the Serialized Item box.
• Project ID: Pick from the drop-down list. (Our Example: Docs) Define your own (4 characters or less) by selecting the management icon next to Project ID:

Screenshot: Project ID Management Icon

Screenshot: Create PN (TOP of the FORM)

Screenshot: Create PN (BOTTOM of the FORM)

4. Check it. (Type your PN in the filtering fields)
5. There it is…..

Screenshot: PN Successfully Created

 

Map the PN to a Route

 

1. Go to: Shop Floor Control > Configuration > Product Route

Screenshot: Product Route Icon

1. Select Add
2. Every field is mandatory.
3. Best practice naming conventions are noted in<a href="https://docs.google.com/document/d/1C6in9ByMppv3K7F0JTN0s-enYuvx7BmuJXc0uaY-EQg/edit#heading=h.cvppgf2jes56"> this document.</a>

Screenshot: Route Name: Our Example

4. Hit Save.
5. The Route Step screen automatically displays.

 

Create Routes

Route Step 1

1. To create the first step in your production route:
2. Select the following:

• Tick Standard
• Check Start
• Location: Select the first step. (Our Example: ASSY Assembly)
• Pass: Select where you want your product to go next. "where you want your product to pass to…" (Our Example: FCT1 Func Test. We want our product to move to a test station after it is built.)
• Fail: Select where you want your product to go if it fails. (Our Example: AS2R AssyRework. We want our product to move to an Assembly Rework Station if it fails.)

• If the location route steps you want aren't in the drop-down list, go back to the main page in SFDC Configuration and configure them: Shop Floor Control > Configuration > Location

 

Screenshot: Location Icon

Screenshot: Route Step 1 (This is the Route Step Screen)

 

 

Create Route Step 2

Screenshot: Create Route Step 2

 

Create Route Step 3

Screenshot: Create Route Step 3

Screenshot: Route Steps Successful

 

Part X Route Assignment

 

Screenshot: Part x Route Assignment

 

Screenshot: Add Part X Route Assignment: Our Example

Screenshot: Save/Save & Publish

 

 

Add an Attribute

 

 

 

Screenshot: Process/Location

Screenshot: Attribute: Our Example

 

 

Screenshot: Step List

 

Screenshot: Attribute Step Form

 

 

Screenshot: Attribute Name and Prompt

 

Note: It is best practice to use a specific Attribute Name - it becomes a reference designator for bang bang commands, which you may decide to use at a different time.

Screenshot: Complete Attribute Step Form

 

Screenshot: Save Attribute Again

 

Create A Shop Order

 

1. You will create your Shop Order and Release the SNs in the same place.
2. Go to: Shop Floor Control > Production Control > Shop Order Control
3. Pick Shop Order Release.
4. It looks like this:

Screenshot: Shop Order Release Icon

5. Add the Mandatory fields:
   1. Shop Order Number (Our Example: TRAINING_101)
   2. Part Number (Our Example: OLE001). There is no drop-down. Did you jot it down?
   3. Quantity: Select the number of SNs you want to release (Our Example: 10)
   4. Save

Screenshot: Add Shop Order

 

Release SNs

 

1. Locate the Shop Order you just created with the search filter (Our Example: TRAINING_101).
2. Pick Release.
3. Follow the prompts at the bottom of each pop-up screen.

Screenshot: Release SNs

Screenshot: Release Wizard

4. Click Next

Screenshot: Release by Algorithm

5. Choose By Algorithm (Our Example: SNs OLE15 - OLE25 will be released because we specified 10 SNs to be released and the first one was OLE15)
6. Click Next

Screenshot: Full Release (10)

7. Choose Full Release or Partial Release. (Our Example: Full Release of all 10 SNs).

Screenshot: Release Summary

8. Click Next.

Screenshot: Release Results

9. Click Next
10. Click Finish.

Save Everything!!!!

1. If you're working in SFDC, you will need to save everything by updating the server.
2. NOTE: Production Scanning (Conduit) saves within the application itself as the final configuration step. All other steps prior to Saving are the same in SFDC and Production Scanning.
3. Go here: Administration > SFDC Administrator > Download & Services
4. Pick the Shop Floor ID from the drop-down (Our Example: p99dcval1)
5. Pick the Download (Our Example: SFDC Download)
6. Execute
7. It takes a while. Don't leave the screen.
8. You have to execute the Download and the Service separately.

Screenshot: Download Complete

9. Pick the Service (Our Example: SFDC Restart)

Screenshot: Restart Complete

10. Attention: If you go back and add anything else to your Route or PN, or etc. you need to do this whole step again, or configurations will not be saved.

Screenshot: Download Your Data

Scan SN

 

1. It is time to "move to production" and scan those SNs you just created.
2. Go to: Production > Data Collector
3. Enter Station ID (It was VALIDATION). No Drop-down menu.

Screenshot: Enter Station ID in Data Collector

File:Data Collector.pn

4. Select Unit ID from drop-down (Location/Process + First Step of your Route.)
5. Our Example: p99dcval1 005 Assembly

Screenshot: Select Unit ID

6. Enter/Scan SN

Screenshot: Scan/Enter SN

7. If you have an attribute defined to the step, it will display on the right.
8. You can't move any further until you answer the question with the right mask. (Our Example was Yes). Remember that we added the attribute to make the shop floor operator pay attention.

Screenshot: Attribute Prompt

9. Click Next.
10. End Transaction (ASSY Step) (Enter End or click the orange end icon)

Screenshot: End Transaction

11. Enter the next Step for SN OLE15 (Our Example: Functional Test)
12. Scan/Enter SN (Our Example: OLE15)
13. Save.
14. Success Message displays. Your SN moved to the next step.

Screenshot: Success Message: Pass to FCT1

15. Scan SN at next Step (FCT1 Functional Test).

Screenshot: Scan OLE15 SN at Functional Test

16. End Transaction (Type End or click the orange End icon).
17. In Our Example, we passed the SN to Complete after it was tested (FDC1 Func Test). (see the below screenshot).

Screenshot: Success Message: End Functional Test

Screenshot: Record/Repair Defect Options

Flowchart: Route Steps

 

>>>>> gd2md-html alert: inline image link here (to images/How-To21.png). Store image on your image server and adjust path/filename if necessary.
(<a href="#">Back to top</a>)(<a href="#gdcalert24">Next alert</a>)
>>>>> <img src="images/How-To21.png" width="" alt="alt_text" title="image_tooltip">

Revision Log

Rev #	Revision Date	Section(s) Modified	Updated by	Reviewed & Approved by	Published by
A	2/2/2018	Initial Document	Martha Jordan

 

1. However, If the SN had failed inspection and needed to move to the ASSY Rework station, we would need to Record the Defect, then Repair the Defect. To complete those defect operations, we would need a pre-configured defect code. Defect codes are configured similar to the

>>>>> gd2md-html alert: undefined internal link (link text: "Attribute Definition"). Did you generate a TOC?
(<a href="#">Back to top</a>)(<a href="#gdcalert21">Next alert</a>)
>>>>>

<a href="#heading=h.4hbn811mhper">Attribute Definition</a> in: Shop Floor Control > Configuration > <a href="https://42qrpt1.42-q.com/mes_wiki/index.php/SOP-5-I-MES0006-C_RA1_Defect_Codes_Maintenance">Defect.</a>

>>>>> gd2md-html alert: inline image link here (to images/How-To19.png). Store image on your image server and adjust path/filename if necessary.
(<a href="#">Back to top</a>)(<a href="#gdcalert22">Next alert</a>)
>>>>> <img src="images/How-To19.png" width="" alt="alt_text" title="image_tooltip">