Beyond Borders: Building Resilient, High-Performance Global IoT Connectivity

Discover how the SGP.32 ‘IoT’ Remote SIM Provisioning standard is transforming the global IoT connectivity ecosystem. In this on-demand briefing, IoT analyst firm Transforma Insights and connectivity leader Eseye explore the emergence of a critical new function in IoT: the eSIM Orchestrator (eSO).

Join experts Matt Hatton (Transforma Insights), Nick Earle, and Ian Marsden (Eseye) as they unpack insights from their joint Position Paper: “eSIM Orchestration: Driving the Next Wave of IoT Connectivity”. Learn how SGP.32 is simplifying cellular IoT deployments, unlocking new capabilities, and reshaping roles and responsibilities across the connectivity landscape.

 

Hello. Welcome, everyone. Thank you for joining Eseye's Beyond Borders webinar today. I'm Joelle for Eseye, and I will be the host for today's session. In this webinar, we'll be exploring how to build resilient, high performing global IoT connectivity.

The session will be about thirty to forty five minutes, and there'll be a 10 minute Q&A session at the end. Our host for today's session is Anand Gandhi, the SVP of worldwide sales at Eseye, and Jeremy Wood who handles our key accounts. I'm just going to go over a few quick housekeeping bits. Number one, please submit your questions during the webinar via the Q&A section.

Also, the relevant resources can be downloaded, and a video recording of this webinar will be sent out via email after the webinar. So gonna hand over to Anand.

Excellent. Thank you, Joelle.

Anand Gandhi

And, if we go through what we're here to discuss today, as Joelle says, we this webinar is discussing how to build resilience, high performance global IoT connectivity.

Thanks for those who have joined online, and are here as part of the webinar. And for those who are gonna watch their webinar later, we hope you enjoy the webinar. Today, we're gonna discuss what it takes to actually deliver global IoT.

The issues and challenges faced with real world examples of, how and what is needs to address them, and how we support people in addressing those challenges to actually deploy this successfully.

So if we go through the if so we've gone through the agenda quickly.

We're gonna go through some of these hot topics that we're gonna talk about. Again, really, really putting together through real life customer examples. This point is talking about the theory on this. Let's get into what actually works and what has worked for the customers. Do you learn something? A customer success story, and then some tips on resiliency afterwards.

 

Challenges in Achieving Connectivity

So let's get right into it. And the challenge really is, it's all about delivering a hundred percent connectivity or as close to a hundred percent as possible. And there are real challenges to delivering that.

How do you get connectivity from a box, from a single SIM that gives you that connectivity, that allows you to deploy confidently around the world? In our view, in my view, fifty, sixty, seventy percent connectivity or uptime is unacceptable.

Most business cases aren't formed on that. Most business cases are formed on having a hundred percent connectivity of all the devices all the time.

So what do we need to consider? We have a bullet few points here. It's not an exhaustive list, to to by by any means, but these are the key ones that we think are really important. It's the regulatory data data sovereignty issues.

How important is device? Are you designing your own device? Is it a third party device? What do you need to take into account for the device?

eSIM and single SKU. There's so many words and buzzwords going on around that in the industry at the moment. Let's talk about that a little bit, see where that's been applied in real in the real world.

Radio access types. What is the right connectivity for you and your project?

Does this new SGP.32 make sense for you? Does RSP work for you?

I are you making something that is an industry issue your problem by trying to adopt it, or do you need another way of solving that?

Do customers need to become the experts in this themselves?

Do you have to have a team which is, device experts? Do you have to have a team of connectivity experts? Or is there another way of doing it? And then really, one of the key things is post deployment.

It's not about day one. It's not about it working straight away. It's, we have to make that happen. That should be a given. It's the it's what happens on day ten, one hundred, one thousand, two thousand, depending on the lifetime of your device.

So let's take those points individually, and and have a talk through them. So, really, when it comes down to delivering that close to a hundred percent uptime as possible, we have to make sure that you're prepared to do what it takes is necessary to deliver that. And does your use case actually deliver to those that need those kind of statistics that come out of it?

 

Importance of Connectivity for Business

