AWS re:Invent 2020: Connect today, transform tomorrow with AWS IoT

Aug 16, 2023

AWS re:Invent 2020: Connect today, transform tomorrow with AWS IoT

As the proliferation of IoT devices yields an increasingly connected world, device data fuels organizations’ abilities to leverage actionable insights and operate at the speed of software. Regardless of where you are in your digital journey, AWS IoT enables you to securely connect and manage devices, collect and analyze device data, and build and deploy solutions that unlock new possibilities and drive greater business value. In this session, Dirk Didascalou, VP of AWS IoT, shares what’s new with AWS IoT and how organizations are using it to solve real-world challenges today, like deriving consumer insights, creating better user experiences, and improving business operations.

Learn more about re:Invent 2020 at http://bit.ly/3c4NSdY

Subscribe:
More AWS videos http://bit.ly/2O3zS75
More AWS events videos http://bit.ly/316g9t4

#AWS #AWSEvents

Content

2.72 -> [music playing]

13.969 -> Welcome everyone to the IoT Leadership Session

16.499 -> at re:Invent 2020. My name is Dirk Didascalou

20.019 -> and I am the VP of IoT at Amazon Web Services.

23.629 -> I grew up in the mobile industry

25.579 -> for the first 20 years of my career including a company called

28.639 -> ‘Nokia’ building billions of phones connecting people.

32.819 -> Now here at AWS my teams are building services and software

37.399 -> to connect billions of things that can sense the environment

40.839 -> in a way you never could before and make sense of that data.

45.799 -> During the past five years or so,

47.769 -> I have seen IoT make a significant impact on our customers

51.539 -> as they undergo digital transformation

53.719 -> to be data driven and move at the speed of software

56.899 -> and, in the next hour or so, I would like to share with you

59.579 -> some stories how our customers connect their assets today

63.399 -> and how we help them transform tomorrow

66.259 -> with the latest developments and offerings of AWS IoT.

71.949 -> At AWS we start typically all our custom engagements for IoT

75.899 -> with a simple question: If you knew the state of everything

81.099 -> and you could reason on top of that data,

84.029 -> what problems would you solve?

86.029 -> And it is our mission at AWS to make sure that you can know

91.079 -> the state of all your devices and assets,

93.339 -> and that you can reason on top of that data,

95.849 -> so that you can truly solve your business problems,

100.279 -> and our customers solving many problems

102.749 -> and transforming literally every industry around the world;

106.449 -> like Vizio who connects millions of TVs with AWS IoT

110.156 -> and Amazon Alexa; or Comcast, which uses AWS IoT

114.299 -> to build home security solutions at scale;

116.889 -> or Deutsche Bahn, the German train operator

119.889 -> that gathers new insights about their trains with AWS

122.589 -> every day; and LG Electronics which relaunched its IoT platform

127.049 -> and saves 80% in development costs with AWS IoT; or Modjoul and ProGlove,

131.949 -> which create IoT based products to enhance worker safety.

136.969 -> And the explosive growth in IoT use cases

139.949 -> and the sheer number and diversity of devices

143.219 -> out there has been phenomenal.

145.619 -> These are just a few examples of how AWS IoT

148.761 -> is helping a lot of customers solve their business problems,

153.679 -> but in principle customers do two things with IoT.

157.409 -> They become more efficient in what they can do today,

161.069 -> lowering their cost, helping their bottom line,

164.079 -> and they can build completely new services and products

167.639 -> which drives the business increasing the top line,

170.519 -> and I explicitly used the work

172.189 -> and since this is what AWS IoT does for our customers,

176.129 -> it leads to greater operational efficiency and revenue growth.

181.739 -> So, how does it work?

183.459 -> In essence you need three different types of services and software.

187.469 -> First, IoT Device Software to build devices

190.899 -> that operate at the Edge.

192.629 -> Second, Connectivity and Control Services to connect

196.109 -> and manage and secure these devices at scale from the cloud.

199.989 -> And then third, Analytics and ML/AI Services

203.349 -> that make sense of IoT data

205.169 -> and take actions to solve business problems.

208.129 -> But this is not your classic layered software architecture

211.469 -> but rather a circle,

213.259 -> where devices collect data at the Edge with software

216.699 -> which is then transported and routed to the cloud

219.399 -> with the help of Connectivity and Control Services

222.029 -> where Analytics and ML and AI Services

225.659 -> process the data to extract the relevant business insight,

229.119 -> which in turn inform decisions

231.139 -> and control devices behavior at the Edge again,

234.139 -> all with the goal to have better outcomes

236.659 -> for your operations and businesses.

239.219 -> And for each of these three areas, AWS IoT

242.559 -> provides our customers with the right services.

246.339 -> Let’s start at the Edge with devices.

249.359 -> This is about “How can I build devices and software

253.339 -> that operate at the Edge in concertation with the cloud

257.199 -> to support any IoT use case?”

259.949 -> The AWS offering covers the full diversity

262.419 -> from the smallest sensors over gateways and industrial PCs,

266.369 -> to specialized equipment up to dedicated

268.969 -> AWS infrastructure at your premises.

271.839 -> For the smallest devices we have FreeRTOS,

274.289 -> which is the number one operating system for microcontrollers

277.719 -> that allows you to easily build small low power

281.049 -> Edge devices that connect to AWS IoT.

284.219 -> For more powerful devices like a gateways,

287.059 -> AWS IoT Greengrass which is a software run time

290.219 -> that extends AWS to the Edge devices

292.949 -> so they can then act locally on the data they generate

296.339 -> while still using the cloud for management, analytics and storage.

300.719 -> Or specialized appliances, like AWS Snowball Edge,

304.449 -> which is petabyte-scale data transport with onboard storage

307.799 -> and compute capabilities.

309.499 -> It’s hardened and suitable for ruggedized environments

312.439 -> like, for example, in factories.

314.439 -> And for the significant workloads, AWS Outposts,

316.849 -> run AWS infrastructure and services on-premises

321.599 -> for a truly consistent hybrid experience,

324.979 -> and if you’re interested in more details around the Edge,

328.369 -> and how AWS powers Edge-to-Cloud applications,

332.229 -> please tune in to tomorrow’s ‘Edge Leadership Session’ with Bill Vass.

336.829 -> For the second area, Connectivity and Control,

339.369 -> which is all about how can I connect,

342.039 -> manage and secure my devices and fleets at scale,

345.299 -> we start with AWS IoT Core,

348.159 -> a managed cloud service that lets you connect devices easily,

352.369 -> Securely, and interact with the cloud applications

355.319 -> and other devices at scale. Or AWS IoT Device Management,

359.839 -> which helps customers register, organize, and remotely manage

363.599 -> their connected devices and monitor fleet health.

366.369 -> Or AWS IoT Device Defender,

368.149 -> which continuously audits IoT configuration

370.729 -> to ensure they do not deviate from security best practices

375.139 -> and it detects anomalous device behavior.

377.949 -> Amazon Kinesis to easily collect, Process, and analyze video

381.769 -> and data streams in real time.

384.019 -> And finally, for Analytics and ML and AI,

387.659 -> which looks at “How can I make sense of my data

391.159 -> and take actions to solve my business problems?”

394.349 -> First, AWS IoT Analytics which allows customers

397.249 -> to ingest large amounts of IoT data, enrich it,

401.059 -> and run ETL queries or machine-learning models on it,

404.759 -> or AWS IoT SiteWise, our industrial service

407.989 -> which collects data from the plant floors,

