First, the RPA for the inappropriate deployment process
Such a process comprises Class 2:
The first is a very complex process. RPA planning to do for complex processes will generate high costs. The complexity of the process in the low or sub-process is the best goal early RPA project, companies can then focus on the complex processes in the RPA after maturity, starting from the highest value or framework easy part, gradually increasing the degree of automation of the process.
The second category is constantly changing process. RPA is not suitable to be deployed to the constantly changing system to go, frequent upgrades or changes will lead to the difficulty of maintaining RPA project straight up.
Second, for a certain over-flow automation
RPA is the best perspective on it as an auxiliary tool to complete the operation flow basis, so that manpower more time to complete other tasks. When 70% of the low-value part of the automation, 30% of high-value part of a man-made process flow of a good initial target. Robot fully learn each process may take a long time, should try to project through a series of simple changes, and gradually increase the proportion of process automation.
Third, underestimate the impact brought about by the RPA
RPA will encounter many problems in project start, positioning and delivery. However, there are two issues that might affect the interests of the delay line and the RPA project implementation: how to ignore the line on automated processes and operations by the RPA who robots.
A business-oriented of the RPA Center of Excellence is the best way to enhance the management of the virtual workforce. Start building a center of excellence, to reach a consensus on IT management, training employees to use the robot RPA and continued optimization processes.
Fourth, take the traditional method of RPA
Enterprises usually take too engineered software implementation methods to deploy the RPA, including documents and stage division of low-value, the RPA project usually only takes a few weeks to extend the implementation period of several months.
Most software implementation methods are too RPA for engineering, especially RPA small changes to existing systems and new processes have been archived in the RPA tool. Enterprises should be based on the challenges facing their own, simplifying the traditional implementation methods, by means of a flexible phased implementation RPA.
Fifth, the lack of business case for RPA
Most companies usually do first POC (proof of concept) trial to test whether or RPA RPA can be run as scheduled. But there are still huge differences between the POC and generally successful mass production automation, RPA Board team will not be able to answer basic questions about "how to locate the RPA, has a kind of RPA project cost and return" and so on.
But also need to spend several weeks by POC, complex process automation, enough to carry out a solid opportunity to explore assessment, and accomplish specific business cases during this period.
Sixth, the process of establishing POC for the RPA, lack of resources and experience
RPA a common pitfall in just a day or two of training, the majority of business users can automate a simple process. In practice, however, create a flexible extension of the RPA process skills needed far more than that. Therefore, under normal circumstances, POC need to go through a long process of testing and modifications to be implemented, and even reconstruction. Not stingy to spend on team training and skills transfer support, it is an important factor in the success of the project.
Seven return on investment for RPA expectations too high
Although the existing RPA can automate most of the process, but it does not automate all processes - usually because these processes need to start with a phone call or paper records, or take some customer communication. Therefore, companies often automate a lot of sub-processes, but ignored deliberately enhanced by electronically or OCR functionality and automated technology RPA overall process.
Eight, ignore IT system facilities
The vast majority of the RPA tool, preferably in a virtual desktop environment, through appropriate extension and business continuity set, the operation work. RPA process can be quickly implemented, but IT can not build a sound production facility in such a short time, and thus become a major stumbling block to the implementation of the RPA.
Nine, RPA will not be considered for the business-led, but by IT as the leading
Businesses often believe that RPA is in the early automation system project, thus ignoring the RPA will put the final delivery across the company's business to a virtual staff to handle.
RPA is a successful business-oriented, and IT, networking, security, risk, human resources and other departments have a plan or project in close partnership.
Ten, the RPA as a series of system automation project, rather than the end-to-change projects
If the RPA project, there is no good systematic restructuring and employee relocation program, corporate officers quickly dispersed transferred to do other work, such as services to enhance the focus, or focus on more interesting than the manual tasks automation tasks. This may lead to the expected benefits of the project were not fully realized, the follow-up phase of the project has not been approved.
Original Address: https: //www.uibot.com.cn/news-7-1431.html