LC20: The Latest on the New HSE Release

The following automated transcription is from our 2020 Lunchcast Series. For a copy of the PowerPoint presentation, please contact us.

Welcome everyone. Thanks for joining us for lunch today, We hope everyone’s doing well. I ‘m Kat Pullen the marketing coordinator for Ontracks and your Maitre D for today. Our lunch special is a look at the latest maximal HSE release. are informal lunch cast events are held every Thursday and we have invited several IBM folks and members of our team to discuss Maximo topics.

The phone lines are muted throughout the event. If you have a question, please enter it into the question box below and we will answer them toward the end of the meeting.

This lunch guest is being recorded and a link will be made available shortly after the meeting.

Your servers today are Russel B and Kyle Harding of IBM.

Russell is an STS Sim and lead Product Architect with IBM. Many of you know, Russell, as he has over 20 years of experience with maximum and leads, but the oil and gas and the HSC product teams. Kyle, is having connection issues, hopefully, we’ll be able to get him here momentarily. He is a fixture in the IBM world. And he is a Senior Product Manager designer, and will of is also at an IBM architect.

Russell will go over the presentation first, and then we’ll turn it over to Kyle to give a demonstration.

Again, we invite you to type your questions into the Q and A box anytime, and we will answer them at the end of the session. And with that, I will go ahead and turn this over to Kyle.

Here we go. So, lunch for today is Maximo HSA manager, and if you’re listening in from the UK, it’ll be, it’ll be done here.

So, I’m going to do the first part of this presentation.

So, here is the revised Business Process map, for Picture see 7 6 2. Just want to use this to highlight the main differences from a, from a process perspective. So, on the left-hand side, under Operations Management, the main chain cherished the introduction of operates rounds. So, what we’ve done to support operates around just we’ve. we’ve leveraged the new inspection capability for managing inspection forms That creates an inspection results that was always designed from the outset with the intention that supports and operates around use case.

So, this has been our opportunity to, to start to leverage that capability in HSE on LinkedIn today.

What we’ve done is, like, since the operator log capability, so, from a, uh, from an upright so log, you can link into the inspection capability.

And you could reference multiple rounds, you can create, say, rounds from a form within the operator log. You can also do have a note facility.

Sorry, if you just want to record a note about around that you don’t want to connect into an inspection result. You can also do that. The main intention is to be able to use the Operates arounds.

The Inspection capability to For Your Operates arounds.

So, that’s, uh, a change we’ve been looking to make for a while. Knowing that capability was, was coming for. I think because we start to, you start to see, has got the disconnected inspection capability going forward that that, that that process is going to become an important one within the, within the product. From a control of work perspective, we’ve created a new class of permit called Code Access Permit. So so feedback from customers has been that for some types of permit those around.

So the limitation of access inspection related permits were, the work is not necessarily invitees, if someone needs to permission to go in, be in a certain area, you don’t necessarily need the full extent of the of the permit to work process.

So we’ve taking that feedback from multiple customers over awhile and introduce the new access permit class, which is which is supporting that use case. And it offers a, a, a simplified process, can be linked into, permits, permits to work and isolation certificates as well, If you need to, but it’s a standalone, the access time process is a simplified one.

Alongside that, we’ve also introduced a lock management capability, saw our capabilities in this area.

From a, from a permit to work perspective had been around being able to reference semester, Lockbox within your, within your isolations and record.

The record locks used on, on individualized solutions been feet feedback from customers.

This area for a while, about being able to actually manage the, the locks themselves and the individual locks within a, within a box. And so, we have to support this. We introduced a new dedicated application for lock lock management.

So, you can manage this as master locks and you can also manage any type of lock within this, within this, this this this new application as well, and it’s closely linked to into the permit to work in isolation management capability.

Also, new capability that we’ve introduced tied into locations as well to assist with the management of lock open lock close, closed valves, and it’s a mechanism that will offers opportunities to also manage casio type.

Lock locking devices as well.

So finally, from a sub process map perspective, we have the training and competency management, So we’ve.

Today significant amounts of capability around training, I know cover that in more detail. But the for some time that’s been highlighted to us as an area where we could improve our process around, around competency management, to introduce training capability.

Training.

For example, China Against Nemo say it was it was a much higher highlighted requirement by customers.

So those that sort of say, the four major changes from a from a process perspective just looked starts to look a little bit more detail about the the features themselves.