410.229 -> Structures, and labels the data and generates real-time

413.329 -> KPIs and metrics to make better data-driven decisions. Or AWS IoT Events,

418.999 -> which allows you and customers to continuously monitor data

422.479 -> from their equipment and fleets of devices for changes in operations

426.439 -> and trigger the appropriate response when events occur. And from machine

430.709 -> Learning, our signature Amazon SageMaker service,

434.009 -> a fully managed service that provides

436.549 -> every developer and data scientist with the ability to build,

440.849 -> Train, and deploy machine learning models quickly.

443.779 -> And then, with the help of AWS IoT Greengrass,

446.449 -> which I talked about in the device section,

448.189 -> deploy those models back to the Edge for local machine

452.369 -> learning inferencing and action.

454.479 -> Now, you have seen the use cases

457.699 -> and the AWS IoT services that enable them,

460.889 -> how do you get to the applications and business outcomes?

464.269 -> You can build yourself with the AWS services

467.279 -> I just mentioned with a variety of documentation,

470.409 -> getting starting guides and other accelerators

472.439 -> to help customers build on their own and expand their in-house skills.

476.919 -> In addition, we have Professional Services

479.629 -> that can support our customers with business case analysis,

483.089 -> proof of concepts, and ultimately hasten their deployments.

486.589 -> Or, you can engage AWS partners to build on your behalf

490.619 -> or provide specific solutions to address your specific challenges

494.799 -> that gives you a highly customized experience,

497.639 -> get domain expertise from our partners,

499.699 -> and accelerate the deployments as well,

502.389 -> or maybe you want to deploy ready-made solutions directly.

506.219 -> We have IoT solutions directly from AWS

508.999 -> as well as our partners to help you quickly get started addressing

512.399 -> the most common IoT use cases across industries.

515.889 -> Let’s look at our partner network a little bit.

518.769 -> At re:Invent last year we launched the ‘Edge to

521.539 -> Outcome Partner Value

522.609 -> Chain’ to address the complexities of IoT

525.599 -> with a distributed set of partners spanning the Edge, over connectivity,

529.659 -> to actual applications and solutions for your specific use case.

533.759 -> Additionally, we have four mechanisms to accelerate customer outcomes.

538.469 -> First, Silicon Acceleration that is driven by our silicon partners

543.009 -> so that our customers can build connected products

546.019 -> faster in that same realm. The Device Qualification Program

550.149 -> builds on Edge hardware partner community

552.479 -> with all types of IoT devices

554.589 -> ready to use and purchase. Then we have

558.129 -> AWS IoT practices delivered by our global system integrators

561.609 -> and local system integrators to increase delivery capability.

565.359 -> And finally, four, we have IoT solutions

568.369 -> which are domain- specific partner offerings

570.869 -> that deliver business outcomes for our customers and the AWS

575.479 -> Partner Competency Program has vetted, validated, and verified

580.189 -> that our IoT partners have demonstrated success

583.069 -> in providing specialized “Edge to Outcome” IoT solutions.

587.109 -> As you can see, we have hundreds of partners

589.679 -> spanning the Edge, from silicon vendors,

592.099 -> OEMs, ODMs, and contract Manufacturers; or Connectivity,

596.309 -> including gateway suppliers,

597.649 -> and network carriers; to the Solution space,

600.129 -> including the independent software vendors

602.159 -> who provide their own applications based on their domain knowledge,

605.569 -> as well as regional and global system integrators

608.299 -> that build all types of applications and solutions

610.879 -> with and for our customers.

613.469 -> Our network of APN Partners benefits all of our customers

618.029 -> regardless of the industry and use case,

620.009 -> and this network is growing all the time.

623.999 -> And once a partner device

625.319 -> went through the Device Qualification Program

627.229 -> I mentioned earlier, it gets listed in the AWS Partner Device Catalogue,

631.539 -> that helps you discover qualified hardware

634.189 -> that works with AWS services so you never have to worry

638.209 -> if your selected hardware actually will work with AWS IoT.

640.599 -> You can find hardware that works with AWS,

644.569 -> including development kits and embedded systems

648.029 -> to build new devices, as well as off the shelf devices

651.259 -> such as gateways, industrial servers, sensors, and cameras for immediate

655.929 -> IoT project integration.

658.099 -> All devices listed in the Partner Device Catalogue

660.479 -> are also available for purchase from our partners

662.799 -> to get you started quickly.

664.589 -> With hundreds of these devices and more being qualified

667.809 -> all the time, the Device Catalogue

670.199 -> helps you build and deliver successful

672.439 -> IoT solutions faster.

674.679 -> And speaking about solutions, we have IoT solutions from AWS

679.459 -> as well as our partners to help you quickly get started

683.179 -> solving for your common IoT use cases.

686.309 -> These solutions span verticals such as industrial, connected home,

690.599 -> connected vehicles, and many more.

693.169 -> The AWS solutions help you build faster

695.429 -> with AWS CloudFormation templates, reference architectures,

698.999 -> GitHub repositories, and deployment guides.

702.029 -> The partner solutions are built on top of AWS

705.509 -> and they are ready to use from the AWS Solutions Library

709.359 -> and the AWS Marketplace with hundreds of offerings for IoT.

713.949 -> Accelerate your time to value

715.429 -> leveraging the expertise of APN Partners

718.049 -> and the prebuilt solutions. At aws.amazon.com/iot/solutions

724.499 -> we created a space for customers to browse all AWS

728.449 -> and Partner IoT solutions in a single place,

731.659 -> to make it even easier for you

732.929 -> to get started building solutions quickly.

735.339 -> We have also a dedicated AWS

737.599 -> for Industrial initiative at aws.amazon.com/industrial .

744.459 -> So where are we today? How do our customers connect?

749.179 -> Today, AWS IoT has tens of thousands of monthly active customers

753.999 -> across the globe. More than 90% of Fortune 100 companies

758.429 -> and the majority of Fortune 500 companies

761.249 -> utilize AWS Partner solutions and services.

764.849 -> AWS IoT Core alone handles more than half a billion active unique

769.469 -> external endpoints every month,

771.809 -> which send more than half a trillion payload messages monthly.

775.639 -> And we have more than 300 solutions across the IoT Solutions Repository

780.169 -> and AWS Marketplace. With over half a thousand qualified partner devices

785.259 -> in our Device Catalogue which is steadily growing.

788.709 -> And accordingly to the Eclipse Foundation, FreeRTOS

791.709 -> is the leading embedded real time

793.229 -> operating system with 35% market segment

796.769 -> share which is more than four times compared to the next.

801.089 -> But we want to make connecting your devices and assets even easier.

808.519 -> 1NCE specializes in providing managed connectivity services

812.819 -> for low bandwidth IoT applications for constrained devices

816.799 -> such as asset trackers and smart meters.

819.289 -> 1NCE is a strategic partner of Deutsche Telekom,

821.889 -> as well as an AWS Advanced Technology Partner.

825.099 -> Their offering includes an IoT Flat Rate SIM

828.119 -> plus IoT Connectivity Suite.

830.819 -> Their SIM-as-an-Identity onboarding services

834.129 -> map the identities of individual IoT devices

837.169 -> using their SIM cards.

838.729 -> It allows 1NCE customers to fully automate device

841.399 -> onboarding to AWS IoT Core for all IoT devices using a 1NCE SIM.

846.989 -> Simply order the number of SIMs

848.749 -> you need to start your IoT project from 1NCE,

851.729 -> and execute the AWS CloudFormation

