WEBVTT

00:00:00.000 --> 00:00:03.650 align:middle line:90%
[MUSIC PLAYING]

00:00:03.650 --> 00:00:07.530 align:middle line:84%
Everything about the front
end of T minus 24 months

00:00:07.530 --> 00:00:10.520 align:middle line:84%
to T minus 12,
that's really where

00:00:10.520 --> 00:00:13.220 align:middle line:84%
we're thinking about
defining the scope

00:00:13.220 --> 00:00:16.530 align:middle line:84%
and actually understanding
what we're going to do.

00:00:16.530 --> 00:00:18.680 align:middle line:84%
And usually, there'll
be too much scope.

00:00:18.680 --> 00:00:22.460 align:middle line:84%
So it's, how do we actually
go from maybe 3x scope

00:00:22.460 --> 00:00:26.780 align:middle line:84%
to actually just what we can
achieve in that 45-day window?

00:00:26.780 --> 00:00:28.210 align:middle line:84%
And then from that
point on, we're

00:00:28.210 --> 00:00:30.050 align:middle line:84%
just about making sure
we get the contract.

00:00:30.050 --> 00:00:31.910 align:middle line:90%
Is the supply chain engaged?

00:00:31.910 --> 00:00:33.620 align:middle line:90%
Then we get to the actual event.

00:00:33.620 --> 00:00:37.460 align:middle line:84%
What is maybe 100 people
maintenance in an operations

00:00:37.460 --> 00:00:39.920 align:middle line:84%
perspective to something
in the order that

00:00:39.920 --> 00:00:43.550 align:middle line:84%
can be on a major
turnaround event,

00:00:43.550 --> 00:00:47.240 align:middle line:84%
4,000 people working on that
facility at any point in time?

00:00:47.240 --> 00:00:49.550 align:middle line:84%
If you look at any
lessons learned

00:00:49.550 --> 00:00:53.510 align:middle line:84%
or review post an
event, they all

00:00:53.510 --> 00:00:56.270 align:middle line:84%
come up with the same
premise, in the fact

00:00:56.270 --> 00:01:01.320 align:middle line:84%
that 50% of organizations still
don't manage scope effectively.

00:01:01.320 --> 00:01:05.209 align:middle line:84%
And when we think
about a turnaround,

00:01:05.209 --> 00:01:07.430 align:middle line:84%
a turnaround is something
that has to happen.

00:01:07.430 --> 00:01:11.630 align:middle line:84%
So executive management on
board know this thing happens.

00:01:11.630 --> 00:01:14.300 align:middle line:84%
They know that you have
to take an asset offline

00:01:14.300 --> 00:01:16.190 align:middle line:90%
to do enhanced maintenance.

00:01:16.190 --> 00:01:19.150 align:middle line:84%
What they want is
predictability about that.

00:01:19.150 --> 00:01:22.040 align:middle line:84%
And the whole thing about
understanding the scope

00:01:22.040 --> 00:01:24.590 align:middle line:84%
and defining it to the
nth degree and planning it

00:01:24.590 --> 00:01:29.210 align:middle line:84%
is so that when you go
into a 45-day turnaround,

00:01:29.210 --> 00:01:31.460 align:middle line:90%
it's delivered in 45 days.

00:01:31.460 --> 00:01:32.810 align:middle line:90%
And it costs x.

00:01:32.810 --> 00:01:34.550 align:middle line:90%
And there's no loss of life.

00:01:34.550 --> 00:01:36.500 align:middle line:90%
That's what the board expect.

00:01:36.500 --> 00:01:41.450 align:middle line:84%
That's what defining the scope
actually drives you towards.

00:01:41.450 --> 00:01:43.880 align:middle line:84%
We're still in a
very siloed world.

00:01:43.880 --> 00:01:47.630 align:middle line:84%
So scope is defined and
captured maybe in one tool,

00:01:47.630 --> 00:01:49.580 align:middle line:90%
engineering in another.

00:01:49.580 --> 00:01:53.820 align:middle line:84%
We've got the operations that
are working in their own tool.

00:01:53.820 --> 00:01:56.570 align:middle line:84%
There can be upwards of
15 different entities

00:01:56.570 --> 00:02:00.290 align:middle line:84%
all trying to work in
any major turnaround.

00:02:00.290 --> 00:02:03.890 align:middle line:84%
How do we move away
from manumatic to a more

00:02:03.890 --> 00:02:08.000 align:middle line:84%
automated subscription-based
type approach to life?

00:02:08.000 --> 00:02:12.230 align:middle line:84%
And when we think about scope,
the scope isn't the turnaround.

00:02:12.230 --> 00:02:17.060 align:middle line:84%
There can be up to 2 and
1/2, 3,000 elements that

00:02:17.060 --> 00:02:19.280 align:middle line:90%
make up that one turnaround.

00:02:19.280 --> 00:02:22.430 align:middle line:84%
It's that ability to actually
flow that information

00:02:22.430 --> 00:02:24.575 align:middle line:84%
seamlessly around
an organization.

00:02:24.575 --> 00:02:26.450 align:middle line:90%
We want to capture information.

00:02:26.450 --> 00:02:28.100 align:middle line:84%
But we want, too,
to challenge it.

00:02:28.100 --> 00:02:31.790 align:middle line:84%
So from an Oracle
perspective, we actually

00:02:31.790 --> 00:02:34.550 align:middle line:84%
deliver an integrated
solution that

00:02:34.550 --> 00:02:40.580 align:middle line:84%
allows you to think about scope,
cost, risk, schedule, safety,

00:02:40.580 --> 00:02:45.770 align:middle line:84%
quality, handover, all in
one integrated platform where

00:02:45.770 --> 00:02:51.440 align:middle line:84%
people subscribe to that data,
where they can publish data.

00:02:51.440 --> 00:02:54.920 align:middle line:84%
We deliver a single
toolset that supports

00:02:54.920 --> 00:02:57.680 align:middle line:84%
all of those elements
I've just talked about.

00:02:57.680 --> 00:03:02.230 align:middle line:90%
[MUSIC PLAYING]

00:03:02.230 --> 00:03:03.872 align:middle line:90%