Solution enhancements - HxGN EAM - Release Bulletin - Hexagon

About EAM

Language
English
Product
HxGN EAM
Search by Category
Release Bulletin

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

Module

Product Enhancements

Administration

Locales - Added a new Date Format DD.MM.RRRR.

Administration

Import Configuration | Batch Document Upload - Added two small improvements. (1) It is not possible anymore to upload the same filename more than once per session. This will prevent overwriting files with different content just because they have the same name. (2) Empty files will not be added to the grid anymore. Before you could add them to the grid, but the system would not upload them.

Administration

Organizations | Options - An additional option 'COMPLETE' will give the same ability as 'RESTRICTED', with the exception of allowing the WO to close as if the option was set to 'OFF'. This option will give the Transit app the ability to provide a count based on RESTRICTED criteria, but still, allow closure without all required checklist lines needing to be completed.

Administration

The Role Setup screen was enhanced to support being able to select only the Mobile checkbox for a role record without also having one of either the HxGN EAM or Requestor checkboxes selected at the same time. Additionally, the Digital Work App drop-down was added to the HxGN EAM Products section of the screen. Role records that do not have the HxGN EAM or Requestor checkboxes selected but do specify a value for the Digital Work App field are now supported.

Administration

Organization | Options - CHCKLFUP can generate follow-up work orders and deferred maintenance activities at different points throughout the checklist process. At Review, Perform or at Closure.

Administration

Tables with high transaction volumes can experience incomplete synchronization to Data Lake, that is, some data records may be missing from Data Lake upon close examination. This is primarily caused by updates of data in EAM performed in batch mode. The current topology does not support thread synchronization between EAM, the Data Lake utility, and batch jobs, and contributes to partially committed records in EAM being transmitted to Data Lake.

A process has been devised to avoid selecting records saved within a designated time window from the time of Data Lake schedule execution. This window can range from 5 minutes up to 60 minutes, with 5 minutes being the most frequent interval allowed for Data Lake schedule execution. This process will be supported by the install parameter DLHOLD. By applying the DLHOLD install parameter, the Data Lake utility will process records that have a xxx_lastsaved value between lastupdatedate and the current processing time less the value of DLHOLD [minutes]. This will facilitate bypassing records committed to the database with a xxx_lastsaved value proximate to the current execution of the Data Lake schedule and these records will be processed in the next execution of the Data Lake schedule.

Administration

Equipment Overview 360 - Added a new widget that supports running Cognos reports on the overview screen. For the report to work, it must be defined on the Reports screen with Class REPC and have a SEL_OBJ and SEL_ORG parameter on the Parameters tab. You must also have security access to the report via the menu. Otherwise, it will not show on the widget. Some standard reports are accessible this way. Be warned that these reports are not designed for this widget and may give unexpected results. For details, see the HxGN EAM Equipment Overview 360 brief.

Base