Jeremy has a couple of examples, and I'll ask him to talk through of where this has been actually a necessity from day one and how we've helped customers go in and do that.

Jeremy Wood

Yeah. Thanks, Anand. So, yeah, we're talking about, you know, delivering a hundred percent connectivity and how important that is, for your business case, to me, it boils down to to two things effectively.

The first is revenue.

So, you know, if your connectivity solution is only delivering you eighty percent, for example, you know, what is the cost to you as a business? Or, you know, what what's the saving potentially that that could be made by getting that extra twenty percent? So, you know, if we look at payment terminal providers, a really good example, you know, you can draw a straight line between, you know, eight percentage increase and and the revenue.

If they're only getting eighty percent connectivity, you know, that's approximately five hours a day that they're not able to trade. And and, obviously, if a payment terminal, whether it's in vending, parking meters, EV charges, what have you, you know, if you can't take revenue for five hours out of the day, then that's potentially gonna cost you. And, of course, over the course of the year, that's seventy five days that you're not receiving any money for that device. Absolutely. You can see that that that's very quickly gonna be something that's gonna cost you cost you the, money.

Jeremy, you have a health care customer as well, don't you? And that's really important there. That's close to a hundred percent as possible.

Yeah. No. I mean, it it's the the the criticality of certain use cases. So, yeah, health care is really, really important, whether whether it's, voice, devices that obviously operate from telehealth or just basic, patient telemetry.

Obviously You mean remote remote patient monitoring, like blood pressure?

Yeah.

Absolutely. Yeah. And I think with the the the second example I would give there for a particular health care provider is the scalability, of your solution. So you can understand it.

If you've got ten devices out in the field, if you've got eight percent connectivity rates amongst them, that's one device that's out of order. You know, you might spend a few minutes trying to sort out on a daily basis. If you're rolling out tens of thousands of devices, on a monthly basis, as this particular provider is doing in the US today, you can quite easily see how that is going to suddenly become somebody's job if twenty percent of those tens of thousands of devices Yeah. Aren't doing anything.

So one of the examples where we helped as a business was that SI have a particular product called SmartConnect.

Mhmm.

So this is a piece of software that sits on the device itself, and it handles all the heavy lifting of the, the actual connectivity logic.

So, you know, how fast it connects, which networks it connects to. And, you know, the really interesting thing about this is because we obviously we we engaged with them before they developed the SmartConnect enabled product, and afterwards, we've got big enough data set out there in the field today, to actually see the metrics, and we we have seen them. They're really good, that by moving to Smart Connect, they've seen a tenfold decrease in the number of, support tickets generated from those devices. So you can see that that's really helped them that will enable them to to to really scale that business.

Scale and confidence. And I think that in that example as well, this provider gets paid per reading. Mhmm. And so they're they're they're very close to that hundred percent uptime on those device. It's had a massive revenue impact to that customer and his financial Absolutely. Allowing them to go to that next phase of growth, the new round of funding, etcetera. So it's quite exciting what they're doing there.

 

Navigating Roaming Regulations

When you start talking global, one of the key things that comes up when you're talking about cellular connectivity is the the roaming regulations that are coming out. So you'll see in certain areas and places around the world, Brazil, Turkey, China, India, etcetera, where they have permanent roaming regulations, especially things like the Middle East, etcetera.

And these are are really difficult to navigate around when you're not looking at a globalized solution.

What you have to be able to do is, in these circumstances, be able to localize the SIM to comply with local regulations. Now it's this is key for anybody who's deploying this in any serious way. You have to have globally compliant, connectivity.

Otherwise, your devices can be kicked off. You've got some exposure there. You've got customer satisfaction issues. You've got so many organizational things that can be happening if you're not regulatory compliant.

And so you have to try and get this mix of using localized and roaming solutions all at the same time as a kind of a matrix to make sure you are, comply from a regulatory point of view to deliver that hundred percent uptime. And this is all driven by a single SKU, which we'll come down to. The other side of that is data sovereignty issues. And, again, I'm gonna bring Jeremy in here.

He's got an example of a customer that you all know probably, but I know that you you you may not have heard the example what Jeremy's gonna talk to talk about when we help them get into a new market.

Data Sovereignty and Compliance

