Function Called (URI)

Function Type

Overview & Purpose

Logic

Restrictions

Files Updated

RFDASUPD

EVENT

UPDATE_UDA: – Update LOCEX UDA with Asset last seen timestamp  

LOCEX

RFDAUTO

EVENT

AUTOPICKER: – Integration to Barbaric AutoPicker Controls      

RFDAUTX

EVENT

DOORBLANKWRAPPER: – Integration to Bartender Commander  and Integration to Paint Robotic PLC         

RFDAWAY

EVENT

EXPORT_XML_GOLD: – This is designed to be used in conjunction with GOLD ERP system interfacing with AssetTrack Warehouse Module

when Inventory put-away transactions are processed via ATW (AssetTrack Warehouse), these are transformed into an XML document and passed to GOLD on a real-time basis. The document is placed in a nominated folder by GOLD and then picked up and processed to update its inventory.

** not intended to be used with any Reader Schedule, It is a standalone binding function independent of Reader activity

NONE – produces XML extract file

RFDBAE2

EVENT

SHARED_PORTAL: – This is a function that enables a single reader to be shared by two portals (doorways, etc.) as well as share a single GPIO SmartBox for both sensor input and stack light output. For example; Doorway 1 will have antennas 1 & 2 (antenna Group A) and Doorway 2 will have antennas 3 & 4 (antenna Group B).  Read cycle is not fixed for any duration as with other binding functions, it is based on when the door opens (start) and door closes (end) for each portal. IMOVE rules run in the background based on tag movements. Optionally the binding function can send data to a portal event viewer by adding SETVIEWER(*NEW) to the CONNECT command plus adding the IP address of the portal event viewer to the location.

Tags read at Doorway 1 with antennas group A will use std match / nomatch / notag. Tags read at Doorway 2 with antennas group B will use Aux1 / Aux2 / Aux3. Antenna location names can be used to group antennas together else antenna 1-2 and 3-4.   When the Doorway 1 Trigger is detected RCL turns on TRIGGERON condition for INPUT-1 and TRIGGEROFF when door is shut. Same is achieved for INPUT-2. It is important to note there is contention between both triggers, before turning off the read cycle the logic will check to see if the other door is still open and thus keep the read cycle going.  There is a failsafe mechanism in place when using trigger off. If both triggers are not off and the tag read exceeds the read event cycle, tag read will cycle through. Meaning, if both or either portals are left open, the read event cycle (at 20sec in this example) will dictate/override the tag read.There is a failsafe mechanism in place when using trigger off. If both triggers are not off and the tag read exceeds the read event cycle, tag read will cycle through. Meaning, if both or either portals are left open, the read event cycle (at 20sec in this example) will dictate/override the tag read. Making the read event cycle longer makes sense but not too long. Remember, if both portals are closed before the read event cycle then tag read ceases and will cycle through again.

On the physical reader profile you must nominate which antenna does what. Example:  Antenna Location 1 name = INJECTOR-1 and Antenna Location 2 name = INJECTOR-2. Note: Antenna names in the Reader profile must be unique across all readers and this is not programmatically validated.    Six (6) light output conditions are required for this binding. The SmartBox output wiring has been modified to map signals 1, 2 & 3 to OUTPUT 1 and signals 4, 5 & 5 to OUTPUT 2.

RFDPHLOG, RFDLOLOG, RFDLOCIN

RFDBBAE

EVENT

 ORACLE2_TEMPLATE: – This binding validates one or many product object tags (known as Primary) and passes them to Oracle function for evaluation. Optionally a tag can be included in the read event that represents the dept or user (known as Secondary). Note: The primary or secondary designation is defined by the Item type code in the product master. Oracle will evaluate the payload and then return a group condition code that indicates the overall status of the tag(s) read. The conditions can be mapped to RCL output conditions and displayed via stack lights. Additionally, the results of the read events can pushed to the nominated PEV for visualization by specifying the SETVIEWER(*NEW) condition. Note: this binding is intended to be triggered

