SimtoLink: Each street-light controller gets its own SIM
A microgrid controller, or energy management system (EMS), coordinates distributed generation, storage, and load. On-grid, it takes part in dispatch and peak-valley optimization. Off-grid, it keeps voltage and frequency stable. At the instant of an on-grid or off-grid switch, the communications link may drop briefly or latency may jump, so local autonomous algorithms must first protect supply continuity and protection coordination. IoT SIMs are often used for remote monitoring, logs, and over-the-air updates, and in some cases they also carry auxiliary dispatch information.
Islanding, reconnection, and communications layers
Switching off-grid and back on-grid involves synchronization, phase detection, and a change of protection settings. Communications are used mainly to coordinate the order of switch operations and to report status. The hard real-time closed loop still runs in the local controller. Monitoring and control should be layered: PMS/SCADA over a private network, and operations over-the-air updates over cellular or a reverse isolation path. Switch events should carry a high-precision timestamp so waveforms can be aligned afterward. SimtoLink can provide a dual-carrier SIM strategy and remote asset control for mobile microgrid cabins and island microgrids. For long off-grid operation, low power and dial-on-demand save energy.
Applications
Typical sites include backup power for industrial parks, solar-storage-charging at charging stations, emergency power in disaster areas, and remote outposts. An interface to grid dispatch must meet local grid-connection standards and a cybersecurity assessment. Drills should regularly include an off-grid black start and an on-grid synchronization test, to verify the safety boundary when communications fail.
Deployment and operations
During implementation, the enterprise should bind each IoT SIM number one to one with the device serial number, installation location, power method, and the person responsible for maintenance, and enter them in the asset and operations systems, forming a traceable chain from activation, change, and live service through sleep and final cancellation. For equipment moved across provinces or delivered across borders, roaming charges, real-name policy, and local data-compliance requirements should be assessed in advance. Prefer a plan with predictable cost that supports remote network change or eUICC, so devices are opened on site less often, and keep spare SIMs and an emergency replacement process to shorten recovery. For terminals arriving in bulk, sample them, verify coverage and charges, and then activate the batch, which lowers rework cost.
On cybersecurity, production or critical-infrastructure terminals should use a private APN or a VPDN tunnel so north-south traffic converges at a boundary the enterprise controls, and this should be linked with identity authentication, bastion-host remote maintenance, and operation audit. Remote control and parameter writes should have graded authorization, a time window, and a two-person review. Weak-network and primary-backup switchover drills should be run regularly, and latency, packet loss, and recovery time recorded, as technical evidence for MLPS assessment, industry supervision, or an internal risk review. For outsourced maintenance, least privilege, session recording, and key-custody boundaries should be explicit, and shared accounts avoided. In daily operations, the SIM management platform should keep tracking online rate, abnormal traffic, silent terminals, and plan utilization, and alarms should be connected to the ITSM ticket system so tickets are assigned and closed automatically. SimtoLink can split data pools by plant, line, or business domain, and provide bulk suspend and resume, API integration, and bill allocation, so large numbers of sites stay visible, controllable, and able to keep reducing cost, and SIM insight is aligned with project budgets and cost centers for clearer accounting.
Source: https://www.simtolink.com/support/sim/microgrid-controller-link.html