Skip to main content

Using the new Seequent Central integration in MX Deposit, you can seamlessly integrate your geological data with the Seequent suite of products.

This session shows how you can push your drill hole data directly to Seequent Central, and create Leapfrog projects directly from that data. As changes are made in MX Deposit and pushed to Central, a quick refresh in Leapfrog updates your model.



David Kerr
Head of Product – MX Deposit at Minalytix

Sarah Connolly
Senior Project Geologist – Seequent


25 min

See more on demand videos


Find out more about Seequent's mining solution

Learn more

Video Transcript

(soft music)

<v Dave>Welcome everybody.</v>

So, today we’re going to be giving you a little sneak peek

of what we’ve been working on here at Middle Lytics,

and with our friends at Seequent.

So, this is really just something that’s been in the works,

and we’ll talk a little bit at the end about,

when you can get your hands on this,

but really just what we wanted to accomplish here today is

yeah, just give you an idea of what we’re working on,

giving you an idea of how we can…

How we’re thinking about these solutions

and how we’re thinking about bringing solutions together

and listening to our customers

who are always talking to us about

how to integrate better,

and how to get things playing nicely.

So, we’re happy to kind of introduce here

the first version of our full integration

with the Seequent Central Platform,

which ultimately achieves an integration with Leapfrog,

as well as other Seequent products as well.

So, what we’ll do here today,

I’ve got Sarah Connolly with me here as well.

So, she’s a Senior Project Geo

on the Seequent Technical Team.

So, we’ll be kind of doing a back and forth here.

I’m going to show you a bit on the deposit side,

and then I’ll hand it over to Sarah

who can show us some of the Leapfrog side,

to just give you an idea of what the full life cycle

of this integration looks like.

So, bear with us as we change presenters kind of halfway.


And this is an important part of the Seequent Evo ecosystem

that we’ve been hearing about, right?

So, this is really starting to introduce some of these ideas

and really what they look like in practice.

So, what I’ll show you here,

and I guess one point here is

I’m kind of making an assumption that the audience here today

has some understanding or knowledge of what MX Deposit is,

and some understanding of what Seequent Central is.

And if anybody out there doesn’t know

what these two solutions or products are,

please reach out.

We would love to give you more information

about either one of them,

but in the interest of keeping this kind of short and sweet,

and really just getting to the point

of what we want to show you,

we’re not going to really go into much details

about these individual projects or products.

Instead, we’re going to talk about

how the two play together.

And I guess the Leapfrog is kind of part of that as well.

So, what I’ve got on my side here,

is I’ve got an MX Deposit instance

and I also have a Seequent Central instance, right?

So, within the central instance, we have various projects,

all that would be kind of set up by the organization

and this would come with different user access,

and permissions and that sort of thing.

And all that we’re really going to talk about

on the central side, at least is dealing with the files.

So, this is going to be the data room

within one of these projects, okay?

So, within this kind of example,

central instance that I’ve got,

there’s a Pudding Hill project here.

That’s what we’ll be working with here today.

And there’s a files area here,

and this is really what we’re going to show you.

So, knowing about this central instance,

now we’ll flip back to MX Deposit, right?

So, everything’s going to start here with the Seequent ID.

And it’s an important part to talk about because

the Seequent ID is really what pulls this all together.

For anybody who uses Seequent products out there,

you’re already familiar with this.

You’re using it on a daily basis.

And so, this is how you access

all the various products, MX Deposit,

this is our authentication service.

this is where you manage all your entitlements,

this is how you’re accessing all of your products.

And so, now what we’re able to do though

from one product to the other,

is just know about the various entitlements that a user had.

So, as an MX Deposit user,

when I come in and I go through this sign in

with Seequent ID process,

this comes with certain identity parameters, right?

So, we know who the user is.

We trust that user,

we trust that they are who they say they are,

but also now we know what else they have access to, right?

So, and this is really important here because

within MX Deposit now, we’re able to set things up,

and know what access they have across other products.

And I’ll show you what that means in a second.

So, within the MX Deposit System,

again, I’m not going to dive into

the various modules functionality here.

I’m going to go straight into our Integrations Module.

So, anybody who uses Deposit out there,

we already have an Imago one here.

We’re working on adding more here as well,

but the next one that’s coming is the Central one, right?

So the Seequent Central.

