Technical Tuesday: Peer Reviewing with Seequent Central

Collaboration is no longer optional but a key requirement of geological modelling and decision making. Now more than ever, as projects are becoming increasingly complex, teamwork and stakeholder engagement are required to ensure all information is included and all points of view are considered. Understanding and improving your workflows and addressing challenges using a robust peer-reviewing process can be the key you need to unlock value from your deposit and progress your projects to the next stage.

Join Seequent’s Antonio Garibaldi and Jacob de Lacey, who will discuss:

• The peer review process
• Collaborative decision making
• Current challenges of peer reviewing
• Multi-discipline data integration

Overview

Video Transcript

[00:00:02.130]
<v Jacob>Hi, everyone.</v>

[00:00:03.460]
Welcome to the technical Tuesdays webinar series.

[00:00:10.360]
It is time for another Central focused webinar.

[00:00:13.240]
We hope everyone is well and that you will enjoy

[00:00:15.460]
this discussion focusing on ways of making good decisions

[00:00:18.970]
through a best practice peer reviewing process.

[00:00:22.230]
Please feel free to share this content with colleagues.

[00:00:31.690]
My name is Jacob de Lacey, I’m the Director for Seequent

[00:00:34.810]
Data Solutions in the Asia Pacific region.

[00:00:37.510]
And together with my colleague Antonio Garibaldi,

[00:00:40.800]
Central Technical Specialist based in Perth,

[00:00:43.580]
we will be presenting today’s webinar,

[00:00:46.080]
Peer Reviewing with Seequent Central.

[00:00:49.830]
We believe that collaboration is no longer an option.

[00:00:52.900]
Now, more than ever projects are sufficiently complex

[00:00:56.330]
to require a team effort.

[00:00:58.580]
So understanding and improving your routines and risks

[00:01:02.600]
using a peer reviewing process can be the key step you need

[00:01:06.190]
to move your projects to the next step.

[00:01:10.620]
I would like to outline a few details for this webinar.

[00:01:14.130]
The audience will be muted during the presentation

[00:01:17.270]
but you can use the questions panel to ask any questions

[00:01:20.000]
that come to mind.

[00:01:21.710]
We will answer these at the end of the session or by email

[00:01:24.910]
if we run out of time.

[00:01:27.670]
Our recording of this webinar will be sent to you

[00:01:29.810]
in a follow-up email.

[00:01:32.060]
Any other content mentioned during the session

[00:01:34.150]
can also be sent to you.

[00:01:35.670]
So please get in touch if you are interested

[00:01:37.460]
in a tailored demonstration of the webinar videos

[00:01:40.820]
or online resources.

[00:01:43.190]
Okay, let’s get started.

[00:01:47.010]
Here’s the agenda for today’s webinar

[00:01:49.540]
in which we will go through a quick introduction to Central

[00:01:52.900]
and to brief discussion of peer reviewing

[00:01:54.860]
and internal audits.

[00:01:57.100]
Then we will move straight into an active demonstration

[00:01:59.730]
of the system and proposed workflows discussing

[00:02:02.670]
how you can build an ideal peer review process

[00:02:05.250]
with the help of Central.

[00:02:10.460]
A little background on the company.

[00:02:12.710]
Seequent, now a Bentley company is a leader

[00:02:15.540]
in the development of the visual data science software

[00:02:18.390]
and collaborative technologies for the geoscience community.

[00:02:22.480]
It is our mission to enable our customers to make

[00:02:24.700]
better decisions about the earth, environment

[00:02:27.140]
and energy challenges.

[00:02:29.500]
Because it has that robust decision-making process

[00:02:32.170]
that provides security and longevity to an organization.

[00:02:39.440]
Our solutions encompass a range of software products

[00:02:42.580]
applicable for use across the mining, civil engineering,

[00:02:45.810]
environmental, and energy industries.

[00:02:50.500]
Most of the things we are going to discuss today

[00:02:52.950]
are cross sector.

[00:02:54.700]
However, we will use examples

[00:02:56.480]
more familiar to the mining sector.

[00:02:59.900]
Here you can see the summary with the core products

[00:03:02.260]
of Seequent ecosystem driving value across

[00:03:05.170]
the lifecycle of a mining operation.

[00:03:12.670]
Our experience working with many customers across

[00:03:15.530]
multiple sectors and regions leads us to believe

[00:03:18.580]
that the peer review process for geological modeling

[00:03:21.400]
appears to be haphazard in most organizations

