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 main integration point is a 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.
Middle Layer Intergration (Zone Manager)
- Description: Interface specification provides means to read processed and filtered real-time location and sensor data from RF Code tags.
- Pros: Ideal for partners or customers who have existing software solutions and want to consume RF Code sensor and location data in real-time.
- Cons: Requires custom integration work with the top-end application. Does not store tag data in a database (real-time data stream only).