The Locations (HSE) application has a number of additions over that found in the base Maximo product including nine additional tabs. As a summary you can:

• associate the location with multiple audits/surveys, certificates/permits, or regulations,
• record reliability data, perform a FMECA into failure modes,
• indicate whether a meter is being used for environmental consent monitoring,
• record the results of calculations needed to support environmental consents,
• view the number of failures and deferrals that have occurred in the last year,
• view the operator logs that have occurred in last 30 days,
• record document references, area classifications, access requirements,
• record details regarding valves and pipeline,
• perform a set of standard actions.

Meters Tab

There are additions to the details section in the meters table window to indicate whether the meter is being used for environmental monitoring reasons.

Environmental Consent Monitoring Details

• Environmental Consent Monitoring – A check box is used to indicate that the meter is being used for monitoring environmental aspects at the location.
• Consent Type – The consent type is supported by a value list with values, Emission to air, Energy Usage, Emission to ground, Noise consent, Odour consent, Vibration consent, Waste Management, Emission to water

Audits and Surveys Tab

This tab is used to maintain a history of audits and surveys carried out or involving the location.

• Audit and Survey – The audit or survey associated with the location. There is a Select Value and Go To Audit and Survey (HSE). Audit and Survey records at Draft or Inactive state cannot be associated with the location, they need to have at least reached Survey Entry status.
• Type, Category, Organization, SiteA structural element of a Maximo database that is used for data separation. More, Status – These read-only fields show the values from the Audit and Survey record.

There is a Select Audits and Surveys button for associating multiple audit and survey records in one action.

Certifications Tab

The Certifications Tab allows certificates to be recorded against a location. Each record has to have a Permit and Certificate Type, but the actual certificate does not have to be registered in the Certifications (HSE) application. Either the section marked Certificate, or the one marked Certification Record will be used, it is unlikely that there would be a need to use both sections.

Multiple records of the same Permit and Certificate Type can be added to the same location.

Details section

• Permit and Certificate Type – This mandatory field is supported with a Select Value and Go To Permit and Certificate Types (HSE). The Permit and Certificate Types that can be selected are those at Active state. The Category can be either Certificate or Permit and you can select records where any of the four check boxes have been selected.
• Status – This is a read-only field that displays the current status of the Permit and Certificate Type, active, inactive or draft.
• Category – This is a read-only field that displays the category of the Permit and Certificate Type, either Certificate or Permit.

Certificate section

• Certificate Acquired – A checkbox to indicate that a certification has been acquired. When checked the Date of Certification becomes mandatory and the Certificate Expiration Date becomes enterable.
• Date of Certification – This read-only field becomes enterable when the Certificate Acquired field is checked. It has a date lookup, it can be a future date.
• Certificate – This field is used for the certificate number or identifier of the certificate (50 characters).
• Certificate Expiration Date – This read-only field becomes enterable when the Certificate Acquired field is checked. It has a date lookup; the date has to be later than the Date of Certification.

Certification Record section

• Certification – The certification record associated with the location. There is a Select Value and Go To Certifications (HSE) application. The certification records that can be selected can be in any state except Inactive, they need not have the same Permit and Certificate Type.
• Extension – A certification record can be extended and this read-only field shows the number of times the certificate has been extended. If it shows zero, then it has not been extended.
• Expiry – This is a read-only field that displays the expiry date on the certification record.

There is a Select Permit and Certificate Type button for associating multiple records in one action.

Location Details Tab

This tab is for recording additional details about the location, its physical location, key document and drawing references, area classifications and accessibility requirements.

Header section

Used to describe the physical location of the operating location or alternate references for it.

• Physical Location – A description of the physical location in the plant (100 characters). This field has a long description, but it is not displayed.
• Legacy Tag Number – The tag number for the location (24 characters).
• Latitude – The latitude of this location which together with longitude provides its exact position geographically.
• Longitude – The longitude of this location which together with latitude provides its exact position geographically.
• Location Reference – A reference for the location which may be used in regulatory reports (12 characters).

