ITSM for a manufacturing plant -
factory help desk 2026

IT vs OT in the factory - why it matters

In a typical manufacturing plant the IT infrastructure is split into two, often completely separated worlds. IT (Information Technology) is the familiar set of computers, servers, networks, Active Directory, and business applications. OT (Operational Technology) is the infrastructure that controls the production process: PLC controllers (Programmable Logic Controllers), HMI panels (Human-Machine Interface), SCADA systems, CNC machines, industrial robots, sensors, and industrial networks such as Profibus or Modbus.

For decades the two worlds were separated: OT operated on an isolated network, IT in the office. Digitization and Industry 4.0 have changed that architecture. Today machines are connected to the plant network, the ERP reads line data in real time, and MES systems monitor every operation. IT/OT convergence opens new opportunities but raises a concrete question: who handles a PLC controller failure - the IT department or maintenance?

The lack of a clear answer to that question is the most common reason for organizational chaos in factories. The IT team does not know the specifics of the machines, maintenance does not use ticketing systems. A line outage is costly, and no one is formally responsible for response time. A full comparison of IT and OT environment requirements is available in the article help desk for a manufacturing company.

Key ITSM challenges in a manufacturing environment

Managing OT equipment as IT assets

In the CMDB of a typical office help desk you find laptops, monitors, servers. In a manufacturing plant the asset list is far broader: industrial panel PCs (IPC), Zebra label printers connected to the packaging line, barcode scanners in the warehouse, terminals in the production halls, plus the PLC controllers and HMI panels mentioned earlier. Each of these has different technical parameters, different criticality for the production process, and a different spare-parts lead time.

The problem appears when a label printer on the packaging line fails: who opens a ticket? In an office system the user reports the problem themselves. On the shop floor machine operators often have no access to a computer - they work at the line and wear gloves. The reporting process has to be adapted: phone, mobile app, QR code on the machine pointing to a ticket form.

Priorities - a machine failure is always P0

In the office a P0 (Critical) priority appears once a quarter. In a factory running three shifts it can occur several times a week. The ITSM system must distinguish priorities not only based on the problem description but based on context: which machine, which line, which shift, how many orders are waiting to be fulfilled. This requires integration with the production plan - if line A is running an urgent order for a key client, a label printer failure on that line is P0, not P2.

Three-shift operation - who handles tickets at 3 a.m.?

The office works 8 to 17. Production works 24/7. That is a fundamental difference that requires a well-thought-out on-call structure and escalation automation. The help desk needs to know which technician is on call on the night shift, who to escalate a critical incident to at 3:00, and how to notify - SMS, push, voice call? ManageEngine SDP allows defining different on-call schedules and escalation rules per shift, but it requires precise configuration during the implementation.

Integration with MES and CMMS

In mature manufacturing environments there is an MES managing production and a CMMS (Computerized Maintenance Management System) managing inspection and machine repair schedules. Deploying ITSM without integrating it with those systems creates data silos: the IT technician resolves an incident in the help desk, but maintenance cannot see the failure history of that machine in CMMS. A good ITSM implementation is one with APIs between SDP and MES/CMMS.

How to configure ManageEngine SDP for manufacturing

Ticket categories - three worlds, one queue

The foundation of a correct configuration is a ticket taxonomy that reflects the plant's specifics. Recommended structure for a manufacturing environment:

• OT production equipment - machine failure, PLC controller problem, HMI panel, label printer, scanner, production terminal
• Office IT - desktop, laptop, monitor, phone, login issue, office applications
• Infrastructure and network - servers, LAN/WiFi network, VPN, industrial network, SCADA/MES
• Business applications - ERP, MES, WMS, APS - system errors, slow performance, data issues
• Security - IT security incident, OT cybersecurity, access

SLA per category - different response times for different assets

One SLA for all tickets is mistake number one in manufacturing implementations. Recommended SLA matrix:

Automating shift-based technician assignment

ManageEngine SDP lets you define ticket assignment rules (Dispatch Rules) based on category, time of day, and location. For a three-shift environment the configuration should include: shift schedule imported from ERP or HR, separate on-call rotations for OT and IT technicians, fallback to an emergency number when no technician is on the active shift. The escalation rule should work regardless of the time of day - a P0 ticket logged at 2:30 a.m. must trigger an SMS to the on-call technician within 5 minutes.

Integration with MES and ERP - tickets from machine failures automatically routed to the help desk

A mature ITSM implementation in a manufacturing plant assumes that not only people create tickets. Machines and systems do too. Modern MES systems can detect anomalies (exceeded temperature limits, controller errors, line stoppage) and call out events in external systems via API.