853.419 -> template from the 1NCE Connectivity Suite,

856.369 -> to set up resources in AWS accounts. Once customers receive their SIMs,

861.119 -> they can insert that SIM into their device

863.529 -> running the 1NCE Blueprint SDK,

865.739 -> which automatically connects to AWS IoT in the cloud.

868.769 -> It’s that simple, and there’s more.

872.359 -> 1NCE is offering free IoT connectivity plans

876.249 -> for a period of 12 months for low-data consumption

879.179 -> IoT applications exclusively on the AWS Marketplace.

884.479 -> This service offer includes global connectivity

888.219 -> through Tier 1 global networks from, for example,

890.509 -> Deutsche Telekom. Up to 100 free

893.479 -> SIM cards, free of charge, for 12 months for up

897.429 -> to 50 megabyte of data volume each, and you can upgrade to 1NCE’s Flat Rate

902.269 -> pricing at any time. Get your SIM exclusively at the AWS

906.879 -> Marketplace at the link shown on the slide,

911.449 -> and once you connect your IoT devices, you need to put them to good use.

915.419 -> Lenovo is the number one PC maker and leading

918.609 -> OEM for technology solutions.

921.059 -> Beyond consumer, Lenovo is one of the key players

924.109 -> in the commercial and enterprise space.

927.479 -> Lenovo has selected AWS

929.249 -> as its partner for their new Commercial

931.259 -> IoT division, a division focusing on bringing scalable

935.019 -> IoT solutions to enterprises to enable smarter stores

938.749 -> and smarter workplaces, recently branded

941.029 -> as ‘Think IoT’ under Lenovo’s broader Think portfolio.

946.229 -> Think IoT will be cross-vertical including retail,

949.799 -> commercial real estate/ smart buildings, and others.

952.999 -> The initial focus is on getting people back to work

955.779 -> through a Covid-19 focused campaign.

958.159 -> The use cases today vary from touchless access control,

962.229 -> employee and visitor tracking, to smart shelf management,

966.539 -> energy efficiency, and public safety. With customers in more than 180 markets

971.399 -> and expertise supporting more than 125 million devices,

975.339 -> Lenovo provides leading solution monitoring and management to keep all

979.359 -> ‘Think IoT’ Back to Work solutions running for customers.

984.279 -> According to the World Food Programme, Globally, about one third of the food

988.419 -> we produce each year is lost or wasted, costing

991.909 -> the global economy nearly one trillion

994.299 -> US dollars annually.

996.289 -> Carrier is a global leader in building and refrigeration solutions.

1000.519 -> Carrier monitors more than 15 million cold chain products annually

1004.729 -> and about nine billion dollars worth of goods

1007.479 -> are transported via ocean daily in Carrier’s

1010.679 -> refrigerated containers, known as reefers.

1014.489 -> Carrier and AWS are collaborating to develop Lynx,

1018.399 -> a digital platform to optimize cold chain operations for perishable

1022.409 -> foods and critical medications. It’s very important these days.

1027.569 -> Lynx unifies the highly fragmented cold chain

1030.849 -> to reduce food spoilage, support end-to-end visibility,

1034.699 -> and increase efficiency throughout the various stages

1038.119 -> of refrigerated storage and transportation.

1041.059 -> It’s built on AWS IoT

1042.904 -> to manage temperature-controlled transport

1045.089 -> and storage of perishables at scale.

1048.549 -> Overall, on time, on temperature food

1052.179 -> reduces waste with low cargo spoilage,

1055.019 -> it lowers logistic costs for the highest equipment

1058.019 -> uptime and resilience. A really great use case for IoT.

1064.179 -> Particularly with industrial scenarios however,

1067.039 -> and the many associated brownfield and specialized applications,

1070.419 -> many customers prefer to have ready-made solutions

1073.789 -> that they can buy to solve their problems.

1077.299 -> One of the global leaders in the industrial IoT space Hitachi

1081.899 -> with its Lumada industrial solution platform,

1084.839 -> is a leader in Gartner’s 2020 Industrial IoT Platforms Magic Quadrant

1089.719 -> and expands their strategic collaboration with AWS.

1094.059 -> Hitachi Vantara’s Lumada Solutions detect,

1097.209 -> Collect, and organize data then run data analytics

1100.239 -> for customers of manufacturing, transportation, and energy,

1103.619 -> that manage industrial operations such as plant floors, power networks,

1108.089 -> train systems, and even mining sites. It can be deployed with AWS IoT

1112.779 -> services to deliver advanced digital solutions for customers

1117.219 -> to reduce energy cost, or detect and fix equipment

1120.379 -> issues faster, to spot inefficiencies in manufacturing lines

1123.719 -> more accurately, and improve product quality and production output.

1128.659 -> The partnership expands across manufacturing, transportation

1132.339 -> and energy verticals. For Hitachi, this means they can focus

1136.569 -> even more on developing domain-specific functions

1140.649 -> and outcome-focused value for their customers

1143.579 -> while leveraging proven AWS’s infrastructure capabilities

1146.859 -> for the scalability, fault tolerance,

1148.679 -> and ease of maintenance that they are known for.

1151.939 -> The first example is the Lumada

1153.909 -> Manufacturing Insights software, now available on AWS

1157.929 -> and leveraging AWS IoT native services.

1162.889 -> Powering transformation isn’t limited to commercial organizations

1166.129 -> or products though.

1167.529 -> We see the public sector take great strides to introduce smart cities,

1172.069 -> smart campuses, and solutions to drive municipal benefit, like safety.

1177.199 -> IDC MarketScape named AWS

1179.649 -> as the leader in IoT application platforms

1182.159 -> for smart cities earlier this year, and the University of Melbourne,

1186.349 -> the number one university in Australia,

1188.779 -> selected AWS as their key vendor

1191.369 -> to support their smart campus initiative in early 2018.

1195.609 -> The project has provided key insights

1197.879 -> which enabled the university to maximize space utilization

1201.519 -> and resource capacity planning.

1203.609 -> It provided energy dashboards showing metrics and trend analysis,

1208.119 -> and identified over four hundred thousand dollars

1210.299 -> in savings to the university in 2020 alone.

1214.059 -> These insights are also being used in the Return to Campus strategy

1218.179 -> for the first quarter 2021, helping them maintain

1222.159 -> required hygiene statuses and social distancing.

1226.189 -> They established an IoT as a service platform

1229.049 -> using AWS IoT Core to integrate with IoT devices

1232.769 -> to collect and centrally store data for analytics and insights.

1237.179 -> At any point in time,

1239.279 -> they can visualize an estimated number of people in any building

1243.259 -> as well as other information such as temperature,

1246.129 -> energy usage, and much more.

1249.309 -> As you saw, we have AWS customers and partners doing incredible things

1253.579 -> to improve business operations, create new offerings, and keep food

1256.979 -> and people safe with the help of AWS IoT.

1260.899 -> They are doing those things today,

1262.519 -> Yet, we are always mindful of the their experience

1265.649 -> and how we can make progressing their digital journeys even more seamless.

1270.649 -> This is why I am excited to share with you

1272.759 -> our latest product enhancements and launches.

1276.859 -> More than 90% of our deliverables are the direct results of learning

1281.639 -> from the pain points of our customers and partners,

1285.189 -> and turning those learnings into functionality

1288.449 -> that then helps them securely build and manage IoT solutions at scale.

1292.949 -> It is a true customer-driven roadmap.

1295.809 -> It started end of 2015 with AWS IoT Core, our core