Documentation References section

Used to identify the main drawings and manuals where the operating location will be found. The drawings and manuals may also exist as linked documents.

• P and ID – The identifier of the Piping and Instrumentation Diagram in which this location appears (24 characters).
• Operating Manual References – The main identifier of the operating manual where this location appears (10 characters).
• Drawing Reference – The identifier of the plant reference drawing in which this location appears (16 characters).
• Hazardous Area Classification Dwg. – The identifier of the Hazardous Area Classification Drawing in which this location appears (14 characters).
• Single Line Diagram – The identifier of the Single Line Diagram drawing (circuit diagram) in which this location appears (14 characters).

Area Classifications section

• Hazardous Area Classification – The classification of the hazardous area. This is supported with a lookup based on ALN domain PLUSGHAZARDCLASS which will need to be set-up prior to use.
• Fire Zone – The fire zone reference for this operating location (12 characters). There is no value list. A large site or building will be split into several fire zones.
• Ex/ATEX – A checkbox to indicate that the location is within an area that could be subject to an explosion or an explosive atmosphere (Fr.ATmosphèresEXplosibles.) When checked the Ex/ATEX Standard field becomes enterable and mandatory.
• Ex/ATEX Standard – A value list to identify the Ex/ATEX standard being used for this location:

• • ATEX 95 – Equipment and protective systems intended for use in potentially explosive atmospheres;
  • ATEX 137 – Minimum requirements for improving the safety and health protection of workers potentially at risk from explosive atmospheres.
• Area – The area associated with this location. This is supported with a lookup based on ALN domain PLUSGPERMITAREA which will need to be set-up prior to use. This domain is also used with Permit to Work; therefore, this field should not be used as the Ex/ATEX zone classification which should be held in another field.

Access section

• Access Requirements – Special requirements that may be needed to reach this operating location. Supported with a value list with values of Crane, Scaffolding.

 

Reliability section

Fields to store values for MTBF and MTTR. They are not linked to the recording of failure data in Maximo.

• Historic MTBF – The integer historic Mean Time Between Failures entered in hours.
• Target MTBF – The current target Mean Time Between Failures, entered in hours.
• Benchmark MTBF – The benchmark Mean Time Between Failures, entered in hours.
• Benchmark Source – The source of the benchmark figure for MTBF. This field is supported with a value list with values of Internal Data, Military Standard Data, OREDA.
• Predicted MTBF – The predicted Mean Time Between Failures, entered in hours.
• Date of Prediction – The date the predicted MTBF was made.
• MTTR – The current Mean Time To Repair, entered in hours.

Production Impact section

This section has fields to record the expected loss when an outage occurs.

• Outage Consequence – The impact on production if there is an outage at this operating location. This field is supported with a value list with values of Production Loss, No Production Loss.
• Loss Reference – The record that defines the production loss if there is an outage. This field is supported with a Select Value and Go To Benefits and Losses (HSE). To be selected the Benefits and Losses record must be at Active state and have an Impact Type of LOSS, a record with impact type BENEFIT cannot be selected. The description of the Benefits and Losses record is shown alongside.
• Loss Type – This read-only field shows the type of loss taken from the Benefits and Losses record. It can have values of Near miss to a loss, Planned Production Loss, Unplanned Production Loss.
• Loss Quantity – The quantity of the loss. It is an enterable field which is copied from the Benefits and Losses record but can be updated. It is a decimal field.
• Loss Units – The unit of measure of the loss. It is an enterable field which is copied from the Benefits and Losses record but can be updated. It has a Select Value to the Units of Measure values which can be entered in Classifications or Item Master applications.
• Replacement Cost – The replacement cost of the equipment at this operating location. It should be a value in the base currency of the organization. It is used in defect density calculations in the Improvements (HSE) application.
• Location Profile – A location profile is a set of values over time for a location, for example, the actual production units for the location. Only one location profile can be associated with the Location record, although there can be multiple location profile records that reference this location. In the context of this section it is likely to be a production profile. There is a Select Value and Go To Location Profile (HSE), only Active location profiles can be associated. The location profile on a Benefit and Losses record is not copied to this field.

