Solution enhancements - HxGN EAM - 12.0.1 - Release Notes/Bulletin - Hexagon

HxGN EAM Release Notes for 12.0.1

Language
English
Product
HxGN EAM
Search by Category
Release Notes/Bulletin
HxGN EAM Version
12.0.1

The following is a list of enhancements that are included with this release of HxGN EAM:

Module

Product Enhancements

Administration

User Setup - a new field, Last Login Date/Time (Server), was added to the Record View tab of the User Setup screen. This protected field is populated by the system each time a user is successfully logged into the system through the base application, through a mobile application, or through a web service call.

Advanced Reports

Advanced Reports - Visualizations 11.0 and 11.1 are supported from within the application using Advanced Reporting tools. These can then be accessed by Report Consumers when made available.

Base

Base - When MOBSVSYN parameter is enabled, the MSRCLEANUP job will clean up the R5MOBILEDBSYNC table of all records older than 7 days.

Checklist Improvements

Task Plans | Checklist - Added a new checklist type called Dual Quantitative. This new type will allow entry of two numeric values, for example, the air pressure as found and as left. A second UOM value was added for this purpose. If you leave the second UOM blank the system assumes the same UOM for both values. A second set of slider control fields to support mobile was also added. This includes the minimum and maximum slider values (Minimum Slider Value 2 and Maximum Slider Value 2), the metric fraction slider checkbox (Metric Fraction Slider 2), and for the imperial measurements, the fraction dimension of 1/16 or 1/32 (Fraction Slider Dimensions 2). Also added as part of this enhancement is validation that the value entered is between a minimum and maximum value. The minimum and maximum slider already force this on mobile, but in base EAM the entered value was never validated. If you select the new checkbox called Min/Max Validation and enter the minimum and maximum slider values, the system will now raise an error if values are entered outside the range. Along with this update, we enhanced the checklist tab on the work order and the equipment screens, and the operator checklist screens to use this new checklist type.

Checklist Improvements

Work Orders | Checklist - Added the work order activity user defined fields to the Checklist Details section at the top of the Checklist tab. The user defined fields are hidden by default, so please use screen designer to unhide the relevant ones if you want to use this option.

RCM Improvements

Equipment (A/P/S/L) | RCM - Increased the length of the description of the Function, the Functional Failure, and the Failure Mode from 80 characters to 255 characters on the RCM tab of the Equipment screens and the RCM Templates screen.

RCM Improvements

Case Management | Failure Modes - Increased the length of the description of the Function, the Functional Failure, and the Failure Mode from 80 characters to 255 characters.

Checklist Improvements

Work Orders | Checklist - Increased the length of the checklist item description from 80 characters to 255 characters. Support for this extended length was provided on all checklist screens and tabs throughout the system, for example, the operator checklist, case management checklist, etc.
Note that the creation of nonconformities from the checklist is influenced by this change. Nonconformities can be created for certain checklist items after a review of the checklist when the reviewer signs the Reviewed By. This process copies the checklist item description into the nonconformity description and may now be truncated to fit the shorter 80 characters of the nonconformity description.

Checklist Improvements

Task Plans | Checklist - Increased the length of the checklist item description from 80 characters to 255 characters. This also impacted the checklist tab of the job plans screen and the translation popup. Support for this extended length was provided on all checklist screens and tabs throughout the system, for example, the operator checklist, case management checklist, etc.
Note that on the checklist tab of the work order screen, the creation of nonconformities is influenced by this change. Nonconformities can be created for certain checklist items after a review of the checklist when the reviewer signs the Reviewed By. This process copies the checklist item description into the nonconformity description and may now be truncated to fit the shorter 80 characters of the nonconformity description.

Date and Date/Time fields on Summary View

The summary grid will now show Date and Date/Time fields for all 3 grid modes. This is for informational purposes only, and there will be no searching capability for these types of fields.

Drag and Drop Capability for Document Attachment

