Worker Ops Views

HyperTrack provide different embeddable Ops Views that are Worker centric.

Worker List/Map View

The Worker list/map view provides a list of the worker fleet in a tabular format or on the map. It provides powerful filters that allow Ops teams to slice and view aggregated segments of data based on a time range, profile, Ops Groups and much more. Once an Ops member has found the segment of workers, they can export it to analyze the data further.

List View

Sample URL:

https://embed.hypertrack.com/views/workers?token=<token from OAuth API>

Map View

Sample URL:

https://dashboard.hypertrack.com/drivers?token=<token from OAuth API>&driver-view=map

Restrict views based on Ops teams

The Worker List/Map view can be customized for your teams or customers. You can filter the data in these views based on the metadata provided for each order or operations group you've set up.

For instance, ops managers might need to see where their team members are, or you might want to create restricted views for different clients in an operations dashboard.

To achieve this, use metadata filters in the URL when embedding these dashboards into your web application. The embed view URL can include a profile_filter parameter that reflects your current selection.

Example:

https://embed.hypertrack.com/orders?token=<token from OAuth API>&profile_filter=%7B%22team_id%22%3A%22106%22%7D

📘

Your worker profile can only have one layer of nesting and must be a valid JSON

Example - { "team_id": 20240812 }

Your browser will most likely encode { } and : special characters, but when distributing embed URLs with a metadata_filter, be sure to encode your link. To read more about URL encoding, please read this guide.

Worker Timeline View

The Worker Profile view provides the entire timeline of events that occurred for a worker on the selected date. The combination of the timeline and the map enables your Ops teams to have visibility into all the work done by their team member with specific timestamps. the replay feature provides the ability to see the path traversed by the worker to help triage location based escalations.

Worker Analytics

It's important to ensure that all your workers are being tracked as expected. In order to provide this visibility, we provide aggregated metric charts in your Worker Ops List view that helps identify behavioral or integration issues that can be causing the poor tracking of your fleet. This view can help Ops look back in past 7 days to understand the fleet behavior trends for your business.

Workers Chart

This chart offers a daily snapshot of successfully tracked versus untracked workers within the selected time range. It’s crucial to keep the untracked count low to ensure your teams have full visibility into all field activities.

Tracking Health

This chart provides the score of how well your workers track during their shifts. A high tracking health score ensures that during the lifetime of your orders, sufficient ground truth was available to help your Ops teams have visibility.

Outages

This chart provides the day-wise split of outages that impacted your worker fleet. These outages have been distributed within buckets to reflect the cause. Learn more about the different outages here.

In addition, we provide an action report that helps you quickly identify the top impacting outages and the steps you need to take to resolve them.

Embed Customizations

We provide the ability to customize, show and hide elements in our embeddable Worker Ops view. Each of the options can be provided as URL parameters to configure your custom embed experience.

Example format for the  Embed URL:

https://embed.hypertrack.com/views/drivers/<driver_handle>?token=<token from OAuth API>&isAdmin=true&view=devices&driver-state=<b64_encoded_str>

Example Usage for driver-list-state

let obj = {"ops_groups": ["test-ops-group", "b33ed748-e17f-4d93-905d-7238837736c6"], "tracking": "true"}
let urlEncodedStateString = encodeURIComponent(btoa(JSON.stringify(obj))) // B64 encoding followed by URI encoding
console.log(urlEncodedStateString)

// The value below can then be passed as the value of the `driver-list-state` query param.
// eyJvcHNfZ3JvdXBzIjpbInBiLXRlc3RpbmciLCJiMjdlZDc0OC1lMTdmLTRkOTMtOTA1ZC03MjM4ODM3NzM2YzYiXSwidHJhY2tpbmciOiJ0cnVlIn0%3D