The Smart Field Service Prototype powered by SAP FSM and Wechat

In this blog I will introduce a prototype regarding a Smart Field Service prototype recently developed by our team. The aim of this prototype development is to give our local partners a demonstration about how SAP FSM is flexible enough to integrate with popular mobile application framework to achieve a more modern user experience.

SAP FSM is named as VISIONARIES in Gartner Magic Quadrant for Field Service Management.

See the report in Aprial 2019.

And till 2019 Q1, Wechat has more than 1.1 billions active users per month. The Wechat users finds out that more and more of activities in their daily life could be achieved within Wechat itself by "subscription account" and "mini program", without installing any additional mobile application. Wechat has almost become a sort of "mobile application platform" in de facto standard.

So it would be very promising if both could be combined to make customer life easier.

We design such a scenario: suppose a customer has bought an equipment from a given company, and need to finish the equipment installation by a technian some days later.

Traditional way for field service reservation

That customer has to call equipment selling company, discuss with the service agent via the phone, schedule a technian and determine the field service date and time. All of such discussion has to be performed online via phone.

And for the service agent who has picked up the call, he/she has to manually create every record in SAP FSM, such as service calls and activities. It‘s time consuming with poor productivity.

Innovation way for field service reservation

(1) The customers can directly make reservation themselves via self service provided in Wechat. No additional application required.

(2) The self service in Wechat is developed with a frontend web application and a backend proxy server leveraging SAP FSM nodejs SDK. When customers choose the appropriate date time, specify a technician and confirm the reservation, the request is sent to the backend proxy server, which then calls SAP FSM Restful API via nodejs SDK, to create service calls and activities automatically.

In this way, no human service agent is needed any more.

Below is more detail about this demo scenario.

(1) After the customer has bought the equipment, he/she subscribed the official subscription account of the equipment selling company, in our demo it‘s "SAPCX数字创新空间".

Once done, the menus provided by the subscription account is available. Click "预约(Reserve)" to start book a time via self-service way.

Then the web application developed by our team is displayed in Wechat.

"预约地址":the address of customer who currently uses Wechat for booking, which is automatically filled by GPS API call. Manual change is still available.

"联系电话":customer mobile phone number.

"上门时间": the actual time that customer would like to book the field service.

Once service time is determined, the web application will fire a query request to SAP FSM to fetch technicians list who are available for that very booked time.

The available technicians are rendered in Wechat via list format, with each technician‘s name, title, employment length, user ranking etc. Then the customer can choose a technician based on these information.

Once the customer confirms the reservation, our proxy server will call SAP FSM Restful API to create corresponding service calls and activity in the system:

Here below is the created service call in SAP FSM triggered from W echat:

Here below is the created activity in SAP FSM:

In order to let customers can check the appointment anytime after this successful booking, once our web application receives the response from SAP FSM API call, we will push a "reservation confirmation" to Wechat:

Click this notification and customers can review reservation detail in Wechat:

Now a day later, it‘s time for the selected technician to travel to the customer site. Once the technician starts, the customer will receive a "real-time position sharing" initiated by the technician in customer‘s mobile phone:

With the support of location tracking, the customer can have a rough estimation when the technician arrives.

Now let‘s switch to technician perspective for the time being. Once the dispatcher employee presses the "Release Assignments" button on the installation task created by SAP FSM API call in the dispatching dashboard,

The technician will receive a notification message from the SAP FSM application in his phone:

Click the FSM mobile application and the technician can see what exactly should be installed for the current field service:

where do two items (installation service and accessory list) in task view above come from?

Two templates are created in advanced in SAP FSM, tile "Smartforms and Feedback":


The binding relationship between the activity which the technician see in the mobile and the two work items is achieved by an API call to assign the two templates into the created activity in the runtime.

Once technician has finished installation service, in our prototype, a bill will be pushed to customer‘s Wechat application containing detailed price:

The customer can open the bill detail, review it and press the blue button "支付账单(pay the bill)" in the bottom.

Wechat Pay is one of most popular payment method currently used in China. We simply bind a credit card in Wechat and then can perform payment directly using Wechat.

Once the customer pays the bill, a user survey will be sent to the Wechat to collect feedback about this field service experience.

We have developed a web page leveraging Qualtrics survey API. The survey result will be sent back by API to generate corresponding Qualtrics Response for further analysis.

In summary, using our prototype, customers can now perform all necessary steps for a typical field service process purely in Wechat. Neither phone call nor other application is needed. This prototype demonstrates how flexible and powerful SAP FSM Restful API in regard to integration with third party software and how Wechat can be involved to bring an enhanced user experience of SAP FSM.

I have uploaded a video in youtube: https://youtu.be/tscSPtPlPqE

Hope it can inspire you a little bit.

