The Benefits and Losses (HSE) application is used to support benefit identification and loss reporting. For example, the benefits and losses associated with a Solution or an Improvement, production losses, or the impact resulting from an incident.

The application has two sub tabs. If the impact type is BENEFIT then the Losses sub tab becomes read-only. If the impact type is LOSS then the Benefit sub tab becomes read-only. There is a checkbox called “Benefit and Loss Apply” which when checked will allow both a benefit and a loss to be entered.

A Loss record can be created from the Operator Log (HSE) application as would be the case when recording a production loss. The Work Order Tracking (HSE) application can also be used to create a loss record. A follow-up investigation may be created from a Benefit and Loss record using the action Create Investigation.

Benefits can be associated with the Plans and Actuals of an Improvement record, in actual fact a loss can also be associated but this wouldn’t make sense and the screen fields are those associated with benefits. A Loss can be associated with the Job Plans (HSE), Preventive Maintenance (HSE) or Work Order Tracking (HSE) applications as a way of indicating the production impact on performing the associated work. An impact record can be associated with an incident in the Incidents (HSE) application, or a defect in the Defects (HSE) application, in both cases either a benefit or a loss can be associated.

The main table of the application is PLUSGBENEFIT and it resides at the SYSTEMORGSITE level, care will need to be taken to ensure that the benefit or loss can be associated depending on the system, organization or site level of the target application.

Impacts Tab

The header fields identify the impact and type; benefit, loss or whether both can apply.

• Impact – The unique identifier of the impact record with organization and site.
• Description – The description of the impact record, it has a long description button.
• Impact Type – Identifies whether the record is a Benefit or Loss. This is supported with a synonym domain PLUSGIMPACTTYPE. If LOSS is selected, then the Benefits sub tab becomes read-only. If BENEFIT is selected, then the Loss sub tab becomes read-only. However, if Benefit and Loss Apply checkbox is checked then the fields of both sub tabs will be enterable. If you change the value after filling in fields on the sub tabs then those fields are not blanked, but they may become read-only.
• Impact Area – The area affected by the impact. There is a value list with values of Environmental, Production, Reputation, Health & Safety.
• Benefit and Loss Apply – A checkbox to indicate that both benefits and losses apply to this impact record.
• OrganizationA structural element of a Maximo database which is used for data sharing and is often aligned to a legal entity of an organisation. More – Part of the unique key with Impact and SiteA structural element of a Maximo database that is used for data separation. More. It will become read-only after save. It has a standard lookup.
• Site – Part of the unique key with Impact and Organization. It will become read-only after save. It has a standard lookup.
• Calculation Method – The method of calculation of the benefit or loss. There is a value list with values of Discounted Cash Flow, Internal Rate of Return, Net Present Value, Return on Capital Employed, Return on Investment.
• Impact Reference – A reference of the source of this impact record (12 characters). When a loss is recorded from the Shift Log (HSE) application this is the reference of the Shift Log record.
• Measurable – A checkbox to indicate that the benefit or loss can be quantified or measured.
• Status – A read-only field to display the current status of the impact record. The Change Status action is used to change the status. The default status is DRAFT, and it can be changed to ACTIVE or INACTIVE.
• Status Date – This read-only field displays the date/time when the status was last changed.

Benefits Sub Tab

Benefit Details section

• Benefit Quantity – The quantity of the benefit. When a value is entered the Benefit Units field becomes mandatory.
• Benefit Units – This read-only field becomes enterable when a value is entered for the Benefit Quantity. There is a Select Value to the units of measure that can be entered in Classifications or Item Master applications.
• Per – This read-only field displays the same unit of measure selected for the Benefit Units field.
• Unit Price – The price on which the benefit was based.
• Price Units – This read-only field becomes enterable when a value is entered for the Unit Price. There is a Select Value to the units of measure that can be entered in Classifications or Item Master applications.
• Calculated Benefits – The calculated benefit is determined by Benefit Quantity x Unit Price, it is read-only.
• Calculated Units – The calculated unit is the same field as Price Units and will always show the same value, it is read-only.
• Period of Benefit – The period of time over which the benefit will be measured.
• Period Units – The unit of time associated with the Period of Benefit. It is a read-only field which becomes enterable when a value is entered for the Period of Benefit. There is a Select Value to the units of measure that can be entered in Classifications or Item Master application.
• Last Update of Unit Price – The date when the Unit Price field was last updated.

Estimates section

• Estimated Benefit – The estimated benefit. When a value is entered the Estimated Benefit Units field becomes mandatory.
• Estimated Benefit Units – This read-only field becomes enterable when a value is entered for the Estimated Benefit. There is a Select Value to the units of measure that can be entered in Classifications or Item Master applications.
• Estimated Cost – The estimated cost associated with implementing this benefit.
• Cost Estimate Class – The class of estimate reflects its accuracy. This field has a value list with values of Class 1, Class 2, Class 3. Class 1 is considered the final cost estimate class, the total estimate against which a project will be measured.