When the read event is triggered, the tag(s) are evaluated to ensure they are mapped correctly and that there is at least (1) Primary designated Tag. If so, those are passed to Oracle one tag block at a time (11 attributes as described in mappings below) until all tags in that read event group have been passed and accepted. Oracle then writes the result set for that Group ID to an internal Oracle work file that includes the following attributes; Group ID, Condition Code & textual description (future use).  Binding function queries this table until the result set is found in the table (see Binding Settings).     For your RCL post-processor scripts, you need to define MATCH (Condition 1), AUX2 (Condition 2), AUX3 (Condition 3), NOMATCH (condition 4), NOTAG (no tags read), AUX1 (only secondary tag read).  In addition, you must specify an ERROR since an interface is involved. If you don’t have a script for ERROR, the job will send an email notification if so configured in the binding settings and attempts recovery.

The Primary tags must be mapped to a product and have a non blank container code in TGMAP and must have LOCIN record with a Level1 and Lot # value.

RFDPHLOG, RFDLOLOG

RFDBMEM

EVENT

MEMORY_BANK_PAYLOAD: – Memory Bank Payload integration with Oracle      

RFDBMHM

EVENT

 ACCUTRAC_TEMPLATE: – This is designed to be used in conjunction with directional intelligence feature used at a given read zone/portal. Updates current location for a given asset tag in the Accutrac SQL Server database. 

** Primary ** evaluates the tag event to determine whether the tag read is new to this read zone (reader/antenna combination). If yes then determines if there is a match in the Movement Rules using the previous and current read zones. If match made, updates PHLOG with the movement code (displayed in Event viewer). ** Secondary ** with a match made in primary logic, checks to see if at least one asset tag and one badge tag have been seen together (within ‘x’ read events specified in system settings), if yes then SQL call is made to update new location of a given Asset Tag within Accutrac System.

** must be used alone as the only synchronous binding function. Any other logic must be included in that binding function

RFDPHLOG, RFDLOLOG, RFDCOMMS

RFDBSCI

EVENT

MULTI_TRIGGER TMPLT: – This is a function that captures Tag Event information on a food processing rail via a specific antenna based on the triggering port, and writes it to a customer specific log file.

When the Antenna 1 Trigger is detected RCL turns on SignalON1 light, and antenna #1 will attempt to read a valid tag. If it is seen, the RCL turns on the appropriate light (MATCH or NOTAG). When the Antenna 2 Trigger is detected RCL turns on SignalON2 light, and antenna #2 will attempt to read a valid tag. If it is seen, the RCL turns on the appropriate signal output (AUX1 for match or AUX2 for notag conditions).

On the physical reader profile you must nominate which antenna does what. Example:  Antenna Location 1 name = INJECTOR-1 and Antenna Location 2 name = INJECTOR-2. Note: Antenna names in the Reader profile must be unique across all readers and this is not programmatically validated

RFDPHLOG, RFDLOLOG, RFDSCLOG

RFDBSCP

EVENT

RAIL_PORTAL: – This is a function that captures Tag Event information on a food processing rail and writes it to a customer specific log file. The tags are affixed to hanging ‘trees’ that are read as they pass by a given reader/antenna.

Portal is not intended to be triggered nor display any output light conditions, Antenna is on all the time looking for a valid tree tag. If a valid tree tag is found a record is written to RFDSCLOG at the plant level (TAGID, ANTENNA NAME, DATE & TIME + STATUS). A job is then submitted to update the given read event information to a corporate instance of SQL (table dbo.tblRFIDReaderData). If the JDBC interface fails, then a manual batch program (Resend_RFID_Data_Log.bat) must be run to pickup any unprocessed records in SCLOG and resend them to corporate table.

On the physical reader profile you must nominate which antenna does what as a single reader could support multiple (up to 4) read points. Example:  Antenna Location 1 name = WEIGHSCALE1 or Antenna Location 2 name = SMOKEHOUSE. Note: Antenna names in the Reader profile must be unique across all readers and this is not programmatically validated.

RFDPHLOG, RFDLOLOG, RFDSCLOG

RFDBSTCH

