End2End SCM can go deeper than the just functions
Last month, I was at the IBM Consultants & System Integrators (CSI) conference at Goa, a wonderfully event-managed event where to my utter delight, even verbose senior folks were brutally cut down from their loquaciousness by the time-keeper's flag. I was invited since Enterprise Asset Management (EAM) is one of the domains I head in my portfolio here at SCM practice. IBM, as many of you would know got into EAM in a big way post acquisition of Maximo app from MRO software. But this post is less on EAM and more on a topic I'm thinking and reading up a little bit these days - end2end SCM and more specifically - why should it just remain at a domain level and not be inclusive all the way down at a deeper infra level?
Apart from the EAM session, the other two terminologies that caught my attention were Green IT and Cloud Computing, both splendidly vague terms, if I may add. Green IT these days cover everything from infrastructure streamlining to saving on power consumption (my father would fanatically love that!) to optimize resources of all kinds to monitoring systems in EAM that helps reduce emissions/carbon footprint in any device, whether its a transformer, an central A/C system or a full fledged plant. Cloud computing covers so many things - utility computing, grid computing, virtualization at all levels, I'm not even going there. Sure, there's overlap between the two, but both Green IT & Cloud Computing seem to be evolving on their own terms, though the latter is still more a CIO-level discussion.
Sitting in soaking-wet, monsoon-lashed Goa and listening to all this got me thinking on the applicability of these philosophies in end2end SCM. There's no morass greater than SCM application landscape in any major Fortune-500 or Global-2000 company, the wider the globalization, the more tangled the SCM web is. Unlike the ERP behemoth, what we have is an endless series of best-of-breed apps, legacy bolt-ons and some modules of ERP all performing various components of SCM and not necessarily in the best of talking terms with each other.
At the top of this hierarchy, we have the SCM functions or depatments - Demand Planning, Transportation/Logistics, Warehouse Management, Order Management, Procurement et al. At the next level, we'll have the plethora of apps - an i2 Demand Planning system with a Manugistics network optimization talking to a Red Prarie WMS and a Manhattan on-demand TMS with orders coming with SAP SD is not an atypical case. Add to it special apps for fraud check or RFID integration or route planning, you take the complexity level by another few levels.
Now, if you look at all these departments and their various applications, it doesn't take a wizard to guess that infrastructure also would've been acquired along the lines of "I need my boxes under my desk - every last memory card of it" philosophy - add dev, system test, QA, integration test, production, golden environments...you have just multiplied the box count by 6 times. I am not an expert in virtualization though I understand what's meant by virtualizing at Desktop, Server, Storage & Network levels, but the opporunity to consult on this should be huge. In the infrastructure wasteland of 10% utilized UNIX machines, applying the cloud principles should automatically result in greening and can hopefully create end2end SCM beginning with the lowest layer of the landscape block diagram.
Bringing these three disparate layers - business functions, IT applications and IT infrastructure and starting from the bottom on the philosophy of "sharing perishable & intangible computing power" - btw, that's from Wikipedia - and how that would help in an integrated view of SCM wouldn't be a task for the faint-hearted. We're making some humble steps, will keep you posted based on the direction it takes. In the meantime, would like to hear your views on this as well.


