OSM PRO
Dispatch & billing for oil and natural gas hauling

OSM Pro is becoming a web platform.

The same dispatch, audit and billing logic your operation already runs on — rebuilt for the browser, delivered in stages, with nothing switched off until its replacement has been proven against your own data.

How we are going about it

Nothing is switched off early

The desktop applications keep running until the web platform has done the same job, on the same loads, and the numbers have been reconciled side by side.

You move when you are ready

Companies move across one at a time, with their partners, on a date that suits their billing cycle. There is no weekend where everybody changes systems at once.

Your history comes with you

Every load, tender, audit, invoice and scanned ticket is migrated with its original record kept alongside it, so any past invoice can still be traced back to the run that produced it.

The sequence

Each stage has to work before the next one is useful.

This is a delivery order rather than a calendar. Stages build on one another — the platform has to exist before accounts can be set up, and accounts have to exist before anyone can be invited onto it.

In build Stage one

Telling you what is happening

This site, and this page. The old one had not been updated in over a decade, which is its own kind of answer to the question of what was going on. Replacing it came first because everything below is easier to judge when you can see it written down.

  • A current account of the product
  • This roadmap, kept honest
  • A way to actually reach us
In build Stage two

The platform, and getting you onto it

The foundations everything else stands on, and the administration behind them — setting a company up, inviting the partners it works with, and giving its people the access they should have. Nothing can be onboarded before this exists, which is why it is first.

  • Cloud-hosted, nothing to maintain
  • Company and user administration
  • Invitations a partner has to accept
  • Read-only access you can grant
  • Single sign-on where you use it
In design Stage three

Carrier dispatch, in the browser

The screens dispatchers live in, being designed now. Built to run alongside the existing desktop application through changeover, so a load dispatched in one appears in the other rather than being entered twice.

  • Dispatch board and status boards
  • Order entry, dispatch and search
  • Time, quantity and identity audits
  • Tendered values shown against actuals
  • Closing, validation and billing hand-off
  • No install — any browser
Next Stage four

The energy company side

So that a tender raised by one company and the load worked by the other are the same record rather than two that have to be reconciled.

  • Tendering and order entry
  • Audit review and approval
  • Reference data owned by the company it belongs to
  • Payables against what was actually hauled
  • Invoicing configured rather than coded
Then Stage five

Everything around the screens

The parts that are not a screen but decide whether a company can actually run on the new platform — which is why they come before anyone is asked to move.

  • QuickBooks Desktop and Online
  • An API for your own systems to tender
  • Invoices, BOLs, tenders and tickets
  • Reporting you can build yourself
  • Documents stored and retrievable
Then Stage six

Moving across

One company and its partners at a time. Both systems stay in step throughout, and the reconciliation is read by a person before anything is called done.

  • Full history migrated first
  • Counts and totals reconciled
  • A period of running side by side
  • The ability to go back
Planned Beyond

Capture at the wellsite, and books that know the job

Once the platform stands on its own, the two additions that change the work rather than reproduce it.

  • Driver capture on a phone — ticket, quantity, gauge readings, signature
  • An optional financial module, costed by lease, well and AFE
What changes for you
If you are a carrier

Less re-keying, and a clearer paper trail

  • Dispatch from any machine, with no desktop install to maintain.
  • Audits show the tendered value beside the actual, with the difference highlighted.
  • Billing rules become settings rather than a software release, so a new customer can be onboarded in days.
  • You can invite an energy company to watch your loads read-only, and end that access whenever you choose.
If you are an energy company

Your coding, carried through properly

  • Your accounts, report centres and routing travel with the invoice as structured data, not as text your AP team has to read off a line.
  • You maintain your own reference data instead of a carrier keying it on your behalf.
  • Invite the carriers you work with, and see exactly who has access to what.
  • Tender from your own systems through a documented interface.

Want to know where your company sits in this?

We are choosing the first companies to move now, and picking them alongside the partners they work with most. If you would like to be early — or would rather be late — that is worth a conversation.