Six things, every time, or it is not an answer.
A figure on its own can only be believed or disbelieved. These six make it checkable, which is what it has to be before you take it into a reconciliation meeting with a JV partner.
Unaccounted volume, attributed line by line.
The gap between what a flow station sends and what a terminal receives has several ordinary causes, and they are separable. Each line below names the system it came from, so you can check the figure before a reconciliation meeting and defend it inside one.
The size of the problem is already published.
Every figure below comes from a Nigerian regulator, a statutory audit or a multilateral tracker. They describe the industry, not Muono's results. They are the losses a sourced record is meant to reduce.
- NEITI · Oil & Gas Industry Audit, 2023
- 362.28m bbl of crude oil losses recorded across the industry between 2014 and 2023.
- NEITI · Oil & Gas Industry Audit, 2023
- 110.66m bbl of those losses were production deferment: repairs, line breaks and equipment performance.
- NUPRC · Annual Report, 2024
- 183,011 bopd average production deferment for 2023, reported by the upstream regulator.
- NUPRC · Gas Production Status Report, 2025
- 203.9 bscf of gas flared in 2025, 7.54% of production, against utilisation above 92%.
- NOSDRA · Gas Flare Report, 2025
- $646.1m in flare penalties operators were liable for in 2025, on 323 bscf flared.
- NUPRC · Domestic Crude Supply Obligation, Q1 2026
- 28.5m bbl actually delivered against 61.9m bbl allocated to domestic refineries.
Whatever the question, the answer is already somewhere in your operation.
Muono connects the evidence behind it.
The day's figure starts at the flow station.
Rate, choke position, the last well test and the open work order sit in different places. The well-by-well split gets rebuilt by hand, usually after the decision that needed it.
A flow station measures the commingled stream, and the well-by-well figure comes from the test separator plus whatever the last test said. When a well is tested monthly, an allocation carries a month-old assumption. Muono holds the test, the readings and the work that touched each well against the same asset, so the allocated figure shows how old its evidence is.
That matters most where the flow station is unmanned for part of the week. A shut-in that nobody logged looks identical to a measurement error at month end. Held on one record, the shut-in carries its own timestamp and the work order that caused it, and the two stop competing as explanations.
Where volume changes hands, it needs evidence.
A custody figure is only as good as the meter's last proving and the correction applied to it. Both live outside the system that reports the number.
Every transfer point is a small negotiation: your meter, their meter, and a correction factor each side applies. The disagreement is rarely about arithmetic. It is about whose figure carries its proving certificate, its sampling and its downtime record. Muono attaches all three to the meter itself, so the number arrives with the evidence that makes it arguable.
The same applies along the run. A pump station trip, a pressure excursion or a batch of off-spec crude all move the delivered volume, and each has a record somewhere. Held against the line rather than in a monthly summary, they explain the shortfall while the operators who saw it are still on shift.
- Meter factor, last proving
- 0.9987
- Proving age
- 41 days
- Sampled BS&W
- 0.4%
One figure for the terminal, before it is argued.
Tank gauging, the export meter and each partner's own report have to agree. Today they are reconciled in spreadsheets, under a reporting deadline.
A terminal closes the month on opening stock, receipts, exports and closing stock, each measured a different way. Muono holds the readings behind every one of those, with their timestamps and the corrections applied, so the reconciliation is a review of sourced lines rather than an argument between two spreadsheets.
Your obligations sit on top of that: NUPRC production reporting, JV statements to your partners, OPEC quota returns where they apply. Muono assembles the figures and the evidence behind them, with every line traceable. Your team still reviews and submits the return. We do not file on your behalf, and we do not claim a certified integration with any regulator.
One train, and every barrel accounted for.
A complex built as a single train has no second line to fall back on. Feedstock, unit condition and product accountability stop being separate questions.
Feedstock is the first accounting problem. Domestic allocation, what producers actually offer and what arrives are three different numbers. The regulator's own quarterly figures show deliveries at 28.5 million barrels against 61.9 million allocated. The balance is imported, so the tank a unit is drawing from holds several grades bought on different terms, each with its own assay and its own certificate.
That matters because yield moves with the crude. When a batch comes off spec or a run rate is cut, the reason sits in the assay, the unit's condition and the work open on it. Three systems, in the hour when the decision is worth making. Muono holds them on the same asset, so a product figure can be traced to the barrels and the machine that made it.
The plant you inherited, and the drawings you were given.
A handover pack is a snapshot of someone else's record-keeping. What is on the plant and what is on the drawing diverged years before the transaction.
The first job after taking over an asset is establishing what you actually have: which tags are real, which drawings are as-built, which inspections were done and which were deferred. Muono builds that register from the handover pack, then marks each item with how it was established, whether from a drawing, from a live reading or from a walkdown. Flattening all three into one confident list is how a register starts lying to you.
The gaps are the useful part. A nozzle on the drawing that nobody can find, and a tie-in on the plant that appears on no sheet, are both findings worth recording. They become work rather than surprises, and the register improves every time somebody confirms something in the field.
- Tags in the handover pack
- 1,240
- Confirmed on the plant
- 986
- Unresolved after walkdown
- 254
A dropped link should not stop the record.
Swamp and offshore locations run on VSAT and radio. Anything that needs a live connection to be useful is useless on the days it matters.
A collector sits on site, reads the historian or RTU locally and buffers what it has gathered. When the link returns, it forwards the backlog with the original timestamps, so a gap in connectivity does not become a gap in the record. Operators keep working against the local copy in the meantime.
Where data has to stay in the country, it can. Muono runs in your own cloud tenancy, on your own hardware, or in-country as a hosted deployment, with the region fixed at deployment. The collector on site behaves the same in all three.
- Link availability, 30 days
- 91%
- Readings held at the edge
- 4,318
- Longest gap
- 6 h 20 m
A deferral you can defend, on a line that has run for decades.
Thickness readings, corrosion rates and the integrity case sit apart from the schedule that decides what gets inspected next.
Every deferral is a judgement: this line can wait, that one cannot. Making it well needs the last thickness readings at each monitoring location, the corrosion rate they imply, and the case that set the interval in the first place. Muono keeps them on the spool itself, so the remaining life is a figure with readings behind it rather than a date in a spreadsheet.
When a reading moves the picture, the assets it affects are already linked to it. A location trending faster than its neighbours surfaces against the schedule while there is still time to plan a shutdown around it, and the reasoning is on the record if the deferral is ever questioned.
Flared gas is a measured figure, not an estimate.
Reducing flare and holding a domestic supply commitment both depend on knowing, hourly, where the gas went and why.
Flare volume is metered, but the reason is operational: a compressor down, a downstream plant not taking gas, a trip on the knock-out drum. Muono holds the flare meter reading against the equipment that caused the flaring, so a monthly flare figure decomposes into events with named causes instead of one number to explain.
The same record supports the supply side. When a domestic offtake commitment is at risk, the constraint is usually a specific machine with a specific work order against it. Seeing the two together turns a contractual problem into a maintenance decision, early enough to act on.
The reason it is run that way should outlast the person who knows it.
Every plant runs on local practice that is nowhere in the documentation. It leaves with the operator who developed it.
A pump that is always started on the bypass, a seal flush that is left running longer than the manual says, a valve that is throttled rather than opened: each is a real decision made for a real reason, usually after a failure. None of it is in the operating manual. Muono records it against the equipment it applies to, so the practice and the asset stay together.
The value shows up on handover and after turnaround. A new engineer asking why a machine is run this way gets the answer with the failure that produced it, the readings from the time, and the person who recorded it. Experience becomes part of the record rather than something a site rebuilds every few years.
One flow station, five stages, a figure at the end.
A paid pilot on a single facility, then an annual licence per site. The baseline is taken before anything changes, so the review has a number to work from. Deployment can sit in-country from the start.
- ScopePick the facility and the figure it has to defend.
- ConnectHistorian or RTU, the maintenance system, and the drawings you hold.
- BaselineMeasure how the facility reports today, before anything changes.
- First answersYour team asks real questions and checks the sources behind them.
- ReviewCompare against the baseline and decide whether it widens.
Put your own numbers in.
The published figures above describe the industry. This one describes your facility, and every input is yours to set.
This is the size of your problem, not a claim about our effect on it. Muono does not recover a barrel and it does not touch the unaccounted volume on its own. It attributes the gap to causes you can act on while the operators who saw it are still on shift, and the recoverable share is yours to set.
Your questions, answered
- Can our data stay in Nigeria?
- Yes. Muono runs in your own cloud tenancy, on your own hardware, or as an in-country hosted deployment. The region is fixed when the deployment is set up and does not move afterwards.
- Our links drop. Does it need constant connectivity?
- No. A collector on site reads locally and buffers while the link is down, then forwards the backlog with its original timestamps. Site teams keep working against the local copy, and the record has no hole in it afterwards.
- We inherited the asset with incomplete records. Where do we start?
- With one facility. The handover pack and the drawings you hold are read in and turned into an asset register, with each item marked by how it was established. Older scanned sheets need one pass to confirm tag numbers before you can trust them as a source, and the register improves as the field confirms it.
- Does it produce our regulatory and JV returns?
- It assembles the figures and the evidence behind them, with every line traceable to the system it came from. That is the part that takes the time. Your team reviews and submits. We do not claim a certified integration with any regulator, and Muono does not file on your behalf.
- Which of our systems can you connect to today?
- Historians and SCADA over OPC UA or the vendor's own interface, and maintenance systems including SAP and Maximo. Both read-only to begin with. Anything else we scope honestly rather than assume.