So, access permits, as I’ve mentioned, mentioned this new class of permits to support access control.

one of the things we’ve done with the access permits is incorporate the new new training capability as well to highlight. For example, if someone accessing the site needs a certain training capability all must have completed some in some induction training. We’ve also taken the opportunity to us, as well as the work we’ve done around, operates around. This is an area where we’ve integrated inspection, form and inspection result capability, so we’ve actually done that in two different places. So you can reference an inspection, sorry, if the access purposes and supports of an inspection. You could reference the actual inspection record.

Or if you just wanted to use an inspection maybe to record the the results of a site inspection or potentially a server type a tailgate talk, then you could use the inspection capability to, to do that.

As a supplement to the capability within the access permits application itself, we actually remove the full toolbox talk capability that you get in the permits, worker, or isolation certificate applications just to sort of as part of simplifying the overall process flow of the of the access permits. So significant amounts of capability coming in there around the, around the access permits.

We made some small changes to try to bypass management, being able to reference permits on on the bypass record.

And also, if a bypass was it was associated with a, with a lock, then you can reference the lock and also indicate the state of the lock as well on the Bikes management application.

There is a with a new clone of craft so previously we use the, the asked the box crafts application. We make no changes to it, but they, as we introduce training than the craft, is the area within Maximo the, which is sort of represents a role.

This is an opportunity to identify training requirements by role, So we’ve introduced a clone of crafts, so that we can add in the, the ability to support training requirements, Spy Craft, and also by, because of the structure of crafts with skill levels.

You can identify training, but it’s by craft on skill level.

On the incident side of it.

So substantial feedback in this area for awhile and seeing customers present at conferences. Now, a couple of times in the Cam Margaret, we’ve sort of had discussion since 18 people presenting the approaches to managing multiple incidents on the same incident. So Kyle is going to cover some of this in his demo, so go into too much detail here.

But it’s a feedback area of being able to handle multiple events associated with a single incident, and also multiple injuries or illnesses outcomes.

And we’ve also some small amounts of workaround claim and damage management on an incidence as well, as well as updating our osha reports. So, Kiowa, we’ll go into some more information, and into more detail, and give you more information in that area, on the investigation side of things.

So, we, we support five Whys, root cause analysis method, out of the box, and we’ve had feedback for awhile now, about being able to support a structured cause analysis, technique, systemic, cause analysis, Scott’s Scott charts. Some, some, some customers will call them. So, we sort of just generically refer to that as a structure cause analysis, so a lot of work being done in that area to to support that capability. I think we’ve got something interesting to show you. Their car is going to demo that capability.

We, we also have taken the opportunity to do a bit more with the filmmaker on the Investigation.

So, one of the things that this will now allow us to do is to, is to be able to better support the overall RCM process. So, so, previously, the use case for, for me, could capabilities on the investigation. So, if you found a new failure mode on an investigation, you want you to record it, you could do that. So, what we’ve done is use that structure, extended it, put more information, to allow you to manage a study, and also put multiple locations and assets on the.

against each row of the, of the, of the failure mode on the investigation.

So, that sort of provide say, a focal point, say, if you had to wants to pull together information, the, the capability that is the in the fight, the RCM capability that’s in, the location assets, applications on the failure analysis tab, to go into the detail of a dictates how that, for me, style analysis that, Now, what you can do is to pull multiple different locations and donuts to, if you wanted to mix locations and assets, You can do that on the investigation record and the, the, for me catch up. So, you can not think is a good step forward and in our overall support for, for RCM.

We’ll also add it as part of our work on the supporting ISO 14224. So from oil and gas perspective, where the customers get that data, we’ve been looking at supporting the latest version of the Standard 2016. So we’ve also taken the opportunity to, one of the gaps was around being able to put the support system condition as defined in the. In the ISO.

So there’s a whole, there’s a new section on the investigation which supports the ISO 4000 to 4 system condition Probably worth mentioning just for oil and gas customers, that everything I’m covering here in HSE is also in oil and gas.

They, the difference is with oil and gas, SEC, you got the ISO 14224, that date.

So, in that case, we’re supporting the 20 16 Version 4 for this release.

