What to expect from a TankActive install

What happens before activation?

TankActive starts with a compatibility and connectivity review. The team identifies the automatic tank gauge (ATG), its available interfaces, the location network or cellular constraints, and the people authorized to approve access. That review determines whether the planned connection is supported and what information or onsite work is needed before activation.

Supported Omntec Proteus deployments can often connect without replacement hardware. That is not a blanket promise for every Proteus configuration: model, software, interface, network access, and current condition still need to be confirmed. Veeder-Root, Franklin Fueling, and other ATG systems are reviewed during setup, and compatibility and the connection method are confirmed before activation rather than assumed.

The review should also establish scope. List the locations, tanks, products, users, and supported data expected in the first handoff. Identify the operating contact who can validate the gauge and the IT or network contact who can authorize connectivity. A clear scope avoids treating a working data path as complete when tank mappings or access assignments are still unresolved.

What information should your team provide?

Provide source information rather than guesses. Photos of the gauge label and communication interfaces can help identify the model and installed options, but they should not expose passwords or other credentials. If the software version or network owner is unknown, mark it for discovery so the installation plan does not depend on an unverified detail.

Use the product’s Location terminology consistently. The location name, address, tank numbers, and products should match the organization’s operating records closely enough that users can recognize them. Decide who has authority to correct a mismatch before data is activated.

• Location name, address, and primary contact.
• ATG manufacturer, model, software version, and a clear equipment photo.
• Tank and product details that can be checked against the gauge.
• The network or IT contact if the connection uses location infrastructure.
• Known VPN, firewall, cellular, power, access, or maintenance constraints.
• The people who need dashboard or mobile access and the organization role each person should receive.

How is the connection method confirmed?

Connectivity may use an existing VPN, a cellular connection, or a direct ATG network connection, depending on the location and gauge. The choice should be approved by the people who own the network and equipment. It should limit access to the required purpose, document dependencies, and name the team responsible for future support.

An existing VPN may fit a centrally managed fleet. Cellular may separate the ATG path from the business network but requires suitable coverage, power, equipment access, and service ownership. A direct network connection may use existing gauge capability only when the specific deployment and access design are supported. Do not expose an ATG to the public internet or make an unapproved firewall change to speed up activation.

Share sensitive connection details through the approved secure channel. Record the final path in a location-level handoff without placing credentials in screenshots, public documents, or general support notes.

What are the setup steps?

1. 1TankActive reviews the ATG identity, interfaces, configuration details, and available connection paths.
2. 2Your team confirms the location, tank, product, network owner, operating contact, and intended user scope.
3. 3The authorized connection method is configured and tested without expanding access beyond the approved design.
4. 4The intended ATG and data source are confirmed before tank and product mappings are accepted.
5. 5Received inventory, supported ATG status, alarms, and other available data are checked with someone who knows the location.
6. 6Authorized users are invited, access assignments are reviewed, and notification ownership is confirmed.
7. 7The final connection, validation evidence, open items, support owner, and handoff decision are documented.

How long does installation take?

Supported installations typically take under two hours per location once required access and information are ready. The statement applies to supported installations with the needed contacts, approvals, connection path, equipment access, and location details available. It is not a guaranteed appointment length for every ATG or network.

A new network path, unconfirmed interface, onsite service need, weak cellular coverage, firewall approval, unavailable IT owner, equipment issue, or missing location data can extend the schedule. The compatibility review should surface these dependencies before the activation window where possible.

Measure completion by validated scope rather than elapsed time. A connection that reaches a gauge but has unverified tank mappings, missing user access, or unresolved data questions is still an open implementation. Document those items and assign owners rather than declaring completion to preserve a target duration.

How are readings and mappings validated?

A technician should first confirm that the approved connection reaches the intended ATG. Then an operating contact should compare the location, tank numbers, products, current inventory, and ATG status with the source gauge and known location conditions. This two-part check catches both transport errors and meaning errors.

Tank inventory and status typically refresh every 5–15 minutes depending on ATG configuration. Validation should account for that cadence rather than expecting every value to move instantly. Supported critical alarm events are routed as soon as TankActive receives them from the ATG, but alarm availability and meaning still originate with the connected system and supported configuration.

A reading that appears technically valid may still belong to the wrong tank or product. Resolve mapping questions before broad user rollout. If the gauge or source information appears incorrect, involve the qualified owner rather than editing the display to conceal the discrepancy.

How should user access be handed off?

Invite only the people authorized for the organization and give each person the access needed for their responsibilities. Confirm that users can sign in through the intended path and see the correct organization data. Do not use one shared credential as a substitute for individual access.

Review who receives operational notifications and what each recipient should do. A contact list alone is not a response process. Identify primary and backup owners for inventory, ATG alarms, connection outages, and billing or account questions as applicable.

Show users where to find the dashboard or mobile app views included in their workflow and how to contact TankActive support. Avoid promising that every ATG function appears remotely; demonstrate the supported information actually available for that connected deployment.

What should you verify before handoff?

• Every expected tank appears under the correct location and product.
• Current inventory, data freshness, and supported ATG status are checked against the source and operating context.
• Received supported alarm and delivery information is reviewed where it is part of the deployment.
• The right users can sign in and see only the organization data assigned to them.
• Notification destinations, operational thresholds, and response owners match the approved operating plan.
• The connection owner, operating contact, support contact, and escalation path are known.
• Open items, limitations, and follow-up owners are written down rather than left as verbal assumptions.

How does TankActive help after activation?

Watch the new connection during normal operations and investigate gaps, unexpected mappings, repeated offline periods, or missing supported records. Early follow-up should test the operating process as well as the technology: recipients need to recognize the location, understand the notification, and know who owns the next action.

Include the connection in future change management. ATG service, router replacement, firewall changes, cellular work, power changes, tank remapping, or staff turnover can affect monitoring even when the original setup was correct. Revalidate the affected scope after material changes.

TankActive support is available at support@tankactive.com or +1 (631) 981-2001, Monday–Friday, 8:00 AM–5:00 PM Eastern. Response timing depends on request volume and issue complexity. For a useful support handoff, include the organization, location, affected ATG or tank, last known good time, observed behavior, and any recent changes without including passwords.