Fiery

Fiery print controllers (RIPs) are supported by OptimiDoc as network print targets with server-side print-job accounting. Unlike multifunction devices from other vendors, Fiery does not provide an embedded application platform, so OptimiDoc interacts with it as a print destination using standard network protocols and reconciles usage by reading the controller's job log.

Fiery is a print- and accounting-only vendor: there is no embedded terminal, no device authentication, and no panel application. It does not appear on the device with an OptimiDoc UI — it is driven entirely from the server.

Integration Method

Fiery controllers do not have a device-specific API or embedded application layer. OptimiDoc delivers jobs to Fiery using standard network printing protocols:

• IPP (Internet Printing Protocol)

• IPPS (IPP over HTTPS)

• LPR (Line Printer Remote)

• JetDirect (raw TCP port 9100)

No application is installed on the Fiery device, and there is no install or uninstall step — OptimiDoc treats Fiery purely as a delivery target and (optionally) an accounting source.

How the Integration Works

1. Job delivery

Users print to an OptimiDoc pull-print queue as normal. When a job is released, OptimiDoc delivers it to the Fiery controller over the configured network protocol (IPP/IPPS/LPR/JetDirect). Because there is no on-device terminal, release happens from the OptimiDoc web interface or at another (embedded-terminal) device.

2. Print-job accounting (job-log polling)

Although Fiery has no embedded agent, OptimiDoc can account Fiery print jobs. On a one-minute interval, OptimiDoc reads the controller's job log, and for each entry it finds the matching job that was released through OptimiDoc (matched by the job owner and title). It then records the real page and colour counters from the controller into the accounting record, applies the device's price list, and marks the job complete. A cursor of the highest processed job id ensures each job is accounted only once.

Only jobs printed through OptimiDoc are accounted this way — entries in the Fiery log that do not correspond to an OptimiDoc-released job are skipped.

3. What is not available

Fiery has no copier and no scanner exposed to OptimiDoc, so walk-up copy accounting and scanning are not applicable. There is no card reader, device authentication, or landing page.

Supported Models

OptimiDoc supports any Fiery print controller that accepts jobs via standard network printing protocols, including:

• Fiery E-series controllers

• Fiery IC-series controllers

• EFI Fiery embedded controllers

Supported Features

Authentication and User Attribution

Fiery controllers have no device authentication and no embedded terminal, so the Terminal tab (where authentication methods are chosen for other vendors) is not shown for a Fiery device. Users are not authenticated at the controller.

Instead, print jobs are attributed to users by the job owner recorded in the Fiery job log, which OptimiDoc matches against the owner of the job released through the pull-print queue. Card-based and device-level authentication methods are therefore not available.

Prerequisites

1. Ensure network connectivity between the OptimiDoc server and the Fiery controller.

2. Choose a print protocol (IPP, IPPS, LPR, or JetDirect) and verify the corresponding port is open.

3. Note the Fiery credentials if the controller requires authentication for print-job submission.

4. Enable job logging / accounting on the Fiery controller if you want OptimiDoc to reconcile print counts from its job log.

Known Limitations

• No embedded terminal — Fiery is a print target with no on-device OptimiDoc application.

• No copy or scan — a Fiery RIP has no copier or scanner exposed to OptimiDoc.

• No device authentication — card-based or device-level authentication methods are not available; users are attributed by job owner.

• Accounting scope — only jobs printed through OptimiDoc are reconciled from the Fiery job log; unrelated log entries are ignored.

• No remote install/uninstall — there is no application to install on the device.

In Summary

Fiery is treated as a network print target with server-side accounting. OptimiDoc delivers released jobs over IPP/IPPS/LPR/JetDirect, then reconciles page and colour counts by polling the Fiery controller's job log once a minute and matching entries to OptimiDoc-released jobs by owner and title. There is no embedded terminal, device authentication, copy accounting, or scanning — Fiery is a print- and print-accounting-only integration.

Related Articles

• Managing Devices

• Driverless Print (IPP)

• Supported Devices