[00:03:24.180]
with either very manual or limited auditability.

[00:03:28.420]
We believe this points to an interesting need

[00:03:30.790]
for a solution that is intuitive, effective and efficient

[00:03:34.820]
while incorporating automatic auditability

[00:03:37.237]
and data security.

[00:03:40.850]
This brings us to the technical discussion.

[00:03:42.940]
And so, I will hand over to Antonio.

[00:03:47.900]
<v Antonio>Thank you, Jacob.</v>

[00:03:49.290]
Hello, everyone.

[00:03:51.300]
Let me start running you through a short discussion.

[00:03:55.410]
The basic reason for an internal assessment of procedures

[00:03:58.840]
and outcomes is business risk reduction.

[00:04:02.670]
So the tool you use have fundamental importance

[00:04:06.130]
whereby you can address debates and decisions.

[00:04:10.170]
They must catalyze the process and will stop results

[00:04:13.851]
to enable people involved with to free up their time,

[00:04:17.440]
to do what they were trained for, interpreting and analyzing

[00:04:21.170]
the data to make the best possible decision.

[00:04:25.670]
On that context, we reach in mirrors things like data,

[00:04:30.170]
model management with previewing processes.

[00:04:34.780]
Furthermore, it’s being on while internal audits

[00:04:38.810]
and behavioral process have been required

[00:04:41.040]
for a professional auditable and assessable to address

[00:04:45.553]
its discussions and decisions in a fast, safe

[00:04:49.920]
and interactive way.

[00:04:52.925]
And this is our main topic of discussions

[00:04:56.258]
on today’s session.

[00:05:02.490]
So what exactly are we talking about?

[00:05:07.100]
What is the peer review?

[00:05:11.405]
Peer review is nothing more than assessment process,

[00:05:15.180]
an internal audit track in which one of your colleagues,

[00:05:18.810]
in general with the same employment level will review

[00:05:22.800]
audit and validate your process,

[00:05:25.970]
also your procedures and outcomes and generally

[00:05:29.350]
before your work progresses to the next step.

[00:05:38.600]
Okay, now that I know what is it,

[00:05:41.900]
how about is the reason why my company and I need to run

[00:05:45.490]
a process like that?

[00:05:47.030]
They trust me, I trust me.

[00:05:50.080]
For example,

[00:05:53.500]
identify and minimizing risk of costly mistakes

[00:05:56.340]
can ensure you have a project and your job much longer.

[00:06:02.550]
Also projects have red flags can help you to detect

[00:06:06.784]
potential errors.

[00:06:08.190]
Some are obvious, others not so evidence but most of them

[00:06:12.220]
are critical factors.

[00:06:14.570]
Find them, debate them, discuss why they happened.

[00:06:23.520]
Expertise sharing and quality improvement.

[00:06:26.500]
The prompt benefit of peer review is bringing to the table

[00:06:30.120]
ideas and insights that can save time and money.

[00:06:34.330]
Guidance driving the big picture understanding.

[00:06:40.830]
The peer review helps to address reproducibility

[00:06:44.810]
to a project which ensure procedures have been applied

[00:06:49.520]
correctly and changes along with the project life cycle

[00:06:52.760]
are predictable enough to avoid big problems.

[00:06:57.010]
The history always repeats,

[00:06:58.490]
so learn from good and bad decisions.

[00:07:02.924]
This also has to do with the concept of persistence

[00:07:06.690]
for projects that operate for years where evidence

[00:07:10.770]
and methodologies developed through the time

[00:07:13.630]
have to be available and assessable.

[00:07:17.310]
Also, an open communication is no longer an option

[00:07:20.370]
for technical motivations or government requirements.

[00:07:24.810]
Anyway, it helps you to understand the project

[00:07:28.540]
and its provisional weakness before they become permanent

[00:07:31.553]
as well as its strength and how to boost them up.

[00:07:43.760]
And how we can do that?

[00:07:47.880]
From here, we have a wide field of discussion

[00:07:51.540]
but the answer is simple.

[00:07:53.770]
Today we are going through the wealthy and fruitful,

[00:07:57.660]
good practice direction.

[00:08:00.160]
You starting with

[00:08:05.440]
a good organization of your projects and process

[00:08:10.910]
beginning with database basic rules

[00:08:14.400]
then go to the geology related issues.

[00:08:18.280]
Make use of checklists to cover all the possibilities

[00:08:21.550]
and don’t forget to resist everything.