The Create/Upload Document pop-up was updated to enable a user to 'drag & drop' a document into the pop-up, to be uploaded to the system. Additionally, a new toolbar button, the Create/Upload Document button, was added to permit the user to invoke the Create/Upload Document pop-up directly from the toolbar without having to navigate to the Documents tab of any screen for which document association is permitted.

EAM Restful Web Services

EAM tables, R5alertdataobjects and r5trackingdata will have REST web service support.

EAM Restful Web Services

GIS features and functionality related to maps and equipment will have REST API support

GIS

Support was added to the HxGN EAM Add-In for ArcGIS Pro to support creating HxGN EAM equipment records from GIS features that are accessed through ArcGIS Online hosted feature services; and for synchronizing attributes between equipment records and GIS features from ArcGIS Online. This support includes the ability for a user to perform equipment creation and/or synchronization of attributes wither manually or as a scheduled task (i.e., auto-sync).

GIS

EAM will now support ESRI ArcGIS Enterprise v11.0 for EAM v12.0.1, except for the ArcGIS Pro Add-In which will remain at ESRI v10.9. See the EAM Hardware & Software Guide for more details.

Integration Configuration

The Integration Configuration screen will be used to define and manage OAuth 2.0 protocol configuration connection details.

Integration Configuration

The user will be able to download the SAML metadata file regardless of the status of the IDP upload.

Integration Configuration

The Integration Configuration screen will support generation of up to two API Keys for an Application Name for a single specified user.

Integration with SDx Tag Info Map

The integration of EAM to SDx will allow the EAM user to view and access information stored in SDx for position records. To support the integration of EAM to SDx, the SDx Integration Configuration screen will be used to populate all the required parameters.

Integration with SDx Tag Info Map

The integration of EAM to SDx will allow the EAM user to view and access information stored in SDx for position records. The user will click the Tag Infomap button on the Positions screen to view the associated Tag Infomap in SDx

Mappings between Digital Work and Transit screens

Screens - Add New Field 'Mobile Deep Link Mapped Screen' to Support Deep Linking. With EAM Transit supporting cloning of work order screens and the new capability of navigating between EAM Transit and Digital Work, this field was developed to support creating the relationship between various work order screens created for either mobile application, but in reality, serve the same use case. This field will be protected when on any other screen besides a work order screen record. When opened, the list of values will show the opposing application's work order screens, that once selected, are used for deep linking between EAM Transit and Digital Work.

Python Studio

Python Scripting - A new 'processing' table (back-end only) has been created to hold enough information about the Python script that needs to be executed and EAM information that needs to be passed into the script for it to perform its intended task. Each time a Flex Business Rule or Alert executes because conditions have been met for a Python script to be run, a record is inserted into this 'holding' table with the relevant data. This table is called R5PYTHONEVENTS. Contents of this table can be viewed using a user-defined grid created on the Grid Designer screen in EAM.

A new Flex Python Driver job has been created, that when activated, will process records in R5PYTHONEVENTS into the Flex Python execution framework API for execution of the identified Python script.

See the HxGN EAM Python Framework Technical Reference document and the HxGN EAM Python Framework and Flex Python Scripting brief for more details.

Python Studio

Python Scripting - A new screen has been added to the Administration > System Configuration menu called Python Studio. When selected, this function will NOT open a screen in EAM, but will instead open a new window to display the Python Studio environment, where Python scripts can be created, published, and maintained.

It will NOT be necessary for the EAM user to login into Python Studio if the necessary configuration has been performed within EAM and the EAM tenant has access to Python Studio.

See the HxGN EAM Python Framework Technical Reference document and the HxGN EAM Python Framework and Flex Python Scripting brief for more details.

Python Studio

