SAP & ERP Consulting from the Customer Point of View

SAP implementation ROI, SAP architecture, & SAP business solutions

SAP IT Governance – Achieve Business IT Engagement

October 24th, 2011

SAP Business IT Convergence

Business - IT Convergence

Proper SAP project governance is a function of the business in partnership with IT.  With the exception of a few of SAP’s technical applications (like parts of Solution Manager, HANA, etc.) the entire application suite is about business; business transaction processing and business processes. If key business resources are not directly engaged in SAP project governance you may never realize the SAP benefits you expect.

This brings me to the point of what benefits you expect from an SAP implementation?

From what I have seen there are generally 2 broad “buckets” of benefits on SAP projects.  The first “bucket” is focused on consolidating and eliminating systems while the second is all about transactional business execution.  Or, IT benefits and business benefits.

SAP Project Drivers in IT

The first benefit “bucket” is related to pure IT cost reduction with a focus on consolidating and eliminating legacy systems for many of the following reasons:

  • reducing numerous applications’ license costs
  • narrowing technical infrastructure needs
  • simplifying technical architecture
  • reducing system maintenance costs
  • reducing legacy staffing needs
  • standardizing on a single development platform

If your SAP project is more of a pure landscape play, around replacing legacy systems, then SAP project governance would fall more clearly under IT.  However these types of projects usually end up having the business user community demand that all legacy system functionality be meticulously reproduced in SAP.  In the end you will likely achieve some measure of savings but far less than you originally anticipated.  Any expected savings will generally be consumed through mountains of custom coded solutions which will need continual care, maintenance, and feeding after go-live.  These custom coded “solutions” are not supported by your SAP maintenance agreement and can eat you alive in post-production support costs.

SAP Project Drivers in the Business

The second benefit “bucket” is related to business processes and business transaction execution producing results such as:

  • improved cycle times
  • greater process automation
  • inter and intra departmental integration
  • unified reporting data
  • improved inventory management
  • better planning capabilities
  • greater supply chain efficiencies
  • faster, more accurate financial closes and statements
  • better operational decision making tools

As you can guess, the list goes on.  The difference here is the focus is on direct engagement and active participation with the business.  This is the real challenge.  A business partnership in your SAP project requires more change management, greater flexibility, and a clear understanding that some business needs will override IT drivers and IT goals.  The goal of well executed SAP project governance is to achieve measurable benefit –, it is more about delivering business objectives and strategic direction. 

IT Governance of the SAP Enabled Organization

When the SAP enabled IT organization is able to deliver on business objectives and focus on strategic direction their role in the enterprise changes.  This SAP change moves the IT organization from being a mere “service provider” (a very expensive cost center) to a critical “value added” business partner. When the SAP IT department is seen as a “service provider” you quickly encounter budget and cost cutting pressure.  As I have previously noted:

In today’s competitive global economy, filled with international economic instability, no part of the enterprise can afford to move very far from what pays the bills.  If your SAP or IT organization is focused completely on technology solutions you lose sight of what is important to the business.  And what is that?  Customers! Customer retention, acquisition, loyalty, satisfaction, and experience.  Without customers there is no growth or revenue.  Without growth or revenue there is no need for that expensive SAP or IT investment…

Without a clearer focus on customers as well as innovation in the enterprise, or “how business gets done,” the SAP and overall IT organization becomes a very expensive operational support layer.  Without the genuine business focus the organization becomes a commodity to be outsourced (see SAP IT Convergence Beyond Business to IT Alignment).

SAP Governance Includes Business to IT Convergence

The whole area of governance and convergence is very closely related.  For effective governance the business direction and integration must be a key component of all SAP or IT initiatives.  When you have that involvement, over time, and with some effort, convergence happens.  It isn’t automatic but the environment for it to occur begins with direct business engagement. 

If the business isn’t in the SAP co-pilots seat you may be headed for a IT crash landing.

