Use Caution When Considering RDS Services For SAP Implementations

Gene Cao

I’ve just returned from SAP’s 2013 SAPPhire China user conference; with more than 17,000 attendees, it’s still the largest SAP event on the planet. The vendor has recently launched new offerings, like HANA enterprise cloud and extended ERP solutions for new industries; it has also extended its China strategy by announcing SAP Anywhere, a bundle of cloud-enabled mobile CRM services, which it has just begun piloting here.

At the event, clients presented their feedback on SAP services, particularly rapid deployment solution (RDS) services. Ever since their launch two years ago, SAP has extended RDS services to more than 150 software applications. The RDS concept aims to provide everything out of one box; clients buy a bundle of application and implementation services. RDS services have brought tangible benefits to clients that want to quickly start their SAP journey or begin with pilot implementations before going for a full-scale rollout.

However, RDS does not apply to all SAP application implementations; it primarily depends on the client usage scenario. Forrester believes that RDS will not be an attractive choice in a few instances:

  • Large enterprises using SAP core ERP systems as a mission-critical application. Large enterprises normally make huge investments in these projects. Their primary focus is not on saving time or money; instead, their top priority is ensuring that the project is a complete success and that all functionality is rock-solid: well-developed and thoroughly tested. RDS services, which can cover up to 80% of ERP system functionality, may not be the best choice in this scenario. We’ve seen this happen in China and Southeast Asia time and time again over the past two years.
Read more

SAPPHIRE NOW 2010 – The Quest For Innovation

Holger Kisker

 

 

 

The Name

This year SAPPHIRE officially changed its name and became SAPPHIRE NOW. Why? Different answers from different people. Those that should know said: "The new name stresses the urgency." Urgency for whom, SAP? And will the next SAPPHIRE be named SAPPHIRE THEN? Never change a successful brand.

The Event

Another premiere for SAPPHIRE was the simultaneous show in Orlando, US and Frankfurt, Germany. With 5,000 attendees in Frankfurt, 10,500 in Orlando and 35,000 online participants, this was the biggest SAPPHIRE event ever. I must admit I was concerned going to Frankfurt while everyone in Walldorf desperately tried to escape to Orlando. Who wants to attend a second-hand event? But now I’m a believer. SAP managed to balance the important parts of the show between Orlando and Frankfurt. Keynotes were held simultaneously in both locations via virtual video connection and speakers in both cities. In general I never had the feeling I would miss anything important in Frankfurt simply because it was the smaller event overall. It didn’t make a difference if I couldn’t attend another 400 presentations in Frankfurt or 800 in Orlando from the total of 1,200+ presentations – I had a packed agenda and got all that I expected and needed, including 1:1 meetings with SAP executives like Jim Snabe. The simultaneous, virtual set-up not only helped to save a lot of cost, it created a sense of a bigger virtual community and underlined SAP’s ambitions for more sustainability. To all that traveled intercontinental: Shame on you, next year stay in your home region!

The Stars

Like every show SAPPHIRE 2010 had its stars as well:

Read more