The million dollar question for organizations when it comes to SAP change management is: “How much does it cost to manage our SAP technical changes?” For many SAP customers, it typically costs approximately a million dollars per year to manage SAP changes. Hard data from our customers and prospects indicates the cost to manage SAP change is usually $150-$300 per change. What does it cost you?
Dan McGrann is the US Sales Director at Rev-Trac
He first joined the company in 2015 to grow Rev-Trac’s partner ecosystem and build relationships with like-minded organizations to creates strategic DevOps initiatives for SAP-using enterprises. Dan has an in-depth understanding of the challenges and opportunities facing today’s SAP IT teams, particularly in SAP change management, cross-platform integration trends and DevOps best practices.
Dan brings to the role more than 20 years’ experience in sales management in enterprise software and IT infrastructure. He works with Rev-Trac’s strategic customers to ensure they maximize the value of their investment in RSC solutions and software partnerships and gain a competitive advantage.
Dan is an avid Philadelphia team sports fan and holds a BA in Management Science from Schippensburg University and an MBA from Drexel University.
Wisdom crafted by Dan McGrann
To massively improve your SAP change management outcomes, automation is critical. Rev-Trac automates the entire SAP change management process, enabling an end-to-end SAP DevOps toolchain.
Customers have been using Rev-Trac – a Revelation Software Concepts solution – for more than 20 years – to safely and efficiently deliver SAP changes for better business outcomes.
Data is the language of the digital age. It is the core of nearly every business decision made, providing insight into every facet of your organization. And it dominates the headlines, with regular stories about data security and privatization, data ownership, big data analytics and so on.
The SAP TechEd conference starts this week and we’re more excited than ever. There are two things in particular we’re looking forward to discussing at TechEd.
These days it’s hard to find companies using SAP where a modern approach to improving SAP change management is not top of mind with business owners or IT leaders.
Just before the recent SAPPHIRE conference, SAP quietly announced the “beta” availability of a new Cloud-based Transport Management System which is supposed to be similar to CTS+. Since it’s still in beta, it’s hard to determine exactly how it will work. However, SAP states that it will support a wide variety of content and many different types of target environments.
Our customers sometimes amaze me – in a good way. Many organizations have been kicking around the agile, DevOps and continuous delivery phrases for some time now, but we haven’t seen very many execute on their plans.
Join the thousands of people that keep up-to-date with Rev-Trac
Join the Rev-Trac newsletter and we'll keep you informed of the new articles, resources and updates.
It’s hard to believe, but the SAP COE has been around for more than 21 years. SAP COE’s started around the same time that Rev-Trac did and it’s safe to say that they began for many of the same reasons. That is – in general – to help SAP customers reduce the cost of operations, provide a required level of governance and continually improve SAP processes.
It’s a bit late for New Year’s resolutions already in the first half of February, but with 10 ½ months of 2018 left, here are three quick questions with corresponding resolutions to help simplify and improve your SAP change management processes
In speaking with SAP IT teams who are successfully pivoting to agile SAP development, one theme continues to stand out. Control of the SAP change and release process needs to move from a single, centralized point of control to multiple, decentralized points of control.
It goes without saying that unplanned SAP production outages are costly. That’s why many SAP customers spend large amounts on ensuring high availability and redundancy. Eliminating single points of failure ensure continuous up time. But those infrastructures, no matter where they exist are still subject to accidental production downtime. Whether on premise or in the cloud, SAP systems are still at risk from poorly managed SAP change activities.
The recent article Ringing Down The Curtain On Change Management Theater by Forrester analyst Charles Betz made me think about the future of SAP change management. What is it going to look like in 3, 5 or 7 years? One thing that is certain is that it won’t look the same as it does today. Over the years, I’ve seen SAP customers go from managing SAP change with spreadsheets, emails and ITSM tickets (and many still do it that way); to ITIL-based, semi-automated processes; and now towards business-driven automated Agile/DevOps practices.
That has proven to be a difficult question to answer accurately because the Solution Manager scope has been expanding over the years to cover many different functional and solution support areas.
One of the best resources to help understand the overall size and scope of Solution Manager is the recently published SAP Solution Manager 7.2 Adoption Framework. This lengthy document describes 40 different functional areas in Solution Manager 7.2. SAP also provides some rough guidelines regarding estimated efforts to implement the functionality. What struck me was the overwhelming amount of effort required when you take a closer look.