So, this is synchronizing your MX Deposit data

up into the Central database.

So, if I go through this configuration process,

now using that Seequent ID,

we’re able to now understand

what Central instances you have access to as a user,

and within that Central instance,

what are the various projects, right?

So, we saw here some of the different projects listed here.

Well, in my Deposit config, it’s that same list of projects.

And, we’re thinking about the different scenarios

of having maybe more than one Central instance,

if you’re the type of user that might be working

across organizations or something like that.

But really, you know,

the idea here is the user comes in here,

we know who you are,

we know what access you’ve got

and what entitlements you have within,

the other Seequent products.

And now we can start to bridge these together.

So, for the purposes of our little demo here,

I have a Pudding Hill project,

configured and established within MX Deposit.

And then I have that Pudding Hill project

defined within the Seequent Central Platform.

So I’m able to just basically do a simple mapping here

within MX Deposit.

So, this is where we’re going to be able to bridge

the two systems from a project perspective

and make sure that the data

is the same across the projects,

and also let you work across different projects.

So, if you’ve got different country operations,

or different Central instances,

or just projects and projects everywhere,

this is giving you that ability to now focus in

what deposit project is going to send the data

to what central project.

And the point of having this done

in a config screen like this,

is to just have it configured

so that now every time that I run this integration,

it’s already set.

It already knows where to go.

So, now as I come and I look at my drillholes…

And before I kind of show this and send the data up,

the other thing that we can make use of in this integration

is our new export template feature.

So, this lets us really customize

what this output’s going to look like, right?

So, there’s a certain default export

that you can get from Deposit, looks a certain way,

very much based on the MX Deposit model

and column names and stuff like that.

But now with these expert templates,

you’re really able to customize this and we can make it look

how Leapfrog is expecting it, for example, right?

Just to really streamline that flow of data back and forth.

So, I’ve got a pretty basic

Central export template defined here,

where I’ve got, and I’ve renamed,

to have a collar, assay, lithology and survey files.

And within those it’s basic just whole number,

basically the information that we really need, right?

So, I’ve already pre-configured that export template.

So, now that I’m a user with an MX Deposit,

let’s say that I’ve got…

Let’s say we’re working towards a Drilling Program,

and say that kind of phase one is complete.

And phase one of that drilling program,

was dedicated to one drill target.

So, as the deposit user, I’m going to come in,

I’m going to apply a filter here.

So I’m going to say,

“I only want to submit the data

“for a particular drill target.”

In this case, I’ve got a central valley, right?

So, first I would filter my set.

So, that’s going to give me these 39 drillholes,

and all associated data.

This is the collar data, lithology, survey, assay data.

Again, this is all I’m showing you the final product

of that part of it.

And then from an export perspective,

I can either do kind of that generic export

with the upload to Central option,

or I can just do my straight central export

and it just already knows where to go, right?

So, we did that project mapping.

It knows what project to send it to,

and then using these export templates

it knows how to format that data.

So now, the export has just posted these files,

up into the Central Data Room.

So, if I now come into the Central instance,

and let me just find that same project.

So, here’s that Putting hill.

If I then go into the files or the data room,

as we call it.

So, I now have this MX Deposit folder.

And within this folder,

I have my assay, collar, lithology and survey file, right?

So, this is the final product of everything that I did

up until this point, right?

So, the Seequent ID bridge the gap

between the two solutions,

that project mapping just defined where the data’s going to go,

my export template defined what the data’s going to look like

and what these file names even look like.

So, you can rename and customize those

to exactly what you want.

And then now I’ve successfully posted these files

up to the Central instance,

so that anybody who has access to the Central instance now

can see these files and make use of those files.

So, what I’m going to do now,

is I’m going to pass things over to Sarah,

who is going to show us how she can make use of these files.

And then after, we’re going to do a bit of a specific scenario,

just to show you how things can look

if we do a quick update here,

and what that can look like flowing through.

<v Sarah>Okay, Dave, thanks for that.</v>

Hi everybody.

My name is Sarah Connoly.

I’m a Senior Project Geologist with Seequent,

and I will be sharing my monitor now.

Dave, can you confirm you can see my Leapfrog?

<v Dave>Yep, that looks good for me.</v>

<v Sarah>Awesome.</v>

Okay, everyone.

So, Dave kind of explained the first half of this workflow

and I will take her from here

