<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Olga Kostina IoT Whiz on Medium]]></title>
        <description><![CDATA[Stories by Olga Kostina IoT Whiz on Medium]]></description>
        <link>https://medium.com/@olgakostina_iot?source=rss-3bc4a5230a9d------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*lZJONkCjz9PEj0DBM6QJ6g.jpeg</url>
            <title>Stories by Olga Kostina IoT Whiz on Medium</title>
            <link>https://medium.com/@olgakostina_iot?source=rss-3bc4a5230a9d------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sat, 21 Nov 2026 16:29:33 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@olgakostina_iot/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[How IoT Solution Providers chose THE ONE — LEO satellite IoT connectivity provider.]]></title>
            <link>https://medium.com/@olgakostina_iot/how-iot-solution-providers-chose-the-one-leo-satellite-iot-connectivity-provider-90d30cf9bfe4?source=rss-3bc4a5230a9d------2</link>
            <guid isPermaLink="false">https://medium.com/p/90d30cf9bfe4</guid>
            <category><![CDATA[oem-manufacturers]]></category>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[leo-satellite]]></category>
            <category><![CDATA[satellite-technology]]></category>
            <category><![CDATA[iot]]></category>
            <dc:creator><![CDATA[Olga Kostina IoT Whiz]]></dc:creator>
            <pubDate>Sun, 06 Mar 2022 19:11:19 GMT</pubDate>
            <atom:updated>2022-04-03T16:09:49.328Z</atom:updated>
            <content:encoded><![CDATA[<h3>How IoT Solution Providers choose THE ONE — LEO satellite IoT connectivity provider.</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*lXiBfS6IXgD6YJUdzKyt7g.jpeg" /></figure><p>Are you an individual or a System Integrator, looking to enhance your existing IoT set-up with a different link, to reach those rural sensors? <br><strong>This article is not aimed at you,</strong> because you probably already have all the IoT sensors in stock and you just need a different connectivity leg.<em> </em>My advice would be to go and pick out a Starlink dish or another out-of-the-box satellite connectivity solution. Big network providers like <a href="https://www.vodafone.com/business/iot/managed-iot-connectivity/iot-satellite">this</a>, or integrators like <a href="https://m2mconnectivity.com.au/services/">this</a> could help to get you up to speed. Nevertheless stick around to understand the trade-offs that satellite networks have, to make sure you are not oversold.</p><p>Or</p><p>Are you of the IoT Solution Providers kind — <br><strong>an IoT Original Equipment Manufacturer</strong> (<a href="https://medium.com/@olgakostina_iot/which-types-of-customers-are-out-there-for-an-iot-modem-manufacturer-db69136cc4fe">OEM)</a>, who manufactures IoT sensors and whose portfolio needs a lift; <br>or are you <strong>a Connectivity and Service provider</strong>, looking to expand their IoT offering into the satellite space? <br>If you landed here, you might be looking to carry out due diligence on a <a href="https://medium.com/@olgakostina_iot/types-of-satellite-networks-used-in-iot-solutions-de464672d16c">few Low-Earth Orbit (LEO)-satellite network providers</a>…</p><blockquote><strong><em>Bingo, you’ve got a match.</em></strong><em> In this lengthy piece, you’ll find an overview of the LEO-satellite network qualification questions, to make sure that your business case wins with the right LEO satellite player.</em></blockquote><blockquote><strong>Special treat! For a </strong>downloadable checklist to choose your next LEO satellite network provider and a <strong>shorter list of “make-it-or-break-it” connectivity factors, navigate to the bottom of the article.</strong></blockquote><h4><strong>Short intro</strong></h4><p>Since the Satellite IoT industry is developing rapidly and these types of overviews are still fragmented and marketing-driven, I want to initiate a discussion on standardizing the way how IoT Solution Providers assess LEO satellite network providers.</p><p>I have interviewed several Tier 1 (Global, large corp) - Tier 3 (Local players, agile production) IoT Solution providers to better understand their needs towards the LEO-satellite market and to get an insight into their decision process to bridge the two types of market players.</p><p>Solution providers want to extend the range of coverage for their “critical applications” — high-value logistics, critical infrastructure monitoring, governmental contracts to gain higher revenues. The LEO market doesn’t fully satisfy the reliability requirements for the critical applications yet, while it can meet quite a few requirements from “wide-area monitoring” applications. <br><strong>During the due diligence on the LEO satellite provider, IoT Solution provider would need to assess the network reliability to match an offered network capability to the criticality level of their business applications.</strong></p><p>My focus here is on the due diligence of the LEO-sat network when Solution Provider integrates a satellite modem and airtime service into their end-product, even though part of the considerations overlaps with integrating a <a href="https://www.iridium.com/products/iridium-edge/">satellite terminal</a> into the end product.</p><p>Importantly, I previously did an <a href="https://medium.com/@olgakostina_iot/types-of-satellite-networks-used-in-iot-solutions-de464672d16c">overview of what a LEO-enabled IoT solution looks like</a>, to help you follow the article.</p><p>Okay, we’re done with curtsies, let’s dance.</p><h3>How do Solution Providers choose the right LEO satellite network provider?</h3><p>The quickest answer is — whatever provider is the cheapest and can deliver reliable functionality, that is required by Solution Provider’s business case.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fgiphy.com%2Fembed%2FtlGD7PDy1w8fK%2Ftwitter%2Fiframe&amp;display_name=Giphy&amp;url=https%3A%2F%2Fmedia.giphy.com%2Fmedia%2FtlGD7PDy1w8fK%2Fgiphy.gif&amp;image=https%3A%2F%2Fmedia1.giphy.com%2Fmedia%2Fv1.Y2lkPTc5MGI3NjExZ2hvc2h1aGVpdXA0ZmlwODMwajFhNHVmM28zd2d6OWw3bmUyazA1MSZlcD12MV9naWZzX2dpZklkJmN0PWc%2FtlGD7PDy1w8fK%2Fgiphy.gif&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=giphy" width="435" height="261" frameborder="0" scrolling="no"><a href="https://medium.com/media/858a32c65b8c0390c71f318e4f60c45b/href">https://medium.com/media/858a32c65b8c0390c71f318e4f60c45b/href</a></iframe><p>Simple, right? But the devil’s in the detail, and there are lots of details.</p><h4>Due diligence on LEO-Sat</h4><p>There are 4 broad areas of due diligence that any Solution Provider does on a LEO satellite connectivity supplier.</p><ol><li><strong>Financial evaluation</strong> — is there business interest in engaging with this connectivity supplier?</li><li><strong>Technical evaluation</strong> — does this supplier satisfy Solution Provider’s technical requirements?</li><li><strong>Integration evaluation</strong> — is the integration with this connectivity supplier feasible and is the end-product usable for a customer and an end-user?</li><li><strong>Operational evaluation</strong> — can we scale our business with this connectivity supplier?</li></ol><p>Let’s dive into the due diligence questions that can make up the 4 areas to understand which considerations are contained within each. <strong>Or just scroll to the bottom if you want a downloadable LEO-sat qualification worksheet.</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*aEhu2qSHq4WzaZhDxmZ5Gg.png" /><figcaption>A due diligence checklist for IoT Solution providers to evaluate an IoT LEO satellite connectivity supplier. Color coding indicates relative importance for the items, red being the highest and gray — the lowest. Source: Olga Kostina.</figcaption></figure><h4>Financial Evaluation</h4><p><strong><em>LEO sat connectivity hardware costs fit the Solution Provider business case.</em></strong></p><p>For a Solution Provider, that integrates connectivity modem into the end-product, the LEO-sat hardware costs under 50 Euro (at scale) are favorable - in the majority of developed economies. But in use-cases with little financial gain, where the final IoT device would cost 20–40 EUR, the component price of 50 EUR isn’t be feasible. Depending on the use-case for the final product, the cost of supplied satellite hardware components “at scale” should be below 25–35% of the total end product bid of material.</p><p><em>Tier 1 Solution Provider </em>might incorporate the costs of hardware directly into their product BOM (the bid of material), therefore differentiating the satellite-enabled product by price.</p><p><em>Tier 2–3</em> <em>Solution Provider</em> would either incorporate the hardware costs into BOM or spread the costs over the service fees — maintenance, data management, or another add-on. Essentially, smallest Solution Providers with a defined customer base might be the most cost-sensitive.</p><p><strong><em>Solution Provider recurring profit margins are high.</em></strong></p><p>This is linked to the first point. Solution Providers experience pressure from supply chains with growing component prices, at the same time Solution Providers have to respect the market trend and keep the product and service prices low towards the end-customer.</p><p>While satellite connectivity is not cheap in general, in the situation of low margins every Euro per month counts.</p><p><em>Tier 1 IoT Solution Providers </em>generally have low margins in their solutions, so they look for cost-effective supply and scale.</p><p><em>Solution Providers in regulation-locked markets</em> might have higher (20–35%) margins since they are in a more advantageous situation towards an end-customer.</p><p><strong><em>The OPEX model of the LEO-satellite provider suits Solution Provider&#39;s commercial model.</em></strong><br> Apart from hardware, Solution Provider needs to re-package LEO-sat network recurring services (network access, add-ons like device management etc) into the end-product in a way that is comfortable for the whole value chain. Seems excessive to say that Solution Providers would prefer to have low recurring costs.</p><p><em>Tier 1 Solution Providers</em> tend to absorb annually prepaid satellite network airtime fees and add-on services and re-package them into annually-billed maintenance contracts billed directly to the end-customer. Though the customers are generally not price-sensitive, such construction helps to pass the Solution Provider offer through the customer’s procurement department, because the costs are predictable for the whole value chain.</p><p><em>Smaller Solution Providers</em> might be more sensitive about adding recurring airtime costs into their offering since their customers might experience “a bill shock”. If a Solution Provider solution requires regular maintenance, some recurring costs attributed to connectivity might be added to the maintenance fee or spread over the data management service subscription. Otherwise, smaller Solution Providers might avoid re-packaging airtime altogether and diffuse the customer cost exposure by sending their customers a separate bill for airtime from the satellite network supplier directly.</p><p><strong><em>The LEO-satellite network has access to Solution Provider target markets.</em></strong></p><p>The fact that the satellite network provider has satellites in space doesn’t mean that they can serve customers globally out of the box.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fgiphy.com%2Fembed%2FdBgbM7HVOgqNgKXN2c%2Ftwitter%2Fiframe&amp;display_name=Giphy&amp;url=https%3A%2F%2Fmedia.giphy.com%2Fmedia%2FdBgbM7HVOgqNgKXN2c%2Fgiphy.gif&amp;image=https%3A%2F%2Fi.giphy.com%2Fmedia%2FdBgbM7HVOgqNgKXN2c%2Fgiphy.gif&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=giphy" width="435" height="242" frameborder="0" scrolling="no"><a href="https://medium.com/media/b8bfc546e6c53a1c6acc668670ad0b1e/href">https://medium.com/media/b8bfc546e6c53a1c6acc668670ad0b1e/href</a></iframe><p>Sometimes LEO sat. provider needs to turn on the satellite above a new region — which is both a technical and a business decision. Also, sometimesa LEO sat. provider need permission from the local authorities to “land the data” from their satellites in a specific country (Russia, China, Brazil, etc). Therefore LEO-constellations might fly globally — but serve customers in a patchy pattern.<br><em>If Tier 1 Solution Provider</em> has a global customer base — the service area of the network is a big decision factor.</p><p><em>Smaller Solution Providers </em>might be more flexible — their customer base is local, also they can consider more flexible SLA-s during a pilot and commercial stage of (service level requirements, for example, 90% success rate of a message reaching a satellite over a day).</p><p><strong><em>Final product certifications costs are low.</em></strong></p><p>In essence, the more hardware certifications and process operation compliance certifications the LEO sat provider has, the easier it is for a Solution Provider to bring the new product to the market. <br>Solution Provider might need to recertify the new product if it includes a new radio-emitting element — an antenna and an (IoT) modem. The costs for this process depend heavily on the <br>a) target market radio certification regulation and <br>b) which certifications the satellite-enabling hardware already has. <br>These costs could be potentially shared between a satellite network provider and a Solution Provider.</p><p><strong><em>Longevity of an IoT LEO satellite network provider.</em></strong></p><p>The lead time to create a new product varies from 6 months for an agile Solution Provider to 18 months for a Tier 1 Solution Provider. <br>When the upfront investment in integration is high, the final product or solution should be sold for at least several years to create enough margins for a Solution Provider to cover those costs. Therefore, Solution Provider needs to conduct due diligence on the satellite network supplier, to make sure that the company would still be in operation in the next 10 years. That includes investigating the satellite network provider’s funding, the revenue streams, and cash reserves, potential B plan for lack of funding, etc.</p><p>The more Solution Providers have adopted the specific network supplier, the bigger the names are — the more reliable the brand seems.</p><p><em>Tier 1 Solution Providers </em>are the most sensitive towards this decision factor, though it matters for all Solution Providers.</p><p><strong><em>Production ramp-up speed can be high.</em></strong></p><p><em>Tier 1 Solution Providers</em> ramp up from 1–10K units for PoC (Proof of Concept) to 100K units for production. <br><em>Smaller Solution Providers</em> might ramp up to a smaller batch of 1–2K units before proceeding with 10–50K. <br>An IoT modem manufacturer — almost always a LEO service supplier themselves — must be able to match the required volume ramp-up of a Solution Provider for an uninterrupted product R&amp;D and roll-out.</p><blockquote>Solution Providers are, of course, concerned not only with a financial feasibility but also with the technical feasibility of the new product. Technical evaluation can be run in parallel to financial, by engaging the in-house technical expertise.</blockquote><h4>Technical Evaluation</h4><p><strong><em>LEO Hardware properties satisfy the requirements of the end-product.</em></strong></p><p>Firstly, satellite modem application needs to be <em>energy-efficient</em> unless the IoT device is planned to be mains-powered by the customer.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fgiphy.com%2Fembed%2F127JeHZl15PRII%2Ftwitter%2Fiframe&amp;display_name=Giphy&amp;url=https%3A%2F%2Fmedia.giphy.com%2Fmedia%2F127JeHZl15PRII%2Fgiphy.gif&amp;image=https%3A%2F%2Fi.giphy.com%2Fmedia%2F127JeHZl15PRII%2Fgiphy.gif&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=giphy" width="435" height="245" frameborder="0" scrolling="no"><a href="https://medium.com/media/2593e7d5926807385f36e5bf7d823268/href">https://medium.com/media/2593e7d5926807385f36e5bf7d823268/href</a></iframe><p>Satellite-enabled installations are generally very remote. Potentially without returning maintenance, or with a yearly maintenance cycle (can be more often in agriculture). Therefore, the whole IoT device needs to consume so little energy, so that it can survive a whole year on one industrial battery in varying environmental conditions. <br>Sattelite modems consume close to nothing in sleep mode, but during message transmission to sattelite the consumption spikes from microAmp to Amp levels for a few seconds. As a rule of thumb, the IoT end-product might allow the modem to consume about a third of a total budget on satellite communications. A good number for a modem is considered to be around 3Ah over a year for no mains-powered setup.</p><p>Secondly, it is beneficial if modem size doesn’t require a big redesign of the Solution Provider’s end-product. Many Solution Providers would repurpose their product from a cellular-enabled IoT device into a satellite-enabled one. Therefore it means fewer costs on re-design if a new modem footprint is comparable to the legacy modem’s footprint. Bigger Solution Providers with longer development processes are more sensitive to product re-design.</p><p><strong><em>LEO Service properties satisfy the requirements of Solution Provider commercial service.</em></strong></p><p>Solution Provider buys first a modem and then — access to the satellite provider’s network — in space and on the ground. Major network performance characteristics and properties, that are a consideration for a Solution Provider:</p><ul><li><em>Duplex (two-way) satellite link</em> — allows to poll sensor data and to push commands down to devices to change message frequency, to actuate the device [e.g. turn on the light on an oil rig in the sea] or to send the firmware update down to the modem.</li><li><em>Message frequency is high enough</em> — regulatory use-cases for groundwater level might require one averaged sensor reading per day to view the trend, while a weather station — an agricultural IoT device that reads a local microclimate in the crop field might require 100 readings per day with a high message rate to view the dynamics. Solution Provider would choose an LEO-satellite network that can either deliver the required message frequency now, or that conveys assurance in the growth of satellite constellation to enable the higher message frequency in an observable future.</li><li><em>Sattelite service quality doesn’t affect the end-product SLA.</em> <br>Service quality is expressed through service level agreements (SLA) that stipulate the service characteristics, for example, 99% availability per year, 90% reliability and Support team on standby. As Solution Providers include satellite networks into their product, satellite SLA should not degrade the customer-facing SLA — “the chain is as strong as its weakest link”. <br>For a Solution provider it is crucial to consider how many messages can 1 sattelite pick up from one “footprint” area — if a hundred of co-located devices are sending payload, and the bandwidth is constrained, data might be lost. Network reliability assurance is an important discussion to have with your provider-to-be, to know how many messages can go through the channel simultaneously.<br>Bigger Solution Providers commit to a high service quality directly to their end-customers, traditionally in critical verticals, like governmental, flood-, fire-prevention or oil, gas, and mining with continuous production. <br>Smaller Solution Providers might expose satellite network SLA directly to the customer, being concerned only with selling the device data and not packaging the connectivity into the end product.</li><li><em>Customer data is secure. </em>In a few sectors like governmental, energy, or medical, end-to-end data encryption is required. <br>Solution Provider needs to ensure that with the introduction of a new service the data, passing through the system, is protected. Data take paths over an air link, over an IP link between the satellite dish and a locally-deployed data center, and then over the link to the client’s cloud. LEO service providers might need to invest in local ground stations and hosting in local data centers to comply with a few critical use-cases.</li></ul><p><strong><em>Environmental protection of antenna fits the end-product use-case.</em></strong></p><p>IoT Solution Providers beforehand know specific environmental limitations, imposed onto their end-product.</p><p>Such limitations might include: burying equipment in sand, exposure to marine (salty) air, water splashes, regular sun radiation, extreme cold, chemical exposure — that has to be mitigated by the hardware protection levels, assured by the hardware supplier — i.e. LEO satellite provider.<br>Before testing the end-product in a real-life pilot with actual users, Solution Provider might want to assess the <a href="https://en.wikipedia.org/wiki/IP_Code">protection rates</a> for any complementary non-embeddable hardware, like satellite antennas and connecting cables.</p><p><strong><em>Modem application satisfies Solution Provider application requirements.</em></strong></p><p>If I oversimplify, the modem’s firmware application allows the satellite modem to accept an input from an IoT sensor (e.g. soil moisture %), package the moisture % payload into a message, and send this message up to the satellite with a given schedule.</p><p>Solution Providers might want to have a bit more variety to the modem’s application, depending on the end-product use-case.</p><p>Most importantly, when the modem pushes up the message, Solution provider pays for every bit of that. The cheapest connectivity costs don’t matter if your edge application is not smart enough to reduce your data from a hundred messages to one with an averaged value with spikes of deviaitons over a day. While the energy is definitely a tradeoff, a basic <em>edge data analytics application module </em>goes far.</p><p>In high-risk use-cases — flooding/fire prevention, soil and water contamination Solution Provider might prefer the modem to be able to <em>send an</em> <em>unscheduled</em> <em>alarm message</em> or <em>increase message frequency based on a threshold value</em> for more regular updates.</p><p>In highly remote use-cases — when the nearest support team is thousands of kilometers away from the equipment, the modem might be required to initiate a “<em>remote restart</em>” to bootstrap satellite service or to <em>send an alarm</em> when the <em>device sensor is not responding</em>. Additionally, it is important to identify the radio fading — e.g. by a regular <em>reconciliation message </em>(not containing any sensor payload)<em> with RSSI —</em> in existing installations to avoid service degradation.</p><p>It is hard to define the best message payload size for all Solution Providers due to a wide variety of types of objects of monitoring. Sometimes <em>more than one sensor is connected to a modem</em>, so it can be beneficial to <em>differentiate different sensors within one message</em> and <em>allow different message sending schedules per sensor</em>.</p><p>Also, more advanced Solution Providers manufacture IoT devices with multiple connectivity options, with an ambition to enable satellite modem on-demand as a <em>“fall back”</em> costlier option, in case more affordable cellular is out of range.</p><p><strong><em>The modem is compliant with specific industry certifications.</em></strong></p><p>Solution Provider might be producing products for highly regulated industries, such as energy, aviation, or automotive.</p><p>In e.g. energy sector — oil and gas — the equipment must be explosion-safe, certified with <a href="https://www.gore.com/resources/iecex-atex-defining-and-certifying-explosion-protected-ex-safety-standards">ATEX, IECEx</a>, or others. <br>When a new radio-emitting element is integrated, Solution Provider might need to re-certify the end-product. LEO sat modem and antenna, therefore, must have such current and transmission power characteristics so that it can easily pass the re-certification tests.</p><blockquote>After a theoretical evaluation comes a practical one — Solution Provider gets a few modems or a devkit in to access the hardware and service quality.</blockquote><h4>Integration Evaluation</h4><p><strong><em>LEO supplier supports the integration project.</em></strong></p><p>Development of a new satellite-enabled IoT device costs around 100K Euro, and every day that is spent without a satellite service to test the prototype or without necessary documentation lowers the future margins for Solution Provider. These costs are influenced by the support provided by the modem manufacturer — documentation and developer support.</p><p>The integration project is the first real business process that a Solution Provider and satellite modem manufacturer go through together — it would show the level of technological readiness of both companies and establish mutual trust, which would be required for the pilot stage in the product development.</p><p>The process of the integration should be rapid so that Solution Provider leaders don’t pull the plug on the project.</p><p><strong><em>The final product (with sat. antenna) is usable in a given use case for an end-user.</em></strong></p><p>Solution Providers try to fit their end-product to multiple use-cases, and satellite antenna’s size and performance must satisfy them all.</p><p>If a farmer wants to optimize the crop yields, IoT devices would be installed on the field; with plant growth, the antenna might eventually sit beneath the vegetation — which inevitably worsens the satellite signal quality. With a heavy antenna, it might be not economically viable for the farmer to create a mounting installation to secure an IoT device.</p><p>Similarly, with tree monitoring, the antennas might be overshadowed by the foliage — signal worsening on sub-GHz bands or exposed to chemical sprinkling to draw away pests. <br>Bright-colored or shiny antennas might become subject to vandalism or theft. Most Solution Providers that deploy equipment remotely, say that it “should look ugly”.</p><p>Antenna’s size is definitely a factor for Solution Providers — in most use-cases, the IoT device is relatively small, the estate space to install the antenna is small too, thus a device with a bulky antenna can’t be secured (e.g. groundwater bores for water monitoring or residential propane tanks). End customers might even compromise on network reliability if they can exercise interesting use-cases with a smaller Iot device.</p><p>The end product also should be out-of-the-box installable for an end-user, so that no technical knowledge is required after receiving a shipment in the most remote place on Earth.</p><p><strong><em>Developer documentation, reference design, and application examples are present.</em></strong></p><p>Solution Provider engineers would be among the first ones to decide whether LEO satellite service is good. And then they would be the ones to make sure that the product R&amp;D is done quickly. <br>The hardware and service properties, physical dimensions of the hardware, and hardware functionalities can be reliably evaluated through developer documentation. Therefore many LEO modem manufacturers publish all documentation — see, for example, a comprehensive <a href="https://swarm.space/developertools/">SWARM guide</a> or <a href="https://developer.myriota.com/technical-documentation">Myriota portal</a>.</p><p>It is great when modem manufacturer has developed several reference applications utilizing modem APIs to speed up product development for Solution Provider’s engineers.</p><p>Apart from the hardware R&amp;D, Solution Provider needs to integrate with the satellite network’s backend for operations — advanced web-APIs and extensive documentation mean a quick service pilot and take-off.</p><p><strong><em>Development Kit is present.</em></strong></p><p>Devkit is an easy-to-assemble-and-deploy sample IoT device with a satellite network modem, antenna, a simple sensor or sensor connector. It can be purposed to validate the quality of the satellite networks or used as a development platform for Solution Providers to try new product ideas.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fgiphy.com%2Fembed%2FeYqCcqAhvsxqoMUi0z%2Ftwitter%2Fiframe&amp;display_name=Giphy&amp;url=https%3A%2F%2Fmedia.giphy.com%2Fmedia%2FeYqCcqAhvsxqoMUi0z%2Fgiphy.gif&amp;image=https%3A%2F%2Fi.giphy.com%2Fmedia%2FeYqCcqAhvsxqoMUi0z%2Fgiphy.gif&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=giphy" width="435" height="244" frameborder="0" scrolling="no"><a href="https://medium.com/media/c3134f607a94df187af21a208c5339d9/href">https://medium.com/media/c3134f607a94df187af21a208c5339d9/href</a></iframe><p>Solution Provider might go forward with a modem supplier even without a Development Kit if there is enough trust in the supplier and enough LEO-sat experience in-house.</p><p>Large IoT Solution Providers would usually use the DevKit as means to convince internal stakeholders about new technology for the new product line. It is a quick demo without a big FTE commitment.</p><p>More agile Solution Providers would use a DevKit to validate the satellite technology quickly with a few friendly customers.</p><blockquote>Through the operational evaluation, Solution Provider can assess how scalable the new IoT product line would be with a given satellite network provider.</blockquote><h4>Operational Evaluation</h4><p><strong><em>Component registering into Solution Provider’s ERP is scalable.</em></strong></p><p>A Solution Provider might want to check if LEO satellite providers can dynamically change the service level of their modems over the air. If not, it would be important for a Solution Provider to unilaterally identify the LEO modems on their production line and couple their meta-data with the meta-data of the end product. <br>The responsibility for registeration of the components lies on the Solution Provider, but the modem supplier should be able to comply with the requirements imposed by Solution Provider’s production line.</p><p>Bigger Solution Providers might invest in the production line automation — smart cameras reading out a QR code on a modem, then pairing a future device with the modem in the Solution Provider’s stock management system, and passing the pairing info back to the satellite service supplier for Support.</p><p>Smaller Solution Providers might use the MQTT protocol for meta-data modem registering at volume roll-out. The key enabler is open APIs to the satellite network provider’s back-end.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fgiphy.com%2Fembed%2FSSM6HdOicCahnOZ5hM%2Ftwitter%2Fiframe&amp;display_name=Giphy&amp;url=https%3A%2F%2Fmedia.giphy.com%2Fmedia%2FSSM6HdOicCahnOZ5hM%2Fgiphy.gif&amp;image=https%3A%2F%2Fi.giphy.com%2Fmedia%2FSSM6HdOicCahnOZ5hM%2Fgiphy.gif&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=giphy" width="435" height="222" frameborder="0" scrolling="no"><a href="https://medium.com/media/8dbd8f7a118828bad3d8339c82419827/href">https://medium.com/media/8dbd8f7a118828bad3d8339c82419827/href</a></iframe><p><strong><em>Remote IoT device provisioning into the network is scalable.</em></strong></p><p>Upon delivery, after the IoT device is powered up, the device needs to be provisioned into the network — customer’s name, IoT device ID, service level, location, potentially — reseller’s name, etc have to be all linked together for an accurate airtime service and billing.</p><p>Satellite-enabled end-products would reach their end customer via multiple channels — directly — physical sales or online sales, or indirectly — via local resellers and system integrators.</p><p>The LEO sat provider should be able to support this complexity through any sales channel, anywhere in the world, in most remote places, also with varying satellite service quality. Without automation of the device onboarding process, it is extremely difficult to scale beyond thousands of devices.</p><p><strong><em>Satellite service activation and billing are scalable.</em></strong></p><p>LEO service activation on a device might trigger the associated billing package. And it’s not always, that the use-case of Solution Provider benefits from this coupling.</p><p>Many end-customer product installations might be compromised by theft or planned activation might be delayed due to logistical issues, therefore there should be automated processes for SLA-compliant service activation and deactivation. Satellite service activation and deactivation could be managed by a Solution Provider directly (if there is a robust API integration between the LEO satellite network provider and Solution Provider’s back-end) or by a LEO network provider following the Solution Provider’s request.</p><p>In regard to billing, Solution Providers and Network providers would honestly prefer to have ”service payment controls” within their quick reach to change the billing model for the seasonal cadence of harvesting or a delay caused by equipment relocation.</p><p><strong>Onboarding on the1st line support is easy and provided 2nd line support is efficient.</strong></p><p>LEO supplier would show operational maturity if they have established the 2nd line support flows for the end-customers. It’s even better if the satellite network provider can expose network monitoring tools to the Client and provide sufficient training to Solution Provider’s personnel, so that network monitoring and 1st line support are onboarded quickly.</p><p>This is by no means an exhaustive list of evaluation points for a Solution Provider to choose an IoT satellite network provider, but it is definitely a great list to cover the bases for any product manager.</p><h3>To summarize,</h3><p><strong><em>Tier 1 Solution Provider Make-or break factors to choose an IoT LEO Satellite provider.</em></strong></p><p>Financial evaluation:<br>- Longevity of an IoT satellite network provider<br>- Easy to ramp up production to hundreds of thousands of devices</p><p>Technical evaluation:<br>- End-to-end customer data security<br>- Network coverage of satellite network is sufficient</p><p>Integration evaluation<br>- The cost of integration is low (average integration takes 18 months)</p><p>Operational evaluation<br>- Customer onboarding is automated.</p><p><strong><em>Tier 2–3 Solution Provider Make-or break factors to choose an IoT LEO Satellite provider.</em></strong></p><p>Financial evaluation:<br>- The end-to-end total cost of ownership (TCO) of the end-product is low<br>- Operational expenditure (OPEX) is low</p><p>Technical evaluation:<br>- Network coverage of satellite network is sufficient<br>- The power performance of the modem fits the power profile of the use-case, the modem is highly low-power.</p><p>Integration evaluation<br>- The integration is fast and the integration cost is low (average integration takes 6 months)</p><p>Operational evaluation<br>- Start/stop billing is automated</p><h3>Go ahead and download the checklist to evaluate your next LEO satellite connectivity supplier!</h3><p><a href="https://docs.google.com/spreadsheets/d/1B9WpvQlPNMXdDg2oT7706wph5xh44rnqc-T0sdfCHx0/edit#gid=891834841">Public LEO-Sat supplier evaluation by Olga Kostina (Make a File COPY to adjust)</a></p><p>Write me or comment below if you find it helpful or if there are more consideration points!</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fgiphy.com%2Fembed%2Fl3V0nKt696ClG9Xws%2Ftwitter%2Fiframe&amp;display_name=Giphy&amp;url=https%3A%2F%2Fmedia.giphy.com%2Fmedia%2Fl3V0nKt696ClG9Xws%2Fgiphy.gif&amp;image=https%3A%2F%2Fi.giphy.com%2Fmedia%2Fl3V0nKt696ClG9Xws%2Fgiphy.gif&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=giphy" width="435" height="230" frameborder="0" scrolling="no"><a href="https://medium.com/media/ff897ba89135f6dd831af6588f2f232e/href">https://medium.com/media/ff897ba89135f6dd831af6588f2f232e/href</a></iframe><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=90d30cf9bfe4" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Types of satellite networks used in IoT solutions]]></title>
            <link>https://medium.com/the-iot-magazine/types-of-satellite-networks-used-in-iot-solutions-de464672d16c?source=rss-3bc4a5230a9d------2</link>
            <guid isPermaLink="false">https://medium.com/p/de464672d16c</guid>
            <category><![CDATA[satellite-technology]]></category>
            <category><![CDATA[iot-solution]]></category>
            <category><![CDATA[iot]]></category>
            <category><![CDATA[iot-network]]></category>
            <category><![CDATA[oem-manufacturers]]></category>
            <dc:creator><![CDATA[Olga Kostina IoT Whiz]]></dc:creator>
            <pubDate>Sat, 15 Jan 2022 21:57:12 GMT</pubDate>
            <atom:updated>2022-01-16T20:39:45.098Z</atom:updated>
            <content:encoded><![CDATA[<h3>There’s More Than One? Types Of Satellite Networks Used in IoT Solutions.</h3><p>This article is a part of my series of articles about <a href="https://medium.com/@olgakostina_iot/which-types-of-customers-are-out-there-for-an-iot-modem-manufacturer-db69136cc4fe">Original Equipment Manufacturers (OEMs)</a> that procure satellite IoT services to build better IoT products. <br>To build a satellite-enabled IoT solution, OEM integrates a satellite IoT modem into their product. That allows OEM customers to connect to the IoT satellite network; depending on the IoT solution architecture and value chain, OEM can offer a user dashboard with IoT data or use a white-labeled solution from the network provider or a third party.</p><p>I realized that Internet hasn’t produced a high-level overview of satellite networks that can be used in IoT solutions. It&#39;s time to correct that for all the curious product-, sales-, engineer- and entrepreneur-people out there.</p><p>⬇ Also, scroll all the way down for an overview of satellite-enabled IoT solutions!</p><p>Naturally, all satellites use <a href="https://www.esa.int/Enabling_Support/Space_Transportation/Types_of_orbits">orbits</a> — orbits can be as high as thousands of kilometers above the Earth’s surface (geostationary orbit GEO), all the way down to hundreds of kilometers (low-earth orbits LEO).</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*xhTDvzqSvIRMWdk3nXBWfA.png" /><figcaption>Orbital altitude for GEO, MEO, and LEO satellites. <a href="https://www.satellitetoday.com/content-collection/ses-hub-geo-meo-and-leo/">Source</a>.</figcaption></figure><p>Massive <strong>GEO-satellites</strong> sit on the geostationary orbit, which allows them to rotate in sync with our planet, hence GEO-satellites always “look down” on the same big area, called <em>footprint</em>. Typically a GEO-satellite network consists of very few satellites — a <em>constellation</em>, that cover the whole globe with connectivity.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/608/1*iE4i4LTbdeeLWMPtgBHNvA.jpeg" /><figcaption>Here are the 3 footprints of 3 GEO satellites by one of the major GEO satellite service providers. <a href="http://www.marinesatellitesystems.com/index.php?page_id=125">Source</a>.</figcaption></figure><p>Geo-satellites mean</p><ul><li>big solar panels — hence, high power output into an IoT link down to Earth,</li><li>powerful antennas — hence, a lot of data can be sent up and down,</li><li>uninterrupted IP link with the receiver on the ground — hence, a continuous flow of IoT data.</li><li>Geo-satellites are in operation for decades and they can continuously upgrade their software, which means a reliable technology partner for an OEM that buys into the satellite service.</li></ul><p>All the perks are balanced out by a high service bill, that customers pay for a slice of the GEO network.</p><blockquote>A lot of resellers of satellite IoT solutions are upselling bill optimization mechanisms.</blockquote><p>On the other end of the satellite service spectrum are the compact (sandwich-box to shoe-box in size) <strong>LEO-satellites</strong> that occupy low-earth orbits or a sun-synchronous orbit.</p><p>Their path above the globe might look like a knife peeling an apple — a <a href="https://images.app.goo.gl/wN3V8M1Z12xf6hcA8">gradually shifting signal footprint</a>, that eventually revisits the same spot with a given cadence. LEO satellite footprint is also relatively small compared to the bigger GEO-sibling — only a few hundred kilometers. Sattelite network providers mitigate signal interruption, as a LEO-satellite moves away, by having a big constellation of LEO-satellites with smooth signal handover.</p><ul><li>Small satellites have a shorter lifespan in space — network providers need a lot of them to have a reliable operation,</li><li>they have a smaller energy supply — hence, the signal received and sent down is lower in power.</li><li>Luckily, the signal latency is also lower due to the shorter distance from the surface, which helps in critical IoT applications.</li><li>The quality of the service depends on the number of satellites in service — if the number is low the link is interrupted for a longer period of time and IoT data is collected with time gaps.</li></ul><blockquote>Minimizing those gaps is, therefore, a price differentiator, and the main motivator for new LEO startups to launch as many satellites as possible to catch up with established LEO players, like Iridium and Orbcomm, who charge now premium.</blockquote><p>LEO satellite IoT network and solution providers include Myriota, Kineis, Astrocast, Kepler Communications, SWARM technologies (bought by SpaceX), Starlink (in a Very-low orbit), Orbcomm, Iridium.</p><p>Anywhere in between the orbits of GEO and LEO satellite are Medium Earth Orbit MEO-satellites. In my experience MEO-satellite services are used for maritime navigation and crew communications, therefore not serving many IoT-related use-cases just yet, though maritime logistics is going to win a lot from it.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*UUsXdUwycfgU4pm-wlaMPA.png" /><figcaption>Types of IoT satellite networks, with objects of monitoring and the ground infrastructure that facilitates the network. This graph also illustrates the composition of a satellite-enabled IoT solution, that provides IoT data insights to the end-user. Source: Olga Kostina.</figcaption></figure><p>While the space segment differentiates a lot per each network type, the ground part of each network is roughly similar — IoT device with a satellite antenna that transmits IoT sensor data (and receives control commands), satellite dish — a local data sink for any satellite — that connects to the network; the network delivers IoT data to the data center and, eventually, there is an endpoint for a user to view the IoT data.</p><p><em>Disclaimer: This is an article from my series of articles about IoT modem manufacturers: the value chain, the business, the risks, the customers. Articles are not sponsored, this is not company-specific marketing, but it is a collection of publicly available insights, delivered with love for IoT.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=de464672d16c" width="1" height="1" alt=""><hr><p><a href="https://medium.com/the-iot-magazine/types-of-satellite-networks-used-in-iot-solutions-de464672d16c">Types of satellite networks used in IoT solutions</a> was originally published in <a href="https://medium.com/the-iot-magazine">The IOT Magazine</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Which types of customers are out there for an IoT modem manufacturer?]]></title>
            <link>https://medium.com/@olgakostina_iot/which-types-of-customers-are-out-there-for-an-iot-modem-manufacturer-db69136cc4fe?source=rss-3bc4a5230a9d------2</link>
            <guid isPermaLink="false">https://medium.com/p/db69136cc4fe</guid>
            <category><![CDATA[technology]]></category>
            <category><![CDATA[oem-manufacturers]]></category>
            <category><![CDATA[iot]]></category>
            <category><![CDATA[business]]></category>
            <category><![CDATA[internet-of-things]]></category>
            <dc:creator><![CDATA[Olga Kostina IoT Whiz]]></dc:creator>
            <pubDate>Wed, 22 Dec 2021 21:19:39 GMT</pubDate>
            <atom:updated>2022-01-15T22:17:03.672Z</atom:updated>
            <content:encoded><![CDATA[<h3>Which Companies Buy IoT Modems? Let’s Talk IoT B2B(2B).</h3><p>I thought to start writing and sharing my experiences about terrestrial &amp; satellite B2B(2B) IoT world on Medium for people that work with IoT in the Product, Sales, and Technical teams, but also for people who are interested in the IoT supply chain outside of the B2C context. <br>In my time, I spent lots of time looking for this type of information, I was wildly frustrated with the scarcity of it — there was plenty to read about smart home set-ups, or about e.g. IoT Hub in Microsoft or IoT web-service of Amazon for cellular-enabled IoT devices, but nothing about business relationships for B2B(2B)in terrestrial and space IoT.</p><p>I hope this and the following articles might be helpful, as well as mildly entertaining to you.</p><p><strong>So, to rephrase, which companies would buy an RF (radio-frequency)-enabled IoT modem from the IoT network providers (if they also build modem) or from IoT modem manufacturers?</strong></p><blockquote>RF Connectivity options for IoT are plentiful.</blockquote><p>Any company that manufactures an RF modem that is low-cost AND/OR low-energy AND/OR for a long-range network, can be roughly considered an IoT modem manufacturer.</p><figure><img alt="IoT modems for different RF options from varying modem suppliers." src="https://cdn-images-1.medium.com/max/1024/1*YKLx_RXoDxjqvYtlgnJ3DA.png" /><figcaption>Just a few IoT modems supporting different radio frequency communication technologies. Image source: Olga Kostina.</figcaption></figure><p>Modems can vary from Near-field NFC RF (not in the image), LPWAN RF — such as LoRa and derivatives, cellular RF all the way to satellite RF. And given specific modem and RF properties such as low cost, low energy consumption, signal robustness, duplex signal, etc the modem might make it to the IoT device manufacturer’s or an original equipment manufacturer’s wish list.</p><p>IoT modems would find themselves to be part of varying IoT devices and solutions:</p><ul><li>environmental meters — soil moisture meter, air quality meter;</li><li>utility metering devices — IoT device that reads the analog output of i.e. your water meter and sends the data over RF to a local gateway;</li><li>industrial IoT devices that communicate the status of the monitoring equipment;</li><li>monitoring IoT devices that frequently or in real-time transmit telemetry data — trackers, data acquisition hubs;</li><li>bigger equipment that requires an IoT dimension for safety, operational, or business model purposes — equipment for rent, expensive or luxury items, logistics containers.</li></ul><h4><em>The typical customers for an IoT modem manufacturer:</em></h4><p><strong>Original Equipment Manufacturers (OEM)</strong> are generally the companies that produce components or complete products for resellers, that bring the final product to the end-customer. Generic OEMs primarily operate in B2B space and rarely are recognized by a regular consumer.<br>Nevertheless, the specifics of the IoT world — structural complexity and a wide spectrum of possibilities, leverages the capabilities of OEMs to reach all the way to the end-customer directly.</p><p>OEMs can be global (Tier 1) and local (Tier 2–3). There are roughly 200 Tier 1 OEMs — <a href="https://www.honeywellforge.ai/us/en/home">Honeywell</a>, <a href="https://global.abb/topic/ability/en">ABB</a>, <a href="https://www.advantech.com/embedded-boards-design-in-services/embedded-iot/iotsoftwaresolutionsanddistribution">Advantech</a>, etc. would produce IoT equipment as well as supply the whole IoT connectivity solution with services to the end-customer.</p><p>Therefore IoT OEMs of all sizes that procure RF modems can be roughly split into 2 types.</p><ol><li>Device Manufacturers — those OEMs sell IoT devices — hardware plus occasional software for device management and simple IoT data management.</li><li>Solution Provider — these companies take a step further from Device manufacturers and include monitoring and maintenance services into their offering. OEM Solution providers that create large items like farming equipment or heating and ventilating units might be inclined to rent out their equipment with a maintenance add-on service.</li></ol><blockquote><em>Global Tier 1 OEMs might spend a lot of time choosing a new RF modem for their product line</em> since this choice would affect the next 6–10 years of OEM’s business operations.</blockquote><p>The decision is primarily <em>cost- and reliability-driven</em> and it originates in a business development unit, supported by an R&amp;D department. <br>An introduction of a new connectivity technology within a product line means among others an R&amp;D investment, an adjustment to operations, logistics, sales, and customer support.</p><p>Global OEMs like <a href="https://zenner.com/">Zenner</a>, <a href="https://miromico.ch/?lang=en">Miromico</a>, <a href="https://aiut.com/en/">AIUT</a>, <a href="https://global.abb/topic/ability/en">ABB</a>, <a href="https://www.se.com/au/en/work/campaign/innovation/industries.jsp">Schneider Electric</a> or <a href="https://www.ptc.com/en/technologies/iiot">PTC</a> might produce above 200K IoT units per year with a specific RF modem, thus the confidence in the radio technology quality and modem supplier longevity must be high.</p><p>In order to assess fitting modem options and cut the chase, hence time-to-market, Tier 1 OEMs might contract a System integrator or an IT Consultant (like Accenture) to research and evaluate different modems and, thus, shorten the decision making (see infographics below).</p><blockquote>Smaller Tier 2 and Tier 3 or local OEMs are more agile.</blockquote><p>They differ mainly by the speed with which they can assess a new modem and see a potential fit for their market. Such OEMs are characterized by a) small size — less than 200 people employed, b) representation in one or two markets, 3) smaller production volumes — up to 10K units per year. There are roughly 1500 Tier 2-Tier 3 IoT OEMs out in the world.</p><p>In OEMs, like <a href="https://dfmtechnologies.co.za/">DFM Technologies</a> or <a href="https://centaur.ag/farmer-solutions/">Centaur</a>, tech departments that test new RF modems have a short feedback cycle to the management (folks could be working in the same space as an IoT branch CTO or CEO) hence the procurement cycle for a new modem takes about a half or a third of the time required by Tier 1 OEM companies. Rarely any external companies are involved in taking a decision to procure a connectivity modem for a smaller OEM.</p><p>The decision is <em>CAPEX (CAPital EXpenditure)- and performance-driven</em> and is pushed by the Head of the IoT department.</p><blockquote>The general trend for all device manufacturers within most verticals is to leverage the IoT device data through own data aggregation or visualisation platform solutions.</blockquote><blockquote>Any of the links above would land you into a webpage that focuses on a OEM platform. The degree of interoperability of these platforms is currently low. <br>IoT devices at this point are the entry gates that allow an OEM to get the customer to buy into a proprietary platform. Such approach might potentially lock in an end-customer in the OEM-specific IoT platform solution.</blockquote><p><strong>Another type of RF modem buyer is more region-specific —</strong></p><p><strong>a Local (value-add) reseller.</strong></p><p>Countries like China, Russia, Australia, Brazil, Indonesia, etc require specific compliance for commercial radio frequency usage, usually on top of global radio electronics certifications, like CE, FCC, etc. The IoT modem manufacturer might need to obtain governmental permission to use the modem frequency in the country of interest. If the modem manufacturer also allows customers to connect to a proprietary network, like many satellite network operators do — Myriota, Orbcomm, Iridium; then the modem maker needs to become a licensed operator in the target country. That is usually <em>expensive – </em>heavy on time, and CAPEX, hence — a big market entry blocker for smaller modem manufacturers and network operators.</p><p>Salvation comes from a (value-add) reseller — a local network operator or solution provider that already holds the rights for the required frequency band in the country or holds the permissions to enter the market with locally-certified IoT solutions. Such resellers, i.e. <a href="https://www.pivotel.com.au/">Pivotel</a> in Australia, <a href="https://www.marsat.ru/en/enterprise">Morsvyazsputnik</a> in Russia, comply with the data security and regulatory requirements locally and act as an agent that allows IoT modem manufacturers into the market for, usually, a mark-up fee.</p><p>A reseller might just resell the modem downstream to the local OEM or an end customer locally, or ‘add value’ by providing integrated solutions.</p><p>Globally there are roughly 150 resellers that allow a market entry for RF modem manufacturers, coupled occasionally with a network access license.</p><p>Resellers tend to evaluate IoT modems based on <em>connectivity reliability, possibilities to ramp up production</em> (ideally, 10K units a year), and <em>costs to land the product locally</em>. Depending on an agreement a local reseller might share some certification and localization costs with an IoT modem manufacturer, or take the costs completely on themselves.</p><p>I find a global overview below very helpful: you can see which companies buy an IoT modem on the left and on the right there are the potential end customers for the final OEM product. The list of the end customers is far from exhaustive.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*_Ar_8EPQnYNFX4MAstUOGQ.png" /><figcaption>A generic IoT modem value chain. Image source: Olga Kostina.</figcaption></figure><p>This way you can really appreciate the ultra-wide reach that IoT modem manufacturers might have. Just one of the above modem manufacturers has more than <a href="https://www.semtech.com/lora/what-is-lora">225</a> million modems deployed across continents and use-cases. The total is growing each day.</p><p><em>Disclaimer: This is an article from my coming series of articles about IoT modem manufacturers: the value chain, the business, the risks, the customers. Articles are not sponsored, this is not company-specific marketing, but it is a collection of publicly available insights, delivered with love for IoT.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=db69136cc4fe" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>