Definition
Global Dashboard is a unified visual dashboard provided by the ICMP platform, centrally displaying core metrics such as multi-region card volumes, usage, alerts, billing, and connection status. Together with Single Pane of Glass unified view and KPI Dashboard, it helps customers achieve global monitoring and decision support for cross-border IoT assets.
Display Content
Global Dashboard Typical Display: Card Quantity Statistics——Total cards, by status (active/paused/terminated), by region, by customer distribution; Usage Statistics——Total traffic, by country, by carrier, trend chart; Alerts and Exceptions——Offline devices, over-limit alerts, abnormal consumption, connection failures; Billing Overview——This month's charges, pending settlement, year-on-year and month-on-month comparisons; Connection Quality——Attachment success rate, average signal strength, Card Diagnostics health. Supports filtering and drill-down by time range, customer, project, and region.
Relation to Single Pane of Glass
Global Dashboard is the implementation of the Single Pane of Glass concept: it aggregates data scattered across multiple systems and regions into a single view, avoiding the need for customers to switch between multiple platforms. Combined with KPI Dashboard, key KPIs and threshold alerts can be configured to support operational decisions and abnormal responses.
Implementation in ICMP
SimtoLink ICMP's Global Dashboard aggregates data sources such as Usage Analytics, CDR, Cross-Border Billing, Card Diagnostics, etc.; it supports multi-tenant isolation, allowing customers to view only their own data; provides APIs and export functions for easy integration into customers' own BI systems; supports customized dashboards and Event Subscription alert linkage.
Dashboard Measures and Time Alignment
A global dashboard is an aggregated projection, not a second meter. SIM counts come from lifecycle state, traffic from CDRs or counters, alerts from diagnostics and events, and charges from billing results. These sources do not close at the same speed: a suspension or resume can show up in status at once, while cross-border usage often settles only after the visited network returns the CDRs. Before using the board, agree three things: whether the window is cut by platform time zone, customer time zone, or billing cycle; whether the filter is tenant, project, or country; and whether unclosed records may appear on the chart. A meeting can use it for distribution and trend. To confirm what a given day should settle, go back to closed usage aggregation and the invoice. The figure on screen is not the amount payable.
It fits when one connectivity platform already sees several regions or carriers, and the reader needs one place to judge which SIMs are in service, which usage has drifted, and which charges have not entered settlement. It does not replace single-SIM diagnostics or a formal invoice. In a multi-region deployment the access point may sit near the device while accounting is written on another node. If the board mixes those clocks, the same SIM can appear as two peaks in two different hours. An export must keep the filters that were in force. Otherwise the file is only numbers, with no way to see which tenant or which region it belongs to.
Where Cross-Region Readings Drift
The easiest mistake is to reconcile against current usage. When roaming CDRs arrive late, that day’s bar sits too low, then jumps when the late records land, which looks like a sudden burst of device consumption. Another bias comes from status. A suspended SIM can still leave a little signaling, and if terminated SIMs stay in the statistical set the denominator grows and the active share is pushed down. Plotting attach results from different carriers on one series, without saying whether the sample is attempts or SIMs online, makes a weak network look like a platform fault.
Filter order also rewrites the result. Customer then country, versus country then customer, may not be the same SIMs in a multi-tier channel, because the country where a SIM sits is not the customer’s country of registration. If the alert total mixes acknowledged and unacknowledged events, the on-call shift will dispatch events that were already handled. When reading a global dashboard, check the metric definition, whether the CDRs are closed, and which layer the filter covers, then decide whether to drill into a single SIM.
Daily trends need their own day cut. Visited networks often return usage in their own billing batches. Traffic a device produces in the local evening may already fall on the next day in the platform time zone. If the board cuts the calendar day at midnight in one time zone, evening usage in Europe slides into the next day, and Asia-Pacific traffic that crosses midnight can land in the previous month. Before comparing yesterday and today, write down the day-cut time zone and whether the chart includes records that are not yet closed. A sharp drop between two adjacent days is sometimes only a change in the day cut, not a device that stopped sending.
Drill-down and export must carry the same conditions. Opening a SIM list from a country alert should still limit the list to that country, that tenant, and that time window. If the drill-down becomes every SIM, the reader will think the alert grew. The exported file should include the metric name, the start and end of the count, the time zone, the filter scope, and the time it was generated. A file that contains only a number cannot, the next day, explain which SIMs it referred to. When several people view the board at once, one person’s saved filters must not overwrite another’s, or a handover will treat someone else’s customer scope as their own.
The board is for finding anomalies. It is a poor sole basis for approval. Suspension, price changes, and settlement confirmation should return to the specific SIM, CDR, and invoice, and should run only after status and amount are checked. Acting in bulk on a red number in the overview easily pulls in late CDRs, test SIMs, and alerts already acknowledged. The overview shows where to look. Each layer of detail keeps its own measure.