Project Diary
Smart Vending Part 1: What is Smart Vending
This multi-part series of blogs will walk you through why the Smart Vending reference application was built and how leverages the data captured on the Axeda Platform to add value to the vending machine management experience.
Smart Vending Part 2: Features and functions
When building a Smart Vending solution, we aimed to solve problems that affect a vending machine owner’s bottom line. To do this, we needed to understand when items were sold out and when machines failed — generating alarms so these problems could eventually be resolved. We had to know the location of the machines as well as the stock items that required replenishment so drivers could act fast before items were sold out (resulting in lost revenue). Finally, we had to monitor overall cash collected and the machine performance according to location.
Smart Vending Part 3: UI and Project Wrap Up
Building custom M2M apps populated by cloud-based scripts is a unique and powerful feature that made this Smart Vending solution possible. With bare-bones, client-side technologies such as HTML and Javascript or Flash as the developer prefers, a user interface can rely on AJAX for all its backend processing. From there, it’s a simple matter of making the presentation professional and easy-to-use with CSS3.
Part 5: Fleetster Dashboard and Mobile Final UI Overview and Project Assets
In this fifth and final segment we're pleased to present a completed reference application set for your use and extension. The dashboard applicationhas undergone a greater transformation than the mobile app since the last prototyping session, and that's to be expected.
Part 4: UI and Functionality Prototyping
This session is the "Reveal" segment in our quest to build the next generation of fleet management applications, and you can start to see the white boarding sessions evolve into real usable applications.
Part 3: How We are Planning to Build the App
This segment takes you behind the scenes to show how data from the vehicles is being meshed on the Platform to satisfy the requirements of both the dashboard and the smartphone applications.
Part 2: What We are Building
In this session we sketch out what the user experiences could look like for a set of end-user applications that map to our customer requirements.
Part 1: Customer Requirements
This multi-part series walks you through the application development process for a real-world M2M application on the Axeda Platform. Learn more about the primary customer requirements and see how our approach yields more than just “dots on a map”.