How do you arrive at a quote?
The shape of the engagement determines the quote: number of assets in scope, depth of probabilistic simulation, whether ongoing fitting against actuals is required, and which deployment mode is needed. We aim to give an indicative quote within five working days of the initial conversation.
What does a typical engagement look like?
Engagements begin with fitting ChainVision's chain-model parameters against the operation's data, followed by a baseline simulation and a working session with the planning team. From there, the engagement evolves: scenario libraries, periodic re-runs as actuals arrive, integration with planning workflows.
What if the operation has an unusual processing route?
The node library covers common mining and mineral-processing patterns. For operations with novel processing steps, custom node types are part of scoping at the Enterprise tier. The architecture is built so adding a node type is a contained, well-defined task.
How do you protect operator data?
Data protection is treated as a design requirement, not a bolt-on: encryption in transit and at rest, database-engine tenant isolation verified in CI, Australian data residency by default, and no use of customer data to train models without written consent. For operations where data must stay entirely on the operator's own infrastructure, private cloud deployment is available at the Enterprise tier.