Yeah. No. Thanks. And, yeah, obviously, that particular brand was, Costa Express or Costa Coffee, as they now are.

So their problem was that they wanted to open up their their their market to to to to China. So they wanted to put devices into the Chinese market.

And, of course, one of the challenges they faced with, such a plan was the fact that all the data within China needs to stay within the data, or be offloaded within China for for compliance reasons.

So, you know, it was a simple fix.

We've got a large network of an MPLS network of data centers.

So the solution was to, to obviously route all of their traffic, locally onto the Chinese data center that we operate.

We also split the traffic. So the telemetry came back to the UK so they could bring the telemetry data back, but keep all the sensitive data in China as well. So Absolutely.

Yeah. And that that was quite an interesting side effect because, obviously, during the initial phases, as part of the the the testing, what we found was and the business model of, cost within China is very different to how it operates in the UK. Was if you've used a cost for express machine in the UK, you will know that you obviously you select your coffee, you then it, you then go and pay for it at a manned station.

Now in China, what they wanted to do was use, a a remote payment system. So not necessarily a point of sale terminal, but it was all done with QR codes. I think it was Alipay was the name of the company, whereby you scan a QR code, and all of the transaction is done via the mobile phone. Obviously, it then sends a signal back through the payment system back to the device to say, okay.

They've paid, and they can obviously dispense the drink. Now what we found early on was because that whole, process was being bounced between China back to the UK or indeed of Germany. There was a a, you know, another data center that we're using. But, of course, you know, there's four different parts to this process.

And what we're finding was that the latency with, with that process, was causing it to be taking quite an uncomfortable amount of time. And, of course, what happened was that, you know, if people didn't see that go through in in a small number of seconds, they would tend to walk away.

So by routing all that traffic to TriNet, we vastly reduced the latency down to what we you know, with a much, much more faster rate on staff.

Excellent. So it's all about the customer. It's not about just about data sovereignty. You have to keep this sensitive data for GDPR purposes, for security purposes within region.

The the other side of that from from a technical point of view is we get able to provide really low latency solutions for customers as well. Now that has an impact when you're talking about these high data amounts, video application, that are coming and being more much more prevalent nowadays. But this brings brings us to the next point. IoT kind of starts and ends with the device. You shouldn't really take the or not even take the risk. You shouldn't overlook how important this is.

 

Device Optimization for Global Deployment

At Eseye, we have a device background.

We have a, hardware device team internally. But we work with all our customers to optimize their devices, test and optimize their devices for global deployment, from our from initial engagement and onwards. We do this because we without having that understanding about the device, how does it perform in different areas, locations?

How do you then scale it confidently? How are you confident to make sure you don't have to do visits to the devices afterwards through the field, which can be costly?

So we work with all our customers. One of the examples here is a construction equipment manufacturing company, a monitoring company that we work with. We spent months working with them, optimizing how the module and the SIM work together. The firmware on the module is optimized to make sure it can take advantage of the technologies that are available today, multi IMSI technologies, eUICC, etcetera, etcetera, etcetera.

So when they deployed, and they these guys deploy in tens of thousands per month. When they deploy the device into probably what is now sixty, seventy countries around the world, they can be confident that the device is going to work, and they can be confident that it's gonna connect. So, really, the importance of device shouldn't be overlooked. Again, one I'm gonna bring Jeremy in, who's got some examples of this apart from the construction company that we work with as well.

Yeah. Thanks, Anand. Yeah. I mean, obviously, the the onboarding of devices is really key, in the early phases of sort of rollouts. You know? In a in a lot of cases, it it can make or break the deployment success, of a new device.

We've seen that canvas times before.

But, also, you know, the there's the companies that come to us because they put a device out into the market, and, you know, it's not necessarily giving us giving them that hundred percent uptime that, that the Well, basically, the projects fade.

They're chasing.

Yeah. Effectively. So, you know, there there's a really good example. In the UK, one of the major, EV charging infrastructure, you'll see them on various different sites, out and about in the world, in the UK.

So they came to us. They had a device already. They had a network. They were well established.

