V4.3.0.0.0 Release Notes

• TFS312326
• TFS308868

• The Site ID column has been removed from the Analysis and System worksheets.
• The Analysis Type column has been removed from the Analysis worksheet.
• The Site Reference Name column has been added to the Analysis worksheet.

Previously, the ACA Data Loader did not import Site IDs related to ACA analyses. This issue has been resolved. Now, if you have a site assigned to an ACA analysis, it will be imported correctly.

Previously, if you configured ACA to send criticality indicators to an SAP CMMS, an error occurred when the GE Digital APM system attempted to send the information. This issue has been resolved.

• TFS241986
• TFS292976

• TFS85956
• TFS298164

• TFS274235
• TFS274234

In addition, the MI AHI Viewer group now has View permissions for the Policy Event family.

• TFS268475
• TFS248037

• TFS91046
• TFS86625
• TFS86430

• The All tab has been renamed to Implementation Packages.
• The following tabs have been added:
  • Maintenance Plans
  • Actions
• The Maintenance Plans By Type chart has been added.
• The Package Count chart has been renamed to Implementation Packages By State.

To facilitate these enhancements, the following Catalog items have been added to the folder \\Public\Meridium\Modules\Asset Strategy Management\Implementation\Queries:

• ASI Overview Page - Actions
• ASI Overview Page - Maintenance Plans
• ASI - Maintenance Plans by Type Count

• TFS309329
• TFS309318
• TFS309317
• TFS309313
• TFS309298

• The ASI Package workspace has a new layout.
• The WMI structure for packages has a new location.
• You can now send an individual action to a package instead of sending the entire strategy to the package.
• New URL routes have been added.

• TFS288568
• TFS283874
• TFS280619
• TFS277936

• The Measurement Location and Measurement Location Group families have been removed from the Has Work Management Item relationship definition.
• The Measurement Location Group, AMS Asset, GE Tag, KPI, OPC Tag, and Thickness Monitoring Task families have been removed from the Implements Action relationship definition.

Previously, when you implemented a package, no processing indicator appeared in the implementation window to let you know that the package was in the process of being implemented. This issue has been resolved.

Previously, if you created a new ASI package and saved, and then modified the fields in the package and saved the changes, a warning message incorrectly appeared, stating that the current entity was updated by another user. This issue has been resolved.

Previously, if you expanded the State Management dialog box, and then closed the active tab, the State Management dialog box remained expanded in view and incorrectly overlaid other open pages. This issue has been resolved.

This issue may have resulted in incorrect values appearing in these fields in GE Digital APM. This issue has been resolved.

Previously, when you cleared the Maintenance Strategy field in a maintenance plan and then saved the changes, the following issues occurred:

• The changes to the field did not reflect in the corresponding child WMIs.
• The Manage Cycles button was incorrectly disabled.

These issues have been resolved.

Previously, if you pasted a task list to a maintenance item that already had a task list, the copied record did not appear on the WMI tree (as expected, because there can only be one task list under a maintenance item), but a success message appeared for the paste action. This issue has been resolved. Now, if you copy a task list and then select a maintenance item that already has a task list, the paste button is disabled.

Previously, if you created a new implementation package and attempted to navigate to a different tab in the Package Details pane without saving, an error message appeared. This issue has been resolved. Now, the Action Organizer, SAP, and Tasks tabs are disabled and you cannot navigate away from the new package tab until you have saved the record. You can, however, navigate away from the main tab at the top of the page before saving, and your data will be retained.

Previously, when you modified an existing package and then attempted to navigate away from it without saving, you were not prompted to save the package and your changes were lost. This issue has been resolved. Now, if you navigate away from the package, you are prompted to save.

Previously, pasting a copied WMI node into the package structure tree was potentially confusing due to the naming convention used for the pasted node. This issue has been resolved. Now, when you copy and paste a WMI node into the package structure tree, the pasted node has a unique name to easily identify it.

Previously, there were scenarios in which the Copy () and/or Paste () buttons were incorrectly enabled or disabled on the WMI toolbar of an implementation package. This issue has been resolved.

Previously, if you created an implementation package, and then attempted to save the package without entering a value in the ID field, you were logged out of the application. This issue has been resolved. You must now enter a value in the ID field before you can save the package.

Previously, if you created an implementation package from a strategy, and then packaged an action by building an operation, the action’s Long Description field did not match the operation’s Long Text field as expected. This issue has been resolved.

• In Progress
• Implemented
• Single Cycle Plan
• Strategy Plan

• ASIInProgressPackages
• ASIImplemented Packages
• ASISingleCyclePackages
• ASIStrategyPlanPackages

The ASM Overview page has been redesigned to enhance usability. The following changes have been made to the page:

• The System Strategies and Unit Strategies tabs have been merged into a new tab, System and Unit Strategies tab.
• The Optimized Strategies tab has been removed. The strategies in the Optimized Strategies tab now appear in the Asset Strategies or System and Unit Strategies tabs.
• The following new tabs have been added:
  • Risks
  • Actions
• Following columns have been added to the Templates tab:
  • Criticality
  • Duty
  • Service
• The following charts have been added:
  • Active Actions By Source
  • Active Actions By Implementation
• The Strategy Count by State chart has been renamed to Asset Strategies By State.
• The Active Strategy Action Count By Type chart has been renamed to Active Actions By Type.

• TFS309327
• TFS309325
• TFS309324
• TFS309323
• TFS309322
• TFS309321
• TFS309320
• TFS309315

• The Implement button has been added to facilitate implementation of actions.
• You can now implement actions as policy instances, health indicators, and lubrication requirements.
• You can now send notifications to an EAM system for an asset.
• The actions grid now has only one row per action and the columns have changed to improve usability.
• The Send to ASI Package button () has been moved to the Implement Actions workspace. The following changes have also been made to the button’s behavior:
  • The button’s icon has changed.
  • Selecting the button no longer navigates to ASI (instead, you can use the hyperlinked package name on the ASI Package workspace to navigate to ASI).
  • The button is only enabled when you select one or more unimplemented, unpackaged actions.
  • The Send to ASI Package windows have been redesigned.