If you’re thinking to yourself this “doesn’t apply to me” then you might want to think again.  A recent IBM study found that many corporate lines of business are beginning to make their own independent technology purchase decisions.  And they are doing this outside of the SAP or IT organization.  Add to that Ray Wang’s recent Harvard Business Review Blog Post about the consumerization of [business] IT (see Integrating Business Stakeholders as Part of SAP IT Convergence) and you have a serious issue to contend with.  As his research noted, “corporate tech spending is up by 17 to 20%… [but] spending by IT departments is flat.. business leaders, not their IT colleagues… are driving purchasing decisions.”

Business decision makers are starting to use their own budgets to make their own IT decisions rather than making the contribution to what they see as a very expensive “service provider.” That integration or “convergence” with the business is more important than ever because in the end they have more influence over your budget than you may realize.

For more information on this topic please see these additional posts:

Related Posts:

Protecting Yourself from SAP Consulting Fraud

October 17th, 2011
SAP fake consultant
SAP fake consultant

One of the most pervasive problems with SAP or any other ERP project is the sheer amount of fraud.  It is so rampant with such huge financial effects in any other area it would be seen as organized crime.  I’ve previously written about SAP consulting screening methods and required skills, but there is one key method to filter through the huge number of frauds–, simple experience verification.

Many organizations that have SAP periodically need experienced consultants to help with specialized requests, requirements, new functionality, or to occasionally backfill employees.  Because contract staffing is not a key portion of their business they turn to staffing firms or recruiters.  Unfortunately too many of the staffing firms and recruiters have only one interest–, to collect a paycheck.  Very few of these recruiters care about how they get that payday so it is up to you as the customer to ensure you are not getting ripped off.  There is no incentive for them to carefully screen candidates–, no background checks, no former project verifications, nothing.  A recruiter’s goal is to get them through the interview and have your organization hand over the cash.  The cheaper the resource they can find (i.e. read “fake”) the fatter their margin if they can convince you to use them.

The consulting fraud in the SAP arena (and ALL of the business application space) is widespread and out of control.  For more background and information on some of my experiences with this you may wish to see some of the following posts:

Just in case you think this is just complaining, take a look at an actual timeline of consulting at a real company where an internal employee periodically posts some of the horror stories they are dealing with; http://sapmesideways.blogspot.com/.  Although the employee at that company does not come out and say they are dealing with frauds, con artists, fakes or “SAP freshers,” I’ve seen this so many times that if that company checked these “con”sultant’s backgrounds I could guarantee a very high percentage of SAP fakes or “freshers.”

Protecting Your Organization from the SAP Fakes and SAP Frauds

If your organization would like something different you can do at least one small thing to protect yourself.  AFTER a staffing or recruiting firm has submitted a candidate demand they include references, from the last 3 projects listed on that consultant’s resume.  The ONLY references I accept are client resources, still at those organizations, and on an e-mail address that is clearly at that organization.  If they cannot provide these then my immediate assumption is they are a fake.  If the staffing firm doesn’t get the message you will not accept fakes then do not do business with them EVER!

The ONLY references I accept are client resources, still at those organizations, and on an e-mail address that is clearly at the organization.

Think about that a minute, even if you miss out on someone who has the actual experience you are looking for, do you really want to pay those kinds of rates for someone who was so uninspiring that no one even remembers them?  What about their consulting skills?  Were they a bump on a log that hid in the background and made little or no contribution to the direction or success of the SAP project?

Step by Step to Find the Real SAP Consultants

If you decide to use a staffing or recruiting firm, make it a hard requirement that they provide ONLY candidates who can provide an e-mail reference STILL EMPLOYED at each of that consultant’s last 3 clients.  This is basic employment verification stuff but few if any of the staffing firms do this unless you insist it is a requirement.  And nothing less than a direct verification from someone who is still at that organization will work because I have seen many “stories” about how they have some other reference or the person left and are now working at “XYZ” company instead.  Would you accept that from a permanent employee candidate?

