The Infosys global supply chain management blog enables leaner supply chains through process and IT related interventions. Discuss the latest trends and solutions across the supply chain management landscape.

« What drives China’s Supply Chain – Quality, Cost, Time or Flexibility | Main | Solution definition..or Requirements Refining..or Both? »

...SAP SRM 7.0 is here to stay, available to Leverage your SRM footprint: “Sign-off the SAP SRM 7.0 Road mapping exercise for an Enterprise” – Part 2

The prelude blog of SRM 7.0 was a fair enough curtain raiser to demonstrate our intentions.
In this blog we will focus on what exactly goes in during the “Road Map exercise”, the length and the breadth of the exercise.
i.              Roadmap Scope Definition
ii.             Questioning the holy cows
iii.            Intent for a BPR (Business Process Re-engineering) initiative, YES / NO
iv.            Identification of an SRM council
v.             Pre-Blue Printing (powered by Workshops)
vi.            Revisiting the Roadmap Scope definition
vii.           Roadmap review and Sign-off
Most of these look repetitive, but believe me, these in itself are a masquerade if not dealt with properly.Lets try and understand what we do in each of these phases and the Exit Criteria for the exercise.
i.             Roadmap Scope Definition
In this step, the consulting partner throws all the gyaan in his basket to the customer on the offerings of the Solution and also analysis of the Spend Analytics report / any such strategy document that led to the birth of the SRM initiative. The customer, at a very high level picks up Enterprise specific areas of interest to narrow down on a rough scope
Exit Criteria: Initial Road map draft
ii.            Questioning the holy cows
It isn’t necessary during the course of scope definition to accept all that’s currently identified as the core business processes to get carried onto the Future state SRM solution that’s in mind. This step gives us an opportunity to look at Questioning the way business processes are carried out currently and also identify those cumbersome wasteful processes that can be eliminated.
Exit Criteria: List of Processes that can go into BPR
iii.           Intent of a BPR
This step gets called, if step 2 reveals a big list of wasteful processes that require an elimination via adoption of Best Practices. This step becomes highly critical for companies that have opted to evaluate a Best of Breed SRM solution tailored on Best Practices to give them the competitive edge.
Exit Criteria: BPR document with an identified list of processes that needs tailoring
i.             Identification of an SRM council
It becomes all the more difficult now to look for the Super User community that actually influences the BPR initiative and drills down to the user community that are going to be impacted with the futuristic changes coming in. It’s a key responsibility of the Customer to identify the SRM council that can join hands with the consulting partner to craft the process and the Transformational roadmap
Exit Criteria: A highly sound SRM Cross-functional SRM Council
ii.            Pre-Blue Printing (powered by Workshops)
Now, we have the team, lets start work and arrive at an acceptable SRM transformational roadmap that will leverage the investments of SRM which would help CPO desk align themselves to the Overall Strategy and Business plan driven by the CEO desk to report meaningful KPI’s vide successfully implemented initiatives. Rest assured, an influential strong team will be able to delivery the ideal pre-blur print that has the Roadmap Scope definition enriched with the identified Transformational initiatives.
Exit Criteria: Pre-blue printing document
iii.           Revisiting the Roadmap Scope definition
Performing a rapid gap analysis will help content consolidation of Brainstormed initiatives, some of which will be knocked off and some will get in and become the final roadmap line items.
Exit Criteria: Finalized Roadmap draft
iv.           Roadmap review and Sign-off
Customer will review the Finalized roadmap draft and suggest modifications / sign-off the initiatives. This will give birth to potential projects and implementation scope to reach the future state adoption of SRM.
Exit Criteria: Signed-off Road-map document
This blog was long, but am sure would have given you a dope of a basic minimum walkthrough of events during a SRM Roadmap exercise.
I would wait to hear from you on similar experiences or a thought on “architecting a more complex result oriented road-map exercise”
In the next blog we will discuss on a selected case study of a customer on what they perceived out of the Roadmap exercise and the next steps towards the SRM journey.
Regards, Tridip

Post a comment

(If you haven't left a comment here before, you may need to be approved by the site owner before your comment will appear. Until then, it won't appear on the entry. Thanks for waiting.)

Please key in the two words you see in the box to validate your identity as an authentic user and reduce spam.

Subscribe to this blog's feed

Follow us on

Blogger Profiles

Infosys on Twitter