From an isolation management perspective, we, one of the things that was missed when this was first released, was the ability to create a lockout, a lockout tagout template, that you had on the permits work applications. So we’ve, we’ve added that in. We’ve added in the sanctioned support for the sanction for test process. Sets of changes that support the work we’ve done around lock management, to be able to support Lockbox is also the Tide permit use case, which is an important one from a locked perspective. So a colleague Francisco has been heavily involved in that. Those of you wrote.

But Calgary Base Will, will, will, will, will know Francisco from some of his visits to Calgary, where years picked up some good, good, good information that led to the work on Log Management area. We’ve also been done some of the workaround, tidying up some of the rules around isolation of progress status.

From a location perspective, we’ve added lock state fields or actions to support the lock open, closed use case. We’ve added in the definition of a safety and environmental critical element group. So, and, and bury a reference fields so, you can link location, Not just you can, you can associate location.

Not just with its its type of safety critical element, but the group it belongs to run and barrier as well.

We’ve also introduced some additional fields to identify all operating states and barrier states, so, sort of another step forward and the ability to better what support the management of a barrier status and operating status. And be able to link that in, as we start to introduce sort of to the schematic capability going forward, the ability to overlay that sort of information on, say, for example, a Paean ID. So the data structures that have been added now to be able to support that.

We then have the New Lock Management application. So a standalone application written interface to multiple other applications are so as I’ve covered.

As we go to the next slide, While Nemo say, we couldn’t have done training without adding IMO say of sewed it so many times. So that was one of our priorities to try and make sure that we we we met the requirements, and also, we make the safety critical element just a small change on on MFC there.

An interesting area of feedback that was, that was that we’ve heard from customers as the as I sort of saw, the work we’re doing around inspections was, was to be able to, in the future, Link K inspection capability to pre start Safety review, and most C So, it didn’t quite have time to get that done. But that’s something that we’ll, we’ll look out for future releases on the permits and certificate types. We’ve got to training associates, training capability with the type of permanent now, and it will also support the definition of access permits, So, you’ve got some control over where, when you can, you can use use access permits. On the people application, we have added there, again, training capable, let’s say. We’ve also added the extended the existing authorization capability to cover lock management.

Permit to work there, quite a number of, uh, of small changes individually, but sort of generally significant changes, in terms of functionality and process flow. Flexibility, so a lot of work been done around, around this area, sort of incremental work. So one of the requirements that we’ve heard was almost on a permanent.

this multiple issue, issued multiple times to be able to add the, the, the reference, the different tissue numbers.

So we’ve added that sanction for test process, the rules around work, complete another area feedback river, looked at that and tied it up some of the work, the way that the work, complete rules. We’ve added in log management fields, like isolation managed. We’ve changed the isolation in progress rules, and we’ve also simplified, again, based on customer feedback. And make my lower optional some of the rules around closure and constellation of permits. We’ve also added a safety critical reference failed, so it’s been a good opportunity to pick up quite a lot of areas of feedback from customers that are around, around permits work.

On the regulatory compliance application, we had that much feedback about being able to support revision, we’ve introduced, that’s also the ability to be able to classify regulation and have an associated specification top. So, for example, if you want to introduce more detail in about a permanent regulation, say, for example, you’re using it as a performance to model performance standards, as many customers do, then you can put in the specification, nitrogen attributes associated with a classification. We’ve also made a couple of small changes.

I did the technical Authority reference for the, as well as an owner, for the for the regulation, and we, we’ve added certifications on the way use capabilities, that that, that, that’s been the best on the on the previous release.

We’ve also added the, on, on the risk matrix application, we’ve introduced, risk, risk, matrix revision. one of the things we have been looking at doing was also looking at the risk assessment revision. We sort of just felt probably needed some more customer discussion before we went too far with that. So that’s something that’s in our sites.

But for this release, we focused on on managing the coefficient of the if the risk matrix.

Training management as I’ve referred to. And I’ve got a slide just to show you before I finish my section shortly. And then on work or to trucking we’ve put the same equipment condition. We usually mirror on the federal report fairly reporting of the work or during the Investigation.

We, we provide parallel capability there, so we’ve added a equivalent condition section there, as well, and we’ve also put in the the reference, the, the ability to reference the safety and environmental critical element group as well.

So, in this case, we’ve actually, you see this sort of small change in the, from a group perspective, whereas previously, we had separate safety, critical, and environmental critical references. We know that some customers combine those, when we’ve done it at a group level, it felt like it was logical to use that terminology safety and environmental critical element, so we’ve, we’ve, adopted.