The next step, AFTER the 3 prior project references still at those companies (on the company e-mail address / domain) is copy that portion of the resume listing that consultant’s experience at that company into an e-mail message to their reference.  Send the message with a notice they used this information on their resume to indicate their experience and you would like to know if they can verify that the candidate’s experience is consistent with what is listed.  If that cannot, or will not, then that is the end of the screen for that person.  I do not bother to waste any time with a phone screen until that verification step is complete.

What are some of your thoughts or suggestions for screening out the fakes, frauds, charlatans and con artists?

Related Posts:

Where Does SAP Offshore Development Make Sense?

October 10th, 2011

SAP Return on Investment or ROI

SAP Offshore Development Cost

If you are capable of providing detailed design specs where there is almost no deviation or thought required then this is a great option.  The instant your SAP design requires a measure of experience and insight to make judgment calls, or to look for data or processing that is not explicitly spelled out in detail, you are headed for huge hidden costs. 

The level of detailed spec design work by SAP functional consultants merely shifts the development time and costs to the higher priced resources where it is “hidden” from TCO and sales quotes.  If you are capable or writing “functional” specs that are really more like technical specs with specific table and fields spelled out in detail, program pseudo-logic defined, every possible alternative anticipated, and no detail left out then SAP offshore development works well.  If you are not prepared for that level of detail and “perfect specs” then you are likely headed for a much larger invoice in change order costs and hidden functional time than you ever anticipated.

Offshore resources are often smart, industrious, and hardworking but the ugly reality no one talks about are the real rates because these resources do NOT have any significant amount of SAP experience.

This is the final post in this series.

A quick “test” for the SAP outsourcing or SAP offshore fit is the nature of the work.  “Commodity” services are a perfect fit for SAP outsourcing or SAP offshore work. 

If the effort involves any type of innovation, business transformation or needs any level of change management then SAP outsourcing or SAP offshore development may be dangerous and it WILL cost you far more than you are led to believe.

SAP Upgrades Might Support SAP Offshore Development

One area I have seen where SAP offshore development work makes sense is with upgrade projects.  Much of the development work there is re-working existing objects where the requirements from previous projects have been well tested and adjusted.  Or, if there are enhancements the gaps are well-known and understood so that the detailed SAP development requirements can be easily defined.  From this standpoint SAP offshore review and adjustment of existing code makes sense.  There is little in the way of experience needed to use the syntax checker and to do the occasional program adjustment.  And other than poor coding which causes performance problems the risk is lower.

SAP Production Support Might Work With SAP Offshore Development

In a fairly stable production environment, where there are not a lot of enhancement or new functionality requests SAP offshore support might work well.  The “fix” requirements are very specific and limited so that these types of small adjustments or corrections work well in an offshore environment.  Even for some of the smaller and less complicated enhancements or improvements SAP offshore support might work well.  However, for more extensive troubleshooting, or very complex requirements, you are likely better with some sort of local or onsite support. 

For a more details see Outsourcing Your SAP Application Support.  This provides some insight and a little framework for understanding the SAP outsourcing or SAP offshore fit.

Conclusion on SAP Offshore Development

Regardless of the hype and sales pitches SAP Off Shore development has far more Total Cost of Ownership than anyone has been led to believe.  There is a place for it but that is rarely in a new project or an extensive rework of complex processing requirements.  While you may not see the costs, the offshore project model will cost you unless you are fully aware of the requirements and hidden costs that are never defined in any of the sales pitches or materials.  Of course they will never tell you SAP offshore development might cost you far more than higher priced local resources in many situations.  If they had that level of integrity you would never engage with them for those services. 

For more information and insight on this topic see IT Outsourcing, Off Shore Support, Cost Cutting and IT Department Changes.  That post provides some additional insight on helping to understand where SAP internal resources should focus as well as where offshore support might make sense.

Related Posts: