Skip to main content

Whether your team is importing assay results in the office, checking on progress from the hotel, logging core in the core shack, or picking up grab samples off the grid – MX Deposit provides the tools to keep everybody connected no matter where you are.

This session will describe how a distributed team can all work together, on a single version of the truth.



David Kerr
Head of Product – MX Deposit at Minalytix



22 min

See more on demand videos


Find out more about Seequent's mining solution

Learn more

Video Transcript

(gentle upbeat music)

<v Anna>Hi, everybody.</v>

Welcome to our demo of MX Deposit,

my name is Anna Kutkiewicz

and I’m a Senior Project Geologist at Seequent,

and I’m here to introduce MX Deposit.

I am of course, joined by our presenter David Kerr,

who is Head of Product at MX Deposit at Minalytix.

So we’re getting a demo straight from the expert here.

Hi Dave, take it away.

<v David>Awesome.</v>

Thank you very much.

And thank you everybody for taking the time out of your day

and hope everybody’s staying safe out there,

and hope everybody is enjoying this year’s Remote Roundup.

So happy to spend a bit of time with you here today

to chat with you about MX Deposit, and talk through

some of these kind of unique, specific scenarios

and how we can really help you to facilitate

this connection of teams these days.

And we’ll talk about kind of what all that means,

and really what I’m hoping to do here today is give you

just have a discussion around how MX Deposit

facilitates these scenarios.

Not really going to go into too many functional details here.

That’s kind of a follow-up session if anybody’s interested.

So really what I’m hoping to do here

is just spark a conversation that we can either have later

through a Q and A session or through a follow-up

conversation or a dump.

What I’m really trying to achieve here today

is to demonstrate a practical approach on how we can connect

teams and engage teams, specifically using MX Deposit.

At the end of the day I’m a service provider,

I have a product, and I’m really going to focus

the conversation around how my product

can facilitate this process.

And why are we even interested in this conversation?

Or I should say,

why are you interested in this conversation?

I think one of the most obvious ones

is just the nature of the industry.

I mean, we don’t get to choose where deposits are located

around the world.

So we have to just work within this global culture.

So we know that deposits are going to be where they lay

and we just need to work within that.

But then we’ve got corporate offices and corporate teams,

and we’ve got project teams.

And then we’ve got people who are at site, in the field,

and as well as all the contractors, consultants

and other service providers as well.

So for me these are all part of the team.

It’s not just people who work for the same company,

but it’s basically everybody who’s involved

in your projects.

And something that I think has come up a lot more

in the last year specifically,

is this working from home scenario.

I think what once was a bit of a luxury for some people,

this ability to work from home here and there,

has now become more of a requirement for a lot of us.

And that changes things, this changes how we engage

with each other.

This changes how a company and how a business operates.

And so we need to be able to adapt and adjust,

and make use of some new tools that can help us

in that process.

And that’s really kind of what I’m here

to talk to you about today.

So, now we’ll talk through a couple of specifics, right?

So knowing kind of why we’re here, why we’re even interested

in this, how can we do this, okay?

So now we’ll talk through a few scenarios,

and again I’ll try to do as much of this split screen

as I can.

So let me just grab my browser here.

So I’m going to be showing us the Deposit web app,

as well as the Deposit mobile app

for some other scenarios here as well.

So just bear with me as I kina go back between the two,

hopefully it’s not too distracting for anybody.

So I would say step one,

when we’re thinking about this team scenario,

and thinking about getting people connected

is to really get organized, okay?

And what does this mean?

Well, it means identifying who are the stakeholders, right?

So who are the corporate players?

Who are the project teams?

Who are the field teams and the field members,

and what role does everybody have to play, right?

And why that’s important for a system like Deposit

is because that’s going to kind of determine

how we get things set up, right?

We’re going to have various team members

that we need to just now designate who’s doing what,

who has access to what, and ultimately just controlling

that environment.

When we’re going through a setup of the project

we need to just pay attention to where are we operating?

What are any local considerations in terms of boundaries

and tenements that we need to adhere to?

What is it that we’re doing within this area?

So setting up all the requirements around that, right?

So what I mean by this is what’s the regional geology

look like?

This is going to drive what kind of logging parameters

we’re going to use.

Are we doing a detailed diamond core logging?

Are we doing exploratory RC logging?

And these are all going to get broken out

into these different activities that then drive

this logging exercise, and drive the full process

of getting data in getting data out.

And what are all the different points along that.

The operating procedures are important process here as well,

just defining who’s responsible for what,

what happens when this happens?

How does somebody start a new drill hole?

How does somebody go from planning a hole

all the way through to building a 3D model with it, right?

So just what are all the steps involved there?

And then how does the software facilitate that?

And Deposit’s got a lot of mechanisms to be able

to really support that conversation.

Getting connected now, right?

So MX Deposit is a completely hosted

and web based offering, which means you’re accessing it

from anywhere in the world, right?