So the engagement started because the the SIM cards that were being provided as part of that solution weren't necessarily giving them the uptime. So, obviously, we began that. We saw some improvement. But what we're finding was that the device itself, the the the cellular router, that was provided as part of this EV charging equipment wasn't quite up to scratch. You know? It was not necessarily, the most graceful when it came to, you know, stable connectivity.

Secondly, it was sending data to places that they didn't necessarily want the data to be sent to, and they couldn't really do a great deal about it. Now, you know, the solution that SI offered to them and offers to them today, is our cellular head router.

So that's a product that, that Eseye offer, as a potential solution for these types of use cases.

It's highly configurable. It's been built from the ground up with the multi network AnyNet SIM card, in mind. And, you know, today, we are at the point at which we are reaching pretty much ninety nine point nine percent connectivity with these cars.

And that's that's an absolutely fantastic statistic. Again, this is all about revenue to them. The higher uptime they get, the more money they get. Yeah. And so we've we've worked with them to optimize not only the IoT estate, but optimize their revenue from these machines that they're managing as well. Yeah. One of the other things that SI do in this area, we do it with all our customers, is something called device validation.

We run devices through a set of set tests, against performance and replicate real world scenarios. It gets kicked off at last. It powers down, where we have to we have to switch then rotate the IMSI's, and profiles in that device to something else to maintain that uptime. How does the device react and perform in all these ways?

At the end of that, testing period, we give the customer full report, twenty page report, about how the device has performed with any advisory, notes, etcetera. It's like an MOT, really. Like, with the advisory notes that come across it, what they need to do to actually optimize that device. Again, it's about having that confidence before you deploy.

Then that's it. And it's still one of the biggest things that you can do to make your IoT project successful. We all know that pretty much most IoT projects, seventy percent of projects of IoT projects fail, and that is down to the device.

 

Advancements in eSIM Technology

And that brings us on to the next point, really, eSIM and single SKU. Now people are used to having plastics plastic SIMs out there from their their their suppliers, and they have them all in their iPhones or whatever phone you use, and it's a single single, profile. With the eSIM, you're able to put multiple profiles where you've been able to embed the SIM into a device.

This has allowed us to, over the last fifteen years, actually, develop a technology called Multi IMSI, which some of you may be aware of.

And then also on top of that, layer eUICC.

eUICC is a way of getting profiles into the SIN remotely, as well as OTA technologies.

So this allows customers then to actually deploy the single SIM or a single SKU, as an as as a example from our construction manufacturer that's out there. They they're able to deploy create a single device with a single SIM in it, deploy it anywhere in the world, and have it connect to work first time.

Choosing the Right Radio Access Technology

And that comes to the next point. This is, around radio access time. This is really prevalent at the moment. We see a lot of customers, looking at their use cases and trying to choose which rack type that they need to or radio access type that they need to go to market with. You can see them out there. There's 3G, 4G, 5G, 5G SA, NB IoT, CAT M1, etcetera, etcetera, etcetera. Now selecting that right that, technology is absolutely key.

We've seen many customers out there at the moment who are, it's completely dependent on their use case, but they're deploying on things like CAT M1 and NB IoT because of the low power, low bandwidth, or low data requirements that they have. But you have to take into account that these technologies, NB IoT, CAT M1 in particular, have not been deployed ubiquitously across the world. And even in countries, they might not be available in certain areas.

So, you have to be really careful when selecting the right RAT type.

5G is something that's coming prevalent as we move through, into, the rollouts adapt from the MNOs, allowing much higher data volumes to be said, lower latency applications to be put on board and everything like that. So, with video applications, with much more data rich applications, you've got those. But when it comes down to CAT one and MBIT, if you're looking to deploy a product globally, you have to try and figure out whether that's the right one for your use case. We've seen a trend recently with customers who had deployed previously on NB IoT and CAT M1, actually creating their second generation or next generation of devices using something with CAT1 BIZ, which is far more ubiquitous to be available around the world. It's because it's based on the 4G spectrum, rather than, NB IoT.

So, we're seeing a lot of sort of people in that decision making process now, we would ask you to really take that into account when you're trying to figure out what you want to do, where you want to deploy, what your use case is. And if need be, speak to your partner about it. Speak to us about it. We've got real world examples. We can tell you where it should where it's claimed to have coverage and where we're seeing there's no coverage. We work with our customers and our partners in that specific way to make sure they can deploy confidently.

 

