Set it once. Know when it drifts. Put it back.
Describe how your printers should be set, and PrinterVision keeps checking. When a printer drifts, you see what changed and put it back in line with one click.
- Darkness is at least70%
- Firmware is at least your chosen version
- Compliant21 printers
- Not compliant3 printers
- Unknown (not read yet)1 printer
Illustration. The policy and figures are made up.
Every printer was set up right. Once.
A technician changes the darkness to fix one label, a printer is swapped, a reset brings back the defaults. Nobody writes it down, and the fleet slowly stops being the fleet you set up.
For the site manager
What it costs your operation- Labels that scan on one line and not on the next, because two printers are no longer set the same.
- A customer or an auditor asks how your printers are set, and the answer is a walk around the site.
- The numbers you need - availability, supplies, alerts - live in nobody's spreadsheet.
For IT
What keeps you up at night- You can't prove which printers run an approved firmware, or carry the right settings.
- Fixing drift means finding it first, printer by printer.
- When something changed, you want to know who did it, and when.
Describe it, check it, fix it.
A policy says how printers should be. PrinterVision compares every printer with it, all the time, and shows the differences.
Write a policy
A scope - every printer, or by tag, manufacturer or model - and rules on settings and firmware (Zebra, Honeywell, SATO), tags and attributes (every make).
PrinterVision keeps checking
After every change to a printer and every 15 minutes: compliant, not compliant, or unknown until it has been read.
Remediate
One click writes the wanted settings, sets tags and attributes, and sends the firmware a rule names, on the makes that support it.
A printer quietly drifts on the packing line.
10:32 - After a settings refresh, PACK-12 no longer meets the policy for the packing printers: its darkness and its media sensor differ from the policy.
The printer goes out of line, and an automation on that event mails the line's technician with the differences.
The technician clicks Remediate. The wanted settings are written, the printer is compliant again, and the operation log records who did it.
Labels come out faint for days until a scanner starts refusing them, and someone compares settings by hand.
Everything that scenario runs on.
The settings you want, written down once.
A policy applies to every printer, or to printers with certain tags, manufacturers or models. Its rules cover settings, common settings and firmware of Zebra, Honeywell and SATO printers, and tags and attributes of every printer.
- A setting is, is at least, or is one of a value
- Firmware at least a version
- A tag carried or not, an attribute set or with a value
- Differences per printer, also on the printer's own page
- Going out of line, or back in, can start an automation
- Darkness55% · wanted at least 70%
- Media sensorContinuous · wanted Gap
- FirmwareOK
Illustration. The printer is made up.
Your own fields on every printer.
Add the fields your organisation needs - a cost centre, an owner, a line - set by hand, or computed from what PrinterVision knows about the printer. Use them in policies, filters and reports.
- Text, number, yes/no, choice or link
- Set by hand, or computed from an expression
- As columns and filters in the printer list
- Cost centreSet by hand
- LineChoice
- Labels per dayComputed
Illustration.
The numbers, without the spreadsheet.
Run a report when you need it, or have it arrive in your mailbox. Every action on a printer, by a person or an automation, is in the operation log.
- Inventory, alert history, availability per printer, operations, supplies (where reported) and compliance
- Filtered by period, manufacturer, tag, site and group
- CSV download, or a daily, weekly or monthly e-mail with the CSV attached
- An operation log as audit trail: who did what, on which printer, and when
- Availability · all sitesWeekly
- Supplies · Dock printersDaily
- Compliance · every printerMonthly
Illustration.
Common questions about printer compliance.
What is a printer compliance policy?
A description of how a group of printers should be set. In PrinterVision a policy has a scope - every printer, or printers with certain tags, manufacturers or models - and rules: a setting is, is at least or is one of a value, firmware is at least a version, a tag is carried or not, an attribute is set or has a value. Rules on settings and firmware apply to Zebra, Honeywell and SATO printers, whose settings PrinterVision reads; tag and attribute rules apply to every printer.
How often does PrinterVision check compliance?
After every change to a printer - a poll, a settings refresh, a tag or an attribute - and every 15 minutes. A printer whose settings have not been read yet shows as unknown rather than compliant.
How do I fix printers that drifted from their settings?
Use Remediate. PrinterVision writes the wanted settings, sets the tags and attributes the policy asks for, and sends the firmware a rule names through the normal firmware update - on the makes that support it (Zebra, Honeywell, SATO). An automation can also start when a printer goes out of line or comes back.
Which reports does PrinterVision have?
Inventory, alert history, availability per printer, operations, supplies (where the printer reports them) and compliance, filtered by period, manufacturer, tag, site and group. Download them as CSV, or schedule them daily, weekly or monthly by e-mail with the CSV attached.