• The windows for implementing actions have been redesigned to improve usability.

• TFS280619
• TFS278606
• TFS278594
• TFS278226
• TFS278225
• TFS268499
• TFS243908
• TFS200348
• TFS65267

Now, an asset strategy cannot exist without a linked asset. Therefore, when you create an asset strategy, you are now required to link an asset before you can save the new strategy.

When you upgrade to V4.3.0.0.0, any strategies in your database that are not linked to assets will be converted to templates.

• Save a copy of a template, remove the parts of it that you do not want to apply, and then apply the template copy to the strategy.
• Apply the entire template and then remove the parts of it that you do not want in the strategy.

Previously, on iOS devices, when the Resource Finder window appeared after selecting the Import icon () in the Resources section, the Import and Cancel buttons were not visible and you could not close the window. This issue has been resolved.

Previously, when the value in the Risk Rank field was less than 0.01, no data was displayed on the Risk Profile chart in the Strategy Overview section and the Risk Summary chart in the Risk Analysis workspace. This issue has been resolved.

Previously, in the Risk Analysis workspace for a unit or system strategy with no assessed financial risk, an unmitigated risk icon appeared on the Financial Risk chart with a value of 0. This issue has been resolved. Now, if no risk has been assessed then no icon will appear on the chart.

Previously, if you created a new strategy and then moved to another tab without saving the strategy, the focus on the tabs on the left pane shifted. This issue has been resolved.

Previously, if you expanded the State Management dialog box, and then closed the active tab, the State Management dialog box remained expanded in view and incorrectly overlaid other open pages. This issue has been resolved.

Previously, on a Risk or Action datasheet the options to print, turn on the help text, and access reference documents did not appear as expected. This issue has been resolved.

Previously, when a strategy template had a custom required field, the template could not be applied as a master template. This issue has been resolved.

Previously, when you attempted to apply a master template to a strategy, incorrect options appeared for actions and risks that you could apply. This issue has been resolved. Now, when you apply a template as a master, all the actions and risks are applied to the strategy.

Previously, you could incorrectly implement an action with an item that was already implementing another action. This issue has been resolved. Now, only records that are not already implementing an action can be selected when you search for HI sources.

Previously, if you deleted a strategy from the ASM Overview page, the strategy count by state on the ASM Overview page did not update to account for the deletion, and you had to refresh the page for the count to be updated. This issue has been resolved.

To simplify the ASM workflow, the Activation Date and Activated By fields for the Asset Strategy and Asset Strategy Template families have been deprecated. These fields are no longer needed because the State Management feature provides the full activation history for a strategy. (TS ID: 268138)

• DPI 611 - Pressure Calibrator
• DPI 612 - Pressure Calibrator
• DPI 620 - Multifunction Calibrator
• DPI 620 IS - Intrinsically Safe Multifunction Calibrator
• DPI 620 Genii - Multifunction Calibrator, HART/Fieldbus Communicator
• DPI 620 Genii IS - Intrinsically Safe Multifunction Calibrator, HART/Fieldbus Communicator

• TFS260505
• TFS260504
• TFS238983

On the Calibration Admin Preferences page, you can now perform the following tasks:

• Manage Calibration Strategies for each Profile Template.
• Manage mappings based on the selected device types.
• Manage the master templates for manual calibration that will be used in a Calibration Profile.
• Modify Calibration Setup Defaults record to set the default values for Profile Templates.

• TFS316625, 294774

• In the Calibration Template, Discrete family, the following fields are now enabled and the values are required:
  • Activate Switch 1
  • SW 1 Contact State
• The following queries have been added to the Catalog folder \\Public\Meridium\Modules\Calibration Management\Queries:
  • CalibrationDeviceDriverList
  • GetFamilyFeilds
  • CalibMapFamList
  • CalibMapFieldsList
  • CalibMapStratList
  • CalibrationMappingList
  • CalibTemplateTypeSysCode
  • GetLinkedCalibratorFields
  • GetLinkedFamilies
  • GetLinkedFields
  • GetLinkedStrategies
  • LinkStratToMap
  • MapListFinal
  • CalibTemDfltsList
  • CalibProfTempList
  • TemplateDefaults
  • MappDirSystemCodes
  • GetUnrelatedFamilies
  • CalibrationStrategyList
  • RetrieveFieldData
• The following families have been added:
  • Calibration Device Driver
  • Calibration Device Driver Has Mapping
  • Calibration Device Mapping
  • Calibration Mapping Family
  • Calibration Mapping Field
  • Calibration Mapping Has Family
  • Calibration Mapping Has Field
  • Calibration Mapping Has Strategy
  • Calibration Profile Template Defaults
  • Calibration Strategy
• The following System Code Tables have been added:
  • CALIBRATION_DRUCK_UOM_LIST
  • MI_CALIB_TEMPLATE_DEFAULTS_CODES
  • MI_CALIB_TEMPLATE_TYPE
  • MI_CALIBRATION_MAPPING_DIRECTION
• As part of the device mapping implementation, when you upgrade to V4.3.0.0.0, you can use the device mapping upgrade utility to upgrade data from the old device mapping families to the new device mapping families.
• To allow only members of the MI Calibration Administrator group to manage the master profile templates, the Profile Templates button has been removed from the Calibration Management Overview page, and placed in the Mappings section on the Calibration Admin Preference page.
• The Strategy field has been removed from the Calibration Template, Analog and Calibration Template, Discrete families and added to the Calibration Profile family.

• TFS309955
• TFS308901
• TFS295470
• TFS294802
• TFS294777
• TFS294774
• TFS294772

• On the Calibration Template, Discrete family, if the Calibration Type is DPI 620 or DPI Pressure Calibrator, the following fields have been disabled:
  • SW 2 Setpoint
  • Activate Switch 2
  • SW 2 Contact State
  • Specified Minimum Dead Band Switch 2
  • Specified Maximum Dead Band Switch 2
  • Validate Deadband