Understanding eSIM and Orchestration

When we talk about the next point, there's a big buzzword in the industry at the moment around SGP.32 and RSP.

An RSP or eSIM orchestration, it is what is it? It's confusing to a lot of people, but what's it actually deploy? What's it actually deliver?

We have, eSIM and eSIM orchestration is about a set of technologies that come together that allow you to put profiles onto an embedded SIM within a device. It's that ecosystem of technology that you need.

SGP.32 is one way of taking and putting, a profile onto a SIM. There's SGP.02, then there's SGP.22, etcetera, etcetera, etcetera.

In the end, we don't believe that that's the customer's problem. You should be partnering with someone who understands this technology and basically provides you with a service that allows you to deploy your devices as you need. However, if you do want to have some control about what profiles are being used, etcetera, we will work with you to scope that, and understand how you can do that in this SGP.32 world. By the way, SGP.32 isn't deployed yet as a standard.

We're expecting that early next year. And so this is a moving, target at the moment. And so we'll really have that come to fruition over the next six to eight months, ten months kind of time frame. But we welcome your your any any questions on that.

We look forward to working with our customers on that.

 

The Importance of Partnering for Expertise

And this comes to the next point. Customers think they need to be technical experts. In some some cases, they are. They've done this all themselves. They've worked on that. They've got a team of hardware experts. They've got a team of telco experts.

But should they be that? Do they need to be that? Should you be looking at that, or should you be working on what is your core business?

It's really about finding the right people to work with to either, add to complement the skill set that you've got internally or partner that you can trust to deliver around the world your requirements as you move forward. So it's about, do you want to do this in house? What's the cost of doing that? To the balance of, is there a partner who can do some of this stuff for you and help you get there quicker?

Jeremy's got an example of where we've done this for customers before. So, Jeremy, this is a quite a quite a key one, what we've done.

Yeah. No. Thanks. And and just to your point is do your customers need to be experts?

So they a lot of our customers do have expertise. They have hardware engineers. They have firmware engineers. But what they sometimes don't necessarily have is that really deep knowledge of cellular connectivity in particular.

So, you know, one of our potential services the, that our technical consultants can deliver is really focused on filling that particular gap, complementing what the good work of, our customers, the good work that our customers are doing rather than displacing it. So, you know, one example of that is, Shell. So Shell Recharge, again, they operate a a large network, pan European network of e g PB chargers.

Now the challenge that they had was they have multiple different device types that they operate. Now, you know, they might take them for four or five different companies, rather than just one individual device that they've designed themselves. And, you know, what we found early on, is that all of these device types often have completely different comms modules, completely different from how they behave when they're connecting to a network or not connecting to a network.

And, of course, you know, you look at a deeper level, you know, a lot of them have completely different firmware versions, even down to the modem modules. And, you know, all of this can affect how a device behaves.

And, of course, what were they were seeing is, you know, if they had an issue, you know, they got a phone, decided it was having a day off one day, how quickly or, you know, which one of those device types tended to recover faster than than the others, and you could spot trends.

So, you know, it was kind of getting to the point where it was difficult to manage.

 

Case Study: Shell's Technical Consultancy

So they engaged with Eseye, on our technical consultancy service. So, effectively, on demand, access to access and mainly to, to, but not limited to, the device validation process.

So as part of their onboarding process, we slotted in one of our technical consultants that as they were putting it through their paces in terms of, obviously, how it connects to the back end, how it integrates with their systems, Side by side with them, we'd be running that device validation process. And we'd be doing this on, you know, not just the device firmware, but this is the individual modem firmware version we've done it on. And, obviously, in life, not just as part of that initial setup process, we were revisiting that every time a new version of firmware came out so that we could make sure that we could deliver them really consistent service across their entire state.

And this went to their scalability. So it actually allowed them to scale a lot quicker and a lot more confidently when they were deploying. Now Shell deploys not only across Europe and the US now as well. Yeah.

