FOUR QUESTIONS FOR OIL, GAS, ENERGY AND MINING. ANSWERED FROM YOUR OWN RECORDS.
An operator or supplier in oil, gas, energy or mining lives with the same four uncertainties: whether the volumes agree from the source to the sale, whether the right to operate is on the record, whether the inputs will arrive and can be traced, and how the sites are really running. Resources answers each from the records an organization already keeps, with the evidence beside the answer. It is optional. An enterprise outside these industries leaves it off and nothing else changes.
1. Do the volumes agree from the source to the sale?
A stream is measured at more than one point: at the wellhead, the plant inlet, the terminal, at the pit, the mill, the port. The measurements rarely match exactly. The question is whether the difference is inside what the measurement can explain, and whether it keeps the same sign period after period.
| Resources shows | How |
|---|---|
| Point to point | For each stream, the quantity at each measurement point and the difference between consecutive points, after the expected factor you record (for example shrinkage or recovery). Both values are kept. Derived. |
| Outside tolerance | The periods in which the difference exceeds the tolerance for the commodity. Defaults are named assumptions you can change: 0.5 percent for hydrocarbons, 5 percent for mining, 2 percent for power. |
| Same sign, again | A run of consecutive periods in which the difference has the same sign is shown as a possible meter or model effect. It is an inference, labeled as one, and it is a reason for a person to look, not a finding of fault. |
2. Is the right to operate on the record?
Resources lists each site with the permit your organization recorded, the area it covers and when it expires.
| State | Meaning |
|---|---|
| Valid | A permit is recorded and its expiry is beyond the warning window. |
| Due | A permit is recorded and falls due inside the warning window, which is a named assumption. |
| No valid permit on the record | The permit is missing or expired on the record. This reads the record. It does not say the site is operating illegally, because the record may simply be out of date. |
EOS records what an authority granted. It never grants a permit and never presumes one.
3. Will the inputs arrive, and can they be traced?
| Resources shows | How |
|---|---|
| On time | The share of delivered shipments that arrived on or before the promised date. |
| Open and overdue | Shipments not delivered and past their promised date, by item, supplier and tier. |
| Concentration | Items for which one supplier provides more than a share you set (50 percent by default) of the recorded quantity. |
| Certificate gaps | Lots for which a required origin or chain-of-custody certificate is not on the record. EOS shows the gap. It does not certify origin. |
4. How are the sites running?
For each site over the last twelve months: availability from the recorded outages, unplanned outage hours, the recordable incident rate from the hours worked, and near misses. The incident rate is compared with an internal review line you set. That line is a trigger for a person to look. It is not a safety standard, and Resources does not state that a site is safe or unsafe.
What it proposes, and who decides
Seven kinds of proposal, each from the records: find the cause of the volume differences, renew or restore permits, chase overdue shipments, qualify a second source, obtain missing certificates, review low-availability sites, and have a person review sites above the internal incident line. Each carries its insight with its evidence, the expected outcome, the impacts, and alternatives that each carry the same, including doing nothing.
Outcomes are measured on the proposal's own metric (percent, days, count), not in dollars, and are never added into one figure. A named owner, admin or controller decides, with a reason. An agent never does. The outcome is reported later by a person, with its evidence, and compared with the target.
What it needs, and what it does not have
Six kinds of record: sites with their permits, measurements at each point of a stream, hours worked, incidents, shipments and outages. They arrive by spreadsheet template in the platform, by a warehouse query, or by a signed push from your systems. Resources reads two kinds of source directly. A production-accounting system with a REST list endpoint feeds measurements through a field map you supply, and AVEVA PI Web API feeds them from the month-end totalizer for the tags you name. Both are conformed against a scripted vendor and have not run on a customer's tenant; a probe reads one page from your own system first. SCADA and DCS are not reached from the service, by design: a control network does not accept inbound connections from a cloud service, so the route is a gateway program on the customer's side that reads the totalizer tags over OPC UA, Modbus TCP or DNP3 and pushes one signed monthly quantity per tag, under a key that can write Resources only. It can also carry out a set point that two named people have approved, if you switch that on in the gateway; it is off by default, bounded by limits you set there, read back, and not a safety system. It withholds a month it cannot close exactly. It is tested against the service, but its OPC UA, Modbus and DNP3 readers and its set point writers have been run only against scripted devices, not a live controller. Where a system has no route, a person or a scheduled export carries the data in. A record that fails its checks is named with the reason and the rest are recorded.
See it. Open the platform and choose Resources to read a recorded run on the synthetic operator, or sign in to run it on your own records.
Open Resources in the platform · Optional modules · Assure · Optimize · Fleet