Podcasts > Use Cases > Ep. 088 - The next generation of location-based tracking
Download MP3
Ep. 088
The next generation of location-based tracking
Tom Ruth, VP, Quuppa
Friday, May 14, 2021

In this episode, we discuss the value of location data across a wide range of use cases from tracking hockey team performance to hospital safety. We also explore the tradeoff between battery life range and other factors that must be considered when finding best fit solutions for location tracking. 

 

Tom is the VP of Americas at Quuppa. Quuppa is a leading provider of Real-Time Locating Systems (RTLS), with 2600+ deployments in 55+ countries and over 200 partners worldwide. Quuppa Intelligent Locating System™ is a powerful technology platform for Location Based Services and Applications. It enables real-time tracking of Bluetooth Smart Tags and devices, with accuracy even down to a few centimeters. It is a reliable, versatile, highly customisable, fully scalable and cost efficient solution. quuppa.com

Transcript.

Erik: Welcome to the Industrial IoT Spotlight, your number one spot for insight from industrial IoT thought leaders who are transforming businesses today with your host, Erik Walenza.

Welcome back to the Industrial IoT Spotlight podcast. I'm your host, Erik Walenza, CEO of IoT ONE. And our guest today is Tom Ruth, Vice President of Americas at Quuppa. Quuppa is a powerful technology platform for location based services and applications, that enables real time tracking of Bluetooth smart tags and devices with accuracy down to a few centimeters. In this talk, we discussed the value of location data across a wide range of use cases, from tracking hockey team performance to hospital safety. We also explored the tradeoffs in battery life range, cost and other factors that must be considered when selecting the right location tracking solution.

If you find these conversations valuable, please leave us a comment and a five-star review. And if you'd like to share your company's story or recommend a speaker, please email us at team@IoTone.com. Thank you. Tom, thank you so much for joining us today.

Tom: Thank you, Erik, it's pleasure to be here. And we're very excited to represent Quuppa here on your call. And I'm excited for the next 45 minutes to an hour to discuss IoT and how we're changing the landscape of business in that regard.

Erik: And I'm really looking forward to learn about Quuppa. I mean, this is a company I've known about for many years now and I've really never had a chance to have a deep dive discussion with any of your team. But Tom, before we get into Quuppa, I'd love to learn a bit more about you. I think you've been somehow touching this space for but three decades now, maybe even four decades. When did you first start to touch the topic of IoT?

Tom: Well, actually, I came to IoT through telecom. And so I've been in telecom for just about 30 years, and most of my experience has been in disruptive technologies in that sector. And so my last foray was with BroadSoft. BroadSoft is just recently acquired by Cisco a couple of years back. They made it a core services platform that enabled service providers to disrupt the market by entering and providing innovative services to their end customers, usually for business that is more along the lines of unified communications.

So it was disruptive in that allowed a network provider to enter the market at a 10th of the cost of what the legacy technology-enabled, that was provided by Nortel and Lucent and Nokia and the like. What's kind of fascinating about that is the solution, it was a core technology that required an ecosystem of partners to deliver whether it was we're talking about endpoints, whether there was other network gear that was involved as well as software to make the whole user experience more relevant for the end customer.

That ecosystem approach in selling through channels was a unique challenge. Because in most cases, when you're selling and technology, it's always best to try to have a direct interface with your end customer. And that was one of the challenges that BroadSoft had, but it succeeded, and it was a multibillion company and was acquired by Cisco a few years ago and is now part of the WebEx family.

I happen to know a former colleague who was based in Helsinki, and he was an Italian gentleman who had a football team, I guess, of all the Italian expats in Helsinki. One of his best friends came here to Washington and was in the process of opening up the Quuppa operation here in the Americas, and was looking for somebody who had experience in taking a technology to market in the guys that I just described with selling through end partners developing channels, and starting from the early stages with the early adopter types of partners, taking it to market through the continuum of late adopters, and so forth.

