Difference between revisions of "Best Practice for Designing a Rifidi APP"
From RifidiWiki
| Line 11: | Line 11: | ||
==Design== | ==Design== | ||
| − | + | ||
| − | + | *What Hardware (readers and sensors) are you looking to use? | |
| + | **Do these sensors come out of the box with Rifidi? | ||
| + | ***If No then one can be developed using the Sensor API - [How_to_create_a_sensor_plugin] | ||
Revision as of 18:21, 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?
- If No then one can be developed using the Sensor API - [How_to_create_a_sensor_plugin]
- Do these sensors come out of the box with Rifidi?