Operating Context Tab

This tab is for recording the operating context and determining the risk categorization of the location.

Header section

• Physical Location – A description of the physical location in the plant (100 characters). This field has a long description, but it is not displayed.
• Function – The organizational function that has responsibility for this operating location. This field is supported with a value list with values of Drilling, Inspection, Maintenance, Production, Projects, Well Completion.

Operating Context section

This section has fields for identifying the operating context and criticality of the location and whether it is governed by an operating policy.

• Normal Operating Mode – The normal operating mode for this operating location. There is a value list with values of Running, Active, Intermittent, Standby.
• Operation Category – The operation category is supported with a value list with values of Manual, Subsea, Remote.
• Maintenance Strategy – The maintenance strategy for the operating location is supported with a value list with values of Time-Based, Run to Fail, On Condition, Campaign, Opportunity-Based.
• Operating Policy – The operating policy associated with this location. There is a Select Value and Go To Operating Policies (HSE). Operating Policies need to be in Active state to be selected.
• Safety Critical – A checkbox to indicate whether the location is in a safety critical area. If it is checked then the Safety Critical Element becomes mandatory.
• Safety Critical Element – If the location has a safety critical element then this field can be used. It is supported by a value list but the ALN domain PLUSGSAFETYCRITREF will need to be configured.
• Environmentally Critical – A checkbox to indicate whether the location is environmentally critical. It if it checked then the Environmentally Critical Element becomes mandatory.
• Environmentally Critical Element – If the location has an environmentally critical element, one that may be governed by regulation then this field can be used. It is supported by a value list but the ALN domain PLUSGENVCRITREF will need to be configured.
• Commercially Critical – A checkbox to indicate that the location is considered commercially critical.
• Quality Critical – A checkbox to indicate that the location is considered critical for ensuring quality of the product being manufactured.

Risk Categorization section

This section has fields for categorizing the risks associated with the location and associating the location with a Risk Assessment.

• Risk Assessed Location – A check box to indicate that the location has been assessed for risk.
• Risk Assessment – The safety risk assessment carried out for the location. There is a Select Value and Go To Risk Assessment (HSE). Risk assessments need to be in Active state to be selected, they would normally be for the same location, but this is not validated.
• Risk Rating – This read-only field displays the most significant risk ranking from the associated risk assessment.
• Risk Based Priority – This read-only field displays the most significant risk priority from the associated risk assessment.
• Risk Type – This field is for recording the most likely type of risk exposed at this location. There is no value list. Values may be Health, Safety, Environment, Production.
• Risk-Based Inspection Code – The level determined from a Risk Based Inspection assessment. This is normally associated with pressurised vessels (stress cracking) or structural elements (corrosion). The level is used to determine the frequency of inspection. This field is supported by a value list but the ALN domain PLUSGRBICODE will need to be configured.
• Safety Integrity Level – The Safety Integrity Level resulting from an assessment into functional safety according to IEC61508. The values are 1 to 4 where SIL4 is used to protect against the highest risks.

Characteristics Tab

This tab will be mainly used for Valves and Piping.

State section

This section is mainly associated with the assessment of valves that are closed under normal operation and whether they have been found to be leaking internally. There are also fields to indicate whether the location is considered temporary.

• Temporary – A checkbox to indicate that this location is temporary. When checked the Temporary Until date becomes mandatory.
• Temporary Until – This date (and time) field is read-only and becomes enterable when the Temporary checkbox is checked.
• Passing Valve – This checkbox is used with valves to indicate that they have been checked for leakage. These are valves that are set to closed under normal operating conditions but can still leak internally. Acoustic techniques can monitor that the valve is fully sealed.
• Last Checked Date – The date/time when the valve was last checked for internal leaks.
• Risk Assessment – The risk assessment performed when the valve was found to be passing (leaking). There is a Select Value and Go To Risk Assessments. Only risk assessments at Active state can be selected.
• Leaking – A checkbox to indicate whether the asset at the operating location was found to be leaking.
• Leak Details – The details of the leak. The field has rich text formatting (4000 characters).