EVENT

SMS_MESSAGE: – This is a function that captures Tag Event information on employee objects and sends it to the SingleTouch SMS Service for furtherance to a subscriber phone.

Employee object tags are selected from read event cycle, if the mapped employee has a valid phone number in the badge ID then a post is made to the SingleTouch website passing the phone # and Reader location that tag was read at. The subscriber will then receive an SMS message from the SingleTouch service based on the business rules setup with SingleTouch. GPIO conditions of MATCH (at least one tag read is mapped) and NOMATCH (tags are read but none are mapped) and NOTAG (no tags are read during read cycle) are supported if enabled in the RCL. PEV output is also supported if enabled in RCL with SETVIEWER(*NEW) directive.

The reader location alias must be populated as this is what is sent to SMS service. The singletouchsms.htm document must be in the designated folder specified in the binding settings as shown below

RFDPHLOG, RFDLOLOG

RFDBTCC

EVENT

LIBRARY_TEMPLATE: – This is a check-out / check-in function intended to be used in a library circulation desk setting. Books that are being checked-in are passed in front of antenna A and books being checked-out are passed in front of antenna B. The TagID of the books are sent to a hardware keyboard wedge that populates the appropriate field of any given LMS (Library Management System).

When the book tag is seen at the check-out antenna, it populates the BIN Map date/time in RFDTGMAP with current date/time.  This is checked later on in the verification binding LIBRARY_PORTAL_TEMPLATE (below). When the book tag is seen at the check-in antenna, it clears the BIN Map date/time in RFDTGMAP.    Settings Options – uses the ‘Interface IP Address’ for the Keyboard Wedge as well as specifying the ‘Terminate With’ escape character. The ‘Dwell Time’ setting allows for the tag to be ignored in succeeding reads thereby not being reprocessed.    For your RCL post-processor scripts, you need to define AUX1 (book checked out confirmation), AUX2 (book checked in confirmation) & AUX3 (error - book is already checked in or out) conditions.  In addition, you must specify an ERROR since an interface is involved. If you don’t have a script for ERROR, the job will end, sends an email notification if so configured and attempts to restart if there is a recovery attempt specified

On the physical reader profile you must nominate which antenna does what. Example:  Antenna Location 1 = CHECKIN and Antenna Location 2 = CHECKOUT   Settings Options – uses the ‘Interface IP Address’ for the Keyboard Wedge as well as specifying the ‘Terminate With’ escape character. The ‘Dwell Time’ setting allows for the tag to be ignored in succeeding reads thereby not being reprocessed.

RFDTGMAP

RFDCSHP

EXTRACT

EXPORT_ASN: – This is designed to be used in conjunction with the PEV_DOD_SHIPVERIFY Event binding when interfacing with Mil Pac’s WAWF engine

when user selects [Generate ASN] button from PEV, it produces an extract file that gets placed in the directory path specified in the binding function. Mil Pac polls this directory and imports that into its repository

** not intended to be used with any Reader Schedule, It is a standalone binding function independent of Reader activity

NONE – produces XML extract file

RFDDCOM

EVENT

TAG_DECOMMISSION : – Decommission Tag (TGMAP + LOCIN)                 

RFDTGMAP, RFDLOCIN

RFDEAGG

EXTRACT

EXTRACT_AGGREGATION : – Extract SU Assignment to Sparta             

RFDEIN2

EXTRACT

EXTRACT_INV_TRANS_2 : – Inventory Transaction Extract basic             

NONE – produces CSV extract file

RFDEINV

EXTRACT

FTP_EXTRACT : – Extract Inventory Transactions            

NONE – produces CSV extract file

RFDELLS

EVENT

PEV_IMOVE_ELLSWORTH: – Broadcast Read events to PEV clients (with IMOVE)       

RFDFULL

EVENT

FULL_INVENTORY: – Program Binding Template for Full Inventory

RFDHDSP

EVENT

HD_STORED_PROCEDURE: – H-D Stored Procedure to SQL (Tomahawk)

RFDIAST

IMPORT

