Keeping a Lid on Oracle Licensing Costs while Ensuring Compliance
Nov 20, 2007 / By Paul Vallee
If this post seems a bit like an “advertorial”, please believe me — it’s not. Well, at least it’s not an advertisement for Pythian in any way. What it is, however, is a post about a longstanding business partner of Pythian’s who run a very useful service I think more of you should know about. Rest assured there is nothing “in it” for me or for Pythian for writing this. (Doug, I look forward to hearing you out on whether this post was appropriate or not!)
As background, supply management as a discipline has grown leaps and bounds for managing the quality and cost of parts. I was reminded of this today as I was reading this outstanding analysis by the Boston Consulting Group of Toyota’s supply-management process and its related successes.
Supply management for services is a different matter altogether, and has not really achieved this level of discipline. I will save a blog posting on that subject for another day, as it turns out that the Pythian model actually enables some more advanced supply management methods to apply to infrastructure-management services. But as I’ve already said, this article isn’t about Pythian.
It turns out that there is a way to apply sophisticated supply management techniques to your database licensing costs in quite an efficient, turnkey manner, and that way is simply to outsource this work to Miro. I recommend this to Pythian customers all the time.
Miro has a unique and extremely useful business model: they are consultants, but their subject matter expertise is focused squarely on Oracle licensing. As a result, they know all of the different versions of the OLSA, the different methods by which licenses can be converted from one type to another, and so on. They stay on top of all of the changes so that they can claim the options and opportunities for conversions on the most beneficial terms. They also offer an outstanding service of documenting compliance with Oracle licenses, either in support of a licensing audit by Oracle itself, or simply in support of internal review of software asset licensing.
I first worked with Scott Rosenberg and Eliot Colon in 1998, shortly after Pythian’s founding, when they were at Cintra — back when Cintra was the largest Oracle license reseller on the US Eastern Seaboard. These guys sold so many Oracle licenses that they learned all the tricks. And then, they decided they could start a company that put that knowledge to work not for Oracle Corp. but for the Oracle licensee. Neat idea, no?
Note that they are not alone in taking on this consulting model: Vinnie Mirchandani appears to be able to make a good living doing much the same thing as an independent.
What prompted me to write this note today is that I asked Scott for permission to post his recent Oracle licensing circular to our blog, since it has direct relevance to our open letter to Larry Ellison on AWR licensing, from this summer. Now that I’ve introduced Miro, I’ll write another blog post with their circular so you can have a glance at it. Stay tuned.
5 Responses to “Keeping a Lid on Oracle Licensing Costs while Ensuring Compliance”
Leave a Reply