扫描二维码

订阅kaiyun体育官方人口 微信

实施移动应用的框架思考

来源: kaiyun体育官方人口作者:Steven Cheung
2012/2/23 9:57:16
利用移动技术为客户提供更好的服务已经成为企业毋庸置疑的选择,但是如何规划和实施移动应用仍然困扰着企业变革的实践者和决策者。


分享到: 新浪微博 腾讯微博
本文关键字: 移动应用 框架 解决方案

英文原版

The need for company to be equipped with mobility technology to serve their customers is a foregone conclusion.The question is largely how to go about it.

We can rush to develop some exciting mobility technology that wows the customers and be perceived as a leader. But, before you go too far, I would like to share with you a checklist to get a few things in order before you go.

The biggest temptation to jump in before we look is clearly the urge to be a market leader in rolling out the technology. Timing is everything and I could not agree more.What I have presented here are not things that will take a long time to resolve generally, but you need to be mindful of them so as to reduce unnecessary future expenditures.

The framework that I am using today is a basically common sense approach as shown below.



To make the framework a little easier to understand, a sample mobility application called First Notice Of Loss Claims system (FNOL System) is being used. FNOL system on a handheld device allows the claimant of an auto insurance company to file a claim at the time of a car accident. He can take pictures of the accident scene and the damaged parts of the car, collect information from the other party, download the necessary instructions for help during the accident -- road side assistance, order tow truck -- and get hospital information on the handheld device. He can also connect real-time with a representative from the insurance company. He can report the claim by simply (a) scanning the driver license of the other party, (b) upload the pictures he took, (c) fill in a simple form or message the insurance company. Do all this during an interactive session with the insurance company. The claimant can make sure that all the necessary information is collected and the guidance is provided by the carrier. The grid below takes each column of the_chart and provides more details on what the quick checklist is all about.

Column 1: Business Model – What is the Value Proposition and how does it fit in with Long Range Strategy?

Business stakeholder’s view

CXO’s concern

Mission statement-Do you have an overallmobility computing strategyof which the current mobile computing project is a part?

Sample statement:“Provide instant help to customers involved in an automobile accident and make the resources of an entire insurance company virtually accessible by the customers at the critical moment. This is the First Notice of Loss (FNOL) system.”

Mobile Strategy -Is time about time to review and rewrite your existing mobile strategy?

Payback– What is the value proposition and payback?

Value proposition- How does it improve business processes and customer perception? Is it for cost reduction, process improvement, giving power to the users, intermediaries, or for social networking presence?

TCO– What is the Total Cost of Ownership (TCO) for this application on a per capita basis, based on expected adoption?

Investment horizon –What is the life span of this application before a major upgrade is needed?

Mobility Policy– What is the policy for access of enterprise data on personal devices?What governance exists between consumer data vs. enterprise data, who pays for the devices that the sales people are mandated to use and what standards should be used?

Legal liability –Do you understand the legal liability issues around sensitive data, security, and errors in financial transactions?

Designer’s viewBusiness Solution Design Consideration & Extensibility

PoC- Is it a Proof of Concept (POC) or a permanent solution?

Extensibilityto other functional areas - Is the mobile application intended to be a one-off or the foundation for other applications? For example: Is the claim application just the beginning and mobility will be introduced to other functional areas such as sales, distribution models, and underwriting?

User experience --How much emphasis is placed on the quality of user experience?What resources are available to ensure that the application is user friendly and ergonomically sound e.g. usability lab?

Social integration –Is the application purely functional or has a social component to it like Twitter, Facebook. LinkedIn etc.?

Implementer’s view

Rollout Mechanism

Adoption- How do you sustain high adoption rate and stickiness?

Enterprise Users vs. Consumer -- How do you train customers and users? What is the support structure for each class of users?

Track past web traffic metric –What devices do your customers/ agents use, which browsers are the most commonly used and what features do they visit the most?

Global roll-out- Is it a single-country roll-out, regional or international roll-out?

Column 2: ProcessModel –What functionalities do the mobile applications provide to customers, and how?

Business stakeholder’s view

Processes Modeling

What business activitiesare involved in this application? Do you have clearly defined sub-processes both for the mobile application as well as the applications in the back-office supporting the mobile application? For example: Recorder of the phoned-in message about the accident, video storage and retrieval system.

Samples: List the sub-processes for these key activities:

Locate tow trucks, ambulance, police info and emergency road-side assistance.

Take video of accident site, pictures of driver licenses, vehicle and witness

Filing claim @ First Notice of Loss for Auto (Physical Damage/ Personal Injury/ TP Liability)

Track claim status after filing.

Designer’s viewProcesses, Business rules and Workflow

Business Rules and workflow:Can we leverage existing business work flows and business rules currently used in the backend claims system? For example: are there new sets of processes for mobile claim filing and when can we develop them?

Implementer’s view

System functionality delivery

How to automate business processes and turn them intosystem functions?

Audience- Is the application rolled out to non-customers as well?

Speed- Can we do it using Agile methodology? It is rolled out based on features rather than big-bang approach?

Scale- Is a PoC required or can we go straight to full scale implementation?

Scope- Are we putting more information than a handheld device can present in terms of screen real estate and processing speed?

责编:张鹏宇
vsharing 微信扫一扫实时了解行业动态
portalart 微信扫一扫分享本文给好友
著作权声明:kaiyun体育官方人口 文章著作权分属kaiyun体育官方人口 、网友和合作伙伴,部分非原创文章作者信息可能有所缺失,如需补充或修改请与我们联系,工作人员会在1个工作日内配合处理。
畅享
首页
返回
顶部
×
畅享IT
    信息化规划
    IT总包
    供应商选型
    IT监理
    开发维护外包
    评估维权
客服电话
400-698-9918
Baidu
map