0:02
Good morning and good afternoon.
0:03
My name is Anamora.
0:04
I’m a part of the Cohesive marketing team and I’ll be assisting the team today with the webinar as moderator.
0:10
We will give it another 30 to 60 seconds to allow all the attendees to join us on this call.
0:30
Great, I think we can start.
0:31
Hi everyone and welcome to our webinar on deploying mass and disconnected environments.
0:36
Before we start, I would just like to highlight some administrative tasks.
0:41
Note that this webinar will be recorded and distributed post webinar.
0:44
All the attendees are currently set to listen only mode, but feel free to post any questions or comments in the chat or question box located in the top right hand corner of your screen.
0:53
We will address all of these at the end of the webinar.
0:56
Should you have any technical questions or problems, please log it with the go to webinar technical team in the form of a question mark or help section on the panel itself.
1:06
Before we dive in, let me briefly introduce Cohesive.
1:10
We are leading service provider and systems integrator for IBM Maximo, helping organizations maximize their asset investments through improved efficiency, extended asset life and reduced risk.
1:22
Our expertise spans implementation, upgrades and digital transformation, ensuring sustained success for US intensive industries.
1:30
In today’s session, we’ll explore what it takes to seamlessly transform 7 independent maximum environments into a unified global platform without downtime and without data loss.
1:40
To kick things off, let me hand it over to our first speaker who will guide us through this, through this discussion.
1:46
Martin.
1:50
Yes, my name is Martin.
1:52
I work with the standard drilling as you can see here, the images a few years ago, but still looking good.
2:02
I’m the project manager shotgun for for our project here that we’re about to to show you.
2:12
I’ll hand over to Andrew from Gracie.
2:16
Thank you, Martin.
2:17
Good morning.
2:18
Good afternoon, everyone.
2:19
My name is Andrew Carey.
2:21
I’m the Enterprise Asset Management Director at Cohesive and I worked closely with Martin and his team in a senior business sponsor capacity on this project.
2:32
Martin is going to take us through a little day in the life of Stena and a quick introduction before we move into the details of the project itself.
2:40
Martin, thank you.
2:43
So this is short video of how life is on board one of our units.
2:50
Typical working period offshore.
2:55
You, you don’t use a car to commute.
2:57
You take the helicopter of course.
2:59
And as you can see, there’s people making the food for you, people cleaning the cabin.
3:08
There’s all sorts of it’s like a mini town basically working offshore and you can see here is a variety of different job jobs going on at the same time day or night on on the units.
3:27
So it’s a 24/7 operation.
3:30
This is an image showing the head office and the main entrance in Aberdeen.
3:41
So currently we are operating 6 offshore units throughout the world.
3:50
We kind of move around quite a bit and it’s all over the the globe.
3:58
We’ve been in Asia, Europe, US, South America, yeah, pretty much all over the place.
4:06
And, and here you can see all the rigs presented, 5 drill ships and 1 semi sub drilling rigs.
4:24
So this this slider or this animation will show you typical drill ship.
4:31
You can see the this data above and below around the ship.
4:38
Basically the capacity, how much or what’s water depth, how much, what depths can we operate in etcetera.
4:48
But it’s basically you can see at the hook load capacity that’s the limiting factor for how how long of a drill pipe you can have underneath the the rig and how, how far you can drill into the off basically.
5:02
So this is something we’re looking at in standard drilling to to upgrade at present to increase the capacity so we can go even deeper and further out offshore for for our operations.
5:18
Yeah, as you can see, it’s a fairly big unit over 220 meters long and 45 meters wide for the for the eight I think it was.
5:31
But yeah, like a minute out.
5:39
So this brings us to to this project and and what, what we needed to do and and why etcetera.
5:49
So we had 6 units across the globe, all operating with limited connectivity and the, the enterprise asset management system or the maintenance system that we did have before was limited in, in what you could do with regards to connectivity, etcetera.
6:17
So we need a top credit to enable more, facilitate more connectivity towards our own systems internally, but also external systems.
6:35
And that proved to be quite a challenge in in our our offshore marine environment as you can see here.
6:45
But yeah, we’ve got there in the end.
6:47
So we’ll can take it to the next slide.
6:56
Thank.
6:56
Thank you, Martin.
6:58
Yeah.
6:58
So I’ll take us through the the main broad strokes of the of the project itself.
7:03
So in early 2024, Martin approached myself to to ask a very straightforward question, which was how on earth are they going to upgrade their seven distinct maximal instances to this new thing called the maximal Application Suite?
7:21
And in a completely honest and transparent fashion, I told Martin that I didn’t know because it was never been done before.
7:29
The application Suite was presenting some interests and challenges, not just for standard drilling, but for all maximal organizations.
7:37
For those that are aware, there’s a significant change in the technology that underpins Maximal, which was going to have a greater impact for organisations such as Standard that are running multiple maximal instances.
7:50
So in terms of that project, Johnny, the first thing that we did together was work on a proof of concept and the purpose of that proof of concept was to not just test if it was technically feasible, but ensure that it was the the right decision for standard from a financial and an operational standpoint.
8:09
The upgrade to the application suite was proven to be a very significant investment for standard drilling and they had to ensure that it was the right choice.
8:19
So I was very pleased when Martin approached me to to ask for an advisory capacity to assist with that.
8:26
The good news was that the business case and the technical feasibility study proved that there was a method for us to upgrade their solution not just from a technical standpoint, but also without having a detrimental impact on the operations of the business.
8:42
So the full implementation project started properly in earnest in October 2024.
8:49
We rolled out over quite an aggressive timeline going live in April of 2025.
8:56
And then since then we’ve been continuing to add enhancements and support standard across a variety of different initiatives.
9:06
Really pleased to say that the project went live on time and on budget with very, very little impact to the organization front end users.
9:17
So just a little bit of a reminder then in terms of what was the as is situation, so standard building, we’re running six, what we call remote instances in maximum.
9:29
So these are maximum instances that are installed locally on board each vessel.
9:34
And then in addition, there was 1 central instance of Maximal which was hosted on premise within Aberdeen’s network.
9:44
In order to keep these systems In Sync with each other and to overcome working in, you know, remote geographies which are exposed to high latency and low bandwidth.
9:56
Standard drilling were taking advantage of a cohesive proprietary tool called the Cdr, which is the cohesive Data Replication tool.
10:04
This allowed standard to work in disconnected environments and then replicate their information as and when the opportunity allowed.
10:13
They were running this on AMS SQL database.
10:17
So if we take a look at what that infrastructure looked like, we can see here in the purple box at the top, this is representative of the central instance, which is a complete snapshot.
10:28
It’s of maximum in its entirety.
10:31
And then each green box represented as one distinct vessel.
10:37
So on board the vessel, you would have a local maximum instance, a local database, and then the replication tool, the Cdr, would be showcasing a snapshot.
10:48
So basically think of it as one wedge of a pie so that we would only showcase information that was pertinent to that vessel or the postcard into the global overall that the global fleet.
10:59
And then each of those segments of π make up the entire maximum instance that’s represented in the purple box.
11:09
So, So what was it that made this particular project quite challenging?
11:14
So the first thing was that you’re talking about doing 7 simultaneous upgrades, not just one.
11:21
How on earth are we going to do that without having an impact on operations of the business?
11:26
As Martin clearly outlined earlier, the vessels are a 24 hour operation seven days a week.
11:33
They they can’t go offline, they can’t stop.
11:35
We can’t necessarily fly people out to perform an upgrade.
11:39
So we had to ensure that what we were delivering was going to have 0 downtime and zero data loss.
11:47
The other challenge for standard drilling was overcoming what could be perceived as a body out of the change of technology.
11:57
So Maximo 761 currently sits on typical Windows servers running a middleware such as web server or web logic.
12:06
And the application suite is a complete shift in architecture where we’re moving to red tap open shift containerization, which presented several challenges.
12:18
So for example, when we were starting to roll out the project, the actual footprint that was required for a maximum instance was far too large to be installed on a typical vessel.
12:29
This idea of a multi cluster environment.
12:31
Therefore we had to work with IBM and and expedite supportability for things such as single node open shift environments.
12:41
And then the final challenge for Stena was how do they learn this technology?
12:45
Once they’ve deployed this new technology, how can they ensure that they can support and maintain it?
12:50
So with the help of Cohesive with both knowledge and technology, we were able to to overcome these challenges and turn them into distinct competitive advantage for standard drilling.
13:04
So what we’re going to explore a little bit today is 2 technology tools that Cohesive brought to the table.
13:10
1 is the Cohesive Data utility tool or CDU for short.
13:15
The other is the Cohesive data replication tool that we mentioned briefly to help overcome the intellectual challenges or the the knowledge challenges.
13:26
Cohesive said, I’ve made a a good business choice in my mind to move from being an on premise solution into a hosted managed solution that’s hosted by Cohesive.
13:38
And therefore, they transferred that risk in terms of the knowledge and understanding required for the technology from themselves to Cohesive, which then allows them to focus on pushing other areas of innovation.
13:51
And then finally, as I said, to overcome the technology barriers that were found on board the vessels, we did a huge amount of learning and experience and training and dare I say, troubleshooting around the deployment of single node Openshift for maximum manage.
14:08
What that then meant in terms of the actual to be or what is known as is the the final state is the we’ve now got maximum application suite running on board each and every vessel.
14:23
We also took the opportunity to transfer the database type from Microsoft SQL Server to DB2.
14:29
That was both for policy reasons and for financial savings.
14:33
The central instance was moved from on premise into the keys of cloud.
14:39
The downtime that was impacted or that was felt by Stena was negligible.
14:43
I mean, we’re talking literally minutes of downtime from the actual cutover, which was predominantly just down to the time that it took to communicate that this system is down and new ones up.
14:55
And then it’s worth stressing that that due to the complexities of the project overall, there was a decision made that it was purely a technology upgrade.
15:04
We didn’t increase risk by introducing new functionality as part of that upgrade.
15:09
But Martin can talk us through the the road map that is currently in progress a little later in the presentation.
15:18
So if we were to take a little bit of a deep dive into those two bits of technology that are referred to the Cdr and the CDU.
15:27
So starting first with the Cohesive Data replication tool, what this is, is a tool that allows you to effectively use maximal in traditionally or traditional environments where previously it was just not possible.
15:41
As we know, Maximo typically requires access to a network or to the Internet and working deep sea or in certain remote geographies, it’s just impossible to have a stable connection.
15:55
And therefore, the Cohesive Data Replication tool allows you to implement a full, a full maximal suite in a local instance.
16:05
And then using the the tool and the the rules file, the engine there beneath it, you can determine your business rules to help manage data and keep multiple environments In Sync simultaneously.
16:20
Currently, the solution is used globally.
16:22
It’s been in the marketplace for well over a decade now.
16:25
And we’re very proud of the fact that we’ve got clients quite literally on every continent.
16:31
I think at last count we had not one, not 2, but three separate clients using the tool in Antarctica, which we’re very proud of.
16:42
Moving on to the second tool, and this was really critical.
16:45
This was the kind of the silver bullet in many ways that allowed us to perform this upgrade for Santa drilling is something called the Cohesive Beta Utility tool.
16:56
So a typical mass upgrade would see you take a clone of the maximal 76 instance.
17:02
You would then execute some form of mass upgrade on that and your mass system would be up and running.
17:08
But the challenges would be the time taken in between what happens to that data set from when you first take that initial cut of the database to then executing your goal line.
17:20
Often, you know, people have been involved in upgrades previously where you have to have a, you know, downtime where the system is unavailable to the users.
17:29
And then myself concluded, I’ve been involved where you then have a very panicked weekend where you’re working extremely hard to try and get the new system up and running as quickly as possible, normally over a weekend, normally working late evenings.
17:43
And then you’ve kind of got your fingers crossed open that come Monday morning, that upgrade is going to be successful and that you don’t have to roll back the system.
17:52
The CDU effectively takes all of that risk or in some ways all of that fun out of the upgrade.
17:59
So the CDU is a proprietary bit of software that we deploy alongside your existing maximum instance.
18:07
And then we point that towards you the the new mass instance.
18:11
And what it will do is it will effectively lessen for any transactional data during that cutover.
18:18
During that time which can last days, weeks or even months.
18:22
So you take your initial cut of the database, you push that through the typical mass upgrade path, you can perform business process improvements on top of the application.
18:33
You can even perform transformations and cleansing to the data as you move it from your existing system into the new system.
18:42
Because that system is effectively up and running and live, albeit nobody knows about it well ahead of your cutover point.
18:49
It takes all of the risk out of the the update itself.
18:54
Some of our clients previously have described this as a very boring and I think even Martin’s colleague described the upgrade for Stena themselves as very anti climatic because it does take all of that risk and the the kind of worrying concern out of it.
19:11
So what was that process overall then Pristena?
19:16
So the first thing that was kind of like a major hurdle, which we we probably don’t shout loud enough about was actually deploying mass itself on board the vessels.
19:25
So as we can see from the video at the top of the call, these are not geographies that are easy to get to.
19:34
We can’t just jump on a jump on a flight and then a helicopter land on the vessel, do an install and then get back home in time for dinner.
19:42
So therefore we have to do these things remotely.
19:45
Now, there’s the way that the mass solution wishes to be deployed made this really challenging.
19:53
So So we had to effectively build a dedicated tool which would allow us to deploy it in an automated air gapped manner.
20:02
So in cohesive, we built a specific suite of processes which allowed us to effectively physically send off a package to the vessel, have somebody locally plug it in and then the package would take care of itself and perform the full installation, ensuring that the right IP addresses and the right ports, etcetera were were all connected and opened in readiness.
20:27
It was a fantastic piece of work by our technical team which really helped us overcome the the biggest head scratch up on the project in terms of how we deployed that.
20:40
We effectively had the 76 instance and the application suite running in parallel for a short period of time.
20:48
So we can see an entire view here.
20:49
But if we were to dive into a bit more detail, starting in that top right hand corner, so we’ve seen this was the existing solution.
20:58
So the green box represents A vessel with the purple box representing the original central instance.
21:07
And there we can see that previously described process floor, that data flow where data flows from maximum onboard the vessel through the Cdr into the central maximum instance.
21:20
But when we deployed the CDU that would then listen for those transactional datas, sorry, that transactional data that has been sent from the vessel or from the central instance itself.
21:32
It would then migrate that into the newly created mass central instance, which was then moved to the keys of plant that was now operating on ADB 2 database.
21:45
And then a secondary Cdr network would then push that data out to those vessels where we had deployed and readiness for Go Live.
21:55
So typically that was just one way initially because nobody was using the new instances.
22:01
But if we look at that as a full view once more, so start on that bottom right hand corner, the vessel would flow from vessel data would flow from the bottom right.
22:10
It would then flow into the old central instance, which is highlighted in the purple box.
22:16
The CDU tool would then extract that data and then inject it into the new mass central instance, which is represented in the top left with that kind of Peach coloured box.
22:29
And then finally we push that data to to the vessel to give us a complete data flow.
22:35
Now we weren’t just doing this one time, but we were doing this six times in parallel.
22:39
And then therefore it becomes a fairly complex, but then I say straightforward flow of data to ensure that we were continually keeping these new instances fully up to date.
22:55
That allowed us to do full testing across functionality, integrations, etcetera, safe in the knowledge of knowing that it was going to work when we decided to to cut over.
23:06
So what did that cutover actually look like, look like then?
23:10
So as I said, it was rather boring and I mean that in the in the best possible sense.
23:15
So starting from the left hand side at a time which was convenient to stand drilling, stand up, advise us that they wish to take the central 76 instance down.
23:27
Since the cloud instance was already up, there was nothing that we had to do there other than to coordinate communication to the users and ensure that users couldn’t log into that old system and then just point them to the new the new instance.
23:42
And I think the biggest issue we had there was people had forgotten their passwords and then therefore we had to do some password resets.
23:48
That was about as challenging as the as the tickets initially were from a vessel perspective, it was a bit of kind of lather, rinse, repeat because both instances were up and running in parallel, albeit nobody was using the the mass instance.
24:05
We would notify that the vessels or this instance the 4th, we would advise them that the 76 instance would be coming down.
24:15
They would effectively stop using the system.
24:20
And then what we would do is instigate A replication path to push the data from 76 into central, central into mass, mass into remote mass.
24:31
And then the the users could log into the mass instance on board the vessel and see the work orders and the POS and etcetera that they’d be working on 7/6 just a few moments earlier.
24:43
And the, the service time time was the time taken to do one complete lap of replication, which was approximately 5 minutes.
24:51
And then we just repeated that for each of the vessels.
24:54
Stena had the opportunity where they could choose which vessels to bring online as and when.
25:00
And I think from memory, Martin can confirm a little laser that I think once we’ve done one or two vessels, we realized that everything was running very well.
25:08
We just chose to to do the rest there and then.
25:13
It was genuinely a massive success and when about as well as it could have, which we’re incredibly proud of in spite of that.
25:22
I mean, there was project challenges.
25:23
We live in the real world.
25:24
So we did hit some hurdles and typically the hurdles that you hit are the the really easy things that you don’t think about.
25:33
So these are this, this list is not exhaustive, but some of the typical challenges that we seem lack of direct network access to the vessels themselves.
25:43
We, we were not in control of where the vessels were operating.
25:46
Sometimes the vessels were operating either in a geography or pointing in a particular position direction, which meant that we physically could not access the the environments when we needed to kind of perform remote, remote working.
26:02
Because he’s a data replication tool, there was a serious amount of testing and development.
26:06
I had to go into that to ensure that it was going to be supportable from us.
26:10
And one of the things that we kind of stumbled across was the fact that we couldn’t use Cdr initially to to sync user accounts which are stored in Mongo DB.
26:21
So for those that are kind of more technically orientated, the way that the user licensing is handled inside application suite is different from traditional 761 because it caters not just for manage, but across the entire suite itself.
26:37
And therefore we had to overcome some challenges there that replication speeds were challenging where there were two and a half million attachments that we had to migrate as part of this project.
26:50
The fact that the second order Openshift cannot be duplicated at the M level.
26:56
And then just general connectivity performance during your initial deployment as we were sending database content back and forth.
27:03
But but thankfully then the continuous monitoring tools that we’ve got in place helped us to overcome that with as I say, there was some work going on on under the under the water line.
27:15
But in terms of the end user impact, they felt very little in terms of the impact for the business overall.
27:23
Martin, perhaps I can hand over to yourself and you can talk us through the the impact that the application suite has had.
27:35
Yeah.
27:36
So the as Andrews explained here was a a lot of new inventions and complex solutions that was developed during this project.
27:52
But as I said, you know there was a bit of an anti climax when we went live with the whole system.
27:59
The, the biggest challenge was basically users because we gave everybody the same user or the same password for all the users.
28:13
The biggest impact was rolling out, you know, tell people that you can now log into the new mass environment.
28:21
But we had to kind of tell the CEO and all the top level people to, to log in and change their passwords 1st and then the next level.
28:32
And then, you know, so hence why it took all, all those 5 minutes to roll out to the central instance.
28:40
If it wasn’t for that one, it would have taken still a second.
28:46
And then as another kind of comment, it’s usually the, the simple things you miss out and, and the same here, you know, we did all the things right with a complex or which Greece did most of the advanced stuff.
29:05
But it was one small issue where a copy paste error just threw everything on its on its site for about, I don’t know, 10-15 minutes.
29:16
But then, you know, quickly discovered what the issue was and then fixed it.
29:20
And then we were back on track.
29:22
But it just shows you, you tend to focus on the, on the complex stuff and then forget about the small simple stuff.
29:34
So Eric, you’re looking at the statement from our Chief Technical Officer, Graham Brunt.
29:42
He’s he’s looking at the new system as an open opener for a lot of other kind of it’s enabled us to to get access to a lot of new tools such as monitor health, etcetera.
30:01
Where we can, we can use the like utilize those functionalities to to assist us optimising the likes of maintenance against assets, etcetera.
30:12
So this is something that that we are kind of begin to well looking into at the moment.
30:22
Anyway to to, to try and find our use case and then develop to say this next statement here is from Stuart Guinness, our Chief Financial Officer.
30:38
He was really thrilled with the some of the development we we’ve been doing in, in the new system here where we’ve managed to take an old kind of monomatic system where you’re signing PDFs etcetera and sending them by e-mail for AFE approvals.
31:00
For example, in the procurement side of things where we just moved it all into maximum to the mass system and and made it automated by workflows and and user access.
31:18
So I think the IT was, it was a no brainer from us from our side.
31:26
Andrew mentioned before we did a proof of concept for the whole upgrade where we also looked at staying with 76 and we also looked at changing maximal altogether for for any other system out there.
31:43
But when you took everything into account, it was there was no discussion really.
31:51
The operating to mass was, was the logic choice for us, you know, if you want to stay on top of things for the, the technology and development.
32:05
So, yes, so this took us to Maximum World and we we well, Andrew listed for us the this upgrade project as a presentation at the maximum World.
32:21
And then all of a sudden we found ourselves up on stage receiving this award here.
32:27
So I think it was a big team effort, not just by, you know, us here at this presentation.
32:38
It was by all the subject matter experts whether winning stand up or the business sections in Stana and it was also all the kind of different sections within cohesive where people was involved in, in all of the various development phases.
32:58
So yeah, great, great achievement really.
33:03
Well, I didn’t really enjoy standing up the stage there, but I enjoyed the the T-shirt and the award ceremony afterwards.
33:14
I think the beers before the presentation helped as well.
33:20
Most likely, yes.
33:22
So yes.
33:23
So where, where does this take us?
33:25
So we’re now like more than six months into mass and we’ve kind of asked with every system because we were the first out and it was such a complex environment.
33:42
We’ve had to you know tweak the system here and there, fixed minor bugs, etcetera where we couldn’t anticipate its behaviour before we actually upgraded the system.
33:56
So we are now at the point where we’ve stopped at kind of the next phase of our development.
34:02
So we’ve said a key to to success with the work management for us is that the end user should have a as simple as possible system to to work with.
34:15
And.
34:15
And this was why we’ve chosen to, to develop the mass mobile solution for work management so that we can give them the opportunity to have a mobile phone or a tablet and complete their work there.
34:33
And then as it happens, rather than maybe pick seven different jobs, go and do 7 jobs.
34:40
Remember 6 of them or five of them or whatever when they are back at the computer or punching it into to the desktop option of the mass.
34:51
So clean data.
34:53
The key to that for us is it should be as simple as possible to, to put the data in us.
35:01
And when it happens there’s also in in the offshore environment pretty much every job out there is in conjunction with an electronic permit or not electronic public with a permit.
35:21
And today we operate people based permit work system and isolation etcetera.
35:28
And because of Maximo having the whole full HSE suite, we decided let’s do a proof of concept here and see, you know, see where it takes us.
35:40
So we, we looked at 4-5 different options, well known electronic permit system providers and then not just looking at cost, but also, you know, it’s a piece of to use.
35:57
What’s it for the look like for the, for the end user, etcetera.
36:01
And, and what we came up with was the obvious choice or just keep it in in masks because everything is there already, the connections.
36:16
You can expand it further if you want to or you can just keep it as is, but you have all the capabilities within one system and easily tied in to each other work orders or tied into isolation or tied into electronic products, etcetera.
36:34
So this is what we’re what we’re developing now.
36:40
And then what we hear now is that HSE is actually coming out as a mobile solution in mobile 9.2 I believe.
36:49
And that’s probably what we’re going to put our eyes on next, once we’re happy with the, the mobile solution and the electronic format solution to further develop and, and make it more user friendly for the, for the end user.
37:11
So there’s a lot of lot of things up with with mods, we we find that there’s so much to keep up with all the things you want to do.
37:27
So yeah, those are the important bits anyway, for now.
37:34
Thanks.
37:37
Yeah.
37:37
Yeah.
37:38
Excellent.
37:38
Thank you, Martin.
37:39
I think it’s, it’s probably important to stress that Steiner’s journey with Maximal started in 20, late 2018 and then roll out 2019.
37:51
So we’re now 6-7 years into the Maximal journey and Stena Drilling continue to expand the footprint, increase the maturity, not just of maximum of their asset management practices in a continuous improvement cycle.
38:05
And I’m personally very proud of the fact that I’ve been involved since the beginning, although Martin’s realized that there’s bigger and better people that can work on his projects now.
38:15
So I’m getting relegated at some points.
38:17
But so hold on by my fingertips, Martin.
38:22
I mean, a lot of this comes out to the the One Team 1 mission approach, which has definitely been absolutely fundamental to the relationship.
38:30
It’s always been viewed as just one team with a common, common mission in mind and definitely a pleasure to work with an organization such as Stena Drilling.
38:40
That brings us to the end of the presentation with regards to the project delivery.
38:45
Anna, is there any questions that we’ve had in the chat that you’d like to like us to tackle?
38:52
Great.
38:52
Yeah, thank you so much for that session.
38:55
We looks like we do have a little time for some questions.
38:59
So if you have any questions and haven’t done so already, please go ahead and enter them in the chat or question box in the top right hand corner of your screen.
39:07
And it looks like we do have our first question, which is was the upgrade really 0 downtime and were there any issues with data loss?
39:18
Yes, for if I can answer this one, there was absolutely no downtime at all.
39:26
The downtime, the end user experience was as I talked about earlier that we kind of held back on releasing the the new URL to some of the users because we wanted a certain group of people to log in, change their passwords 1st and then we could allow the the following set of people to log in.
39:48
But yeah, no loss of of any of the the work related data or PO data etcetera at all.
40:02
Excellent.
40:02
Just just to add to that in terms of a lot of the testing goes in to the project well before go live so that the fact that we’ve got everything in place.
40:14
In terms of environments, the transactional data that’s flowing, the testing threads, highly unlikely that we’re going to lose any data.
40:24
Really, really good question though.
40:26
The CDU tool is a very mature solution which has been in the marketplace for over 10 years now.
40:31
So it’s, it’s well, there’s the maximum upgrades I think you can add to that as well on connection to the likes of or integration thought about the systems those were all taken care of prior Go light as in Go light for end use of.
40:52
So because it was upgraded the way it was, we had a mass instance running in parallel to 761.
41:00
We could take care of all the integrations into mass before we went light.
41:06
So it was already there seeing live data in the mass system where we were using 76 for creating new work orders, creating new POS.
41:18
So on the day of switchover we don’t have to worry about that segment of of the domain.
41:27
Great, thank you.
41:29
Another question is did the users have to receive training for the new system?
41:38
I can answer that one as well.
41:41
So the new system, because we had it set up the way we had, we had test environment dev environments up and running for quite a while before go live.
41:55
We could allow users to go into the test environment and and look around just to familiarize them with the new looks of things, what flow and and how everything was operated pretty much the same as 761.
42:16
So there was no, no major change.
42:18
It was just finding the buttons basically in the new system.
42:23
So no, no training worthwhile, you know, mentioning got it.
42:34
Thank you.
42:35
Another question, was the CDU created specifically for Stena or can this be used by any organization?
42:44
Yeah, good question, Anna.
42:46
So no, the the CDU too, as I said has been in the marketplace for over 10 years now.
42:52
I think the first earliest maximal version that we’ve upgraded using that solution is version 4, right the way through each interim maximal state since then with obviously now multiple case studies for using it to the application suite.
43:11
We’ve had several clients use it multiple times across their journey.
43:17
So it’s yeah, it’s a tried and tested solution which is which is available not just for remote instances such as standard drilling, but also for, you know, your fully connected LAN based maximum implementations also.
43:38
All right, awesome.
43:39
Thank you both and with and that is all the time that we have for today.
43:44
So any questions that were unanswered, we’ll make sure to get back to you via e-mail.
43:49
And then with that we can conclude our webinar.
43:51
I want to thank our speakers for joining us today as well as you our attendees for listening today.
43:56
We have additional information available on our website in the form of blog posts, articles, case studies, and even brochures.
44:03
If you want to really reach out and discuss your strategic path forward, please reach out.
44:07
You can also reach out via our website and that is a wrap for today’s webinar.
44:12
A short survey will be sent to you in a follow up e-mail and we would really appreciate it if you could take a minute to complete it.
44:18
Your feedback helps us improve and choose the topics that matter most to you.
44:22
Martin Andrew, thank you again and I wish everyone a great day.
44:31
Thank you.
Partner with the market-leading IBM Maximo service provider and systems integrator.