The problem
A model is out of date the day the next assay batch arrives. With licensed software, keeping it current means keeping the licence and the person who knows how to run it, whether there is news or not. Without them, the model in the investor deck quietly stops matching the data.
What you send
The new data, as it comes from the laboratory, the rig or the field: assay certificates, new collars and surveys, a new geophysical line. It is checked and merged using the same rules as the original data integration.
What we do
- Validate the new data and add it to the database, with the same checks as before
- Rebuild what depends on it: surfaces, grade shells, rankings and ranges
- Reissue every deliverable that changed, so they stay consistent with each other
- State what changed and why: which targets moved, which ranges narrowed or widened
What you get
A new dated version of the database, the model and the documents, and a short change note.
Example: new assays arrive from the laboratory, and the database, tonnage and grade ranges, 3D model and investor PDF are reissued together.
What it cannot say
An update reflects the data received. If assays are preliminary or quality-control results are pending, the update says so and is marked provisional. Previous versions are kept, so that it is always possible to see what was known at a given date.
Questions
Is there a subscription or retainer?
No. Each update is scoped and priced as its own piece of work. If nothing new arrives for a year, you pay nothing for that year.
Can you update a model that someone else built?
If the underlying data can be exported, yes. It is first brought into one validated database, and the model is rebuilt from there so that later updates are repeatable.
What exactly is reissued?
Everything that depends on the new data: the database, the 3D model, target rankings, tonnage and grade ranges, and the figures and documents built from them.