[00:08:28.332]
Choose the suitable assessor that runs constructive

[00:08:31.410]
assessment and helps to anticipate for future risks

[00:08:35.620]
and potential alternative for your problems.

[00:08:41.750]
Determine procedures and make them official

[00:08:44.370]
in your company’s policy.

[00:08:50.270]
And run a frequent and continuous process

[00:08:54.910]
such as reconciliation and performance checks

[00:08:58.270]
in order to verify how efficient is your model

[00:09:00.960]
and workflows.

[00:09:10.200]
And what is the peer reviewer role?

[00:09:20.150]
Regarding the assessor role,

[00:09:22.510]
it starts through a detailed assessment.

[00:09:25.270]
There’s no space for last minute evaluation.

[00:09:29.050]
Review the technical details, the tools available,

[00:09:32.070]
and also teams ability to use these tools.

[00:09:36.500]
Special attention to scale issues that perhaps

[00:09:40.457]
were already discovered by other teams.

[00:09:48.470]
Knowhow and accountability transferring.

[00:09:51.500]
So you can make sure the experience of the professionals

[00:09:56.440]
involved is transmitted to the team.

[00:10:03.800]
Define the quality level for each step and the state

[00:10:09.780]
if the project has enough quality to be continued

[00:10:12.770]
to the next level.

[00:10:16.220]
The peer reviewer should not do the interpretation work,

[00:10:20.170]
otherwise we would need another peer reviewer

[00:10:22.940]
for his or her work.

[00:10:25.020]
So the peer reviewer should keep focus on the assessment,

[00:10:28.660]
requesting changes throughout the process as required.

[00:10:36.320]
Documentation of all steps is the most heavy point.

[00:10:40.130]
It includes for instance, comments through a 3D web tool

[00:10:45.700]
and documentation through a professional storage tool.

[00:10:52.490]
So the process landmarks.

[00:10:59.320]
The database has a fundamental importance here.

[00:11:02.800]
Basic inspections in the raw database as well as checks

[00:11:07.050]
such as EDA’s basic statistics and the composite things

[00:11:11.340]
are essential.

[00:11:13.260]
Equally important is how you manage and store them.

[00:11:18.220]
Database validation in 3D allows you to identify consistence

[00:11:23.160]
regarding interpretation versus two holes for example.

[00:11:27.543]
In the end of all this checks, make sure you retain

[00:11:30.950]
and organize all the data.

[00:11:33.360]
However, be a 100% sure you are using

[00:11:37.340]
only the verifiers once.

[00:11:41.190]
Also make sure documentation in the audit trail

[00:11:44.450]
in the chains which includes track the file history

[00:11:48.060]
and events for example.

[00:11:54.910]
Think about the geology model after a good check

[00:11:58.940]
on the previous topic.

[00:12:01.400]
Interpretation is the key deed here.

[00:12:03.950]
Do not fall in love for your model,

[00:12:07.810]
question it and encourage your team to disagree

[00:12:11.400]
with the current interpretation, provoke debates.

[00:12:16.080]
Things like location, boundary

[00:12:18.300]
and interpretation methodology are the starting points.

[00:12:23.120]
What are the control keys?

[00:12:26.730]
Check for inconsistency in the geology, geotechnical

[00:12:31.270]
and structural parameters.

[00:12:34.130]
Run contact analysis to determine hard or soft boundaries

[00:12:38.350]
for domains, use cross sections and run 3D checks

[00:12:42.941]
in all the heads and triangles through a database comparison

[00:12:47.740]
to help you to identify not so obvious inconsistencies.

[00:12:53.530]
Special attention when integrating different data,

[00:12:56.900]
RSC and diamonds railing, for instance,

[00:12:59.323]
as well as project with multiple databases.

[00:13:03.780]
Ensure you run reconciliation checks,

[00:13:06.600]
contrasting interpretation versus other data

[00:13:10.267]
and the raw information based in subjective methodology

[00:13:15.540]
such as maps, geochemistry, and geophysics.

[00:13:23.040]
Then check your block model estimation

[00:13:26.060]
and your resource classification.

[00:13:30.520]
Bring discussion about the biography to the table,

[00:13:34.560]
is it robust enough?

[00:13:37.830]
If there is a lack of basic skills in the team,

[00:13:40.720]
help by addressing internal and external courses.

[00:13:45.050]
Questioning your methods and consider all the ones

[00:13:49.230]
for your estimation, use 2D and 3D tools in conjunction.

