Q-Tag Editor
Q-Tag Editor is required to define the data layout on RF Tags or in the PLC memory. This is a key component of the Q-Trace suite, because it provides tools to easily implement changes as they relate to the ever changing data requirements. Many times, quality issues arise that require you to track additional data. This may be a temporary adjustment to identify quality issues or a permanent change to support customer requirements. Q-Tag Editor is designed to be flexible and comprehensive, thus allowing you to easily manage changes in your process. Additionally, Q-Tag Editor automatically maintains versions of all memory map layouts avoiding any impact on historical data.

The editor consists of a set of graphical utilities designed to configure different data types that are then related to their associated stations and/or operations. Users can define and configure the physical tag/memory layout to:

• Relate the status data (pass/fail/bypass/abort) on the tag to specific stations and/or operations
  • Identify and map the status data for a station and operation to a particular address location on the memory map (1, 2 or more bytes of data)

• Create quantitative data items for stations
  • Configure bit data types (representing quantitative data such as: force too high, pressure too low, etc). These data items will be represented as bits (0 being false and 1 being true)

• Create quality data for stations and/or operations
  • Configure multiple data values (different data types such as integer, float etc) for each station or operation

• Create component data for stations and/or operations
  • Configure alphanumeric component data such as: part numbers, serial numbers, data matrix codes, and relate them to specific station or operation

Q-Tag Editor also provides a “scripting” feature, which facilitates massaging the data prior to committing to the database. Three scripting modes are supported, they are: ‘read code’, ‘write code’ and ‘report code’. Utilizing the scripting features, your data collection components will adapt to exception situations.

• Read Code: business logic that is executed while the tag is being read. This is typically used for data validation, identifying missing data, etc.

• Write Code: business logic to write information back to the tag. Typically used to inform the downstream stations if the upload succeeded or failed in the previous upload stations

• Report Code: business logic to massage and interpret the data that is being committed to the database. Bits, abbreviated codes, and/or values can be interpreted and converted into descriptive data