Supported Devices

OptimiDoc integrates with multifunction printers from all major manufacturers. Most vendors are supported through a vendor-specific embedded framework that installs an OptimiDoc terminal on the device panel; Fiery is supported as a network print target with server-side accounting. Each vendor page below lists the supported model families, firmware requirements, and the integration features available for that platform.

Integration Types

OptimiDoc supports two fundamentally different integration types, which determine what a device can do:

• Embedded-terminal vendors — OptimiDoc installs an application on the device control panel. These devices can lock the panel behind authentication (card, PIN, login/password), release held print jobs at the device, account copies and prints, and (for most) run scan workflows. This covers Konica Minolta, Develop, Xerox, HP (Enterprise and Pro), Lexmark, Epson, Ricoh, Canon, and Kyocera. (Ricoh is embedded but provides a configurable landing page rather than a full web terminal.)

• Print- and accounting-only targets — Fiery print controllers have no embedded platform. OptimiDoc delivers jobs over standard network protocols and reconciles print usage by reading the controller's job log. There is no on-device terminal, authentication, or scanning.

In This Section

Feature Comparison

* Fiery has no walk-up copier, so there is no copy accounting; it does support print-job accounting by reconciling the Fiery controller's job log against jobs released through OptimiDoc.

† Remote login (unlocking a device from the OptimiDoc web/mobile app) is supported, but remote logout is not implemented for Lexmark, Canon, or Ricoh. Konica Minolta, Develop, and Kyocera do not support remote login/logout at all; authentication is performed at the device panel.

Accounting at a Glance

Different vendors report usage in different ways, which affects how quickly and how granularly usage appears in OptimiDoc:

• Push (real-time): Konica Minolta and Develop send counter notifications after each job; HP posts to a registered statistics agent. Usage appears almost immediately.

• Polled: Xerox is polled via Job Based Accounting (and purged) on a five-minute interval; Fiery's job log is polled every minute; Epson usage is read from the device job log when the device notifies the server.

• Requires Device Authentication: Canon, Kyocera, and Ricoh can only account copies when Device Authentication is enabled.

Choosing a Device

When planning a deployment, consider the following factors:

• Embedded framework support — not all models within a family support embedded applications. Check the vendor page for the minimum firmware version.

• Card reader compatibility — USB card readers must be supported by the device's embedded framework. See the vendor page for tested reader models.

• Network requirements — OptimiDoc communicates with devices over HTTP/HTTPS on vendor-specific ports (for example, Konica Minolta OpenAPI on 14267, Canon on 8000/8443, Kyocera on 8080) and monitors them via SNMP (ports 161/162). Ensure the relevant ports are open between the server and the devices.

• Scan requirements — if device scanning is needed, check the vendor page: Kyocera and Epson scan natively through the device engine, most other embedded vendors scan through their embedded framework, and Canon, Ricoh, and Fiery do not offer device scan.

• Terminal vs print-only — choose an embedded-terminal vendor for walk-up authentication, release, and copy accounting; Fiery is appropriate where the target is a print controller and only print-job accounting is required.

Related Articles

• Managing Devices

• SNMP Configuration

• Device Monitoring