System Requirements (SPC)

System Requirements

This section outlines the typical hardware and system requirements for running Smart Print Controller (SPC) and RIP Server.

Actual requirements will vary depending on:

• Job size and resolution

• Throughput requirements

• Use of features such as RIPAhead and proofing

Performance considerations

SPC can perform additional roles such as:

• Proofing

• RIPAhead

These features increase system load.

If you plan to use RIPAhead, ensure that the SPC machine has sufficient CPU and memory, as it must match the memory requirements of the RIP Server.

System configuration requirements

Antivirus

• Antivirus software is optional

• Recommendation: Do not run antivirus on SPC or RIP Server systems

  • Can significantly impact RIP and data throughput performance

Firewall and ports

• Firewall configuration is implementation-dependent

• SPC and RIP Server communicate using:

  • A shared folder

  • Network ports (configuration-dependent)

If a firewall is enabled, required ports must be opened to allow communication.

File sharing

• The RIP Server must expose a shared folder

• This folder must be:

  • Accessible from the SPC machine

  • Configured with read/write permissions

This is required for job transfer and processing.

Time synchronization

• Not strictly required

• Recommended: Keep SPC and RIP Server system clocks synchronized

This simplifies log correlation and troubleshooting.

Typical SPC system requirements

Typical RIP Server system requirements

Key differences: SPC vs RIP Server

SPC (Control + Optional RIPAhead)
- Moderate CPU
- High RAM (if RIPAhead enabled)
- Handles job orchestration + optional processing

RIP Server (Processing Engine)
- High CPU
- Very high RAM
- Handles raster generation and output

Practical guidance

• Prioritize CPU and RAM over storage for performance

• Size systems based on:

  • Maximum job size

  • Required throughput (jobs/hour)

• If unsure, start with recommended specs and scale based on testing