Measurements section

• Related KPI – The Key Performance Indicator that can be used to measure the benefit. There is a Select Value and Go To KPI Manager application, there is no restriction on which KPI can be selected. The KPI’s description is shown alongside.
• Related Meter – The Meter that can be used to measure the benefit. There is a Select Value and Go To Meters. Any type of meter can be selected. This field may be populated if a Measurement Point is selected. The meter’s description is shown alongside.
• Related Measurement Point – The Measurement Point that can be used to measure the benefit. There is a Select Value and Go To Condition Monitoring application. Selecting a value may set the Related Meter to the meter on the Condition Monitoring record. If the Related Meter has a value, then the Select Value is restricted to measurement points that have that particular meter. The measurement point’s description is shown alongside.

Related Assets section

• Asset – The asset to which the benefit is related. There is a Select Value and Go To Assets (HSE). Any asset at any state can be selected. When an asset is selected its location is used to populate the Location field. The asset’s description is shown alongside.
• Location – The location to which the benefit is related. There is a Select Value and Go To Locations (HSE). Any location at any state can be selected, including storeroom locationsA physical place where assets exist and where work can be performed. More. Selecting a location will not populate the asset field if the location has only one asset. The location’s description is shown alongside.
• Location Profile – The location profile which this benefit is associated with. There is a Select Value and Go To Location Profile (HSE). To be selected the impact record must be defined at the Site level, this is because a location profile is defined at this level. The location profile must also be at Active state to be selected.

Losses Sub Tab

Loss Details section

• Loss Type – The type of loss. There is a value list with values of Near Miss to a Loss, Planned Production Loss, Unplanned Production Loss.
• Loss Indicator – How the loss was discovered. There is a value list with values of Computer generated Alarm, Leak Detection, Emergency Shutdown, Visual Inspection.
• Loss Source – The source of the loss. There is a value list with values of Downhole, Loss from Fire System, Leakage, Production Shutdown.
• Potential Loss – A checkbox to indicate that the loss is a potential loss. If unchecked it indicates an actual loss.
• Is an Estimated Loss – A checkbox to indicate whether the loss is estimated. If unchecked it indicates an actual loss with a reasonable level of accuracy.
• Is a Repeatable Loss – A checkbox used to indicate that the loss has previously occurred, or a repeatable loss is likely in the future.
• Production Impact – A checkbox to indicate that this loss has/had an effect on production.
• Loss Quantity – The quantity of the loss. When a value is entered the Loss Units field becomes mandatory.
• Loss Units – This read-only field becomes enterable when a value is entered for the Loss Quantity. There is a Select Value to the units of measure that can be entered in Classifications or Item Master applications.
• Improvement Required – A checkbox to indicate that an Improvement record should be created, and the improvement process followed through to its conclusion.
• Regulatory Reportable – A checkbox to indicate whether a regulatory authority should be informed of this loss.

Loss Reference section

These fields are read-only and are filled when reporting a production loss in the Shift Log (HSE) application, a new impact record is created in this case.

• Shift Log Reference – The shift log reference when a loss is reported from the Shift Log (HSE) application. This is a read-only field.
• Summary – The read-only description on the associated Shift Log.
• Log Entry Reference – The log entry reference on the Shift Log, the record from which the Record Production Loss button was pressed. This is a read-only field.
• Summary – The read-only summary field on the log entry where the Record Production Loss button was pressed.

Dates section

• Observed Date – The date/time that the loss was observed.
• Reported Date – The date/time that the loss was reported.

Related Assets section

• Asset – The asset to which the loss is related. There is a Select Value and Go To Assets (HSE). Any asset at any state can be selected. When an asset is selected its location is used to populate the Location field. The asset’s description is shown alongside.
• Location – The location to which the loss is related. There is a Select Value and Go To Locations (HSE). Any location at any state can be selected, including storeroom locations. Selecting a location will not populate the asset field if the location has only one asset. The location’s description is shown alongside.
• Location Profile – The location profile which this loss is associated with. There is a Select Value and Go To Location Profile (HSE). To be selected the impact record must be defined at the Site level, this is because a location profile is defined at this level. The location profile must also be at Active state to be selected.

Related Records Tab

This is the standard layout with a table window for Related Tickets and one for Related Work Orders that is found on ticket and work order based application.

Log Tab

This is the standard tab with two sub tabs for the Work Log and Communication Log.

Actions

• Change Status
• Create Investigation
• Create Communication
• Modify/Delete Work Log

There is no action to show the status history.

 

Location Profile (HSE)

