I recently sat in some sessions to start to learn about the new C4C, also known as Cloud for Customer. Obviously, my interest was the piece of C4C called Cloud for Service. From everything I can see, this is the newest approach from SAP to handle service.
Previous years, you hear about CRM Service or HANA, this year it’s all about C4C. So, of course I needed to get a little info on it. At first glance, it looks very cool, and I’m flattered to say that many of the features I have built in JaveLLin applications is showing up in C4C. From what I can see, C4C is very good at taking over the notification portion of service, as well as the Field Service portion. The biggest piece I see that is missing from C4C (and I doubt will become part of it any time soon) is the in-house repair portion. Again, this comes down to handling all the deliveries.
One of the pieces that I”m excited about, and plan to exploit is the oData integration. If you’re not technical, it just means that my stuff just needs a Netweaver Gateway service, and it can be called directly from C4C. This means that if you use C4C, you can still use JaveLLin applications. You might not need all the functionality, but since C4C does not cover everything we do, you can get the best of both worlds. Or just use all of our pieces, and get a cheaper version of Cloud for Service 🙂
Thanks for reading,
As always, thanks for reading and don't forget to check out our SAP Service Management Products at my other company JaveLLin Solutions,Mike