• In the Calibration Template, Analog family, if the Calibration Type is DPI 620 or DPI PRESSURE CALIBRATOR, the Loop Power field now contains the values Yes and No.
• In the Calibration Template, Discrete family, the following fields have been disabled:
  • Ramp Time
  • Repeat Count
  • Reset Set Point
• You can now transfer calibration data between GE Digital APM and the GE Druck documenting process calibrators using USB port connections.
• Before you perform an automated calibration, you can modify the serial number in the Settings window.
• The following queries have been added to the Catalog folder \\Public\Meridium\Modules\Calibration Management\GE Druck\Queries:
  • DPI 612 Receive Query

    DPI 620 Receive Query

    DPI620SendQuery

    DPI620SendQuery Display

    DPIPCSendQuery

    DPIPCSendQuery Display

• In the Calibration Profile family, two new fields, Calibration Type and Calibration Strategy, have been added.
  • When you select a Calibration Type, the list in the Profile Template field is filtered to only contain the profile templates associated with the selected Calibration Type.
  • When you select a Profile Template, the list in the Calibration Strategy is filtered to only contain the calibration strategies associated with the selected Profile Template.
• To support GE Druck documenting process calibrator units of measure, the following system codes have been added to the MI_CALIBRATION_REFERENCES system code table:
  • DPI 620 UOM CURRENT (DPI 620 Unit of Measure Current)
  • DPI 620 UOM FREQUENCY (DPI 620 Unit of Measure Frequency)
  • DPI 620 UOM PRESSURE ( DPI 620 Unit of Measure Pressure)
  • DPI 620 UOM RESISTANCE (DPI 620 Unit of Measure Resistance)
  • DPI 620 UOM TEMPERATURE (DPI 620 Unit of Measure Temperature)
  • DPI 620 UOM VOLTAGE (DPI 620 Unit of Measure Voltage)
  • DPI PRESSURE CALIBRATOR UOM CURRENT (DPI Pressure Calibrator Unit of Measure Current)
  • DPI PRESSURE CALIBRATOR UOM PRESSURE (DPI Pressure Calibrator Unit of Measure Pressure)
  • DPI PRESSURE CALIBRATOR UOM VOLTAGE (DPI Pressure Calibrator Unit of Measure Voltage)

• TFS315489
• TFS308955
• TFS263702
• TFS260505
• TFS259376
• TFS238979

• A new subfamily, Calibration Template, CMX, has been added to the Calibration Template family. This subfamily stores the details of the calibration that must be performed using the Beamex CMX Calibration software.
• Previously, on the Profile Templates page, when you select the Add button (), a list of Calibration Templates appeared. Now, when you select the Add button (), a drop-down list appears, displaying options Fluke Template, CMX Template, and Manual Template. You must select one of the options, and then select the type of Calibration Template that you want to create.
• A new subfamily, Calibration, CMX, has been added to the Calibration family. This subfamily stores the details of the calibration that has been performed using the Beamex CMX Calibration software.
• The Meridium Devices Service has been enhanced to support communication between GE Digital APM and Beamex CMX Calibration software via Beamex Business Bridge (B3) software.
• On the Calibration Management Overview page, in the Calibration Queue section, the Send to Calibrator button had been renamed to Send for Calibration.
• On the Calibration Management Overview page, in the Calibration Events section, the Receive from Calibrator button had been renamed to Receive from Calibration.

• TFS252757
• TFS249831
• TFS247861
• TFS247860
• TFS239014
• TFS239014

• TFS61319
• TFS61334

• Number of records by Cognition: Displays the number of records classified per cognition, for the 10 cognitions with the most records.
• Number of records reviewed in workbench by classifier: Displays the number of records trained in the Test Results workspace of the Scripts page per machine learning classifier.

Previously, when an executed cognition timed out, the value in the Status field in the History workspace remained as Running, and you could not see the actual status. This issue has been resolved.

Previously, when you navigated between the properties windows of Logic nodes in the design canvas of a cognition, at times, an error message appeared stating that there was an error loading the page. This issue has been resolved.

The eLog module has been introduced in V4.3.0.0.0.

You can use this module to document scheduled and unscheduled events that occur during the course of asset operation, to report findings related to shift periods, and to document when shifts begin and end.

• Current Entity
• Current Relationship
• Create Entity
• Create Event
• Create Production Event
• Create Recommendation
• Create Relationship

If the input specified for a Sum node is an empty collection, the resulting answer from the Sum node is automatically zero (0), which may considerably simplify the policy design. Previously, in this scenario, depending on the policy design, the policy issued a warning and the execution of the policy may have stopped.

In a Create Entity node’s Properties window, you can now specify the Site Reference Key of the site to which the new record should be assigned.

New logs for sync service and policy execution service are now written to C:\ProgramData\Meridium\Logs.

Previously, if you created a policy with a Text node containing the standalone characters “{“ or “}�? that were not intended to be part of a placeholder value, then the characters were not parsed correctly and an error occurred. This issue has been resolved in most scenarios.

Note: Refer to KBA #5444 for more information

Previously, when a Boolean value was selected in a Comparison node, the value NaN was displayed on the node in the model canvas instead of yes or no, as expected. This issue has been resolved.

Note: This issue was display-only and the calculations still functioned as expected.

• TFS274235
• TFS274234

Bulk Data Form

Previously, records with an invalid date value were saved with a blank value in the date field. This issue has been resolved. Now, if an invalid date is used, the record is not saved, and an error message appears. You can either select a valid value from the calendar to correct the value, or delete the invalid value and replace it with a valid one.

