R.I.P. FCAPS
The FCAPS model has been a big part of network management for well over a decade. For those unfamiliar with FCAPS, the letters stand for Fault, Configuration, Accounting, Performance, and Security, the basic functions envisioned for network management that were then formalized by the ITU in 1997. I can recall FCAPS discussion long before 1997. It became a near-biblical reference in networking circles, as we all struggled to deal with the management of this new bit of complexity. All networking decisions came to include FCAPS in the process.
Times change, and so has the focus on such operational best practices. ITIL is now the model in vogue, so FCAPS has waned in importance. Both are viable perspectives of service management, but ITIL’s broader appeal and widespread development have propelled it over FCAPS.
The biggest problem with FCAPS is its centricity to the network. It was developed by networkers for networkers and it ignored anything outside the network plumbing. Ask a network professional about it and they can probably recite the five topics of FCAPS and maybe even accurately describe each. Ask anyone outside of the networking domain and it’s unlikely that you will get anything other than a quizzical look.
I even sometimes find myself arguing against FCAPS in my own organization. My business unit at EMC is heavily based upon the former Smarts company that EMC acquired in early 2005. Smarts built a formidable position in fault management (remember: the ‘F’ in FCAPS). It has been difficult for many Smarts veterans to shift away from fault management after having been immersed in that discussion for so long. Changing deep-rooted thinking is not easy, but we have made great strides, even amongst the Smarts alumni. We are expanding well beyond the ‘F’ and moving aggressively along the ITIL path.
FCAPS is dead. Let us learn from it, respect it for what it was, and allow it to fade away. ITIL is the new sheriff in town. Let’s move on without FCAPS.
November 29th, 2007 at 14:49
As a Service Management System Architect I find FCAPS still viable in helping me to communicate ITIL to engineers and then using this linkage back towards the Managed service designers. I still apply it to vendors in toolset selection process to inject the need for technical depth as well as all the pretty business dashboards. FCAPS is not dead - it’s just doing a three day week as a wise old consultant to ITIL!
November 30th, 2007 at 15:23
Hi Brian,
Yes, I suppose nothing ever truly dies. All of this just fades off to form a historical reference from which to draw comparisons and to build upon. One of my points is that FCAPS does indeed resonate with those endowed by a good background in networking, but outside this circle, it’s largely unknown.
As we try to align FCAPS and ITIL, we see some problems. The ‘C’ in FCAPS is now spread across Configuration, Change, and Release in ITIL. The ‘P’ is all over the map, with most of its relevance to Capacity and Service Level Management in ITIL.
Is one right and one wrong? No. It’s just the same discussions being spoken in different languages. They’re both mostly right, although ITIL is more formalized and better socialized across technology domains. I do think ITIL could be much better on its treatment of performance, but I guess we’ll all have to work on that for future clarifications of ITIL.
Tools are only beginning the migration from FCAPS to ITIL, especially network management tools. I shudder when I hear people talk so much about Fault Management, including within my own company. Such talk is neither evil nor foolish; it’s just a reflection of the state of transition. I firmly believe that “Fault” Management has become an anachronism. Technology and business conditions have graduated to much more than that. It’s time for us all to move forward with open minds (and tools) beyond faults.
I do like your analogy of the “three day week as a wise old consultant to ITIL” … great point!
– Glenn –
July 24th, 2009 at 17:19
FCAPS dead? Hmmm… I actually read the specs. And when you begin to understand the form and function of Management Functional Domains and Management Functional Areas, you see that maybe FCAPS isn’t quite as dead as you say it is.
ITIL is about process and how to manage IT. FCAPS is a different look and a sifferent take - I feel that FCAPS and ITIL are complimentary. Just like if you say FCAPS is dead because of ITIL, what about eTOM?
There’s a dozen or so different “standards” but in the real world, you adapt, adopt, and abolish.
ITIL new? hehehehehe!!! I’ve been doing workflow based ENMS Architectures since 1993…