The Location Profile (HSE) application can be used for recording numeric values over a set of time periods. These values are unlikely to be held elsewhere in Maximo. They are most likely to be used on reports with other Maximo data, or as a way of providing a set of constants used in calculations.

There are three particular use cases and each of these has its own specific tab for recording the profile.

• Production – accepts decimal values
• Persons on Board – accepts integer values
• Working Time – accepts integer values

A location profile would use one of these tabs, but there is no restriction stopping multiple tabs from being used. The Type field on the main Location Profile tab could be used to conditionally show the associated tab.

The Production tab can be used for recording target and actual production output or to show the impact of a turnaround or shutdown on the production output. The Persons On Board tab can be used for capacity planning of personnel, for example the expected number of people during a turnaround or shutdown can be used for determining catering arrangements or accommodation if it is an offshore facility. The Working Time tab might be used for recording the capacity of training programmes.

The Location Profile is used on the following applications:

• Job Plans (HSE) – Main tab, Production Impact section. To be selected the location profile has to be in Active state. The Job Plan has to also be defined at the Site level to match the site on the location profile. This is most likely to be used for showing the impact of performing the work on the production profile.
• Work Order Tracking (HSE) – Main tab, Production Impact section. To be selected the location profile has to be in Active state. The work order has to be defined with the same site to match the site on the location profile. This is most likely to be used for showing the impact of performing the work on the production profile.
• Preventive Maintenance (HSE) – Main tab, Production Impact section. To be selected the location profile has to be in Active state. The PM has to be defined with the same site to match the site on the location profile. This is most likely to be used for showing the impact of performing the work on the production profile.
• Benefits and Losses (HSE) – On both Benefits sub tab and Losses sub tab. This could conceivably be used for any type of location profile. To be selected the location profile has to be in Active state and the Benefit and Loss record has to be defined at the site level to match the site on the location profile.

Location Profiles are defined at the SITE level and there is a unique key of ORGID, SITEID, PROFNUM – the Profile field. The location profile status defaults to Draft and can be changed to a status of Active or Inactive. The location profile can only be changed at Draft status, but it must be at Active status to be used in other applications. This might require the Location Profile being set to Active to link it to other records and then changed back to a status of Draft to continue to update the records especially when recording actuals on the Production tab.

Location Profile Tab

This tab provides the context for the location profile including the link to the location record.

• Profile – The profile number is part of the unique key with Organization and Site. It has an autokey to generate the next number.
• Description – The description of the location profile (100 characters). It has a long description.
• Type – The type of location profile. There is a value list with values of General, POB, Production. Working Time is not on this list but can be easily added.
• Category – The category of location profile. This is supported by an ALN domain PLUSGLOCPROFCAT which will need to be set-up prior to use.
• Status – The status field is read-only and is changed by using the action Change Status. The default status is DRAFT and it can be changed to ACTIVE or INACTIVE.
• Status Date – This read-only field shows the date/time when the status was last changed.
• Site – The site identifier is defaulted from the user’s default insert site when they create a location profile record. It is read-only. The Organization identifier is similarly populated but it is not displayed. Both Site and Organization are part of the unique key with the profile number.
• Owner – The owner of the location profile record. This field is read-only and is set by using either Take Ownership or Select Owner actions. When populated it will blank the Owner Group field.
• Owner Group – The owner group of the location profile record. This field is read-only and is set by using the Select Owner action and choosing a Person Group. When populated it will blank the Owner field.

Profile Details section

• Details – The details of the location profile. This is a long description field supported by Rich Text Formatting. It is not the long description of the Description field.
• Location – The location that this profile is based on. There is the standard detail menu that includes Select Value and Go To Locations (HSE) but also the location drilldown and ability to find the location through a classification or attribute search. It does not populate the asset field if there is only one asset at the location. The location’s description is shown alongside.
• Asset – The asset that this profile is based on. There is the standard detail menu that includes Select Value and Go To Assets (HSE) but also the location drilldown and ability to find the asset through a classification or attribute search. When an asset is found its location is used to populate (or overwrite) the location field. The asset’s description is shown alongside.
• Constraint Point – The point or reason that constrains production capacity. This field has a value list with values of Export, Process, Reservoir, Well.
• Classification – The classification of the location profile, for example, for a type of Production this might be a classification for each type of product. The Class Use With object is PLUSGLOCPROF. The classification has the standard menu that includes Classify, Clear Classification, Go To Classifications. When found it populates the Class Description field. The attributes of the classification are displayed in the Specifications tab.
• Class Description – The Select Value on the description of the classification may sometimes be the quickest way to find a classification because it provides a word search capability. When found it populates the Classification field.

Dates section