IMPORT_ASSET_DATA: – Import Asset data from flat file

UCCRCIM, RFDASSM, RFDASSEX

RFDIINV

IMPORT

IMPORT_INV_LOCATION: – Import Tag Location inventory from flat file

LOCIN, LOCIH

RFDIITM

IMPORT

IMPORT_ITEM_MAP_LOCN: – Import Complete Object Mapping info for Monstanto

LOCIN, LOCIH

RFDILOG

IMPORT

IMPORT_RFIDLOG: – This is designed to be used in conjunction with Mil Pac labeling software interfacing with TagNet ‘s DoD Event History

when SmartLabels are printed/commissioned from Mil-Pac, it produces (if configured) an extract file that gets placed in the directory path specified in the binding function. TagNet polls this directory and imports that into the DoD Event History file (DODEH). Before the file is imported it is renamed to avoid any contention with new inbound files of same name from Mil Pac.  . When so instructed from DoD PEV, interfaces with Mil Pac for ASN furtherance to WAWF.

** not intended to be used with any Reader Schedule, It is a standalone binding function independent of Reader activity

RFDDODEH

RFDIMAP

IMPORT

IMPORT_ASSET_MAPPING: – Import Asset data from flat file                 

LOCIN, LOCIH

RFDIMLOC

IMPORT

IMPORT_MAPPING_LOCN: – Import Tag Mapping and Location for Monstanto

LOCIN, LOCIH

RFDIOIN

IMPORT

IMPORT_OBJ_INFO: – Import UDA data from flat file to UDAXR

LOCIN, LOCIH

RFDMMAP

EVENT

ACCUTRAC_TAG_MAPPING: – This is designed to be used in conjunction with ZPL label printing from Accutrac.

receives CSV print file from Accutrac system (SendtoRFPrinter.exe), maps print parameters to TagNet ZPL format, and prints/commissions to RFID enabled printer.

** designed to be used with ACCUTRAC label print function only.

NONE

RFDNTFY

EVENT

TAG_NOTIFICATION: – Send out JSON payload of Event Notification

RFDPCHK

EVENT

PEV_CHECKIN_CHECKOUT: – This is designed to be used in conjunction with the PEV (Portal Event viewer) client application and IMOVE logic

is called directly from PEV client when Check-in / Check-out feature is enabled. The [Accept] action will send the payload of employee + assets cached on PEV via RFDPCHK binding function will return back results of update. See Check-in / Check-out addendum for more details.

** not intended to be applied directly against a reader schedule

RFDLOCIN, RFDLOCIH

RFDPCMR

EVENT

CAMERA_TEMPLATE: – This is designed to be used in conjunction with the image capture feature configured in the Physical Reader profile.

instructs the digital camera to take a picture when the read event cycle is trigged in a schedule, and associates that image with the Tag event log record. Outputs image to C:\rfid\capture folder that can be viewed in the Tag Event Viewer.

** can be used alone as the only synchronous binding function or in conjunction with Movement logic binding function

Camera file?

RFDPDII

IMPORT

IMPORT_PDI_WITH_ITEM: – Import PDI Object data for TB

RFDPEVD

EVENT

PEV_TEMPLATE – This is designed to be used in conjunction with the PEV (Portal Event viewer) client application

collects whatever tags are read during a given read event cycle from a given portal, and pushes them in real time to the PEV display so they can be visualized. Payload includes base attributes of each object type of person, product, GTIN, Container, or Asset. This also incorporates PMOV logic

** can be used alone as the only synchronous binding function and must have the SETVIEWER(*NEW) in the CONNECT statement of the RCL Script.

RFDLOCIN, RFDLOCIH

RFDPEVG

EVENT

PEV_Generic – This is designed to be used in conjunction with the PEV (Portal Event viewer) client application

collects whatever tags are read during a given read event cycle from a given portal, and pushes them in real time to the PEV display so they can be visualized. Payload includes base attributes of each object type of person, product, GTIN, Container, or Asset. This also incorporates PMOV logic

RFDLOCIN, RFDLOCIH

