Implement PDI (Production Data Interface)

Implementing PDI (Production Data Interface)

This feature enables a Customer ERP or MTO (Made-to-Order) system to pass along & associate manufacturing attributes to an RFID tagged WIP item within TagNet. This provides multiple benefits downstream such as enabling IoT and automating repetitive tasks such as recording station-to-station progression movements and label printing during packaging/assembly. It also enables this data to be selectively 'visualized' on monitors (via a simple web browser) placed at these stations where it is a benefit for the operator to see data relevant to their operation in real-time. The RFID tagged production item can also communicate to PLC/Robotic systems on various lines (e.g. machining, paint, assembly, etc.) to instruct how those lines need to perform their operations on that particular tagged WIP item. Additionally, the RFID event data can be integrated with production reporting systems as to when the part(s) arrived at a given station, how long they dwelled there and what took place.

Note: Implementing PDI is is an advanced topic and requires proper planning and the involvement of multiple departments such as order processing, engineering, production, IT, etc. Ideally you would have gone through a Phase I implementation with Stratum guiding the way achieving a foundation of basic event management (e.g. where is my 'stuff'). This is the important starting point so that you have event data that is accurate and meaningful. Planning is the most important step in an RFID implementation prior to execution so that time and budgets are used most effectively.

Key Workflow Steps:

1.Customer's order configuration data is extracted on a regular basis (e.g. hourly) to simple CSV files and placed in a nominated folder as seen in Step #2. The scope of this data can range from a few attributes to 100's based on your industry and level of desired automation. An example of such metadata configuration can be seen here.

2.TagNet polls that shared folder and imports that configuration data into its Object Repository in Step #3.

3.The CSV data is imported into TagNet by means of a Data Import Binding as seen here. This is linked to a scheduled task the polls the folder and imports the CSV files based on the desired frequency.

4.This dataset is stored in a simple staging table and can be updated and modified in Step #1 up until such time the manufactured item is either picked or started for production (e.g. door blank, cabinet frame, etc.)

5.The associative process can happen in multiple ways based on your Industry and the AIDC methods deployed.

❖In the Door industry, if a robotic AutoPicker is deployed this happens when the the correct stock size door is picked from the slab inventory. Note that in this case the AutoPicker carriage is RFID enabled as part of the implementation.

❖In the Cabinet industry, this can be when the Tag is applied to the cabinet frame (or other component), or when the tag applied previously is scanned using a Handheld device to link the picked item with the PDI attributes.

6.The end result of this process is that the tagged item has its needed attributes ready to be visualized/integrated during the manufacturing process. An example of this can be seen below in TagNet's Inventory Inquiry.

Example of TagNet User Defined Attributes (UDA's) used in a PDI Implementation

Example of Inventoried Tagged Item with its UDA Associations