Five years ago, I started a career transition by moving from the messy world of telecom IT systems to the mysterious domain of next-generation video infrastructure. At the time, I didn't realize that it would be such a massive leap. After all, IT and engineering are usually down the hall from one another.
By the time a few colleagues and I started our new company in 2011, the change for me was near complete. I had gone from pitching enterprise software to wireless and wireline CIOs to learning the secret language of cable CTOs. It has been challenging to earn a place at the table where long-standing video vendors such as SeaChange International Inc. (Nasdaq: SEAC), Motorola, and Rovi Corp. have long sat. But, as Comcast Corp. (Nasdaq: CMCSA, CMCSK)'s Brian Roberts has suggested, this is a time of unprecedented change in the TV industry. And that brings new players, new needs, and new opportunities. Just ask the impressive Johnny-come-latelies in video such Ericsson AB (Nasdaq: ERIC) and Cisco Systems Inc. (Nasdaq: CSCO).
So why am I here? There's a very simple answer: It's because IT-oriented culture, technology, and software are permeating video back-office systems. In other words, as Light Reading would put it, it's time for (the) SPIT (Service Provider Information Technology) to start flying in the traditionally closed, proprietary, and vendor-locked back offices that make up cable TV. As QAM and its cousins begin to get replaced by IPTV, RDK, and their brethren, a new breed of open, agile, and flexible infrastructures will emerge to keep cable operators relevant and competitive.
At Light Reading Mobile, Sarah Reedy has been writing about open APIs for some time now, but there is still little to be said about them on LR Cable. As Sarah has recently begun to observe, operators may not care so much about APIs to foster a third-party development community, but they sure need open interfaces for their internal development agility. New product development demands that video functions and features like EPG, cloud DVR, search, and OTT content can all be exposed by APIs and available via flexible service-creation platforms for rapid enablement to new screens.
Cable operators know they need to embrace SPIT, and they need to do it now. If they can't use open systems to leverage and integrate new services from the cloud, their roadmaps will lead nowhere. Just look at how Comcast Xfinity is setting the pace with a breadth of services on the television, such as Pandora, Facebook, and voicemail. With its 2011 announcement of CodeBig, which appears to be well underway (although you can't currently register on the site), Comcast is building a blueprint for the next-generation operator, and the rest of the industry will have to adapt to new SPIT-inspired architectures.
What this also means is that video middleware vendors certainly have their work cut out for them. They must be ready to make the shift to SPIT enablers like cloud-APIs and service creation layers or else they'll disappear into their own self-made black boxes. It won't be an easy transition, but I see it slowly happening.
Recently I was on a conference call with the lead architect of a well-known cable set-top vendor, who was lamenting the move of "all these IT guys" into cable, and complaining that opening up APIs, using service-delivery platforms, and implementing transaction layers were all unnecessary. Well, count me guilty because I am one of those IT guys who broke into your domain, and the video back office is on its way to being covered with SPIT.
Oh, and Light Reading, it's time to change your description of SPIT. May I suggest a slight modification to define SPIT as "Light Reading's term for the evolving set of non-traditional telecom, data networking, and cable technologies to allow for a greater degree of flexibility in the creation, management, delivery, and monetization of new-generation communications and video services."
— Gemini Waghmere, Founder & CEO, UXP Systems