Python Scripting - Added a new EAM integration with Python Studio. Alerts and Flex Business Rules, when executed, can now cause Python scripts created by your system administrator to be run. Python scripts can make wanted changes inside EAM and/or other systems. The Documents screen in EAM will be used as the script repository. Each Python script created and published will have an associated Document record in EAM. The Python script will be uploaded to the Document record. The Python execution framework will execute the script stored with the Document record when called.

Several new fields have been added to the Document screen record view to keep information necessary to distinguish 'Python' documents from other documents in the system and to store the required information. These fields include the following: Python Script Type, Python Script Executable Document, and Python Script Owned By. All these fields are protected and are only populated by this integration.

  1. A newly delivered Dataspy called "Python Scripts" has been added to the Documents screen to display Python documents.

  2. Any Document where Python Script Type is populated will NOT be displayed for use in the system in the same locations as other documents.

Python Studio

Flex Python Events - New screen to View Python Events. This new read-only entity will provide a mechanism for users to view all of the Flex Python Events that have been requested with the status and invocation source (Alert or Flex Business Rule trigger). The log file will be an attached document on the Flex Python Event record that can be downloaded and viewed from this screen. It will support comments and documents, the same as any other entity, to provide Python authors with a meaningful place to associate any documents and/or comments that are created during a Flex Python execution event.

Python Studio

Alert Management - Added a new Alert Type: Flex Python. When this check box is selected, the new Flex Python Alerts tab becomes enabled.

Alert Management | Flex Python Alerts - This tab should be used to define parameters used to populate records into the table R5PYTHONEVENTS. This is a back-end-only table used to 'stage' records for processing into the Flex Python Execution Framework API by the Flex Python job.

See these feature briefs for more details:

Python Studio

Dataspy - Display Grid ID & Dataspy ID on the advanced tab of the Dataspy view. Displaying the Grid ID and Dataspy ID on the advanced tab of the Dataspy view would assist advanced users in identifying which Grid/Dataspy they are observing in base for use in REST Grid web services, troubleshooting, and many other scenarios.

Python Studio

Python Studio | Configuring cloud-based EAM integration - At this time, only cloud-based EAM is supported. Whenever EAM attempts to open Python Studio or connect to the Flex Python Execution Framework API, the system will get the necessary URL and credentials for these connections from a configuration file populated by the cloud operations team.

Root Cause Analysis

Case Management | Fishbone - Added a new tab where a fishbone diagram (Ishikawa diagram) is displayed. The fishbone diagram is based on the entered root causes associated with the case. The diagram shows the Problem Description of the case, the Root Cause Categories of the root cause records, and the primary causes recorded in the Why 1 field of the root cause records. And by clicking any of the Root Cause Categories you can drill down one level and view the secondary causes of the listed primary causes. The secondary causes are recorded in the Why 2 field of the root cause records.

The tab has a Brainstorm button. If you click this button the system will open a popup where you can quickly enter the root cause data used on the diagram. Note that entering data on this pop-up is the same as entering data on the Root Causes tab of the Case Management screen. The difference is the pop-up has a specific focus (the diagram) and therefore only has a limited set of fields present.

Root Cause Analysis

Case Management - Added a Deep Dive check box. When you select this checkbox and click save, the system will add deep dive tasks to the list of case tasks already present. Tasks may be inserted anywhere in the list of existing tasks based on their assigned Sequence and Step. The tasks that will be added are determined by the selected Deep Dive Service Code of the case Organization (see Organizations screen) and may include additional task comments, documents, and a checklist. Added tasks may also influence the scheduled and requested start and end dates of the consecutive tasks depending on the setting of the Organization option CASECASC (automatically cascade scheduling dates for tasks). Deep dive tasks can also be removed again simply by de-selecting the Deep Dive check box and saving the case record. On the Tasks tab, the added deep dive tasks are also marked for easy identification by a new protected check box that is also called Deep Dive.

Additionally, two more check boxes were added to the Record View, called Safety Consequences and Environmental Consequences. There is no additional functionality related to these.

Root Cause Analysis