So that's sort of how I ended up at Quuppa. And it was a fascinating story because one of the founders Fabio Belloni explained to me that this is disruptive in a couple of different ways. Quuppa is an RTLS company, that we provide real time location services. And that allows businesses to make informed decisions by knowing where things are, simply stated. I asked Fabio, and our very first meeting, I said, isn't this sort of similar to RFID? And after explaining that it happens through the use of radio frequency technology, he said that sort of our predecessors, our RFID are on steroids, if you will.

So taking it one step at a time, if you really look back, is just to give you a little brief history, that RFID had sort of morphed out of the barcoding space. If you scan a barcode at a point in time, that gives you the information or the identification digitally. RFID is an extension of that allows you to use radio frequency for identification purposes. But what it doesn't do is provide you with location, other than if you can mark the location of where you are at that point in time, where you read that data. And that's not a very practical methodology if you follow what I've just said.

So this allows you to do everything I've just described, plus provide the location of where something is. And the market place itself is somewhat jaded because this type of technology has been around for a while. The marketplace is somewhat jaded about it because as I like to say, once bitten, twice shy, so they proceed with caution whenever they hear that I can accurately provide positioning information of where something is using radio frequency based technologies. So, Quuppa simply stated is delivering on that promise right now today.

Erik: I'd love to get more into what the system looks like in terms of how do you accomplish this and gateways with triangulation or what is the solution there. But before we get into the technology too deep, tell me a bit more about the business. Our audience is coming from different perspectives. Some people will be very familiar already with this space. Some people this might be really their first discussion around the topic. So what is the core value proposition, or what are the types of use cases that you would be typically solving,

Tom: Generally speaking, by providing positioning information that allows you to make informed business decisions of tracking, whether you're tracking people or assets in a location. Our strategy or our direction is to do this in a horizontal fashion. We are a very horizontal technology, in that we're used in all these different verticals, whether that's healthcare, sports, or industry 4.0, which I think we're going to focus most of our focus will be today.

And so being able to provide tracking information of where things are in a space is really the core focus of what our business does. What you do with that information is delivered by our partners and that's how our partners use our technology to go to market. Just to kind of explain a little further about our company, as I mentioned, it uses radio frequencies.

So the founders of our technology came out of Nokia. In fact, this technology was a spinoff from the Nokia Research Center. And it's a mature technology that's been developed since 2005, when Nokia decided that it was going to exit the indoor positioning space, our founders were unable to leave and start this company. So in 2012, that's when we are shipping product in 2013. Shortly thereafter, 500 customers, 2,000 systems, 180 partners, later we are have literally been growing a little bit at a time in a bootstrap fashion through that time. We raised 20 million euro in capital in August of 2020, which was quite a feat in doing that in the middle of COVID is no small order.

Erik: And then I suppose you're very horizontal, so you're working across a range of industries. In terms of the scale of the deployment, is this also highly differentiated or highly diversified? I suppose you have some situations where they're very much spot situations. We have some kind of device that we maybe have three of them and we need to monitor their movement. But I suppose you could also have situations where you might have 10,000 pallets that are moving between suppliers to your warehouse to your manufacturing center to the customers, and you want to make sure that you're not losing those pallets, you know where they are, for example, which could be a much more system wide deployment. Could you give us a couple examples of typical deployment sizes are?

Tom: I'll give you an industrial example. So I'll refer to this example frequently, because it's fascinating in that it was a challenging environment. And as I mentioned earlier, there are some challenges to this type of technology. Some customers that are producing goods and it seems to be a common statement that you would think that in this day and age with digitization methodologies that you would have trouble locating products that you produced, and that seems to be a common thing that we hear about postproduction.

So, asset tracking from post production through the whole logistical supply chain is a real challenge for a lot of businesses, especially if some of these products have a half-life or have an expiration period if they can't be outside for too long, or they have to be in refrigerated environments as an example. You'll find this actually in the steel industry, where oxidization is a factor for things they can't be outside for too long, or it taints or damages the product.

