Help desk for a manufacturing
company: how it works and what it delivers

A help desk for a manufacturing company is not the same as a help desk for an office. In a plant, an hour of line downtime costs tens of thousands of zloty, an OT technician is not a computer user, and a SCADA system does not tolerate reconfiguration without a change management protocol. This article shows how a help desk differs in a manufacturing environment, which features are essential and how to run the implementation smoothly.

Why manufacturing needs a separate IT help desk approach

In an office, a computer failure frustrates an employee and blocks email access for a few hours. In a manufacturing plant the same failure - if it affects a workstation controlling a line - halts production. The stakes are incomparably higher, and response-time requirements many times stricter.

Many manufacturing companies operate for years without a formal IT ticketing system. Technicians respond by phone, incidents are not documented, there is no SLA, and knowledge of failure history disappears with staff turnover. Once a plant employs 200 people, has 3-6 IT technicians and runs dozens of network-connected machines, that model stops working.

The key difference from ITSM in an office is priority: in the office it is the user SLA that matters, in the plant it is the machine or production line SLA. A ticket "router down on the shop floor" should have a higher priority than "printer in reception not working". The system must enforce that automatically, without the technician deciding.

Manufacturing specifics: OT, IT, SCADA and ERP

A manufacturing plant is not just computers and servers. It is the convergence of two worlds that historically ran separately: IT (Information Technology) - servers, office computers, LAN and ERP - and OT (Operational Technology) - PLC controllers, HMI panels, SCADA systems and automated lines.

IT/OT networks and what they mean for the help desk

More and more plants integrate IT and OT networks. A single incident - for example a bad PLC firmware update - can affect ERP and the production line at once. The help desk must handle tickets from both domains, often routing them to different teams with different competencies and SLAs.

Typical OT assets in the help desk of a 100-300 employee plant:

• PLC controllers (Siemens, Allen-Bradley, Beckhoff): critical for production continuity
• HMI panels and operator stations: human-machine interface, often Windows Embedded
• SCADA servers: real-time supervision of the production process
• MES (Manufacturing Execution System): production planning, order recording
• Industrial switches and production VLANs: isolated from the office network

ERP as the central data system

A manufacturing plant typically runs an ERP system (SAP, Comarch ERP XL, Epicor, enova365) integrated with order, warehouse and production planning processes. An ERP server failure or database connection loss is a top-priority incident: it stops order entry, production reporting and inventory management.

The help desk must be aware of this hierarchy and automatically categorize ERP-related tickets as P1 or P2 with a dedicated SLA and escalation to the system administrator.

Key help desk features for a manufacturing plant

1. Ticket categorization tailored to the industrial environment

Standard help desk categories (hardware, software, network) are not enough in a plant. You need a richer taxonomy that reflects manufacturing specifics:

• Production line: machine failure, CNC program error, PLC communication loss
• SCADA / MES: system unavailable, sync errors, historical data issues
• ERP / business systems: server failure, performance problems, module errors
• IT infrastructure: servers, backup, network, Active Directory
• Workstations and terminals: office computers, production terminals, label printers

Good categorization is a precondition for valid reports for management and compliance with audit requirements (ISO 27001, NIS2 for critical infrastructure).

2. SLAs dedicated to critical assets

Key distinction: in the office an SLA is tied to ticket priority. In a plant the SLA should be tied to the asset (CI, Configuration Item). A ticket about a SCADA server gets a P1 SLA automatically, regardless of what the requester sets.

3. CMDB integration: IT and OT assets in one place

A help desk without a CMDB works blind. The technician picks up a ticket but does not know whether the device is under warranty, who services it, what its failure history is, whether it was upgraded. The CMDB integrates these data and surfaces them in the context of every ticket.

In a manufacturing environment the CMDB should cover both IT assets (servers, computers, switches) and OT assets (controllers, HMI panels, measurement devices). Relationships between them ("SCADA server runs line 3 and line 4") let you assess incident scope without calling the production manager.

4. SLA clocks with the production calendar

A plant works two shifts (6:00-22:00) or three shifts (24/7). SLA clocks must factor in: shift hours, planned maintenance schedule, plant holidays and technological downtime. Misconfigured SLA clocks generate false breaches and devalue management reports.

5. Self-service portal designed for production workers

