How Much Does PLC Programming Cost in Canada? What Drives the Price
By VitroVentures Engineering · Updated · 8 min read
There is no single price for PLC programming, because two machines with the same PLC can need very different amounts of work. This guide explains what drives the cost, so you can compare quotes fairly and give an engineering firm what it needs to price your project accurately.
Why there is no standard price
People often ask for a price per I/O point or per line of code. Those numbers can be useful for a rough budget inside one company that builds similar machines again and again, but they do not travel well. A conveyor with 40 I/O and a simple start and stop sequence is a very different job from a 40 I/O machine with servo motion, recipes, a safety PLC and a vision system.
Most of the cost of PLC programming is engineering time: understanding the process, writing and organizing the logic, building HMI screens, testing, and commissioning on site. Anything that adds time to those steps adds cost. Anything that removes uncertainty before the work starts reduces it.
This article does not quote hourly rates or typical totals. Rates vary by region, by firm and by the type of work, and they change over time. Instead, it explains the factors every quote is built on, so the quotes you receive make sense.
1. The size of the system: I/O and devices
The number of inputs and outputs is the first rough measure of size. Every input and output needs a tag, an address, a description, and logic that uses it. Every device on a network (drives, robots, scanners, remote I/O, safety devices) needs to be configured and tested.
I/O count alone is not enough. Ten digital sensors take far less work than one servo axis, one weigh scale or one barcode reader that has to be parsed and checked. When you describe a project, list the devices as well as the I/O count.
2. How complex the sequence is
The sequence of operation is usually the biggest driver. A machine that runs one cycle the same way all day is simpler than one with multiple modes, product changeovers, partial cycles, manual jogging and recovery from every possible stop.
Fault handling is where much of the time goes. A good program does not just run when everything is right; it detects what went wrong, tells the operator in plain language, and lets the machine recover safely. Asking for detailed alarms and clean recovery is worth it, but it is real work and should be in the quote.
- Number of modes: automatic, manual, setup, cleaning, maintenance
- Recipes or product types and how changeover works
- Motion: VFDs, servos, coordinated axes, robots
- Interlocks with upstream and downstream equipment
- Data: counts, batch records, reports, links to other systems
3. New program or changes to an existing one
Writing a program for a new machine starts from a clean sheet. Modifying an existing program can be faster, but only if the existing program is understandable. A well-commented program with consistent tag names is easy to extend. A program with no comments, cryptic addresses and logic added by many people over many years can take longer to understand than to rewrite.
If you have the existing program, send it with the request. A quick review of the code is often the difference between a vague estimate and a firm price.
4. The platform
The controller platform affects cost in a few ways. Software licences for some platforms are expensive, and a firm that already owns and uses them every day will be faster. Some platforms make structured, reusable code easier than others. And some projects require a specific platform because of a plant standard, which is a good thing: standard hardware and code are easier to support.
For legacy upgrades, the old and new platforms both matter. Converting an Allen-Bradley SLC 500 program to CompactLogix is a different job from converting a Siemens S7-300 program to S7-1500, and both are different from moving between vendors. See our guide to PLC migration for more on this.
5. HMI screens
HMI work is often underestimated. Each screen needs to be designed, built, linked to tags and tested. A basic machine might need an overview, a manual screen, an alarm screen and a setup screen. A line with recipes, trends, user levels and maintenance screens needs many more.
If you have an HMI standard (colours, layout, navigation, alarm classes), share it. If you do not, a quote should include a simple, consistent screen design.
6. Safety
Machine safety functions such as emergency stops, guard door monitoring, light curtains and safe speed affect the hardware, the electrical design and the program. Safety functions need to be specified from a risk assessment, implemented correctly and validated. The amount of work depends on the machine and the required safety performance, so make safety requirements clear early.
7. Documentation
Documentation can be minimal or extensive. At the minimum, you should receive the final program files, an I/O list and enough comments for a maintenance technician to follow. Some projects also need a functional specification, a sequence of operation, alarm lists, operator instructions and as-built electrical drawings. More documentation costs more up front but usually saves money over the life of the machine.
8. Testing and commissioning
Testing in the office (simulation and offline testing) finds many problems before anyone travels to site. Factory Acceptance Testing (FAT) at the builder and Site Acceptance Testing (SAT) at the plant add confidence and time. On-site commissioning includes I/O checkout, functional testing, tuning, operator training and the inevitable small changes when the machine meets real product.
Site time is the hardest part to predict, because it depends on the readiness of the machine, the wiring, the utilities and the people. A clear quote states what on-site time is included and how additional time is handled.
9. How complete the information is
The less is known at the start, the more risk is built into the price, or the more the price is likely to change. A short functional description, a device list, drawings and photos reduce uncertainty for both sides. If the scope cannot be defined yet, a small paid study or a time-and-materials phase can be the fairest way to start.
Two machines, two very different scopes
Imagine two machines that both use a CompactLogix controller and a 10-inch HMI. The first is a transfer conveyor: a few motors, photo-eyes, a start and stop sequence, and an interlock with the next machine. The second is a filling machine with servo-driven pumps, recipes for different products, a weigh check, a reject station, a safety relay for the guards and batch reports.
On paper, both are "a CompactLogix program". In practice, the second needs a detailed sequence of operation, motion tuning, recipe management, more HMI screens, safety validation and a longer commissioning period with product. A fair comparison of quotes always starts with the scope, not the controller.
Costs that are easy to miss
Some costs are not obvious when a project is first discussed. Asking about them early avoids surprises.
- Software licences for the PLC, HMI or safety platform, if you need your own copy
- Travel time and expenses for sites outside the local area
- Waiting time on site when the machine, wiring or utilities are not ready
- Changes to the sequence after programming has started
- Updating electrical drawings to match the final system
- Training for operators and maintenance staff
- Remote access setup, if you want support without a site visit
How to reduce the cost without cutting corners
The best savings come from clarity, not from reducing quality. A written sequence of operation, a complete device list and a decision on the platform before the work starts make every later step faster. Standard hardware and a consistent program structure across machines reduce both programming time and long-term support costs.
Testing in the office before going to site is almost always cheaper than finding problems during commissioning. Having the machine mechanically complete, wired and checked before the programmer arrives keeps expensive site days productive.
Fixed price or hourly?
A fixed price works well when the scope is clear: new machines with a defined sequence, or upgrades where the existing program and I/O are known. Hourly billing suits work where the scope cannot be known in advance, such as troubleshooting, small changes or ongoing support. Many projects combine the two: a fixed price for the defined work and hourly rates for extra on-site time or changes.
Whichever model you choose, ask what is included. Two quotes with very different numbers often describe different scopes.
How to compare PLC programming quotes
- Are HMI screens included, and how many?
- Is safety programming included?
- What testing is included before site: simulation, FAT?
- How many days on site are included, and what happens if more are needed?
- What documentation will you receive?
- Do you receive the full, unlocked source program?
- Who owns the program, and are there licence costs?
- What support is available after startup?
What to send for an accurate quote
To get a firm price, send a short description of the machine or process, the PLC and HMI platform if it is already decided, a device list or I/O list, any existing program and drawings, photos of the machine and panels, and your timeline. Our guide on what to send an engineering firm lists everything in one place.
