Reporting resources FAQs
Reporting options and managing your dataBatch reconciliation: can a label inspection and batch reconciliation be generated?
Yes - Perceptor IoT reads/writes to SQL. A label inspection lookup can be printed to PDF and, depending on which software version the end user is running, a batch reconciliation report with all the batch and inspection results is generated.
A report can be generated on demand from any web browser by a user with the correct user role permissions.
FTP: can our data be exported by FTP?
Yes - As Perceptor IoT reads/writes to SQP, data can be made available to third party applications via FTP if required.
Database: can I connect more than one Perceptor IoT system to the database?
Yes - this is a core feature of Perceptor IoT. Global connectivity is integral to the solution, allowing multiple sites and multiple printers to be connected to the same SQL database.
Report data: how is data accessed for reporting?
Each Perceptor IoT device has its own unique Station ID and fingerprint. All data generated through a printer which has a licence for a Perceptor IoT device is recorded against the Station ID.
Reports are generated using the data from each station. For example, a Batch Reconciliation can be generated on demand via a web browser and the Perceptor Management Console. This can be a report from any period of time during which the IoT device and licence has been in use.
Power BI can be used to drill down further into data (the user needs their own Power BI licence). Data reported on can be by site, by shift, by operator, by product and by printer.
Roadmap
- Media use will be captured so that reporting can be by media batch or by media supplier.
- Field based verification: an app is planned for scanning a product in the field to check for authenticity, market location, possible counterfeits etc. The customer will be able to access their data via API.