Three ways to connect an ATG for remote monitoring

How does an ATG connect to remote monitoring?

Remote monitoring needs a secure, reliable path between the automatic tank gauge (ATG) and the monitoring service. That path may use an existing virtual private network, a cellular connection, or a direct ATG network connection, depending on the location and gauge. The connection carries supported gauge data; it does not change how the ATG measures inventory or generates its own alarms and test results.

There is no universal best method. ATG model and interface, network ownership, security policy, carrier coverage, firewall controls, equipment access, and the people responsible for support all affect the decision. The right design is the one the location can authorize, operate, and troubleshoot consistently. The monitoring provider should confirm compatibility and the connection method before activation rather than assuming that a familiar gauge name or visible network port is sufficient.

Start with discovery, not cabling. Record the ATG manufacturer, model, software version, available communication interfaces, current network connection, and any existing remote-access equipment. Identify the organization that controls the location network and the person allowed to approve changes. Clear information at this stage prevents an installation plan from depending on access or hardware that is not actually available.

When does an existing VPN make sense?

A managed virtual private network can let approved traffic reach the ATG over infrastructure the organization already operates. This option can fit fleets that connect locations to a central network and have an IT team responsible for addressing, routing, firewall rules, monitoring, and change control. It keeps ownership with the team that already supports the location network.

The important question is not simply whether a VPN exists. The team must confirm that the ATG is reachable through the approved route, that the connection can be limited to the required destination and traffic, and that the design will survive ordinary network changes. A broad remote-access rule is not a substitute for a documented, least-access path.

Operational ownership matters after activation. The network team should know how the route is monitored, how planned changes are communicated, and who investigates when the ATG becomes unreachable. A remote-monitoring service can report that data has stopped arriving, but the organization still needs a path to distinguish an ATG issue from a local network or VPN issue.

• Confirm that the ATG has a supported network interface and stable address.
• Limit routes and ports to the traffic required for the approved connection.
• Document who owns VPN monitoring, firewall changes, and incident response.
• Record any network dependencies that could interrupt the path during maintenance.

When is cellular connectivity useful?

A cellular path can keep supported ATG traffic separate from the location’s business network. It may be useful when that network is unavailable, tightly controlled, managed by a third party, or inconsistent across a fleet. Separation can simplify coordination, but it introduces its own equipment, carrier, signal, power, and service ownership.

Coverage should be evaluated where the connection equipment will operate, not from a general coverage map alone. Building materials, equipment-room placement, antenna location, and local conditions can affect reliability. The installation plan also needs safe power, physical access for service, and a named owner for the cellular device and subscription.

Cellular does not eliminate change management. A device can lose power, service can lapse, or signal conditions can change. Decide who receives an offline notification, who can inspect the location, and who contacts the carrier or service provider. Keep device identity and support information with the location record so troubleshooting does not begin with a search for ownership.

• Verify carrier coverage at the planned equipment and antenna location.
• Plan for antenna placement, power, and equipment access.
• Assign responsibility for the cellular device, service, and renewal.
• Keep the ATG connection isolated and limited to the approved purpose.

When can a direct ATG connection work?

Some supported deployments can use the gauge’s existing network connection. Supported Omntec Proteus systems can often connect without replacement hardware. That statement is specific to supported Proteus deployments: the model, configuration, access, and network path still have to be confirmed before activation.

Veeder-Root, Franklin Fueling, and other ATG systems are reviewed during setup. A manufacturer name alone does not establish compatibility because interfaces, software versions, installed options, and network conditions differ. The review determines whether the existing interface is supported and whether another connection method or onsite work is needed.

A direct connection should still follow the location’s security process. Do not expose a gauge to the public internet or make an unapproved firewall change merely to accelerate setup. The network owner should approve addressing and access, and the final configuration should be documented so later troubleshooting does not depend on personal memory.

How should the three options be compared?

Compare options across authorization, reliability, security, support ownership, and physical constraints. An existing VPN may align well with a centrally managed fleet but depend on the corporate network team. Cellular may avoid that dependency but require signal and equipment support. A direct ATG connection may use existing capability but only when the gauge and network configuration are supported.

Avoid choosing solely by the smallest initial task. The operating model after activation matters more: who notices an interruption, who can access the equipment, who approves changes, and how the path is restored. A technically possible connection is not operationally complete until those responsibilities are clear.

• Authorization: Who owns the network, gauge, and approval decision?
• Reliability: Which dependencies can interrupt the connection?
• Security: Can access be limited to the approved traffic and destination?
• Support: Who troubleshoots the ATG, network path, and connection equipment?
• Consistency: Can the approach be documented and supported across locations?

What should the location provide before setup?

Share credentials only through the approved secure process, never in a public ticket or guide. If details are unknown, say so rather than guessing. A wrong ATG version, network owner, or location assignment can lead to unnecessary work and make later validation harder.

• ATG manufacturer, model, software version, and available interfaces.
• Clear photos of the gauge, labels, and communication connections without exposing credentials.
• The location’s network or IT contact and the person authorized to approve access.
• Known firewall, VPN, or cellular constraints.
• Current network addressing or connection information shared through an approved channel.
• A maintenance window and onsite contact if a physical change is required.

What should be tested before activation?

Validation should cover both transport and meaning. First confirm that the approved path reaches the intended ATG consistently. Then confirm that received data belongs to the correct location, tanks, and products. A working connection to the wrong gauge or an incorrect tank mapping is not a successful activation.

Review current inventory and ATG status with someone who knows the location. Where supported data is available, compare received alarms and delivery information with the gauge. Confirm that temporary test access has been removed, final ownership is documented, and authorized users know where to report a problem.

1. 1Confirm the approved connection path and identify every device or service it depends on.
2. 2Verify that the intended ATG is reachable without broader access than the design requires.
3. 3Match locations, tanks, and products to the source gauge with the operating team.
4. 4Review data freshness and supported ATG status after the connection remains in normal service.
5. 5Document the final design, owners, and troubleshooting path before handoff.

How does TankActive help after activation?

TankActive shows the latest supported data it has received from the connected ATG, including the reporting state and reading time available for the Location. Use that visibility to identify a gap, then investigate the source gauge and approved connection path; an offline state does not identify which network, power, or equipment component failed.

Treat router replacements, firewall changes, ATG service, addressing changes, carrier work, and Location network redesigns as potential monitoring dependencies. Include the TankActive connection in change planning, then verify the data path after the work is complete. Preserve the last received time when reporting stops, and keep a short connection record that the Location operator, IT owner, and support team can understand.