RFDPEVT

EVENT

SHIP_VERIFY TEMPLATE: – validates EPC tags on outbound portal against Event history to ensure they are valid and updates ship date/time + Logical Reader portal.

accumulates all tags read during reader duration cycle. Does a lookup of that EPC against the TagNet Event History. If hit, updates the record with read verify time/date stamp and sends match condition. If no hit, no update takes place and sends no-match condition.

none at this time

RFDEPCH

RFDPINV

EVENT

PEV_INVENTORY: – This is designed to be used in conjunction with the PEV (Portal Event viewer) client application and IMOVE logic

collects whatever tags are read during a given read event cycle from a given portal, and pushes them in real time to the PEV display so they can be visualized. Looks for IMOVE matches and automatically transfers inventory from location A to Location B. Includes base attributes of each object type of person, product, or Asset. Supports full GPIO script as a result of standard match / nomatch / notag variables.

** can be used alone as the only synchronous binding function and must have the SETVIEWER (*NEW) in the CONNECT statement of the RCL Script.

RFDPHLOG, RFDLOLOG, RFDLOCIN, RFDLOCIH

RFDPLC1

EVENT

H-D_PLC_PAINT_LOAD: – Integration to Paint Robotic PLC

RFDPLC2

EVENT

H-D_PLC_PAINT_LOAD2 : – Combined Integration of PLC1/HDSP

RFDPMAP

EVENT

TAGMAP_TEMPLATE: – This is designed to be used in conjunction with a Label Print template. It takes entered parameters and stores them in a number of TagNet mapping files.  Program executes some pre-processor logic before actually calling the Print routine. This is used in conjunction with a Binding definition (RFDPSQL) the returns these values to the enterprise system requesting that information.  IP Address – set to jdbc:oracle:thin:@192.168.0.203:1521:ORA. User Name & Password – Credentials to connect to Oracle DB

ensures that the entered parameters (Item, quantity, Cage code, date code) are valid, populates the mapping files, then substrings in the values to the ZPL template and submits a print job to send the final ZPL to an RFID printer.

none at this time

RFDTGMAP, RFDLOCTN

RFDPMOV

EVENT

 MOVEMENT_TEMPLATE: – This is designed to be used in conjunction with directional intelligence feature used at a given read zone/portal.

evaluates the tag event to determine whether the tag read is new to this read zone (reader/antenna combination). If yes then determines if there is a match in the Tag Movement Rules (TMOVE) using the previous and current read zones. If match made, updates PHLOG with the movement code (displayed in Event viewer). Also includes camera integration logic if enabled at reader level, outputs image to C:\rfid\capture folder (or whatever is configured in system settings).

must be used alone as the only synchronous binding function. Any other logic must be included in that binding function.

RFDPHLOG, RFDLOLOG, RFDCOMMS, RFDNETCH

RFDPOST

EVENT

 ENDPOINT_POST: – Post simple XML to an HTTP endpoint on read event

evaluates the tag event to determine whether the tag read is new to this read zone (reader/antenna combination). If yes then determines if there is a match in the Tag Movement Rules (TMOVE) using the previous and current read zones. If match made, updates PHLOG with the movement code (displayed in Event viewer). Also includes camera integration logic if enabled at reader level, outputs image to C:\rfid\capture folder (or whatever is configured in system settings).

RFDPPLT

EVENT

CONVEYOR_TEMPLATE: – Typically used for Tagging Stations module where case/cartons are being validated on conveyer after print applicator applies tag to case. Adjusts for pallet counts.

accumulates all tags read during reader duration cycle (normally 1 at-a-time on conveyer). Does a lookup of that EPC against the TagNet Event History. If hit, updates the record with read verify time/date stamp and sends match condition. If no hit, no update takes place and sends no-match condition. Keeps track of current Pallet ID (EPC) and adjusts the case Pallet EPC if tagged cases have been diverted off conveyer for whatever reason

none at this time

RFDEPCH

RFDPRMT