• The Generation Availability Analysis workspace has been added. The following tasks are supported in this workspace:
  • You can view the list of Regulatory Organizations supported in GAA and the Unit Types and Unit States available for these Regulatory Organizations.
  • You can view, add, or modify Event Categories and Event Types. You can also associate the Event Categories and Event Types with a color code, which are then used to represent them in the graphs in the Unit Summary workspace for a GAA Unit.
  • You can view, add, or modify Amplification Codes, Cause Codes, and Fuel Types for the Regulatory Organizations.
  • You can manage the mappings of the Amplification Codes and Cause Codes between North American Electric Reliability Corporation (NERC) and Canadian Electricity Association (CEA). You can also add or modify event transitions for Events in GAA.
  • You can configure Regulatory reports for NERC and CEA.
• In the workspace for a GAA Unit, the following changes have been made:
  • The Reports tab has been renamed as Performance & Reports. In this section, you can now view the list of Performance records and Regulatory reports associated with the GAA Unit. You can also associate and disassociate reports with the GAA Unit.
  • The Reference Documents tab has been added. In this section, you can manage generated Regulatory reports, logs, and other documents related to the GAA Unit as Reference Documents.

• TFS286381
• TFS272967
• TFS262651
• TFS261858
• TFS261854
• TFS261853
• TFS261852
• TFS255951
• TFS221932

• GAA Performance Fuel
• GAA Performance Indexes
• GAA Performance Summary

• TFS278489
• TFS262649

• NERC Event Report 07
• NERC Performance Report 05

• TFS257237
• TFS257236

• TFS257237
• TFS257236

• GAA Event Categories
• GAA Event Transition
• GAA Event Types
• GAA Unit Types
• GAA Unit States
• GAA Supported Organizations

• TFS255951
• TFS286380
• TFS249941
• TFS249939
• TFS249937
• TFS249428

• TFS259545
• TFS259545
• TFS258846
• TFS259540
• TFS249938
• TFS258846
• TFS258846
• TFS249938
• TFS262650

• TFS284568
• TFS282097
• TFS281729
• TFS281723
• TFS281132
• TFS281096
• TFS281094
• TFS227130
• TFS227120
• TFS227119
• TFS227118
• TFS227077

• Total Equivalent Derate Hours w/out Shadowing
• Total Equivalent Derate MWh w/out Shadowing

• TFS234410
• TFS234310

• Generation Forecast
• Generation Fuel Annual Report
• Generation Fuel Monthly Report
• Generation Fuel Report
• Generation Nameplate
• Generation Nameplate Combined Cycle
• Generation Nameplate Diesel
• Generation Nameplate Fluidized Bed
• Generation Nameplate Fossil Steam
• Generation Nameplate Gas Turbine
• Generation Nameplate Hydro
• Generation Nameplate Miscellaneous
• Generation Nameplate Nuclear
• Generation Role
• Generation Role Assignment
• Generation Role Definition
• Generation Role Field Configuration
• Generation Unit Loading Profile
• Generation Unit Starting Profile

• TFS184663
• TFS184661
• TFS184660
• TFS184659
• TFS184657
• TFS184656
• TFS184655
• TFS184653
• TFS184652
• TFS184646

• MI Generation Management Forecast
• MI Generation Management Nameplate
• MI Generation Management Security

• TFS184663
• TFS184661
• TFS184660
• TFS18465
• TFS184657
• TFS184656
• TFS184655
• TFS184653
• TFS184652
• TFS184646

Previously, the DAQ ID field in the GE Tag Event family was a numeric field, which may have caused errors while transferring data from your GE system to your GE Digital APMsystem. This issue has been resolved. To facilitate this fix, the numeric DAQ ID field has been deprecated, and a new DAQ ID field with a character data type has been added. When you upgrade, values from the old field are populated in the new field automatically.

• TFS250283
• TFS249987

• The metadata type, KPI, has been added that allows you to import or export KPIs.
• The metadata type, Policies, has been added that allows you to import or export policies.
• The metadata type, Strategy Macros, has been added that allows you to import or export strategy macros.

• TFS309283
• TFS248283
• TFS211261

• TFS291987
• TFS263456
• TFS205957

• TFS291986
• TFS210514

• The System Code Table NR13_FLUID_CLASS has been added. This table is used to populate values in the Fluid Class field of Fluid Code records.
• The System Code Table NR13_FLAMMABLE has been added. This table is used to populate values in the Flammable field of Fluid Code records.
• The field Protected Equipment Type has been added to the NR13 Technical Data family.
• The relationship table NR13 Equipment is Protected By has been added. This relationship indicates that a piece of equipment is a Safety Device.
• The report queries NR13 Full Inspection Report and NR13 Technical Data have been updated so that they now to display a list of protected equipment.

• The Inspection Confidence Evaluation worksheet has been added.
• The following fields have been removed from the baseline Full_Inspection and General_Inspection worksheets.
  • Extent
  • Degradation Mechanism
  • Inspection Type

Previously, when you accessed a localized version of the Inspection Management module, the following occurred:

• On the IM Admin page, in the Manage Human Resources section, the column values were not properly translated.
• Text on error messages was not properly translated.

These issues have been resolved.

• TFS252879
• TFS254109)

• Create
• Save
• Delete
• Edit

The Layers of Protection Analysis module has been introduced in V4.3.0.0.0.

You can use this module to identify the required Safety Integrity Level (SIL) for SIL Assessment of an Instrumented Function defined in the SIS Management module and to determine the level of safeguarding required for a hazardous scenario defined in the Hazards Analysis module.

The ability to manage State Assignments in Life Cycle Cost Analysis is now available. When you create a new Life Cycle Cost Analysis, it is in the In Progress state. When the analysis is complete, users with appropriate team member roles can then change the state to Complete, and the analysis will become view-only.

Super Users and members of the MI LCC Administrator security group can modify the state of any analysis without being members of the analysis.

• TFS265212
• TFS265209

The Management of Change module has been introduced in V4.3.0.0.0.