1299.669 -> connectivity service, with iRobot

1302.439 -> as the early adopter driving for scale.

1305.299 -> In 2016, we went then to the Edge with

1308.799 -> AWS IoT Greengrass to support customers like Enel, to collect,

1312.879 -> convey, and process data across a network of sensors

1316.249 -> and meters at over 500,000 cabins

1319.509 -> distributed across Europe. Followed in 2017 by FreeRTOS,

1324.929 -> to enable the low power devices to securely connect to the cloud

1328.879 -> and together with partners like TI and NXP.

1332.629 -> It was then Philips who worked with us to create

1335.489 -> AWS IoT Device Management in 2018 for their

1339.149 -> HealthSuite digital platform to control their fleets

1343.239 -> of the medical devices and keep them healthy.

1346.309 -> The same year we also launched AWS IoT Analytics and Device Defender,

1350.569 -> which was then recognized as the “Best IoT Security Solution” at the 2019

1356.11 -> IoT World Awards.

1358.419 -> And over the past two years, we doubled down on analytics

1361.989 -> and industrial use cases, with AWS IoT Events

1364.345 -> and AWS IoT SiteWise for customers like Bayer CropScience

1367.459 -> for their crop processing plants.

1370.509 -> And this year at re:Invent 2020,

1372.929 -> we continue to expand our roadmap

1375.329 -> across all three areas driven again by our customer needs.

1380.709 -> Let’s start at the Edge. Again, this is about “How can I easily build

1385.429 -> and manage IoT device software at the Edge?”

1388.459 -> And our answer so far to this question has been IoT Greengrass,

1392.564 -> which extends AWS IoT

1394.235 -> onto your devices so they act locally on the data they generate

1398.872 -> while still taking advantage of the cloud.

1401.989 -> AWS IoT Greengrass extends

1403.489 -> the same programming model from the cloud to the Edge

1406.199 -> and does this using the same security mechanisms

1409.529 -> and encryption used in the cloud with AWS IoT.

1412.864 -> It provides many useful features available at the Edge

1415.879 -> depicted on the slide. And it is also updateable

1419.469 -> so you always get the latest access

1421.559 -> to new features and security enhancements in the future,

1425.579 -> and this year it’s about a major update.

1430.859 -> I am proud to announce AWS IoT Greengrass 2.0.

1435.809 -> We rewrote the entire software stack to be JVM based

1439.569 -> and modularized, to create the most flexible Edge platform,

1444.709 -> to easily build, deploy, and manage device software

1448.199 -> across millions of devices. It’s now completely modular,

1452.369 -> customers can easily add or remove features

1455.609 -> by choosing which device software components

1458.009 -> are installed on their devices. AWS IoT Greengrass lets customers

1462.629 -> add capabilities to more powerful devices

1465.429 -> or remove features on constrained devices

1468.149 -> with limited memory or compute power, so customer

1471.159 -> only use the features they need. And deploy device software at scale:

1476.569 -> Customers can deploy code in the cloud or now on a local device,

1480.989 -> and then deploy and manage the software

1482.879 -> on millions of heterogeneous devices

1485.529 -> even with intermittent connectivity to the cloud.

1488.809 -> Being integrated with Device Management, Thing

1491.469 -> Groups lets customers view deployment history,

1494.469 -> and start, stop, and cancel deployments

1497.619 -> for any number of AWS IoT Greengrass devices. And finally,

1502.269 -> it’s locally deployable and configurable.

1505.219 -> AWS IoT Greengrass provides customers options to build, test,

1510.549 -> and manage device software deployments

1512.599 -> locally using the Greengrass command- line interface (CLI).

1516.959 -> Customers can deploy, Test, and debug devices software

1519.709 -> locally with common program languages such as Java and Python and all new,

1525.729 -> the AWS IoT Greengrass 2.0 Core client software

1530.099 -> is now open source,

1532.499 -> making Edge computing even more accessible to customers and adoptable

1537.479 -> to the hardware platform in industry requirements of their choice.

1542.429 -> Customers benefit from an open Edge software environment

1545.789 -> that empowers them to develop, debug and customize their IoT software

1549.929 -> they need on the device of their choice.

1554.299 -> Arthrex is a global medical device company

1557.409 -> and leader specialized in orthopedics.

1560.439 -> Arthrex has pioneered the field of arthroscopy

1563.859 -> and develops more than a thousand innovative products

1566.729 -> and procedures each year, and arthroscopy, or keyhole surgery,

1571.469 -> is a minimally invasive surgical procedure

1573.909 -> on a joint in which an examination and sometimes treatment of damage

1578.189 -> is performed. They developed

1580.469 -> Synergy, the fastest growing video and integration solution

1584.629 -> in operating rooms worldwide.

1587.109 -> The Synergy product portfolio is a comprehensive set

1589.589 -> of interconnected surgical tools and technology

1593.059 -> for the operating room.

1595.019 -> It’s award-winning image system is comprised of 4K cameras

1598.559 -> to put into that keyhole inside a body,

1601.229 -> and monitor and video,

1602.839 -> for the surgeon to see what’s ongoing with data management.

1607.429 -> Arthrex’s interest in AWS IoT Greengrass is for offline data

1611.289 -> processing for mission critical device communication

1614.309 -> during operations and surgeries.

1616.739 -> You don’t want this to go dark doing a procedure

1619.819 -> because of loss of Internet connectivity.

1622.259 -> With AWS IoT Greengrass, Arthrex expects to have improved

1626.209 -> visibility to procedures and much better patient outcomes.

1631.109 -> Another question we got from embedded

1632.719 -> Developers, mainly at original equipment manufacturers

1636.439 -> and microcontroller vendors,

1637.619 -> is “How can I ensure my FreeRTOS libraries are maintained and secure?”

1642.639 -> They want the benefit of official bug fixes

1645.179 -> and security updates in newer releases,

1648.139 -> without increased maintenance cost and project risks,

1651.489 -> when they try to integrate the newer release

1654.509 -> containing additional features in APIs.

1657.939 -> This is why we now offer FreeRTOS long-term support (or short LTS).

1664.239 -> FreeRTOS long-term support libraries give embedded developers at OEMs

1668.839 -> and MCU vendors the predictability and feature stability

1673.349 -> with assurance from AWS of security updates

1676.429 -> and critical bug fixes for two years from release.

1680.699 -> Feature stability:

1682.419 -> FreeRTOS LTS libraries are easy to integrate with applications

1686.459 -> designed for resource constraint MCU based devices.

1691.009 -> Security updates and critical fixes: AWS

1694.449 -> provides ongoing security and maintenance updates for LTS libraries

1699.859 -> to ensure devices meet quality standards and are secure.

1704.189 -> LTS comes with security updates and bug fixes to the FreeRTOS kernel,

1709.019 -> the IoT libraries, and AWS libraries for two years.

1713.859 -> Updateable, the secure connectivity:

1716.179 -> FreeRTOS long-term support comes with a complete set of libraries,

1720.629 -> including IoT libraries and AWS libraries,

1723.659 -> for example, Device Shadows, with secure connectivity

1727.689 -> and over the year (or short OTA) update functionality.

1733.139 -> SOLshare is a provider of peer-to-peer

1735.749 -> solar energy trading platforms and a pay-as-you-

1739.349 -> go solutions for low income households and communities

1742.249 -> in Bangladesh and beyond.

1744.309 -> It provides rural end-customers with a reliable supply of electricity

1749.139 -> while making sure it’s affordable for people

