Difference between revisions of "Best Practice for Designing a Rifidi APP"

Revision as of 18:40, 26 August 2014

Here is an overview on the best practices for How to Approach designing a Rifidi Application

The Goal

First ask your self what is the goal of the application such as automation of a business process, increased productivity/efficiency, tracability of an asset, security, visibility into the supply chain etc..

Problems to be solved

Once you have a clearer understanding of the Goal the ask your self what problems are you looking to solve such as Asset Tracking, Inventory Control, Inventory Management, Automation of a business process through sensors/RFID, Work in Progress (WIP). Defnitions of these can be found in the business solutions offered by Transcends using the Rifidi Platform Transcends Sensor Business Solutions

Design

• What Hardware (readers and sensors) are you looking to use?
  • Do these sensors come out of the box with Rifidi? (LLRP, Motorola, Impinj, Alien, ThingMagic, CSL, Thinkify, any handheld vis Generic Reader Adapter, Opticon Bar Code)
    • Yes - Following the user's guide User's_Guide and/or quick start guide the sensor/reader adapter can be configured to start reading
• The Application Design - Basically a Rifidi APP has access to any configured sensor/reader
• 1
  • • No - One can be developed using the Sensor API - How_to_create_a_sensor_plugin
• What are you integrating with? (Such as MySQLO database, Messaging Queue, ERP/CRM system via WebServices, Cloud/AWS)
  • Example Jumpstart Rifidi Applications for those integrations mentioned can be found here Rifidi APP Jumpstarts