You can use this module to effectively manage implementation of changes in your organization. Using MOC, you can manage changes using Change Projects in which changes are formally introduced, approved, and implemented as tasks. Additionally, you can relate records from other GE Digital APM entities to ensure that all impacted areas of the organization are recorded as changed elements in a Change Project. This provides your organization with a greater degree of auditability, which is essential in industries that require Management of Change as a regulatory compliance requirement.

• TFS313118
• TFS311404

• TFS211068
• TFS211066

• Generation Availability Analysis (GAA)
• Pipeline Management
• Risk Based Inspection (RBI) 580
• Risk Based Inspection (RBI) 581

• AMS Asset
• Entity
• GE Tag
• Health Indicator
• Measurement Location
• OPC Tag
• Create Entity
• Create Event
• Create Production Event
• Create Recommendation
• Create Relationship

• TFS303628
• TFS289573

• TFS305023
• TFS302179

Previously, when you accessed the PLA Application Settings in a localized version of GE Digital APM, the following issues occurred:

• In the Event Codes section, the Production Event Code tree header was not localized.
• In the Production Profile section, the grid on the Margins datasheet was not localized.
• In the Definition subsection of the Production Profile section, the Production Profile datasheet fields were not localized.
• In the Definition section of the Units workspace, the Definition datasheet fields were not localized.

These issues have been resolved.

• TFS293026
• TFS292697
• TFS292694
• TFS292691

• TFS311821
• TFS311816

• TFS289571
• TFS289039
• TFS289038
• TFS289037
• TFS289035
• TFS289034

• TFS306259
• TFS299864

• TFS294129
• TFS294121
• TFS294110

• TFS258501
• TFS258817

• TFS289034
• TFS289035
• TFS289037
• TFS289038
• TFS289039
• TFS289571

• The All tab has been renamed to Analyses.
• The following tabs have been added:
  • Risks
  • Recommended Actions
• The following charts have been added:
  • Analyses By State
  • Recommended Actions by Type
  • Recommended Actions by State
• The Risks without Recommended Actions chart has been updated to show the number of risks with recommended actions against the number of risks without recommended actions.

• In the folder Public\\Meridium\\Modules\\FMEA
  • FMEA Analyses By State Query
  • FMEA Analysis Recommended Actions
  • FMEA Analysis Risks
  • FMEA Recommended Actions by State
  • FMEA Recommended Actions by Type
• In the folder Public\\Meridium\\Modules\\RCM
  • RCM Analyses By State Query
  • RCM Analysis Recommended Actions
  • RCM Analysis Risks
  • RCM Recommended Actions by State
  • RCM Recommended Actions by Type

• TFS309106
• TFS309102
• TFS309093
• TFS309084
• TFS308839
• TFS308838
• TFS308813

• TFS307876
• TFS160858

• TFS306022
• TFS299751

Now, an analysis cannot exist without a linked asset. Similarly, you can only link virtual assets to RCM and FMEA analysis templates. Therefore, when you create an RCM or FMEA analysis, you are now required to link an asset before you can save the new analysis.

When you upgrade to V4.3.0.0.0, any analyses in your database that are not linked to any assets in the asset hierarchy will be converted to analysis templates.

• TFS255099
• TFS225762

You can now view the information on the number of processed, rejected, updated, and created records after using the RCM and FMEA Data Loaders.

The Template List query is now used to display the content in the Select Template window of the Apply Template Builder for RCM and FMEA.

You can now copy and paste nodes in RCM and FMEA templates.

• Overdue tab
• Complete tab
• Ongoing tab
• All RCM FMEA Risks Without Recommendations chart
• Criticality Distribution of All Assets chart

• From the folder \\Public\Meridium\Modules\FMEA\Analysis:
  • Overview Page - Complete
  • Overview Page - Ongoing
  • Overview Page - Overdue
  • Criticality of RCM FMEA Assets
• From the folder \\Public\Meridium\Modules\RCM\Analysis:
  • Overview Page - Complete
  • Overview Page - Ongoing
  • Overview Page - Overdue

• TFS308824
• TFS183011

• TFS225762
• TFS255099

A new feature, Inventory Grouping, has been introduced in V4.3.0.0.0. Using this feature, you can create inventory groups in a process unit and add components to the inventory group. GE Digital APM then calculates the value in the Inventory Group Mass field for all the components that belong to the inventory group.

The following changes have been made as part of the Inventory Grouping feature:

• Two new families, Inventory Group Configuration and Has Inventory Components, have been created. Inventory Group Configuration records store details about an inventory group. The Has Inventory Components family defines the relationship between the RBI Components and Inventory Group Configuration family.
• A new section RBI 581 Inventory Groups has been added to the RBI Admin Preferences page. If the Use Calculated Inventory check box is selected in an RBI 581 Consequence Evaluation, and if the associated component is linked to an inventory group, then the Inventory Group Mass field is disabled and populated automatically.

• TFS267599
• TFS254369
• TFS254372
• TFS260580

• Criticality Calculator RBI Components (and its child families)
• RBI 581 Risk Analysis
• RepresentativeFluids

• When you select a toxic fluid that is valid for RBI 581, this check box is disabled and selected, indicating that the fluid you have selected is valid for RBI 581.
• When you select a toxic fluid that is not valid for RBI 581, this check box is disabled and cleared. In this scenario, if you attempt to calculate the RBI 581 Risk Analysis, an error message appears, indicating that the fluid you have selected is not valid for RBI 581.

• A new Security Group, MI RBI Viewer, has been created. This Security Group has only the View privilege to all the families used in RBI. A member of this Security Group can only access all the records used in RBI.
• A new Security Role, MI Mechanical Integrity Viewer, has been created and assigned to the RBI Viewer Security Group.

• DEFAULT-RISK_MAPPING-FINANCIAL
• PL-DEF-RISK_MAPPING-FINANCIAL
• PL-RISK_MAPPING-FINANCIAL
• RISK_MAPPING-FINANCIAL

• TFS258647
• TFS255000

