# White Paper

## Tracking Print Jobs via OPC UA and Smart Print Controller

### Using Complete Files, Hot Folder Submission, and OPC UA Integration

---

# Executive Summary

Modern print production workflows require reliable traceability between Management Information Systems (MIS), prepress workflows, digital front ends (DFE), and production devices. In highly automated environments, the ability to track a print job consistently across systems is critical for:

* Production monitoring
* Reporting and analytics
* ERP and MIS integration
* Device synchronization
* Quality control
* Reprints and traceability
* Industry 4.0 and smart factory initiatives

Hybrid Software Group SmartDFE and Smart Print Controller provide an integrated mechanism to associate business identifiers with print production jobs and expose them through OPC UA for real-time monitoring and external integration.

This white paper explains:

1. How to inject tracking metadata into a SmartDFE job using Hot Folder submission
2. The purpose and usage of `JobTag`, `MIS.JobID`, and `MIS.JobPartID`
3. How Smart Print Controller exposes this information through OPC UA
4. Recommended integration patterns and best practices
5. Example OPC UA node paths and retrieval workflows

---

# Introduction

In automated print manufacturing environments, multiple systems interact during production:

* MIS / ERP systems
* Workflow automation systems
* RIP and DFE systems
* Presses and finishing devices
* Reporting and analytics platforms
* Factory automation platforms

A common challenge is maintaining a persistent identity for each job throughout the workflow.

SmartDFE and Smart Print Controller address this challenge by allowing external systems to:

* Submit jobs with business metadata
* Associate production identifiers with the job
* Monitor job state in real time
* Retrieve metadata through OPC UA

This creates a standardized bridge between print production and industrial automation systems.

---

# Architecture Overview

## Workflow Components

The typical architecture consists of:

1. MIS or ERP system
2. SmartDFE Hot Folder
3. Complete File metadata
4. Smart Print Controller
5. OPC UA server
6. External monitoring or automation clients

### Workflow Sequence

1. MIS creates a production job
2. A Complete File is generated containing production metadata
3. Files are submitted through a SmartDFE Hot Folder
4. Smart Print Controller processes the job
5. Job metadata is exposed through OPC UA
6. External systems retrieve live job status and identifiers

---

# Hot Folder Job Submission

SmartDFE supports automated job submission through Hot Folders.

A Hot Folder monitors a filesystem location and automatically imports jobs when files appear.

The submission can include:

* Artwork files
* PDFs
* Job tickets
* Complete Files containing metadata

Reference:

