What to Consider When Designing an IoT Solution
Part 3: Telematics and Data Transmission
As mentioned earlier in my blog, there is an extreme amount of information available on machines today so you may ask yourself, "how do I get to that information without being at the machine or taking it out of service?" This is where data transmission comes into play. Whether you're looking to store all of the information on the machine until it returns to the "barn" for data upload via Wi-Fi, or you're expecting real-time updates from the machine over cellular service while it's operating, there are options available. Other questions you may struggle with are, "What transmission type should I use and will it work for all of my use cases without costing thousands of dollars over the life of the solution?" To help answer these questions, a new set of questions need to be answered:
- What data is most valuable for the end-user?
- When does the end-user need the data?
- Where will the data be collected and/or used?
The answers to these questions will help define what transmission technology you'll need for your solution today, but don't forget about the future. Many of these transmission technologies, especially celluar, change over time which is why you may want to look at hardware with multiple transmission capabilities. While these module types may initially be more expensive, they could save hundreds if not thousands of dollars from a Total Cost of Ownership (TCO) perspective.
Data Transmission - Local Access
Data transmission is typically viewed as "the act of sending data over the internet to a website" but it can mean other things. For example, technicians have been receiving data from machines through a physical cable connection for years to give their service tools ways to communicate with the machine when working on them. Now we're starting to see these service tools and web interfaces pre-installed on a Telematics module and installed directly on the machine. This allows technicians or even operators "Local Access" to the machines data from any PC or smart device via an Ethernet or Wi-Fi connection. This local access to data doesn't end with the technician. Workflow processes can be improved, safety regulations enforced, and even inventory management can be achieved through the use of an on-module web interface developed and used by any individual who works with or in close proximity of the telematics module and asset.
Related Blog Posts:
Part 1: What is Telematics and Why is it Important?
Part 2: Telematics and Data Collection
Part 4: Telematics and Data Aggregation, Visualization and Storage
More on Telematics
Meet The Author
Chad Repp is the Business Development Manager of the CANect Telematics product family at HED where he works closely with internal and external customers to design, develop and implement best-in-class end-to-end Telematics solutions. Chad has over 20 years of asset mobility experience specifically in solution architecture and design. Prior to joining HED, Chad was the Manager of Business Development & Strategic Planning for Verizon Wireless supporting various end-to-end solutions focused on Telematics and IoT.
Please wait while we gather your results.
Servicing the Military as a Small Company in the Face of Increasing CMMC Regulations
In his blog post, Kevin Malliet, Key Account Manager for HED, talks about the extreme importance of OEM’s supplier sourcing, particularly in the military market and navigating its highly restrained regulatory landscape. Published 4/13/2021
5 Reasons Telematics (IoT) Projects Fail - Reason #1: The Real Cost of Telematics
In this blog Jayson Pierringer, HED Software Development Team Leader talks about 5 Reasons Telematics Projects Fail and provides ways to avoid unforeseen project management and customer facing issues. Published: 2/8/2021