CONNECTED TECHNOLOGY. CLEARLY EXPLAINED.
Industrial gateways
Choose industrial gateways through field interfaces, data meaning, local processing, interruption handling, access boundaries and the supported service lifecycle.
An industrial gateway connects a defined field system with another application or network. Its job may include acquiring values, translating a protocol, processing records or buffering data. Specify those responsibilities and the operating boundary before treating the word gateway as a complete integration solution.
Define the interfaces and the operating boundary
Map both sides of the connection
List the actual field equipment, physical interfaces, protocol roles and destination. Distinguish a serial device server, protocol converter and programmable edge computer. Confirm exact model and software support; having Ethernet or a protocol name on both sides does not establish that their data can be interpreted correctly.
Describe the information contract
Record tag identity, units, scaling, timestamps, quality indicators and expected update behaviour. Agree how missing values, restarts and duplicate records appear. Keep data acquisition separate from any permitted write or control action, with its own engineering responsibility and authorisation.
Assign support and change control
Name the owner of the hardware, operating system, application, credentials and destination service. Review installation conditions, updates and recovery with the authorised OT team. A new connection must fit the site’s operating and security requirements rather than relying on a generic cloud-ready label.
Follow the data and ownership through the gateway
Hardware and regional fit
Check power, enclosure, interfaces, mounting, environment and the exact communication variant. Moxa’s AIG-501 documentation, for example, lists different regional cellular models and separately describes Modbus and MQTT functions. A series-level feature list is a starting reference; verify the actual supplied configuration and its current support.
Protocol support and data meaning
Confirm the implemented version, client/server role, supported operations and application mapping. Preserve source identity and quality information when transforming records. The interoperability and application protocols guide explains why transporting a payload and agreeing its meaning are different parts of the integration task.
Buffering and interrupted delivery
Define what is stored, where, for how long and what happens when capacity is reached. AWS Greengrass Stream Manager documents configurable storage and retention policies for intermittent connectivity. Request a representative interruption and restart review; a store-and-forward feature name does not guarantee unlimited retention, perfect ordering or recovery without duplicates.
Local processing and security
Specify which processing remains local and which depends on a remote service. AWS documents that Stream Manager’s local stream data is not automatically encrypted at rest or between local components, while cloud exports use TLS. Review those separate boundaries, local access and storage protection rather than treating encrypted upload as protection for every copy.
Commissioning and operational records
Agree the expected input and output using an authorised non-production demonstration or site-approved process. Preserve mapping, versions, clocks, configuration and observed failures. Check how an operator recognises stale data, restarts the service through the approved procedure and escalates an unresolved integration fault.
Lifecycle and destination changes
Check support dates for the gateway software and every destination service. AWS documents that IoT Analytics ended on 15 December 2025 and its Stream Manager exports no longer work. That retirement concerns the named service, not all AWS IoT products. Keep a supported export and service-exit plan with the deployment record.
An illustrative integration brief
Choose one authorised source value and specify its identity, unit, timestamp and destination meaning. Ask the integrator to show a normal record, a missing value, an interruption and a controlled restart with evidence. This is a proposed review method, not a completed integration, commissioning result or production change.
Primary documentation
Moxa: AIG-501 series documentation provides a hardware and protocol example. AWS: Stream Manager data handling explains storage and security boundaries; AWS: supported export destinations records the named service retirement. These are supplier documents rather than independent integration tests.
Connect the gateway to an operating purpose
Condition monitoring and maintenance connects measurements with investigation and action. Keep monitoring, remote administration and machine control clearly scoped. No gateway was connected to a field system or cloud account for this guide.
By Admin · Reviewed 18 October 2026. Documentation-based product-type guide; no protocol interoperability, field connection, commissioning, security certification or recovery result tested. Return to Industrial IoT.
Develop the integration and operating brief
EXPLORE FURTHER
Interoperability and application protocols
Separate transport, data models and application meaning.
EXPLORE FURTHER
Condition monitoring and maintenance
Give the data an accountable maintenance workflow.