Piping section

This section is used for identifying the pipeline, its characteristics and when it was last inspected. There may be some duplication with data recorded in the Location Specification to look out for.

• Piping Type – The type of pipe that is used at this operating location. There is a value list with values of Pipeline, Process, Small Bore.
• Reference – This field is used for a document reference or an identifier (20 characters).
• Line Number – The piping line number (20 characters). There is normally a line numbering scheme that will uniquely identify the line number on a P&ID and this becomes the tag number. There is normally a master Line List or Line Designation Database or Piping Register.
• Line Class – The classification of the pipe (20 characters). This may be the material type and whether it is seamless or welded.
• Last Inspection Date/Time – The date/time when the pipeline was last inspected.
• Inspected By – The person who last inspected the pipeline. There is a Select Value and Go To People (HSE). The person needs to be in an Active state to be selected.
• Rating – A field to record the pressure that the pipeline is designed to withstand (20 characters).
• Process Medium – The type of process medium that the pipeline carries. This is supported with a value list with values of Cement, Fuel, Hydraulic, Methane, Mud, Water.

Failure Analysis Tab

This tab is for performing a failure analysis for this operating location and its components. There is a similar tab on the Assets (HSE) application. You can determine how to address each failure mode and assess the risk of the failure occurring and what follow-up actions should take place.

Failure Analysis Details section

• Summary – A summary of the failure analysis and method used (50 characters).
• Details – The details of the failure analysis and methods used with Rich Text Formatting. It is the long description of the summary field.
• Failure Analysis Type – The type of failure analysis performed. There is a value list with values of FMEA, FMECA, RCM.
• Start – The date/time the failure analysis is due to start. The date selected cannot be earlier than today and it must be earlier than the Complete date.
• Complete – The date/time the failure analysis is due to finish. It must be later than the start date.

Failure Modes table window

• Line Number – The line number has an increment of 10. It is the most likely field for sorting the records in the table window.
• Description – The failure mode description. This field has a long description which could be used for the possible causes of this failure mode.
• Failure Class – The class of the failure, the top level in the failure hierarchy. Supported by a Select Value and Go To Failure Codes. The description of the failure class is shown alongside, with supporting long description.
• Problem Code – The problem code associated with the selected failure class. It is supported with a Select Value, it has to have been previously set up in the Failure Codes application, hence is likely to be created after completing the failure analysis. The description of the problem code is shown alongside, with supporting long description.
• Failure Mechanism Code – This field is supported by a value list with values from 1 to 6 whose descriptions are Mechanical, Material, Instrument, Electrical, External Influence, Miscellaneous. Changing a value in this field will blank the Failure Mechanism Subdivision Code.
• Failure Mechanism Subdivision Code – This field is supported by a value list with 38 values, for example 1.0, 1.1, 1.2 – which are all divisions of the Mechanical Failure Mechanism, for example, General – Mechanical, Leakage, Vibration. The value list will only show the subdivision codes for the selected value entered for the Failure Mechanism Code.
• Criticality – The criticality of the component in the operating environment at the location. This field has a value list with values of High, Medium, Low.
• Subunit/Component Code – A field to indicate the actual component that failed including the subassembly where the component exists. This is a text field of 50 characters there is no lookup.
• Maintainable Item/Part Code – A field to indicate the identity of the main part or subassembly that needed replacing or repair. It may be an item that is found in the Item Master (HSE) application. This is a text field of 50 characters, there is no lookup.
• Function – The functional impact of the failure associated with the failure mode. This is a long description field with Rich Text Formatting. There is a Function code field, but it is not visible without configuration.
• Effect – The effect of the failure mode. This is a long description field with Rich Text Formatting. There is an Effect code field, but it is not visible without configuration.

