Luft Medical Care Co., Ltd.

We utilize RK to assist with the creation of job listings. Among these tasks, the most frequent one is the migration of information between databases. In our company, we maintain separate databases: one for "information management", which compiles customer registration information and job information to form the basis of the job site, and another for "progress management," which tracks the development of job listings. Therefore, when a new customer account is registered, the data in "information management" needs to be migrated to "progress management".

Until now, employees manually performed this migration work about 4-5 times a day. With the introduction of RK, this task can now be performed automatically and more frequently, 14 times a day.

Furthermore, we have automated daily tasks such as aggregating the number of registered facilities, job listings, and accounts, as well as backing up the database, using RK.

We have one creator license and one runner license. I (Mr. Okumura) and the Support Unit Leader (Ms. Niki) use the creator license, and we use a dedicated computer to run the RK automation program with the runner license.

Our site is a new service that started as a project in 2019. It started as an in-house venture, with a project team of just three people. When launching a service from scratch with a limited number of people, the key is, of course, operational efficiency. To achieve this, we began considering the introduction of an RPA/business automation tool.

Around that time, a member from another department in our company introduced us to KEYENCE's RK, which they had found at an exhibition and thought looked promising. After comparing it with other RPAs, we decided to adopt RK due to its expected cost-effectiveness and the support offered.

Yes. In fact, I (Mr. Okumura) had experience using another company's RPA in my previous job. While not as straightforward as RK, I still believed that effectively leveraging RPA brings us closer to a future where virtually every computer-based task can be automated.

In the midst of this, when I actually tried RK, I found it easier to handle than the one I used before, the accuracy of scenario execution was high, and the support was also substantial, so I highly appreciate it.

Yes, I feel the advantages in the following aspects:

1. Ease of use

I believe the most important point in evaluating an RPA is whether the scenario is easy to create or not. RK is very easy to operate and has a plethora of features that reach the right places. For example, selecting commands via drag & drop and rearranging them is very simple and convenient. The frequent upgrades that consistently improve ease of use are also an advantage.

2. High accuracy of scenario execution

I can create a scenario with a method called “app recording” which can record my actions as I operate the computer. Some RPAs have low reproducibility of the recording, leading to unexpected performance issues. However, with RK, I noticed there were fewer such malfunctions, and it maintained a high level of accuracy.

3. Comprehensive support

Above all, the support was very helpful. With "accompanying support", a dedicated expert in RK provides you with personalized one-on-one lessons, allowing you to learn the fundamentals and complete scenarios with guidance. Also, when I ask a question their response is quick and thorough. At the latest, I receive some kind of reply within the day. Moreover, each question is handled by the person who initially performed the onboarding, providing a sense of security that there will be no handoffs.

Thanks to this, I was able to achieve the "automation" that I have struggled to create a successful scenario for. Even if I attempted it previously, the outcome didn't work as I expected and I ended up giving up. Introducing RK changed that.

With automation, the time required for that task has been significantly reduced to nearly zero. For example, the "migration of information between databases" task I mentioned earlier took about 15 minutes each time and was done 4-5 times a day, so it took at least an hour each day. Now, the migration is done automatically, on a set schedule, without human intervention. The frequency of data migration has nearly tripled, and human errors such as forgetting to migrate and input errors have been eliminated, improving the quality of the task itself.

Each of the tasks we automated, including aggregation and backup tasks, did not take much time. However, it required the interruption of other work. Eliminating these interruptions by automation has significantly contributed to smoother task execution. I’ve heard staff members describe it as a lifesaver.

RK is a like a virtual robot that works on my behalf. It's a bit challenging at first, but once mastered, it reliably performs tasks equivalent to the work of multiple people within specified time frames. Its independence from traditional working hours and days has proven crucial.

Our site is a new service that has just been launched. Since we are creating a business from scratch, the operation of various data and necessary items are changing day by day. If we were to make system modifications each time, it would be very costly and require copious amounts of time.

On the other hand, with RK, we can develop quickly and make specification changes on our own, so we decided to use RK instead of overhaul our entire systems.

There is a high possibility that it will happen in 2-3 years. However, even in that case, it doesn't mean that we no longer need RK. There are many other tasks that we want to automate with RK, and as we continue to use it, we believe that we will still come up with ideas for tasks that we want to automate, so we will continue to rely on it.

At this point, if I have 10 tasks I want to accomplish with RK, I've only been able to achieve about 1 or 2 of them. For example, I aim to automate the task of monitoring tens of thousands of registered job listings to ensure compliance with the Employment Security Law and job creation rules as soon as possible. If we can download job information during the night when site traffic is low and automatically check for any problems or omissions, I believe it would greatly reduce the burden on both the server and personnel. By solving these issues one by one, we aim to further improve efficiency. Furthermore, in the future, we are considering creating scenarios that can be utilized in other departments and businesses, such as selecting targets for sales on the internet and listing them and expanding them horizontally.

In fact, I have already told the management team about the benefits of RK many times. As we increase the number of scenarios and our increase in efficiency becomes more visible, I anticipate broader adoption of RK within the company. At that time, we will definitely need KEYENCE's generous support, so I look forward to your continued support.