Case Management | Documents Lists - Added a new Documents List tab. This tab offers the same functionality as the Documents tab, but additionally also lists all documents that are associated with any of the tasks of the case. The documents related to the task can be viewed here. However, it is impossible to add or delete these documents on this tab. That still must be done directly on either the Task tab of the Case Management screen or on the Documents tab of the Case Management Tasks screen.

All documents related to a case task will have a source type referencing the case management task entity and will show the task number and, between parenthesis, the task sequence in the source code field. For example, 10018 (3).

Root Cause Analysis

Case Management | Tasks - Added a Comments Attached and Documents Attached field. Both fields are counters and indicate how many comments and documents are attached to the task.

Root Cause Analysis

Case Management | Related Cases - Added this new tab where cases can be selected that relate to the selected case on the Record View. Maybe because they both are about an oil spill, or both concern a root cause analysis on the same equipment. Select the Related Case and fill in any of the available user defined fields, if desired. Once a relationship has been established, it is only one record, you can view, update, and delete this record on this tab starting from either case.

Root Cause Analysis

Case Management | Corrective Action - Added a Campaign field. This field can only be entered if equipment is selected. And then once you click Apply Corrective Action or Apply Corrective Action to All the system will add the equipment to the Campaign and will select the Campaign Applied checkbox. The system will then show a few details of the relationship, like the Campaign Survey Line Status, the Campaign WO and WO Status, and the Multiple Equipment Parent WO checkbox. Unlike for the RCM data, there is no button to remove the equipment from the campaign again. But if needed you can do this manually on the Campaign screen itself.

Root Cause Analysis

Case Management - Added a View All Comments button. This button will give access to a popup where all comments associated with the case and any of its associated tasks can be viewed. Comments can be viewed only, but the button should allow for much faster access to all comments associated with the case tasks. A similar button was added to the Case Management Tasks screen.

Root Cause Analysis

Case Management | Root Causes - Added a new button called Update Work Order. This button will copy the Problem Code, Failure Code, Action Code, Cause Code, Failure Mode, Symptom, Tactical Cause, Human Factor, Workmanship, Human Oversight, and Method of Detection from the selected root cause record to the work order that is associated with the case. Use this button to update the work order after the root cause analysis is completed and the proper closing codes are identified. Note that it is still possible to update the work order from here, even if it is already completed. Also, note that the Failure Mode is only copied if the equipment of the work order is still the same as that of the case.

Root Cause Analysis

Work Orders - Added a button called Create Root Cause Analysis. This button will use the Root Cause Analysis Service Code of the work order Organization (see Organizations screen), and with that service code, the system will create a new root cause analysis case on the Case Management screen. The case will be populated with the work order data like Description, Equipment, Location, Department, Downtime Cost, Downtime Hours, Problem Code, Failure Code, Action Code, Cause Code, Failure Mode, Symptom, Tactical Cause, Human Factor, Workmanship, Human Oversight, and Method of Detection. The case Problem Description will be set equal to the work order Description. The new case will be created in the request status. More than one case can be created from the same work order if needed, But the system will ask for confirmation after the first case is created. Note that the work order does not show that any root cause analysis cases have been created for it.

Root Cause Analysis

Case Management | Failure Mitigation - Added the Effect Indicator and the Effect Consequence from the selected Failure Mode as visible fields on the screen. Added the same fields also to the RCM Failure Mitigation tab of the Equipment screens and the RCM Templates screens.

Screen Setup

Screen Setup - Allow for Mobile Work Orders (WCJOBS) and clones of this screen to be accessed for individual filtering per screen. This will allow the user to display multiple Work Orders within the Mobile Transit application, but only show specific datasets, filtered by Type or Class for example.

SSO configuration for HxGN EAM

A new section will be added to the SSO Configuration screen to support the ability for a client to import an Identity Providers metadata file to EAM. This will be an XML file, and it will automatically configure Hexagon’s federation server (Ping Federate) to connect to the customer’s IDP. The metadata file will be used for browser based SAML authentication. It is not used for either OIDC or ws-trust.