Shop floor workers are not computer users. The self-service portal must be ridiculously simple: minimum fields, clear categories, the ability to submit from a phone or tablet at the machine. Complex forms mean workers go back to calling the IT technician.

ManageEngine ServiceDesk Plus: sample plant implementation scenario

Help desk integration with ERP and MES

The biggest value of a help desk in a manufacturing environment is not the ticketing system itself but its connection to the rest of the plant's systems. A standalone help desk is a better inbox. A help desk integrated with ERP, MES and CMDB is an operational continuity management platform.

ERP integration (SAP, Comarch, Epicor)

The simplest and most important integration: a webhook or REST API that informs the help desk about ERP server status. When the server stops responding, a P2 incident is created automatically and assigned to the ERP administrator, without human intervention. In a more advanced scenario the help desk issues a service order to the ERP (CMMS) when a machine failure is recorded. A detailed view of integration scenarios is in our article on ERP cloud vs on-premise.

MES and SCADA integration

MES systems (Epicor MES, Wonderware, custom solutions) often have alarm modules that can trigger help desk incidents via webhook or email. Result: technicians see the MES alarm directly in the ticket queue, with machine context, CMDB failure history and an assigned SLA. They do not have to take a call from the shop floor and look up the information themselves.

IT infrastructure monitoring

ManageEngine OpManager or external systems (PRTG, Zabbix) can automatically create incidents in ServiceDesk Plus when a monitored device crosses an alert threshold. The technician does not have to check the monitoring dashboard. The incident lands in their queue with full context: occurrence time, threshold values, network node.

How to start with integrations: priorities

Not every integration needs to be deployed at once. Recommended order for a plant starting out with a help desk:

1. Active Directory: user sync, SSO (priority 1, typically 1-2 days of work)
2. CMDB with asset import: IT list via Discovery Agent, OT via CSV import (priority 1)
3. IT monitoring → auto incidents: eliminates manual ticket creation (priority 2)
4. ERP webhook: automatic incidents on ERP server unavailability (priority 2)
5. MES / SCADA alarms: advanced, after the basic processes stabilize (priority 3)

A detailed cost and return-on-investment breakdown is in our ITSM ROI calculator.

How to start a plant help desk deployment: 5 steps

A help desk deployment in a manufacturing environment differs from an office one mainly in analysis and configuration. Below is a simplified plan we use at Rotech Group. Full methodology is on the page what an implementation looks like.

Step 1: IT/OT environment map (1-2 weeks)

Before you configure anything you need a full asset inventory: servers, workstations, controllers, switches, application systems. Without that map you cannot define SLA priorities or build a meaningful CMDB. For a 100-300 employee plant it is usually 200-600 CMDB entries.

At this stage you also identify critical assets (those whose failure halts production). They get the P1 and P2 SLAs.

Step 2: SLA definition and priority matrix (3-5 days)

Together with the production manager and IT manager you define: which assets are critical, what response and resolution times are acceptable, what hours IT support operates (one shift, two, 24/7). The output is a priority matrix ready to be loaded into the help desk.

Step 3: Installation and basic configuration (1-2 weeks)

Server install (on-premise or cloud), Active Directory integration, department/group configuration and permissions. UI localization to Polish. At this point the system can accept tickets, though without full ITSM processes.

Step 4: Process and CMDB configuration (2-3 weeks)

Ticket categorization, SLA configuration with production clocks, CMDB import, automatic assignment rules. This is the most time-consuming stage. Its quality determines the system's everyday value.

Step 5: Training and go-live (1-2 weeks)

IT technician training (8h), manager training (4h) and a short shop-floor session on the self-service portal (30-60 minutes, ideally on a tablet at the machine). Production start with active consultant support for the first 2-4 weeks.

Summary: a help desk in manufacturing is not a cost - it is insurance

The absence of a formal IT help desk in a plant does not eliminate the costs. It pushes them into the dark: unrecorded downtime, repeated repairs of the same failures, no data for negotiations with external service, and no way to demonstrate the IT department's value to management.

A help desk integrated with CMDB, ERP and monitoring shortens response time, makes it easier to eliminate recurring incidents and gives management visibility into the real state of infrastructure. The pace of return on investment in ManageEngine ServiceDesk Plus depends mainly on plant scale and downtime cost - the more expensive line outages are, the faster the system pays back.

Want to know how much you can save in your plant? Try our ITSM ROI calculator or book a free consultation.