Service

HMI and SCADA systems

We build an operator interface that shows the state of the machine at a glance. After a stoppage there is no guessing: the alarm log says what happened and when.

  • Operator interfaces
  • Alarms and trends
  • Access control
  • Remote access

When people get in touch

The symptoms that
usually come up

“It stopped and we do not know why”

The machine stops, and the operator tries to work out what is wrong from the lamps and the noise.

  • Alarms in plain, readable wording
  • A timestamp and acknowledgement state for every event
  • A searchable event history for maintenance

No data, only impressions

Everyone feels that it “got slower”, but there is nothing to point to when a decision has to be made.

  • Trend recording on the signals that matter
  • Cycle times and downtime reported
  • Exportable data for further analysis

Everyone has access to everything

Parameters can be changed freely, and afterwards there is no telling who changed what.

  • Roles: operator, maintenance, administrator
  • Protected parameters and setting limits
  • Logged changes
A machine-side operator panel with a touchscreen and an emergency stop button
An operator panel at the machine — touchscreen, mode selector, emergency stop

What the work involves

What we build
into the interface

Screen design and operator logic

First we settle who the screen is for, and what they have to be able to see at a single glance.

  • Overview, machine and process views
  • Manual and automatic mode shown unambiguously
  • Consistent use of colour and status indication

Alarms, trends, logging

An alarm is not a flashing line of text but an event you can look up.

  • Alarm list with filtering and acknowledgement
  • Trends for the selected analogue signals
  • Run-time and event logging
  • Production data collection, technical groundwork for an ERP or MES connection

Access and connectivity

Access control and, where it makes sense, secure remote visibility.

  • Role-based permissions
  • Web or remote access, agreed with the operations team
  • Redundancy where availability calls for it

What you receive at handover

  • The HMI/SCADA project source and a runnable backup
  • Screen and alarm lists with the signal assignments
  • Operating instructions for the operators, in plain language
  • A description of the permission roles

Why SKY SOL

Why it is worth
calling us

Ten years in the field

The team has spent ten years in industrial environments: programming, commissioning, fault finding. We do not know machines from textbooks.

One engineer, start to finish

The same person surveys the job, writes the program and commissions it. You never have to explain the same thing twice, and nothing is lost in a handover.

The source code is yours

The program backup, the I/O list and the operating instructions are part of the handover, not a separately priced item. The system does not tie you to us.

From the operator point of view

We design the screen for the person standing at the machine at two in the morning — not for the person who developed it.

Boundaries

Where our work
ends

Scope — what we do not take on

Clear boundaries

We design and develop the operator interface and connect it to the controller. Procuring and installing the panel and the hardware, and running the IT network, are not ours to do.

Why this is good for you

Hardware and network decisions belong to whoever runs them — we supply the technical requirements and fit the interface to them.

FAQ

What people
usually ask

What is the difference between HMI and SCADA?

The HMI is the panel at the machine: it starts, stops, sets parameters and shows faults. SCADA is wider — it ties several machines or a whole process together, with stored data, trends and an alarm log. In a smaller plant a well-written HMI is often enough.

Which development tool is the interface built in?

We use the manufacturer tool that belongs to the controller. That keeps the system workable for your own maintenance people too. Where the choice is open, we suggest the one that fits your existing toolset.

Can the system be accessed remotely?

Technically yes. But it is also a security question, so we decide together with operations and IT what kind of access is acceptable. Password-based access control and logging are there in every case.

Can an existing HMI be taken over for extension?

If the source project and the version of the development tool are available, yes. If only the running panel is left, with no source, it usually has to be rebuilt. We can tell after a survey.

What does alarm handling mean in practice?

Every alarm has an identifier, readable wording, a timestamp and an acknowledgement state. The operator sees on the screen what happened and when. Maintenance can look it up afterwards — it does not have to be reconstructed from the operator memory.

Does it need a separate computer or server?

Not for an HMI panel at the machine. For SCADA, yes — we agree the machine specification at design time and fit it to the existing IT environment.

Get a quote

Let us look at
the task

Describe in a few sentences what you need solved. We reply within one working day and tell you what we need in order to quote.

Phone+36 30 463 32 43 E-mailinfo@skysol.hu
Registered officeSKY SOL Kft. · Római körút 23.
6723 Szeged, Hungary — we work nationwide
What helps us quoteA description of the process, an I/O list or an estimated signal count, any existing wiring diagrams, the platform and the deadline.

To speed up the technical discussion, tell us the PLC/HMI type, the estimated I/O count, a short description of the task, the location and the deadline you need. You can send an I/O list or technical documentation to info@skysol.hu.

Fields marked are required. We reply within one working day. You can also write to us directly: info@skysol.hu