SSO configuration for HxGN EAM

The SSO Configuration screen will be used to support Single Sign-On authentication. Both WS-Trust and OIDC configuration will be supported using the parameters populated on this screen. A customer may choose to configure both WS-Trust and OIDC; these are not mutually exclusive.

The WS-Trust settings populated on the SSO Configuration screen will be the default settings to enable tenant specific configuration and will override any customer information stored in yaml files. While on-prem customers can use this screen to store WS-Trust configuration, this screen will be used in the cloud to facilitate tenant specific WS-Trust settings. This screen also supports OIDC configuration in place of using install parameters and will incorporate validation logic to ensure all required fields for OIDC authentication are populated.

User Defined Screens

Preventing duplicate browser tabs - If the user is on an EAM screen in the browser and then opens a duplicate tab from there, the system will now raise an error indicating the duplicate tab should be closed. The reason for this change is that duplicate tabs share the same session id which in turn causes issues.

Some examples of these issues are:

  • If the user is on the same screen (that has more than 50 records) on both tabs and scrolls down to fetch more records on one tab, then does the same for the other, the system will show an unspecified error (unable to retrieve text).

  • If the user does an action on one tab and then closes it, and then does an action on the other tab, the system will then go to the login screen on that remaining tab.

Instead of duplicating tab the user should open a new tab or new browser window and log in to the system independently.

Voice of the Customer

About Window - Add fields to display the License Type and number of Licensed Users. Providing license information in the About window will provide context to users and/or administrators the current license type (Named or Concurrent) and the total number of licenses for the EAM environment to ensure that the information is correct, and users are maintained accordingly.

Voice of the Customer

If there is a failed email notification transmission, the recipient(s) that did not successfully receive the notification will be recorded in the R5FAILEDMAILRECIPIENTS table along with the associated device. If an individual recipient has multiple registered devices, a transaction would be recorded for each registered device with a failed notification transmission in this table. The user will click the Notification Failures link button from the Email Viewer screen to review this detail.

Voice of the Customer

Screen Designer - Screen Code is available to be reviewed via the right-click option, View Field Details. This will allow the user to identify what the screen code value is for the selected screen.

Voice of the Customer

Additional options were added to the QUICKDEF install parameter, which defines the default value for the Operator field on the Quick Filter portion of the Search Bar, as well as the Dataspy and Column Filtering. The new options added in this release are E for ‘Equals', EW for ‘Ends With’; in addition to the existing options of S for ‘Starts With', C for ‘Contains'.

Voice of the Customer

Case Management functionality in EAM will now have inbound BOD support (EAMCaseManagement)

Voice of the Customer

Equipment (Structure & Structure Details tabs), Equipment Configuration (Structure tab), Equipment Lookup (Structure tab) - A new icon has been created for display in the equipment tree structure for equipment/locations/equipment configurations that are 'Out of Service'.

If the 'Out of Service' checkbox is selected for the record displayed in the tree structure node, the system will display the new out of service icon on the node. This new icon could be displayed along with the existing 'No Cost Rollup' icon if both conditions are satisfied.

Voice of the Customer

Equipment (A/P/S/L) | Event Log - Added an event log tab on the Assets, Positions, Systems, and Locations screens. On this new tab, you will find all audit records for any of the equipment base fields, custom fields, and related comments combined in one view. Additionally, you can enter event log records manually and use any of the available user defined fields for these entries if needed. The Event Type selection for these manually entered log records can be configured on the System Codes screen using Entity ELTP (Event Log Type) and System Code OBJ (Equipment). The tab only allows insert, update, and delete of log records are not allowed.

Voice of the Customer

Support was added for GIS layers sourced from geodatabases having the GISOBJID field defined in lowercase (i.e., 'gisobjid') to multiple screens in the system; including the GIS Map Search screen, the GIS Map WO Dispatch screen, and other pop-ups displaying map images.