But being able to get products through postproduction, getting them on the trucks, getting them to the end customers, getting the end customers then to recognize that they have taken receipt of the product, and are able to then put it into use their production cycle of whatever they're making, whether it's cars or refrigerators, or what have you, that gets an additional tracking capability of a work in progress.

So one of the things that we're finding in this particular business is that it's more of a logistical play, both not only where we're tracking things globally, but also inside a facility where you have a lot of products that may look the same but are differentiated because of their age, or whatever it is that the core of the product that makes it different. So at the surface, it may look the same, but they have different characteristics, obviously. And so being able to track them, and have an accurate method to do so is often a problem for business.

Erik: And then it sounds like based on our earlier discussion that you were selling primarily through channels now and through maybe system integrators. So would these be then typically part of a larger solution where the system integrators could be either developing some customers software application or using something off the shelf but basically providing a semi customized solution to the customer? Or is it also frequently just plug and play, you have kind of a standard configuration? Maybe you can describe a little bit your tech stack? Are you also providing the software application around this or is this something that's always provided by your integration partners?

Tom: So our go-to market strategy, as I mentioned at the beginning and our core are a bunch of radio physicists. I run the business development side here in the Americas. Our founders are all physicists, and they know how to harness radio frequency technology to provide accurate positioning. The industries that and the use cases for it, and the handshakes and the language in being able to, whether it's healthcare or sports or industry or what have you is not something that we're going to excel at.

So as a go-to market strategy, we realized early on what we're good at not and what we didn't want to endeavor into a vertical that we knew nothing about. So we would let our partners excel at delivering the end solution to the customer and that allows us to focus on designing the technology and producing a good position and allowing our partners to do what they're good at which is taking that position and then adding logic to it, if this, then that types of scenarios that based on position, maybe I need to summon workers that have a certain skillset in the production process.

Maybe I need through a logistical, being able to track things down whenever the delivery truck is waiting to take it away. So we had one partner who had experienced all kinds of problems and challenges in their whole delivery, logistics supply, and just about being able to find things help them excel and reduce cost and deliver products to happier customers.

Erik: Who would be a typical buyer here, decision maker? Are we talking about a factory general manager? Are we talking about corporate level technology to team? I guess the answer here is also going to be at various tremendously, but who would you want to be talking to at a company?

Tom: We don't sell direct, so our partners are the ones that are taking this to the end customer. I will share a funny anecdote, because when people mentioned IoT, they usually mean the IT department gets involved. And I had one production executive who saying, listen, I've got a logistical problem. I don't have an IoT problem. He forced everyone to use this language when presenting the solution. He says, because if you're going to call it IoT, then they're going to start coming in to, my IT departments going to start debating, are we going to use Splunk, are we going to use Tableau to analyze the data? What is the best reengineering the wheel that may have already been created?

So in this case, it was an operations executive. A lot of industrial engineers tend to be the ones that are looking to improve the operations of, if its manufacturing that we're talking about, but those tend to be the actual user buyer.

Erik: And obviously, IT is very critical and becoming even more so, but nonetheless, they're strictly more maintenance organization, so this is often not the role that they are playing at organizations.

Tom: We typically always find ourselves working with them, because there is networking that's involved. And of course, it all has to pass security and that's one of the points that we'll touch on here at some point.

Erik: We've been going through a very challenging 12 months really around the world now. And I'm curious how COVID has impacted Quuppa. Because on the one hand, I think everybody has been a little bit budget shy around new projects. On the other hand, this seems like the type of technology that would actually be very useful when you're having trouble getting people on site, and maybe working with more of a skeleton workforce. So what's been the impact of this kind of situation for you?

Tom: Well, I can't lie and say that it's been great. With challenges always come new opportunities. And so while yes, we have had certain projects in certain market sectors slowed down, as an example, in healthcare, it's been all hands on to deal with this pandemic. And so a lot of operational improvements that we find in the healthcare space certainly got tabled and shelved. We've also have some partners that use our technology in long term care facilities and they were certainly among the most affected.

