Wireless

Overview

The TMS wireless area is the operator-facing workflow for reviewing wireless terminal inventory and spotting connectivity records that still need follow-up before field troubleshooting or failover work.

Current Wireless Workflows

The current platform implementation supports these customer-safe workflows:

• review which terminals are currently modeled as wireless
• inspect carrier, communications-provider, and device-inventory metadata attached to a terminal record
• check whether WAN visibility has been observed recently enough to support troubleshooting
• identify records that are still missing inventory or readiness details such as router serials, backup-carrier planning, or failover evidence
• follow links back to terminal detail for deeper investigation, routing review, or command work

What Operators Should Look For

Wireless workflows are most useful when operators treat the page as a readiness and exception surface, not just a raw inventory table.

• confirm that the terminal is actually marked wireless when the field deployment depends on cellular connectivity
• make sure the carrier or communications provider metadata is present and current
• verify that a recent WAN observation exists before assuming remote troubleshooting will work
• use the page to find records that still need backup-carrier, router-serial, or failover follow-up
• jump back to terminal detail when a connectivity issue turns into broader routing, RMS, or incident work

Relationship To Terminal Detail

The wireless page is a fleet-level view. Terminal detail remains the place for deeper per-machine context such as telemetry, RMS activity, alerts, routing state, and broader lifecycle history.

Use the wireless page when you want to answer questions like:

• which wireless terminals are missing key support metadata?
• which devices have not reported enough WAN information yet?
• which records still need failover-readiness cleanup before a field event?

Use the terminal page when you need to inspect one machine more closely or continue into adjacent workflows.

Public Boundary

This page is intentionally customer-safe.

• it should help operators understand wireless inventory and connectivity readiness
• it should not publish VPN credentials, carrier-account secrets, private network topology, or internal-only remediation runbooks
• internal switch telemetry payloads and sensitive network operations remain outside the public docs boundary

Related APIs And Surfaces

The customer-facing docs site does not expose private network credentials or internal-only troubleshooting endpoints. The broader live platform surface still includes terminal, connector, and routing APIs plus the authenticated TMS browser workflows that back wireless operations.

For adjacent guidance, see Terminals and the higher-level Terminal Management.