Over the years, I’ve caused much consternation amongst engineers, as I talk of the looming “anarchy” regarding the standards used in network and systems management.

The surprise is in part because of my active role in standards bodies (charter member of the TMF NGOSS team, and a former DMTF chair) but mainly because talking about anarchy is just so counter-culture.

Occasionally I look back wistfully at the glory days of SNMP. Things were so simple then. Well, that’s the point; things were simpler in the 80’s. While SNMP still plays an important role in managing a good chunk of the network, structures like the MIB, and GDMO became to restrictive for creative developers.

Some opted for the chaos of syslog, or its refined cousin Common Event Format. Others decided on a more proprietary route, mitigating their approach by using XML, or JSON. Both using natural language to make the messages mores flexible and expressive.

If you built your management architecture based on an SNMP MIB paradigm, then this is anarchy indeed. But if you have a 21st Century solution that handles Natural Language Processing in its stride, it’s actually great news.

You see, natural language adapts to change very well indeed, no developing schemas, or forward compatibility issues, no lengthy ratification processes or system upgrades or normalization, and so on.

We agree, with Incident.MOOG’s natural language processing capabilities, we feel embracing even anarchy could be the new standard.

If you’d like to hear more of my view on natural language processing and Incident.MOOG, I invite you to join me at my next Webinar, “Managing Large, Complex IT Operations Projects” on Thursday July 10th. Con Blackett, former IT executive at BT, will be co-presenting with me.