So, that outlines the, the, the new features in the release. And I, just, before we move over to the demo, I just wanted to quickly show you one more slide around the training context.

So, you can see in the center here that we’ve added two new, within sort of, what we’ve referred to as a library, We’ve introduced a training course application, so that dot manages, allows you to manage all different definitions of training courses that you might want to. And it’s supported by a very simple application that allows you to build a training course up from training modules. If you want to do that, sort of an optional capability.

You can do a training course without using the training modules, but that, that’s there if you need it.

Also, within this training course capability, it’s used to manage the delivery of the, of the sessions associated with those training courses and the participants in those sessions.

So quite a bit heavy capability in, and around the training, across applications, to also manage the delivery, as well as the basic definition of the, of the training courses themselves. Again, this is an area where Francisco has been heavily involved in the, yeah.

The design of this, of this capability.

So there’s a lot of customer feedback has been been coming into this application. And so in terms of how we apply it, as I mentioned, the crafts and skill level is, supports. the role based training. From a personal perspective, then, on the person record, you can identify both required and completed training.

So it starts to make it much easier to build training plans for individuals, which is groups of individuals, which has been an area where we are.

I’ve had feedback that more could be done in terms of the link between labor and qualification. And you can actually we associate the, we’ve associated training requirements at the permit certificate type. So through the qualification, on the labor record, you can get some training. That way through the, through the permitting Certificate type. On certifications, for personnel certifications, is also the link. The link is there through the Permitting Certificate type.

Turning to the right of this slide, then from a yet, from an asset perspective, then you have the ability, again, to certify, to identify asset specific training through the type of certificate that you, for that asset, or multiple types of certificates.

Structure that supports multifold, certifications on an asset’s, similar thing on the on our location, and I’d also in the actual certification.

Application itself through, through permanent certificate type, from a sort of a tough space perspective, then you can, you can identify training courses directly on a, on the M O C record, on the access permanent record, on a work order and a jobs plan.

Again, you can do it through the through the parachute certificate type.

So it’s a pretty hefty, whole round capability around trading.

First time, we’ve introduced this capability into maximo, so it’s an area where we anticipate will grow and evolve it based on based based on customer feedback. But we think this is a significant step forward, and the capability for the maximum.

So at this point, that’s probably good timing to, to swap over for our demo two.

Kyle, if you write your resume hi, Kyle, can you hear me up? Can you hear me OK? I can hear you. Fine. Yes. So I’ll stop sharing.

I will start sharing, hopefully. Let’s show my screen.

Kyle’s just Wildcards getting a screen up there.

It’s, I mean, it’s, Kyle will there’s, there’s more than we can show you in one session here, so we’re going to focus on investigations and an incidence here. and it’s this general questions about the broader capability that would be glad to answer them, but please come back through to us and through.

You can always put you in touch or reach out directly, and we can give you more information on on capability we may not be able to cover in a detailed demo today.

Thanks.

So like Russell said, I’m gonna cover primarily two big areas that are part of this release. one is around incident management, and the updates that we’ve taken on within the incident management process. The second area is around some of the analysis capabilities that are available within the investigation application.

So, just to, jump in to the incident work that we’ve done, like Russell had mentioned, as part of his slide presentation.

We have a lot of situations where an incident involves multiple, what, we’re now calling events occurring as part of the overall incident. In the past, customers have used capabilities within Maximo, whether it’s global and related to global records or an originating incident record. And then multiple follow ups to capture these types of details. So, this was kinda the use case that we used with a lot of our dev partners, as we went through the process of identifying exactly what we wanted to do. So in this particular use case right, there’s a tractor trailer that’s going down the highway. There’s an accident.

The driver of the truck has fractured his right leg is dislocated shoulder. He did it stitches his forehead.

It’s going to be out of work for three months and then unrestricted duty for another three months.

The tractor trailer is damaged the the load of diesel that was in the tractor trailer highway. And the driver of the other car that was involved in the accident was also injured in his vehicle is totalled. So historically, or prior to this current release.

There are ways to capture all of these details, but it wasn’t necessarily as smooth as it could be. So we’ve taken on this use case as part of this work, and as I go through my demonstration, this will be just kind of keep this use case in mind as we go through part of that demo.