And we and we are still working with them on new devices that are coming through to make sure they're optimized for the connectivity. And as Jeremy was pointing out, it's not just about when they deploy initially and getting it into the field. It's about day ten. It's about day one hundred.

 

Post-Deployment Optimization Strategies

It's post deployment optimization.

And that's, that's the key here. Yes. We have to do all this stuff and this work and this this complexity upfront, but you also have to manage that complexity when you come to the back end as well. So when we look at the back end in which after you've deployed these devices, and deployments can take a number of years, so you still maybe it may be a four or five year deployment if it's around the world. But you've got to, sort of, manage and maintain the estate from devices from day one of that deployment and onwards.

It really is, key to work with a partner who can give you that global support around the world, who understands the regulatory issues around the world, helps you access new markets, has a help desk that can, you can pick up and call whatever day, at the time, or night, wherever that device is, who who is at hand, who understands your device that can help you and your customers get the experience that you want and fix them as soon as possible.

The Role of Configurable SIMs in Global IoT

So that is absolutely key. And then one of the main things around that is deploying a SIM, an eSIM, a partner that has a configurable SIM. It's not about what the config is on day one. It could change. This this this whole ecosystem, the the connectivity landscape changes quite often around the world. You have to be able to configure that SIM post deployment to optimize with what's going on.

Just as we as we and I'm gonna come to an example of how we're doing that and where where we've done that before.

So really, as a as a recap, is delivering global IoT hard? Yes. There's so many different, aspects that you have to take into account. Just not just what we've mentioned here. There are other things as well. But when we go through all these these things, can it be made easy?

And it can be made easy when you work with the right partner.

You're always gonna have to explain me to say that, but it is true. We've done this since we've been doing this since two thousand and seven, and it's not just about the sin. We have four areas of our business that we've been developing since two thousand and seven to be able to deploy global IoT. We start off with the SIM. We talked about the Multi IMSI SIM, the eUICC SIM.

It's compliant to the standards that's coming out. We've got a multi MD bootstrap. We can automatically switch between the profiles. We can update it over the air.

All these things go to providing that service and that hundred percent uptime connectivity, and it's not just that.

We're backed up by something called what we've been putting in place over this time, the AnyNet Federation, which is the largest federated connectivity, partner federation of connectivity partners in the world. We have twenty five partners around the world. We're able to use those profiles and the roaming profiles of, not only just in localised way, but in the roaming profiles of those those network providers as well, given us access to over eight hundred networks around the world. So the solution then becomes one of roaming and localization to actually comply with all those regulatory issues that you see around.

The global network that sits underneath it, the MPLS, we call it our MPLS. We have fifteen data centers around the world. It has resiliency built into it. Each one fails over somewhere else should something happen.

You have multiple paths to each of these operators that are there. And this leads to, low latency applications, data sovereignty, capabilities, etcetera, as you start deploying globally. But when you look at it, it's about deploying the technology stack. We are able to have deep integrations into the, MNOs that we work with, to give that core network, integration.

We can do billing. We've got service orchestration, and we have a portal. We have one platform where you can manage all this from. It's about simplicity of operation. It's about making it easy for you guys and our customers. And we deliver this as a managed service, all underpinned by eSIM orchestration, which we work with you on, to make sure the rules that are put in place, the automated rules to make sure the the the SIM and the connectivity stake configured to how you want it remains in place for you.

Amazon's First-Time Delivery Challenge

So, really, when we look about when we look about how we deliver this and what we're going on about, we wanna put this into context from, one of our our main customers, Amazon. A lot of you, know of Amazon, but what you may not know of Amazon is they have, a key metric of theirs is how they complete first time deliveries.

And a failed delivery is a of that from Amazon cost them an absolute fortune because they have to take the the parcel back to the depot, has to go through the internal logistics process, get resent to a driver who sends it back, and tries to deliver it again. So every missed delivery cost them quite a lot of money.

hen deploying their solution, which is a door access control. So if you're seeing your Amazon driver, you you see you may have seen it here. In buildings of, multiple occupancies, so apartment blocks or office blocks or things like that, the delivery driver doesn't actually have to ring the doorbell of the piece people they're actually, delivering to. They have an app, which is integrated into the door access system that allows the Amazon driver access for the specific time that they're actually there.