• The order of the columns in the Risk based Inspection (RBI) 580 Data Loader has been modified to match the order of the fields as they appear on the corresponding datasheets in GE Digital APM.
• The following columns have been added:

• Column	Worksheet
  PWHT	RBI_Component
  Is Entry Possible?	RBI_Component
  Source of Calculated Corrosion Rate	RBI_Component
  Allowable Stress Override	RBI_Criticality Analysis
  Allowable Stress	RBI_Criticality Analysis

• The following columns have been removed:

  Column	Worksheet
  PWHT	DME_Environmental_Cracking
  Is Entry Possible?	DME_Environmental_Cracking

• The following columns have been renamed:

  Old Name	New Name
  Component Start Date	Component Date in Service
  Course Number	Course Number (For Tank Bottom)

• The following column names have been appended with (Channel Side for Exchanger Bundle) to allow you to add the field values for channel side if the component is an Exchanger Bundle:
  • Operating Pressure
  • Operating Temperature
  • Initial Fluid Phase
  • Process Fluid
  • Toxic Fluid
  • Toxic Mixture
  • Percent toxic
  • Design Pressure
  • Design Temperature
• The column names for estimated corrosion rates and predictable corrosion locations have been updated to indicate whether they correspond to inside or outside the tube of an exchanger bundle.

• Inspection Confidence
• Inspection Strategy ID

• Cylindrical_Shell Worksheet.
• Exchanger_Bundle Worksheet.
• Exchanger_Header Worksheet.
• Piping Worksheet.
• Tank_Bottom Worksheet.

• The Risk Summary ID field is now populated with the value Risk exceeded, Mitigation does not help.
• The Risk Summary Description field is now populated with the value Residual Risk after applying highest level of Inspection.

• RBI 581 Financial Consequence Evaluation
• RBI 581 Damage Factor - Thinning
• RBI 581 External Corrosion Damage Factor
• RBI 581 CUI Damage Factor

• TFS305997
• TFS293594

• The methodology type appears below each PDM.
• The PDM appears as a hyperlink. If you select the link, the PDM record appears in Record Explorer on a new page.

Similarly, in the Degradation Mechanisms section of an RBI Criticality Analysis, RBI 581 Risk Analysis, RBI PRD Analysis, or RBI Pipeline Analysis, if you select the Add Item button ():

• The methodology type appears below each Degradation Mechanism (DM).
• The DM appears as a hyperlink. If you select the link, the associated PDM record appears in Record Explorer on a new page.

• A new field, Controlling Corrosion Rate, has been added to the RBI 581 Thinning and Lining Damage Evaluation family. This field appears as a text box in the Generalsection of the datasheet.
• A new system code, Controlling Corrosion Rate, has been added to the 581_CORR_TYPE System Code Table. Therefore, you can select Controlling Corrosion Rate in the Selected BM Corrosion Rate and Selected Cladding Corrosion Rate fields in an RBI 581 Thinning and Lining Damage Evaluation.
• The RBI 581 Damage Factor - Thinning policy has been modified to calculate damage factor using the value in the Controlling Corrosion Rate field if the value in the Selected BM Corrosion Rate or Selected Cladding Corrosion Rate field is Controlling Corrosion Rate.
• The RBI 581 Damage Factor - AST Bottom Thinning policy has been modified to calculate damage factor using the value in the Controlling Corrosion Rate field if the value in the Selected BM Corrosion Rate field is Controlling Corrosion Rate.

Previously, if the Material Type field in a PV Stress record contained a value, then the value in the Allowable Stress field in the following records was not populated.

• RBI Criticality Analysis
• RBI Pipeline Analysis
• RBI 581 Risk Analysis

This issue has been resolved.

Previously, the following issues existed in the documentation for Risk Based Inspection and RBI 581:

• In the first time deployment instructions, the step to import data mapping and strategy mapping records was missing.
• In the upgrade instructions, it was specified that importing the RBI Strategy Mapping Configuration and RBI Strategy Mapping Details records was not a required step.

These issues have been resolved.

• TFS261305
• TFS257898

Previously, in a Criticality Int. Corr. Deg. Mech. Eval. record associated with a piping component, the value in the Pressure at Minimum Thickness field was calculated incorrectly. This issue has been resolved.

Previously, in a Criticality Ext. Corr. Deg. Mech. Eval. record, the value in the Corrosion Factor field was calculated incorrectly if the field values in the record satisfied one of the following conditions:

Due to this, the value in the Probability Category field was calculated incorrectly. This issue has been resolved.

These issues have been resolved. If the inspection satisfies the aforementioned conditions, then the previous inspection date is used to calculate the value in the Weibull Updated Characteristic Life field.

• You cleared the Toxic Mixture check box.
• You selected a fluid valid for an RBI 581 Risk Analysis in the Toxic Fluid field and then cleared it, or selected a fluid that was not valid.

Similarly, the Fluid Valid for 581 Analysis check box was not cleared even if you selected a process fluid valid for an RBI 581 Risk Analysis in the Process Fluid field and then cleared it, or selected a fluid that was not valid. These issues have been resolved.

Previously, while assessing the mitigated risk for a DM, on the Risk Matrix window, if you selected Done multiple times, then multiple Risk Assessment records were created and linked to the DM. This issue occurred with DMs linked to any of the following analyses:

• RBI Criticality Analysis
• RBI PRD Analysis
• RBI Pipeline Analysis
• RBI 581 Risk Analysis

This issue has been resolved.

• Risk Based Inspection (RBI) 580 Data Loader.

  • Cylindrical_Shell Worksheet.

  • Exchanger_Header Worksheet.

  • Tank_Bottom Worksheet.

  • Exchanger_Tube Worksheet.

  • Piping Worksheet.

• Criticality Calculator RBI Components datasheet - Corrosion Data section.
• RBI Criticality Analysis Data Sheet - Design Data section.

• The damage factor for a governing damage mechanism (DM) on plan date was less than the minimum of the three target minimum damage factors (defined for the three governing DM methodologies) before or during inspection planning.
• The analysis was linked only to non-mitigating DMs.