Failure Addressed By section

This set of fields identifies the ways that the identified failure mode has been addressed, it may be through preventive maintenance, condition monitoring or an operating policy/procedure. You can also identify the job plan/task to perform if the failure occurs.

• Operating Procedure – The operating procedure that addresses the type of failure identified. There is a Select Value and Go To Operating Procedures (HSE). Operating procedures have to be at Active state to be selected. The description of the operating procedure is shown alongside.
• Operating Policy – The operating policy that addresses the type of failure identified. There is a Select Value and Go To Operating Policies (HSE). Operating policies have to be at Active state to be selected. While there is an Operating Procedure that implements an Operating Policy, it isn’t copied when an Operating Policy is selected. The description of the operating policy is shown alongside.
• Preventive Maintenance – The Preventive Maintenance record that is implemented periodically in order to reduce the risk of the failure identified. There is a Select Value and Go To Preventive Maintenance (HSE). PMs have to be at Active state to be selected but they needn’t be associated with the same location, they could be associated with an asset of the location. The description of the PM is shown alongside.
• Job Plan – The Job Plan that will be used to address the failure if it occurs again. There is a Select Value and Go To Job Plans (HSE). Job Plans have to be at Active state to be selected. When selected if the job plan has tasks then the Task field becomes enterable. The description of the job plan is shown alongside.
• Task – This field is read-only until a Job Plan is entered. It is the task that is specifically created to address the type of failure that could occur. There is a Select Value showing the tasks of the associated job plan. The description of the job plan task is shown alongside.
• Measurement Point – The Condition Monitoring point that is implemented in order to monitor the condition that can lead to the type of failure identified. There is a Select Value and Go To Condition Monitoring. This should be a condition monitoring point of the location or a related asset. The description of the condition monitoring point is shown alongside.
• Item – The item associated with the failure mode identified. This is used to indicate that other assets or locationsA physical place where assets exist and where work can be performed. More that have the same item could also be affected by the same failure mode. There is a Select Value and Go To Item Master (HSE). The Select Value allows you to select a Tool Item. The item must be at Active status to be selected. The description of the item is shown alongside.

Risk and Consequence section

This set of fields uses the risk matrix to derive a risk ranking based on the potential consequence and likelihood of the failure mode occurring.

• Potential Consequence – This is the expected consequence of the failure mode occurring. There is a value list with the set of values being entered in the Risk Matrix (HSE) application.
• Potential Severity – This is the value of the severity field for the selected potential consequence and is derived from the Risk Matrix (HSE) application. It is a read-only field. Default values for severity are Critical, Major, Minor, Significant.
• Likelihood – The likelihood of the failure mode occurring. There is a value list with the set of values being entered in the Risk Matrix (HSE) application. The values are those associated with the selected consequence in the risk matrix, the values shown in the Risk List table window. The values might be Almost Certain, Probable, Significant, Unlikely, Rare.
• Risk Ranking – This read-only field shows the risk ranking associated with the consequence and likelihood in the risk matrix. It is not a value copied to the location and could therefore change if the risk matrix changes. The default values are Very High, High, Medium, Low.

Action Required section

• Recommendation – The action recommended for a failure of this type (20 characters). There is no value list, but there is a long description which could be shown instead of this field.
• Action By – The person who has been given the action. There is a Select Value and Go To People (HSE). Only People at Active state can be selected.
• Action – The follow-up action to be performed. There is a Select Value and Go To Standard Actions (HSE). Only Standard Actions at Active state can be selected.

Safety Critical Failures section