[00:13:55.780]
Keep rethinking your classification to the deadline.

[00:14:02.840]
So finally, we can see this suggestion sequence solution

[00:14:09.310]
that could be part of the process as your tool to address

[00:14:13.860]
what we discussed so far.

[00:14:17.170]
Note that Central has an important paper here

[00:14:21.790]
and it is really well equipped to address most of the topics

[00:14:27.820]
as we are going to see next.

[00:14:34.240]
Now, a brief line about Central.

[00:14:37.670]
We developed Central to address consistent feedback

[00:14:41.070]
from clients about challenges and tangential work

[00:14:44.410]
related to the modeling process.

[00:14:49.290]
A model and data management and collaboration tool

[00:14:53.290]
to allow teams to visualize track and administer their data

[00:14:57.700]
through a centralized environment would be great fit, right?

[00:15:01.850]
So a single source of truth can minimize the time span on

[00:15:06.560]
basic data management and allow more time for cordial

[00:15:10.800]
science work.

[00:15:12.400]
This is what century is about.

[00:15:16.090]
The main idea is to bring project teams together,

[00:15:21.860]
holding all your critical data in one place.

[00:15:25.060]
So you develop more integrated and dynamic workflows

[00:15:29.580]
and build robust models.

[00:15:32.920]
In a sense, Central is a cloud based solution.

[00:15:37.560]
It can be accessed in the following ways.

[00:15:43.020]
The Central Portal where the management process

[00:15:46.630]
is a completion for both projects and users, right?

[00:15:52.370]
There is a notification panel here that you can set

[00:15:55.830]
to follow a project activity as well as to address

[00:15:59.630]
collaboration, technical discussions,

[00:16:02.110]
such as those ones during a peer review.

[00:16:05.062]
Project workspace including a data room to store

[00:16:09.220]
and share all the scientific data.

[00:16:13.200]
And of course, the web visualization 3D tool,

[00:16:17.840]
that is also a cloud capability which allows a Central user

[00:16:21.870]
to share objects and ideas directly in 3D in a web browser.

[00:16:29.820]
The Leapfrog connection that includes Geo, Edge, Works

[00:16:34.610]
or Geothermal.

[00:16:36.300]
It’s where the addition process take place and we can define

[00:16:40.650]
various workflow structures through the object integration.

[00:16:45.160]
You can download and upload projects from and to Central.

[00:16:54.430]
Oasis Montaj and target can be also connected direct

[00:17:00.393]
to the data room in Central whereby is your soft grids

[00:17:03.750]
and boxes for instance, can be published in a direct way.

[00:17:08.350]
And once stored in Central,

[00:17:10.510]
can be directly imported into Leapfrog.

[00:17:14.230]
We also have an integration with both in house

[00:17:16.990]
and partner solutions granting you the following modes

[00:17:20.500]
such as GeoStudio in August.

[00:17:23.860]
The idea is streamlining workflows,

[00:17:26.560]
remove manual data management tasks.

[00:17:32.590]
Also coming soon in August,

[00:17:35.200]
we will have the MX Deposit integration.

[00:17:38.890]
MX Deposit is a service solution for classy, simple

[00:17:44.250]
and drilling data management.

[00:17:46.120]
Once integrated, you would be able to create

[00:17:48.870]
a streamlined workflow from MX Deposits through Central

[00:17:53.120]
and Leapfrog Geo.

[00:17:54.900]
So you update your core logging data in just a few clicks

[00:18:02.250]
and your model will update in turn.

[00:18:15.370]
So we can organize the Central features in five main groups.

[00:18:24.850]
The 3D cloud capability,

[00:18:30.710]
a place where there is consistency and persistence.

[00:18:35.570]
All the information built at the time is available including

[00:18:40.810]
for projects that operate for eight years for example.

[00:18:47.360]
The version control for an optimal track.

[00:18:53.930]
A collaborative environment that can ensure a team

[00:18:58.890]
based for, for example.

[00:19:01.930]
And a centralized, secure and accessible

[00:19:06.510]
single source of truth.

[00:19:14.090]
Cool, putting it into practice to give you

[00:19:18.380]
a better perspective about how the system works.

[00:19:21.840]
Here we can see a simple example of workflows.

[00:19:28.550]
We can have both exploration teams working through

[00:19:31.310]
the field, selecting new target areas for example,

[00:19:34.410]
as well as an open pit project already in production.

