Oil and gas, and the industrial services around it.
For the contractors, engineering firms, maintenance companies, suppliers and field operations that keep production running: organizations whose work is audited before it is awarded, recorded on paper, and done where there is no signal.
The sector runs on documents and on trust. An operator qualifies a supplier before it hires one, and the qualification starts with whatever the supplier has published. A permit, a certification, a daily report and an HSE record each have to exist, be current and be findable when an auditor asks. Most of that is still carried on paper and in spreadsheets, re-keyed at a desk at the end of the day, by people who were in the field when it happened.
That is the ground Recalibre works on. Brand and identity for the firm that has to be trusted with a scope of work; the field systems that carry the day without a network; the integration that makes the office and the site read one version of it; and the automation that takes the repetition out of the documents while leaving every decision that carries weight — safety, money, a contractual commitment — with a person.
Where the work sits.
The sector’s structure, not any company in it. Point at a segment, or move to it with the keyboard, to see which of the firm’s services apply there.
Upstream
Exploration, drilling and production: the fields, the wells and the facilities on them.
- Work is done on remote sites, in shifts, often without a network connection
- Permits to work are issued per zone and lapse on a date
- Every intervention has a crew, a time, a state and a report that someone has to sign
WHAT WE BUILD HERE
- /02Custom software development.Field systems that carry the day on the device and queue until coverage returns
- /03Enterprise systems and integration.One register the field writes to and the office reads from
- /01Agentic AI and automation.Alerts raised from the data: a permit about to lapse, a report not filed
Midstream
Pipelines, storage and transport: moving what is produced to where it is processed.
- Long assets with many contractors working on them at once
- Inspection, maintenance and shutdown work planned months ahead and executed in days
- Records that have to reconcile across the operator, the contractor and the regulator
WHAT WE BUILD HERE
- /03Enterprise systems and integration.Integration across the systems the operator, the contractor and the regulator each keep
- /02Custom software development.Shutdown and maintenance registers with the trail an audit asks for
- /01Agentic AI and automation.Document intelligence for the inspection reports and the contracts behind them
Downstream
Refining, processing and distribution: plants, terminals and the supply chains out of them.
- Plant operations with many systems that each hold a piece of the truth
- Procurement that runs on tenders, qualifications and supplier documentation
- Reporting to the board, the regulator and the client in formats that do not match
WHAT WE BUILD HERE
- /03Enterprise systems and integration.A source of operational data the plant’s systems agree on
- /01Agentic AI and automation.Tender and supplier documents read, checked and routed, with a person deciding
- /02Custom software development.Reporting systems that produce the document each reader actually asks for
Industrial services
The contractors, EPC firms, maintenance companies, suppliers and logistics operators that work for all three.
- Qualified by procurement before any work is awarded, on what they have published
- Crews on client sites, under the client’s permits and the client’s HSE rules
- Certifications, equipment records and daily reports that must be current and findable
WHAT WE BUILD HERE
- /05Brand strategy and identity.An identity written for the procurement reader deciding whether to trust the firm
- /04Product and experience design.A public website built for tender qualification, and the field interfaces crews actually use
- /02Custom software development.The crew, equipment and certification registers that a contractor runs on
Six kinds of organization.
Contractors
Firms working pipeline, steel erection, civil works and shutdowns on operators’ sites.
Qualified on paper before being hired, then measured on how the work is recorded as much as how it is done.
An identity and a website written for the procurement reader; a field register for the crews, the permits and the daily report.
EPC firms
Engineering, procurement and construction companies carrying a project from design to handover.
Documents from many parties that have to agree, and a handover package the client can actually use.
Document intelligence across the contract set; integration between the project’s systems; the reporting the client requires.
Maintenance companies
Planned and corrective maintenance, inspection and shutdown work on producing assets.
Work orders, permits and inspection records that have to exist before the work and reconcile after it.
A maintenance register with its permits and its trail; alerts raised from the data when something lapses.
Supply and logistics
Suppliers, transport and base operators feeding the sites.
Orders, deliveries and certifications moving between the supplier’s systems and the client’s.
Integration between the two sides; a portal where a client submits, tracks and retrieves in one place.
HSE
The health, safety and environment functions on both the operator’s and the contractor’s side.
Records that have to be current, signed and findable when an auditor asks, produced by people in the field.
The signed daily report with its countersignature; certifications tracked to their lapse date; the trail behind every automated step.
Field operations
The crews, supervisors and site leads doing the work where there is no signal.
A day recorded once, in the field, in the languages the crew actually reads, that the office can trust.
An offline-first field system in French and Arabic — OPS, the product in development, is designed for exactly this.
Questions about the sector.
Both kinds of organization have the same problem from different sides: a day’s work that has to be recorded, permitted, reported and audited. The work published on this site is for an industrial contractor and for the field crews a product is designed around; the systems apply on either side of the contract.
Yes, when it is designed for that from the start. OPS, the field operations product in development, carries the day on the device and queues it until coverage returns. The offline case is an architecture decision taken during Calibration, not a feature added later.
Inside the organization that owns it, by design: one server, one database per organization, on infrastructure you control. Data residency and access are agreed during Calibration and written into the scope.
The five services apply wherever an operation runs on documents, field work and systems that do not talk to each other. Oil and gas and its industrial services is the sector the published work comes from, and the one this page describes; the engagement itself starts the same way everywhere, with a Calibration.
Still have a question?
REQUEST A QUOTATIONTell us what is not working yet.
A quotation request takes a service, a scope and a timeline. A Calibration takes a conversation. Either way a person reads it.