EVENT

 OBJECTLOOKUP_TEMPLATE: – This is designed to be used in a closed loop model when validating a tag to see if it is mapped to a valid Object ID. Typically used for Demo purposes.

accumulates all tags read during reader duration cycle. Firstly, if the TagID is a valid EPC# and determined to be an SGTIN, it does a lookup of that GTIN against the TagNet Item Master. If no hit, it then looks to see if it has a TagNet mapping association and checks that mapping against either a valid product or person ID. If all tags read meet either of the above conditions, then Match condition is sent, if not then no-match condition is sent.

no file updates take place

NONE

RFDPSCR

EVENT

COMPLIANCY_TEMPLATE: – This is designed to be used in a compliancy model when validating outbound tagged product against previously commissioned tags. Used in conjunction with Smart Label Printing updating TagNet EPC Event History (usually by Customer batch jobs). Typically used in Stretch wrapper application where case/cartons are being validated on pallet turntable. Responsibility of customer to ensure that all EPC’s have a correct and common Pallet ID. 

accumulates all tags read during reader duration cycle, looks up EPC# in Event History, if found then updates ship verify date/time and Match condition is sent, else if not found no-match condition is sent. All tags read must belong to same container ID, if no-match is sent

If EPC# does not exist in Event History, no update will take place (assumes tag was not commissioned at the location). Requires RCL script to instruct read cycle of Reader

RFDEPCH

RFDPSHP

EVENT

PEV_DOD_SHIPVERIFY: – This is designed to be used in conjunction with the PEV (Portal Event viewer) client application and DoD Event History

collects whatever tags are read during a given read event cycle from a given portal, and if the exist in DODEH, pushes them in real time to the PEV display so they can be visualized. Displays Container level as well as aggregated cases below that and automatically updates which tags were read in DODEH. When so instructed from DoD PEV, interfaces with Mil Pac for ASN furtherance to WAWF (see EXPORT_ASN Binding). Supports full GPIO script as a result of standard match / nomatch / notag variables.

** can be used alone as the only synchronous binding function and must have the SETVIEWER (*NEW) in the CONNECT statement of the RCL Script.

RFDPHLOG, RFDLOLOG, RFDDODEH

RFDPSQL

EVENT

ORACLE_TEMPLATE: – This is designed to be used in conjunction with a call to an Oracle based stored procedure. The program executes some pre-processor logic before actually evoking the RPC. . IP Address – set to jdbc:oracle:thin:@192.168.0.203:1521:ORA.User Name & Password – Credentials to connect to Oracle DB

ensures that there is a valid product tag as well as an employee (badge) tag before calling RPC. Passes a number of parameters that are retrieved from TagNet mapping files. Oracle RPC returns either a Match or NoMatch condition. Updates standard subscription activity history

none at this time

RFDEPCEH, RFDPHLOG, RFDLOLOG

RFDPTCC

EVENT

LIBRARY_PORTAL_TMPLT: – This is designed to be used in conjunction with the LIBRARY_TEMPLATE above that checks out books from a library setting. When the book passes through an RFID read zone (typically security pedestals), it validates that the book was actually checked out.

when the book tag is read, the BIN date/time in RFDTGMAP is checked to see if it is populated, if so then book has been checked-out and MATCH condition is sent to RCL. If the values are blank, then book as not been checked-out and a NOMATCH is sent to RCL. If no tag is read then a NOTAG condition is sent. Note: if multiple tags are read, they all must be checked-out to get MATCH condition. If at least one tag is not, then NOMATCH is sent.     Settings Options – The ‘Dwell Time’ setting allows for the tag to be ignored in succeeding reads thereby not being logged or indicating any RCL conditions until the dwell time period has been reached.

On the physical reader profile you must nominate which antennas are to be used and name them portal. Example:  Antenna Location 1 = PORTAL and Antenna Location 2 = PORTAL

NONE

RFDWSDL

EVENT

SAP_WEB_SERVICE: – Web Service  to SAP via MII  (WSDL/SOAP)

RFDZCTG

EVENT

HSC_ZONE_CATEGORY: – Broadcast Read events to PEV clients (with IMOVE)