All documentation, including the HxGN EAM Help resources, will be made available on the Hexagon ALI documentation site (https://docs.hexagonali.com) starting with the HxGN EAM 12.0 release. The URL to which all Help entry points in the system are directed has now been updated to reflect this change.

Administration, GIS

Added support to retrieve the mobile user's ArcGIS credentials from the EAM user record in base EAM. The fields used are ArcGIS Server Username and ArcGIS Server Password. These credentials will be used to gain access to any secured ESRI GIS service consumed on the Digital Works app if valid token cannot be found on the device. The purpose for this improvement is to try to reduce the opportunity for login prompts while using GIS functionality. A prompt will be displayed if there is no valid token and valid ArcGIS credentials cannot be retrieved from the user's record.

Calibrations

Calibrations improvements:
2 new options for controlling the behavior of precision-controlled fields used for calibration processes within EAM have been added. These changes specifically deal with how trailing zeros after the decimal are handled and other precision rules. Existing customers will be able to continue to use the pre-v12.0 behavior, if desired, or change to one of the new options. In summary, there will be 3 total options for controlling precision behavior.

A new installation parameter called CALTZERO will control which option is selected. Valid values are 'A', 'B', and 'C. The default will be 'A'.

CALTZERO = A (i.e., this is pre-v12.0 behavior):
o EAM does NOT store trailing zeros entered by the user. In general, Number fields in our system do NOT store or display trailing zeros when entered after a decimal. This is standard database behavior. When a calibration technician gets a Device Reading of 105.120 during a calibration and they enter this value into our system, EAM stores/displays this value as 105.12. EAM does NOT keep up with trailing zeros entered by the user.
o EAM automatically adds enough trailing zeros so the number of decimals matches the Precision (calibration specific functionality in EAM) defined on the test point or device, even if the user does NOT enter these trailing zeros. These trailing zeros are displayed on the front-end only. Trailing zeros are added to specific calibration fields on the equipment and work order screens if the user enters a value and the number of digits after a decimal do NOT match the Precision defined i.e. Precision = 2 and user enters 25.1, the system will automatically add a trailing zero to match the Precision i.e. value displayed as 25.10.
o The user is NOT allowed to enter more non-zero decimals than the defined Precision.

CALTZERO = B (i.e. new option 1):
o Trailing zeros will NOT be automatically added to precision-controlled field values to match the defined Precision.
o The user is allowed to enter less decimals than the defined Precision AND the system will NOT add trailing zeros automatically to match Precision.
o If trailing zeros are manually entered by the user, these trailing zeros will be maintained and displayed.
o User is NOT allowed to enter more decimals than the defined Precision.

CALTZERO = C (i.e., new option 2):
o Trailing zeros will NOT be automatically added to precision-controlled field values to match the defined Precision.
o The user MUST enter the EXACT number of decimals specified by the defined Precision i.e. the user cannot enter less, or more decimals than Precision.
o If trailing zeros are manually entered by the user, these trailing zeros will be maintained and displayed.
o User is NOT allowed to enter more decimals than the defined Precision.

Note: See the Calibrations Brief for more details.

Checklists

Aspects | Nonconformity Types - Added the Severity field. The Severity will not default from the selected Nonconformity Type but can be manually updated by the user as required. The selected Severities will be made available on the checklist items of type Nonconformity Check.

Checklists

Work Orders | Activities - Because of the new Severity field on the Nonconformity Type tab of the Aspects screen, the maximum number of possible severities associated with the generated checklist item was increased from 50 to 400. Like before, the resulting Severity lookup will show these severities on, for example, the Checklist tab of the Work Order screen.

Checklists

Work Orders | Checklist - Added a new Documents Attached field displaying the number of documents associated with the checklist line. Additionally, the Comments checkbox was renamed Comments Attached and now displays the number of comments attached to the checklist line. Note that this counter includes all comments in all languages. The View Checklist Item Comments popup was adjusted accordingly to show all comments from all languages.

Checklists

Equipment | Work Order Checklists - Added a Documents Attached and Comments Attached field displaying the number of documents and comments associated with the checklist line on the Checklist Items popup. Comments can be viewed from here by selecting Actions and then View Comments. Documents have a similar option, but this popup can also be activated by double-clicking the line. Note that the Comments Attached counter includes all comments in all languages. The View Comments popup was adjusted accordingly to show all comments from all languages.
Similar changes were applied to the Operator Checklists tab and the Checklists tab of the equipment screens. Note that on the Checklists tab, a Comments Attached checkbox existed already. This checkbox was replaced with a counter as well.

Databridge

The inbound ReceiveDelivery BOD will support populating the Received By field (R5DOCKRECEIPTS.DCK_RECEIVER) on the PO Receipts screen

Ecosys Integration

An integration between EAM and EcoSys has been developed to optimize Investment Plans and enable businesses to better use their capital funding. If the integration is enabled, the user will have visibility to two new buttons on the Investment Plan screen, Launch EcoSys and New Scenario. The Launch EcoSys button will allow users within EAM to launch an active session of EcoSys and review, modify, or approve investment plans. The New Scenario button will launch the Scenario popup screen where the user can create an investment Scenario that references one or more investment plans. When the popup opens, it defaults the selected investment plan Description to the Scenario Name and it also adds the plan to the scenario. You can then manually add more investment plans if desired. When the user activates the Scenario, EAM will send notification to EcoSys that investment planning data is ready for further review and processing. For details, see the HxGN EAM Investment Planning brief.

Equipment Configuration

Equipment Configuration | Configurations Associated - Introduced the ability to control how many children are created on the Equipment Generation screen. For this purpose, the following fields were added to the Configurations Associated tab on the Equipment Configuration screen: (1) Default Quantity - Enter how many children you would like to generate. If you leave this field blank, the system will assume one must be generated. (2) Allow Variable Quantity - If selected, this checkbox allows you to change the quantity generated. If unselected, the quantity will be fixed and equal to the Default Quantity entered here. (3) Minimum Quantity and Maximum Quantity must be entered if Allow Variable Quantity is selected. These two fields can define the minimum and maximum quantities that can be generated. You can set the minimum equal to zero if you want to give the option to exclude the child from the generation.

Equipment Configuration

Equipment Generation | Details - Introduced the ability to control how many children are created. For this purpose, the following fields were added to the Details tab on the Equipment Configuration screen: (1) Exclude Equipment - If this checkbox is selected, the equipment, and any of its children, will not be generated. Whether this checkbox is available for selection depends on your settings on the equipment configuration screens. (2) Quantity - The number of children that will be generated for this level. This defaults from the Default Quantity that was entered on the equipment configuration screens. For details, see the HxGN EAM Equipment Configuration brief.

GIS-ESRI

A new 'View Log Files' button was added to the HxGN EAM Add-In for ArcGIS Pro to support the ability for a user to quickly & conveniently navigate to the folder location where the Add-In writes log files during the equipment creation & attribute synchronization processes. Log files are available through the %appdata%\Hexagon\HxGN EAM GIS Extensions\GIS Pro Logs (i.e., C:\Users\<username>\AppData\Roaming\Hexagon\HxGN EAM GIS Extensions\GIS Pro Logs) folder location.

GIS-ESRI

The HxGN EAM Add-In for ArcGIS Pro was enhanced to add a verified, trusted digital signature to the Add-In installer.

MS Projects

MS Projects - Supported versions of Microsoft Projects are 2016, 2019, and 2021. This included 32-bit and 64-bit installers.

Reports

Calibration reports have been updated to consider the new precision and trailing zero handling behavior implemented in this release. Any precision-controlled value displayed in a calibration report should appear as it does when viewed on the related EAM screen.

Root Cause Analysis

Case Management | Corrective Action | Map RCM Data - Added a new popup that you can access from the Corrective Action tab. On this popup, you can decide how the failure mode data of the case should be applied to the RCM tab of the selected Equipment or RCM Template. You can either map a new failure mode to an existing function or functional failure, create it as new or exclude it from the copy. For details, see the HxGN EAM Case Management brief.

Root Cause Analysis

Case Management | Root Causes - Added a new tab called Root Causes to support a root cause analysis. Root cause attributes like symptom, problem code, failure code, cause code, tactical cause, etc., can already be recorded on the case Record View, but this tab supports the ability to enter more than one root cause per case if needed. Additionally, you can enter a contribution percentage and two why fields for the root cause. There is also a link button to quickly create a record based on the data already entered on the Record View, and the tab supports user defined fields. For details, see the HxGN EAM Case Management brief.

Root Cause Analysis

Case Management | Failure Modes - Added a new tab called Failure Modes to support a root cause analysis but feel free to use the tab for your RCM project and collect all functions, functional failures, failure modes, and consequences for new equipment. The tab lets you define all data needed on the RCM tab of the equipment screens, but rather than using several pop-ups here, you can enter all the required data in one record. This also makes it much easier to load data using the import utility. For details, see the HxGN EAM Case Management brief.

Root Cause Analysis

Case Management | Failure Mitigation - Added a new tab called Failure Mitigation, where mitigation strategies can be defined for failure modes of the case. The tab works like the RCM Failure Mitigation tab on the RCM Template screen. For details, see the HxGN EAM Case Management brief.

Root Cause Analysis

Case Management - Added a question message when you change the Equipment and one or more records exist on the new Root Causes tab or the new Failure Modes tab that reference functions or failure modes from the RCM tab of the Equipment. The question will ask for confirmation to continue with the change. If confirmed, the system will accept the new equipment but will clear the Failure Mode field on all records on the Root Causes tab and delete all records on the Failure Modes tab where an Existing Function is filled in. This will also impact records on the new Failure Mitigation tab. These records will also be deleted if the related Failure Mode is deleted.

Root Cause Analysis

Case Management | Corrective Action - Added a new tab called Corrective Action to support a root cause analysis. On this tab, you can select Equipment or RCM Templates and then apply (=copy) the data collected on the Root Causes tab and the Failure Modes tab of the case to the RCM tab of the selected Equipment or RCM Template. The tab also lets you remove this case related data again if, for some reason, you would like to undo the changes on the RCM tab. And you have access to the RCM Mapping popup from here, where you can decide how you want to apply the collected data to the selected Equipment or RCM Template. For details, see the HxGN EAM Case Management brief.

Root Cause Analysis

Organizations - Added a new RCM Level field that will serve as a default on the Failure Modes tab of the Case Management screen under certain circumstances. It is not used as a default on the equipment screens. Additionally, we added two new fields related to the root cause analysis: Root Cause Analysis Service Code and Deep Dive Service Code. Currently, these fields are not used elsewhere in the system, but they were added in preparation for a future enhancement.

Root Cause Analysis

Case Management | Failure Modes | Edit Failure Consequences - Added a new popup that you can access from the Failure Modes tab. You can select the consequence of functional failure or failure modes on this popup depending on the RCM Level. The tab works the same as it does on the RCM tab of the equipment and RCM Template screens. For details, see the HxGN EAM Case Management brief.

Work

PM Schedules | Equipment - For fixed and variable PM schedules, the awaiting release work order, or in case of nesting the bypassed work order, will now be deleted immediately if Date Deactivated is entered and is set to today or a date in the past or if Date Deactivated is less than or equal to the PM work order Due Date. The same is also applicable for PM work orders with a Due Date (calendar-based) that are also meter-based. For PM Schedules that are meter-based only, the awaiting release work order will not be deleted if the Date Deactivated is in the future.

Note that a PM Schedule that is calendar-based and meter-based and that has a due date and a deactivation date in the future, but where the deactivation is earliest, the system will delete the awaiting release work order and therefore ignore any possible releases based on meter readings. If you still want the meter readings to release this PM work order, then the Due Date needs to be cleared.

Work

PM Schedules - Updated the Type dropdown to support the Define Drop-down Filter option in screen designer. Previously any defined filter would not work. After this upgrade a filter (for example des_code != 'F' ) will hide the Fixed option. Please note that any previously defined filters before this upgrade are now invalid and may cause the drop-down to show unexpected results.

WS Toolkit

Samples for modern Visual Studio Users have been updated