Specification guard
Required fields and product rules prevent E5/E10, diesel/XTL or fuel/operating fluid from being silently treated as the same item.
Product · grade · quantity · unitSCF TECHNOLOGY / PRODUCT & ENGINEERINGTechnology that keeps
Technology that keeps
the order readable.
A tank reading without an observation time is not dependable stock. A price curve without a delivery route is not an offer. SCF connects the measurement, requirement, price basis, approval and delivery evidence—and shows where data is missing or a forecast is uncertain.
Request a technology discussionExplore Oiliver AI- 01STOCK
- 02REQUIREMENT
- 03SCENARIO
- 04APPROVAL
- 05EVIDENCE
SCF Control Layer
Five control modules. One bounded assistant.
Every function carries an operating status. External data sources, meters and AI functions are connected only after technical, domain and security approval.
Delivery review
Postcode, quantity, delivery mode, date, free tank capacity and access are captured as one delivery case—not scattered emails.
Location · access · window · receiptComparable offers
The marketplace compares only offers whose product, delivery basis, tax and freight treatment, validity and payment are visible.
Price · freight · tax · paymentRoles & approvals
Organization, user role and permission determine who can see and perform a request, offer or decision.
Organization · role · limit · approvalEvidence record
Versions, login events, decisions and transaction evidence are attached to the correct organization and record.
Version · event · document · timeControlled assistance
Intended for document extraction, completeness checks, forecast explanations and exception prompts. It cannot award or confirm an order.
Read · calculate · explain · hand over
SCF / TANKLINKINTERFACE DESIGN
From tank reading to an
approval-ready requirement.
TankLink is the integration layer between approved level instrumentation and the SCF supply process. Autonomous radar sensors can transmit readings over NB-IoT, LTE-M or LoRaWAN; existing inventory platforms can expose them through a REST API. SCF attaches the data to the correct tank, product, site and observation time.
- SIGNAL
- Level · device ID · time · status
- TRANSPORT
- NB-IoT · LTE-M · LoRaWAN · gateway
- HAND-OFF
- REST API · MQTT · event webhook
- 01
Measure
The instrument supplies distance or level plus device and quality data. Tank geometry converts the reading into a usable stock value.
- 02
Validate
Timestamp, device identity, plausibility, radio status and outliers are checked. A stale reading must never look like live stock.
- 03
Calculate range
Burn rate, safety stock, free capacity and real delivery lead time produce a range window—not a falsely exact run-out time.
- 04
Prepare the requirement
Before the last safe ordering boundary, TankLink creates a proposal with product, target quantity, delivery point, window and rationale.
- 05
Approve & reconcile
An authorised person or an explicitly agreed contract rule releases the case. After delivery, the order, approved meter value and stock movement are reconciled.
PREDICTIVE PROCUREMENT / CONTROLLED DEVELOPMENTCONTROLLED DEVELOPMENT
Understand demand. Gain lead time. Explain the buying window.
Oiliver AI is designed as a customer-specific decision module. It forecasts demand from real consumption history, tank readings, confirmed deliveries, operating plans and seasonal patterns. In parallel—where the data is licensed—it evaluates multiple market scenarios using the forward structure, price movement, volatility, FX, freight and real offers. Both meet in an explainable procurement corridor.
What belongs in the forecast
- 01
Stock & consumption
Readings, deliveries, drawdown and data quality for each tank.
- 02
Operations
Shifts, fleet activity, production plans, shutdowns and exceptional demand.
- 03
Season & weather
Site-specific patterns; for heating oil, for example, DWD weather data and degree days.
- 04
Delivery route
Lead time, minimum lift, free capacity, delivery window and safety stock.
- 05
Market context
Forward structure, movement, volatility, FX, tax, freight and real offers—licensed and carrying source and observation time.
What Oiliver returns
- RANGE
- A defensible lower/upper band and the last safe ordering boundary.
- QUANTITY
- A target quantity within free capacity, safety stock and delivery constraints.
- WINDOW
- Buy now, stage or wait—compared by expected total delivered cost and supply risk.
- RATIONALE
- The data, assumptions, uncertainty and change since the previous recommendation.
SCF Innovation Line
The next generation is not another dashboard.
It is built where the measurement, delivery route and evidence currently separate. These modules are introduced only with a clear data contract, a named system of record and a controlled operating status.
eFTI-ready delivery record
Order, ETA event, electronic delivery note, meter value and quality evidence are versioned in one record. Hand-off to a certified eFTI platform remains a defined interface; platform certification sits with the selected eFTI provider.
See discrepancies earlier
Tank movement, expected consumption, device health and approved delivery-meter values are reconciled. The module flags unexplained differences for specialists; it is not a substitute for required leak detection or calibration.
A delivery window that can adapt
Range, free capacity, site hours, vehicle status and disruption are translated into a dependable receiving window. If conditions change, dispatch first sees the affected order and the next permitted option.
Multiple tanks as one procurement picture
Sites are prioritised by supply risk; compatible requirements can be grouped by product, region and window. Freight and part-load consequences become visible before a request is released.
One data path—without hardware lock-in.
SCF integrates approved systems through clearly versioned interfaces. Every input retains its source, observation time, organization and quality state. Only then may it influence a requirement, offer or evidence record.
- 01TANK TELEMETRY
Level, free capacity, observation time, device identity and battery state
- 02ROAD-TANKER METER
Approved delivery quantity, temperature basis and associated delivery record
- 03DISPATCH / ETA
Vehicle, status, time window, geofence event and exception
- 04ERP / EDI
Order, confirmation, delivery note, invoice and master-data reference
- 05QUALITY EVIDENCE
Product, batch, document version, issuer and recipient
- 06SOLAR / WIND SCADA
Approved project and operating data through separate, defined interfaces
Not a chatbot over operational data. Not a model without a rationale.
Oiliver combines time-series forecasts, deterministic procurement rules and—optionally—language-based explanation. The language model is not the calculation basis. Every recommendation must expose its data, assumptions, range and change, and may never override an operational boundary by itself.
- 01
Measurement, source and observation time remain visible
- 02
Forecast range instead of false precision
- 03
Deliverable offer before market indicator
- 04
No autonomous order or price approval
- 05
The human decision remains recorded
Security as a system boundary
The sensor may send data. It may not open a side door.
Device and platform credentials are separated from user accounts. Inbound events carry device identity, time and integrity checks; replays and implausible jumps are intercepted. API secrets do not live in application code, tenants remain isolated, and privileged changes require approval and an audit trail. Direct supply and marketplace still share a brand—not access rights.
Review the security architectureA controlled first step
Start with one tank, one supply route and one measurable objective.
SCF reviews the instrumentation, data access, tank geometry, consumption history and approval rules in a bounded integration case. Telemetry becomes an operational decision aid only after the measurement and delivery process hold together.
Discuss TankLink & Oiliver