Documentation
Reference.
The vocabulary the product is built on: the states a job moves through, what each role sees, which modules exist, and how figures are written. A step by step manual follows the product into service, because a manual written before anyone has used the thing documents an intention.
A job has one life and twelve states.
A job is one record from the first estimate to the settled invoice. It does not become a different object when it moves between teams, and nothing is re-keyed at a handover. What changes is its state.
The first four are the opportunity, carrying the confidence that it will happen at all. The next four are delivery. The last four record how it ended or that it has not started.
- P10, P50, P90 and Awarded
- The opportunity, at rising confidence. The industry's opportunity classes, in the activity reading: P10 is a conversation, P90 is expected work, and Awarded is committed work that has not yet been designed
- Design
- The scope and the tool string are being built. The estimate becomes real here
- Prepare
- The workshop is readying the string: inspection, QA sign-off, load out
- Execute
- The job is offshore. Runs, morning reports and field tickets are logged against it
- Close
- Back at base. Returns received, failures resolved, lines ready to invoice
- Won, Lost
- How the opportunity ended. A lost job keeps its record and its reasoning
- Draft, Archived
- Not started, or finished and out of the way. Neither is a deletion
The role decides the view.
There is no separate login per view and no switching between them. A person has one role, an administrator sets it, and it decides which parts of the product they see. The roles are the same in every company.
- Administrator
- Everything, plus users, roles and company settings
- Project engineer
- Plans and runs jobs end to end, including the commercials
- Sales engineer
- The opportunity and its pricing: jobs, finance and rate sheets
- Workshop engineer
- Prepares and maintains tools: the fleet, operations and the tool catalogue
- Operations coordinator
- Load-out and logistics across jobs, the fleet and operations
- Field engineer
- Operations only, plus the rig app on site
- Viewer
- Read only. Sees everything the company has and changes nothing; the server refuses every write from this role
Modules.
Three are always on because the product does not make sense without them. The rest are switched on for your company by us. A module that is off blocks its data, not only its menu.
- Jobs · always on
- Jobs, opportunities, the well map, assemblies, customer orders
- Operations · always on
- Jobs on the rig, the fleet, logistics, workshop, run records
- Reference data · always on
- Tool catalogue, rate sheets, reference data
- Rig app
- Tablet and phone app for crews on site
- Finance
- Estimates, invoicing, margins, revenue
- In the well
- Tools left in the well on plug and abandonment work
- Crew
- Crew competence and staffing
- Reliability · in development
- Run history and failure rates per tool
- Import · in development
- Part catalogue and service history from spreadsheets and exports
How figures are written.
Consistent everywhere, because a number that changes shape between two screens is a number somebody has to check. Run times are always UTC: a crew, a base and an office in three time zones need one clock, and local time on a run sheet is how two reports disagree.
- Currency
- NOK 4 984,60. Your own currencies, with the job's booking rate
- Date
- 14.08.2026
- Timestamp
- 2026-08-14 04:20Z, always UTC
- Depth
- 1 500,5 m
- A missing value
- Written as a dash, never as zero. Nothing recorded and none measured are different facts
- Your data
- An administrator can download every table the company holds, from Company settings
More
Ask, and the answer becomes the manual.
Rather than put you in front of a search box that finds nothing, ask a person. What you needed to know is what gets written down first.
- Integration
- The API and what it does today