The second area that was a big focus of this release is around structured RCA type data, so as Russell said, Investigations, today, when you go to the Analysis tab, we allow our customers to perform all types of different analysis. So whether it’s five whys: human factors type analysis, root cause type analysis, those are all their prior to the current release. What we’re trying to enable is, as we talk to customers, a lot of them are using different sources for their structured RCA type data.

So, whether it’s ABS type data, or not type data, or performing scat type analysis, they really wanted to be able to capture that data in a very structured way. So, it could generate a result that’s actionable and accurate as they’re identifying some of the leading indicators within their environment.

So, we needed to make it somewhat.

Configurable. So, I could take any one of these data structures. Whether it was five nodes, deep, six nodes deep, or eight nodes deep, and allow them to identify the number of nodes that they wanted to capture, the descriptions of each of those nodes. And out of the box, what we do is, we provide a relationship between each of those nodes, where the previous node selected, then filters the values for that next node that’s being selected.

So, we’ll go through an example of this, and it will create the structure and show you how easy, hopefully, that we’ve made it as part of this release.

Just to give you a quick summary, I think Russell did a nice job going through some of these areas.

But within incident management, being able to capture multiple events on an incident and using some of the capabilities that are part of the maximum platform, particularly around classification and extended attributes whereas I capture an event and it might be let’s say a spill, I could capture very specific information related to that spill and drive that capture through extended attributes on each of the events.

Next two areas. Our, we’ve heard this over and over again. The ability to capture multiple injuries per impacted person And then for each of those injuries captured multiple outcomes per injury. So, in our example, we were saying somebody was going to be out of work for three weeks, and then as they came back, they were unrestricted duty for another three weeks. Being able to capture both of those outcomes was integral to as part of this process. We’ve also done a little work around claims management, tracking both at the, what I’d call, the primary incident level, as well, as the event level.

So, when we talk about claims management, whether it’s a medical claim, a legal claim, a property claim, no, being able to identify claim reference.

So, as the incident is being managed and processed, I always have kind of a reference to that, that claim that might have been filed against that, either events are against the incident.

We also had updated the self-service incident, UI, an application, to allow for the capture, some of that event type detail from the self-service user. And then, subsequently, as as we made all of these changes, there was impacts to all of the out of the box reports that we provided.

So whether it was the Incident Summary Report, the Incident Details Report, or any of the osha reports, the 300 to 300 a on the 301.

So, I’ll go through, I’m gonna focus when we get into the incident management on events and then the multiple injuries and multiple outcomes. And I’ll also show you where we’re capturing some of that claims management capability. Over on the investigation on the Analysis tab. Really what we’ll do is we’ll focus on the two personas that are involved in this use case. one is the administrator who creates the structure, right? They consume the ABS data, the … data, the narrative. they were able to bring it into maximum.

And then the, the actual investigator, right who uses that structured data to perform is structured data analysis. So we’ll go through both of those sides. And then, the final piece that we added, as part of the investigations, and I think it’s pretty powerful, is the ability to drive corrective actions from the results of any analysis that’s been performed. So, we’ve added that capability to create a service request or create an MRC request for an action related to each of those root causes as they’re identified as part of the investigation process.

So, with that, let me jump out of here.

I am, let me go over to my maximum, everybody see my maximo, OK?

Yes, yes. Excellent. So, I’m going to go through the incidents. Of course. I need to log back in.

So I am on a QA box, so if I run into any problems that it will be my, my excuse. So I am going to jump into the incident management process, and I’m going to create a new incident.

So as part of the primary incident, I might capture the fact that there was an injury, an incident that resulted in an injury, and it could be a major injury. I’m not going to capture all the details. I just wanna give you the feel for, kind of the overall process, right, Where I have. What I would consider the primary incident.

Probably the one that’s going to be reported to osha, because there is an injury related to one of my employees. So as part of that header on my incident record, I’m capturing the fact that this is an incident with injury, and it was a major injury.

I would also, as I captured all those details, I want to show the incident Events tab that we’ve now added. So if I click on the new event, you can see we’re using a table window approach. So I can have as many events related to this incident as occur. So there’s 15 different things that I want to capture and track against the primary incident. I can do that using the details, The incident types.

So let’s say there was also let’s say there was a spill and it was a, it was a minor spill.

It was a safety observation, I could capture that as well. What I want to show as I come through and I capture those to those events? This is just an example of a classification that I created.

So, as I select this classification, you’ll see down the specifications area, right? I’m presenting two additional questions, and of course, I didn’t set this up properly prior to the demo. But in the description, it was going to ask the user what was spilled?