So anywhere that you’ve got internet,

you can launch a web browser and access

your Deposit account.

There’s no desktop software to install,

there’s no license keys to carry with you.

And it really gets you connected again,

thinking about those stakeholders,

the corporate players in Downtown Toronto

or Downtown Vancouver can now have a real-time access

to the data that’s being collected in the field

anywhere around the world,

and all the different stakeholders in between

also have their relevant access as well.

With offline data capture tools as well,

so we recognize again in the industry a lot of times

we might be out in the field or in a core shack

with no internet.

So we’ve got these tools to be able to get those users

still using the system.

We don’t want them capturing things on paper,

or in an Excel file.

We want them to capture things within the MX Deposit

framework, and that’s where our mobile apps come in, right?

So letting users be able to capture this information

through the standardized legends, and tables,

and configurations, and validations,

and then get all that information

up to that centralized repository.

So these are just kind of features of the software.

Integration is a big piece here too,

where we can start having the conversation

with your other data providers.

These could be down hole survey vendors.

These could be other software vendors.

These could be geochem labs, right?

So we can speak with them.

We can learn about integration scenarios,

and how do we get that data into MX Deposit as well.

So we’ve got some of these, we’re having more conversations

with more of these data providers.

So we are well positioned to be able

to really kind of facilitate that integration

across data in and data coming out.

So when we’re talking about data coming into the system,

we’ve got a lot of different tools available

to work with that.

So when we’re talking manual data entry,

this is where we can set up

the different logging interfaces,

where users are capturing things based off of predefined

legends, and capturing them into tables that have been built

and validation rules that have been established, right?

We’re able to leverage device hardware

in terms of using a GPS to capture a position.

So this could be a field surface sampling program

where we’re capturing accurate position data.

It could also be getting into taking pictures

and associating an image, whether it’s with a drill hole,

whether it’s with a soil sample or a particular interval

of interest, right?

So using our tools you’re able to provide this interface

where these users can capture the required information

in a way that’s consistent and it’s usable, right?

It’s that time to kind of action and time to use

that gets reduced because you’ve got that data integrity

right at the point of capture.

All the way through to capturing sample numbers

off of a barcode scanner as another kind of example, right?

So whether that’s a QR code,

or just a pre-generated barcode.

So I don’t have one here, but I’ll skip that, okay?

Even using a voice to text feature on these tablets as well,

you could even get into a bit of almost a dictation scenario

here as well, right?

Thinking then through other data management functions.

So, this distributed team, the mobile app, that data entry,

that’s going to be our end users getting data in, right?

But that’s not the only way to get data in,

these can be imports from files, right?

So whether that’s coming from a down hole survey vendor,

or an XRF instrument,

or whether this is just another project

that’s coming online that now you want to bring

into the system.

So import tools around that.

Filtering and exporting your data.

So when we get into now managing a list of drill holes,

we can come in and we can start to filter this data out

on specific drill targets, for example.

Or filtering it based off of show me all the drill holes

created in the last seven days, that sort of thing, right?

So narrowing our view and then being able to export the data

in various formats.

So whether that’s dumping it into another software package,

or just creating different versions of these exports

that serve different purposes.

Maybe it’s a quick log type of export

just with generic data, or it’s a detailed as a QA QC type

expert for monthly reporting, right?

So we can really now filter out and refine these export

templates and profiles to match what we need

to get out of the system.

With these distributed teams what’s really important

is getting everybody coordinated and collaborating

on the data.

So we’ve got these tools to let people

have these conversations, right?

So we’ve got this feed where people can see what’s going on,

see who’s working on what, who’s importing assay results.

And we can even get into the case of people asking questions

to other members of the team,

or just promoting and engaging others.

So using our feeds and our kind of networking components

there, we can do it all while keeping the conversation

relevant and keeping it in context, right?

So this is secure, it’s transparent, it’s reproducible.

And it’s now part of the data.

It’s part of the story of these drill holes

and these sampling programs.

We can send messages to administrators

and ask for a new codes and project access,

that sort of thing.

Something that’s really important too that as we’re working

through these drilling programs and sampling programs

is the ability to collect team feedback

and be able to adjust and course correct, right?

Whether that’s just adding new list elements,

or changing list codes, or adding new kind of logging inputs

that we want people to start capturing new alteration

minerals or something like that, right?

So this ability to kind of work as a team,

define some changes we want to make,

be able to quickly and easily go in and make those changes.

And that now everybody on the team is working off

of that changed dataset.

With a distributed system, whether it’s an MX Deposit type

system or even something that you’ve got in-house,

what’s really important to think about is the protection

and the security of this data.

I mean, we fully recognize and appreciate

the money that goes in to these drilling

and sampling programs.

So it’s critical that these are secure,

that only authorized users ever have access.

That we know who’s interacted with the data,

and who’s changed it, and who’s made what changes.

And making sure that it’s always available when we need it.

