KyoungilSystem
Services · SCADA / HMI

Screens built the way operators actually work.

The layer that watches and drives the equipment. Screen design, tag structure, alarm strategy and commissioning on site. We use Autobase alongside software we write ourselves, so whatever the package cannot do, we build.

When you need this

When integrators are called in.

  • 01

    The screens mirror the drawing

    A screen laid out like the equipment diagram is correct and unusable. We lay it out in the order the line is actually operated.

  • 02

    Hundreds of alarms a day

    Once alarms nobody can act on are mixed in, all of them get ignored. We group the duplicates and cascades and re-rank what is left.

  • 03

    The SCADA platform is discontinued

    A line can keep running on an unsupported platform right up until it breaks and nobody can fix it. We move it, reorganizing tags and alarms on the way.

  • 04

    Nothing is being recorded

    Trends and history can only be designed once retention is decided. We size the storage from how many years you need and how fast you need to query them.

Scope

What you get.

Scope is fixed after the site survey. These are the items a SCADA/HMI project normally includes.

Screens
Supervisory and control screens, operator permissions
Tags · comms
PLC tag map, driver setup, defined behaviour on comms loss
Alarms
Rationalized alarm list, priorities, occurrence and recovery history
Trends
Storage sized to the retention you need, with query screens
Migration
Screens and tags moved off a discontinued platform
Commissioning
Parallel running on site and handover to your operators
Common questions

What we are asked most, before a quote.

What is the difference between SCADA and HMI?

An HMI is the panel in front of a machine. SCADA is the layer above it that supervises several machines at once and keeps the history. On most floors you need both, so we design the screens and the tag structure together rather than as two projects.

Do we have to replace our PLCs?

No. Whatever controller is already on the floor stays. Yokogawa, Mitsubishi and LS Electric dominate our recent projects, and where Autobase SCADA does not ship a driver we write one.

Can you migrate screens off a discontinued platform?

Migration is routine work for us, but we do not copy the old screens across. Tags and alarms have to be reorganized or the new system inherits the old problems, so the site survey settles what to keep and what to drop before anything moves.

Our alarms are ignored because there are too many.

The most common request we get. Alarm rationalization is not about reducing the count — it is about leaving only alarms someone can act on. Grouping duplicates and chattering alarms and re-ranking priorities changes how a line is run without changing a single screen.

Does the line have to stop?

Development and verification run against Virtual-M3 and simulators, with the line still producing. The cutover itself may need a short stop; when and how long is agreed in the commissioning plan, not discovered on the day.

Next

Take one layer, or take all three.

Tell us your equipment and protocol.

A first reply within one working day; the scope itself takes a few conversations.

Request a quotation
04 — Contact

Start with what you have. We’ll work out the rest.

Equipment list, protocol, and what the data has to reach. That’s enough for a first answer — usually within a working day.

Telephone
+82 31 267 4759
Office
47-13 Yunggeon-ro, Hwaseong-si,
Gyeonggi-do 18343, South Korea
Hours
Mon–Fri 08:30–17:30 KST