I can capture those details in the alphanumeric I pray as part of our live implementation. I would probably clean up some of these fields I’m only presenting what would be applicable, but that’s one example The second example here is was it contained or not?

And, as I open, you can see, it set up that second attribute it to be driven through a value list, and it’s a yarn value list, so I could capture if it was contained. Yes or no.

The other part you will see here is, at the event level, is that that ability to collapse capture a claim type. So, if there was a legal or any other type of claim, I can capture those details as part of each of the events.

The other part that’s related to this, that’s kind of traditionally, what you would expect from maximum, is that is a value list, right? So as you roll this out, you might have other types of claims that you wish to track. So as you look at the value list, right, we’re providing legal, medical, and property out of the box. But you can go in here, and you can modify and add as many values.

The key point is, I can have multiple events. So in this case, now as or as a result of that action accident, there was a skull that needed to be cleaned up.

There was A So vehicle damage, so it was the passenger vehicle. That was damaged right, so it’s not a vehicle.

That’s my vehicle, But it’s one that, because it was one of my employees, I need to be able to track of that event and potentially any type of claim or additional follow up that’s required.

As we worked with our dev partners, initially when we were thinking about these events, is, we were thinking about these almost in the same context, and the same level of detail, and the number of attributes we presented as the primary incident.

And we probably went through 2 or 3 iterations of this, to get to the point where we’re at now, where it was pretty clear from the feedback that we were getting, that there really are, the customers are only looking for a subset of detail, in relation to the, the primary incident record.

So, behind the scenes, if you go and look at the object that’s associated to the events, there is quite a few other attributes that are available. So during your implementation, say, you know, I want to capture priority for each of my events as well, that there’s probably a priority field that’s already part of that object that you can expose using App Designer. But we’re taking more of a minimalist approach to make it simple quick and allow you to capture the data that you need.

So let me just go back to the primary incident.

And before I get into the details for each of the impacted persons and some of those multiple injuries or multiple outcomes, we also allow the capture of the claim type and claim reference at the, the, the primary incident level as well.

So you’ll see that here.

Now, what I want to do is, I want to capture the details for an impacted person. So this is my employee who was the driver of the truck and my incident who was injured.

So, let’s give him a name. We’ll call him writing.

And as I Put those details in, the system is going to pull up all of his related information.

I could add the role that he actually played this case. I’m not sure how familiar everybody is on the phone, but one of the things that we provide out of the box, is one of the roles is called Injured, or Ill. So this is my driver who had a cut on his head he dislocated shoulder. And he broke his leg. So I want to capture all of those details related to reading. For HIPAA purposes and some privacy purposes, there’s a section that’s conditionally presented only to people who’ve been granted rights to that section.

It’s presented when that logged in user has those rights and the person role is injured or ill.

So when I select that, you’ll see there’s a new section that’s presented, which is this whole injury and illness section.

In Prior releases, this was a section where it was a whole bunch of attributes that weren’t organized in the way they are now.

So what we’ve done is we’ve taken a table, a window approach and allowed for insertion of multiple rows, into each of those stable windows that are related to multiple injuries and then multiple outcomes for each of those injuries. But I can also have multiple people who are involved, as well as multiple injured people. So it sounds confusing. I think, as you were we, if you walk through a couple of examples, I like the way that we’ve organized this.

So if I click on a new injury or illness, I’m presented, basically, with the form to capture all of the details for this particular injury or illness.

So in this case, I’m going to say that there’s an element of an injury, say it was A, let’s say, a cut or a laceration.

Say it was on his cheek.

I can go through and capture all of the details related to the health care provider as well as the outcome for this particular injury.

And again, we’re taking that table window approach so I can have multiple outcomes for the injury.

So let’s say he is going to be out of work, say, starting today. And then ending next week, and then a second outcome when he does come back is there’ll be a job restriction for another week.

So once I’ve captured the outcomes related to the laceration, you can see I still have that button to add another injury.

So I’m going to add a new injury and it inserts the second row within that table. And now I’m going to go through that same process.

What was the injury I’m going to say as a fracture and it was his leg.

And again, the outcome. Multiple outcomes again. So I think you get the idea of what I’m, I’m trying to illustrate here.

So let’s just say he was on a, he’s going to be out of work again.

For a week, and then it’s going to be on a restriction.

