Skip to content
+90 850 885 27 43 info@argeict.com

Services

OT infrastructure for manufacturing

ARGE ICT builds and operates the servers, network, backups, and remote access behind production line systems (MES, SCADA, historian), in the plant, on ARGE Cloud, or both. Our service is limited to the information technology (IT) side: servers, virtualization, databases, network, security, backups, access, licenses, and monitoring. Machines, PLC programming, and production process consulting are out of scope.

Operational technology (OT) is the general name for systems that directly control a physical process: the programmable logic controller (PLC) that controls a machine, the human-machine interface (HMI) screen an operator uses, the SCADA software that supervises many machines, and the manufacturing execution system (MES) that passes work orders to the line. Office computers and enterprise resource planning (ERP) software are the IT side. In IT the priority is keeping data confidential; in OT it is keeping the process running. If an ERP server is down for an hour, invoices are late; if a SCADA server stops, operators cannot see the line. The database that stores time-stamped machine data is called a historian. The infrastructure behind production line systems has to be built with that difference in mind.

This page explains how that infrastructure is built and who does what. For the general IT topics of manufacturers, such as ERP, KVKK (Türkiye's Personal Data Protection Law), and customer audits, see the manufacturing and industry page; we do not repeat them here.

The layers of production systems

The industry describes these systems with the layers of the ISA-95 standard. Knowing the layer settles who is responsible for what when something fails, or when you compare quotes.

ISA-95 layers and where ARGE ICT sits
LayerWhat it doesOur part
Machines, sensors, and PLCs (levels 0–1)Controls the machine in real timeNone. The PLC and machine program belong to the automation integrator; we only keep the backup.
HMI and SCADA (level 2)Operator screens, monitoring and control of the lineWe build and operate the SCADA server infrastructure (virtual server, network, backup); the automation integrator configures the software.
MES (level 3)Passes work orders to the line; keeps production, quality, and maintenance recordsWe build and operate the servers, database, backup, and access; functional setup belongs to the MES vendor.
ERP (level 4)Planning, inventory, cost, invoicingWe build and operate it on ARGE Cloud or in your own environment; details are on the industry page.

What runs in the plant and what runs in the cloud

The rule fits in one sentence: real-time control stays next to the physical process, and work that is not sensitive to latency can go to the cloud. The position paper that the International Society of Automation (ISA) published in December 2025 points the same way: it recommends keeping real-time control at or near the physical process. The first design condition is that the line keeps running when the connection drops.

Where each production system runs
ComponentIn the plantOn ARGE CloudReason
PLCs and safety controllersYesNoReal-time control
HMI and line SCADA serverYesOnly a read-only monitoring copyMust keep working if the line connection is cut
Edge server, OPC UA and MQTT gatewayYesNoBuffers data when the connection drops
Historian (primary)YesA copy is possibleReporting reads from the copy
MESDependsDependsDepends on the architecture the MES vendor supports and whether the line must work offline
ERP, reporting, OEE (overall equipment effectiveness) dashboards, analyticsPossible (in your server room)YesNot sensitive to latency; either works
BackupsA local copy for fast restoreAn isolated copyTwo copies in two places
Monitoring and security information and event management (SIEM)CollectorAnalysis and retentionLogs leave the plant; control does not

The MES row says "depends" because the answer is in the software architecture. Some MES products run fine in the cloud and others want a local server at the line. We do not promise this on our own; we read your vendor's documentation and, where needed, propose a design that can keep working offline at the line.

The plant network: cells, industrial switches, and rings

A plant network is usually divided into cells. Each cell, a line or a group of machines, runs in its own network segment, and the cells join at a distribution layer. The machine manufacturer usually decides the addressing inside a cell. The distribution and core layers, the VLAN (virtual network segment) design, and the firewall are the IT side, and that is our work.

Because of dust, vibration, and heat on the production floor, we use managed industrial switches that mount on a DIN rail. Connecting them in a ring is common: if a cable or switch fails, traffic continues the other way around the ring. When choosing the redundancy protocol (MRP, ERPS, or RSTP), we do not mix two protocols on the same ring. Recovery time depends on the protocol and the manufacturer; we design to the value in the manufacturer's documentation. The scope of the industrial switches is settled during discovery: we supply and configure some, and the ones that ship with a machine stay as the machine builder configured them.

Separating IT and OT: the industrial DMZ

A firewall between the office and plant networks is the first step, but it is not enough on its own. In the reference architecture known as the Purdue model, plant layers are numbered from the bottom up, with the office and ERP at the top. The buffer zone numbered 3.5, between IT and OT, is called the industrial DMZ. Traffic does not pass directly between the two networks; it stops in this zone and is inspected.

In practice the DMZ holds a readable copy of the historian (the IT side reads the copy and never queries OT directly), an intermediate server for data moving between the MES and ERP, and a jump server for remote access. The OT zone does not reach out on its own; only defined conduits are opened.

The idea of zones and conduits comes from the IEC 62443 series. A zone is a group of assets with the same security requirement, such as a line's SCADA and HMIs. A conduit is the permitted communication between two zones, which in practice shows up as a firewall rule, a DMZ, or a proxy. We turn which zone may talk to which, over which conduit, into a written table, so the reason for a rule is clear when it is added. This work follows the standard's zone-and-conduit approach; it is not a compliance assessment or a certificate (see the who-does-what table).

Remote maintenance access for machine builders

When a machine on the line fails, its builder often wants to connect remotely. Opening a separate virtual private network (VPN) endpoint for each supplier creates many separate entry points into the plant network, and the record of who connected and when ends up scattered. The OT connectivity principles that the UK's National Cyber Security Centre (NCSC) and the US agency CISA published together in January 2026 likewise advise gathering remote access in one secure point and logging every connection.

We build this with ARGE ZTNA. A supplier user signs in with two-factor authentication, connects only from a registered device, and reaches only the resource the administrator allows; the rest of the network stays closed to them. Every session, device, and access decision is logged, and the administrator receives a monthly report. Access credentials are short-lived and are revoked when the job ends or the supplier's employee leaves. You decide who gets access to which machine and for how long; we turn the decision into a rule.

Systems that cannot be patched, and passive monitoring

It is common to find a machine PC that has run in the plant for years on an old operating system. Installing a patch (a security update) can stop production, or the machine builder may not support the new version. So we apply compensating measures instead of the patch: putting the system in its own zone, narrowing the list of devices and users that can reach it, restricting USB and external connections, and watching its network traffic.

Monitoring in the OT zone is passive. The active network scanning that is routine in IT can lock up an old PLC or network card, so we do not run active scans in the OT zone. Passive monitoring takes a copy of the traffic from a mirror port on the switch and works out which device talks to which. We agree on the tool and the scope with you during discovery. If an active test is needed, we run it during a planned shutdown together with the automation integrator.

Backup: SCADA, MES, PLC programs, and network configuration

Backup for production systems is wider than for an office server. We cover four things together:

  • SCADA and MES virtual servers: backed up as system images, so after a failure we restore the image instead of rebuilding the server.
  • Databases and the historian: taken at a consistent point, with the restore tested.
  • The current copy of PLC and HMI programs: the automation integrator hands over the copy after every change and we store it under version control. Loading it back into the PLC is the automation integrator's job.
  • Switch, router, and firewall configurations: kept so that a replaced device does not have to be configured from scratch.

One copy of the backups stays in the plant for fast restore; the other goes to the isolated backup zone on ARGE Cloud. The isolated backup zone is a logical area kept separate from where the systems run. We test restores and report the result in writing; the method is described on the backup and disaster recovery page.

Production data: OPC UA, MQTT, the historian, and OEE

Machine data is collected with a few standard protocols. OPC UA carries structured data between a machine and higher-level systems and supports authentication and encryption. MQTT is a lightweight publish-subscribe protocol: devices send data to a broker and the subscribed systems pick it up there. Depending on the machine's age and make, you also see other protocols such as Modbus TCP, PROFINET, or EtherNet/IP. The edge server that collects the data runs in the plant and, when the connection drops, stores the data and forwards it later.

The collected data is written to the historian, a database designed for time-stamped records. OEE is the product of availability, performance, and quality, and the dashboards draw on those records. We build the path the data travels: the edge server, the network, the historian, the DMZ copy, and the server the dashboards run on. Which data is collected, the tag names, and how OEE is defined for each machine are decided by the MES or automation integrator.

Who does what

Production systems are a shared job among several parties, and if the boundary is not written down, the argument over whose problem it is starts at the moment of failure. The table below shows the default split; we write it into the contract at the start of the project.

Division of work on production systems
TaskARGE ICTAutomation integrator, machine builder, or MES vendor
Plant servers, virtualization, the IT side of the network, firewall, DMZDesigns, builds, and operatesInstalls and configures the application on those servers
PLC, HMI, and SCADA programming; machine automationNoYes
MES functional setup, ERP-to-MES mapping logicNoYes
Machine network inside a cell and machine addressingAssigns the VLAN and address range the cell connects toUsually
Remote maintenance accessBuilds and logs the accessUses the access
Backup and restore testingStores and testsHands over the current copy of the PLC program
MonitoringServers, network, and security; passive only in OTThe machine's own diagnostics
Hardware and operating system licensesSuppliesAutomation software licenses come through their channel
IEC 62443 assessment and certificationBuilds the technical measures, does not issue certificatesA consultant runs the assessment; an accredited body issues the certificate

Several plants and the link to head office

A company with more than one plant gives each plant its own OT zone and its own DMZ. The link between the plants, head office, and ARGE Cloud can run over the carrier's MPLS line, a private line that does not touch the internet. Without MPLS, SD-WAN-capable routers and firewalls build IPsec tunnels over the existing internet lines, and a mobile backup line takes over if a line drops. Your carrier provides the lines. We compare the options in how head office, branches, and the cloud connect.

The rule is that the OT networks of the plants are not connected directly to each other. So that a problem in one plant does not spread to another, each plant's data goes through its DMZ to the MES or ERP at head office. If traffic between plants is needed, it is defined as a separate conduit and opened for that purpose only.

Regulation and expectations

Law No. 7545 on Cybersecurity provides additional obligations for critical infrastructure. The boards and institutions that are authorized under the Law decide which sectors and facilities count as critical infrastructure; not every plant is critical infrastructure. Check the Cybersecurity Directorate's rules and ask your legal counsel whether your plant is in scope. ARGE ICT holds no authorization or certificate under this law; we only build the technical measures described on this page.

On personal data, KVKK, Türkiye's Personal Data Protection Law (Law No. 6698), touches a plant in two ways. The first is workplace cameras: under the Personal Data Protection Authority's public announcement on workplace security cameras, the purpose must be defined and proportionate, there should be no cameras in rest and changing areas, access to recordings should be limited by authorization, and retention should be short. We set up encrypted storage of recordings, access rights, and deletion of expired footage; the legal assessment belongs to the data controller. The second is the operator ID, shift, and turnstile data in the MES and terminals, which is also personal data; we limit access by role.

Hardware, licenses, and hosting on ARGE Cloud

We can supply plant servers, storage, firewalls, industrial switches, and operating system and virtualization licenses under the arrangement on the single-source procurement page. Automation software licenses come through the automation integrator's channel. We can host the MES, a historian copy, ERP, and reporting servers on ARGE Cloud, which runs in a data center in Istanbul, in a virtual private cloud (VPC) dedicated to you; we confirm the architecture your vendor supports from its documentation before installation. The part that stays in the plant we build and operate in your own environment. Both can be used together: control and SCADA in the plant; the MES (if its vendor supports it), the historian copy, backups, and reporting in the cloud.

Related services

For ERP and customer audits, see the manufacturing and industry page, or SAP infrastructure if your ERP is SAP. We describe log collection on the SIEM page, network design on the corporate network page, and backups on the backup and disaster recovery page.

Frequently asked questions

If we move the MES to the cloud, does production stop when the internet drops? Control and SCADA at the line stay in the plant, so the machines keep running. How long the MES can work without a connection depends on the software architecture, and we settle that with the MES vendor. We set up an MPLS or SD-WAN link between the plant and the cloud, with a mobile backup line.

Do you back up our PLC programs? We receive the current copy of the program from the automation integrator and store it under version control in the isolated backup zone. Loading it back into the PLC is the automation integrator's job; we do not do that.

Our SCADA server runs an old operating system. Can you virtualize it? It depends on whether the SCADA vendor supports the virtualization platform and version. If it does, we move it to a virtual server and keep its backup as an image. If not, we keep the physical server in its own network zone and narrow access to it.

Do you run security scans on the plant network? We do not run active scans in the OT zone, because old controllers can lock up under scan traffic. We work with passive monitoring and an asset inventory. If an active test is needed, we run it during a planned shutdown together with the automation integrator.

Can we get an IEC 62443 certificate? An accredited body issues the certificate; we do not. We build the technical measures of the zone and conduit structure and prepare the rule table and logs as evidence.

We have several plants. Should all their OT networks be connected? Usually not. Each plant's OT zone stays separate, and data goes through the DMZ to the MES or ERP at head office. If traffic between plants is needed, it is defined as a separate conduit.

Talk to us about plant infrastructure

Tell us which MES and SCADA you use and how many plants you have; we reply within 1 business day.

Talk to a specialist