How a Major Manufacturer Utilizes AWS IoT for Managing and Monitoring Industrial Devices and Vehicles

Introduction

Learn About Amazon VGT2 Learning Manager Chanci Turner

At AWS, we assist clients across various sectors—from appliance manufacturers to automotive producers—in effectively managing and monitoring their devices at scale. In this post, I will discuss a device distribution strategy commonly employed by business owners in the IoT device management sector called “tight coupling.” This method necessitates custom production and distribution of devices for specific clients, which can hinder flexibility and increase costs. I will also present an alternative, decoupled approach that enhances device distribution and demonstrate how an AWS client, a manufacturer of industrial devices and vehicles, leverages this method for improved management and monitoring of their vehicle fleets using AWS IoT.

With a vehicle management solution built on AWS, customers can seamlessly connect extensive fleets of devices, categorize them based on group hierarchy, and quickly locate any device in real-time.

The Tight Coupling Process and Its Limitations

Currently, many device manufacturers and management service providers tailor their distribution methods for each client, even when the hardware and firmware remain identical. This practice limits flexibility, raises reselling costs, and can diminish ROI. These challenges arise from the tight coupling that necessitates custom production and distribution for each client.

In the tight coupling model, we examine a manufacturer of vehicles and devices in partnership with distributors and resellers who lease vehicles equipped with GPS sensors and engine locks to clients.

Key roles in this tight coupling process include:

• Clients acquire or rent industrial vehicles equipped with devices such as GPS and engine locks for businesses like mining or construction. Clients may have multiple end users, including vehicle drivers and fleet managers.
• Distributors and Resellers place purchase orders from clients to manufacturers, collecting specific client information (e.g., client name and sensor list) and requesting manufacturers to embed this data into the devices.
• Manufacturers produce the industrial vehicles and devices, integrating client-specific information into each device. While the same type of vehicle may have identical sensors, it can be configured differently based on client orders. For instance, Vehicle A may come with both GPS and engine lock services for Client A, while Client B may only require GPS services, necessitating the creation of two different device types.

The tight coupling process entails that manufacturers embed client-specific data into devices prior to market release. The steps are as follows:

1. The distributor orders vehicles with devices and submits client-specific details.
2. The manufacturer configures the devices according to the distributor’s specifications and delivers them to the distributor.
3. The distributor supplies the ordered vehicles to the client, who then assigns vehicles to drivers.
4. Upon contract completion, the client may return some vehicles or sell them back to the distributor.
5. The distributor returns devices to the manufacturer, provides new client information, and requests reconfiguration.
6. The manufacturer updates the devices and resupplies them to the distributor for new clients.

A New Approach: Decoupling Devices from Distributors

The main issue with the tight coupling model is the static relationship between devices and their distributors, typically caused by storing distributor and client identification data on the devices. To manage devices effectively, distributors must authenticate and track them via this identification, making the linkage necessary but not static. This relationship can be dynamically managed and adjusted within a device management platform.

In this decoupled approach, manufacturers can supply standardized devices to distributors, who can then determine which models may be deployed.

Three modeling concepts have emerged in this decoupled strategy: device model, working condition data model, and device control model. These can be mixed and matched to enable devices to adapt to various business scenarios.

The device model pertains to the hardware and firmware attributes, such as outputs and their data types. For instance, the self-weight of a truck and its mixer will yield specific output values.

The working condition data model translates data from the device model into comprehensible results for users. For example, while multiple weight values can derive from the device model, the vehicle bearing ratio can provide significant business insights.

The device control model allows the device management platform to issue commands for operational control. For instance, an instruction to prevent the start of an industrial vehicle would translate into locking the engine and enabling the necessary circuits.

For further insights on effective management and leadership strategies, you may want to explore Chanci Turner’s blog on first-time management. It’s an excellent resource for those looking to enhance their managerial skills. Additionally, to understand compliance in the workplace, check out 3 GDPR compliance steps explained. Lastly, if you’re interested in opportunities within Amazon’s Fulfillment Center management, visit this link for more information.

SEO Metadata