Location module
Designing map functionality within the location module to help deployers overseeing and organizing their devices in a Location.
TL;DR
The full story
01
Where we started
About Wiliot platform
Wiliot’s Cloud processes sensory data from IoT Pixels for supply chain insights, managing assets and devices while enabling third-party analysis and providing demo tools to test and demonstrate its technology
01
Current design
Location page- Zones tab
01
Location page- Device tab
02
What goals we set up
The Location page is the hart of the deployment process
Enhancing the location module within the platform to facilitate users in efficiently managing deployments within their designated locations.
Providing a comprehensive overview of deployments on the platform.
Enabling effective monitoring of deployment activities.
03
How we learned
We carried out user interviews to understand how the Location module is used and identify its missing features
conclusions
“These key points highlight the importance of documentation, association methods, mapping, alerting, and metadata in the device deployment process.
Additionally, considerations for working environments and specific processes for deploying certain devices were identified.”
1. Deployment is based on defined custom events.
2. Comments are added to devices for additional context.
3. Some facilities restrict the use of laptops, prompting consideration for mobile solutions.
1. Different methods are used for associating devices in different location types
2. Associations should be made from the full list of Bridges associated with the account.
1. Alerts are created using “opsgenie” to indicate device downtime.
2. There’s a desire for map notifications.
3. Device status is important for monitoring.
1. Exploring ways to save the specific location of devices for API use.
2. Metadata should be added to devices for additional information: Photos, timestamp, details of placement.
1. Currently using three different maps in a different environment for devices: Gateways, Bridges, and Pixels.
04
What we planed
Action Items
Based on the insights from the interviews we conducted, we have determined our action items for the redesign of the Location module.
Integrating the capability to position devices on a map. and allow users to add metadata to devices
Enhancing the usability of the Location module including the creation of default Zone
Permitting users to delve deeper into zones to view the list of devices.
Define roles and permissions for actions in the map feature.
05
What we tested
Wireframe
06
Where do we aim to grow
Outcome and future steps
Map integration in the location system will happen in stages, starting with an emphasis on the Minimum Viable Product (MVP) for current deployment sustainability.
Priority is given to reconstructing the location module with a default zone before introducing the maps feature.
Additionally, metadata for zones and devices, including API integration, is a key focus.
Monitoring activities are planned for later stages after MVP completion.