• Created By – The person who created this location profile record. This field is read-only and is populated on record creation. It has a Select Value and Go To People (HSE). The display name of the person is shown alongside.
• Created Date – The date/time when the location profile was created. This field is read-only and is populated on record creation.
• Changed By – The person who last changed this record. There is a Select Value and Go To People (HSE). It is not populated automatically on save of record but needs to be manually selected. To be selected the person has to be at Active state. The display name of the person is shown alongside.
• Changed Date – The date/time when the Changed By field was last updated. It is a read-only field.

Production Tab

This tab would be used if the Type field was set to Production. It allows production targets and actuals to be recorded for each time period.

• Production Period – The period of time associated with the production data. There is a value list with values of Month, Quarter, Year, Week.

Production Data table window

• Production Data – The identifier of the production data record. It has a numeric sequence, 1, 2, 3, etc, but the value can be modified including after save. It is a mandatory field.
• Description – The description of the production data record, most likely the title on any report (100 characters). There is no long description.
• Product Type – The type of product associated with this production data record. There is a value list with values of Gas, Oil, Condensate, Miscellaneous but this will need to be modified to meet your needs. The ALN domain is PLUSGPRODTYPE.
• Comments – A comment field used to describe anomalies or reasons for a variance in the production data values (200 characters). This field has a long description, but it is not shown.

Production Values section

• Installed Capacity – The total production capacity for the period.
• Production – The estimated or actual production data for the period.
• Unit of Measure – The unit of measure used for the installed capacity and production data. There is a Select Value. Additional units of measure can be added in Classifications or Item Master (HSE) applications.

Production Period section

• From – The starting point in time for this production data record. The To date/time must be after the From date/time.
• To – The end point in time for this production data record. The To date/time must be after the From date/time.

Persons on Board Tab

This tab would be used if the Type field was set to POB. It is used for people capacity, for example the number of persons allowed on an installation, the number of people in an accommodation block, etc. The values entered in the POB Planned section fields can exceed the capacity or extended capacity. There are also no calculations, for example to show contingency as the value of capacity less crew, vendors and visitors. This calculation can be added by using a Maximo formula.

Persons on Board table window

• POB – The identifier of the POB record. It has a numeric sequence, 1, 2, 3, etc, but the value can be modified including after save. It is a mandatory field.
• Description – The description of the POB record, most likely the title on any report (100 characters). There is no long description.
• POB Type – The type of POB. This is supported by an ALN domain PLUSGPOBTYPE which will need to be set-up prior to use.
• POB Period – The period of time associated with the POB data. There is a value list with values of Month, Quarter, Year, Week.
• Comments – A comment field used to highlight information in the POB values shown, for example to indicate that capacity is at its limit (200 characters). This field has a long description, but it is not shown.

POB Capacity section

• Base Capacity – The base capacity (number of persons) of this POB record, an integer value.
• Extended Capacity – The extended capacity of this POB record, an integer value.

POB Planned section

• Core Crew – The number of persons in the core crew that will use some of the capacity, an integer value.
• Vendors – The number of planned vendors that will use some of the capacity, an integer value.
• Visitors – The number of planned visitors that will use some of the capacity, an integer value.
• Contingency – The number of places held in contingency, an integer value.

POB Dates section

• From – The starting point in time for this POB record. The To date/time must be after the From date/time.
• To – The end point in time for this POB record. The To date/time must be after the From date/time.

Working Time Tab

This tab would be used if the Type field was set to General. It might be used for availability or recording other values with a total number of hours or days.

Working Period table window

• Period Reference – The identifier of the working period record. It has a numeric sequence, 1, 2, 3, etc, but the value can be modified including after save. It is a mandatory field.
• Description – The description of the working period record, most likely the title on any report (100 characters). There is no long description.
• Working Period Type – The type of Working Period. This is supported by an ALN domain PLUSGWPRDTYPE which will need to be set-up prior to use.
• Working Period – The period of time associated with the Working Period data. There is a value list with values of Month, Quarter, Year, Week.
• Comments – A comment field used to highlight information in the Working Period values shown (200 characters). This field has a long description, but it is not shown.
• Staff Working Time – The duration of staff working time, normally in hours, it must be an integer value.
• Contractor Working Time – The duration of contractor working time, normally in hours, it must be an integer value.
• Unit of Measure – The unit of measure used for Staff and Contractor Working Time. There is a Select Value to the units of measure, additional values can be entered in Classifications or Item Master (HSE) applications.
• From – The starting point in time for this POB record. The To date/time must be after the From date/time.
• To – The end point in time for this POB record. The To date/time must be after the From date/time.

Specification Tab

This is the standard Specification Tab that is found on many Maximo applications. The Class Use With object is PLUSGLOCPROF.

Log Tab

This is the standard tab with two sub tabs for the Work Log and Communication Log.

Actions

• Change Status
• Select Owner
• Take Ownership
• Create Communication
• Modify/Delete Work Log

There is no action to show the status history or ownership history.