Book a consultation

Engineering and Integration

Systems Integration

PLC, HMI and SCADA, delivered by the people who have to defend the design

Classic systems integration: PLC and HMI programming, SCADA and historian build, control panel and network design, commissioning and handover. It is the scope every plant recognises, and the one most often delivered to a standard the plant only discovers after the integrator has gone.

Joltek delivers this work directly. Independence does not stop at advice. We write the code, build the screens, commission the line and hand over documentation the plant can actually maintain. Because no vendor pays us, the platform is chosen on what fits the site rather than on what we would rather sell.

Why it matters

What this costs when it is left alone

The reasons this work gets deferred are usually the reasons it gets expensive.

Code outlives the project

The integrator leaves after handover. The logic stays for fifteen years, and every future change is priced against how readable it is.

Standards are the whole game

Consistent tag naming, structured routines and documented interlocks are what separate a system the plant can support from one only its author understands.

Commissioning is where scope hides

Most overruns are not programming problems. They are undocumented I/O, missing acceptance criteria, and interlocks nobody agreed on in writing.

Handover decides the payback

A line that runs on the day of handover but cannot be modified by plant staff has moved the cost, not removed it.

Our approach

How the work runs

We bring the same discipline to delivering the work that we bring to governing somebody else's. Design first, standards agreed before a routine is written, and acceptance criteria that cannot be quietly reinterpreted later.

01

Design and Specification

  • Define the control philosophy, I/O list and functional description before development starts
  • Agree tag standards, naming conventions and code structure with the plant, in writing
  • Set acceptance criteria describing how the system must behave, not merely that it must run
02

Controls Development

  • PLC programming on Rockwell and Siemens platforms, built to the agreed standard
  • HMI and operator screen design that matches site templates and existing operator habits
  • SCADA and historian configuration, tag mapping and alarm rationalisation
03

Panel, Network and Field

  • Control panel design and specification, including drives, safety and industrial computing
  • Industrial Ethernet layout, addressing and segmentation, so the network is designed rather than inherited
  • Instrument and device selection, with the diagnostics needed to troubleshoot it later
04

Commissioning and Handover

  • Factory and site acceptance testing against the criteria agreed at the start
  • Startup support, tuning and defect resolution through to stable production
  • As-built drawings, commented code and operator training, so the plant owns the system

What we deliver

What you end up holding

  • A functional design specification agreed before development begins
  • PLC, HMI and SCADA applications written to a documented site standard
  • Control panel and network designs, drawings and device schedules
  • Factory and site acceptance test plans, executed and signed off
  • As-built documentation, commented code and handover training for plant staff

Who we support

Who this is for

Plant and Project Engineers
who need a line delivered and cannot absorb another system nobody can support.
Operations and Maintenance Leaders
who will own the result long after the project team has gone.
OEMs and Machine Builders
needing controls delivered to an end customer's site standard.

Why Joltek

What you are actually buying

We Deliver, and We Stay Independent

No vendor pays us a commission, a referral fee or a share of licence revenue. The platform is chosen on fit. That is unusual for an integrator, and it is the point of the offer.

Written to Be Inherited

Standards, naming and documentation are agreed with the plant up front, because somebody else maintains this next year.

Ownership Through Handover

The engagement ends when the plant can run and modify the system, not when the line first makes product.

Questions

Answered before you ask

What does Joltek's systems integration scope actually cover?

PLC and HMI programming, SCADA and historian configuration, control panel and network design, commissioning, and handover documentation. Work is delivered primarily on Rockwell and Siemens controls with Ignition for SCADA, though platform choice follows the plant standard rather than a preference of ours.

You describe yourselves as independent. Can an integrator be independent?

Independence here has a specific, checkable meaning. No vendor pays us a commission, a referral fee, or a share of licence or hardware revenue, and our fee is the same whichever platform an engagement lands on, including the platform you already own. Every vendor relationship is disclosed on the Partners page.

How is this different from your IT/OT Architecture service?

Systems Integration delivers the control layer itself, meaning PLC, HMI, SCADA, panel and network. IT/OT Architecture is the layer above it: how plant data gets modelled, moved and consumed by enterprise systems. Many projects need both, and they are scoped separately because they answer different questions.

Will our team be able to maintain what you build?

That is treated as an acceptance criterion rather than a courtesy. Code standards and naming are agreed with your team before development starts, the application ships commented and documented, and maintenance and operator training is part of handover rather than an option on top of it.

Do you take over integration work that has already started?

Yes, and it is a common request: a project that has stalled, an integrator that has left, or code nobody can safely change. That work starts with an assessment of what actually exists, because committing to a completion date before reading the logic would repeat the original mistake.

Have a project that needs technical ownership?

Send us the situation. If it is not something we should take on, we will say so.