[00:19:39.980]
As soon as we evolve projects, new revisions are created

[00:19:46.320]
and published generating these notes

[00:19:49.270]
that are our version control and all the should be driven.

[00:19:54.860]
We also have all the software suites integrated

[00:19:58.000]
such as a contribution from a geo-physical team

[00:20:01.960]
which uses Oasis Montaj to import the two degree

[00:20:05.790]
direct to Central and then Geos also import direct

[00:20:10.440]
from Central this files.

[00:20:19.900]
Also note the object integration happening across projects

[00:20:24.300]
from different styles and teams.

[00:20:32.430]
Here we can see, there is a notification received

[00:20:35.920]
by me about an action required.

[00:20:38.190]
So you can click on it and be directly on the 3D perspective

[00:20:43.820]
and the resource, information

[00:20:47.650]
and report delivering et cetera.

[00:20:51.010]
Heaps of possibility.

[00:20:58.310]
So let me jump into the demonstration we prepared for you

[00:21:04.100]
with some of the points discussed above.

[00:21:09.200]
Sweet, as discussed so far, Central is a system hosted

[00:21:14.784]
in a server in which we have application’s work around.

[00:21:21.430]
Here we can see some of them such as our best friend

[00:21:27.030]
Leapfrog, right?

[00:21:28.560]
That it’s the Diishan Gate here.

[00:21:32.730]
You can see here, the project tab where you can access

[00:21:37.190]
your Central information such as the history tab here

[00:21:45.810]
for each project.

[00:21:50.340]
Look the branches on the left of the screen

[00:21:55.570]
and the graph representing the evolving line.

[00:22:00.590]
And here on the right, the comments panel that by the way

[00:22:04.800]
you can hit the thumbnails and load the comment

[00:22:11.340]
and the 3D perspective also in Leapfrog.

[00:22:15.860]
If you want to publish,

[00:22:20.240]
after some edition you can upload this revision to Central.

[00:22:29.560]
Select the files you would like to make available

[00:22:34.500]
in the web links and follow the process such as branch names

[00:22:39.720]
and stuff like that.

[00:22:44.010]
We also have Oasis Montaj as an integrated software.

[00:22:51.270]
Here you can connect to a server and as you’re happy,

[00:22:58.060]
you can publish to the grids, boxes and all the data

[00:23:03.560]
direct to Central data room.

[00:23:10.198]
Let me show you now MX Deposit, our classic simple

[00:23:16.060]
and through whole data management.

[00:23:20.970]
That is also by the way, going to be integrated

[00:23:23.970]
with Central next month.

[00:23:27.320]
You can see all the options you have

[00:23:31.190]
and how friendly and intuitive is everything.

[00:23:39.860]
And here, Central Portal, the management

[00:23:44.510]
and collaboration web app.

[00:23:47.950]
In today’s webinar, I’m going to show you some pieces

[00:23:51.020]
of the system in particular, the web based workspace.

[00:23:57.069]
This will be only few but essential fragments, tools

[00:24:01.970]
or features of Central whereby you can play and apply

[00:24:05.960]
some of the concepts of all the peer review process, right?

[00:24:09.880]
By the way, I’m going to use a beta application

[00:24:12.390]
for some stuff, so I can run you through some features

[00:24:16.130]
that will be available in Central in August release.

[00:24:21.080]
That by the way, it’s a major milestone for us

[00:24:24.780]
as we make significant updates to a number of cloud service

[00:24:30.570]
that make up Central, all right?

[00:24:34.850]
Cool, let’s get started our tour by my mail.

[00:24:42.540]
As the peer reviewer for one of my colleague’s project,

[00:24:48.660]
I’ve received this notification in my mail

[00:24:51.900]
about someone tagging me to a comment in Central.

[00:24:59.310]
So I can read some information about this notification.

[00:25:03.910]
And if I click here, in this link, it drives me direct

[00:25:09.450]
to the 3D perspective and where I can start the process

[00:25:18.110]
from my perspective.

[00:25:20.890]
So this is again, Central Portal, right?

[00:25:24.600]
More specifically, the web based whereby you can run

[00:25:28.840]
your discussions and set comments and assessment request

[00:25:32.750]
for example.

[00:25:35.670]
In this example, I can…

[00:25:42.087]
Like a simulation let’s reply my colleague here

[00:25:46.420]
stating I will change this revision stage to for example,

[00:25:52.840]
peer review, right?

[00:25:54.710]
As the peer review process started.