And the flip side, industry needed to get back to work and a lot of companies came to us saying we've found a way to use your technology because it provides location in real time, that we can do social distancing, and contact tracing for our workers so that we can create a workplace safe work environment. So as a good example, what we will do is provide the location information of the items that we're tracking in a physical space. We’ll provide that information to a software platform that is taking the data to make and we will build business rules around it that will say, if these two individuals dwell too long together at a certain period of time, and they can find what that period is.

And as we learn more during this pandemic, those characteristics changed in terms of some of the distances and some of the dwell times depending on where you are and the type of environment that you're trying to attract people in. And so, you'll also be able to use haptics by having a wearable that may vibrate based on a certain policy that was being broken illegally. If you want to notify the employees, say, you're all too close, you need to disperse. And so you can provide that kind of information back to each employee by providing this logic based approach with the information we're providing that system.

That not only provides the social distancing aspect, but also the historical tracking of where employees are in the workplace, if in fact there is somebody that shows up or tests positive, then you can go back and look historically who they've interacted with, and who may also be at risk.

One of the things that we are very quick to point out, and we had to try to educate all of our channel partners who have developed these types of solutions is that they need to do more with location. But the idea being that if you can solve for one problem, because you've got this infrastructure installed, now you can start solving for other things, like perhaps in a factory environment, you can also create another worker safety application for collision avoidance. Perhaps you can also do some things that will allow you to track assets, the previous example that I was giving earlier. So you could do all of that with one infrastructure. And one of the business challenges that we often find are that people tend to do things in a siloed approach, where they solve one problem with one technology or one solution, and it has one ROI around it.

Erik: We do a lot of work helping companies develop their technology roadmaps. But we always try to differentiate between enablers and efficiency gains. In efficiency gains, you can usually have a very direct business case, which is quite straightforward. But the enablers, there might also be a business case there in terms of some immediate cost reduction or improvement in quality. But often, the real value lies in enabling future use cases.

And it's a bit more challenging there to explain the value proposition because often it can be logically very strong. But if somebody is just looking at their P&L and saying, okay, but I need optics to go down, then okay, you got to have more of a longer conversation around how this is going to enable the organization to be stronger over time, but it's not necessarily going to have a six month payback period.

Tom, I'd love to get now into the technology a bit deeper. One of these projects that we were working on recently, we used a solution, so had the challenge was basically having pallets come into the warehouse, and then wanting to track the location of these around the warehouse. And we use maybe a cumbersome solution it was put RFID on the pallets, and then put UWB ultra-wideband on the forklifts so that whenever a forklift picks up a pallet, it moves it around and you know where the forklift is. Because UWB, you can track location, and then RFID you know what's on that pallet, so you have a reader at UWB or an RFID reader on the forklift that would actually read the pallet. But how would Quuppa compared to that? What would be the infrastructure required for Quuppa to solve this type of challenge?

Tom: The first comment is that ultra-wideband, very, very accurate technology, but it has its constraints and challenges too. The reason the power requirements alone may provide a solution or challenge to the solution. If you're putting this on the fourth truck, so obviously, there's probably a constant power supply. But then there's the tracking of the assets itself.

So in your example, you have two different technologies that are there to handle the identification, and then the associated positioning of one that RFID was actually read. With Quuppa, all the assets can be tracked with an active tag. And similarly, the fork trucks would be tagged as well providing position in real time at all times wherever something is. If the tags that we use are active so they do have the battery requirement on them, the cost that we see of these tags is probably somewhere in the $10-20 range us, all depends on what other sensors that you're placing on them. And again, if you're tracking hundreds of thousands of things, then probably passive RFID might be the better way to go. We do see costs of these tags going down.

But one of the tenants that we find with our technology is that often we are compared frequently against ultra-wideband. Again, while that is a very accurate technology, we are able to do it with a much lower power tag and therefore the cost of the tag is also much lower. So, one of the things that we've seen in other examples is that people were trying to track thousands of things but they had re morphed their business around processes, around the limitations of the technology that they were using, and perhaps the cost of the tags were too high because of the power requirements.