now that I’m ready to do some modeling with the data

that have been linked from Deposit

through to central,

and then I can then…

Because my Leapfrog instance is also connected

to that central server,

see to that data room and bring in my drilling from there.

So to begin with,

I’m actually just in a completely blank project,

and I’m also going to show you another project

which we have already linked.

So, when I have a brand new project now,

if you guys are already using a Central,

you’ve probably seen this feature before,

but I just thought I’d demonstrate it for anyone

that does not have Central.

So, in a fresh project,

if I right click on the drillhole data folder,

there is this option to input drillholes via Central.

So, if I click on that one,

again, because my Seequent ID is linked

to the Central server,

I can see into any of the projects on that Central server.

I’m going to click on that Pudding hill,

click on the file link,

and you’ll see,

I’ll be able to see that subfolder called MX Deposit,

which is what Dave was looking at within the Central portal.

And I can see those four files that he (indistinct)

from MX Deposit.

If I open up the collar file,

it will automatically pick my survey, assay and lith tables.

And it’s just a case of then importing them.

My Leapfrog Geo will look to the Central Data Room

and see those files,

and then you’d be walking through.

You can have classic drilling imports,

as you all know pretty well from just imports in CSVs

all over the years.

That I won’t actually import them all today,

but that is what you would do

if you were starting from fresh.

If I had some Pudding hill actual project

where I already have a geological model built,

I can open up my local version of that model.


This already has a geological model built

whereby I’ve already imported my drilling.

And it might be tricky to see (indistinct)

where there’s a little Central,

see on all of my drilling tables.

So, I automatically know that they are connected

to that Central Data Room.

I built my geological model here.

I’ll just hide the cover there.

And you can see the drillholes that have been imported,

and then I’ve built my geological model,

based off of that information.

If I just open up the collar table,

you can see that I have those faulty holes

that Dave has actually already filtered out.

Based off of that Central Valley filter from an MX Deposit.

For now, in the background,

Dave’s actually going to push another set of data

to expand our data set,

as we’ve done some more drilling in the field.

Let me know when you’ve done that Dave.

<v Dave>Yeah.</v>

So, my export’s done here.

So basically all I did in MX Deposit was

I cleared out that filter, right?

So, I no longer want to filter the drillholes list

to that specific drill target.

Now, I’m saying we’re at the end of our drilling program.

So, now I’m going to give you all the drillholes

across all drilling projects.

So, I already ran that export.

So, now those files and new versions of those files,

are available on that Central (muffled voice speaking).

<v Sarah>So, before I could jump back to Geo</v>

and actually update that drill in,

I just thought, I’d show you the Central portal

one more time.

I’m in my put Pudding hill project.

If I click on the files tab,

I can take a look in that MX Deposit slip folder.

I’ll just take a look at one of my files there,

and I can see that Dave has uploaded a new version

on March 10th at 9:14 AM.

So, I know that that fresh data

has actually been uploaded to the Central Data Room.

If I go back to Leapfrog geo now,

I’ve got my model built.

It’s simply a case of right clicking on my drillholes,

reload latest file version.

And that’s just going to kickstart

the reload of my drilling.

So, it’s going to look to the data room,

it’s going to see that new file for the collar, survey,

assay, and lithology tables,

and then it’s going to go through the workflow of…

Look into that data.

I’ll reimport it,

and then it will dynamically update my model.

<v Dave>Yeah, that’s excellent.</v>

So that’s…

You know, that’s really what we wanted to show you there.

So, I think she’s showing you here,

the update of those files.

So, really the main points here

is to just demonstrate that workflow, right?

And Central really being the engine, if you will,

that kind of drives all of that.

And, you know, Leapfrog is kind of one scenario.

This is probably the main scenario

that we’re talking about now,

but really knowing where Seequent is going

with the Evo ecosystem and the other products,

is by doing this through Central,

it’s now going to enable other solutions as well,

to be able to pull this MX Deposit data.

And, one of the things

that we probably don’t have a time to show it,

but eventually Sarah’s Leapfrog view here

would actually notify her,

that the new files were available.

It would just give her a bit of an icon there that said,

“Hey, you’ve got a new collar file,

“or you’ve got a new asset file.”

So, that’s again showing the new notification system.

And by these drillholes sets

being tied to these data room files,

then you know,

now we’re able to see everything come together.