1751.859 -> who are at the lowest echelon of the society.

1755.659 -> SOLshare has developed SOLbazaar, an IoT-driven trading platform

1761.189 -> which enables people to trade their excess solar energy

1763.889 -> generated by solar home systems.

1766.679 -> Consider the SOLbazaar as a dynamic energy marketplace

1770.659 -> where solar home system users come to sell their excess energy

1774.879 -> to non-solar home system users.

1776.919 -> One party earns money, and the other party

1779.739 -> finally gets access to affordable electricity.

1783.845 -> SOLshare uses FreeRTOS LTS on constrained MCUs for microgrid logic

1789.876 -> connecting securely to AWS IoT

1791.696 -> and AWS IoT Core and IoT Greengrass.

1794.769 -> This will help them be more effective

1797.229 -> managing their fleets of peer-to-peer microgrid devices

1800.469 -> that are often in remote, rural locations.

1804.409 -> Earlier we talked about cellular connectivity,

1807.269 -> which is an important enabler of IoT. But what if your IoT applications

1812.719 -> require small sensors with very low battery usage

1816.639 -> and have to last, let’s say, for ten years or so

1819.679 -> and you want them to connect over very long ranges for applications,

1822.959 -> like asset tracking of goods, machinery, or even livestock?

1827.199 -> There is a wireless technology called ‘LoRaWAN,’

1830.649 -> which stands for long-range, wide area network,

1834.169 -> that requires very little power.

1837.159 -> And I am happy to announce AWS IoT Core support for LoRaWAN.

1842.849 -> AWS IoT Core for LoRaWAN is a fully managed feature

1847.529 -> enabling enterprises to connect wireless devices

1850.369 -> that use low-power, long-range wide area network technology

1854.689 -> without developing or operating a LoRaWAN network server themselves.

1860.059 -> It eliminates the undifferentiated development

1862.609 -> work and operational burden

1864.199 -> required to set up and manage an LNS and associated infrastructure thus,

1869.439 -> accelerates the network set up pretty much.

1872.569 -> It comes with support for the open source gateway

1874.939 -> LNS protocol, a software called ‘Basic Station’

1878.829 -> and a gateway qualification program

1881.589 -> that offers pretested gateways to connect with AWS

1884.109 -> IoT Core with a few simple steps,

1886.349 -> And, of course, you can find them in the Device Catalogue.

1888.829 -> You can choose any LoRaWAN compliant sensor device

1891.989 -> for a plug and play experience reducing

1894.139 -> onboarding friction significantly. Its built-in integration

1898.809 -> automatically routes device data to AWS

1901.259 -> IoT Core Rules Engine to accelerate IoT application development.

1905.669 -> And, last but not least, it offers transparent consumption

1908.669 -> based pricing that is cost effective at scale expected to cut total

1914.009 -> cost in half versus a do-it-yourself

1917.089 -> or third party service option. And, there is more …

1920.859 -> We also integrated the public Amazon Sidewalk network,

1925.249 -> which uses similar technology than LoRaWAN with AWS IoT.

1929.139 -> The integration will enable device manufacturers to easily connect

1932.819 -> and manage their Sidewalk devices with AWS

1935.349 -> IoT Core.

1936.599 -> The Amazon Sidewalk network has been designed

1939.229 -> to support a range of consumer devices for use cases

1942.089 -> like locating pets or valuables,

1944.939 -> smart home security and lighting control,

1947.369 -> or remote diagnostic of appliances and tools.

1951.939 -> Most restaurants use notebooks and clipboards for compliance checks.

1956.619 -> ComplianceMate is changing that.

1959.389 -> ComplianceMate offers a solution to address

1962.229 -> a critical need for proactive food safety at restaurants.

1966.919 -> Through a combination of wireless temperature

1968.949 -> sensors mobile technologies and easy to use tools

1973.409 -> built for the modern kitchen,

1975.059 -> ComplianceMate gives you total control

1978.099 -> over food safety and compliance

1980.149 -> at stores. With real time access to temperature data,

1983.799 -> customers can quickly identify operational deficiencies

1987.079 -> and prevent food safety mishaps before they even happen.

1991.769 -> They can also take evidenced-based decisions

1993.949 -> about kitchen processes and staff training.

1997.649 -> ComplianceMate is using AWS IoT Core for LoRaWAN

2001.089 -> to connect temperature sensors in restaurants

2004.369 -> in refrigeration and freezer units.

2006.969 -> These cold climate sensors are devices that leverage LoRaWAN.

2011.469 -> The LoRaWAN device can penetrate very thick walls

2014.829 -> of refrigeration units and can last for years

2018.129 -> without replacement thanks to the low power consumption,

2021.479 -> which reduces the operational cost.

2024.049 -> AWS IoT Core for LoRaWAN eliminates the undifferentiated development work

2030.009 -> and operational burden required for ComplianceMate to set up

2033.819 -> and manage LoRaWAN network servers and associated infrastructure,

2038.649 -> which in turn allows them to more easily

2041.109 -> meet their goal of ensuring customer food safety

2044.619 -> while reducing the risk of food perishing.

2048.779 -> All this technology enables you and our customers

2051.869 -> to connect more and more devices. They now have to manage device fleets

2056.569 -> ranging from thousands to sometimes tens

2059.209 -> or even hundreds of millions of devices

2061.369 -> and must configure update and troubleshoot these devices remotely.

2065.679 -> Typically using a web Application. But developing

2069.089 -> and maintaining a custom application like this for field service engineers

2073.289 -> and support engineers and technicians,

2075.269 -> it’s time consuming and resource intensive,

2077.989 -> particularly as device fleets scale.

2081.129 -> And this is why I am happy to announce preview of Fleet Hub for AWS

2086.309 -> IoT Device Management.

2088.619 -> Fleet Hub for AWS

2089.819 -> IoT Device Management enables you to easily create

2093.559 -> a fully managed web application

2096.199 -> so you can view and interact with your device fleets,

2100.079 -> to monitor device health,

2101.639 -> respond to alarms, take remote actions,

2104.159 -> and reduce time for troubleshooting.

2106.679 -> Fleet Hub integrates with existing identity systems

2109.469 -> like AWS Single Sign On, or Active Directory,

2113.509 -> and AWS organizations for users to sign in

2116.619 -> with the corporate credentials;

2118.499 -> no need to create new logins. Deploy in minutes with no code:

2123.179 -> Administrators can create a web application

2125.559 -> without writing code, add users from the corporate directory

2129.039 -> to enable access to the web application,

2131.369 -> and grant those users privileges

2133.409 -> to manage the web applications themselves.

2135.979 -> Once deployed you can now easily interact with device fleets.

2139.799 -> Let me show you how it looks.

2142.719 -> You can view from your preferred device anywhere.

2145.829 -> Web applications created using Fleet Hub

2148.599 -> can be easily accessed via desktop browser,

2151.489 -> phone, or in this case a tablet.

2154.779 -> As you see in one of the dashboards here,

2157.209 -> you can view the aggregate health metrics of your fleet,

2160.589 -> such as checking connectivity issues, for, let’s say, a fleet of thermostats.

2165.089 -> But you can also filter and drill down

2167.539 -> to specific devices to investigate issues or anomalies

2173.249 -> such as assessing the connection state,

2176.119 -> or other health metrics of a specific thermostat

2178.269 -> within that fleet. You can create alarms to be notified

2181.319 -> when a health metric, for example, device temperature,

2183.879 -> falls below a certain specific threshold.

2186.239 -> And finally, you can take corrective actions.