These issues have been resolved.

• TFS314724
• TFS314723
• TFS314722

Previously, after you calculated an RBI 581 Risk Analysis, the value in the Inspection Will Mitigate field was Yes (Y) instead of No (N) if both the following conditions were satisfied:

• The risk was not mitigated on the plan date.

• The Damage Mechanism (DM) in the analysis was linked to a B or C level inspection, and the damage factor for the DM was less than the target minimum damage factor value for the DM.

In addition, the following fields were not populated:

• Risk Summary ID

• Risk Summary Description

This issue has been resolved.

Previously, after you calculated an RBI 581 Risk Analysis, the value in the Coating Adjustment field in the associated RBI 581 External Cracking Damage Evaluation was calculated incorrectly. This issue has been resolved. (TS ID: 278793)

• You cleared the Toxic Mixture check box.
• You selected a fluid valid for an RBI 581 Risk Analysis in the Toxic Fluid field and then cleared it, or selected a fluid that was not valid.

Similarly, the Fluid Valid for 581 Analysis check box was not cleared even if you selected a process fluid valid for an RBI 581 Risk Analysis in the Process Fluid field and then cleared it, or selected a fluid that was not valid. These issues have been resolved.

Previously, Security Groups were not assigned security permissions to the RBI 581 Env Cracking Insp Recommendation Policy.

In addition, in an Oracle database, Security Groups were not assigned security permissions to the following policies:

• RBI 581 885 Embrittlement Sigma Damage Factor

• RBI 581 AST Bottom Corrosion Rate

These issues have been resolved. Now, Security Groups have been assigned permissions to the policies as follows:

Previously, although Inspection History was not used to calculate the damage factor of the following Damage Mechanisms (DMs), you could assign Inspections to Degradation Mechanism Evaluations (DMEs) of the following DMs:

• 581-High Temperature Hydrogen Attack
• 581-Internal Component Lining Damage
• 581-Piping Mechanical Fatigue
• All DMs that belonged to RBI 581 Brittle Fracture Damage Evaluation

Previously, in an RBI 581 Thinning and Lining Evaluation, the following issues existed:

• You could enter 0 in the No Highest Effective Insp field irrespective of the value in the Highest Effective Insp field.
• If the value in the Highest Effective Insp field was InEffective (None), then you could not enter a value other than 0 in the No Highest Effective Insp field.

These issues have been resolved such that:

• If you enter 0 in the No Highest Effective Insp field, then the Highest Effective Insp field is disabled and populated with the value InEffective (None).
• You can now enter a value other than 0 in the No Highest Effective Insp field even if the value in the Highest Effective Insp field is InEffective (None).

• RBI 581 Financial Consequence Evaluation
• RBI 581 Damage Factor - Thinning
• RBI 581 External Corrosion Damage Factor
• RBI 581 CUI Damage Factor

Unlinking a Measurement Location from a Measurement Location Template.

Accessing a list of recent Routes.

• TFS292056
• TSF288635

A new field, Capacity Unit of Measure, has been added in Lubrication Requirement and Lubrication Requirement Template records to replace the existing field, which has been deprecated. The new field contains a drop-down list, populated by the MI_LM_REFERENCES system code table, from which you can select an appropriate Unit of Measure.

When you upgrade to V4.3.0.0.0, this field will be populated automatically with a reference to the unit of measure that corresponds to the value in the deprecated Capacity Unit of Measure field. Therefore, prior to upgrading your database, we recommend that you review the values in the Capacity Unit of Measure field to consolidate any near-matches, and to ensure that corresponding values exist in the MI_LM_REFERENCES System Code Table.

• TFS302914
• TFS279942
• TFS162008

• Lubricant Type
• Trade Name
• Description
• ISO Grade
• Viscosity Rating
• Flash Point
• Flash Point UOM
• Manufacturer's Part Number
• Storage Location
• Material Number
• Notes

• TFS279026
• TFS267523
• TFS145678

• Measurement Location family
• Measurement Location Template family
• Lubrication Requirement family
• Lubrication Requirement Template family
• Lubrication Requirement Worksheet (MI_LR_TMPLT) in the Rounds Template Data Loader Workbook.
• Measurement Location Worksheet (MI_MEAS_LOC) in the Rounds Routes Data Loader Workbook. This worksheet covers both Measurement Locations and Lubrication Requirements.
• Measurement Location Worksheet (MI_ML_TMPLT) in the Rounds Template Data Loader Workbook.

To support this enhancement for Windows Mobile handheld devices, the following changes have been made:

• A new family, Rounds Sequence Information, has been added to store the route sequence information.
• A new button, Save Route Sequence, has been added to the route page in Rounds Designer. Selecting this button after reordering a Route allows the Route sequence to be immediately reflected when you download the route to a handheld device. Otherwise, Route Sequence Information records will be updated only on a defined schedule, when you access another tab, or after the Rounds Designer page has been closed.
• A new section, Route Sequencing, has been added to the Rounds Designer Application Settings. You can use this section to define a schedule on which to synchronize the Route sequence changes with the Rounds Sequence Information family.
• When you upgrade to V4.3.0.0.0, if you have modified the following queries, then you will need to copy the new baseline queries and reapply your modifications to take advantage of this enhancement:
  • Public\Meridium\Modules\Lubrication Management\Queries\Report Queries\Lubrication Management Data Capture
  • Public\Meridium\Modules\Operator Rounds\Queries\Report Queries\Measurement Location Data Capture
  • Public\Meridium\Modules\Mobile\Operator Rounds\Measurement Locations

• TFS27137
• TFS271166
• TFS265666
• TFS260429
• TFS260428
• TFS260394
• TFS185936

• In the Rounds Routes data loader, on the Route worksheet:
  • Next Date
  • Last Date

• In the Rounds Routes data loader, on the Checkpoint Task worksheet:
  • Next Date
  • Non-compliance Date
  • Non Compliance Next Check Date
