Blue CollarResearch
MonDak Wellsite Navigator

MonDak

Wellsite Navigator

Oilfield navigation.Built for the destination.

MonDak Wellsite Navigator is built specifically for the North Dakota and Montana oilfield.

Search for a well by name, API number, or operator, then get the information and navigation you need to reach the actual location.

Traditional navigation is built to get you to an address. MonDak is built to get you to the well.

From well search and turn-by-turn navigation to road information, weather, field reports, and wellsite access guidance, MonDak puts the tools oilfield drivers need in one place.

Find the well. Know the road. Get there.

Coming soonExplore features
Diagram of oilfield navigation: a public mapped road continues past a junction, while a separate access path follows a supported corridor of section-line and lease-style roads to a wellhead. It does not cut straight across open ground.

MonDak / Field nav

Public road to access corridor

ND · MT

Bakken ops

01Mapped road

02Access

DestWellhead

The problem

Built for where ordinary navigation stops.

Conventional navigation is built around conventional mapped road networks—addresses, highways, and the next legal turn.

Oilfield work often needs more than that. A public-road route can be correct and still leave a driver short of the well. MonDak is being designed for the part of the job that starts when the highway is no longer the destination.

  • 01Well identification
  • 02Oilfield destination context
  • 03Access awareness
  • 04Field conditions
  • 05Road restrictions
  • 06Changing local information

Capabilities

Tools for the run. Not a highway skin.

MonDak is being built around well discovery, route awareness, and destination guidance. Available information varies. Nothing here is a guarantee that every road, restriction, or access path is known.

01

Well search

Find oilfield destinations using information such as well name, API, or operator. Results can be organized with proximity and location so the right destination is easier to identify before you roll.

02

Oilfield navigation

In-app route guidance designed around oilfield destinations. MonDak can use available mapped roads and supported access information to help guide you toward the well—not just the nearest town or highway exit.

03 · Differentiator

Destination guidance

The well coordinate remains the point. When conventional routable road data ends, dropping a pin on the nearest mapped road is the wrong destination.

MonDak is being designed to provide additional destination and access guidance based on supported data—following available corridors rather than treating the last public road as the end of the job.

Guidance depends on the data that is actually available. It is not a claim that every lease road is known, or that a path across open ground is implied.

Comparison diagram: ordinary routing ends at the last mapped public road, while MonDak continues along a supported access corridor toward the well coordinate.

MappedPublic road

ThenAccess corridor

DestWellhead

04

Field reports

Report changing conditions such as road issues, access problems, hazards, closures or restrictions, and other relevant field conditions. Reports may include text, voice, location, and photos where supported. These are field observations—not independently verified professional assessments.

05

Road & route awareness

MonDak can surface warnings and available information about road restrictions and route conditions. Treat it as decision-support. Posted signs, permits, and what you see on the ground still govern the run.

06

Weather awareness

Weather information can help you understand conditions near the route or destination before and during a run—another input for judgment, not a substitute for looking outside.

07

Offline support

Field work does not always have a signal. MonDak is being designed with offline-oriented support: cached information, offline search where supported, stored map and data regions, and queued field reports. This is not a promise of complete navigation without connectivity.

08

Driver-focused design

Built for people who spend long days driving in the field: readable navigation, large controls, straightforward information, a field-oriented interface, and as few extra steps as possible.

Vehicle profile

The truck is part of the route.

Users can create a vehicle profile with information such as weight range and axle count. When restriction information is available, MonDak can help warn about—and strongly prefer to avoid—roads that appear incompatible with that profile.

Profile

Weight range

Configure a vehicle weight range so restriction information can be compared against the rig you are actually running.

Profile

Axle count

Axle information can help MonDak account for posted limits and other axle-related restrictions when that data is available.

This is advisory information. It does not replace posted signage, permits, company rules, or driver responsibility.

Field intelligence

The field changes. Your map should know.

Local conditions can move faster than traditional map datasets. A road that was fine last week may not be fine this morning. Field reports are intended to surface recent information from people actually operating in the area.

  • RD

    Road condition

    Surface, washouts, ruts, and other travel issues reported from the field.

  • AC

    Access issue

    Gates, blocked approaches, and other problems reaching a location.

  • RS

    Restriction

    Limits and constraints that may affect whether a road is usable for the run.

  • HZ

    Hazard

    Conditions that may affect how—or whether—a driver should proceed.

  • CL

    Closure

    Roads or access that appear closed or no longer available.

  • OT

    Other field issue

    Local conditions that do not fit a tighter category but still matter.

Reports come from people in the field. They are not independently verified unless separately stated. Use them as additional context alongside posted information and what you see on the ground.

Geography

Built for the Bakken.

MonDak's initial focus is North Dakota and Montana oilfield operations. The product is being shaped around that geography and that way of working—not a national map with an oilfield label on it.

ND

North Dakota

N 47° · W 102°

Bakken operations, field roads, and well destinations as the working context—not a generic city map.

MT

Montana

N 47° · W 104°

The same oilfield problem on the west side of the play: destination-first navigation where public maps thin out.

Regional focus. Not a coverage claim.

Responsibility

Assist the decision. Don't replace the driver.

  1. 01MonDak provides navigation and field information intended to assist decision-making.
  2. 02Road conditions, access, and restrictions can change after any dataset is collected.
  3. 03Drivers remain responsible for posted signs, road restrictions, permit requirements, laws, employer rules, and actual field conditions.
  4. 04MonDak does not guarantee that a route is legal, suitable for a vehicle, or safe.

Release

MonDak is coming.

Purpose-built oilfield navigation for the people who actually drive these roads.

MonDak support