• Safety-critical – A checkbox to indicate that the location is or is part of a safety critical element.
• Safety-critical Element – A reference to an element (equipment or system) for example, pressure safety valve, that is critical to safety and associated with a regulation, for example, emissions of hazardous substances. A failure of a Safety Critical Element could cause or contribute to a major accident or incident. This field is supported with a value list which will need to be set up in order to be used. The ALN Domain is PLUSGSAFETYCRITREF.
• Barrier – A field to indicate the barrier that protects against a failure. This is supported with a value list with values of Process Containment, Detection System, Emergency Response, Ignition Control, Life Saving, Protection System, Safety Climate, Shutdown System, Structural Integrity.
• Regulation – The regulation associated with the type of failures at this location. The regulation must be at Active state. This field is supported with a Select Value and Go To Regulatory Compliance (HSE). It doesn’t have to be a regulation where the Applies To field is set to Location.

Calculations Tab

The calculations tab is used to store the results of mathematical calculations related to the operating location. These could be manually entered or if all the parameters to the calculation are stored in Maximo then it might be possible to use the Maximo Formulas functionality that was introduced with Maximo 7.6.0.6 in the Database Configuration application.

The Calculations Tab might be used to store values to support environmental consents. It has a table window.

• Calculation Number – This is the identifier of the calculation. It is an integer that starts at 10 and is incremented in steps of 10 for each new record.
• Description – Use this field as the title of the calculation (100 characters). It has a long description which can be used for notes to explain how the calculation is calculated and its dependencies, the parameters used in the formula.
• Calculation Type – The category of the calculation. This field is supported with a value list. There is a Synonym domain PLUSGCALCTYPE with values of Environmental, Integrity, Safety. Using a synonym domain provides a way of grouping the calculation types.
• Calculation Notes – Notes about the calculation that would be useful to the person reviewing the results of the calculation rather than the person who may have compiled the formula (500 characters).
• Calculated Value – The calculated value which can either be entered or calculated with a Maximo formula. It is a persistent field; the value will be recorded in the PLUSGLOCCALCULATE table.
• Unit of Measure – The unit of measure of the calculated value. It has a Select Value to the Units of Measure which can be entered in Classifications or Item Master applications.
• Consent Type – This is the type of environmental consent for which a calculated value may be recorded. There is a value list with values of Emission to air, Energy Usage, Emission to ground, Noise consent, Odour consent, Vibration consent, Waste Management, Emission to water.
• Validated – A checkbox to indicate whether the calculation should be validated.
• Validation – A read-only date/time field which is set to time now when the field Validated is checked.
• Validated By – The person who validated the results of the calculation. There is a Select Value and Go To People (HSE). Only Active persons can be selected.
• Regulation – The regulation associated with this calculation record, possibly the regulation associated with the consent type. There is a Select Value and Go To Regulatory Compliance (HSE). To be selected the regulation must be in Active state, it doesn’t have to be a regulation where the Applies To field is set to Location.
• Certification – The certificate that may be provided when consent has been granted. There is a Select Value and Go To Certifications (HSE). Certificates must be in Draft or Active state to be selected, they can’t be in Inactive state.

Review Actions Tab

The Review Actions tab allows a standard set of actions to be considered when performing a review, for example a review of the criticality. This uses a feature of the HSE product called standard actions which have two supporting applications Standard Actions (HSE) and Standard Action Groups (HSE).

A standard action is used for checklists or a set of review actions requiring a yes or no response. A standard action can require the user to provide a Yes, No, or Not Applicable response, an alphanumeric response, a score, or to mark the action as completed. A standard action can also have multiple review items. Standard actions are grouped together to make it easier to apply to other types of record.

Summary section

• Review Action Summary – A field for providing a short summary (200 characters) of the review actions.
• Total Score – A numeric field for recording the total score from the scoring provided on the review actions. There is no automatic calculation of the total score.

Review Actions table window

The icon at the end of the table window indicates that the standard action has one or more review items.  The user can update the table window directly. The descriptions below are in the order of that displayed in the table window details section.