We’re able to see all the solutions

kind of play together here,

and what that workflow looks like end-to-end.

<v Dave>Yep.</v>

So, I’ve got all my new collars in there.

Now, it’s just running through my geological model update.

Obviously, you’d want to be doing any internal selection,

any interrogation of your model once it’s processed

and all of that kind of a thing.

But, by using that connection through Central,

you’ve got that real smooth link between your login data

and your Geological Model.

<v Dave>Excellent.</v>

Okay, so that’s great.

I guess I didn’t quite mention it beginning,

but, we do have some time now

to just go through some questions.

We do have a few submitted here,

but even now, as I’m talking,

feel free to submit any other questions that you want.

And so, now we’ll just go through kind of a quick Q and A

of the questions that we do have,

and if anybody has any follow-up questions by all means,

feel free to reach out to any of us.

And we’ll be happy to follow up with you.

So, first question we have here is just asking about how

the data is updated in the data room.

And I think really trying to understand

if this is a manual process or an audit automated process.

So, it’s a good question.

And I think, you know…

So, what we’re showing here today,

this isn’t the final product at this point, right?

So, some of the UI probably more on the deposit side,

some of the UI might be a bit different

when we finally release this.

I’m showing you a manual push-up of the data,

but this will definitely evolve into some ability

to whether that get pushed on some schedule,

or an event or something like that.

That’s kind of a natural evolution of this.

So, I think when we first get this out there,

it will be just a manual push.

So, the user is going to control when that data goes out,

but definitely it would be a natural evolution

to get this thing working even more in an automated manner,

whether it’s based off at status change,

or some schedule event.


I think…

So, there’s a Leapfrog question here

that I’ll send to you, Sarah.

So, can Leapfrog handle getting data from two sources,

such as a mix of CSV, which I guess would be kind of

an external CSV,

and now stuff coming from MX Deposit.

<v Sarah>Yeah so,</v>

if you set up your main link from MX Deposit,

so that you’ve got your collar and survey table,

you can add extra CSVs for any new tables

that you want to bring in there.

I’d have to test it the other way around.

I’m afraid (laughing) I’ve not tried that before,

but you can definitely add extra information

later if for some reason it’s not your Deposit database.

Let me, I’ll double check on the other way around

Nicole, and I’ll let you know.

<v Dave>Perfect.</v>

And I think one of the…

One kind of probably burning or pressing question

on everybody’s mind is,

when is this going to be available?

At this point, so we are…

We’ve got a pretty good…

Call it a proof of concept in place at this point.

So, we’re just going through kind of finalizing

that entire user experience.

There’s still some entitlement things to kind of sort out

and commercialization aspects to this,

but, currently it looks like we’re targeting

kind of the summer, kind of a mid-August timeframe.

So, that’s kind of the current target to get this out.

And part of that too,

is to give us a bit of time to have conversations

with some people out there

that are using both MX Deposit and Leapfrog,

and central as well, right?

So, we’re looking for feedback.

We’re looking for comments on, you know,

is this going to provide value?

Is this useful the way it is?

Do you see something that’s maybe missing?

Yeah, any kind of general comments or feedbacks

are always appreciated and always help us

kind of get to that final product.

And I think another one that I know,

I always think about at least for MX Deposit customers,

you know, because we see that this all goes

through Seequent central, right?

And so a question around that is likely going to be,

am I going to have to go and get kind of a full-blown

instance of Central, to be able to run this?

So, what’s happening around that, is,

Seequent is actually working out kind of a new…

A new solution within the Evo ecosystem,

which will basically enable access to this integration

if you don’t have Central.

So again, the details aren’t fully formalized there.

And, I suggest that anybody that is curious

or interested in what that might look like

or what that might mean for your organization,

to please reach out to your account managers

and account executives,

so that we can have that conversation

and get an understanding of where you are,

and what your requirements are,

and then how we can make sure that the solutions

that we’re packaging and putting together

between Middle Lytics and Seequent,

are going to solve the real challenges that are out there.

So, yeah, I think we’ll leave it at that.

There’s a few more questions here,

but I think we can maybe follow up

on some of these just externally.

And definitely if anybody else has any further feedback

or questions or comments,

definitely send them through

and we’ll be happy to answer everything

and clear it up for everybody else.

So, thanks everybody for taking the time.

(soft music)