So, they developed a device that does that and then and integrates the store access systems. But they faced fragmented carrier performance, latency issues, and they didn't have somebody that could that that could actually be, ubiquitous and scalable. So they started off deploying with someone else, and then the project wasn't working. They came to Eseye.

We worked with them on the device side of things. Again, we talked about device validation and how we move forward in doing that. We worked with them for a number of months optimizing the firmware for the device that they could then deploy, not only in their key market, you know, main market is US, but then they could deploy globally around the world. And they're in, in other countries now all around the world.

We've moved to an embedded SIEM, to give them access to, our recent solution with the multi-network switching, with the localization, with the compliancy, we are now as close we are increasing their uptime because we're able to to reconfigure the SIM dynamically over the air, both from, eUICC point of view and OTA transfers of of profiles.

And so they're now able to deploy a single, scalable product with, that high level of availability globally. And then what we do once it's deployed into the regions, we optimize for the region post deployment. So they can get up and running quickly, get into into field, and optimize them consistently.

Therefore, they're getting the benefits, getting the revenue in, increasing the revenue, reducing cost of non-delivery.

So we've seen consistent improvement across the board, and we're still doing that in consistent improvement as we work with them today. We've been working with them now for about four years, on this project.

They've now expanded into, eight countries across three continents, and they're doing it confidently.

It's now when the market is ready, not when the technology is ready. When are they ready to enter the market, they go into the market. And then even at the point where now their door access system, not only is it, become a global standard, they're now thinking of how other people can use such technology to get access as well.

Tips for Achieving Resilient Connectivity

So when we think about it, we have four tips for resilient connectivity.

We've reviewed some of the challenges and we've discussed some real life customer examples, how SIs help people overcome them.

In the end, highly resilient connectivity is achievable. It is complex, but it can be made easy. But you have to follow some steps. Find the right partner.

We believe it's us. There may be others available. Who knows? But we believe it's us.

We have the right approach, but don't ever underestimate working on your device from the start.

Deploy a global solution from day one, and then work on optimizing and making day two, day ten, day one hundred operations smooth and reliable, and continual optimization of your connectivity as you go through the lifetime of your product.

We work with you across all of those factors to help you deliver your global IoT.

That's kind of the end of the presentation part of the webinar.

I know there are some people online, but if there are any questions, we welcome any questions. Yeah.

So we have time for a few questions. And just a reminder to participants, you you can submit questions via the q and a button, and we'll answer them. So the first one is, what would you say is the number one thing that you have to get right at the very early stages of a global IoT deployment?

Jeremy, do you wanna say one or two?

Jeremy wood

Yeah. No. Absolutely. I'll take that.

I would say e device, you know, how how it how it works, how it operates, how it connects to networks because once they once once that product is out there in the marketplace, it's very difficult to if it's even possible at all to obviously change that firmware. So I would certainly say that that that that's high up my list. What about you, Lance?

Finding the Right Partnership for IoT Projects

I'd say find the right partner.

You're not gonna deliver this yourself. But in reality, it is. If you you're not gonna be able to deliver this yourself. You have to find a partner that, is willing to work with you in the way you work, who's willing to understand and accept your business case, to optimize it and and not leave you in the lurch on halfway through a project with it. Here's a SIM card. See you later.

Cool. And the next question is, what kind of KPIs should businesses consider when measuring that success of a global IoT roll rollout?

That's an interesting one because the business should have their own KPIs. For example, in in EV charging, the the the key status CSR. Yeah. Charge success rate.

For our our customer in health care, it's reliability and receiving readings from the device.

So I think the key the KPI is what is what is the customer's KPI? What's their North Star metric on measuring success with the project?

Now connectivity, everything else helps to achieving that, but everything should be going to optimizing that KPI.

Challenges of Connectivity in Poor Infrastructure Regions

Cool. Another question has just come through. So what about regions that have historically poor connectivity infrastructure? How do you maintain, you know, a hundred percent uptime in those areas?

That's a difficult one because if it's got no cellular coverage or it's bad, there's not a lot you could do about it if you use it.