2189.169 -> Once alerted, you can take built in corrective actions,

2192.539 -> such as deploying a thermal update or rebooting a device.

2196.259 -> Fleet Hub’s seamless integration with the many AWS

2199.389 -> IoT Device Management features allows you to easily interact

2203.059 -> with your devices to, for example, push over the air updates via Jobs

2207.319 -> or open a Secure Tunnel to troubleshoot a device remotely.

2213.149 -> Airties, the most deployed Wi-Fi mesh solution

2217.409 -> for service providers worldwide,

2219.319 -> turned to Fleet Hub as a solution to allow them to visualize,

2222.839 -> interact with the fleets of tens of millions of devices

2226.469 -> without their team having to spend any time

2229.099 -> and resources deploying their own custom solution.

2232.539 -> Their ultimate goal is allowing each operator

2235.749 -> to securely visualize their own fleet,

2238.479 -> perform self-service updates based on specific requirements,

2241.979 -> and access real time reporting.

2245.739 -> Let’s switch gears a little bit

2247.199 -> and look at the analytics and industrial area.

2250.039 -> Industrial customers want to manage and monitor their equipment data

2254.079 -> not only in the cloud… but also directly on the shop floor

2259.039 -> using the same asset models, and APIs, and functionality

2263.189 -> they use in AWS

2264.389 -> IoT SiteWise in the cloud, to help them

2266.419 -> reduce costs, support existing on-premises applications,

2270.169 -> ensure business connectivity, and comply

2273.359 -> with data residency requirements. This is why we built AWS IoT SiteWise

2279.299 -> Edge, in preview today. AWS IoT

2283.149 -> SiteWise Edge is software that runs on-premises at industrial sites

2288.619 -> and makes it easy to collect, process, and monitor equipment

2292.909 -> data on-premises before sending the data to the AWS

2296.389 -> Cloud.

2297.969 -> SiteWise Edge is installed on local hardware

2300.619 -> such as third-party industrial computers or gateways,

2303.849 -> or on AWS Outposts and the AWS Snow Family compute devices.

2308.509 -> It has consistent asset models: once developers have used

2312.549 -> IoT SiteWise to model their equipment in the cloud,

2315.889 -> they can use the very same models with SiteWise Edge at the Edge.

2319.459 -> Local data collection: SiteWise Edge includes a gateway software component

2324.269 -> that runs on popular third-party industrial gateways

2327.539 -> and reads data from onsite data aggregators or historian databases

2331.769 -> using OPC-UA, Modbus-TCP, and EtherNet/IP protocols.

2337.359 -> The gateway software is provided as a pre-packaged AWS

2341.029 -> IoT Greengrass connector for each protocol

2343.519 -> and can be deployed on any device that can run AWS IoT Greengrass.

2348.279 -> It also comes with local data processing.

2351.749 -> The SiteWise Edge developers can now locally process machine data first

2356.819 -> and only send relevant data to the cloud for further analysis

2360.919 -> or cross site visualization.

2363.739 -> Having all the data processed at the Edge

2366.019 -> also means it is available to the local applications

2369.539 -> without connectivity to the cloud,

2371.779 -> and once data is processed data is routed to IoT SiteWise by default.

2377.399 -> But customers can also choose to route data directly to other

2380.749 -> AWS services, such as Amazon S3 or Amazon Timestream, for storage

2385.999 -> and their industrial data lake and additional analytics.

2389.419 -> And it comes with local data monitoring.

2392.779 -> SiteWise Edge includes a local version of the SiteWise

2396.299 -> Monitor visualization application

2398.919 -> which is accessible through a web browser

2401.909 -> for process engineers to locally monitor real-time

2405.689 -> and historical time series asset data. It is disconnected operations capable

2411.569 -> since SiteWise Edge runs on-premise local applications

2415.919 -> that use data from SiteWise Edge will continue to work,

2419.149 -> even when cloud connectivity is disrupted or latency

2422.739 -> sensitivity is high. And there are more great new

2427.199 -> IoT features, like for example, the AWS IoT EduKit.

2431.349 -> A quick starter learning kit that includes hardware

2434.449 -> that you can buy on amazon.com

2435.979 -> just search for EduKit on amazon.com,

2439.099 -> that you can buy there and a guided online workshop

2442.139 -> that helps you start from simple IoT applications

2444.909 -> and add voice controls and machine learning over time.

2448.879 -> And for AWS IoT Core we have now Apache Kafka and VPC Actions.

2453.009 -> It’s a new rule action which allows customers to send data

2456.709 -> from devices connected to AWS IoT Core

2459.179 -> directly to either their self-managed or Amazon-

2462.899 -> managed Apache Kafka (MSK) clusters in a VPC for stream processing.

2467.659 -> And for AWS IoT Device Defender, we now have ML Detect.

2471.589 -> ML Detect automatically sets up

2474.249 -> and updates threshold for security alerts

2477.159 -> based on your device’s behavior using machine learning.

2480.999 -> And you don’t need machine learning experience to use this feature.

2484.999 -> AWS IoT Device Defender now also has Custom Metrics.

2488.619 -> Custom Metrics lets you define your own specialized metrics

2492.259 -> that Device Defender should monitor for your devices like, for example,

2495.919 -> power usage, charge levels for batteries, or details

2499.359 -> about network traffic. And last but not least,

2502.259 -> both IoT SiteWise and IoT Events now have Alarms.

2505.529 -> Define alarms and set up alarm notifications

2508.219 -> within minutes from the AWS IoT SiteWise

2510.699 -> console and display and organize alarm data in a customizable

2515.239 -> SiteWise Monitor web application.

2518.579 -> A company you have heard me speak about before which uses

2521.889 -> SiteWise is the Volkswagen Group,

2524.669 -> the world’s largest automotive manufacturer.

2528.169 -> With the help of AWS, VW is transforming the automotive

2532.989 -> manufacturing industry with one of the largest Industry

2536.589 -> 4.0 projects ever undertaken, to significantly improve production

2542.399 -> and logistics performance across the manufacturing plants.

2546.399 -> The heart of project is Volkswagen’s Digital Production Platform,

2551.009 -> or short DPP, which is a key lever for VW to improve performance by 30%

2557.269 -> to be much more flexible and save billions of dollars.

2562.489 -> The DPP is a global platform that will combine data of all machines,

2568.309 -> Plants, and systems from their more

2570.329 -> than 120 production facilities across the world.

2573.559 -> The DPP is a multitenant secure and scalable platform

2577.439 -> consisting of device, data, and analytic services.

2581.669 -> When it started in 2019 last year,

2584.069 -> the group started with their integration of three main plants.

2587.429 -> This year an additional ten plants from different brands like Porsche,

2591.079 -> SEAT, and Skoda have been connected to DPP.

2594.119 -> With running use cases and earlier this year, in July 2020,

2599.069 -> Volkswagen, together with AWS and Siemens,

2602.749 -> a key Amazon partner network partner in the industrial space,

2606.799 -> announced the expansion of its Industrial Cloud initiative,

2611.229 -> which extends the DPP capabilities to a community of partners

2615.229 -> and suppliers beyond Volkswagen to deliver an open architecture

2619.689 -> and set of services where partners can collaborate to build solutions

2624.129 -> that can also benefit their own

2626.299 -> manufacturing plants and supply chain processes.

2629.399 -> If you just take VW’s 1,500 key suppliers alone,

2634.899 -> we are talking about another 30,000 industrial facilities worldwide.