So whether this is people getting data in,

somebody importing an assay certificate,

or a modeler trying to pull the data out

to start adjusting their model.

All of these different stakeholders and users

throughout the team need to have that access,

in a secure way that’s always available

and always high performing.

And another component to this

is this kind of continuity aspects.

So let’s say that one of our members of this team

happens to leave, then what happens?

By using a commercial system like MX Deposit

with all of the support networks

and kind of material around it, we can offer that continuity

so that we can swap out resources and somebody else

can come in and learn the system.

And it’s not all this knowledge that’s lost

when a resource might leave.

So that’s it, this is short and sweet.

But really it’s just, I wanted to really kind of talk through

that scenario, right?

Identifying kind of what I mean by teams,

which is the just distributed nature of the industry

and deposits around the world.

This new working from home world

that we’re all in right now.

And just, what are some of the tools that we can offer you

to be able to just get these people working together,

get everybody working off the same data,

get everybody capturing data the same way,

telling the same story.

And then letting people have conversations around that,

and as required be able to pivot,

be able to course correct and adjust.

And then ultimately just having

all the different stakeholders identified,

all the inputs, all the outputs,

and hopefully I’ve been able to give you a bit of an idea

of how Deposit can facilitate that.

Obviously in within the time,

I can’t dive too deep into any of those things,

but really if I’ve been able to spark any questions

or ideas here then not where now we could kind of work

into a question scenario now.

And ultimately, if anybody has any further questions

or wants to explore any of these scenarios further,

happy to have that conversation and deep dive if we want to.

<v Anna>Okay, great.</v>

Thanks Dave.

So as David said, we’ve got some time for questions.

I’m going to just give everybody a moment

to type anything in there.

You should see that questions panel

in your little go-to webinar dialogue.

So it looks like we’ve got…

I’ll just ask this first one.

How does MX Deposit integrate with other software?

<v David>Yeah, it’s a great question.</v>

And it’s really something

that we’re always working on, right?

So as of today, we’ve got some integrations in place

with our Seequent partner.

So we’ve got an integration with Target,

and Target for our GIS.

We’re actually actively working through an integration

with the CQL central platform,

which will facilitate the Leapfrog integration

and enable all the notifications that kind of come with that.

We’re working on an integration with the MDX hub

to be able to pull in that instrument, down hole survey

XRF gamma type data.

We’re starting to have conversations

with some of the commercial labs out there.

So the ones that actually have APIs available.

As I mentioned, we’re very well positioned

to be able to really explore these and get you connected

to those other service providers in a way

that you don’t have to revert to expert in importing files.

So you can basically either click a button to go out

and fetch your data, or just get a notification

within the app that a new data sets available

for your review, right?


<v Anna>Cool.</v>

Yeah, I’m especially excited for the central

interoperability with Leapfrog.

How does your data get into MX Deposit?

<v David>Yeah, so few different ways.</v>

There’s that manual logging scenario

that we’ve got mobile apps to facilitate,

we’ve got web apps where users can kind of log directly

into the system.

We’ve got import tools as well,

that can serve a few different purposes.

So whether that’s just dealing with a distinct data set,

whether it’s downhill survey data, assay results, XRF,

whatever that case is, import tools to enable that.

And can also be a kind of a bulk data migration scenario

as well, right?

So as a brand new customer comes online to MX Deposit,

or if a customer acquires another project,

a lot of times we need to kind of work through that data

and figure out how to get it into the system.

And that step typically comes with a cleaning process,

an external validation.

So at the end of the day you get a validated dataset

into MX Deposit that’s now described the same way

that all of your other data is.

So then when you start to pull that data out

you’ve got consistency, you’ve got integrity,

and you can just start using it right away with confidence.

<v Anna>Okay, great.</v>

I guess last question here is,

is MX Deposit limited to exploration?

<v David>No, it isn’t.</v>

So there are these core logging tools that work very well

in exploration scenarios, and even into kind of more early

field sampling, outcrop mapping type scenarios as well.

So all that works, but we also have customers

that are using this in a full production capacity as well.

So grade control, blast hole, sampling and logging,

or even bringing tablets underground and logging rounds

and face samples and stuff like that.

So at the end of the day we’ve built a platform

that really can be applied to any drilling

or sampling scenario because that we’ve build it

to your requirements, so it works.

That’s a nice opportunity then as an organization

to get all operations in the system,

and then start carving things out

by these different activities, started carving out

access mine geos can only ever see,

production data, exploration geos can only work

with an exploration data.

So you’re able to really get the entire team

and that entire workflow fully enabled,

fully supported, fully secure.

And then again, how do we get that data out

to all the other downstream systems?

<v Anna>Yeah, awesome.</v>

Really good points there.

Okay, so it looks like we’re out of questions.

That wraps up our demo.

Thanks so much for your time

everyone that attended.

And of course, David thank you for your presentation.

(gentle music).