* SmartDFE Hot Folder Job Submission Documentation
  [https://documentation.hybridhelix.com/sdfe/hot-folder-job-submission](https://documentation.hybridhelix.com/sdfe/hot-folder-job-submission)

---

# Complete File Metadata

The Complete File is used to associate metadata with a print job.

This metadata becomes available throughout the workflow and is exposed through OPC UA.

The most important identifiers for job tracking are:

* `JobTag`
* `MIS.JobID`
* `MIS.JobPartID`

These fields provide persistent identifiers linking the production job to external business systems.

---

# JobTag

## Purpose

`JobTag` is a flexible user-defined identifier associated with the job.

It is intended for:

* Production grouping
* Workflow correlation
* Device-side tracking
* Operator visibility
* Custom automation
* External system correlation

Unlike MIS identifiers, `JobTag` is not restricted to a business system structure.

## Typical Usage

Examples:

* Shift identifier
* Campaign name
* Production batch
* Customer reference
* Automation workflow ID
* Device routing key

## Example

```json
{
  "JobTag": "Campaign_A_Label_Run"
}
```

## Best Practices

Recommended characteristics:

* Human-readable
* Short and unique
* Stable throughout production
* Avoid spaces or special characters when possible

Examples:

Good:

```text
BATCH_2026_041
CUSTOMER_X_RUN_12
SHIFT_A_ORDERS
```

Avoid:

```text
This Is A Very Long Job Tag With Many Spaces
```

---

# MIS.JobID

## Purpose

`MIS.JobID` is the primary business-level job identifier.

This value typically originates from:

* MIS
* ERP
* Order management system
* Web-to-print system

It represents the overall production order.

## Usage

This identifier should remain constant for the entire lifecycle of the production job.

Typical uses:

* Production tracking
* Reporting
* Costing
* ERP synchronization
* Analytics
* Reprint lookup
* Press reporting

## Example

```json
{
  "MIS": {
    "JobID": "ORD-2026-000245"
  }
}
```

## Characteristics

Recommended properties:

* Globally unique within the business
* Persistent
* Never reused
* Generated by the upstream business system

---

# MIS.JobPartID

## Purpose

`MIS.JobPartID` identifies a subdivision or component of a larger job.

Many print jobs consist of multiple parts:

* Different SKUs
* Multiple labels
* Versions
* Languages
* Color variants
* Packaging variations
* Finishing segments

`MIS.JobPartID` allows each production segment to be tracked independently.

## Usage Examples

### Example 1 — Multi-SKU Production

Main job:

```text
ORD-2026-000245
```

Parts:

```text
SKU_A
SKU_B
SKU_C
```

### Example 2 — Language Variants

Main job:

```text
ORD-2026-000310
```

Parts:

```text
EN
DE
FR
IT
```

### Example 3 — Repeated Production Sections

Main job:

```text
JOB_5000
```

Parts:

```text
PART_001
PART_002
PART_003
```

## Example Metadata

```json
{
  "MIS": {
    "JobID": "ORD-2026-000245",
    "JobPartID": "SKU_A"
  }
}
```

---

# Example Complete File

The following simplified example demonstrates how tracking metadata may be included in a Complete File.

```json
{
  "JobTag": "Campaign_A_Label_Run",
  "MIS": {
    "JobID": "ORD-2026-000245",
    "JobPartID": "SKU_A"
  }
}
```

When the job is imported through the Hot Folder, SmartDFE associates these identifiers with the production job.

The metadata is then propagated into Smart Print Controller and exposed via OPC UA.

---

# OPC UA Integration

## What is OPC UA?

OPC UA (Open Platform Communications Unified Architecture) is an industrial interoperability standard widely used in manufacturing and Industry 4.0 environments.

Benefits include:

* Vendor-neutral integration
* Real-time monitoring
* Structured data models
* Secure communication
* Event-driven automation
* Scalable industrial connectivity

Smart Print Controller exposes production job information through an OPC UA server.

Reference:

* OPC UA Interface Guide — Smart Connectivity
  [https://documentation.hybridhelix.com/sdfe/opc-ua-interface-guide-smart-connectivity](https://documentation.hybridhelix.com/sdfe/opc-ua-interface-guide-smart-connectivity)

---

# OPC UA Job Structure

Within the OPC UA namespace, jobs are represented using unique internal job GUIDs.

Example:

```text
372fb73d-14f9-43fc-905c-361130dc4b81
```

The namespace structure allows clients to browse and retrieve job information.

---

# OPC UA Node Examples

## Retrieve JobID

Example node:

```text
ns=2;s=AllJobs/(job guid)/JobId
```

Concrete example:

```text
ns=2;s=AllJobs/372fb73d-14f9-43fc-905c-361130dc4b81/JobId
```

Returned value:

```text
ORD-2026-000245
```

---

## Retrieve JobPartID

Example node:

```text
ns=2;s=AllJobs/372fb73d-14f9-43fc-905c-361130dc4b81/JobPartId
```

Returned value:

```text
SKU_A
```

---

## Retrieve JobTag

Example node:

```text
ns=2;s=AllJobs/372fb73d-14f9-43fc-905c-361130dc4b81/JobTag
```

Returned value:

```text
Campaign_A_Label_Run
```

---

# Active Job Monitoring

Smart Print Controller also exposes the currently active production job.

This allows external systems to monitor:

* Current production state
* Active order
* Press synchronization
* Real-time dashboards
* Production analytics

---

# Active Job OPC UA Nodes

## Active Job ID

Example:

```text
ns=2;s=ActiveJob/JobId
```

## Active Job Part ID

Example:

```text
ns=2;s=ActiveJob/JobPartId
```

## Active Job Tag

Example:

```text
ns=2;s=ActiveJob/JobTag
```

These nodes provide direct access to the metadata of the currently running production job.

---

# Recommended Integration Workflow

## Step 1 — Create Job in MIS

The business system creates:

* Order number
* Job identifier
* Part identifier
* Production metadata

Example:

```text
JobID: ORD-2026-000245
JobPartID: SKU_A
JobTag: CAMPAIGN_SPRING
```

---

## Step 2 — Generate Complete File

The Complete File includes:

```json
{
  "JobTag": "CAMPAIGN_SPRING",
  "MIS": {
    "JobID": "ORD-2026-000245",
    "JobPartID": "SKU_A"
  }
}
```

---

## Step 3 — Submit via Hot Folder

Files are dropped into the configured SmartDFE Hot Folder.

SmartDFE automatically:

* Imports the job
* Associates metadata
* Generates internal GUIDs
* Pushes the job into production

---

## Step 4 — Monitor via OPC UA

External OPC UA clients can:

* Browse jobs
* Read active job data
* Track job state
* Synchronize ERP systems
* Trigger automation
* Feed dashboards and analytics

---

# Integration Scenarios

## Scenario 1 — MES Integration

A Manufacturing Execution System (MES) subscribes to:

```text
ActiveJob/JobId
```

The MES can:

* Track current production
* Associate machine usage with orders
* Record production KPIs
* Synchronize downtime reporting

---

## Scenario 2 — Dashboard Visualization

A monitoring dashboard displays:

* Current JobID
* Current JobPartID
* Current JobTag
* Press state
* Production counters

This enables real-time operator visibility.

---

## Scenario 3 — Automated Reporting

An external reporting engine retrieves:

```text
AllJobs/{guid}/JobId
```

and correlates:

* Production metrics
* Waste metrics
* Ink usage
* Device statistics
* Operator logs

with business orders.

---

# Best Practices

## Use Stable Business Identifiers

Ensure that:

* `MIS.JobID` remains immutable
* `MIS.JobPartID` uniquely identifies subcomponents
* `JobTag` remains meaningful for operations

---

## Avoid Reusing IDs

Reusing Job IDs may create:

* Reporting conflicts
* Historical ambiguity
* Incorrect analytics
* ERP synchronization issues

---

## Standardize Naming Conventions

Recommended conventions:

```text
ORD-YYYY-NNNNNN
SKU_A
CAMPAIGN_2026_Q2
```

---

## Use OPC UA Subscriptions

Instead of constant polling, OPC UA subscriptions are recommended for:

* Lower network traffic
* Faster updates
* Real-time synchronization
* Better scalability

---

## Maintain GUID Mapping

The internal Smart Print Controller GUID should be treated as the runtime identifier.

The business identifiers:

* JobID
* JobPartID
* JobTag

should be treated as persistent external references.

---

# Security Considerations

OPC UA deployments should implement:

* Authentication
* Certificate-based trust
* Network segmentation
* Access control
* Secure endpoint configuration

This is especially important when integrating with:

* Enterprise MES systems
* Cloud analytics
* Remote monitoring environments

---

# Troubleshooting

## Missing Job Metadata

Possible causes:

* Incorrect Complete File structure
* Metadata fields not populated
* Hot Folder configuration issues
* Unsupported formatting

Recommended actions:

* Validate JSON structure
* Verify Hot Folder configuration
* Confirm metadata field names
* Inspect imported job details

---

## OPC UA Node Not Found

Possible causes:

* Job not loaded yet
* Incorrect GUID
* OPC UA namespace mismatch
* Job already completed or purged

Recommended actions:

* Browse namespace dynamically
* Verify namespace index
* Confirm job lifecycle status
* Validate client permissions

---

## Active Job Not Updating

Possible causes:

* No active production job
* Subscription delay
* Client caching
* OPC UA session issues

Recommended actions:

* Reconnect client
* Verify production state
* Validate subscription monitoring
* Check OPC UA server status

---

# Conclusion

SmartDFE and Smart Print Controller provide a robust framework for end-to-end job traceability in automated print production environments.

By embedding metadata in Complete Files and exposing it through OPC UA, organizations can:

* Connect MIS and ERP systems with production
* Enable real-time monitoring
* Improve reporting accuracy
* Support Industry 4.0 initiatives
* Simplify production analytics
* Standardize automation interfaces

Using:

* `JobTag`
* `MIS.JobID`
* `MIS.JobPartID`

organizations can maintain consistent business context throughout the entire print production lifecycle.

The OPC UA interface then provides a standardized and scalable mechanism for external systems to retrieve and monitor this information in real time.

---

# References

## SmartDFE Hot Folder Job Submission

[https://documentation.hybridhelix.com/sdfe/hot-folder-job-submission](https://documentation.hybridhelix.com/sdfe/hot-folder-job-submission)

## Smart Connectivity OPC UA Interface Guide

[https://documentation.hybridhelix.com/sdfe/opc-ua-interface-guide-smart-connectivity](https://documentation.hybridhelix.com/sdfe/opc-ua-interface-guide-smart-connectivity)

---

# Appendix A — Example OPC UA Paths

## Job Metadata

```text
ns=2;s=AllJobs/372fb73d-14f9-43fc-905c-361130dc4b81/JobId
ns=2;s=AllJobs/372fb73d-14f9-43fc-905c-361130dc4b81/JobPartId
ns=2;s=AllJobs/372fb73d-14f9-43fc-905c-361130dc4b81/JobTag
```

## Active Job Metadata

```text
ns=2;s=ActiveJob/JobId
ns=2;s=ActiveJob/JobPartId
ns=2;s=ActiveJob/JobTag
```

---

# Appendix B — Example Complete File Snippet

```json
{
  "JobTag": "CAMPAIGN_SPRING",
  "MIS": {
    "JobID": "ORD-2026-000245",
    "JobPartID": "SKU_A"
  }
}
```