Premium masterclass
MeasureColor Production: From Setup to Daily Operation
Master the measurement workflow that runs the pressroom.
Course syllabus
- Installing and configuring MeasureColor Production
- Job templates, color bars, tolerances
- PQX, CXF, MIF, ICC, CGATS: what each format gives you
- Daily operator routine: measure, judge, document
- Integration with your MIS / job management via open XML
- Troubleshooting common errors and false positives
Course content
The full lesson, module by module
The video is the introduction. The complete written course is below, structured to match the syllabus. Read it in one sitting or come back module by module.
MeasureColor Production runs on Windows workstations on your local network. The installer sets up the application, a local SQL database, and a service that talks to your measurement devices. License activation is per workstation; an enterprise license covers multiple seats.
Network topology matters more than people expect. The measurement workstation needs to reach the instruments (USB or network), the database (local or central), and any MIS integration endpoint. Plan VLAN segmentation and firewall rules before commissioning, not after.
Device pairing is the first concrete configuration. Connect an eXact 2 handheld via USB and the application detects it within seconds. For IntelliTrax2, the connection is typically over Ethernet to a controller running the X-Rite service. Both flows are guided by the application; manual driver installation is rarely required.
Calibration is the last step before production use. White-tile calibration ties your instrument to its reference; black calibration sets the dark response; spectral calibration verifies the wavelength accuracy. A new install should run all three; routine production runs only white tile, typically daily or per-shift.
Data residency is a feature, not a fix. MeasureColor stores its data inside your network by default. There is no mandatory cloud component. If you choose to aggregate data centrally across multiple plants, the central database is yours, on your servers, not a vendor cloud.
A job template in MeasureColor defines the color bar layout (patch sequence and dimensions), the targets per patch (CIELAB or spectral), the tolerances per patch, and the reporting outputs. A well-designed template library is the difference between an operator measuring a sheet in 30 seconds versus 5 minutes.
Color bar layout follows your existing pressroom practice. If you use System Brunner Mini-Spot, define a template that matches its patch positions. If you use a customer-specific bar (some brand owners insist on their own), build a template per customer. Templates are versioned; do not rebuild them per job.
Targets per patch come from your fingerprint. The most reliable source is a measured press fingerprint taken under controlled conditions on the same substrate the production will run on. Generic targets from ISO 12647 or GRACoL work as a starting point but always sit looser than a measured fingerprint.
Tolerances are where customer requirements meet operational reality. A typical setup uses ΔE 00 for solids, ΔE 00 for grays, ΔH for hue at low chroma, and density for ink-key feedback. The tighter the tolerance, the more often the operator will need to react; calibrate tolerances to your shop's actual capability, not aspirational targets.
Templates evolve. Quarterly review your top 10 templates and look at failure-mode distribution. If a specific patch fails frequently, it might need a tolerance review or a target update. The template library is a living asset, not a one-time setup.
PQX (Print Quality eXchange) is the ISO 20616-1:2017 standard for exchanging measurement data between systems. It is the format brand owners increasingly request for supplier reporting because it is open, vendor-neutral, and includes both measurement values and the measurement conditions (instrument, illuminant, geometry). Use PQX for brand-owner reports.
CXF (Color Exchange Format) is the X-Rite-led ISO 17972 standard for exchanging color data, including spectral information. CXF/X-4 specifically targets characterization data exchange. Use CXF when sharing spectral data with prepress tools that need full reflectance curves.
MIF (Measurement Interchange Format) is MeasureColor's native exchange format and is the most flexible for in-house workflows. It captures the full job context including templates, tolerances, and metadata. Use MIF for internal data movement; switch to PQX or CXF for external sharing.
ICC profiles encode the color characterization of a device or condition. They are the foundation of color management but are not measurement records; they describe what a device or process produces in general, not what was measured on a specific sheet. Use ICC for prepress soft-proofing and process characterization.
CGATS (Committee for Graphic Arts Technologies Standards) defines text-based exchange formats including CGATS.17, the workhorse format for round-tripping measurement data between systems. It is human-readable and widely supported. Use CGATS for legacy integrations or anywhere a CSV-equivalent is needed.
Open standards reduce vendor lock-in. MeasureColor supports all five for import and export. Choose the format based on the receiver, not the sender.
Step one is measurement. The operator pulls a sheet from the delivery, places it on the scanning table or under the inline scanner, and triggers a scan. With IntelliTrax2 this takes under 10 seconds for a full B1 color bar. With a handheld and a Bestrack-style bar, allow 90 seconds for a competent operator.
Step two is judgment. The software shows pass / fail per patch, ΔE 00 per ink, density deltas, and trend over the last N sheets. The operator decides: is this an acceptable sheet, a sheet that needs an ink-key adjustment, or a sheet indicating a non-correctable problem (contamination, wrong plate, fountain issue)? The software gives the data; the operator owns the decision.
Step three is documentation. The measurement is automatically stored against the job ID and timestamped. No manual logging required; the data trail builds itself. At the end of the job, the operator (or supervisor) can generate a quality report PDF or PQX for the customer, signed off with the operator's ID.
This routine is unchanged from job to job, which is its strength. Every job, every shift, every operator follows the same three steps. The variance in outcomes comes from the press, the ink, the substrate, not from procedural differences.
A team running this routine for the first time will be slow. After a month, the routine takes under a minute per sheet on most jobs. The time pays back many times over in faster makereadies and lower reject rates.
A pressroom MIS (Management Information System) like HIFLOW, EFI Pace, Optimus, or Cerm tracks jobs, schedules, costs, and customer information. Without integration, MeasureColor measurements live in their own world and the MIS has no visibility into quality.
Integration goes both ways. From MIS to MeasureColor: when a job is scheduled, push the job ID, customer, substrate, and required template to the measurement workstation. The operator does not hunt for the right template; it is pre-loaded. From MeasureColor to MIS: when a job completes, push the quality summary back to the MIS for billing, customer reporting, and trend analysis.
The protocol is XML over HTTP for most modern MIS systems, with JDF/JMF as the standardized envelope. Older systems may require flat-file exchange via a watched folder. MeasureColor supports both.
The integration is one-time effort with ongoing payoff. After commissioning, the MIS becomes the single source of truth for what was scheduled and what was delivered. Quality reports stop being a separate process; they are a byproduct of running the job.
In multi-site deployments, the MIS-MeasureColor link is also the bridge that lets central management see across plants. A brand owner whose work runs in three of your sites can receive one aggregated quality report at the end of the quarter.
False positive ΔE failure is the most common operator complaint. The press looks fine, the sheet looks fine, but the software flags failure. The usual causes are: wrong template (job ran with the previous job's template), expired calibration on the measurement device, or a misaligned color bar (scan head positioned 2 mm off, reading the wrong patch).
Mismatched job templates happen when the MIS link drops or when the operator manually picks the wrong template. The fix is to enforce template selection from the MIS-pushed job ID, with the operator able to override only with a documented reason.
UV LED drift on IntelliTrax2 is gradual. The UV source ages, the M1 readings drift, and what was a clean ΔE 00 = 1.5 yesterday reads ΔE 00 = 2.4 today. Annual recertification through X-Rite or a certified partner is the answer. If you skip recertification, expect 3 % per year measurement drift.
Polarizer wear on handhelds shows up as inconsistent density on glossy stocks. The polarizer is a consumable in M3-only handheld measurements; budget for replacement every 18 to 24 months in heavy use.
Sample-pad cleanliness on scanning tables: a contaminated white reference under the scan head produces false drift over a run. Daily wipe of the reference tile with a lint-free cloth is the cheapest reliability improvement available.
The single biggest source of false alarms in production is mismatched conditions: M0 measurement compared against M1 target, or polarized compared against unpolarized. The template should pin the measurement condition; mismatches should error out, not silently produce nonsense.
Other masterclasses