[00:25:59.150]
So everyone can be aware we are currently running

[00:26:04.640]
the internal audit here.

[00:26:06.070]
So, let me write this a message.

[00:26:18.900]
Yeah, we will also ask the project owner

[00:26:24.500]
to lock the project branch avoiding other people involved

[00:26:31.440]
keep publishing revisions about this project

[00:26:33.910]
in the same revolving line for example.

[00:26:43.350]
Yeah, so,

[00:26:50.440]
in Leapfrog now, if you are the project owner,

[00:26:56.850]
you can lock this branch in a project tree.

[00:27:01.180]
Setting a message for example, to the team and defining

[00:27:07.240]
how many days this branch will be locked, right?

[00:27:13.700]
Which will trigger an expiry date.

[00:27:19.280]
Look there, close it, bad luck.

[00:27:24.610]
Cool, now back in Central Portal,

[00:27:28.120]
let’s see the project overview dashboard.

[00:27:35.740]
We can add some details about the projects

[00:27:38.410]
as well as see a summary about the project’s activities

[00:27:41.940]
and settings.

[00:27:44.590]
From here, note, you can follow an access the latest comment

[00:27:49.460]
and discussing thread in our peer review.

[00:27:53.500]
And you can also go to web based

[00:27:57.650]
by hitting the thumbnails here.

[00:28:04.580]
The data room, it’s placed it in the project perspective

[00:28:10.830]
and is accessed by clicking on this file tab

[00:28:18.000]
from which you can organize your data as well as track

[00:28:23.370]
the file history through out such as this one for example.

[00:28:29.110]
We have, here you can see a folder

[00:28:32.210]
for the peer review process.

[00:28:36.547]
There are some great use cases about the dot phoning

[00:28:39.870]
in the peer review process.

[00:28:41.930]
I would start with the possibility of addressing

[00:28:44.300]
the suitable permission also on the file perspective.

[00:28:48.010]
So people would only be able to access projects and files

[00:28:54.280]
they are allowed to and during the period of time

[00:28:57.600]
it requires their access, right?

[00:29:01.015]
Additionally, the version control, Central allowed you

[00:29:05.770]
your project revisions are also available for files,

[00:29:10.530]
any type or size by the way.

[00:29:14.050]
This way, in a diligent process,

[00:29:17.630]
you can set an audit trail for the files.

[00:29:20.590]
You can use it to build your projects

[00:29:24.790]
such as the programs and reports.

[00:29:31.260]
Furthermore, some of these files such as three holes,

[00:29:34.900]
points and structural data just some examples,

[00:29:39.560]
can be directed, integrated to your Leapfrog projects

[00:29:43.430]
and as soon as they have updates, you’d be notified

[00:29:48.160]
in Leapfrog about this new version.

[00:29:56.840]
As a good example for a peer review process,

[00:29:59.890]
you can identify a problem in the topography,

[00:30:03.030]
so you can notify the server, server 18 by web based

[00:30:09.750]
and make them know about it.

[00:30:12.030]
Then as a reviewer, you can stop the process till they solve

[00:30:17.380]
the problem and publish the new adjustment.

[00:30:21.870]
And you can restart the process with one red flag down.

[00:30:31.780]
Integrating the drill holes tables from the data room

[00:30:34.450]
directly just Central for to Leapfrog, sorry,

[00:30:38.870]
works in the same way.

[00:30:40.200]
As soon as you have a new version of this table

[00:30:43.840]
in the data room, you’ll be notified in Leapfrog

[00:30:46.650]
about the potential reload.

[00:30:49.890]
And with Central being integrated to MX Deposits in August,

[00:30:55.330]
the concept will be the same but instead of updating

[00:30:58.790]
your CSV tables and publish them to the data room,

[00:31:04.040]
you will identify consistency in the web based, in 3D,

[00:31:09.490]
such as this one and require the change to be done

[00:31:17.460]
in the source of the data,

[00:31:20.900]
that this case is in the MX Deposit.

[00:31:25.610]
Then through the API integration,

[00:31:30.060]
the information, the data will be updated

[00:31:32.810]
and the project owner can apply the reload in Leapfrog.

[00:31:42.070]
So I reply from this stakeholder involvement,

[00:31:49.200]
pointing another detail.

[00:32:00.110]
When it’s also registered in the thread

[00:32:06.540]
and as soon as the MX Deposit and Leapfrog apply the changes

[00:32:16.044]
made in MX Deposit, a new version,

