A TETRA network is infrastructure, and infrastructure is judged by how it is operated over a decade rather than how it is commissioned. The NMS is where that operation happens.

The system follows ITU M.3010 and the FCAPS model — fault, configuration, accounting, performance and security management. That matters practically rather than academically: an NMS built to a framework covers the operational domains systematically instead of accumulating features around whatever was asked for.

• User activity auditing — who did what, recorded
• Local key management
• Terminal enable and disable by TEI or ISSI — a lost terminal removed from the network
• Microsoft Active Directory with smart cards to block unauthorised access

For a network carrying operational traffic, terminal disable is the control that matters most: a radio that leaves the organisation with an employee is a live credential until it is revoked.

Tree view for structured visualisation, real-time response and detailed analysis. On a network of any size the presentation matters as much as the detection, because an operator who cannot find the fault in the display has not been told about it.

Distributed multi-client, multi-server, scaling modularly with network size and requirement, with a comprehensive central database for reliable storage and analysis of management data. See TETRA systems.