要获取更多Jerry的原创文章,请关注公众号"汪子熙":

原文地址:https://www.cnblogs.com/sap-jerry/p/12232803.html

时间: 2024-10-07 09:40:00

The Smart Field Service Prototype powered by SAP FSM and Wechat的相关文章

Dynamics 365 CRM Connected Field Service 自动发送command

上期降到了怎样部署connected field service(CFS) 我们假设现在IoT 设备是温度监控器, 当温度触发我们之前预设的温度值, IoT会通过IoT Hub 发送IoT Alert到CFS中. 第一次触发, 系统会自动发送reboot的command. 为了有更好的用户体验, 我们需要自动发送command. 自动发送非常简单. 首先,我们需要创建一个workflow 我们的workflow需要在IoT Alert创建的时候触发. 这个workflow需要有以下两步: 1.

Jerry的通过CDS view + Smart Template 开发Fiori应用的blog合集

S4/HANA里有一个新的UI框架叫做Smart template, 配合ABAP后台的CDS view技术,能够让developer以Metadata driven的方式来开发Fiori应用, 这种开发方式几乎不需要或者只需要很少量的JavaScript开发. 下面是我写在SCN上的相关13篇blog的链接: Step by Step to create CDS view through SmartTemplate + WebIDE: https://blogs.sap.com/2016/03

Jerry的Fiori原创文章合集

我曾经于2014年10月到2016年5月工作于SAP CRM Fiori应用的开发团队, 我所在的团队负责下列这8个Fiori应用的维护和持续开发: My Opportunities My Tasks My Appointments My Leads My Notes Simulate Sales Pipeline Track Sales Pipeline 在这不到两年的开发工作里,我在使用SAP UI5的过程中遇到各种各样的问题,我都把它们一一记录了下来.还有一些问题来源于我的好奇心,比如看到

SAP Web Service简介与配置方法

p.MsoNormal { margin: 0pt; margin-bottom: .0001pt; text-align: justify; font-family: Calibri; font-size: 10.5000pt } h1 { margin-top: 17.0000pt; margin-bottom: 16.5000pt; margin-left: 0.0000pt; text-indent: 21.0000pt; page-break-after: avoid; text-al

SAP PA Document List

RE-Real Estate 房地产 RE010-EN-Col95-Real Estate Processes in SAP ERP RE200-EN-Col95-Real Estate Management:Implementation RE300-EN-Col95-Land Use Management in SAP Real Estate Management FICO-Finance & Controlling 财务会计成本控制 TFIN50-EN-Financial Accountin

【转】SAP HANA学习资料大全[非常完善的学习资料汇总]

Check out this SDN blog if you plan to write HANA Certification exam http://scn.sap.com/community/hana-in-memory/blog/2012/08/27/my-experience-on-hana-certification Videos available at HANA Academy http://www.saphana.com/community/resources/hana-acad

Smart template的控件能否当成普通控件来用

我的同事问过我这个问题: 只要弄清楚Smart control的原理,就能回答这个问题. 答案是: smart control可以像普通的控件一样在xml view中被定义和使用,但是必须结合OData annotation,否则没有意义.以Smart control里的Smart field为例,详细原理在我的博客Currency example – how Smart field works里介绍. 概括起来,就是: 1. Smart field本身也是一个控件,更准确的说是一个没有UI输出

SAP成都研究院大卫哥:SAP C4C中国本地化之微信小程序集成

今天的文章来自Wu David,SAP成都研究院C4C开发团队的架构师,在加入团队之前曾经在SAP上海研究院工作,组内同事习惯亲切地称呼他为大卫哥. 大卫哥身高据Jerry目测有1米8以上,是成都C4C开发团队身高最高的几位男同事之一.身体非常结实,是成都SAP篮球队的成员之一.有一次大卫哥坐在自己座位上,一手撑在桌子上认真地看着向他求助的同事电脑上打印的日志,飞机哥张航拍了一张大卫哥的背影,评价道:"从照片里看出了大卫哥发达的背阔肌." 飞机哥张航后来完成了一幅素描,下图左边正在沉思

OPEN(SAP) UI5 学习入门系列之一:扫盲与热身(上)

什么是SAP Fiori? 了解SAP UI5必须要从SAP Fiori开始,两者概念经常被混淆,而两者也确实有着非常紧密的关系. 用过SAP的同学们都对SAP的传统的界面(SAP GUI)表示"呵呵",其实传统的SAP GUI的界面功能还是很强大的,但是对于一个新用户来说,学会使用这套界面就需要花上一两 周的时间,所以SAP入门的第一步就是学会使用SAP GUI.此外,传统的SAP GUI只能在Windows和Mac上使用,对于移动端用户没有直接的解决方案,WEBGUI的体验也非常不