[00:32:23.210]
a new revision is published to Central.

[00:32:28.170]
And for example here, it states changes required

[00:32:31.630]
by the peer review on the drill hold WP030T.

[00:32:40.164]
And so, we can also access

[00:32:55.810]
the information that was fixed in the following revision.

[00:33:13.040]
Back to the dashboard here, on the description for example,

[00:33:17.820]
I can insert some details about this project

[00:33:23.870]
by setting the location, you can organize your projects

[00:33:28.110]
in groups at the project tab in Leapfrog.

[00:33:37.200]
Look how the description appear here when you are

[00:33:40.930]
in Leapfrog and hover your mouse.

[00:33:48.500]
We also have the possibility of access the events tab here

[00:33:53.960]
on the project perspective.

[00:33:57.860]
Or the side events tab where you can for example,

[00:34:03.220]
search and audit change and records on the project history.

[00:34:09.840]
You can filter specific actions and time intervals

[00:34:14.900]
so you can explore and use it in your audit trail

[00:34:20.540]
documentation.

[00:34:31.090]
The users tab, it’s where you manage people access

[00:34:34.860]
to projects.

[00:34:37.690]
For instance, in case we want to limit people access

[00:34:41.980]
to the additional approach while the peer review

[00:34:45.110]
is in play for example, you can provisionally change

[00:34:48.610]
their permission to viewers.

[00:34:55.020]
Then they would not be able to download, edit or publish

[00:34:59.620]
models until you grant them access again.

[00:35:09.290]
This instance here, is a beta functionality to be launched

[00:35:13.280]
next month.

[00:35:15.970]
The concepts of a scene has been around for some time

[00:35:19.040]
in our desktop solutions.

[00:35:22.330]
When available, it will act as a 3D bookmark allowing you

[00:35:26.910]
to easily navigate back to the same view of the data in 3D.

[00:35:32.640]
And at the project level, which means they never get lost

[00:35:37.490]
in the history of the project as can happen

[00:35:40.810]
with the commenting your thousands of revisions for example.

[00:35:47.060]
For instance, you can ping and share scenes on the project

[00:35:52.070]
that are more important than others for example,

[00:35:56.020]
such as those ones that you have done during a peer review

[00:36:01.790]
process that for example mean a radical concept changing.

[00:36:13.250]
And finally, the history tab where you can follow

[00:36:19.390]
the revisions history and details.

[00:36:25.045]
Either way, you do that through this color code graph

[00:36:29.760]
that illustrate branches and project styles for example.

[00:36:36.930]
You can also use this tab to access the latest comments

[00:36:40.050]
and the discussion track in our peer review process

[00:36:49.510]
and return to the 3D web visualization

[00:36:53.600]
through the thumbnails when needed.

[00:37:01.410]
Sweet, so let’s do another tool here in WebVis.

[00:37:09.530]
We have introduced here a huge amount of functionality

[00:37:12.680]
over the last few months in web visualization tool.

[00:37:17.550]
And functionality that support will allow you to run

[00:37:24.330]
an enhanced peer review process for example.

[00:37:27.890]
Things like easily navigate through the time

[00:37:31.040]
and step through older versions of your project

[00:37:35.460]
to understand changes.

[00:37:38.610]
Access the project history

[00:37:41.320]
through these drop down list here.

[00:37:47.340]
So in case you are assessing and changing between revisions,

[00:37:53.510]
looking at the scene or a comment can easily navigate

[00:37:57.350]
through the project history to understand

[00:38:00.230]
the 3D point of view.

[00:38:06.700]
Another interesting things you can zoom into a specific 3D

[00:38:11.250]
object to find exactly what you want when you have

[00:38:15.550]
large project with lots of data for example.

[00:38:24.070]
The WebVis project tree works in a really similar way

[00:38:26.990]
to Leapfrog tree.

[00:38:28.780]
Things like multi-select, drag and drop,

[00:38:37.270]
also some object properties and filter data.

[00:38:48.270]
Scales points and do whole bays on bells.

[00:38:54.690]
The possibility of measure in 3D to a better understanding

[00:38:58.840]
of the size and scale of a project.

[00:39:05.530]
You can control the vertical configuration

[00:39:09.861]
through this panel here where you can also find

[00:39:14.470]
screen grade, compass and access via the settings panel.

[00:39:25.460]
All these elements can help you try to steer the assessment.

[00:39:33.870]
Important to mention again that while it is possible