2640.439 -> I highly encourage you to view other dedicated breakout sessions

2644.429 -> at re:Invent this year where you will hear from VW

2647.569 -> on the great process and progress

2649.779 -> they have been making with this initiative.

2653.649 -> Going from manufacturing cars to using them.

2656.939 -> BlackBerry is a leading provider of end-to-end mobility solutions,

2661.189 -> including automotive.

2662.869 -> BlackBerry QNX software is used by ten out of ten automakers

2667.599 -> and its inside more than 175 million vehicles on the road today.

2673.739 -> And BlackBerry QNX is partnering with AWS to provide IVY,

2678.069 -> a new embedded software that runs inside a vehicle

2681.749 -> and integrates with the AWS

2683.019 -> Cloud for provisioning, updatability, and machine learning capabilities.

2688.049 -> It will allow consistent, flexible,

2690.639 -> and secure access to sensor data for developers and applications

2695.119 -> with OEM’s retaining full ownership and control of the vehicle data.

2701.039 -> It also enables the creation of new synthetic sensors,

2704.829 -> which allows applications to be deployed

2707.539 -> at scale across fleets of cars,

2710.069 -> irrespective of the underlying differences in vehicle architectures.

2714.879 -> For example, with IVY, automakers can create a synthetic occupant

2719.319 -> sensor leveraging in-cabin sensors, such as cameras, or seat sensors,

2723.769 -> or sound sensors,

2725.009 -> and others to determine how many occupants are in a vehicle

2728.699 -> and if they are pets, adults, or children.

2731.809 -> Automakers could then share the occupancy information

2734.699 -> via APIs with first or third party applications

2737.659 -> To, for example, recommend the use of the child lock feature,

2741.099 -> or notify a driver if a child is left alone in the vehicle in the sun,

2745.679 -> or restrict music lyrics if children are present,

2748.559 -> or offer geotagged advertisement

2751.079 -> depending on the occupants in the vehicle.

2755.159 -> And another customer that is going through the full circle,

2758.769 -> operating devices at the Edge, connecting

2761.139 -> and controlling large device fleets at scale,

2763.619 -> and analyzing data for a better tomorrow is Vector,

2767.749 -> one of New Zealand’s largest energy companies.

2771.019 -> And it is my pleasure and honor to introduce to you Simon Mackenzie,

2774.989 -> Group CEO, and Nikhil Ravishankar, Chief Digital Officer,

2779.229 -> who will tell you how they use AWS IoT

2782.619 -> to deliver consumers more affordable reliable and cleaner energy options.

2789.839 -> Kia ora, everyone, Simon Mackenzie, Chief Executive of Vector,

2795.689 -> we’re based in New Zealand and joining me in a short

2798.239 -> while will be Nikhil Ravishankar, our Chief Digital Officer.

2802.549 -> We’re really pleased to be here joining you today

2805.099 -> and in particular, our collaboration with AWS

2808.219 -> and what we see as a really exciting platform

2811.079 -> that’s really going to make a huge change

2812.799 -> to the global energy market.

2814.399 -> So quickly just a little bit about Vector,

2817.199 -> we’re a listed company based in Auckland, New Zealand,

2820.609 -> we operate a portfolio of businesses in the energy sector,

2825.379 -> electricity distribution, gas distribution,

2827.909 -> fiber optics, smart meters in New Zealand and in Australia,

2833.109 -> solar battery technology across the Pacific,

2836.499 -> and a range of other businesses that really fulfill our whole focus

2842.439 -> on creating a new energy future, that’s our vision,

2846.099 -> and our Symphony is known as our Symphony strategy.

2849.449 -> With regards to Symphony strategy, what it’s about for us,

2853.719 -> is seeing disruption and the challenges globally

2857.259 -> is a real opportunity,

2859.209 -> and in collaboration with partners such as AWS,

2862.639 -> how do we actually bring new services and solutions

2866.279 -> to customers with customers being at the heart of our thinking

2871.909 -> and the way in which we consider our services?

2875.199 -> This is unlike what we see now

2877.609 -> that traditionally, in an energy market kind of structure,

2880.929 -> which has been very traditional in the sense

2884.599 -> that it started with generation

2887.629 -> and then the generation sector we saw a lot of fossil fuels.

2891.519 -> Luckily, in New Zealand, we have a lot of renewable energy.

2894.699 -> Then through the transmission sector through to the distribution

2898.269 -> to reticulate that energy around cities and communities

2903.569 -> and then obviously to customers through retailers,

2907.669 -> but this model is really out of date nowadays.

2910.629 -> It’s a very traditional model.

2912.249 -> It’s really a single flow from the generation to the customer,

2916.499 -> and what we see is becoming very prevalent now

2919.479 -> to deal with the challenges of the market

2922.469 -> and what customers are needing

2924.459 -> is a much more dynamic integrated market

2928.949 -> where many of the technologies that are being deployed

2932.279 -> to deal with the challenges globally of decarbonization,

2935.979 -> energy affordability, choice for customers,

2939.519 -> electrification of transport, and in particular,

2943.859 -> the need to actually coordinate all these solutions

2948.169 -> and provide platforms and capital efficiency

2952.519 -> to actually ensure that an energy system

2955.509 -> can actually play its part in the challenges

2958.819 -> for everyone globally, not only in New Zealand.

2963.249 -> So our collaboration with AWS is really centered on

2967.619 -> how do we actually take the foundation of this system,

2971.909 -> and one of those foundations is the information

2975.459 -> and the information from smart meters,

2978.579 -> and then create the platforms that will enable the analysis

2981.889 -> and processing of this information

2984.229 -> to really effectively change the models

2988.109 -> that are prevalent in the market, provide the services to our customers

2992.589 -> and obviously provide those choices to customers

2996.879 -> that are using the energy such that

3000.609 -> we can actually adopt a lot of these new technology

3003.259 -> to deal with these changes that we’ve talked about.

3006.269 -> I will hand over now to Nikhil Ravishankar

3009.899 -> who is going to talk about the nature of our relationship with AWS.

3015.949 -> As I mentioned, we’re really proud to be in collaboration

3018.929 -> with AWS through a strategic alliance

3021.819 -> to really bring a totally new framework

3025.199 -> to the use of information to the storage of information

3030.519 -> but, more importantly,

3031.779 -> to be able to develop those products and services

3034.139 -> that will enable these Edge devices

3036.769 -> to meet those challenges I talked about.

3039.529 -> Thank you, Simon, I will now just spend a couple of moments

3042.389 -> just talking about what the new energy platform

3044.829 -> actually is and the types of challenges

3047.859 -> that we’re trying to address with this platform,

3050.249 -> but before I start I think it’s worth reiterating the Symphony strategy

3054.459 -> and describe that a little bit more.

3057.039 -> The core for us about the Symphony strategy

3059.259 -> is finally putting the end consumer

3061.879 -> at the centre of the new energy value chain.

3064.489 -> Historically, the consumer has been a passive user of energy

3069.009 -> and the energy systems, of the current energy systems

3072.599 -> and the systems of the past have been very supply-centric.

3076.059 -> In this new world we’re no longer passive consumers of energy

3079.529 -> but also we get to make, store, trade, share energy

3084.749 -> in ways we haven’t been able to do so in the past.

3087.899 -> So the new energy platform is all about enabling this new future.

3092.359 -> AWS and Vector have been working together for a number of years now.

3096.329 -> We started our relationship really with hosting a metering data

3102.319 -> on the AWS Cloud a number of years ago

