Peplink MAX Transit and InControl Field Runbook
MAX Transit models combine one or more cellular modems with Ethernet, Wi-Fi, GPS, InControl and SpeedFusion features for transportation or fixed deployments. Model and regional variants differ, so the field team must reconcile modem, SIM/eSIM, antennas, power and approved software before installation.
Make each dispatch repeatable and recoverable
Define prerequisites, remote ownership, method of procedure, acceptance evidence and rollback before technicians arrive onsite.
Model, carrier and InControl pre-staging
Verify product code, modem and region, hardware revision, antennas, power accessories and mounting kit. Confirm the InControl organization, group, license or PrimeCare and approved firmware. Claim only into the authorized customer account.
Activate SIM or eSIM profiles, APNs and plans before dispatch where possible. Stage LAN, Wi-Fi, WAN priority, health checks, firewall, GPS reporting, captive portal, SpeedFusion and edge applications through change control. Record sensitive SIM data only in the protected system.
The remote team should supply the site identifier, approved design, equipment list, configuration status, contacts, access window and success criteria. The field technician verifies serials, labels, damage, accessories and prerequisites before changing production service.
- Exact model and modem region
- InControl and subscription
- SIM/eSIM and APN
- Approved firmware/configuration
Power, antenna and physical installation
For vehicles, use an approved fused power and ignition-sense design with secure mounting, airflow and vibration considerations. For fixed sites, verify supply, UPS and environmental limits. Label power, Ethernet, SIM and every antenna lead.
Mount antennas on a suitable ground plane or approved surface with separation and unobstructed view. Protect penetrations, coax and connectors from weather and abrasion. Do not coil excessive cable near radios or interchange cellular, Wi-Fi and GPS leads.
Use a written method of procedure with hold points for configuration-sensitive actions. Photograph and label the before state, preserve known-good cabling or configuration, and keep a practical rollback path. Record deviations as they occur instead of reconstructing them after the visit.
- Fused or backed-up power
- Secure environmental mounting
- Antenna port and cable labels
- Weather/abrasion protection
| Layer | Check | Evidence |
|---|---|---|
| Hardware | Variant, modem, power and antennas | Inventory/photos |
| Carrier | SIM, APN, band and RF quality | Modem status |
| Service | LAN, Wi-Fi, GPS, VPN and apps | User tests |
| Resilience | SIM/WAN/SpeedFusion behavior | Event timeline |
Cellular, Wi-Fi, GPS and SpeedFusion testing
Confirm expected carrier, bands, modem state and signal-strength and quality metrics. Test APN addressing, DNS, applications, VPN and inbound behavior where specified. Compare both modems or SIMs rather than accepting the first registered connection.
Test Wi-Fi clients, GPS location and reporting and the approved SpeedFusion or WAN-failover scenario. For mobile deployments, collect results at representative operating locations and during handoff between coverage areas when the project requires it.
Validation must cover physical status, management visibility, addressing, uplinks, power, policies and representative user traffic. When redundancy is expected, test the approved failure and restoration scenarios. Escalations should include timestamps, identifiers and reproducible evidence.
- Carrier and RF metrics
- Applications and VPN
- Wi-Fi and GPS
- SpeedFusion/failover scenario
Fleet records, monitoring and handoff
Reconcile serial, modem identifiers, protected SIM references, antenna model and port, power source, Ethernet, software, InControl group and vehicle or site ID. Capture signal, application and failure-test evidence.
Assign data-usage alerts, subscription renewal, firmware, configuration backup, fleet monitoring and carrier escalation. Keep official manuals and firmware links in the closeout, while credentials and precise fleet information remain client controlled.
Closeout combines annotated photographs, serials, port and cable records, software versions, test output, exceptions and ownership. Credentials and private configurations belong in the client-controlled repository, while public pages should point only to official manufacturer support resources.
- Site/vehicle inventory
- Protected SIM references
- Data and alert ownership
- Firmware and support process
How we plan and deliver the work
The final design depends on site conditions, existing systems, client policies and the selected manufacturer or platform.
Prepare
Confirm access, equipment, remote readiness and rollback.
Execute
Install through the approved method and document deviations.
Test
Validate management, service, resilience and user workflows.
Close
Deliver evidence, inventory, exceptions and support ownership.
Information to gather before design
Good decisions are easier when the project team starts with complete operational and technical information. The following items help reduce assumptions, change orders and avoidable return visits.
- Site access and remote contacts
- Staging, inventory and prerequisites
- Method, maintenance window and rollback
- Acceptance tests and escalation
- Evidence and operational ownership
Frequently asked questions
These are common planning questions. A site-specific answer should be confirmed during discovery and design.
Can any MAX Transit model be used with every carrier?
No. Verify the exact regional modem, bands and current carrier certification.
Are included paddle antennas always sufficient?
Not necessarily. The environment, vehicle or building, cable loss and RF measurements determine the antenna design.
Why record both signal strength and quality?
A strong but noisy or congested signal can still provide poor application performance.
What belongs in fleet closeout?
Router and modem inventory, protected SIM reference, antennas, power, software, InControl group, tests, alerts and ownership.
Manufacturer software, firmware and technical files remain on the manufacturer’s official website. We do not mirror firmware files locally.
Build a repeatable field-deployment plan
Provide the site list, target schedule, equipment responsibility, change-window constraints and acceptance criteria. We will help turn them into a practical rollout and closeout workflow.