And so they only limited things to pallets instead of items that were on the pallets themselves, when the real need was to be able to track thousands of items on the [inaudible 25:21] factory floor. And so those are the kinds of examples where we find that our technology is a better fit because again, you can solve both problems with one infrastructure. And it's easier to maintain, the battery life is longer, you're not replacing batteries, and so on and so forth, which is a practical challenge in a lot of tracking applications.

Erik: So power, accuracy, what else different types of data capture and latency stability, of course, when you're talking about moving around a factory, for example, you have a lot of metal in there so that can cause some issues with data capture, so what would be the other tradeoffs that you would typically be looking at?

Tom: You asked about the tradeoff, there's a couple of different tradeoffs when we look at radio frequency-based technologies like this. One is if we’re tracking an item that is fairly dynamic, and moving around, the power requirements of the tag is usually the one thing that we're going to excel at because we're using Bluetooth, the power requirements are very low.

In the environment where if you have thousands of things to track, that's going to be a much more cost effective solution than save some of these other technologies. The accuracy that's provided with our methodology is going to be different than other Bluetooth solutions because we're using angle of arrival. And that is one of the things that differentiates us in the marketplace because we're able to provide precision where other solutions do not.

Because of through the school of hard knocks and skin knees, if you will, and learning along the way, we've learned that how to make our solution a little bit more scalable so that we can control the tags and communicate back to them in a way that allows us to change transmission modes based on what zone you're in. So as an example, we're key off of accelerometer data that says, okay, if the accelerometer was triggered, now start transmitting. So we can actually change policies dynamically on these tags that allows us to manage the battery life on them much longer and that, again, allows you to do much more scalable solutions.

And again, you know, to contrast what we do in the marketplace versus a lot of other solution providers, I would suggest that because of our go-to market strategy, we have an open API, we provide the location coordinate information, and allow our partners to deliver the solution. And that doesn't necessarily box us into any one type of solution provider, or any one vertical market.

Erik: So battery life, what would be a typical change cycle?

Tom: It depends because of the application how frequently is that tag going to move. Usually, we can apply a policy that says if we know where something's last known position is, then we don't need to necessarily hear from it. So the tag can go quiet after it sits for a while if it's not in motion. So, a lot of the tags that we are in transmit mode based on the trigger of the accelerometer that's on it and so, it all depends on how frequently that's going to move in space. I'll give you a contrast.

We have hockey players that are wearing these tags that are lasting like a season. Again, based on the policies and the way that I just described that we were able to communicate to the tag, that's pretty good considering that the tag is transmitting at like 30 Hertz. In an industrial environment, we're probably looking at something that's probably much lower than five hertz because you really just don't need that many transmissions on an asset coming from a tag that's fixed to an asset in that example.

If you have a fourth truck that's moving, or an AGV that's moving inside the space, you're probably going to have that transmitting a little bit more frequently. We tend to say anywhere from 1-3-5 years, and again, that's also a function of how big the battery is on the tags. Part of being open allows us to have a tag ecosystem of partners, while we make our own tags, but we, given the specifications to a large variety of tag manufacturers so that they can produce tags that fit a variety of different applications and form factors.

Erik: That’s interesting use case already is tracking hockey players, I suppose this is good for analytics understanding…

Tom: Well, that's a whole fascinating separate conversation. But usually, we try to weave that into the conversation because if you can track a hockey puck or hockey players that are moving at lightning speed on the ice, then we can track just about anything else.

Erik: And then accuracy, I guess, tracking the location about hockey, also, you have to have a pretty high degree. But I believe your colleague mentioned around 10 centimeters, is that an average? Is that a best case scenario? What would be the ranges for accuracy?

Tom: I would say that that's the best case scenario, and that's a function we usually say sub meter in most cases. And certainly, in hockey, we're looking for 10 centimeters, or less of accuracy because of the precision in the measurement of how they're using it, and they actually have a nice environment because it's nice and wide and open. In industrial environments, you have racks that go to the ceiling, and so forth that can cause obstructions and so forth.

