FCAPS is a network management framework that organises everything involved in running a network into five categories: Fault, Configuration, Accounting, Performance, and Security. Defined by the International Organization for Standardization (ISO) as part of its network management model, FCAPS gives IT teams a structured way to think about, and a checklist to measure, whether a management system covers the full lifecycle of keeping a network healthy, not just watching it.

What does each letter in FCAPS mean?

Each of the five areas covers a distinct management responsibility.

Fault management is about detecting, isolating, and correcting problems. It includes receiving alarms when something fails, correlating related events to find the real cause, and logging faults so recurring issues can be spotted. The goal is to fix problems quickly, and ideally to catch them before users are affected.

Configuration management covers setting up and changing the network. It includes tracking the configuration of every device, pushing changes, managing firmware versions, and keeping an inventory of what is deployed. Good configuration management means changes are consistent, reversible, and documented.

Accounting management (sometimes called administration) tracks how network resources are used. In a commercial network this can mean billing; in an enterprise or campus network it usually means usage tracking, capacity planning, and understanding who or what is consuming bandwidth.

Performance management measures how well the network is running, throughput, latency, packet loss, utilisation, and uses that data to optimise it. It answers whether the network is meeting its service levels and where the bottlenecks are.

Security management controls access to the network and protects it from misuse. It includes authentication, authorisation, encryption, access policies, and the logging needed to audit them.

Why was FCAPS created?

As networks grew in the 1980s and 1990s, managing them became too complex to handle ad hoc. The ISO developed FCAPS as part of the Telecommunications Management Network (TMN) model to give operators a common vocabulary and a complete checklist. Rather than every vendor and operator inventing their own categories, FCAPS provided a shared framework so that management systems could be compared and so that no critical area was overlooked.

How is FCAPS used in practice?

FCAPS is most useful as an evaluation lens. When an organisation assesses a network management platform, the five categories reveal gaps: a tool might offer excellent fault alarms and performance dashboards but weak configuration control or thin security management. A platform that genuinely spans all five is described as delivering "full FCAPS," meaning it can run the whole management lifecycle from one place rather than forcing teams to stitch together separate point tools.

In large, distributed networks, campuses, carrier networks, enterprises, this matters because a small operations team cannot manage hundreds or thousands of devices with fragmented tooling. Consolidating FCAPS functions into a single management plane is one of the biggest levers for reducing operational workload.

FCAPS and modern AIOps

FCAPS predates artificial intelligence in network operations, but the two fit together. Modern AIOps (AI for IT operations) platforms build on the FCAPS foundation and add prediction and automation: instead of only detecting a fault, they anticipate it; instead of only reporting performance, they recommend optimisations. FCAPS still describes what needs to be managed; AIOps changes how proactively it can be done.