one of the things that you’ll notice on the outcomes, is there’s a orange field that’s called most serious Outcome.

Just finished capturing these details.

It’s going to be up restriction.

So as we talk to our customers, what actually gets reported to OSHA in the states is the most serious outcome. So I don’t necessarily want to report all of the outcomes that I’ve captured, just the most serious.

So we’ve added that field to allow the person, who’s responsible for managing these incidents, and managing the, the outcomes of the incidents, to easily specify what’s the most serious outcome.

As a result of this work and some of these changes that we’ve made, like I said, we’ve updated all of the out of the box reports that come along with the incident management process.

So now let me jump. I’m going to save those details. I’m going to jump into the into the investigation work that’s been done. And, again, we’re going to go through two personas here.

There’s a new action that’s been added, which allows the administrator, it can be granted it’s controlled by SEC ops so you can grant this to a single user, maybe 1 or 2 users who are your administrators, but it gives them access to this action, which is the ability to add or modify structured RCA data.

Before I do that, I just wanted to give you just a quick view of an example of this type of data.

So the sample that I’ve created, the structure looks like this, right? So, there’s the top level, is that the type of analysis that’s being performed.

Once you identify the type, you can select the problem, then you kinda go right down the hierarchical path. So I select the problem.

Cause categories are presented, an intermediate causes basic cause of root cause.

The key to this is how this data is presented based upon the values selected.

So in this example, if I select this type over on the left-hand side, I’m only presented with a single selection of problem that’s available to me versus if I was using this type. And these are all different values within the data structure. This is just a kind of representation of what the structure looks like.

If I were to select the secondary type, right, it would give me access to all of the problem, the problem level boat nodes that are available.

It’s kind of a really neat way to kind of drive the interaction and capture accurate data to allow your customers or to allow your investigators to capture really accurate inequality data, to really drive some of those leading indicators within your environment.

Let me jump back over here.

And I’m going to jump into this action.

And as I come in, one of the first things, the administrator would have to do is identify the number of levels or nodes of data within the structure.

So I’m going to specify six.

As I specify six, it then presents the system is going to present each of those levels, And it’s the opportunity where I name each of those levels.

So it’s going to be type, problem.

Cause Category.

I could spell. It would be good. Intermediate cause.

The basic cause the root cause, so this isn’t based on ABN or Scad or America, it’s kind of combination of all three.

So I’ve identified each of my column headers and the next part is I can upload an image of what my structure looks like.

So if I come here, I’m going to select a file, and that that example I just showed to you, I want to be able to pull that in.

That’s my example. Hold on. This image. Then I would define refresh. You can see on that refresh levels, the column headers for that structure has now become part of part of the UI presentation. So that’s configurable, almost on demand for that administrator. The second part of this as, as I start to consume that data, it’s very difficult.

There were, it was evident that it would be very difficult to enter this data within the UI row by row. So the ability to import the data path after it’s been massaged and put it into the right format in a spreadsheet was became very important to this whole process. So we’ve created a sample file, which is here, going to open it and now I’m just going to import it.

With a couple of clicks: after I’ve created it, you can see based upon my sample data brought in 12 or 2000 rows of structured RCA data that will now be available to my investigator as he performs his work, I just wanted to show you.

On that refresh, you’ll get the access to that image.

So, as the, the investigator goes through what we like to just provide kind of the example the image as kind of as a reference point for the person who’s performing the, the, the actual investigation.

So, let’s just close that. What I want to do now is just open an investigation record, and I want to go into my Analysis tab. This is an area where we’ve done a little bit of work. We re-ordered some of these screen the tabs within the analysis within the overall analysis tab. So they were just kind of grouped together. Now we’ve added this structured RCA!

So I can capture the details in the header of the RCA of when it needs to be completed, was there an approval required, is it mandatory? Who has a lead is, has been approved.

What I want to show is how you actually perform the results.

So, as I open those details, and I click the row, or I can have multiple rows, within this type of analysis, so there might be, you know, multiple root causes that can be identified using this structured data.

The key part I want to show here and illustrate here, is, based upon the administrator creating that structure, it now is presented over on the the investigation side. So it’s consumable, And it’s, it’s very configurable.

So let’s just open this up, So these are the different types of structured RCI Analysis that are available.  So if I select Environment and I go to a problem, I can see it’s available for an asset or equipment record.  The cause type was an improper use.

