Main performance indicators of PLC programmable controller
On this page
What are the main performance indicators of a PLC?
Four indicators carry a selection: scan time (how fast the controller cycles, from sub-millisecond on performance CPUs to tens of milliseconds), program memory (how much logic and data the application can hold), I/O capacity (how many points the system can address), and reliability characteristics (how the family behaves over years of duty). The selection discipline is to match them to the measured application rather than to buy headroom: a simple machine does not need flagship scan times, and a flagship does not rescue an undersized I/O plan.
An earlier version of this page quoted fixed numerical ranges as if they were universal. Controller specifications vary by family and generation, so this version explains what each indicator means and where to confirm the number: the manufacturer's selection data for the exact model.
The four indicators
| Indicator | What it measures | Where the number lives |
|---|---|---|
| Scan time / execution speed | How quickly the controller completes a cycle or executes a standard instruction set | The CPU's datasheet; figures are per instruction type and conditions |
| Program and data memory | How much user program and data the application can hold | The CPU model's specification; per family and generation |
| I/O capacity | How many local and distributed points the system can address | The family's system manual, including expansion rules |
| Reliability characteristics | Design for continuous duty: environment ratings, redundancy options, support lifecycle | Environmental specifications and the vendor's lifecycle documentation |
Scroll the table horizontally to view all columns.
Source: manufacturer selection data. Numbers differ between families and generations; quote the exact order number when comparing.
Matching indicators to the application
The application class sets which indicator leads. A discrete sequencing machine leads with I/O count and leaves scan time comfortably inside any modern CPU's ability. A process application leads with analog capability, loop performance and availability features. A motion application leads with execution speed and the motion-specific capabilities of the family. Over-specifying wastes budget; under-specifying the leading indicator wastes the project. The order of operations: write the machine's requirement list first, then let it pick the indicator that matters, then the class.
Example: two projects, two leading indicators
A palletiser with 80 digital points and straightforward sequencing buys on I/O count and leaves it there. A six-axis handling cell buys on execution speed and motion integration. Neither project is "better specified"; each leads with the indicator its application actually stresses.
Common questions
Which indicator matters most?
The one the application stresses. Speed-critical duty leads with execution speed; large systems lead with I/O capacity; logic-heavy programs lead with memory. Most applications stress exactly one of the four, with the others satisfied by any modern controller.
What scan time is "fast enough"?
Fast enough for the fastest event the program must catch, which is a property of the machine, not of the catalogue. Discrete sequencing tolerates generous cycles; motion and high-speed counting do not. Compute the requirement from the machine, then check the CPU's documented figures.
Can memory be upgraded later?
Families differ: some allow memory or daughter-card expansion, others make the initial CPU choice final. Check the expansion path before committing, and size honestly from the program's realistic growth rather than from optimism.
Sourcing help
Send the application requirements and the shortlist. KOEED quotes matching controllers across the major brands, with the selection data attached, in active and EOL stock.
Need a quote for this part?
Send us the part number or article link — we will confirm price, availability and lead time.