Reservoir Modeling Governance Software for Subsurface Teams
Kissflow governs which reservoir model version is the approved one, who reviewed it, and who received it, so a reserves booking or a development decision is never made against a version that never got signed off.
Trusted by energy operators worldwide
Kissflow doesn't build the reservoir model. It makes sure the model everyone is using is the one that got approved.
A static or dynamic reservoir model gets built and updated in specialist geoscience software, revised as new well data comes in, and used to support a reserves booking, a development plan, or a well location decision. The modeling and the interpretation stay in that specialist software, where they belong. What often doesn't have a clear home is the governance around the model itself: which version is the current approved one, who reviewed it and signed off before it was used for a decision, and which teams or vendors actually received a copy.
Kissflow runs that governance layer: a model version registry that tracks every update with its owner and status, a review and approval sign-off step before a version is marked usable for a business decision, and an access and distribution log showing exactly who received which version and when.
When a reserves auditor or a partner asks which reservoir model supported a decision, the answer is a record, not a search through a shared drive for the file someone thinks is current.
Where reservoir model governance breaks down between updates
Nobody's sure which version is current
The model file gets updated on a shared drive, and the filename convention is the only thing distinguishing versions.
A decision gets made on an unapproved version
A development plan references a model update that was never formally reviewed and signed off.
Distribution isn't tracked
Nobody has a record of which teams or partners received which version of the model or its outputs.
Review accountability disappears
When a number from an old model turns up in a report, nobody can say who reviewed the version it came from.
Three modules. Every model version registered, approved, and tracked to who received it.
Configure model types, review roles, and distribution lists to your subsurface program.
Model version registry
Every update to a reservoir model is registered with its owner, date, and status, independent of the modeling software itself.
Review and approval sign-off
A version is marked usable for a business decision only after the required technical reviewer signs off.
Access and distribution log
Every time a model or its outputs is shared with a team or a vendor, the record captures who received which version and when.
From request to system of record in four steps
Submit
A new model update is logged with its owner and status.
Review
The version goes to the required technical reviewer for sign-off.
Approve
Once signed off, the version is marked usable for a business decision.
Record
Every share of the approved model or its outputs is logged against who received it.
What changes when reservoir model governance runs on Kissflow
| Process | Before Kissflow | On Kissflow |
|---|---|---|
| Version tracking | A filename convention on a shared drive | A registered version with owner, date, and status |
| Approval before use | Assumed, rarely confirmed in writing | A required sign-off step before a version is usable for a decision |
| Distribution record | Untracked, reconstructed from memory if asked | Logged every time a version or output is shared |
| Audit response | A search through the shared drive for the right file | A record showing which version supported which decision |
| Reviewer accountability | Informal, often undocumented | A named reviewer and a timestamped sign-off on record |
| Access control | Whoever has the shared drive link | Role-based access tied to the governance record |
Connects to your geoscience and reservoir simulation software; Kissflow doesn't run the simulation or interpretation itself
Kissflow governs the version, approval, and distribution record. Your geoscience software stays the system of record for the model and the simulation.
.svg){kind=logo}
.svg)
.svg)
.svg)
.svg)
.svg)
.svg)
.svg)
.svg)
.svg)
.svg)
.svg)
.svg)
.svg)
.svg)
.svg)
.svg)
.svg)
.svg)
.svg)
.svg)
.svg)
Built for governing a model, not building one
A version registry independent of the modeling software
Every update is tracked with its owner and status, regardless of which geoscience tool built it.
Approval before a decision, not after
A model version is marked usable only once a technical reviewer has signed off.
Distribution tracked, not assumed
Every share of the model or its outputs is logged against who received it.
Live in weeks
Configure model types and review roles in the visual builder, or describe the use case to the AI Builder.
Governed from day one
Role-based access and a full audit trail on every version and approval.
A clear boundary with your engineering software
Kissflow never touches the simulation itself, only the governance record around it.
Related apps
Drilling & Well Planning Management System
Feed an approved reservoir model into the well design and risk review.
Lessons Learned From Wells Management System
Capture what a well's actual results taught relative to the model that predicted them.
Casing/cementing Approval Management System
Approve the well construction execution once the reservoir target is confirmed.
We help subsurface teams know which model version a decision was actually built on
.gif)
“If a company cannot enable everybody to use AI, they will never get the true benefit of AI. Platforms like Kissflow allow us to put that capability in the hands of our users in a safe way.”
Vagesh Dave
GVP & CIO at McDermott International, Ltd
See The Full Story
“Advanced automation of all processes is easy to set up. I cannot imagine how to manage workflows without this software.”
Tanay Tiwary
Global Head - Digitalization & Business Improvement
See the Full Story
“Kissflow supports rapid application development by building a working application prototype in the shortest amount of time.”
Maria Theresa Cabigon
CIO, SN Aboitiz Power Group
See The Full Story
See what Kissflow can do for you
Talk to usGot questions? We're here to help.
Get SupportNo. The simulation and interpretation happen in your geoscience software. Kissflow governs the version registry, the review and approval sign-off, and who can access or receive each model version.
Drilling & Well Planning Management System coordinates the well design and cross-discipline sign-off before spud. This app governs the reservoir model version and approval that the well design references, upstream of that process.
Any registered update to a static or dynamic reservoir model, tracked with its owner, date, and status, independent of the geoscience software used to build it.
Whoever you configure, typically a senior reservoir engineer or subsurface team lead, with the sign-off recorded against that specific version.
Yes. The access and distribution log records every time a version or its outputs are shared with a team or a vendor.
It can reference or attach model outputs and reports, but the model and simulation remain in your geoscience software as the engineering system of record.
Configuration and AI-assisted app generation move delivery from a multi-month program to a matter of weeks.
Kissflow is certified to SOC 1, SOC 2, SOC 3, and ISO/IEC 27001, with role-based access and a full audit log on every version and approval.
