I hope Kirit Pandit, an industry professional that I really respect – accepts this blog posting as a semi-apology or at least a firm clarification of a comment I made to him recently. My fairly caustic remark was about someone who wrote a book on procurement technology (I’m not naming names or the specific topic here sorry) and I stated that this particular work was much a more of a poorly conceived attempt to further this person’s career along than an authoritative or worthwhile contribution on the subject.
Anyway, I’m working on a research note on top processes in procurement – and as I go through my final edit I have referred to Pandit’s book, “Spend Analysis, the Window Into Strategic Sourcing” for precise language on OLAP and spend cubes. This isn’t the first time I’ve used Pandit’s book as a reference, and I recommend it as good material for anyone who wants a better understanding of spend analysis.
So Kirit, my follow-up comment that the barb was not intended for you was sincere, and here is my public apology to prove it. And to my readers – here’s a disclaimer – Pandit works for Emptoris, and my recommendation of the book should not be confused with an evaluation of Emptoris’ spend analysis product. That bit of work will be published in the upcoming refresh of the magic quadrant for strategic sourcing suites.
Read Complimentary Relevant Research
Predicts 2017: Artificial Intelligence
Artificial intelligence is changing the way in which organizations innovate and communicate their processes, products and services. Practical...
View Relevant Webinars
The Mobile Scenario: Taking Mobility to the Next Level
The definition of "mobile" in the post-app era will involve new interactions such as bots and conversations, new devices such as wearables...
Comments or opinions expressed on this blog are those of the individual contributors only, and do not necessarily represent the views of Gartner, Inc. or its management. Readers may copy and redistribute blog postings on other blogs, or otherwise for private, non-commercial or journalistic purposes, with attribution to Gartner. This content may not be used for any other purposes in any other formats or media. The content on this blog is provided on an "as-is" basis. Gartner shall not be liable for any damages whatsoever arising out of the content or use of this blog.