Work with what you've got. But I I think what's probably gonna be quite important in the future is obviously the advent of satellite and and how we integrate that into the platform because where there is no infrastructure, you know, the Australian outback, the middle of the Sahara in Africa, there will now be an option a viable option as as as the cost comes down. So, certainly, that's one to watch out for, mate.

Oh, absolutely. And we are working with satellite providers today to provide that joint hybrid cellular satellite service as well. Now, again, this is really important. If you're looking at at at that and understanding that, okay.

I wanna deliver a a hybrid solution, it comes down again to working with the device. The device has to be able to switch between a cellular environment, that's just not rat types in cellular, a cellular environment and a satellite environment, and know when to switch back between the two. It's great having cellular with a backup into satellite, but if you don't the device doesn't know to come back from satellite to cellular and cellular is available again, then you've got some really big satellite bills coming, and that costs quite a lot of money. So yeah.

Absolutely. I think, if there's the this this hybrid the the the notion of hybrid services coming out, I think, is going to be more and more common over the next few years. You've seen Sotelier. You've seen, Starlink, etcetera, etcetera, etcetera.

So I think we will see a lot of that. But, again, it's work with someone who understands it. It can bring those two fields together.

Future Trends in IoT Technology

You mentioned satellite. It's kind of leads on nicely to the next question. What is the next big thing for IoT?

Wow.

What is the next big thing for IoT?

Depends on what part of the IoT ecosystem you're looking into.

At the platform level, at the analytics level, it's how does AI, inf help out in monitoring and managing the state. But there's also AI at the edge. How much processing is gonna be done at the edge? How can you, maximize or minimize data, transfer AI, reducing the cost of of connectivity and making make and making sure that's there. But AI at the edge, AI in the platform, in the visualization aspect, and I think in the in the sort of medium term as well, how do hybrid environments come in where it's not just one, connectivity type. You've got multiple connectivity types.

Cool. So that is all of our questions. So thank you both.

 

Emerging Technologies and Their Impact on IoT

Jeremy, what do you think?

Only time he does ask Jeremy, actually. I would say that I think probably the one the one thing that's coming up more and more is SGPs, especially two.

I think that's gonna put the camera up to the pigeons. You know?

Particularly with large global deployments, have you got the right platform?

And I think it it may well catch a few people out on.

It's not as simple as it's no doubt to be. There's a lot of integration that needs to be done into the back end. Are you gonna run your own platform? How's that gonna work? How does the billing work between different providers that you're working with? You can switch between, etcetera, etcetera, etcetera. So there's a lot of complexity behind SGP thirty two, which will come out over the next year or so.

And in the end, from Eseye's point of view, it's just another way of getting a SIM a a profile onto a SIM. So we're just gonna build in what we do. But, yeah, I mean, from, as you say, from an enterprise's point of view who have been doing this for a long time, it's gonna provide some opportunities, but there are pitfalls to watch out for. We have we have some papers on that on s u v thirty two Yeah. That are available for our customers today.

 

Evaluating IoT Platforms and Strategies

It's certainly probably a key question I would ask if I was evaluating potential platform.

You know? What the strategy and what what what the go to market strategy is gonna be Yeah. For for that.

Absolutely. I understand what your strategy is around that. Do you wanna become an MVNO as such, yourself, or is that not what your core business is?

Okay. So I'm just getting up some more questions.

So, one question came through. Do you offer Smart Connect app on legacy IoT hardware or, like, on different customer sites? Like, do they integrate with each other?

Smart Connect is a a a soft a piece of software that can be put onto the silicon of a device. So it depends on the device that you have.

We've integrated into, certain devices, not all of them, but but we would welcome the question or if you can give us into information on the device or what pieces of hardware you're trying to integrate it into, then we can, absolutely have that conversation with you. The answer to can we do it on devices that are already in the field, it's probably difficult to retrofit SmartConnect.

But, if you've got, if you're still producing those devices on the current platform, then we may be able to optimize your current your current hardware platform.

Cool. So I think that's all of the questions.

So thank you all for joining us today, and all of the resources we'll be able to download after this event, and we will also send out a recording after this event. So thank you all and goodbye.

Thank you. Thank you very much.