How to use suppliers to push data to a global OPS

Introduction

This document will teach users how to send information from a 42Q MES instance to a 42Q Global instance. This functionality is similar to the Import API which allows users to send defects, repairs, components, measurements, comments, attributes, etc.

 

 

Push data to a global OPS

1. Navigate to: Shop Floor Control > Configuration > Shop Floor Configuration > Data Editor.
2. Select the checkbox of the Shop Floor ID.
3. Select Edit.

Figure 1: Edit Button

 

4. Optionally, enter the URL_WEB_SERVICE NAME and VALUE.

For more information, please refer to the document: Conduit Command Appendix.

 

Figure 2: URL, Web Service Name And Value

 

5. Enter the Serial Input Mask that was defined in the Target Client.

 

Figure 3: Serial Input Mask

 

6. Navigate to: Shop Floor Control > Configuration > Shop Floor Configuration > Product Route.
7. Select the checkbox of the Shop Floor ID.
8. Select Edit.
9. Select the Route Step.
10. Select the Edit icon.

 

Figure 4: Edit Icon

 

11. Check the box: Start? to start the serial number in that step on the route.
12. Enter the Route and Location created by the Target Client.
13. Select Save to save all changes or Cancel to abort.

 

Figure 5: Editing The Route Step

 

Note: Both the part number (as seen in the image below) and auto create user on the scan option must be set inside the Target Client. The auto_configuration_publish generic attribute must be configured in the Generic Attribute Maintenance portlet whilst the part number defined in the Setup Data Editor must be set in the Part Number portlet within the Target environment to help the administrator to reduce the quantity of configuration.
 

 

Figure 6: Part Number Defined In The Setup Data Editor

 

14. Notice that in the image below, the serial number pushed already has activities in the Unit History.

 

Figure 7: Serial Number With Activities

 

15. On the other hand, users can notice that in the image below, the serial number in the Target Client does not have any activity.

 

Figure 8: Serial Number Without Activities

 

16. Scan the serial number.
17. Run the command Export Remote Unit Activity.
18. Enter the Remote Workstation, and the Remote Destination (in this case, in the same location).

 

 

Figure 9: Sending Data From A 42Q MES Instance To A 42Q Global Instance

 

19. Scan the END command to finish the transaction. A pop-up window will appear to confirm that the import was successful.

 

Figure 10: Unit Import Success Message

 

20. As users can see in the image below, all the activities have been imported to the Target Site. There is an error on the parametric data due to the parametric tables not being set on the Target DB.

 

Figure 11: Activities Imported To The Target Site

 

---