IT/OT integration consulting
In a new machine, MES or energy monitoring project, we define who owns the network, the data and the access rules. We prepare a shared architecture and change process together with the IT, automation, maintenance and production teams.
Reference architectureResponsibility matrixChange managementRoadmap
What problem does this service solve?
No clear owner for decisions
If it is not written down who approves a firewall rule, a firmware update or a new connection, decisions are delayed or carried out without records.
Devices and systems without an owner
Line switch, engineering workstation, historian server, edge device. When they fail, it is unclear who will intervene.
Disconnected projects
MES, energy monitoring, camera and quality projects run separately; each brings its own connection, server and security exception. The exceptions pile up.
Changes not being recorded
Firmware updates or firewall rule changes are made without looking at the production impact. There is no record.
What we cover, and within what limits
IT/OT integration is the work of combining the data and operation of production systems (OT) with enterprise information systems (IT) in a secure, sustainable way with clear responsibilities. Its technical side is network layers, the OT DMZ, the data integration layer and identity management. Its organisational side is ownership, change management, maintenance windows and incident response. We use the Purdue model as a reference for discussing layers, and ISA-95 for describing the tasks and information exchange between production and enterprise systems; neither is a mandatory physical topology on site. The target architecture is adapted to the plant’s existing investments, team capacity and risk appetite. This consulting is not a software sale. It is a decision framework for carrying out projects in the right order. Define update, capacity and operating responsibility for historian or MES servers as part of server and cloud management.
Technical scope
Current state assessment
Interviews and an on-site review covering the network, systems, data flows, teams and processes.
Target reference architecture
Layers, zones, OT DMZ, data integration layer and identity/access model; a one-page diagram adapted to the plant, with an explanation.
Responsibility matrix
Per asset and process: who is responsible, who approves, who is informed. For example, it is agreed who responds first when a device fails, who approves changes and who keeps the records.
Change and incident management
Request, risk assessment, maintenance window and rollback rules for OT changes; who calls whom during an incident.
Standards
Naming, IP plan, and network and security requirements for new machine purchases (an annex to purchase specifications).
Roadmap
Quick wins, medium-term projects and steps requiring investment; dependencies and sequencing.
Example responsibility table for project start
| Asset / process | Owner | Approves / consulted |
|---|---|---|
| Cell switch configuration | Automation / OT network lead | IT network team (standards) |
| OT DMZ firewall rules | IT security | Automation lead (production impact) |
| Engineering workstation patching | Automation | IT (patch source), production (maintenance window) |
| Supplier remote access | IT security (infrastructure) | Automation (approval and supervision) |
| Historian / data layer | Designated data owner | IT (server), automation (sources) |
The table is a template used at project start; it is filled in together according to each organisation’s structure.
Prerequisites: what we need to get started
We list missing information and access together in the first meeting and complete them during the survey.
- Participation of IT and automation/maintenance managers in workshops
- Existing network diagrams, system lists and policies (may be incomplete)
- A list of planned or ongoing digitalisation projects
- Access and an escort for the site visit
- A decision-making management sponsor
Deliverables
Current state assessment report
Target IT/OT reference architecture diagram
Responsibility matrix per asset and process
OT change and incident management procedures
Technical specification annex for new machine/equipment purchases
Prioritised roadmap and management presentation
Representative scenario: three digitalisation projects starting in the same year
MES, energy monitoring and a new quality system project all start in the same year; each supplier wants its own server and network access. First, a shared reference architecture and data integration layer are defined. Projects proceed on condition that they comply with this architecture. The responsibility matrix and change process make clear who signs off at go-live.
This is a representative consulting flow; it is not a completed customer reference.
Service summary
OT Cyber Security and Segmentation
We inventory the cells, engineering workstations and external maintenance connections in the production network.
OT/ICS cybersecurity assessment ↗
Scope limit
This consulting is not management system certification or a compliance audit. For compliance work such as ISO 27001 or TISAX, the services of uyum.eretek.com, and for OT security assessments, the services of siberguvenlik.eretek.com can be considered separately.
How do we proceed?
No step that affects production is carried out until the maintenance window, configuration backup and rollback plan are written down.
Interviews
Workshop with IT, automation, maintenance and production stakeholders.
Site
Critical lines and system rooms are reviewed on site.
Architecture
The target reference architecture and standards are written down.
Organisation
The responsibility matrix and change process are put in place.
Roadmap
Prioritised project list and management presentation.
Questions about IT/OT Integration Consulting
How long does this work take?
It depends on the size of the plant and the number of stakeholders. The scope is clarified in the first meeting and written into the proposal with its phases. We do not give fixed durations or package prices.
Do we have to apply the Purdue model to the letter?
No. The Purdue model is a reference used for discussing layers; ISA-95 describes the tasks and information exchange between production and enterprise systems. The target architecture is simplified or adapted to the plant’s needs.
Do you also implement after consulting?
Yes; if you wish, we take on the networking, segmentation and data integration projects in the roadmap. We prepare the outputs so that another implementer can also use them.
Our automation team is small; won't this structure overload us?
The matrix and processes are kept simple according to team size; for a non-critical change, a one-line record is usually enough.
Work that can be planned together
OT Cyber Security and Segmentation
We inventory the cells, engineering workstations and external maintenance connections in the production network.
SCADA, MES and ERP Connectivity
We identify which system production orders come from and where production quantity and scrap data are generated.
Factory OT Infrastructure Discovery
Before any investment, we record on site which PLCs, switches, protocols and data flows are in use.
Knowledge Center
Technical guides for this service
Let's plan a technical survey for IT/OT integration consulting
Briefly describe your plant, the structure of your IT and automation teams and the projects ahead of you; we will respond with a written proposal covering scope, assumptions and deliverables.
We deliver OT/IT integration projects at production sites across Türkiye; network and device work is done at the plant, while monitoring and approved changes run over secure remote access. Our service areas.