Good morning and welcome to all of you. It's nice to see so many faces here. It's a big day for Nordic, we are going to take you through the nRF9160 product here. Before we do that, I would like to look a little bit behind on history. Four years ago, we started to assemble a pool of engineers from leading companies in north of Finland in Oulu. These engineers were not only from leading companies but were leading cellular design at these companies that have done cellular design for decades. Due to the amount of engineers that were available, our team managed to put together the most leading engineers in the region. Now, four years after, we have put our LTE products into the market. We are very proud and most important thing is that customers around the globe seem to like the product too.
That's part of what we're going to talk to today. Instead of me talking, I let somebody else talk and show me a very nice movie. It really is examples of where this technology can bring value. All we talk about is to bring value to customers. I hope that during this session, we see the tremendous value we are going to bring.
Nordic Semiconductor has now launched the nRF9160 System in Package. This is a fully integrated device for cellular IoT. It comes with integrated application processor, multi-mode LTE and NB-IoT modem, and an RF front end. Everything in a very small package, 16 times 10 times 1 millimeter. This is extremely low power device that will be possible to use all over the world, and have all the necessary certifications in place. Let's have a look on how Nordic Semiconductor makes cellular IoT for everything else. Now we are connected to the base station. nRF9160 System in Package, cellular IoT made easy.
The agenda for today is that Svein-Egil will go through the readiness of the product. I show you where we are today. Heather will show the advantages of Nordic and also stack us up a bit against competition. Then Geir, our sales director, will talk a little bit about the customer reception so far. Remember the 12th of December, we launched the product commercially. Today is the 18th, we have six days of reaction to show you. You saw a film that showed how the nRF91 works. You will see real life how it works, how it's going to work, and connect around the world. I hand over to Svein-Egil.
Thank you for coming. I also have Martin Lesund with me here today. He's going to help us out with the technical, but also with multiple demos. Martin is a lead on our 91 support group. If Martin can't make it work, no one can make it work. I get to talk about product. What I wanted to just start off with is just showing you this long list of deliverables that is involved in launching our product. Last week, or was it the 12th, last week, Wednesday, we tried to have all this in place. From our company, this is the longest list of deliverables, most extensive product ever made. In some ways, I find it sometimes mind-blowing, the fact that we have so many things that need to be invested.
Still haven't been able to wind down since last week because for the last minute we put everything together. As we will talk more about the details, the list of deliverables are long, but also means that we go to market with a product that are more extensive than anyone else's. I sometimes joke with engineers that we try to bite over a big chunk here, and we still have a mouthful of food, but we'll make it in the end. What we're delivering, the deliverables we've been working on is first and foremost is a system on chip, the IC itself, that forms the basis of our product. This is what we call the 9120. Petter will talk a little bit more about that later.
That 9120, we put into a system in package where we put it together with RF front ends, power management system, passive crystal, we put it into an ultra small package. Our system in package, which is 10 by 16 by one, I think Gabriel will show some of that later as well. That's the hardware part of it, then there's a whole bigger element of software deliverable. What we do is to deliver two protocol stacks for LTE, one being the Cat M and the other one being the Narrowband IoT. We do two separately designed protocol stacks. We have GPS software underway and developed, which is also a big deliverable.
All these things got to be proven to work, we do that, we certify it, we get qualifications, to prove sometimes the radio parameters, but also a lot of these certification goes to see are you compliant with the specification, the LTE specification. These things is a good amount of work, which we've been working on. We talk more about. We talk a little bit more to in the last days about our SDK, our software development kit. One thing we're very proud of is the fact that we bring solutions all the way up, all the way to cloud with these solutions. We think we're unique in the offering we have. There's also big teams working on this. This is essentially getting the IP stacks ready, getting the RTOS drivers, everything else that you need as a developer to make a product.
Finally, we're going to later show cloud connectivity as well. We bring cloud connectivity to our solution so customers can immediately power up a board and be cloud connected. That gives the ease of use and the end-to-end experience that we promise our customers that we're very proud of it. Well, this is the set of deliverables that we've been working on pretty much for three and a half years in different shapes and forms. Right now, when it comes to the System in Package, the nRF9160 that's moved into production, we're volume ramping this SiP right now. It means that we're not in full production as we call transfer to production, which is one of our formal gating that will happen in April.
That gating means that we have completed all qualifications over temperature, we have done all test and measurement as a safe product and so forth. These are posts that typically take three to four months to just go through. It's an inevitable step that we always have to go through with all our products and those things we are in strike now. Also doing slight adjustment to silicon, meaning that we have made some modification to the chip in the last couple months ago, which goes into a final production also for April. As you can see from this table, which outlines the three variants we bring to market, we're working on the other variants of our product as well. The 9160SICA is the first product, which is ready in April. I think this one probably, yeah, looks to be ready the same time.
All good shape when it comes to a product. We ramp in production got significant wafer starts already. We have significant quantities in warehouse and being shipped out and so on. You can get more about that later. Software-wise, I think there's three big elements of protocol software that we're talking about, is the NB-IoT protocol stack. It's the Cat M protocol stack, and it's a GPS software stack. One of the things that we talked about for a long time is that, the initial focus of what we've done is to be U.S. first. U.S. first is Cat M. That's why the protocol stack that's most relevant for U.S. Cat M is now in full public sampling. That will be a production-ready software in March or the same timeframe as we do what we call a formal transfer to production on a silicon.
That is the first part of our software that is ready. You'll see here that in the development board, and if you go to our website, you'll find that this Cat M software is publicly being sampled, so everyone can use it and try it out. The two other elements for our software offering, the NB-IoT protocol stacks and the GPS, is around a quarter or two after in terms of development progress. There are some limited sampling of our NB-IoT and GPS software to limited customers. You won't find that publicly available on our website. You need to be a customer that speak to one of our sales guys and have a good argument why you should get it, then you will get it.
These are coming, up until sort of end first half, all these software deliverables should be ready, and customers can go for full production. You may have seen the announcement we did last Tuesday about certifications. Two types of certifications. Typically, we do teleregulatory, which is the FCCs and the CEs, which is typically good to go from a national teleregulatory point of view. Then the second big one is what we do is the GCF, which is a Spanish group that is working to ensure that your product is compliant to 3GPP LTE specification. We announced a full set of certifications last Tuesday. Needless to say, we're incredibly proud and happy to do these certifications because it means that we've come a long way in terms of our maturity. Means the software's in place, means we run all the tests.
It's just a lot of work to get it in place as well. This is the cake moment when we get these things in place. We do some celebration this week as well. Very happy to announce certification in place. Now, we have certified with a number of bands, which is the most relevant bands in the market we're going to. Now in the next months and quarters, we certify more frequency bands for more markets. We are going to do more teleregulatory in other territories apart from European and the U.S. and Canada. We will do operator-specific certification as well. One thing that is, when you think about questions comes up: what about the operators? A lot of operators have this as a pre-certification. You've got to be GCF compliant.
If you are, then they may or may not say that's enough, or they may want to do additional testing. That depends on territory, that depends on operator. Very good shape on certifications. That's moved forward. I'm very happy to be in a situation where we can tell every customer that this is all certified. Development kits in mass production. We made a development board, which we will sell in large quantities called the nRF connected development kit. This is no longer what we call limited series production. We produce now thousands of these. We production set that a couple of weeks ago. Now, as Kjetil talks more about how they roll out, they look pretty nice. It's a nice product, easy to use. Unfortunately, it takes a minute and a half to assemble the box to put stuff in.
If you're making thousands of them, it starts to become something we have to optimize. It's funny how you have new challenges when you mass produce dev kits that you never thought of before you did it. Yeah, this kit is going out right now. It has the board, it contains connectivity, everything you need to get going, in a nice package too, right? SDK software or middleware, as we also call it, is an important thing of what we do. I'm not going to go into details about exactly what's in there, but in this current release that we did last week, we have a whole number of middleware elements. Again, MQTT, BSD sockets, we have drivers, we have SDKs, we have a number of examples like asset tracking, gateway solutions.
We'll demo that later, route solutions, a whole long list of software development, middleware or solutions that you need to build products. This is work in progress. We're clear about that there are certain things we're not ready with yet. This comes in the next months and quarters. We'll keep rolling these out as we complete more stuff, and we'll make other things as well. Those who are interested can, of course, go to GitHub and have a look what's in, and that's where we will be updating code as we move forward. Right now, I think that the solution we have and we can demo today, is a great starting point and an excellent way to start developing for customers. Finally, nRF Cloud. It's important thing for customers to have an easy start, and we'll demo this later in cloud.
nRF Cloud solutions allows you to do things like activate your SIM card when you get this dev kit. It allows you to manage your development boards. It allows you to try out things. You can connect your own cloud solutions as well, and you can build further on it. It gives a great starting point for anyone who want to build application or for storing for their managers, or proof of concept for anything that gets you going in the journey of development. nRF Cloud is all up and running, and as with all software we do, nRF Cloud is a living website. There are continuous releases. We add new features, and we continue to develop this as well. That is what I want to talk about product updates. Kjetil.
All right. Thank you. I'm going to talk about, not what we've delivered especially, but what the customers are getting and why we're getting into these markets indeed. First thing I want to point out is, we've talked about this in the past. There's LTE-M, there's Narrowband IoT. To a certain extent, they look similar. Some carriers have decided to go with one before the other, et cetera. As we've started to have more detailed discussions with the customers, and the customers are getting more knowledgeable about this, it's becoming very clear that these are two different technologies serving different types of applications.
It's also going to become clear from carrier deployments that we see the rest of this year, which is not much, but still there's some things coming, and all of next year, that a lot of the carriers are going to go with both of these. We saw that already in Norway with Telenor, they got both. I'll talk about the reason for that. It's really on these bottom lines where you see the range. There's a significant delta. Now, range is extremely important. We'll talk a little bit more about how we perform, but at least note that there is a difference in how much range you get out of these technologies. NB-IoT, longer range, more penetration. Then mobility, it works in LTE-M. That works up to 100 km an hour.
This is when you jump from base station to base station as you're driving down a road, for example. This is what makes it work, the phone, the stream video while you're on the train, for example. That's the LTE-M mobility. Allows you to have a connection while you're moving. NB-IoT doesn't allow this. There are some improvements coming in future variants of NB-IoT, but it's not there yet, and it'll take a long time for NB-IoT to catch up on this aspect. Roaming doesn't work with NB-IoT, but the good news is it does on LTE-M, which is also demonstrated very clearly with our development kit. We have a roaming SIM card in there, and ship it worldwide. It'll work anywhere where there's LTE-M, as long as there's agreements in place.
That's extremely important, as you can imagine, for applications that move across borders or get shipped initially to different places in the world. We'll talk more about some of those applications. Battery lifetime is similar, but there are certain applications where NB-IoT has a very significant advantage. Strengths, because we're being positive today, I'm only showing the strengths. The higher throughput of LTE-M definitely makes it more future-proof in terms of marketing's always going to come up with new ideas for things that the product can do. This is the plight of every customer we have. They make a product, first thing they're going to come back and get is more requirement.
It should do this, too." What LTE-M allows is that even if you started on NB-IoT and thought maybe that was good enough from a throughput perspective, once the new requirements come in, you can move to LTE-M and get the higher throughput. Low latency can be important to some applications. You can imagine some door locks, for example. You don't want to stand around waiting for it. There's roaming, as I mentioned, mobility, and then it's most power efficient at medium data rates. We don't say high data rates because in LTE, you know what that means. That's like YouTube 4K. That's high data rate. This is medium data rate. This is for downloading new firmware updates, maybe uploading an image every once in a while. LTE-M is much more efficient. Suitable for TCP TLS end-to-end secure connection. That is extremely important.
The LTE-M has the same way to connect to the internet as your phone does. It connects in the exact same way through an APN, and you can connect. When you connect from your phone to your bank, you do that with HTTPS or TLS connection directly from your phone to your bank server. Okay? That's the way LTE-M works as well. That is not how NB-IoT generally works. It does not have that full end-to-end security with TLS. There are other means to get good secure solutions with NB-IoT, but they're not as clear-cut and as simple as the LTE-M one. With NB-IoT, the biggest range is you get the longer range penetration. This is especially for indoor applications.
In LTE range across open air with free range, we have a video from Pete de Orm. That was a little bit of a teaser, actually. In that previous video, we'll have a full video showing range in open air. That's not a challenge for an LTE. You can go tens or even up to 100 kilometers. It's not a challenge. It's the indoor that's the challenge. We all know this. They've done parking garages, et cetera. That's really where the challenge is. NB-IoT has a real advantage there. There's most power efficient at low data rates. If you have very little data to send and send it only every once in a while, you can get away with significantly lower overhead with NB-IoT than with LTE-M. It's mostly about not having to establish these higher level of connections.
On the contrary, makes end-to-end security more peaceful. Trade-offs, definitely, and we will show a little bit of examples from typical applications. If you have an asset tracking device, say, a container, it may be moving pretty fast down the highway. You may want to track its trajectory towards its location, final location. It will also move across borders. Even things that aren't meant to be moved across borders, sometimes it's actually when it's moving across borders, you actually want to start tracking it. That's very relevant for that asset tracking devices. Roaming needs to work, and mobility is a good feat, so it's an LTE-M application. Wearables, medical, it's one of those areas where you expect pretty fast latency, and rich user interface. Maybe you want to upload or download something every once in a while.
LTE-M is great, and it's also one of those applications where mobility or roaming is expected. You take the watch when you go to Denmark, it should still work there. Retail point of sale and security for homes, this is also one of those areas where LTE-M security end-to-end from your device to whatever server you trust on the other side is extremely important, which is why LTE-M is a good one. Contrary, on the NB-IoT side, we see in smart metering, there are some big vendors out. Power consumption is absolute key. For gas, water meters, depending on the country, the penetration can be deep underground, can be in basements, can be really challenging. You need the absolute best range that you can get, and you get that with NB-IoT and Hard Pass. Smart agriculture. Things don't happen very fast in agriculture.
Latency is not an issue. Very small amounts of data, but very important data. This is fixed installations. They don't move around. NB-IoT is great. Smart city, similar parking spots, streetlights. These are inside the city, don't send a lot of data, perfect for NB-IoT. Preventive maintenance, down in basements, installations inside concrete buildings, NB-IoT is perfect. We do both, and we do it with this line up here. As Svein said, there's a long list of deliverables. The first one is obviously the hardware. That's our biggest value and that's our entry point. That's what we sell. We have further variants coming, which is important. We've talked about this a lot in the past as well, as well as in Bluetooth. If you don't have a roadmap, you don't have a product.
No one wants to see that you have one model and then there won't be a path of the new model. Obviously, we have a strong roadmap, and we'll be able to show innovative new features coming up. There's stack and software, protocol stacks, extensive SDKs, and RTOS. These are just kind of needed for the customer to be able to do their application. When someone comes and says, "I want to do a smart meter," it needs this type of input, they need to be able to process it this way, and then they need to be able to send it. We enable all of this with these three pieces of software. We need tools when they develop. We make it easy for them to develop, to evaluate and test, and then to deploy.
This is very similar to what we do on Bluetooth. This is the Nordic way of doing it, which is we're the developer's best friend. We want everyone who picks up our device to have a good experience with it, and they should want to use Nordic and want to use Nordic again. That is a lot of the reason why we keep having great interactions with customers in early phase of our development. They want us to succeed because we have supported them in the past. We've delivered good products in the past, and it's really about nailing these different aspects of it. You get the device, you get up and running very quickly. It should do something out of the box, and we'll see the demo later today.
It needs to prove that it's a working technology and it's already there, and when you get it, you get a complete solution, and it should be pretty close to what you want to do in the end. You get everything on a single board. There's no stacking. There's no getting something from a different vendor or trying to piece things together. We deliver everything. We put everything down on the same board, which also makes it perfect as a starting point. If you want to make your own product, we give the files, we give everything. You can take that as a starting point for your own development. Free development tools. This may sound petty, but it's important.
If you want to just try out a few things, you don't want to fork out a lot of money for an environment that just allows you to develop something. Just put a lot of effort into this, and we now have a great tool suite. Open-source software, everyone can contribute, and it's the way that it enables us to use tools and get contributions from a broader community, not just Nordic contributing everything. There's device management through a cloud solution that Svein-Egil talked about. You have really the end-to-end, the device to the cloud, and we deliver everything. The small size of the SiP makes it easy to integrate into any product. Even if it's a small device, you can still make it fit.
We integrate all of our tools that are needed for development into a suite that we call the nRF Connect suite. It's easy to recognize the tools from Nordic. It's easy to download them. They're all available in the list and available in the same environment to run on any PC, Mac, or Linux. It's really all of those things makes us popular. What we deliver now is what we think is the most important example, is end-to-end security from our device to the cloud. It's really showing up some of the key features of our device that I'll show in the next slide. We set the bar high. We connect to an AWS-based service, Amazon Web Services sets a high bar for standards of security authentication to their cloud servers.
We do that out of the box with this example that we deliver. This code is already on GitHub. All the design files are available to customers. They can take this as a starting point. What we leverage here, two fundamental security blocks in the hardware. One is the Arm TrustZone. This is to be able to separate trusted code from not trusted code when you develop. Really making sure that you can put some code in a secure environment that will not be touched from any other code. What makes this really important is when you look at the massive scale of security breaches in the IoT have been over-the-air attacks. Attacks that have happened through the internet and to devices on a massive scale.
Part of the reason why that's been allowed to happen is because all the code could be modified after the device was shipped from code that was injected. This is really extremely important to take seriously and do right, and we do that with the TrustZone. The other aspect is the co-processor for crypto. Crypto means that we can do authentication and encryption of everything that goes over the air, all the way to a cloud server in the end. Not just with the SIM card going to the base station, but really all the way. We do that power efficiently with the acceleration. Other than that, what you're looking at is a solution in the package. We deliver as much as possible into this device.
Sensor and eSIM, customers have to choose themselves based on their preferred vendors and what kind of sensors they want. Battery or power supply, very application dependent. For everything else, it's ours, we deliver it, and it's put together by us. You don't have to go searching around for compatible components. The global support. These are the bands that we've enabled into the hardware so far. We can add more as they become relevant. It's really about servicing both U.S., EMEA, and APAC with the same device. Again, the signed device with LTE-M support, for example, with the nRF9160, like this one, we even proved this now with our dev kit. You build it one place in one factory, you ship it worldwide, and it works. Proving it with our dev kit is extremely important.
There's no EU or U.S. or APAC variant of the dev kit. There is only one, and anyone can buy it from any distributor worldwide, bring it up in their own country, and it works. That's that in practice. Low power enables some very disruptive applications. We've said this all along, that this is a key focus area for us. The reason is we want to be able to get into devices where cellular could not go before, where there was no question of using cellular because the power levels were too high. We've done some really amazing things with the power management techniques that we inherited parts of them from our previous portfolio in Bluetooth, but we also have invented some new things. We're very happy with the performance.
PSM, extremely important for long waiting times, such as agriculture and the metering, where the device doesn't have to be reachable all the time, but every once in a while, it wakes up and sends something. We will get down to three microamps in these long wait states. That's extremely important. That's where you spend most of the time. If the device wakes up every once or twice per day and sends something, most of the time it's spending in sleep. That's extremely important to get that right. It's quite similar in eDRX. The sleep times are typically a bit shorter. You have to wake up very quickly and do what you have to do and get back down to sleep again. What's kind of amazing is this number, seven microamps. I will show you on the next slide as well.
We're able to keep everything retained. We remember everything about the session and wake up very quickly, do what we have to do, and go back down to sleep. When we sleep, we're at seven microamps. In that sleep, again, remember everything. There's nothing lost there. Nothing has to be read from somewhere or found out again. We have extremely efficient wake-ups. We had to make an adjustment to the numbers that we showed in January. You may remember we were talking about 15 microamps for connected eDRX. Every 10 minutes, you wake up, check if there's something for you on the server. We're at 11 microamps and not 15 microamps. It's really fantastic work by the team. They managed to squeeze out some of the final opportunities we had for savings there. This is very competitive.
When we move into the higher activity tracker type scenario, we've met our target. On the full speed, there's not much that can be done to or fro there. It's really about pushing a lot of energy across. We are where we should be, and it's a good number. These are the ones that are going to enable the new applications that weren't possible. For 2G, for example, this type of scenario would look very different. Add zeros. Range is absolutely key. Talked about it already in this presentation quite a few times. We have the max output power, 23dBm, that's allowable worldwide. We push that to get the maximum range. On the flip side of that, the sensitivity. When we receive, we receive at -108dBm with LTM. I mentioned this already in January. We already have that number then.
Now we also see that we're at -125dBm with MFPS, sorry, which is a great number. You can also tell by these numbers that you will get maybe one or two more floors down in the basement with NB-IoT than you would. This is a slide that I think is going to be more important than probably a lot of the other ones. It's becoming more and more clear to us as we engage with customers, because we own the chip, the firmware, the SDK, the module, and it's all developed by us. It's all supported by us. When Martin needs to get an answer for someone who designed that particular part of the chip or the firmware that runs on it, he's got an indexed party and just calls him up. The guy works for us. He's in Finland somewhere.
If he needs to know something about the SDK, that's in the office next door. These are experts in development of applications. When we look at that compared to our module competitors who buy chip set from some vendor who actually specializes maybe in mobile phone chip sets and doesn't really care too much about the IoT, doesn't know much about the IoT, this is a really compelling point for our customers. I expect fully that we'll sell a lot of these development kits, and I think they will be put to much, much better use and be much more productive than the comparative kits from our competitors in the module space. That's all I have.
Thank you, Peter, and thanks to you all for being here. I'm Geir. I'm Director of Sales and Marketing in Nordic. I've been invited to give you a little bit of a head up on what's going on with the customers. Little bit of warning if you're here to learn of names, et cetera. It's not going to be given today as usual. We can give you some vectors to work along. I think the nRF9160 has been extremely well-received in the market. You may have seen over the last few years, we have a very loyal customer base. They're all giving our product a lot of praise. It sort of builds upon the things they already know. We have also engaged with a lot of new IoT customers that's used cellular in the past or are planning. We're getting really, really good feedback from them.
Very importantly for us, as you know, we're a broad market company. We're spawned wider than a lot of the other guys in the industry. We rely on trade press coverage. We picked that up on the way as well. Our distributors, of course, are really stoked on this. It's the first time they're allowed to sell a proper cellular product that can really be used in a wide array of applications. We've also been nominated for a lot of professional awards, which I think is pretty cool. We'll take you through those. Carriers are actually referring customers to Nordic. We've done some joint marketing with some of the carriers here in Norway, we already start seeing real good benefits of that, they're actually pulling us in. To me, that sort of indicates a vacuum.
In fact, the only people who have not received this so well is our competitors. I think they've had a little bit of an iPhone moment. If you remember that time when Steve Jobs presented the iPhone for the first time. These guys, they're seeing something they haven't seen before. That's good. I think in the Q3 presentation, we did state to you that our target was to be on 300 lead customer samples by the end of the year. I think safely Nordic, we cannot be outdone by either lower the current consumption. Already today, on the 18th of December, we have shipped more than 350 lead customers in our samples and kits. We're ahead of schedule. We have been working to set up online 9160 availability, the leading online distributors. We've done that.
There is a little bit of a vacuum where we've shipped kits, and they basically sold them quicker than they have received them. We've already shipped more than 1,000 kits in the last week. Rest assured, there's going to be a team in place here in between Christmas and the New Year to make continuous shipments to distributors worldwide and further widen the distribution network. I'd like to take you through these industry press coverage and awards we've been awarded. We didn't quite make it to the Leading Lights Awards, but I think that's acceptable if you look at the other guys nominated in our category. We had Amazon Web Services, we had Huawei, and Nokia competing with Nordic. We're right up there with the best names in the industry.
Now, we also were named the CES Innovation Award Honoree, and this is basically an award given to companies with technology that is above average in the category. Okay. We were not the CES award, but the honoree, and we actually have really compelling products, and we get recognition for it. Last and not least, I'd like to highlight the GSA Award. It's basically an industry peer award. It's 500 semiconductor companies giving their votes on what companies do you think have done an outstanding job in their category in the year that passed. Nordic won that for a second year in a row. We're extremely proud. It means a lot to us and enables us to go on fighting for these products. I mentioned some press coverage.
My team has been very busy since we launched last week, collecting up, okay, what trade press magazines have rewritten our release and our presentation from last week. There's this more than 35 companies as of yesterday, and these are respective publications in the engineering and the community that our customers would go. Also, we've had a very, very high traffic on our webpage since we launched. Compared to the pre-launch close to a year ago, we've had traffic on the web server, and on the day we launched, 10 times the traffic on that section. Most importantly, we are excited to see, are the customers taking our kits and doing stuff with them? Yes, they are.
On the nRF9160 DK, that kit site is now consuming 40% of the traffic that we have on all of our software tools and kit tools pages in literally a few days. I think that's pretty good when you look upon the fact that we're actually shipping close to 30,000 kits in six months. This kit has a lot of good competitors within the company. Also, the increase on the development tools section of our webpage has gone up by 70% since the day we launched. There's an incredible amount of activity. We see it in the support database. There are actually people using our kits that we've just shipped who actually need support and they develop. Does that mean that we're going to have a huge revenue tomorrow?
No, this is when the hard work starts, where people take the kits, the pre-sample customers, they're already working on it. We're shipping out hundreds of units to customer A, B, C, and really laying down the stones onto the foundation of a great product family. That's pretty much all I would like to share with you in terms of customers. Just to show you that it's true, I brought some samples from upstairs. These are not snacks, but leave that with you to while you do the demonstration.
Okay. You're going to hand out some goodies. That would be good.
Yeah.
Okay. Folks, I got one small slide to do.
Yeah.
One more slide to do.
Where is that slide?
34.
Sure.
It's a little bit hard to demo something to make it properly meaningful, but I thought we'll look at three things today. We talk about worldwide coverage, and we're going to show you what that means in practice to be worldwide and the ability to be all over. We're going to talk about and show ease of use, and we'll show you how easy it is for anyone to connect up a dev kit. We're going to show you something else that we think is pretty cool is that you may have noticed on one of the slides, deep in the material, it says something about Bluetooth LE connected. We're going to show you a demo where we actually pop technologies. We think it's a great way to leverage customer base and existing technology to build upon.
That's the three things we're going to try and do. It's demo time, things can always go wrong. Excuse for that in front. We won't do that, Martin, will we? We'll make sure we get it right. Let's take it away. Martin's going to go to our nRF Cloud. What you're seeing here on the front page is the nRF Cloud website. You can go there too, and we're going to log in, and we're going to have a look at what this user has off development portal. Right now we see that we have seven LTE devices connected. You can click on those, and you'll see that they are-- we have different things in different places. I need to see. They're all green?
Yeah.
What we have right now is on this demo, we got a device in Hong Kong. We've got a couple of devices in Finland, both in Oulu and Turku. We got something in Texas. We got something in China, and here we got kits, and we got also the scooter tracker in Portland, Oregon. What you're seeing is a number of kits now connected to this user. They're operating on different networks. They're operating with different technologies and different places. If you're a customer trying to do something, then you could mimic this thing. You can have different things, different places, see how it work. You can pull statistics to see how things work, and unless you make something like this yourself, this is the easiest way to get going. I think it's pretty cool. We're showing off that they're actually worldwide.
I guess that one of the key things. What you're seeing of these kits is that we're not using customer kits right now. This is our team in Portland. This is our team in U.S. with Don. We have different numbers, people set up to be online with these kits. This is what you can do when you're online. We want to drill into one of them. Is that so, Martin?
Yeah.
Which one? Go to the scooter tracker?
Yeah, looking at the Portland one.
What's going on here?
There we have a scooter tracker.
Okay.
GPS data.
We've been tracking the scooter. Is that Chris there? Is that driving the scooter or what?
That's correct.
Okay, he's been out on the bridge. What time is it for Chris right now, though? It's got to be like 3:00 A.M. Well, we've got some dedicated employees in Norway, that's for sure. What we're seeing here is just something simple as tracking GPS location, tracking a piece of something. That may not be or feel like the most advanced thing we can do, but it's probably one of the most valuable applications there are. It's a simple thing. Track something, and it works pretty well. Anything else? Is the temperature correct? 0.7 degrees, is that degrees Celsius?
I'm not sure if that's correct.
Okay, apparently, it's not that warm there anymore either. Yeah, is there anything else you wanted to show there, Martin?
No, not on this one.
Okay, perfect.
Could maybe try to add another device.
You want to add another one, or you want to do the unboxing?
Okay.
how much time are you going to spend doing that?
Max 10 minutes.
Ooh, 10 minutes. You're going to take one of these kits and open it. You promise you haven't opened this before?
I promise.
You're going to open this kit, and we'll give him 10 minutes. We know that you guys are going to be bored with 10 minutes. This is why we said we're going to do questions while you do that. We're going to do a couple of questions right now, Tor, while Martin works. I'll point out sometimes in between exactly what we're doing. Martin, take it away. Show how easy.
Right.
You want to take that one?
Start the clock now.
Start the clock. Let's see. Most importantly, get it right. Don't be stressed out with it. It's fine. We'll start doing the sequence that he will do when a customer gets this board. I'm going to keep it going a little bit more. I know Martin's got it, but we can do this like lightning. This is easy. Also, one thing I wanted you Show us what you got in your hand there on this one. What Martin is showing here is a SIM card. It's a SIM card from iBasis. Henrik, will you say two words about what iBasis is?
Yeah. It's a roaming vendor, they have eSIMs. They're actually reprogrammable SIMs. It looks like a standard SIM card, but it can be programmed to have any profile. They have an extensive R&D department. We're working closely with them. There's no exclusivity between us, but we're trying to explore what we can do in order to get customers started also on a good connectivity path. This seems to be a very solid way to do it with an eSIM. We believe this is absolutely the future, and we want to support software attempts in our DevKit as a standard.
We've been integrating this solution with the iBasis so that, as you said, the really great thing is that you don't need to do anything else to get it to work. You just simply take that SIM card that we provide, it will work in 300, 400 networks at once.
70.
700? All right.
Soon. Soon.
Yeah. They have, but they have to turn on LTE on those networks.
It's almost there.
Yeah.
They have a contract with 300 networks, and they start bringing them on.
Okay. What we've done now is okay, this is going so fast that I don't know if there's going to be a lot of questions here, but we'll see. Register the user on the SIM card, which you could have done if you had the kit. Just keep going, Martin, because if you're on the clock here. Let's see. The only thing that you need to do to be able to do this, you may have to have really sharp eyes, right?
Yes.
Or a magnifying glass to read these numbers. This is the only way we can identify. You got to have an identification between DevKit itself, so that's tied up to the SIM card, and the cloud solution. What are you doing right now, Martin? Tell me.
Now I have written down the code and waiting for the verification.
Where does verification happen?
Yeah. I put in the SIM card, and now we're waiting for the verification to go in, and we're going to power it on, see if it's going to get connected.
What are we waiting for right now?
Now we're waiting from the iBasis-
Servers.
Some of your slots are important, Martin. Do you want any more questions, Tor, about it?
If there's, yeah, it's over.
Let's look.
This 360 customers happening is obviously an impressive number, could you share anything in terms of how many of these are now actually actively developing concepts on your frame?
Geir can answer.
Yeah. I think the majority of them are actually doing that because in the timing leading up to the 12th of December, we've been managing very limited samples and boards going to customers. That's been given in on a prioritized basis in a program that's sort of going into production relatively soon or if it's an interesting application. The majority of those numbers are actually prior to the 12th of December. We just had a couple of days, really, where we've been retailing the units.
You would expect the majority of those to be to kind of launch product based on the nRF91 module?
There's a very high likelihood. It's been qualified. Things could go wrong with the application or the desire not to bring it to the market, the majority is working on it as we speak.
Another question.
I don't know if you want to answer it. Could you share any update on the kind of expected revenue ramp in 2019? Because it seems like things will not be completed really until April at the earliest. Is that when we should start to potentially see revenues coming in?
You will see the revenue by end of 2019. Until that, it will be relatively prototype built by these new customers getting ready for production. End of 2019, you will see revenue.
Lastly from me, on the product roadmap, Petter, I think you stressed the importance of having kind of an exciting product roadmap.
To me, it seems like the product roadmap that you are sharing now is a simplification of the existing offering in terms of the single mode, NB-IoT offering, et cetera. Is that kind of an exciting roadmap, or do you need to show something improving on the kind of the high-end version of it as well to make it even more exciting?
There are several vectors. You should be expecting us to do is have a similar strategy here as we do on competitive devices, that we have some of you going into higher-end stuff, adding more features, and some of them into lower-end stuff, doing more limited feature sets. It's a combination of both of those things that will attract different customers. As with Bluetooth, there are new revisions of the standards coming out, things to follow. The important point that I want to stress is that it's not enough to show a product. It's always with technology. People are making these investments for a longer-term commitment, and they want to make sure that they can continue to design Nordic devices when they need new features and when they need to support new standards. There's 5G coming up, and certainly that's a big part of it.
Just sort of quick follow. When you go into this market, which is kind of, you have traction with a lot of these customers from before on the kind of the short-range business.
Which is, of course, an important element. When you go into a completely new market where you haven't been before in terms of cellular, how can you kind of make your potential customers confident that you have what it takes to kind of provide a reliable product with no track record in that space when they kind of order more and when they order from you?
Yeah, that's a great question. I think we have a very compelling story with the team that we have in Finland. Those guys are experts at what they do, and they have an excellent track record of manufacturing high-volume products in this space before that are significantly more complicated than the one they're making now, by the way. Then they also have some of those names are famous, I think, in the industry. That does go a long way to building confidence. Nothing speaks more than getting the GCF certification, for example, in the short amount of time that we have. That is extremely challenging, the regulatory stuff.
Yeah.
The GCF is pretty significant to us, something that builds confidence in customers.
I'm just going to stop you in the questions, Jim, because, okay, we answered the problem activating that SIM card for iBasis for some reason we don't know. We reverted back to a SIM card that we should know work.
Now we're waiting to get the hookup to the base station.
Yeah.
Then we're going to pair the new device with the nRF Cloud.
That could take up to two minutes, it says.
Yes.
Okay. Are you having connection to base station now?
Not yet.
Okay. Any other question?
How will you do this if you have done a deploy with over 2,000 units?
You're going to be completely pissed. You can't do mobile. You got to find a SIM strategy in bulk registration. You can do the manufacturing. Yeah.
Now we have connection with the base station. We are going to do a pairing procedure with the nRF Cloud. This is random, so for each account.
Now we know again, we know which device is which.
Now I have the green light here. That means we are connected. Let's see if we have added one more device here.
That's the one here, right?
Yeah, that's correct.
Yeah.
Let's turn on GPS data. We can get some simulated GPS data from John Lamm in office.
Apart from getting the iBasis activation going, for some reason that we need to figure out why that.
Yeah, that usually takes seconds.
Yeah.
Actually.
We had some issues with that one, but apart from that, we were actually able to do this in 10 minutes, didn't we, did it? We took the time.
Eight, 50.
850. Give or take, this is how easy it is. Go out by any competitor's kit and try and do anything within 10 minutes, and you won't stand a chance. We think that's a pretty impressive demo. Do you agree?
That's it. We'll let him because at least he deserves an applause here.
This is what we expect.
Okay, we will show one more demo then, Martin. Are you ready to go right away, or do you need preparation time?
Yeah, I have to connect.
One thing that we think is a very interesting market was be able to work with customers who don't want to do both Bluetooth and LTE because you come to Nordic. Not only do you get the world's best LTE solution, you get the world's best Bluetooth solution as well. You got to work together, for that, we prepared a tiny demo.
Great. In this box, we have placed an nRF52, we are utilizing its accelerometer to check here which side the package is on. When it's upside down, it sends an alarm to the nRF91 device, it connects to our nRF Cloud and sends out GPS data, what side it's been tracked on, and such.
That communicates this box with the thing inside communicates over Bluetooth to our 91 developer board, which also has Bluetooth built onto it. It does transfer that data into packet formats necessary to.
Yeah, that's correct. Let's see here. Turn it upside down. Sends the GPS data as well as which side it's been on. It tracks each side now, it sends nothing, but when it's upside up, it sends everything all at once. This is to save power, of course.
Sure. What it allows us to do, and I think that this draws us to Nordic because this is all the customer opportunities. The ability to have a system where you have maybe many inexpensive Bluetooth sensors sending data to a 91 Bluetooth-based device, then suddenly you have the opportunity to build yet another way of building a new device. With Nordic, of course, it's a one-stop shop. You get every solution, you get the software, the hardware, everything from us. You don't have to go to two different vendors to build. You can just go to us. I think that was the end of our demos, wasn't it, Martin? That's pretty good job. Maybe we should give Martin applause for that.