Erik: And then the range, so you have a beacon or you have this transmitter or receiver, I guess, set up in the ceiling. And so I guess there's going to be a couple things related to that. One is how many tags per receiver, and then the other is what is the range? How far can a tag move away from the receiver and still transmit data?

Tom: First of all, the throughput of the receivers or the locators that we call them, they're able to receive up to 600 packets per second. I think their performance actually has exceeded that in certain cases.

In terms of how far away the coverage question that you mentioned, the way that this works is that it provides a cone of coverage. The higher I mounted, the more efficiently I cover the space. Similar to lighting, the higher I put a light, the more easily I can illuminate a larger space. And so the way that the technology works is that by having more than one locator receive a transmission that we are calculating the angle of its arrival relative to each locator that's received it, and thus creating from a data perspective, it's the intersection of those perspectives that allows us to have precision.

So by having more than one locator that's receiving that signal, we're able to calculate the position from a variety of different perspectives. And so that's where we get the precision. That solves the problems or mitigates the problems of obstruction. It mitigates the problems of absorption because people in the environment, people with big bags of water, that also can cause a problem when you're trying to calculate position all the time. So while one can see while the other wires are here, in this case will the other one does not or may be blocked or obstructed. So that's part of the solutioning that goes into this so that you can provide accurate position.

Erik: Security and privacy, is this an issue that that you have to address? Or is this more of an issue for whoever is developing the application to make sure that the data is stored and in use in a secure and private manner?

Tom: There's a two-fold question to that. On a sales call, I would normally answer it's the upstream. The ladder example there is the software provider, that is the one that's going to be doing the association of the tag with whatever it is that they're associating with, whether it's a person or a thing. But in reality, there's also the notion of security that happens in transmission itself. There are some enhancements that we're bringing out for secure transmission.

Our locators are secure in that they send the packets back to the positioning engine in an encrypted fashion. So there's security, at least at the fundamental side, but the real security that concerns most people is what happens at the association when that happens at the application layer.

Erik: Tom, I'd love to walk through a few case studies with you, but before we do that, is there anything on the tech stack that we missed that's important to touch on?

Tom: No, I think we covered it in a haphazard way. [inaudible 34:36] I tend to be tangential. But I guess the piece that in terms of we're known for delivering accurate positioning, I guess the main thing that I want you to walk away with that you can have a variety of different tags that you can use on these tags, using a tag ecosystem is again another differentiating point. A lot of other solutions tend to be very proprietary.

From a cost perspective, it also allows you to go find and develop tags that may not only just be providing positioning but may also be providing other IoT information like temperature and other things that you may be trying to measure in the space.

Erik: Yeah, I mean, they’re a couple that maybe we can kind of aim for a bit of a range here, and it doesn't all have to be industry 4.0, I think it'd be interesting to hear some of the different environments that you're employed in?

Tom: So I'll mention the hockey example. So we're used in two different hockey leagues in Europe, and in pursuing another one here in North America and again, that's through a partner. And the reason I like to talk about this is that it's solves multiple solutions for multiple audiences. So naturally, the teams get the IoT or the Moneyball data, the sabermetrics, however you want to refer to it, in terms of understanding the performance of their players.

The fans that are watching the game can also have some additional real time information that's sent to their mobile devices. It's also solving the problems of providing a foundry of different items for the betting houses to wager on who hit the hardest slapshot, who has skated the fastest, who spent the longest time on the ice. And then of course, the teams are correlating that information to understand what's the most effective strategy moving forward. And then last is obviously, the television networks by being able to provide some augmented reality with in identifying the players on the ice, and whether that's through replay, or whether it's actually happening in real time. It's a multifaceted approach.

We are doing is that essentially the same thing there that we are doing an industry where we're tracking for trucks, or AGVs, pallets, and so forth, that are moving around dynamically.

