When to Call a SCADA Integrator vs DIY Troubleshooting
Key Takeaway
Guidelines for operations and maintenance teams on when to troubleshoot SCADA and control system issues internally versus when to engage a professional SCADA integrator. Covers skill assessment, risk evaluation, common scenarios, and how to prepare for an integrator visit.
The DIY vs. Professional Decision
Operations and maintenance teams face a daily decision: should we troubleshoot this control system issue ourselves, or call in a professional SCADA integrator? Getting this decision right saves money and reduces downtime. Attempting complex programming changes without adequate expertise risks making the problem worse, while calling an integrator for a tripped breaker wastes money and delays resolution. This guide provides a framework for making that decision effectively.
The key factors are: the complexity of the problem, the risk of making it worse, the skill level of your available staff, the urgency of resolution, and the availability of documentation and backups.
When to Handle It Internally
Your maintenance team should be able to handle these common issues without external help:
Hardware Troubleshooting
- Power supply failures: Checking fuses, breakers, and measuring power supply output voltage is fundamental electrical work. Replace failed power supplies with identical units.
- I/O module replacement: Swapping a faulted I/O module with an identical spare is a straightforward hardware replacement. No programming changes should be needed if the replacement is the same model and firmware version.
- Communication cable repair: Replacing damaged Ethernet cables, serial cables, or re-terminating connectors is standard maintenance work.
- Instrument replacement: Replacing a failed transmitter, thermocouple, or RTD with an identical unit and verifying calibration is within most maintenance teams' capability.
Basic Operational Tasks
- Alarm acknowledgment and investigation: Responding to alarms, identifying the root cause, and taking corrective action is the core function of operations staff.
- Setpoint adjustments: Changing PID setpoints, alarm limits, and timer values through the HMI is a normal operational activity.
- HMI navigation and reporting: Using the SCADA system to view data, generate reports, and monitor trends should be a daily activity.
- Restarting faulted equipment: Resetting tripped VFDs, restarting communication servers, and clearing PLC faults that have known causes are routine recovery actions.
When to Call a SCADA Integrator
Engage a professional integrator for these situations:
PLC Programming Changes
- Logic modifications: Any change to PLC ladder logic, function blocks, or structured text requires programming expertise and introduces risk to the running process. Even a small change can have unintended consequences if the programmer does not understand the full program context.
- New I/O configuration: Adding new I/O modules, configuring new analog inputs, or adding new communication modules requires programming changes and proper testing.
- Firmware upgrades: PLC processor and module firmware upgrades can cause compatibility issues and require programming software updates. The integrator should verify program compatibility before upgrading.
System-Level Issues
- Communication protocol problems: Modbus, DNP3, EtherNet/IP, and OPC configuration issues require protocol-level expertise and diagnostic tools that most maintenance teams do not have.
- Network architecture changes: Adding switches, routers, VPNs, or changing IP addressing schemes affects the entire SCADA network and requires network engineering knowledge.
- Cybersecurity incidents: Any suspected cybersecurity event (unauthorized access, unusual network traffic, ransomware) requires immediate professional response. Do not attempt to investigate or remediate without cybersecurity expertise.
- Recurring faults with unknown cause: If a problem keeps coming back and your team cannot determine the root cause, continuing to apply temporary fixes wastes time and money. An integrator with deep platform knowledge can identify the underlying issue.
Safety and Compliance
- Safety instrumented system (SIS) changes: Any modification to a SIS must be performed by qualified personnel following the management of change (MOC) process. Incorrect SIS modifications can compromise safety and violate regulatory requirements.
- Regulatory reporting systems: Changes to systems that generate regulatory compliance data (emissions monitoring, flow measurement for reporting) require careful validation to maintain data integrity.
How to Prepare for an Integrator Visit
Maximize the value of integrator time by preparing before they arrive:
- Document the problem: Record exactly what is happening, when it started, what changed (if anything), and what you have already tried. Screenshots of error messages and alarm logs are invaluable.
- Gather documentation: Locate the PLC program backup, HMI project backup, network diagram, and any previous service reports. If you cannot find these, tell the integrator so they can create them during the visit.
- Ensure access: Make sure the integrator will have physical access to all equipment (panels, junction boxes, field devices) and logical access (passwords, VPN credentials, software licenses).
- Identify the right contact: Have the most knowledgeable operator or technician available during the integrator's visit to explain the process and answer questions about normal vs. abnormal operation.
- Define the scope: Be clear about what you want the integrator to accomplish. A well-defined scope leads to an accurate quote and efficient work.
Building Internal Capability
The long-term goal should be to develop your team's skills to handle more issues internally:
- Send key personnel to PLC programming training (manufacturer-offered courses are the most relevant)
- Request knowledge transfer during integrator visits — have your staff observe and ask questions
- Maintain current documentation, including a program backup after every change
- Start with simple monitoring and trending tasks before attempting control logic modifications
- Establish a relationship with an integrator like NFM Consulting who can provide ongoing support and training tailored to your specific systems
Frequently Asked Questions
SCADA integrator rates typically range from $125-$200 per hour for standard work, with higher rates for emergency after-hours calls. Many integrators also offer fixed-price project quotes for defined scopes of work. Travel time and expenses are usually additional for remote sites. While the hourly rate seems high compared to in-house labor, an experienced integrator resolves problems in a fraction of the time and avoids the costly mistakes that inexperienced personnel make.
Secure remote access can dramatically reduce response time and cost — the integrator can diagnose many problems remotely without a site visit. However, remote access must be implemented securely: use a VPN with multi-factor authentication, limit access to specific systems, log all remote sessions, and require your authorization before each remote connection. Never allow always-on remote access or shared credentials. Your integrator should be willing to comply with your cybersecurity requirements.
Look for experience with your specific PLC platform and industry, ask for references from similar facilities, verify they carry appropriate insurance and certifications (CSIA membership, manufacturer certifications like Rockwell Automation Recognized System Integrator), and evaluate their documentation practices. A good integrator provides detailed documentation of all work performed, updated program backups, and as-built drawings. Avoid integrators who are unwilling to share program source code or documentation with you.