Public Questions & Answers

Pooled plans can reduce waste when sites vary a lot in usage, but tracking which site consumes what and charging back costs can be more complex. Site-specific plans make cost attribution straightforward and let each site stay within its own budget, but unused allowance at one site can push up overall costs and reduce flexibility. Practical steps to decide: estimate total data usage and distribution across sites, model costs under each option, run a short p…

Start with per-site thresholds: cap data usage and set an alert when approaching the limit. Use site-level consumption and delta transfers to avoid false triggers. Define alert rules for data usage, uptime and connectivity, and remote-management activity; set initial values (for example, warn at around 80% of plan usage and critical at 95%), with time-based considerations to avoid noise. Choose alert channels (SMS for urgent items, email or dashboard for o…

Start with a practical site picture: inventory devices, sites and the data each site generates. Use the router or your management platform to capture counters for usage, reporting frequency and data flows, and map how much data is going where. Then set thresholds and alerts per site and use a central dashboard to review usage by site. Compress data and send only delta changes where possible, and schedule large transfers for off-peak times. Consider a poole…

Many do, because the challenge is often reliability rather than bandwidth. A telemetry site may send tiny amounts of data yet still need to survive power events, operate unattended, reconnect cleanly and support external antennas or remote management. If the cost of a missed alarm or a site visit is high, an industrial router can be justified very quickly. Comset usually frames that as a cost-of-failure question. Small data use does not automatically mean…

Machine-to-machine traffic is usually driven by devices and events rather than by people browsing the web. That means uptime, deterministic behaviour, remote support and clean recovery after interruptions often matter more than raw speed. The traffic itself may be tiny, but the business consequence of losing it can be large. That is why Comset talks about interfaces, alarms, management and deployment conditions as much as it talks about download rates. Th…

Estimate payload size, reporting frequency, protocol overhead, retries, remote-management traffic and software updates for each device. Add occasional diagnostics and a safety margin, then multiply by the fleet size. Cameras and log uploads need separate calculations because they can dominate usage. Use router or management-platform counters, set alerts near plan limits and review usage by site. Compress data, send changes rather than full records and sch…

At small scale, a shared password and manual spreadsheet may appear manageable. At hundreds of devices, the business needs unique credentials, controlled configuration templates, firmware tracking, role-based access, inventory, audit logs and automated alerts. Network segmentation and certificate or key rotation become important, as does a process for decommissioning lost or replaced devices. Management traffic and update windows must be planned so the fl…

A full industrial router is appropriate when several local devices need Ethernet or Wi-Fi, when traffic needs firewalling or VPNs, when dual SIM or WAN failover is required, or when the site needs remote management, serial interfaces, GPIO and automatic recovery. It becomes the local network gateway rather than a simple radio link. A basic cellular modem may be enough for one device with its own networking and security, especially at low data volumes. The…