UGAC Yatrik use cases
Connect location
to the work
that follows.
A vehicle to coordinate. Equipment to locate. A field task to complete.
See how our location tracking and operational coordination software connects assets, people and recorded movement with practical workflows.
UGAC hardware + software, or software-only access with compatible location sources.
Start with your operation.
Explore the scenario closest to your work. Each explains the software actions, example workflow and deployment scope.
and field teamsFleet visibility, deliveries, service work, construction, rentals and operational follow-up.View business use casesPersonal useYour items.
Your trusted contacts.Personal vehicles and belongings, recorded history and controlled sharing.View personal use casesDevices and integrationsConnect the sources
you work with.GNSS receiver data, existing trackers and location information for business systems.View integration use cases
These scenarios describe applications of Yatrik’s capabilities, not customer deployment claims. Features depend on account permissions, hardware, available data and agreed configuration.
Business operations
Fleet and transport visibility
For: Transport operators, fleet managers and teams coordinating company vehicles.
Where was a vehicle last reported, how recent is that position, and what happened along its journey? Yatrik gives your team a shared location reference for answering these questions.
What Yatrik can do
- Link a compatible tracking device to the vehicle it represents.
- View the latest available position together with its timestamp and reporting information.
- Review recorded movement, trips and location history to investigate a journey.
- Inspect available location-quality fields before relying on a reading.
Example workflow
- Connect a vehicle and tracker
- Review its position and recorded trip
- Follow up using a shared location record
Deployment requirements and scope
Position updates and coverage depend on the tracker, power and connectivity. A map position does not imply continuous live coverage or a guaranteed arrival time.
Business operations
Delivery and distribution coordination
For: Delivery operators, distributors and businesses assigning transport jobs.
A delivery involves more than a moving vehicle. Dispatchers need to connect the job, the responsible driver, its progress and the information a recipient is allowed to see.
What Yatrik can do
- Assign delivery jobs from the dispatch workflow.
- Give drivers a focused web workspace for assigned work and progress updates.
- Record job completion from the driver workspace.
- Send recipients a tracking link with limited visibility.
Example workflow
- Assign a delivery to a driver
- Update progress and completion
- Share the recipient tracking view
Deployment requirements and scope
Queued driver completion updates can synchronize after connectivity returns. This does not imply fully offline operation, route optimization or guaranteed arrival predictions.
Business operations
Field service and technician coordination
For: Service teams, installers, maintenance technicians and inspection personnel.
Field activity becomes harder to coordinate when assignments, progress updates and location context sit in separate conversations. Yatrik connects field tasks with the people responsible for them.
What Yatrik can do
- Assign tasks to field personnel.
- Let workers view their assigned work in the workforce web application.
- Capture progress and completion updates against the assignment.
- Review authorized operational records alongside relevant location context.
Example workflow
- Assign a field task
- Let the worker update its progress
- Review completion and follow-up records
Deployment requirements and scope
Location availability depends on the authorized source, permissions and consent. Payroll, biometric attendance and a full HR system are outside the capabilities described here.
Business operations
Construction and mobile equipment visibility
For: Contractors, project teams and organizations managing movable machinery or equipment.
Equipment moves between yards, sites and operating areas. Teams need to check its last reported location and understand movement relative to the boundaries that matter to the project.
What Yatrik can do
- Register machinery or equipment as assets and associate suitable tracking devices.
- Inspect the latest available position and recorded movement of tagged equipment.
- Draw geofences around relevant sites or operating boundaries.
- Review configured entry, exit or dwell events where the deployment supports them.
Example workflow
- Register equipment and site boundaries
- Review reported positions and movement
- Investigate boundary events
Deployment requirements and scope
Hardware must suit power, mounting, weather and connectivity conditions. Fuel measurement and engine diagnostics require additional compatible data sources.
Business operations
Rental and shared equipment oversight
For: Businesses renting or sharing vehicles, machinery and other movable equipment.
During an equipment assignment, the owner may need to locate an asset, review its recorded movement or give someone limited visibility without exposing the whole account.
What Yatrik can do
- Associate compatible trackers with rental or shared assets.
- Check where equipment was last reported and review available history.
- Review movement against configured zones.
- Use controlled sharing when limited external visibility is appropriate.
Example workflow
- Connect the asset to a suitable tracker
- Review history during the assignment
- Share permitted visibility or follow up on an exception
Deployment requirements and scope
Rental contracts, deposits, payment collection and remote immobilization are not implied features. Sharing and zone workflows depend on the agreed deployment.
Business operations
Multi-location operations and exception follow-up
For: Organizations coordinating assets and field activity across operating areas.
When a location event needs attention, the next question is who owns the asset, which device produced the reading and what follow-up is needed. Yatrik connects the related records so an exception has context.
What Yatrik can do
- Use customer maps and alerts to review relevant location events.
- Connect authorized asset, device and worker records during operational review.
- Identify the responsible record or assigned work when investigating an exception.
- Discuss UGAC-assisted investigation, work queues, approvals or handovers as a separately scoped service.
Example workflow
- Review a location event
- Inspect related authorized records
- Coordinate the agreed follow-up
Deployment requirements and scope
The UGAC Operations Center and Mission Control are restricted staff tools, not automatic customer entitlements. Advanced operational support and internal workflows require a separate agreed scope.
Personal use
Personal vehicle and item tracking
For: Individuals managing their own vehicles or belongings.
Personal users need a focused way to check a tracked item, review its history and share selected location information when appropriate.
What Yatrik can do
- Use the personal web workspace for tracked items and places.
- Check the latest available position and inspect the recorded timeline.
- Review the alerts enabled for your account.
- Share limited visibility using sharing controls.
Example workflow
- Connect an item or location source
- Check its position and timeline
- Share selected visibility when needed
Deployment requirements and scope
A suitable tracker or compatible phone source is required. Phone sources depend on browser permission, connectivity and operating-system behavior. Continuous background tracking, recovery and emergency response are not guaranteed.
Personal use
Family and trusted-contact sharing
For: Personal users who want to share location information with selected people.
A trusted contact may need access to a particular location view without unrestricted access to every item and record in the account.
What Yatrik can do
- Use family-access and sharing workflows.
- Give selected recipients access within the permissions available to the account.
- Use limited or expiring sharing links where enabled.
- Keep visibility tied to the configured scope of the sharing workflow.
Example workflow
- Choose the information to share
- Set the access scope
- Give the intended contact permitted visibility
Deployment requirements and scope
People-related tracking requires appropriate permission and consent. Sharing availability and scope depend on enabled features. Yatrik is not a substitute for emergency services.
Devices and integrations
GNSS receiver and field positioning monitoring
For: GNSS teams, field engineers and organizations evaluating receiver output.
A map coordinate alone does not explain how a position was obtained. Technical teams may need to inspect receiver data and the quality fields that accompanied a reading.
What Yatrik can do
- Ingest GNSS receiver observations through an assessed telemetry path.
- Inspect available fix type, satellite count, HDOP and accuracy metadata.
- Review position records with their available timestamps and source context.
- Discuss compatible NMEA receiver configurations, including documented F9P-class and suitably configured NEO-6M-style sources.
Example workflow
- Assess the receiver and data fields
- Connect the receiver telemetry
- Review positions with available quality metadata
Deployment requirements and scope
HDOP describes satellite geometry, not accuracy in metres. Accuracy depends on equipment, environment and corrections. Yatrik is not a complete surveying, cadastral or GNSS post-processing suite.
Devices and integrations
Existing tracker modernization with software-only access
For: Organizations that own trackers and want to evaluate a different software workspace.
You may already have tracking hardware. Before replacing it, assess whether the location data it produces can support the maps, history and operational workflows your team needs in Yatrik.
What Yatrik can do
- Assess device protocols, sample payloads, connectivity and access requirements.
- Check timestamps, location fields and available quality information.
- Onboard compatible sources directly or through an agreed bridge or adapter.
- Enable the workflows that the data and confirmed integration scope allow.
Example workflow
- Share device details and representative data
- Confirm compatibility and integration effort
- Validate the agreed software workflow
Deployment requirements and scope
Compatibility is assessed before onboarding. Support for every tracker protocol, universal plug-and-play access and zero integration effort are not assumed.
Devices and integrations
Location-data integration with business systems
For: Businesses with existing portals, operational applications or reporting workflows.
Location information is more useful when it can support an existing process. An integration-led deployment defines how authorized location records or events should reach the system that needs them.
What Yatrik can do
- Assess the relevant REST API, MQTT ingestion or spatial webhook path.
- Define authorization and map the location fields required by the receiving process.
- Agree how location events are delivered and handled.
- Validate data mapping, event behavior and operational responsibilities before rollout.
Example workflow
- Define the business event and destination
- Agree data mapping and authorization
- Validate the agreed integration
Deployment requirements and scope
Prebuilt ERP or CRM connectors and automated two-way synchronization are not assumed. Available paths, development work and service responsibilities are agreed separately.
A focused workspace
for each responsibility.
Yatrik’s web applications give different users the views and actions appropriate to their work and permissions.
- Business Dashboard
- Customer maps, assets, devices, trips, dispatch and monitoring workflows.
- Driver App
- Assigned jobs, progress updates, completion and relevant account information.
- Workforce App
- Assigned field tasks and work updates for field personnel.
- Personal Dashboard
- Personal tracking, items, places, timeline and sharing.
- Public tracking view
- Limited recipient visibility through tracking or sharing links.
- UGAC staff workspaces
- Operations Center and Mission Control support authorized UGAC staff. They are distinct from customer access; additional service scope is agreed separately.
Turn your use case
into an agreed deployment.
Start with what you need to track and the decision your team needs to make. We will assess the hardware, data and software together.
Define the operation
Identify the assets, people, operating areas and work that location information should support.
Assess the sources
Choose UGAC hardware + software, or assess existing devices and data for software-only access.
Configure and validate
Agree permissions, workflows and relevant rules. Test representative conditions before rollout.
Show us the workflow you want to connect.
Tell us what you track, which devices you have and what should happen after a location update.