• In the Rounds Reading data loader, on the Reading worksheet:
  • Reading Taken Date

• A new entity family, Lubrication Component, has been added to store information about lubrication components.
• The following changes have been made to the Lubrication Requirement and Lubrication Requirement Template families:
  • The field Component has been deprecated.
  • Two new fields, Component Type and Component Sub Type, have been added.
  • The Component Type and Component Sub Type fields contain lists that are populated by the values in the corresponding fields in the Lubrication Component family.
• When you select a Component Type, the Component Sub Type list is filtered to only the subtypes corresponding to the selected type.
• The specified Component Type and Component Sub Type are shown in the Lubrication Requirement Summary when a Rounds Data Collection user selects a Lubrication Requirement on a Route.

• TFS214377
• TFS214068
• TFS145676

• A new entity family, Lubrication Method, has been added.
• The following changes have been made to the Lubrication Requirement and Lubrication Requirement Template families:
  • Three new fields, Lubricant Type, Method Type, and Method Sub Type, have been added.
  • The Method Type and Method Sub Type fields contain lists that are populated by the values in the corresponding fields in the Lubrication Method family.
  • When you select a Lubricant Type, the list in the Lubricant field is filtered to only the lubricants corresponding to the selected type of lubricant.
  • When you select a Lubricant, the list in the Method Type field is filtered to only the method types corresponding to the selected Lubricant.
  • When you select a Method Type, the list in the Method Sub Type field is filtered to only the subtypes corresponding to the selected type.
  • The existing Method fields have been marked as Deprecated and removed from the default datasheets.
• The specified Method Type and Method Sub Type are shown in the Lubrication Requirement Summary when a Rounds Data Collection user selects a Lubrication Requirement on a Route.

• TFS214080
• TFS214077
• TFS214070
• TFS145677

When you upgrade to V4.3.0.0.0, a new Lubricant Manufacturer record will be created for each value in the Manufacturer field in Lubricant records prior to upgrading, and the value will be replaced with a reference to the corresponding Lubrication Manufacturer record. Therefore, prior to upgrading your database, we recommend that you review the values in the Manufacturer field in Lubricant records to consolidate any near-matches.

When you upgrade to V4.3.0.0.0, a new entry in the system code table will be added during the upgrade for each value in the Priority field in Lubrication Requirement and Lubrication Requirement Template records prior to upgrading. The value in those fields will be replaced with a reference to the corresponding system code table entry. Therefore, prior to upgrading your database, we recommend that you review the values in the Priority field to consolidate any near-matches.

• Asset ID
• Asset Description

• The Result Column box has been renamed to Field to Classify.
• The Reference Column box has been renamed to Standard List Reference Field.

You can now print the report for an SIS Trip Report record from the page for the selected trip report. The report displays the summary of the SIS Trip Report and its associated records.

You can now create a Recommendation for an Instrumented Function whose SIL Assessment is associated with a LOPA Assessment, and then promote the Recommendation to ASM.

You can now derive a qualitative risk rank mapping for an Instrumented Function in SIS Management using the values calculated in LOPA.

You can now create a Layers of Protection Analysis (LOPA) in the LOPA module, and then link it with an Instrumented Function for which you want to assess the required Safety Integrity Level (SIL). To facilitate this enhancement, a new family, LOPA Assessment, has been added to store the SIL Assessment values for Instrumented Functions.

When you upgrade to V4.3.0.0.0:

• If you were previously using LOPA to assess SIL values for Instrumented Functions, LOPA Assessment records are created by copying values from the LOPA records, and then linked to the corresponding Instrumented Functions.
• The values in Independent Layer of Protection records that existed previously in your database are copied to the corresponding fields in the Hazards Analysis Safeguard records. The safeguards are then linked to the LOPA with which the Independent Layers of Protection records were associated.

• TFS253781
• TFS249999
• TFS249996

When you delete an SIL Analysis, the Protective Instrument Loops associated with the SIL Analysis are deleted only if the elements in the loop are not associated with other Protective Instrument Loops belonging to different SIL Analyses. This ensures that shared elements are not deleted, which may then result in incorrect calculations in other associated loops.

A new Security Group, MI SIS Viewer, has been added. This group has View permissions for all the Entity and Relationship families used in SIS Management module.

Previously, the following areas were not localized:

• Some fields on the Final Element Group Details datasheet
• Some fields on the Logic Solver Details datasheet
• The Alarm Setting (High/Low) field on the Sensors datasheet
• Some fields on the Sensor Group Details datasheet

These issues have been resolved.

• TFS210377
• TFS210375
• TFS210373
• TFS210371

• Sensor in a Protective Instrument Loop
• Final Element in a Protective Instrument Loop
• Custom Device (i.e., Custom Sensor or Custom Final Element)
• Sensor in a Protective Instrument Loop Template
• Final Element in a Protective Instrument Loop Template

You can now enter a value in the Historical Sequence field in a Thickness Measurement record using the Thickness Monitoring (TM) Equipment or Thickness Monitoring (TM) Functional Location Data Loader by adding a column on the Measurements worksheet in the data loader workbook.

The performance of the Thickness Monitoring (TM) Equipment Data Loader and the Thickness Monitoring (TM) Functional Location Data Loader has been improved by allowing multiple batches to load simultaneously.

The Remaining Life graph on the TM Overview page and the Remaining Life pie chart in the Remaining Life section have been updated to calculate and to display the remaining life from the current day, instead of the Measurement Last Taken Date.

You can now perform a bulk analysis of TM Corrosion Analyses from the Assets tab of the Thickness Monitoring Overview page. The Bulk Analyze window displays information related to calculations such as progress, assets, components, analyses, and completion statuses. You can also access a log to view detailed information about the calculation process, and, for any failed analyses, a list of the required fields.

The Piping Stress reference table now includes information on Construction Code ASME B31.1 and Code Year 2014, thus adding 17,286 records to the Piping Stress family.