After installing the Intuitive for SAFEQ on-premise solution and running the ETL application, you should start to notice data flowing into the dashboards.
However, in some cases, some customers may have unintended or lack of data in certain fields. This document will detail those fields, and how you may troubleshoot them.
In a standard implementation of SAFEQ6, some fields against a printer or user are not required to complete their setup. However, as their details flow into the Intuitive dashboards, you may notice that these fields are therefore blank in key dashboards.
Starting with the printers, the key field we use to track devices are serial numbers. They’re a key metric as devices can be renamed and moved around the estate, and it's a single, unchangeable identifier that we can use to track historical printing over time.
When a device is added or readded to SAFEQ6, behind the scenes in the target SQL Server or PostgreSQL database, that device is assigned new ID’s and potentially new names, which would ordinarily present a problem for tracking. By using the serial number as an unchanged, static measure, we can use that to present that devices’ printing, copying, faxing and scanning accurately over time.
If in Intuitive you are presented with a field called <unknown> for a device’s serial number, it’s a good indication that the target device performing that job / presenting that overall volume does not have a serial number attached to it. That field is typically called the “Equipment ID” inside of SAFEQ6, but some customers may use the “Service Agreement ID” instead. If the latter is used, you would therefore need to alter the dashboards to include this metric.
It’s a similar problem for the users themselves inside the dashboards, where the user may present an <unknown> in the OU Name field. That can be down to either a missing Department/Cost Centre against that user, or typically when they are performing Copy or Scan jobs, as those activities may not always have a Cost Centre attributed to them.
Another area to mention is how jobs are recorded at that point in time. When a user performs a print job, it’s a historical record of that users’ department at the time, the device’s name at that time, and any associated costs (if they are being used) – at that time. If any fields were not configured in the past, they will therefore be a snapshot of how that user and device were recorded – at that time. Meaning, that when users, printers or the SAFEQ6 environment as a whole is reconfigured to show richer data, it will therefore present that up-to-date information in the dashboards from that point onwards. I.e. it will not affect historical jobs and totals.