© 2011, All informaon contained herein is the sole property of Pipeline Publishing, LLC. Pipeline Publishing LLC reserves all rights and privileges regarding the use of this informaon. Anyunauthorized use, such as distribung, copying, modifying, or reprinng, is not permied. This document is not intended for reproducon or distribuon outside of
.To obtain permission to reproduce or distribute this document contact
for informaon about Reprint Services.
very cute cat to a ash drive and plug that into my television to revel in her cuteness in HD. Importantstuff.Indeed, we’ve come a long way from the tedium of having to manually manage multiple drivers in ourPCs at home, so it would stand to reason that, outof the aggregate billions that CSPs spend on OSS/BSS solutions, said solutions should come with that same plug-and-play functionality. Certainly, themultitude of telecom standards should have thepotential to drive change in the OSS/BSS space in terms of application integration, right? For example, anumber of developers program CRM solutions using SQL, a language designed for relational databasemanagement systems (RDBMS). SQL, however, alsoserves as a prime example of how an attempt at openstandards failed due to self-interest.What is more compelling is the notion of anoverarching Communications Operating System(ComOS)upon which we could bundle a networksolution with billing and CRM products into oneintegrated package, much like a Microsoft Ofce Suitefor telecom. To take this concept a step further, theimplication that the purchaser of MS Ofce at anyCSP can also purchase an integrated ComOS suiteportends a shift in traditional engineering softwarefrom the back ofce to the IT department.
Caution: Service-Oriented Architecture Ahead
The key to technological and commercial evolutionis adaptation. The old model of integrating siloedapplications required programmers to writecomplicated, custom utilities—a tedious, timeconsuming endeavor—to read and decode databefore it can be shared with other applications, and that simply cannot keep up. On the ip-side, theemergence of service-oriented architecture (SOA) isnot so much revolution as it is evolution. The promiseof SOA lies in its ability to deliver interoperable,independent, modular and reusable software in the form of components or “services.” This affordsbusinesses the nimbleness they need to adaptquickly but, more importantly, it’s all made possibleby open standards.With that said, it is not enough to simply embrace the technology.More important to the full realization of the benets of open standards and SOA is the needfor companies to embrace change on a cultural leveland to step away from the silo, in terms of both IT and thinking. Herein lies the rub; as any anthropologist will tell you, culture evolves at a snail’s pace.The elder Moltke gave us the military maxim, “Noplan survives contact with the enemy.” A real worldvariant translates this into the notion that any plan,idea or concept is only as good as the humanswho implement it. The New and Improved PartnerEcosystemThere is hope, though. Microsoft has come full circle
What is more compelling isthe notion of an overarchingCommunications OperatingSystem (ComOS).