Erik: Just one point on this hockey example, I'm very curious how this business model works. Is this then your partner owns the data, and then they monetize the data by selling it? Because you have you I think you mentioned four or five different stakeholders that all find value in this. So is it your business partner that owns the data? Or is it the Hockey League and then the Hockey League determines who can gain access? Do you know how that works?

Tom: Yeah, you mentioned the Hockey League and obviously, that starts to get into a lot of such situations there in terms of who really owns the data. But yes, it is marketed from our partner to those different audiences, and monetized in a variety of different ways, I'm sure. So we just produce the data, that's all we do. We produce it and send it to them for their analysis.

In the case of the analogy that I'm drawing, whether it's hockey, whether it's animal husbandry, whether it's hospitals, whether it's industry 4.0, we're doing the simple task of providing the information where something is with a timestamp. The things that people are doing with that, and again, I love to tell that story, because it's not just to support the team, it's to support all these other use cases.

In the healthcare as an example, when they implement this in a hospital, they may be trying to do something very simple like doing hand washing compliance, but actually, is not very simple but it's immediate use case that everyone needs to have solved. Where they want to assess to the healthcare worker wash their hands when they walked into a patient's room, or did they go straight to the patient? And if so, is there a corrective action that can be taken?

And whether you're solving for that problem, or whether you're doing baby abduction, if an unauthorized person is now transporting a baby through a door or gets close to the door, should the door lock or not? And so, hospitals are worried about security in that regard. Things like tracking the crash cart, making sure that it's where it should be from a compliance perspective and helping the nursing staff operate more efficiently as they have to maintain and keep that up to date.

So those are all bunch of different use cases as an example that are all facilitated by the same infrastructure. You may have different tags that are transmitting at different levels, different form factors, and so forth. But essentially, we're doing the same thing. We're providing that data to upstream intelligence platform that's making business decisions on the information we're providing.

In industry, we were talking a little bit about the worker safety aspect with COVID and social distancing. I mentioned collision avoidance. There's also mustering for employee evacuation. There's also worker tracking. We have a number of examples where companies are analyzing the metadata of where their workers are in positions around a plant so that they may be able to work more efficiently by staffing in a different fashion and logistical space. That's actually one of the examples that we have.

In the case of another example of worker tracking and collision avoidance, we may have the AGV taking a more secured as route, whenever they see a gaggle of people that are that are congregated at a certain place on the factory floor as an example. So just taking the long way home for the AGV may be the easier way for it to solve that problem, as opposed to immediate notification which is what most people think about, but in the case of collision avoidance.

So then, of course, there's the equipment inventorying, and being able to man down detection and things like that as well as visitor tracking. These are a lot of different examples that we would see just from the security and safety aspect. The operational efficiency piece, where to go early on, I gave an example of where the post production, we had a specific customer that made steel coils, and all the steel coils look the same, but they were all destined for different customers and it was hard to understand which one was for which customer by just looking at them.

And so it would take them literally half an hour to 45 minutes to find locate them. And they realized they were spending an inordinate amount of time trying to track these assets, and as well as manpower because they had to physically send people to try to go find them. And sometimes these coils were stacked X deep against a wall and they had to move the other ones out to get to the one that they were trying to find. And now they were able to find things in less than five minutes.

So that process allowed them to cut their staff a time by like 20%, realizing an immediate return, delivering products at a faster pace to their customers, getting the products there, they had customers that were waiting in the parking lot with trucks, which of course, the meter is running like if the truck is just sitting there and not being used. So in a lot of times, they were being asked to produce rush orders for their customers.

And in this particular case, they had to drop everything, produce the product, and then send the customers all because of the product not being found in a timely fashion. In many cases, it was still on the factory floor, but they had to go back and produce more of it. By putting this platform in just to do location of their assets, they realize that they were able to realize a 30% increase in the number of shipments on a daily basis. And that's real money that almost made the ROI happen in less than two weeks for the entire system.

So kind of an exciting just when you think about, okay, we're going to operate a little bit more efficiently, but what's that really mean? And the company really didn't expect to understand that they would be actually shipping more product out on a daily basis and from a production perspective. Again, they weren't doing production runs or emergency production runs either. So a multifaceted realization just from something that's very simple like tracking and tracing.