Voice of the Customer

Support was added for GIS layers sourced from geodatabases having the GISOBJID field defined in lowercase (i.e., 'gisobjid') to the HxGN EAM Add-In for ArcGIS Pro.

Voice of the Customer

When a PO is copied and it has IS WOs on the lines, the system will create a new IS WOs for each line.

Voice of the Customer

Task Plan /Job Plan Instructions - In previous versions, the Instructions tab and instructions pop-up have considered the values of the following checkboxes on the User's record to determine if the instruction can be edited. In other words, the appropriate checkbox must be selected before editing is allowed, depending on who created the instruction record:

  • Allow Editing of Other's Comments

  • Allow Editing of Own Comments

Starting in v12.0.1, Instruction tabs and Instruction pop-ups will always behave as if both of these checkboxes are selected.

Instruction tabs and pop-ups include:

  • Task Plan | Instructions tab

  • Job Plan | Instructions tab

  • Task Plan | Jobs tab | Add/Edit Instructions action link

Voice of the Customer

Task Plans - Added the ability to change the Enable Enhance Planning checkbox in update mode. The change is only allowed if no data is associated with the task plan yet that would cause an inconsistency. For example, you cannot select the check box if the Isolation Method check box is selected, or if any of the responsibility fields are filled in, or if a checklist item is associated with the task plan that is not supported with this selection. Or alternatively, you cannot change it to unselected if a material list is associated, or if any jobs are associated.

We have also changed the default for the check box to unselected when you insert a new task plan, and the installation parameter PLANLEV is set to EITHER.

Voice of the Customer

Generate Requisitions - The Requested Before date on the requisition line for parts and the Due Date on the purchase order line for parts are both calculated using the part lead time. This part lead time, however, was calculated slightly differently on several screens and processes, causing small inconsistencies. With this release, these inconsistencies have been removed and the part lead time is now determined as follows:

  1. Internal Lead Time (Days) from the Stores screen +

  2. One of the following lead times

  • Lead Time (Days) from the Stores tab of the Parts screen if the Preferred Supplier matches the Supplier of the requisition or purchase order line.

    • Or if empty, then Lead Time (Days) from the Suppliers tab of the Parts screen.

    • Or if empty, then Lead Time (Days) from the Suppliers screen.

    • Or if empty, then Lead Time (Days) from the Stores tab of the Parts screen if the Preferred Supplier and the Preferred Store are both blank.

    • Or if empty, the value of the install parameter DEFLDTIM, providing it is a valid positive whole number, otherwise the system will use 0 (zero).

  • If you enter a lead time of 0 (zero) in one of these that value will be used as the field is not considered empty. This was one of the inconsistencies where the Parts tab of the Requisitions screen ignored the 0 and treated that as empty.

  • The lead time calculation for parts for store-to-store requisitions was not affected by this change.

Voice of the Customer

Task Plan/Job Plan Instructions - These instructions are intended to be viewed on Work Orders, Standard WOs, and PM Schedules. However, an issue has allowed instructions to be updated on these screens. These updates were being saved back to the underlying Task Plan/Job Plan, which is NOT correct. A change has been made so that the instructions are viewed in "fully protected" mode on Work Orders, Standard WOs, and PM Schedules.

The pop-up should always be opened in ‘fully protected’ mode in the same way it is currently opened with the View PM Activity Comments pop-up is opened from Activities for Work Order.

Screens/tabs where this change was made are:

  1. Work Order | Activities - Click View Task Plan Instructions action to get instruction pop-up

  2. Work Order | Jobs - Click View Job Plan Instructions action to get instruction pop-up

  3. PM Schedules | Activities - Click View Task Plan Instructions action to get instruction pop-up

  4. Standard WOs | Activities - Click View Task Plan Instructions action to get instruction pop-up