Find articles, help, and advice.

RF Code Integration Overview

Last Updated: May 09, 2013 03:47PM CDT

RF Code provides and maintains multiple integration points that leverage the power and openness of the RF Code asset management and wire-free sensor monitoring solutions.  The three integration points allow for level integration at the hardware layer, mid-level integration at the middleware layer, and high-level integration at the application layer.  RF Code’s integration strategy is to provide the appropriate level of open integration functionality at each layer of the solution to allowing developers to choose the integration path that best aligns with their integration goals and requirements.

Application Layer Integration (Asset Manager)

  • Description: Interface specification provides means to read processed and filtered asset and tag data both historical and real-time as it is reported by the Asset Manager software application.
  • Pros: Least complex integration point. Makes complete asset data for all tagged assets available for consumption, including any custom data about assets stored in the AM database. Complete historical data reporting. Useful if user has an application that requires an accurate list of assets and their locations such as CMDB or asset repository database.  Also useful for users that do not wish to employ developers to write custom software that will integrate Middleware/Location Engine level integration data with a backend system, or that have a limited amount of time to get functional.
  • Cons: Requires entire RF Code solution stack (tags, readers and Asset Manager software) which may not be ideal from partners that have existing software solutions.


Middleware/Location Engine Integration (Zone Manager)

  • Description: Interface specification provides means to read processed and filtered tag events and location data as it is reported by the Zone Manager software application.
  • Pros: Less complex than integrating at the hardware level. Tag events, including location information, tag status, data as reported by any onboard tag sensors, is already processed ready for consumption.  Useful if the system the RF Code middleware is being integrated with is designed to handle the tag to asset correlation and long term storage of the information.
  • Cons: Somewhat complex; available data is limited to tag numbers, location, and current status.


Hardware Integration (Readers)

  • Description: Interface specification provides means to read raw tag data as it is reported by the readers
  • Pros: Most useful if integrating RF Code tags and readers into an existing RFID-based system that has the capability to decode, translate, and apply logic to RF Code active tags events received from multiple readers simultaneously based on signal strength 
  • Cons: Highly complex; requires extensive work on the developers' part to process, filter and interpret the status and tag data reported by the readers.


Get Help Now
Contact a support professional by E-mail
seconds ago
a minute ago
minutes ago
an hour ago
hours ago
a day ago
days ago
Invalid characters found