Sheet A — System overview
Crucible Management — field technology
Bespoke technology
products for remote
placer mining operations
Crucible Management delivers a series of bespoke technology products for placer operations: networks, field data collection and reporting, records systems, secure access, backups and support. Together they give mine owners and operators a consistent way to manage site systems and operational information, whether they are on site or working remotely.
Per product: A defined scope, written deliverables and a documented handoff.
Open a product brief info@cruciblemgmt.com Go to the six technology productsN‑01
Site
Camp network, local server, field devices, daily capture.
Link — variable
Satellite or marginal cellular. Drops are expected, not exceptional.
N‑02
Cloud
Shared records, backups, remote administration.
Link — steady
Town office connection, treated as ordinary service.
N‑03
Office
Owners and managers, reporting, retrieval on demand.
Local first The site keeps working while the link is down. Entries are captured on site, held locally, and reconciled with the office and the cloud once the connection returns.
Field note — operating premise
Technology products built around the way a placer operation works.
A placer site runs on excavators, generators, pumps and sluices, and the office side has to keep pace with all of it. Crucible Management builds and maintains the technology that sits behind that work — the site systems and the operational record — on sites where power is generated locally, the site connection is unreliable, and the crew turns over during the season.
Each product is bespoke: built for one site, against its own conditions, rather than configured from a standard template. Implementation and support are delivered as services with concrete deliverables, such as a working system, its documentation and a handoff. Scope is agreed before work starts. The approach is informed by hands-on work with Yukon placer operations.
- BuiltPer site, bespoke
- PowerGenerated on site
- LinkUnreliable by default
- CrewTurns over in season
- BasisHands-on Yukon placer work
- Owned byThe operator, throughout
Services
Service specification index
Six bespoke technology products: three that set an operation up, three that keep it running. Each product defines its deliverables, its exclusions, who owns what, and how the finished system is handed over. Scope varies by operation. The operator owns the accounts, the data and the hardware throughout, and managed technology support is optional once a system is in service.
-
Site Technology Plan
A documented plan for the operation, delivered before equipment or software is bought: what runs at camp and what runs in the cloud, who is responsible for each piece, how information moves from the site to the office, what the site connection can be relied on for, and which tools have to work offline.
- Deliverable
- Documented plan
- Precedes
- Any purchase or build
- Owned by
- The operator
-
Field Reporting System
Field data collection and reporting software built for the operation: daily reporting forms designed to be filled in offline, a searchable history of what each crew did, a clear view for owners and managers, and role access that gives each person only the part they need. Delivered working, in the operator's own accounts.
- Deliverable
- Software build
- Capture
- Works offline
- Owned by
- The operator
-
Camp Network and Infrastructure
Connectivity and networking at camp and in the town office, local servers where the internet connection cannot be relied on, and cloud services where it can. Delivered configured for remote administration, documented, and handed over to the operator.
- Deliverable
- Camp & cloud
- Handoff
- Configured and documented
- Owned by
- The operator
-
Operations Records System
A records system covering operating logs, inspection records, monitoring data, field reports, licence and authorization files, and submission packages — with structured access, version history and retrieval whenever reporting is due, and a clean handoff to the operator and its advisers.
The scope is records technology. Permitting and regulatory advice remain with the operator and its advisers.
- Deliverable
- Records system
- Excludes
- Permitting advice
- Owned by
- The operator
-
Access, Backup and Recovery
Permissions are set so each person can reach only what their job requires, backups run on a schedule and are tested rather than assumed, and written recovery procedures tell whoever is on site what to do when something goes wrong, including next season's crew.
- Deliverable
- Access & backups
- Backups
- Tested, not assumed
- Owned by
- The operator
-
Managed Automation and Support
An ongoing service. Automation takes over repetitive office tasks, monitoring and alerts cover servers and connections, and remote diagnosis addresses issues as they arise. Documented support procedures tell the crew what to check and when to escalate, and training is written for the person doing the job. The service scope sets finite coverage hours and response terms rather than leaving them open-ended.
- Deliverable
- Managed support
- Term
- Ongoing, optional
- Coverage
- Finite, stated in scope
On site
What a placer site does to technology
Power often comes from generators, connectivity may depend on satellite or marginal cellular service, and devices pass between seasonal staff. Technology that behaves predictably in town can fail differently at the end of a creek road, and the office still has to retrieve complete records whenever reporting is due.
The design stays simple. Routine operation and first-line troubleshooting should be understandable on site without calling remote support, and the notes left behind should still make sense when a new crew takes over. Every service is set up so the operator holds the accounts, the data and the hardware throughout.
Constraints carried into every service scope designed state
- Site connection
- Interrupted — assumed Connections drop. Tools built for the operation are designed to keep working offline and catch up afterward; services that need a live connection are named in the plan.
- Access
- Partitioned by role Who can see and change what is settled at the design stage.
- Handoff
- Transfers to operator Documentation and training assume the crew may include new staff next season.
Sequence
How a service package runs
One work order, opened at scope and closed at handoff. Nothing is built before the boundaries are written down, and nothing is left running without someone on the operator's side able to run it.
-
Scope first, then build
The service scope names the deliverables and the boundaries before work starts. Backups, recovery steps and permissions are settled at that stage, along with what can realistically be fixed over a slow connection and what cannot.
-
Records stay usable
Reporting and record keeping are delivered so entries can be captured on site, reviewed later, and retrieved whenever the operator or an adviser needs them.
-
Delivered and handed over
Software, infrastructure and training are shaped for the people who use them on site, under the power, connectivity and turnover conditions of the season. Systems are delivered with documentation and a clear handoff, and optional managed support can follow.
End of work order — the operator holds the accounts, the data and the hardware.
Request
Issue a service request
Describe the site, the system or workflow you need, and the conditions it has to work in. You get back a defined service scope: the deliverables, what sits outside it, and how the finished system is handed over.
-
The site
Where it sits in relation to power, road access and the connection.
-
The system
The system or workflow you need, and who has to use it.
-
The conditions
What it has to keep working through, and when it is needed by.
Returned to you
A written service scope naming the deliverables, the exclusions, who owns what, and the handoff. No work begins before it is agreed.