DMR: For example?

John Keagy: Features. Features of people supposedly want, what’s supposedly important to customers and what’s not. It’s very different than what people like to blog about. There’s a lengthy list of small items and some big architectural ones.

DMR: Like Cloud-in-a-box – which more often than not turns out to be “in-a-box” but not “Cloud”?

John Keagy: Sure! There are also a lot of folks out there trying to sell cloud operating systems to telecoms. But so far the only one that’s proven to operate to a scale telecoms would need is our SkySys operating system. There’s just nobody else that’s achieving that scale, not even in order of magnitude. In terms of a cohesive system that offers all the elements of compute, storage, billing, and customer management and operations, in something that pundits don’t write about but that is a very practical need, and that’s the operational tool for delivering the service. That’s something that all these other companies that think they’ve got a system that can distribute the ends on the hardware. They think they’ve got the system. That’s one of 36 elements of our system.

DMR: Is there a difference between mature and emerging telecoms and what SkySys allows them to do or how they would use it?

John Keagy:  So far we are working only with well established telecoms: SkySys is targeting your existing data center, your existing hardware. Emerging operators often either don’t have that data center yet, or – exactly because they are emerging – they don’t want to have them. Purchase equipment, “rack and stack” that equipment, and manage capacity is not yet a best practice for emerging telecoms. It could be.

DMR: Thank you for sharing your time and insights.