3105.819 -> and processing that data on AWS’s Cloud storage and compute services.

3112.369 -> Since then, working with another organization called mPrest,

3116.179 -> we delivered an internet of energy platform

3119.319 -> that really starts to integrate the emerging customer

3122.909 -> Edge with the core energy system.

3125.449 -> It’s a field that is commonly referred to DERMS,

3128.569 -> or distributed energy resource management.

3131.579 -> We’re now taking that heritage of collaboration

3133.719 -> a step further through this new strategic alliance

3136.259 -> and we’re developing what we call the ‘New Energy Platform.’

3139.789 -> The best way to really think about the New Energy Platform

3142.129 -> is an app store for energy, specific apps,

3146.319 -> and the first of the applications

3147.919 -> that we look to develop on the platform

3150.009 -> is what we’re referring to as

3151.149 -> the ‘meter information management platform.’

3153.739 -> Today, the meter is the best representation

3155.899 -> of what’s happening at the customer Edge

3157.959 -> and it’s extremely important to get that data

3161.919 -> into the right parts of the value chain

3164.199 -> such that we can create new products and services

3166.939 -> that allow customers to access more affordable,

3170.189 -> more reliable and cleaner energy.

3172.509 -> So the New Energy Platform,

3174.509 -> or the application of the New Energy Platform,

3176.739 -> the meter information management platform,

3178.659 -> the MIP, really leverages AWS services such as Lambda

3184.179 -> and more importantly AWS IoT services,

3187.679 -> which is at the heart of what we’re trying

3189.279 -> to leverage to develop the MIP, AWS analytic services,

3194.309 -> and of course the base storage and compute services

3196.869 -> that go along with that.

3198.699 -> Leveraging these services, we’re flipping the model on the head,

3201.859 -> where these domains have been really application-centric,

3207.219 -> and really it's the main players in this space

3211.279 -> have large monolithic applications.

3213.779 -> We’re changing the script and we’re trying to tackle this

3216.529 -> as an IoT and a big data and analytics problem,

3220.489 -> and in doing so we are changing the absolute performance

3225.679 -> that’s available but also, enable new market models

3229.439 -> such as peer-to-peer training

3231.109 -> or in the case of a very specific example,

3233.779 -> this application will be leveraged to help transition Australia

3238.339 -> from a 30 minute market model

3240.169 -> to a 5 minute higher frequency market model.

3243.599 -> One of the defining aspects of this collaboration

3246.559 -> besides the services we get to access to then leverage

3249.959 -> and build the MIP in the New Energy Platform,

3253.029 -> is really the fact that we are co-developing

3256.179 -> this with Vector and AWS engineers, and a large part of the process

3261.999 -> to get us to this space was really around understanding

3264.939 -> whether there would be a strong cultural fit,

3267.469 -> and what’s been incredible is the fact that both organizations

3272.399 -> have had a chance to look under the covers

3274.669 -> and there is a lot of mindset alignment

3277.539 -> and a cultural alignment as we go down this journey,

3281.609 -> and core to all of this is two organizations

3283.849 -> that truly believe empowering the customer is

3286.989 -> the be-all-and-end-all in whatever sector you’re operating in.

3290.369 -> So, it’s quite exciting for us to be part of this alliance

3294.289 -> and we’re quite excited to also announce

3297.169 -> that first of our MIP services is in production and live today

3302.209 -> and that’s for the New Zealand market at this stage,

3304.769 -> but we are quite excited to start bringing that

3307.149 -> to a much more global audience.

3309.489 -> So, if you are looking for any further information

3312.139 -> of the NEP itself or the first of its applications,

3315.979 -> please feel free to contact us

3317.299 -> and we would be more than happy to have a discussion.

3322.259 -> Thank you, Simon and Nikhil, that was a great overview

3325.629 -> of what Vector has set out to do and achieve

3328.359 -> with the help of AWS IoT and AWS.

3331.809 -> For the past hour I have shown you how AWS IoT

3335.369 -> is allowing customers to connect today

3337.989 -> and transform tomorrow building better products for a better future,

3342.069 -> but there is more that sets us apart.

3345.069 -> We offer the most secure Cloud and Edge,

3347.749 -> so you can trust your fleets and data are secure.

3351.619 -> AWS is the most secure Cloud with the most standards

3355.139 -> and compliance certification of any Cloud provider,

3359.359 -> and at the Edge we use the same security mechanisms

3363.029 -> as in the cloud for data encryption and mutual authentication

3366.619 -> and support additional industry standards, like PKCS 11

3371.289 -> to benefit from hardware specific features like secure elements.

3375.829 -> For memory safety in FreeRTOS,

3378.009 -> we have gone beyond expected techniques

3381.099 -> and also provide formal memory safety proof tests

3386.629 -> that run each time code is checked in.

3389.919 -> We offer automated scaling with serverless

3392.999 -> so you only have to pay for what you use.

3396.599 -> AWS IoT is built completely serverless and multitenant,

3401.449 -> which means you can connect one single or 100 million devices

3406.329 -> without ever thinking about the underlying infrastructure.

3410.329 -> We removed all infrastructure management tasks for our customers

3415.099 -> so you don’t have to worry about capacity planning,

3418.439 -> clustering, sharding, cell infrastructure, et cetera,

3422.549 -> which gets more and more complicated the larger your fleets grow.

3426.629 -> This also means you truly only have to pay for what you use.

3431.099 -> There is no minimum fees or anything or mandatory service usage,

3435.429 -> nor is there an instance fee that you have to pay

3438.679 -> whether you utilize the instance to its maximum or not.

3442.959 -> We also have the broadest and deepest Edge to Cloud offerings,

3446.699 -> so you can do whatever, whenever, wherever.

3450.309 -> AWS has more fully featured services

3453.519 -> and the largest global infrastructure footprint of any provider.

3457.749 -> This footprint is constantly Increasing. And at the Edge, AWS

3462.789 -> has the most breadth, from the smallest sensors,

3465.649 -> over gateways, industrial PCs, to specialized equipment,

3469.369 -> up to dedicated AWS infrastructure at your premises.

3473.909 -> And we have unmatched experience, maturity, and reach

3477.339 -> so you can accelerate your digital journey.

3480.919 -> Wherever you are in your journey,

3482.849 -> and no matter what approach you want to take,

3485.529 -> build yourself, contract a partner, or deploy readymade solutions,

3490.439 -> we can help you get there with our services, partners, and solutions.

3495.019 -> The problems you haven’t anticipated yet

3497.759 -> there’s a high likelihood that we have already solved them.

3500.899 -> As our CEO likes to say,

3502.769 -> “There is no compression algorithm for experience.”

3507.389 -> Which brings me back to you, our customers and partners.

3511.779 -> Now that you can know the state of every thing

3515.819 -> and you can reason on top of that data,

3518.599 -> what problems would you solve?

3521.109 -> To learn more about AWS IoT visit us at aws.amazon.com/iot,

3527.629 -> and if you want to see what other problems

3529.979 -> our customers and partners solve with AWS

3532.049 -> IoT, please visit any of the specialized sessions

3535.219 -> under reinvent.awsevents.com/iot.

3540.479 -> With this I would like to end the session

3543.029 -> by thanking my co-speakers, Simon and Nikhil from Vector,

3546.549 -> as well as you, our audience,

3548.969 -> for your attention and interest in attending this session.

3552.193 -> Thank you very much and have a great re:Invent 2020.

3559.668 -> [music playing]

Source: https://www.youtube.com/watch?v=C3abggYsaBM