[00:39:37.310]
and it gives you some additional tools,

[00:39:39.770]
I don’t recommend running 100% of the peer review process

[00:39:43.270]
in Leapfrog alone, there are many useful functions

[00:39:47.190]
within Leapfrog which can be a great help however,

[00:39:51.140]
if you have access rate, do as much as you can

[00:39:54.500]
within Central as there are clear benefits to this approach

[00:39:58.470]
such as no ability to process or edit anything via WebVis

[00:40:03.740]
ensuring that any updates or changes needed will not be done

[00:40:08.580]
by the reviewer but by the project owner.

[00:40:12.980]
I would mention also the documentation and the audit trail.

[00:40:17.540]
Cool, sure thing there’s more about peer review to discuss

[00:40:21.840]
and show but this is basically

[00:40:24.040]
what we prepared for you today.

[00:40:26.480]
So, we will jump to the presentation again

[00:40:29.730]
to finalize our webinar.

[00:40:34.440]
So in summary, we can say Central allows you to set

[00:40:38.770]
and enhance peer review process through

[00:40:41.280]
the following points.

[00:40:44.200]
An audit trail of both technical and management changes.

[00:40:49.700]
Also an intuitive, seamless and efficient process

[00:40:54.330]
really ease to use.

[00:40:58.840]
A time-saver and leave report of the decisions

[00:41:02.660]
and documentation is the key so,

[00:41:04.660]
a cloud based solution can be really beneficial here,

[00:41:08.680]
which implies an effective system to communicate remotely.

[00:41:15.530]
And why not through a continuous improvement process,

[00:41:19.200]
that address consistency to your procedures.

[00:41:22.690]
If your modeling process is dynamic and integrated,

[00:41:26.150]
why does your decision track can’t be?

[00:41:33.930]
And set an active collaboration environment,

[00:41:36.540]
so you can share the decision making process

[00:41:39.730]
and also share the responsibility.

[00:41:43.291]
Again, this is a good lease, right?

[00:41:47.730]
I would like to invite all of you to dig a little bit deeper

[00:41:51.860]
into the way you have been dealing

[00:41:53.810]
with your peer review process.

[00:41:56.130]
Think about that and get back to us with your thoughts

[00:42:01.340]
so we can run dedicated sessions for you and for your team

[00:42:05.980]
of course, and discuss your workflows

[00:42:08.450]
in a more comprehensive manner.

[00:42:13.430]
Sweet.

[00:42:18.820]
As the last thing from my side, I also invite you to get

[00:42:22.450]
some complimentary webinar content to what we presented

[00:42:26.550]
today such as the examples below.

[00:42:30.650]
Drill hold data tips for Leapfrog.

[00:42:38.040]
Integrating geophysics into your 3D model.

[00:42:44.350]
And learn Q&amp;A analysis with Leapfrog Edge.

[00:42:51.270]
You can find these in all their Technical Tuesday series

[00:42:54.830]
content on our how to guides and on demand visual space

[00:42:58.620]
in our website.

[00:43:00.960]
I will now hand back to Jacob to close this webinar.

[00:43:05.220]
Thank you very much, bye.

[00:43:11.640]
<v Jacob>Thank you, Antonio, that was great.</v>

[00:43:14.360]
Just a reminder that you are all invited to our future

[00:43:17.060]
Technical Tuesday workshops which we run monthly.

[00:43:20.710]
We also conduct open trainings for our products and systems

[00:43:23.980]
regularly so please let us know if you are interested.

[00:43:27.970]
Our recording of this session will be sent out

[00:43:29.750]
to those who registered and will also be available on demand

[00:43:33.050]
through our website.

[00:43:34.630]
Please feel free to share this with anyone else

[00:43:36.860]
who might be interested.

[00:43:41.280]
These are our offices around the world.

[00:43:44.460]
For more information about Central or guidance

[00:43:47.110]
with what we’ve presented to you today,

[00:43:49.250]
please contact us by email at [email protected].

[00:43:57.170]
Thank you so much for making the time to listen to us today.

[00:44:00.340]
We hope you found the discussion about the peer review

[00:44:02.670]
process and possible applications of Central interesting.

[00:44:06.470]
We believe that the greater your understanding of the tools

[00:44:08.950]
you have available, the more value you can get from them,

[00:44:11.980]
knowing the best context for their use.

[00:44:14.640]
Please call on us to help you achieve your organizational

[00:44:17.120]
goals, see you around.