A practical integration scenario looks like this: a temperature sensor on an injection molding machine detects an alarm threshold being crossed. The MES logs the event and, via REST API, creates a ticket in ManageEngine SDP with the category "Production equipment - sensor alarm", priority P1, assignment to the maintenance technician on the current shift, and a link to the machine parameters chart from the last 30 minutes. The technician receives a push notification in the SDP mobile app. They react immediately instead of waiting for someone to notice the problem and call.

ManageEngine SDP offers a REST API that allows tickets to be created from external systems. MES integration usually requires a simple script on the MES side (Python, Node.js) or a dedicated connector if the MES offers ready-made webhooks. ERP integration (SAP, Comarch Optima, IFS, Oracle) is analogous - a failure of a resource used in an active production order automatically raises the ticket priority.

Managing industrial assets in the CMDB

A Configuration Management Database (CMDB) in a manufacturing environment is much more than a list of servers and laptops. A properly built CMDB for a manufacturing plant contains every element of IT and OT infrastructure that can become an incident source or affects production continuity.

How to inventory industrial equipment

Inventorying OT equipment is different from IT. You cannot install a discovery agent on a PLC controller. Alternative methods are used: scanning the industrial network with dedicated tools (e.g. ManageEngine OpManager with the OT plugin), manual inventory with QR/barcode labels on every device, import from technical documentation and electrical schematics. Each asset in the CMDB should contain: physical location (hall, line, station), serial number, date of last inspection, contact details for external service or warranty, links to other assets (e.g. label printer connected to line 3).

Barcode scanner and mobile inventory

ManageEngine SDP in the Enterprise edition enables asset inventory through a mobile app with a scanner. The technician walks around the hall with a tablet or phone, scans the QR code stuck to a machine, updates the CMDB data on the spot. The QR code is generated by SDP - it just needs to be printed and attached when commissioning the device. On a repeat failure the technician scans the code and instantly sees the repair history, the date of the last inspection, and open/closed incidents linked to that asset.

Repair history as a machine knowledge base

One of the biggest benefits of the CMDB in manufacturing is repair history. After 12 months of use, the ITSM system can answer: which machine generates the most incidents, what is the average MTTR (Mean Time To Repair) for each equipment category, which failures are cyclical and may indicate the need for a proactive inspection. That is a real basis for conversations with the board about replacing aging equipment or changing the service provider.

Example scenario - a metal industry manufacturing plant

How to choose a help desk system for a factory - 5 manufacturing-specific criteria

1. Support for three-shift operation and on-call schedules

Check whether the system allows configuring technician work schedules with daily shifts, and whether the SLA clock is aware of working hours (so-called Business Hours SLA). For manufacturing, a 24/7 SLA for critical categories is important, not only during office hours. ManageEngine SDP allows defining different SLA calendars per ticket category.

2. Ability to integrate with MES and CMMS via API

Every serious ITSM system has a REST API. But the question is: is the API documentation complete, does the API support creating tickets from external systems without a user account (service account / API key), and is support available when configuring the integration? ManageEngine SDP has a well-documented API - Rotech Group delivers ready-made integration templates with popular MES systems.

3. Mobile app for technicians on the shop floor

Technicians on the shop floor do not sit at a computer. They need a mobile app that allows them to accept a ticket, update its status and close it from a smartphone, preferably without having to type long texts. Check: does the app work offline (with weak WiFi in the hall)? Does it support QR/barcode scanning? ManageEngine has a native iOS/Android app for technicians.

4. CMDB with OT asset support

Basic CMDB systems are designed for IT equipment. For OT you need the ability to define your own asset types with non-standard fields (e.g. supply voltage, communication protocol, firmware version). ManageEngine Asset Management in the Enterprise edition allows creating custom asset categories with arbitrary fields - we have verified this in several manufacturing implementations.

5. KPI reporting for production management

The production manager needs different reports than the IT manager. They want to see: downtime per machine in a given month, cost of incidents linked to lost production, MTTR trend for OT equipment. Check whether the system allows building custom reports and whether they can be automatically emailed to management on the first day of the month.

Comparison of systems for the manufacturing environment

Manufacturing ITSM implementation with Rotech Group

Rotech Group specializes in ITSM implementations in environments where IT meets manufacturing. We have experience in metal, food, automotive and electronics plants. We understand the specifics of OT, three-shift operation and CMMS processes - because we implement end-to-end: ITSM, ERP and integrations between systems.

Our ManageEngine SDP implementations for manufacturing always include:

• An IT/OT process mapping workshop - identification of critical assets, priority matrix
• SLA configuration per category, taking into account three-shift operation
• Building a CMDB for OT equipment with QR labels and a mobile app
• Integration with MES, ERP or CMMS (or all three)
• Training of IT and maintenance technicians on system and mobile app usage
• KPI reporting for production management

Typical implementation time: 4-8 weeks, depending on the number of integrations and the size of the CMDB. A pilot deployment (one line, basic configuration) can be delivered in a shorter time. You can read more about how an implementation runs in the article on improving IT response time.