TAMFIS NIG LTDRC 8067447CAC ACTIVEFinima, Bonny Island, Rivers State

IIoT Retrofit on Legacy SCADA — A Practical Approach

An Industrial Internet of Things retrofit can make useful operating information available from an older SCADA environment. It can also introduce new connections, support dependencies and failure modes. The best starting point is a narrow business question: what decision will improve when a particular measurement becomes available?

For example, a maintenance team may want a reliable record of pump run hours or a trend of an existing condition measurement. That is more actionable than a request to connect every available tag to a cloud dashboard.

Write the use case and acceptance test together

Name the data consumer, the decision, the required update rate and the consequence of stale or missing data. Decide whether the information is advisory or part of an operational function. A monitoring project should not quietly become a remote-control project during implementation.

Define a simple acceptance statement. For a hypothetical run-hour application, it could require an agreed comparison against the existing source record, visible indication of missing data and a documented method for reconciling gaps. Set the actual tolerances and observation period with the owner rather than copying a generic target.

Inventory before connecting

Record the controllers, supervisory software, communications links, gateways, time sources and engineering workstations involved. Capture versions and support arrangements. Identify existing backups and confirm who has permission to change each component.

NIST’s Guide to Operational Technology Security treats safety, reliability and performance as important constraints for OT security. Its risk-based approach is relevant to retrofits: the protections appropriate to an office reporting system cannot simply be copied into a process environment without assessment.

Choose the least disruptive approved interface

Evaluate interfaces already supported by the existing installation before proposing changes to controller logic. A documented data interface may offer a more controlled path than adding untested requests directly to a legacy device. Confirm loading limits and vendor support for the proposed arrangement.

“Read only” is a requirement to verify, not a sufficient security description. The design review should explain what access is technically possible, where it is restricted and what happens if the gateway fails or behaves unexpectedly. Obtain approval from the facility’s control and cybersecurity owners.

Design for poor data as well as good data

Condition Question for the design review
Communications interruption How will users know the displayed value is stale?
Clock difference Which timestamp represents the event, and how is that understood?
Changed scaling or units Who approves and verifies the data mapping?
Buffered records after reconnection Can duplicated or out-of-order records distort the report?
Source configuration change How will downstream consumers learn that the meaning of a tag changed?

A dashboard should show uncertainty about the data instead of presenting a plausible but unsupported number. Store enough context to investigate a discrepancy later, including source identity and quality status where available.

Keep access and ownership explicit

Document where information is stored, who administers the gateway and who can grant remote access. Include account removal when suppliers or employees leave. Record licensing, subscription and connectivity dependencies so that the system remains understandable after the pilot team moves on.

Agree how credentials, configuration backups and project files will be handed over. A working demonstration is not a complete deliverable if only one supplier can restore it or explain how its connections were configured.

Pilot, review and expand deliberately

Start with a small approved tag set and compare the new data with the existing source. Observe the installation under representative operating conditions, including expected communication interruptions. Test recovery using an approved plan, and keep the original process functions outside the experimental scope.

Expand only when the pilot produces a useful decision and its operational burden is understood. If the dashboard collects data but nobody acts on it, refine the use case before buying more sensors.

See our PLC and DCS selection guide and automation capabilities. Contact Tamfitronics with your current architecture and monitoring objective to discuss a focused assessment.

Prepared with AI assistance.

Tags

Keep reading

More from News

News

How to Verify an E&I Contractor in Nigeria

Verify an E&I contractor through legal identity, relevant personnel, supported technical claims, practical work controls and independently checkable evidence.

TAMFIS NIG LTD

Engineering, consulting and software from Bonny Island

Electrical and instrumentation engineering, bid preparation and consulting, IT and software.

Get in touch