<?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 CJ Boguszewski on Medium]]></title>
        <description><![CDATA[Stories by CJ Boguszewski on Medium]]></description>
        <link>https://medium.com/@cj_58073?source=rss-e8f8f7d93e80------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*ZN6yxqpU3wmEiDxTztCogg.jpeg</url>
            <title>Stories by CJ Boguszewski on Medium</title>
            <link>https://medium.com/@cj_58073?source=rss-e8f8f7d93e80------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sun, 22 Nov 2026 19:10:42 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@cj_58073/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[AWS Greengrass Announcement]]></title>
            <link>https://medium.com/iotforall/aws-greengrass-announcement-ca75ce1f7940?source=rss-e8f8f7d93e80------2</link>
            <guid isPermaLink="false">https://medium.com/p/ca75ce1f7940</guid>
            <category><![CDATA[cybersecurity]]></category>
            <category><![CDATA[internet-of-things]]></category>
            <category><![CDATA[news]]></category>
            <category><![CDATA[cloud-computing]]></category>
            <category><![CDATA[technology]]></category>
            <dc:creator><![CDATA[CJ Boguszewski]]></dc:creator>
            <pubDate>Mon, 03 Jul 2017 19:10:42 GMT</pubDate>
            <atom:updated>2017-08-03T19:37:28.366Z</atom:updated>
            <content:encoded><![CDATA[<h4>6 Key Takeaways</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*OkEybU32W567dRI79RDmwA.jpeg" /></figure><p>When Andy Jassy announced the release of AWS Greengrass in Limited Preview back in November at AWS re:Invent 2016, the show floor was buzzing for hours. And for good reason — AWS Greengrass promises to power up what we call “the Edge” by allowing connected devices to run local compute, messaging, data caching, and synch capabilities securely, even when they’re not connected to the Internet.</p><p>And while connectivity stands at the core of IoT, if you’re developing or deploying connected devices you know you can’t always count on a steady connection. AWS Greengrass also lets one device act as a hub for others, so they can save energy by keeping data connections with a local intranet.</p><p>So the recent announcement of <a href="https://aws.amazon.com/blogs/aws/aws-greengrass-run-aws-lambda-functions-on-connected-devices/">general availability for AWS Greengrass </a>is a big deal for IoT developers. It’s an important new component in the Cloud toolkit that powers IoT, and gives us 6 things to consider immediately:</p><h3>Key Takeaways from AWS Greengrass Announcement</h3><h4>1. Software Skills Are Now More Portable to IoT</h4><p>Greengrass moving more of what software developers do to the edge of the network is a major inflection point.</p><p>The enormous software developer community is already moving into IoT, and tools like AWS Greengrass will help them to dominate the space over time. Their familiarity with programming in languages like Python and writing lambdas to process streaming data in-flow now becomes applicable on the other side of the “choke point.”</p><h4>2. Connectivity is More Important Than Ever</h4><p>That choke point has always been, and will continue to be, cellular opex. When it comes to connectivity, IoT developers need solutions that are simple, reliable, and flexible.</p><p>Current product offerings rarely deliver on all three, and often burden projects with significant commercial and technical constraints even during development and testing. Signing complicated contracts in the prototype stage, when there’s no guarantee that devices will even work as designed, can still require a years-long upfront commitment that still amounts to small potatoes from the provider.</p><p>And if that weren’t challenging enough…</p><h4>3. Efficiency Still Matters, Even at the Edge</h4><p>Each meaningful communication between a device and the cloud comes with the burden of retransmitting repetitive, undifferentiated data related to security, encryption, and packet headers.</p><p>A significant portion of IoT cellular opex — from as “little” as 25% to as much as 75% or more in many cases as — is related directly to this overhead or “connectivity tax.”</p><p>It would be highly preferable from both a performance and a cost perspective to transmit only the meaningful data: which device is this, what does the register read, and nothing extraneous.</p><h4>4. Your AWS Competency Now Unlocks Edge Computing Capability</h4><p>While software developers are naturally curious and like to learn, sometimes it’s great to be able apply existing skills to an expanded set of problems. As offerings like AWS Greengrass bring the “software development environment” further downstream to ever-more-constrained device environments, the horsepower, elasticity, and agility of the cloud environment will provide greater and greater leverage.</p><p>More importantly, the hundreds of thousands of developers who are already capable of writing functions in lambda can now process large streams of data on the edge of the network, and transmit only the relevant information across the cellular network.</p><p>Think, for example, of a video streaming application to which a filtering function is applied, sending only the relevant information (car make, car model, number plate, time of day, GPS coordinate or space number) to the cloud when exception conditions are met.</p><h4>5. The Total Package for IoT is Almost Here</h4><p>Device-based environments like AWS Greengrass promise a new, easier IoT featuring:</p><ul><li>Familiar development tools</li><li>Pre-processing on constrained devices</li><li>Minimized cellular data connectivity (or newer variants like RPMA, NB-IoT, CAT-M)</li><li>A flexible, take-what-you-need, pay-as-you-go fee structure.</li></ul><p>So what’s missing? Security.</p><h4>6. But the Fundamentals Still Apply</h4><p>The expanded attack surface in IoT may be unfamiliar to software developers entering this space for the first time. It’s a <a href="https://iot-for-all.com/iot-security-why-we-need-to-be-securing-the-internet-of-things/">reasonable source of concern</a>, but help is on the way.</p><p>Rapidly deployed, securely managed connections to AWS that run on a VPC peering platform with the same take-what-you-need, pay-as-you-go fee structure offer a reliable solution for developers coming to IoT from the software side.</p><p>After all, if the devices you’re using to create your IoT solution aren’t publicly visible, they’re not reachable from the public internet.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/145/0*VCEByI5qdwrLACXt.png" /></figure><p>Keeping in mind that the base operating system needs to be managed and regularly updated, the combination of AWS Greengrass type architecture, secure hardware elements, and an “invisible” peer connection can drastically reduce the attack surface.</p><p>For developers used to working with software, physical devices present plenty of new challenges. They’re fussy, they’re messy, and they can’t just be overwritten with a dot release.</p><p>AWS Greengrass simplifies the interface and makes software skills directly applicable to IoT. Combined with a smart approach to connectivity, it’s a huge step toward making the IoT accessible for all, and we should expect to see some exciting new use cases emerge as the developer community starts to put these new tools to use.</p><p><em>Originally published at </em><a href="https://iotforall.com/aws-greengrass-announcement-6-takeaways/"><em>iotforall.com</em></a></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/145/1*R6Vs7D7zKjxMqtm_ZF1pEg.png" /></figure><h3>Want all the latest advances and tech news sent directly to your inbox?</h3><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fupscri.be%2F5e6c65%3Fas_embed%3Dtrue&amp;url=https%3A%2F%2Fupscri.be%2F5e6c65%2F&amp;image=https%3A%2F%2Fupscri.be%2Fmedia%2Fform.jpg&amp;key=d04bfffea46d4aeda930ec88cc64b87c&amp;type=text%2Fhtml&amp;schema=upscri" width="800" height="400" frameborder="0" scrolling="no"><a href="https://medium.com/media/39ce2a0119753a28e90145cbca6d2ed5/href">https://medium.com/media/39ce2a0119753a28e90145cbca6d2ed5/href</a></iframe><figure><a href="http://eepurl.com/cPPD79"><img alt="" src="https://cdn-images-1.medium.com/max/1022/1*F49VxnybKhjmi-bFQGj4kg.png" /></a></figure><figure><a href="https://iot-for-all.com/"><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*LvZqvtDLMZxtmq7cRtj4pA.png" /></a></figure><figure><a href="https://iot-for-all.com/rss-feeds/"><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ugIM8aESdtjz13As4I2JkQ.png" /></a></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ca75ce1f7940" width="1" height="1" alt=""><hr><p><a href="https://medium.com/iotforall/aws-greengrass-announcement-ca75ce1f7940">AWS Greengrass Announcement</a> was originally published in <a href="https://medium.com/iotforall">IoT For All</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Crossing over from software to IoT]]></title>
            <link>https://medium.com/soracom/crossing-over-from-software-to-iot-fda1c5b4e0ee?source=rss-e8f8f7d93e80------2</link>
            <guid isPermaLink="false">https://medium.com/p/fda1c5b4e0ee</guid>
            <category><![CDATA[cloud-computing]]></category>
            <category><![CDATA[internet-of-things]]></category>
            <category><![CDATA[developer]]></category>
            <category><![CDATA[iot]]></category>
            <category><![CDATA[updates]]></category>
            <dc:creator><![CDATA[CJ Boguszewski]]></dc:creator>
            <pubDate>Wed, 14 Jun 2017 05:44:35 GMT</pubDate>
            <atom:updated>2017-06-14T05:44:35.130Z</atom:updated>
            <content:encoded><![CDATA[<p>More and more, software developers are finding themselves dragged, by inclination or necessity, toward the physical world. Thanks to the ever-advancing tide of devices, sensors, and actuators flowing into the IoT market, technically oriented people are experiencing an unprecedented opportunity to expand their skill set and deliver value with a new stack.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*bIEnxUpi5-dXzJIUrI73Sg.jpeg" /></figure><p>Of course, there’s a hitch. Actually, there are two… but let’s deal with the first one first: <strong>connecting physical devices to the familiar cloud-based development environment</strong>. When there’s constant power, or no need for a specific low-power requirement, the natural answer is to use the cell network — it’s already there, someone else rolls it out, maintains it, and optimizes it. So, how to connect the device to it? Well, to connect to a cellular network, you need a SIM card. How to get one of those?</p><p>And so the developer Googles it, searching for something like “IoT SIM”.</p><p>Or they grab what they know — the natural thought being, let me snag a SIM from the same company that provides my cellular service.</p><p>Most inherently know that, if they invest enough time into learning the various solutions that IoT or M2M SIM providers offer, they’ll find something a little bit better than what those two options might yield. Maybe something with slightly better coverage, or slightly better cost, but probably not much more.</p><p>Fair enough. But not all SIMs connect to the same services or the same platforms. In terms of both cost and capability, a little research can actually pay off handsomely. Especially early in development, the last thing a developer needs is to be locked into a contract with escalating tariffs, or on the hook for a rate plan that turns out to be poorly aligned to their actual data needs.</p><p>But that leads us back to our second hitch: <strong>device development environments are not the same as cloud-based ones</strong>. Faced with the need to either bring in some gig expertise or learn about new protocols and development languages, connectivity should be selected with this second hitch in mind. Does the provider’s platform offer (reasonably priced, pay-as-you-go) tools to help the developer actually connect a device?</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*N0fhTTudnbiKdZcIir346Q.jpeg" /></figure><p>After all, the IoT has some very specific challenges including:</p><ul><li>constrained devices</li><li>new development environments</li><li>increased attack surfaces</li><li>power management</li><li>cellular opex</li><li>cloud resource adaptation</li><li>network management</li></ul><p>Faced with this, the developer of an IoT solution can either very quickly develop superhuman learning skills and absorb all that needs to be learned, or leverage purpose-built cloud connectivity platforms that start with the SIM and end with northbound cloud APIs.</p><p>The power of knowing that these things are in hand, without a mountain to climb, can be the difference between delivering effective IoT solutions and getting stuck in the cloud, wondering what all the IoT fuss is.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=fda1c5b4e0ee" width="1" height="1" alt=""><hr><p><a href="https://medium.com/soracom/crossing-over-from-software-to-iot-fda1c5b4e0ee">Crossing over from software to IoT</a> was originally published in <a href="https://medium.com/soracom">SORACOM</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How to improve your IoT ROI with SORACOM Low Data Volume pricing]]></title>
            <link>https://medium.com/soracom/how-to-improve-your-iot-roi-with-soracom-low-data-volume-pricing-e1bd70fd58c1?source=rss-e8f8f7d93e80------2</link>
            <guid isPermaLink="false">https://medium.com/p/e1bd70fd58c1</guid>
            <category><![CDATA[iot]]></category>
            <category><![CDATA[updates]]></category>
            <category><![CDATA[developer]]></category>
            <category><![CDATA[internet-of-things]]></category>
            <dc:creator><![CDATA[CJ Boguszewski]]></dc:creator>
            <pubDate>Fri, 19 May 2017 20:22:19 GMT</pubDate>
            <atom:updated>2017-05-19T20:24:24.849Z</atom:updated>
            <content:encoded><![CDATA[<p>We know that for early-stage IoT developers projects seeking a sustainable development path for their projects, improving ROI calculations is crucial. We also know that what’s good for developers is good for IoT, and we’re always looking to make life easier. We’re happy to be able to announce a revised pricing plan for connectivity to the SORACOM IoT Platform that allows improved ROI specifically for low-data-volume device solutions.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/720/1*tx9gktQcl_bgpn8iN5QdNg.png" /></figure><p><strong>SORACOM connectivity has always come with four NOs, and those will not be changing:</strong></p><ol><li>No contracts or lock-ups</li><li>No monthly minimums</li><li>No gotchas</li><li>No escalating rate plans</li></ol><p><strong>New plan: key differences in keep-alive SIM fee and data/MB pricing</strong></p><p>With this new low-data-volume rate plan, we are reducing the cost of maintaining cellular connection even further. Our existing USA plan of $0.06/day ($1.80/month) for keep-alive and $0.08/MB for data is being reduced to a flat $0.40/month for keep-alive, with data at $0.50/MB, billed by kB (as is the original plan).</p><p><strong>Which plan is right?</strong></p><p>Now that there are two plans, it’s important for IoT developers to estimate their monthly usage and select the right plan. With usage of 4MB/month or more, the original pricing plan makes better economic sense. For low-data-volume or infrequent sensor communications, the new plan can help to minimize daily cost and further improve a solution’s ROI, especially in early days.</p><p><strong>But wait! There’s more!</strong></p><p>SORACOM has always been available to you through your existing <a href="https://www.amazon.com/s?field-keywords=soracom">Amazon.com</a> account, and the 1-, 3-, and 5-packs are still available there. However, we are pleased to also add the capability to buy directly from soracom.io with similar fulfillment times. The buy-direct functionality allows for those customers whose needs are more customized than what the Amazon sales channel permits.</p><p>Existing customers can now simply tell us what you need directly from the console. Here are some illustrations to show you how the order process works now.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/493/1*rHHle3wsSevqkhyq94KmmQ.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/432/1*eVMtyqL6r_BV72Mi-NUWYw.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/306/1*XQWi6sjgC2ExkrVbMDWqMA.png" /><figcaption>Ordering process on SORACOM</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/686/1*qRKRVfzpS4Er4-bw7UwjaA.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/909/1*CMDBa0GVhxLrA0CqvjTCwA.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/911/1*2v0ENZoHWspZQrMCq2NLvg.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/902/1*SDi4Z6JvTJCEHgQUi38O3Q.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/899/1*-JlWv6J2ROXloCcHC_ZXGQ.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/903/1*nN86BGWwK6W89T2Q9EGG8A.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/910/1*QgH_5tDCeCASv0csXqYKoA.png" /><figcaption>Finalizing the low-data-volume SIM order on SORACOM.io</figcaption></figure><p>Nothing’s changed there: SIMs in standard, micro, and nano form factors.</p><p><strong>Any further questions or doubts, you can always contact us</strong> <a href="https://soracom.io/en/contact/"><em>here</em></a><em>.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e1bd70fd58c1" width="1" height="1" alt=""><hr><p><a href="https://medium.com/soracom/how-to-improve-your-iot-roi-with-soracom-low-data-volume-pricing-e1bd70fd58c1">How to improve your IoT ROI with SORACOM Low Data Volume pricing</a> was originally published in <a href="https://medium.com/soracom">SORACOM</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[IoT 101: Building on the SORACOM Platform]]></title>
            <link>https://medium.com/soracom/iot-101-building-on-the-soracom-platform-36d17700829a?source=rss-e8f8f7d93e80------2</link>
            <guid isPermaLink="false">https://medium.com/p/36d17700829a</guid>
            <category><![CDATA[projects]]></category>
            <category><![CDATA[cloud-computing]]></category>
            <category><![CDATA[aws]]></category>
            <category><![CDATA[internet-of-things]]></category>
            <category><![CDATA[iot]]></category>
            <dc:creator><![CDATA[CJ Boguszewski]]></dc:creator>
            <pubDate>Wed, 26 Apr 2017 23:12:40 GMT</pubDate>
            <atom:updated>2018-06-27T21:18:43.975Z</atom:updated>
            <content:encoded><![CDATA[<p>Even for cloud-fluent developers, building for IoT can present a new kind of challenge. The Soracom platform is designed to make getting started easy and to scale as you do, with more advanced services available once you’re connected.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*pD-AC7B4WFnNBlF92Ty3lA.png" /><figcaption>Where it all starts</figcaption></figure><p>From basic connectivity to advanced cloud integration, our philosophy carries across every service we offer: make it easy and keep the developer in control. Every service is offered on a pay-as-you-go, take-what-you-need basis. Pricing is completely transparent, there’s never any contract to sign, and you can stop the service the moment you stop needing it, or someone does it better than us. Even our embedded connectivity options support portability standards.</p><h4><strong>Getting Connected</strong></h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*3cNrH0vLqzFV77Z_oJgAmw.png" /></figure><ul><li>The Soracom SIM is compatible with all standard SIM form factors and <a href="https://www.amazon.com/SORACOM-Air-Global-IoT-3-pack/dp/B01MQ019RJ">available direct on Amazon</a>. Our connectivity service, SORACOM Air, now covers 100+ countries, and can roam when multiple supported networks are available, so if your device is out of range on one network it can attach to another.</li><li>All of your devices and connections can be managed directly from the Soracom console or through <a href="https://dev.soracom.io/en/docs/api/">our suite of over 100 APIs</a></li></ul><h4>Adding Cloud Capability</h4><p>Most connected things don’t have a lot of memory or power, but that doesn’t mean they can’t act like they do. The Soracom platform is designed to let these devices do more with less by harnessing the power of the cloud.</p><p>With a mobile communications core built right on AWS, our services help to reduce data consumption, enhance security, and integrate directly with AWS, Azure, and other cloud resources.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/768/1*aw21xVMJVv60tu9mRddXAw.png" /></figure><p>1/ <a href="https://soracom.io/en/services/beam/">beam</a>: works more like an HTTP server than a proxy. Send a request to <a href="http://beam.soracom.io/">beam.soracom.io</a> and the request is forwarded to a server that you specify in config. So it doesn’t send requests to arbitrary servers. Translates thin-device protocol (e.g., UDP) to cloud-ready protocol (HTTP or HTTPS), or handles MQTT on the device and server sides.</p><p>2/ <a href="https://soracom.io/en/services/funnel/">funnel</a> works on the same technology stack as beam, and directs your devices straight to Kinesis, Kinesis Firehose, Azure Event Hubs, or AWS IoT without the need for an SDK on the device level. Funnel does the protocol and format translation within the adapter. Contrast this with the AWS rules engine, which is a SQL-structured selection mechanism that would allow sorting of data into AWS services. For the rules engine, you’re writing in JSON. And while multiple actions per rule can be concatenated for ease of maintenance, rules proliferate quickly. Funnel lets you avoid this work of writing, and more importantly, maintaining, so you can quickly get devices hopping on to the relevant cloud service with little fuss.</p><p>3/ <a href="https://soracom.io/en/services/canal/">canal</a> / <a href="https://soracom.io/en/services/door/">door</a> / <a href="https://soracom.io/en/services/direct/">direct</a> and <a href="https://soracom.io/en/services/gate/">gate</a> layer-two &amp; layer-three VPC peering within the AWS data center. Allows for the removal of the device from public view, and thereby allows trimming of cellular opex by chopping redundantly transmitted header, security, and other extraneous information. No initial VPC configuration, no each-time authentication process for the device when it wants to access the private resources. The different flavors refer to different levels of integration (e.g. Direct is a leased line connection, Door supports traditional IPSec VPNs). Gate actually enables secure layer-two device-to-device as well as device-to-server communication, not just the VPC in AWS (no NAT or firewall restrictions). The services allow for significant opex and security benefits depending on architectural decisions in the IoT application stack. They also let developers avoid fine-grain permission management, tedious to script and maintain in JSON.</p><p>4/ <a href="https://soracom.io/en/services/harvest/">harvest</a>: visualize the data from the connected sensor/device/actuator without hooking it up to the cloud just yet. Great for prototyping when the ongoing economics of the application aren’t yet secure.</p><p>5/ <a href="https://soracom.io/en/services/endorse/">endorse</a>: like Cognito, offers federated identity — identity pool and specific user definitions. It gives a SIM-based authentication option so that devices “outside the VPC” can get similar privileges and act like they’re inside.</p><p>The Soracom platform starts simple, but also comprises powerful dev tools, which you can explore on the Soracom developer site: <a href="https://dev.soracom.io/en/">https://dev.soracom.io/en/</a></p><p>The reference architecture diagrams you’ll find on each individual service page will give you a good illustration of how each particular service can be used (e.g., using Funnel to have devices send data directly to Kinesis Firehose and then using Lambda to fork the data to multiple AWS service targets like Redshift for your constant query targets and also DynamoDB for cases where fast lookups necessitate the indexing capability).</p><p>The power and extensibility of the SORACOM platform’s various features is evident when you browse the developer documentation, with more than 100 APIs ready to leverage. In among the 6,000+ customers and 300+ partners we have acquired since we started in 2015, there are probably plenty of use cases that relate to what you’re trying to do. Take a look and let us know if we can help you!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=36d17700829a" width="1" height="1" alt=""><hr><p><a href="https://medium.com/soracom/iot-101-building-on-the-soracom-platform-36d17700829a">IoT 101: Building on the SORACOM Platform</a> was originally published in <a href="https://medium.com/soracom">SORACOM</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Silicon Valley Forum: Reflections on Panel Discussion re: AgTech]]></title>
            <link>https://medium.com/soracom/silicon-valley-forum-reflections-on-panel-discussion-re-agtech-dabe3ced5527?source=rss-e8f8f7d93e80------2</link>
            <guid isPermaLink="false">https://medium.com/p/dabe3ced5527</guid>
            <category><![CDATA[iot]]></category>
            <category><![CDATA[farming]]></category>
            <category><![CDATA[events]]></category>
            <category><![CDATA[agtech]]></category>
            <category><![CDATA[internet-of-things]]></category>
            <dc:creator><![CDATA[CJ Boguszewski]]></dc:creator>
            <pubDate>Tue, 11 Apr 2017 22:56:44 GMT</pubDate>
            <atom:updated>2017-04-12T00:39:04.011Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/400/1*hHtyi9xBkRZWl7IRRQWa4g.png" /></figure><p>I recently participated in a panel discussion at the daylong <a href="https://siliconvalleyforum.com/event/29268277205">Seeds of Our Future conference</a>, the culmination of the <a href="http://siliconvalleyforum.com/">Silicon Valley Forum</a>’s AgTech Week and an amazing opportunity to meet and learn from AgTech innovators and developers around the world.</p><p>In Japan, population changes, loss of arable land to other development, and <a href="https://www.bloomberg.com/news/articles/2016-04-23/robots-replacing-japan-s-farmers-seen-preserving-food-security">perception of farming as a less attractive profession in recent years</a> are just a few of the factors driving agriculture to look toward IoT technology as an opportunity for new efficiencies and new opportunities. More and more, Japan is turning to automation as an opportunity to not only increase efficiency but preserve the nation’s food security for the future.</p><p>Japan provides an excellent model for the possibilities available to first movers in AgTech, and underscores some challenges as well.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*zBn4-aJ2Yq933Be6-rY48Q.jpeg" /><figcaption>Panel Discussion: The Role of Japan in Agricultural Automation</figcaption></figure><p>The AgTech space is growing fast, with growers in need of both innovation and simplicity. Existing network options often transgress these two critical requirements — many end-to-end solutions don’t “just work,” and innovation often pays the price.</p><p>Instrumenting with intent — devices, sensors, and actuators deployed in a way that allows growers to remove cost from their operations — is one of the most sure-handed levers that IoT can pull. At Soracom, we have helped early-adopter agricultural IoT players such as <a href="http://kakaxi.me/">Kakaxi</a> and <a href="https://soracom.io/en/case_studies/farmnote/">Farmnote</a> to address specific AgTech challenges in the field.</p><p>We understand that, the more constrained a device is in its compute, storage, battery, and bandwidth, the more it must rely upon other systems to execute logic, record sensor data, and link with other devices. This basic IoT premise applies very directly in AgTech, where connectivity in farmland is often sparse and unreliable. In the absence of reliable connection, that crucial link to other devices and services becomes tenuous and negatively impacts the adoption of needed devices, sensors, and actuators in the fields of the growers.</p><p>Equally importantly, current economic models for connectivity can also weigh heavily on adoption: with SmartPhone-like pricing plans and gotchas like the ones that plague the consumer segment, IoT makers are understandably wary when it comes to selecting connectivity, and well-trained on lowest-price “headline characteristics” such as $/MB.</p><p>Of course, in IoT, this doesn’t tell the full story of how solutions are best architected — existing carrier platforms are pre-cloud, and most pricing models are not adequated to the simpler, lower-data-volume machine-to-machine communications that are needed.</p><p>As technology catches up to deliver the agility, scalability, and economics of the true IoT into the hands of growers, AgTech will be able to evolve the sector towards a more profitable and sustainable future.</p><p>Special thanks to Hiroshi “Hiro” Saijou, CEO and Managing Director at Yamaha Motor Ventures &amp; Laboratory Silicon Valley, for organizing this panel and for moderating a very lively discussion. It was a special pleasure to share the stage with Taizo Otsuka, founder of Kakaxi, which is one of Soracom’s favorite AgTech use cases.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*hdwjbWzDYnPAAWC03WVUug.png" /><figcaption><a href="http://buff.ly/2kwVL0p"><strong>Available at Amazon.com</strong></a><strong> (US)</strong></figcaption></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=dabe3ced5527" width="1" height="1" alt=""><hr><p><a href="https://medium.com/soracom/silicon-valley-forum-reflections-on-panel-discussion-re-agtech-dabe3ced5527">Silicon Valley Forum: Reflections on Panel Discussion re: AgTech</a> was originally published in <a href="https://medium.com/soracom">SORACOM</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>