How can you use analytics to build new projects? In many ways!

This case study example shows you how.

Launching a new automation project is challenging. There is a lot of pressure on your head to get it right and make sure it’s a success. There’s pressure to pick the project that makes the best use of resources. There’s pressure to prove to others that your choice of project is the right one. There’s pressure to demonstrate that the project was a success after it has been up and running for a while.

The problem is that you can’t build a project by guesswork alone. You need data at every single stage of the process.

How do you collect that data?

By using the right software. Insights is our cloud-based collaborative robot monitoring software. It allows you to monitor and analyze your robot’s performance both in real-time and using historical data. It provides you with a reliable method to collect a lot of the data will need to build your new project.

In this article, I’ll show how you can use Insights data throughout the entire process of building a new automation project.

Where does Insights fit into robot deployment?

Insights can be used at every stage of robot deployment! New automation projects use data throughout the three phases:

During Design — This first phase is where you pick your robot application and plan the deployment. Data is most often used here to analyze the existing manual operation of a task, which means you have to record it manually instead of using software. However, you may be able to use Insights data if you have access to a collaborative robot during this phase. That way, you can run tests before you begin deployment as you’ll see in the case study example below.

During Integration — Data can be very useful while you are integrating the robot into your process. In Insights, short-term time periods (e.g. daily view and hourly view) provide an immediate and clear visualization of the effects of any changes you make to the robot’s programming.

During Operation — Insights really comes into its own when you are using it during the Operate phase of robot deployment. Data collected when your robot is running in production mode helps to ensure optimal use of the robot. Insights helps you to spot problems when they occur and allows you to improve the robot’s productivity over time. Data collected at this stage is invaluable for proving the effectiveness of the robot.

Some people only consider the Integrate phase when they think of building a new automation project. However, as will see in the following case study, Insights data can be invaluable in the other two phases as well.

Two case studies: applying Insights to innovate, build and monitor

Let’s take a couple of examples from our Case Study Library to show how Insights can be applied at every stage of a robot deployment.

We’re going to look these two examples:

Continental Automotive Spain — At the time this case study was produced, Insights didn’t exist yet. However, it is a perfect example of the type of new project which can benefit from the data that Insights collects during the Design and Integrate phases of robot deployment.

Walt Machine Inc — By contrast, this case study does use Insights. It’s is a great example of how the software’s notifications are effective during the Operate phase of robot deployment. Although Insights wasn’t available when they first began using robotics in 2016, they have easily integrated it into their process and, by doing so, saved themselves a lot of time.

Case study 1: Continental Automotive Spain

Continental Automotive Spain is always looking for ways to innovate their production processes. In this case study, they were looking for ways to incorporate Industry 4.0 and to improve productivity. Their first collaborative robot project was to incorporate two UR10 robots into their PCB production process for quality testing and machine tending tasks.

Engineer Victor Cantón was chosen to lead the new project, a role which he accepted despite not having any experience using robots. With his solution, they were able to move workers away from non-value-added tasks and reduce the changeover time by 50%, allowing them to convert the line from one product model to another in only 20 minutes.

Here’s how the team could have used Insights data during the Design and Integrate phases of the deployment.

How to use data in the design phase

Data during the Design phase is most useful for exploration and validation. At the time that the project was proposed, the company had already acquired a UR10 robot. This meant that Victor was able to run tests before the application was integrated into the line.

Subscribe to our free daily newsletters!
Please enter your email address to subscribe to ETF Trends' newsletters featuring latest news and educational events.