• Standard Action – This mandatory field has a Select Value and a Go To Standard Actions (HSE). The Standard Action must have been previously defined and be in Active state.
• Description – This read-only field is the description of the Standard Action. It is often written in the form of a question. The long description can be used to provide additional guidance as to the meaning of the standard action.
• Standard Action Group – This read-only field is populated when the Standard Action Group button is used.
• Action By – This field is used to indicate the person who has the action. It is supported with a Select Value and a Go To People (HSE) menu. Selecting a person will blank the Action By Group.
• Action By Group – This field is used to indicate the person group who has the action. It is supported with a Select Value and a Go To Person Group menu. Selecting a person group will blank the Action By field.
• Repeatable – This read-only checkbox displays whether the standard action can be repeated multiple times when it is applied to a record.
• Action Category – This read-only field displays the category of the standard action.
• Review Action – This read-only checkbox indicates whether the standard action is of a review action type.
• Completed – Use the checkbox to indicate when the review action has been completed and the responses, review items and any comments have been added. It will add todays date and time to the Sign Off field.
• Sign Off – This read-only field is marked when the Review Action is completed.
• Comments – This field is used to provide a comment. If required a long description can also be provided.

Responses

The fields displayed in this section are dependent on the response settings on the associated Standard Action.

• Yes, No, Not Applicable – These three check boxes are displayed if the Yes or No response is selected on the Standard Action. The check boxes act like a radio button only one of them can be checked.
• Alphanumeric – This field is displayed if the Alphanumeric response is selected on the Standard Action. It does not have a lookup.
• Score – This integer field is displayed if the Score response is selected on the Standard Action. It does not have a lookup and it does not increment the total score field. Negatives are allowed.

Review Items

• This table window will display the Review Items of the associated Standard Action, if any. You cannot add additional review items, only respond to the defined responses and add a short comment. The response types are the same as those described for the standard action above. The scores do not total to the score field on the standard action.

At the bottom of the screen is a button to take the user to the Operational Actions (HSE) application.

Regulations Tab

This tab is for associating multiple regulations to the operating location. There is a Select Regulations button for adding multiple regulations in one action. When the location is referenced on a work order the regulation records are copied to it.

• Regulation – This is a mandatory field. There is a Select Value and Go To Regulatory Compliance (HSE). To be selected a regulation must be in Active state and have its Applies to field set to either LOCATION or GENERIC.
• Applies to Work Order Default – This checkbox is the default for a similar field on the Work Order Tracking (HSE) Regulations Tab. If checked here it means that the default on the work order indicates that the work order was completed in compliance with the regulation.
• All the other fields are read-only and display information from the regulation record found in the Regulatory Compliance (HSE) application.

Actions

Create

Follow-up tickets and work orders or other types of records can be created from the location:

• Service Request
• Incident
• Defect
• Investigation
• Work Order
• Risk Assessment

There is no Create MOC Request, Create MOC or Create Improvement actions but these could be added through configuration.

View Failure and Deferral History

This action shows the number of MOC Deferrals and the number of failures that reference the location over a period. The default period is 365 days, but this can be changed in OrganizationsA structural element of a Maximo database which is used for data sharing and is often aligned to a legal entity of an organisation. More (HSE) – Oil and Gas/HSE Shared Options – History Period. If it isn’t working, it may be because the Organization setting has the ability to disable the calculation.

• History Period (in days) – The default comes from the Organizations (HSE) setting, 365 days by default.
• Number of Previous Deferrals at this location for the History Period – This counts the number of MOC records where the MOC Type is DEFERRAL. MOC records at Draft status are included. MOC Requests are excluded. This is a read-only field.
• Number of Failures at this location for the History Period – This counts the number of work orders where the failure report includes a Failure Class and Problem Code. This is a read-only field.

View Operator Log Details

This action shows Operator Log entries that have been made for the location over a period of time. There is an option to include the location’s immediate parent or its immediate children, log entries made two of more levels up or down the location hierarchy will not be included. The Log Entries are those that were created in the Log Entry sub tab in the Operator Log (HSE) application.