FAQs: Reporting

The audit trail records all actions by all users and contains:

• date
• time
• user
• device
• event type

It captures:

• configuration changes
• template modifications
• batch deletions
• all operator actions

The audit trail can be accessed via the Management Console, filtered by date, station, and operator, then downloaded as a CSV file.

Yes. End-of-job reporting is available on screen and via a Batch Reconciliation Report generated on demand. The report includes:

• all batch runs information
• label results
• barcode results
• text results
• operator override details
• thumbnail images of inspections

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.

See an example report here.

A report can be generated on demand from any web browser by a user with the correct  user role permissions.

Azure provides standard short term operational data retention of up to 35 days for recovery purposes.

Perceptor IoT End Users may opt into a managed back up subscription providing longer term retention - 7 year or 30 year plans - with incremental daily, weekly, monthly, quarterly, and annual back ups.

The 30 year option is designed for compliance-driven industries.

Retention duration must be selected at subscription.

Purchase of long-term backup services is the End User's responsibility.

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.

Currently, inspection data is accessible only via the Management Console as a Batch Reconciliation Report (PDF) and a downloadable Audit Trail (CSV).

As all data is stored in a SQL database, reporting via Power BI is also possible.

At any time, the end user can request a full or partial extract of data from Perceptor - requests must be verified by the authorised signatory of the subscription agreement.

Yes - As Perceptor IoT reads/writes to SQP, data can be made available to third party applications via FTP if required.

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.

The following reports are available:

1. Batch Reconciliation - generated on demand as a PDF via the Web Management Console, covering all batch run information, label results, barcode results (GS1 DMx, GTIN), text results (LOT, Serial No), anchor results, operator overrides, and thumbnail images
2. Calibration History - includes operator name, station, and an image of the calibration card
3. Audit Trail - filterable by date, station, and operator, downloadable as CSV
4. Individual Label - searchable by serial number, output as HTML
5. Test Batch - clearly identifies data as test data

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. 

All inspection data, runtime data, settings, user roles, and audit trail are recorded to a central customer-specific SQL database hosted in Microsoft Azure within the Perceptor cloud tenancy.

Data is encrypted at rest.

End users do not have direct database level access; data is only accessible through the application's defined reporting functions.

Yes. Perceptor IoT allows an individual serialised label to be searched and displayed on screen, and output as an HTML webpage.

Label lookup is also accessible via the Web Management Console.

No Perceptor IoT prevents alteration of raw data.

Electronic records saved to the cloud (batch runtime records) cannot be modified by users.

Data cannot be deleted from the database by users once generated.

Label vision template deletions and batch deletions require permission and are captured by the audit trail.

Yes. Perceptor IoT allows users to switch between a sandbox test environment and the production environment.

Test batch reports are clearly identified as test data in the batch reconciliation report.