Erik: I think this is the one data point that pretty much every organization in the world somehow would find value for, so then it becomes really a question of yeah, going through and say, okay, how do we prioritize and how do we ascribe value to actually knowing the location? And then I suppose that's always for you a big puzzle for your partner's going into an organization and saying, okay, right now you want to track the location of this specific thing. But what else might be interesting here once you have the infrastructure in place? And I imagine pretty quickly, you can put together a laundry list of different use cases large and small that would also somehow be enabled by that?

Tom: One of the things in work in process is the other thing we really haven't talked too much about. In aerospace, as an example, is a strong one where the skillsets, it's still a manual process in many cases. The skillsets of each worker is highly refined to do a certain task, and as well as the tools.

The tools, it's amazing to hear this story and it's universal in the aerospace industry, where they're trying to find tools. And so being able to find the correct tool or the right implement, to repair an aircraft at the time is a huge inefficiency that's in that industry. Again, and we're speaking, whether it's repair, or whether it's manufacturing, those are similar functions. So, the some of the things that we've learned in that specific space is also the security that goes along with that, because we don't necessarily want the information getting into the wrong hands, whether that's industrial competitiveness, or national competitiveness.

Erik: What's around the corner? You're growing organically, which I think is quite normal for a B2B company. I imagine what that means also, is that you have kind of a steady technology development roadmap, what are the areas where you're focusing on improving the specifications, enabling new functionality, what are the priorities that [crosstalk 46:48] next couple of years?

Tom: Based on the size of the company that we are, it's not like that this industry is still in its infancy. And while we may have a great technology that provides accurate positioning, people that are working with us, from a scaling perspective, we really want to be able to help them scale the business much easier.

So making it easier for people to have positioning is really where our focus is going to be, whether that's in the commissioning of our technology of helping people install it easier, it's already a fairly simple process. Again, I'll contrast it to other technologies that may require a level of expertise. If you know how to run cables, then you can certainly learn how to install our technology. Again, making it simpler and things like self-commissioning, that's a panacea in the future.

One of the technologies, though, that I think that's going to really affect this particular business that is not even something that we're involved in manufacturing ourselves, but affects our business would be energy harvesting. And so that alone would bring down the cost of the tags and allow projects to expand beyond the thousands of things that we track in a typical installation to expand beyond that it would get and it goes into that passive RFID tag cost space. So that's something that I look forward to in the future from other tag manufacturers.

Erik: I just had somebody send through a pitch deck on that. I see there is a lot of interest in development work going on there. So it'll be interesting to see what comes out in the next five years or so in that domain. Tom, thank you. I've really enjoyed the conversation. The topic comes up all the time in projects that we're running. And I'm glad that now I understand more about Quuppa and where you’re positioned here. What's the best way for somebody to reach out to you or to your team, if they're interested in learning more?

Tom: Email us at Quuppa.com. They can go to info@quuppa.com or visit our website at quuppa.com. There's a lot of variety of different ways to inquire and to engage us there, whether you are a tag manufacturer or potential tag partner, or whether you are a potential software company that like to use our location data.

Erik: Well, Tom, thanks, really appreciate your time today.

Tom: Erik, thank you. It was a pleasure. I hope I didn't meander too much and it was certainly a pleasure to discuss the industry 4.0 with you.

Erik: Thanks for tuning into another edition of the industrial IoT spotlight. Don't forget to follow us on Twitter at IotoneHQ, and to check out our database of case studies on IoTONE.com. If you have unique insight or a project deployment story to share, we'd love to feature you on a future edition. Write us at erik.walenza@IoTone.com.

Contact us

Let's talk!

* Required
* Required
* Invalid email address
By submitting this form, you agree that IoT ONE may contact you with insights and marketing messaging.
No thanks, I don't want to receive any marketing emails from IoT ONE.
Submit

Thank you for your message!
We will contact you soon.