Intermediate cars could be a human factor, basic cause, it was too much, the workload was too high. Cindy? Select one of these. I can capture some notes that are related to this type of analysis or do I need to do, you know, might be some.

Additional resources required. Click New Row. I can go through again if this time. I’m going to select quality.  Actually, let’s do this. It’s like safety.

You can see the values that are presented at the next level, at the problem level, are driven by the type selected.

So when it safety, of all three problem values available, by select human employee. It So I’m just trying to illustrate the fact that these are all we call them, table domains. So as the previous value is selected, the child value is filtered seizures. Oh, yeah. Yeah, on the SQL Server, right now, we just having an issue with the Refresh on the image. That image, as I’m going through that analysis, is available, and I can open up, open up the details a little bit, and you can see a little bit better.

The other part that we’ve added as part of the Analysis tab is after I’ve gone through, if I’m using all of these different types of analysis, is on the Results tab.

So, as I capture some of the results that are coming out of the analysis, I could say, you know, there’s A it’s wrack issue. Retraining. It becomes actionable at the results level.

So, the actions that are available, and I could create a service request, I could create a follow-up investigation. So, it might be, you know, I need more detail, Desiccation just on this single factor that would require its own investigation.I could create an MRC request, or I can create an action. I’ll just do one thing before I do that.

Kyle, we’re, we’re actually coming up on five minutes to the hour, so excellent. one minute left.

I just wanted to show the action here, So, as I’m creating the action, right, so these are my illustrating the fact that the investigation results become actionable, alright, so I can create an action. I can assign that actually to somebody, and I can track it through to completion.

All right, kind of a whirlwind tour of everything we’ve done in investigations, as well, as the, you know, over on the incident side.

So, I’ll wrap that up there, and if we do have any questions, I know Russell and I would be more than willing to answer them.

We certainly do have questions. I do want to let folks know that if we’re not able to answer all of your questions, we will answer those offline and get those to an e-mail. So I’ll just pick a couple here that hopefully can be answered quickly on the employee information importer. Can the information be collected from outside HR systems?

Well, I think any data can be collected for outside of Maximo, and then imported using the object structures, So as long as it’s in the right format, you can either use the integration framework to import it, or some of the list page import would also work.

Is the incident module linked to the work management? Can we link up, link follow on work orders with the incident? Will attendance be updated to indicate the driver is on leave?

Incidents can definitely be linked to work orders, right? So, I can create a work order from an incident record, and then the system automatically creates kind of that originate or follow up type relationship, the second part of that question, I’m not sure I. Can you just repeat that? Can we link the follow on work order with the incident? Will attendance be updated to indicate the driver is on leave?

I mentioned that might have something to do with scheduler  For the first part, right, that ability to create the relationship is definitely there. The second part of the driver gets injured.

It almost sounds like they want to automatically send some type of a notification to interested parties that they’re up, what you can do, kylie’s, you can mark them out as an outcome.

You can mark that there aren’t leaf so you can identify the lethal special leave associated with an injury or illness. So you can’t do that.

I think the other part, Well, so that you could do because then drives an escalation That would look for records that mark that way and automatically send an e-mail to notify supervisors or anybody who might play the role of interested party, to that fact that they’re on leave.

Right, yeah, that would be one option. Yeah.

OK, I think we have time for just one more quickie here. Oh, at what status point can you no longer add events?

When the incident is closed, I believe the logic is you can’t I need to confirm that, but typically when a record reaches close just for integrity purposes, we kind of locked down that record from any additional edits.

I think we’ve got, I can squeeze one more in here 7 dot 6 dot 1 X is still supported.

What is the possibility of porting this functionality to current the current version rather than updating 7 dot 6 dot 2 dot exe I’m going to assume that it’s it’s an all or nothing you’ve gotta update to that tool to get all of these new functionality.

I would, I would concur. Like to get all of this new stuff, it’s really just part of the upgrade path to get to 76, 1 2.

Right. OK, well, gentlemen, I wanted to thank you so much for your presentations. And I would like to thank everyone who attended today. We will make this recording available to anyone who would like to take home leftovers. We will be concluding our 2020 Lunch cast Series next week when we chat with Leanne Hornby about the IBM maximal Asset Template application. Thank you so much, everyone. We appreciate you being here, and we will see you next week.

Thanks, Scott

Thanks, Scott. Bye, everyone.