Deployment

Deploy Metrics and Scorecards for the First Time

About This Task

The following table outlines the steps that you must complete to deploy and configure this module for the first time. These instructions assume that you have completed the steps for deploying the basic system architecture.

These tasks may be completed by multiple people in your organization. GE Digital recommends, however, that the tasks be completed in the order in which they are listed.

Note: If you are deploying this module in APM Now, before you begin completing these tasks, review the system requirements for this module to identify the supported features for this module in APM Now. Unless noted, all deployment tasks in the following table are applicable for the deployment of this module in APM Now.

Results

StepTaskNotes
1Deploy SQL Server Analysis Services 2012 or Microsoft SQL Server Analysis Services 2014. Ensure that the SQL Server Analysis Services machine meets the system requirements.

Deploying SQL Server Analysis Services on the SQL Server Analysis Server machine includes the following steps:

  1. Install SQL Server Analysis Services.
  2. Deploy the Work History Analysis Services database.

    This Work History cube is a replacement for the Equipment and Functional Location Work History cubes in the Meridium_Event_Analysis database.

  3. Create a Windows User on the Analysis Server or in your organization’s Active Directory.
    The user name requires minimum privileges and will only be used by the GE Digital APM Server to connect to the cubes. It is recommended that:
    • The password for this user should never expire.
    • The user should be restricted to change password.
    • The user should be restricted to log in to others servers (e.g., meridium_ssas_user).
  4. Add the user created in Step 3 to a role on all SQL Analysis Services databases you want to access in GE Digital APM software.

    The role should have read and drill through permissions. The Work History database already has a View role defined, you should add the user to this role. For more information, consult the MSDN documentation regarding Roles and Permissions for Analysis Services.

  5. Configure SQL Server Analysis Server for HTTP or HTTPS access using basic authentication.

    HTTPS is recommended with basic authentication. For more information, consult the MSDN documentation regarding configuring the HTTP access to Analysis Services on Internet Information Service (IIS).

This step is required.

This step assumes that you have read the Metrics and Scorecards hardware and software requirements and that you have obtained the SQL Server Analysis Services software installer.

2 Verify that your event and asset criticality data meet the standard classification requirements, and modify the Event or Asset Criticality Data for the Work History cube as needed.This step is required.
3 Localize the event and asset criticality values in the application.This step is optional.
4 Schedule cubes for processing on the SQL Server Analysis Server.This step is required.
5 Assign Security Users to one or more of the Metrics and Scorecards Security Groups and Roles.This step is required.
6Create Analysis Services Cube records for each cube that has been defined in SQL Server Analysis Services.

Since GE Digital APM uses HTTP connection to connect to the cube, in addition to server address, you need to provide credentials of the user created in Step 1 Task 3.

This step is required.
7 Grant Security Users and Groups access rights to Analysis Services Cube records .This step is required.
8 Configure privileges for KPI .This step is required.
9 Configure privileges for Scorecards .This step is required.
10 Configure a cube for usage metrics tracking on the SQL Server Analysis Server.This step is required only if you use Metrics and Scorecards to view the usage metrics in a cube.

Upgrade or Update Metrics and Scorecards to V4.3.1.0.0

About This Task

The following tables outline the steps that you must complete to upgrade this module to V4.3.1.0.0. These instructions assume that you have completed the steps for upgrading the basic GE Digital APM system architecture.

These tasks may be completed by multiple people in your organization. We recommend, however, that the tasks be completed in the order in which they are listed.

Procedure

  • Upgrade from any version V4.3.0.0.0 through V4.3.0.7.7
    StepTaskNotes
    1 Deploy the new Work History cube.
    Important: Before deploying the new Work History cube, ensure that:
    • The Security User who will run the Analysis Services Deployment Wizard has been granted View permissions to the cubes associated with the Metric Views.
    • The cubes are active.

    This step is required, and the baseline work history cube must be redeployed.

    The baseline Work History cube was modified such that even if the event or equipment data do not meet the standard classification defined for the Work History cube, with minor modifications to the event and asset criticality data used by the cube, the cube will work with the non-standard event and equipment data.

    2If you have modified a cube that belongs to a previous version, you must manually make the same modifications to the current Work History cube.

    This step is required only if you have modified a Work History cube that belongs to a previous version.

    If you have made modifications to the Work History cube, then you must manually make those updates again.

    3 Verify that your event and asset criticality data meet the standard classification requirements, and modify the event or asset criticality data for the Work History cube as needed.This step is required.
    If you are an existing user who uses the work history cube, you can map the event or asset criticality data available in your database to the standard event or asset criticality data defined for the work history cube using one of the following procedures:
    • Modifying the corresponding views for the work history cube in the GE Digital APM database.
    • Modifying records available for the corresponding event or asset criticality data family by constructing and executing an update query.
    4 Localize the event and equipment values in GE Digital APM .This step is required only if you want to localize the event and equipment values in the Work History cube.
    5 Schedule cubes for processing on the SQL Server Analysis Server.This step is required.
  • Upgrade from any version V4.2.0.0 through V4.2.0.9.3
    StepTaskNotes
    1 Deploy the new Work History cube.
    Important: Before deploying the new Work History cube, ensure that the Security User who will run the Analysis Services Deployment Wizard has been granted View permissions to the cubes associated with the Metric Views, and that the cubes are active.

    This step is required, and the baseline work history cube must be redeployed.

    The baseline Work History cube was modified such that even if the event or equipment data do not meet the standard classification defined for the Work History cube, with minor modifications to the event and asset criticality data used by the cube, the cube will work with the non-standard event and equipment data.

    2If you have made modifications in the previous version of the cube, then you must manually make the same modifications to the current Work History cube.This step is required only if you had made any modifications to the previously provided Work History cube.

    If you had made any modifications to the Work History cube, then you must manually make those updates again.

    3 Verify that your event and asset criticality data meet the standard classification requirements, and modify the event or asset criticality data for the Work History cube as needed.This step is required.
    4 Localize the event and equipment values in GE Digital APM .This step is required only if you want to localize the event and equipment values in the Work History cube.
    5 Schedule cubes for processing on the SQL Server Analysis Server.This step is required.
  • Upgrade from any version V4.1.0.0 through V4.1.7.4.0
    StepTaskNotes
    1 Deploy the new Work History cube.
    Important: Before deploying the new Work History cube, ensure that the Security User who will run the Analysis Services Deployment Wizard has been granted View permissions to the cubes associated with the Metric Views, and that the cubes are active.

    This step is required, and the baseline work history cube must be redeployed.

    The baseline Work History cube was modified such that even if the event or equipment data do not meet the standard classification defined for the Work History cube, with minor modifications to the event and asset criticality data used by the cube, the cube will work with the non-standard event and equipment data.

    2If you have made modifications in the previous version of the cube, then you must manually make the same modifications to the current Work History cube.This step is required only if you had made any modifications to the previously provided Work History cube.

    If you had made any modifications to the Work History cube, then you must manually make those updates again.

    3 Verify that your event and asset criticality data meet the standard classification requirements, and modify the event or asset criticality data for the Work History cube as needed.This step is required.
    4 Localize the event and equipment values in GE Digital APM .This step is required only if you want to localize the event and equipment values in the Work History cube.
    5 Schedule cubes for processing on the SQL Server Analysis Server.This step is required.
  • Upgrade from any version V4.0.0.0 through V4.0.1.0
    StepTaskNotes
    1 Deploy the new Work History cube.
    Important: Before deploying the new Work History cube, ensure that the Security User who will run the Analysis Services Deployment Wizard has been granted View permissions to the cubes associated with the Metric Views, and that the cubes are active.

    This step is required, and the baseline work history cube must be redeployed.

    The baseline Work History cube was modified such that even if the event or equipment data do not meet the standard classification defined for the Work History cube, with minor modifications to the event and asset criticality data used by the cube, the cube will work with the non-standard event and equipment data.

    2If you have made modifications in the previous version of the cube, then you must manually make the same modifications to the current Work History cube.This step is required only if you had made any modifications to the previously provided Work History cube.

    If you had made any modifications to the Work History cube, then you must manually make those updates again.

    3 Verify that your event and asset criticality data meet the standard classification requirements, and modify the event or asset criticality data for the Work History cube as needed.This step is required.
    4 Localize the event and equipment values in GE Digital APM .This step is required only if you want to localize the event and equipment values in the Work History cube.
    5 Schedule cubes for processing on the SQL Server Analysis Server.This step is required.
  • Upgrade from any version V3.6.1.0.0 through V3.6.1.7.4
    StepTaskNotes
    1Migrate your SQL Server Analysis Services database and cubes to the following supported SQL Server Analysis Services versions:
    • 2012
    • 2014
    		This step is required only if you were previously using SQL Server Analysis Services 2008 R2.
    2Configure SQL Server Analysis Server for HTTP or HTTPS access using basic authentication.This step is required.
    3Deploy Work History Analysis Services database.

    This Work History cube is a replacement for the Equipment and Functional Location Work History cubes in the Meridium_Event_Analysis database.
    Important: Before executing this step, ensure that the Security User who will run the Analysis Services Deployment Wizard has been granted View permissions to the cubes associated with the Metric Views, and that the cubes are active.

    This step is required.

    4Create a Windows User on the Analysis Server or in your organization’s Active Directory.
    The user name requires minimum privileges and will only be used by the GE Digital APM Server to connect to the cubes. It is recommended that:
    • The password for this user should never expire.
    • The user should be restricted to change password.
    • The user should be restricted to log in to others servers (e.g., meridium_ssas_user).
    		This step is required.
    5Add the user created in Step 4 to a role on all SQL Analysis Services databases that you want to access in GE Digital APM.

    The role should have read and drill-through permissions. If the Work History database already has a View role defined, then you should add the user to this role. For more information, consult the MSDN documentation regarding Roles and Permissions for Analysis Services.

    		This step is required.
    6 Verify that your event and asset criticality data meet the standard classification requirements, and modify the event or asset criticality data for the Work History cube as needed. This step is required.
    7 Localize the event and equipment values in GE Digital APM .This step is required only if you want to localize the event and equipment values in the Work History cube.
    8 Schedule cubes for processing on the SQL Server Analysis Server.This step is required.
    9 Update the existing Analysis Services Cube records so that GE Digital APM connects to the cube using the HTTP/ HTTPS access.This step is required.
  • Upgrade from any version V3.6.0.0.0 through V3.6.0.12.9
    StepTaskNotes
    1Migrate your SQL Server Analysis Services database and cubes to the following supported SQL Server Analysis Services versions:
    • 2012
    • 2014
    		This step is required only if you were previously using SQL Server Analysis Services 2008 R2.
    2Configure SQL Server Analysis Server for HTTP or HTTPS access using basic authentication.This step is required.
    3Deploy Work History Analysis Services database.

    This Work History cube is a replacement for the Equipment and Functional Location Work History cubes in the Meridium_Event_Analysis database.
    Important: Before executing this step, ensure that the Security User who will run the Analysis Services Deployment Wizard has been granted View permissions to the cubes associated with the Metric Views, and that the cubes are active.

    This step is required.

    4Create a Windows User on the Analysis Server or in your organization’s Active Directory.
    The user name requires minimum privileges and will only be used by the GE Digital APM Server to connect to the cubes. It is recommended that:
    • The password for this user should never expire.
    • The user should be restricted to change password.
    • The user should be restricted to log in to others servers (e.g., meridium_ssas_user.
    		This step is required.
    5Add the user created in Step 4 to a role on all SQL Analysis Services databases that you want to access in GE Digital APM.

    The role should have read and drill-through permissions. If the Work History database already has a View role defined, then you should add the user to this role. For more information, consult the MSDN documentation regarding Roles and Permissions for Analysis Services.

    		This step is required.
    6 Verify that your event and asset criticality data meet the standard classification requirements, and modify the event or asset criticality data for the Work History cube as needed. This step is required.
    7 Localize the event and equipment values in GE Digital APM .This step is required only if you want to localize the event and equipment values in the Work History cube.
    8 Schedule cubes for processing on the SQL Server Analysis Server.This step is required.
    9 Update the existing Analysis Services Cube records so that GE Digital APM connects to the cube using the HTTP/ HTTPS access.This step is required.
  • Upgrade from any version V3.5.1 through V3.5.1.12.3
    StepTaskNotes
    1Migrate your SQL Server Analysis Services database and cubes to the following supported SQL Server Analysis Services versions:
    • 2012
    • 2014
    		This step is required only if you were previously using SQL Server Analysis Services 2008 R2.
    2Configure SQL Server Analysis Server for HTTP or HTTPS access using basic authentication.This step is required.
    3 Deploy Work History Analysis Services database.

    This Work History cube is a replacement for the Equipment and Functional Location Work History cubes in the Meridium_Event_Analysis database.
    Important: Before executing this step, ensure that the Security User who will run the Analysis Services Deployment Wizard has been granted View permissions to the cubes associated with the Metric Views, and that the cubes are active.

    This step is required.

    4Create a Windows User on the Analysis Server or in your organization’s Active Directory.
    The user name requires minimum privileges and will only be used by the GE Digital APM Server to connect to the cubes. It is recommended that:
    • The password for this user should never expire.
    • The user should be restricted to change password.
    • The user should be restricted to log in to others servers (e.g., meridium_ssas_user).
    		This step is required.
    5Add the user created in Step 4 to a role on all SQL Analysis Services databases that you want to access in GE Digital APM.

    The role should have read and drill-through permissions. If the Work History database already has a View role defined, then you should add the user to this role. For more information, consult the MSDN documentation regarding Roles and Permissions for Analysis Services.

    		This step is required.
    6 Verify that your event and asset criticality data meet the standard classification requirements, and modify the event or asset criticality data for the Work History cube as needed. This step is required.
    7 Localize the event and equipment values in GE Digital APM .This step is required only if you want to localize the event and equipment values in the Work History cube.
    8 Schedule cubes for processing on the SQL Server Analysis Server.This step is required.
    9 Update the existing Analysis Services Cube records so that GE Digital APM connects to the cube using the HTTP/ HTTPS access.This step is required.
  • Upgrade from any version V3.5.0 SP1 LP through V3.5.0.1.10.1
    StepTaskNotes
    1Migrate your SQL Server Analysis Services database and cubes to the following supported SQL Server Analysis Services versions:
    • 2012
    • 2014
    		This step is required only if you were previously using SQL Server Analysis Services 2008 R2.
    2Configure SQL Server Analysis Server for HTTP or HTTPS access using basic authentication.This step is required.
    3 Deploy Work History Analysis Services database.

    This Work History cube is a replacement for the Equipment and Functional Location Work History cubes in the Meridium_Event_Analysis database.
    Important: Before executing this step, ensure that the Security User who will run the Analysis Services Deployment Wizard has been granted View permissions to the cubes associated with the Metric Views, and that the cubes are active.

    This step is required.

    4Create a Windows User on the Analysis Server or in your organization’s Active Directory.

    The user name requires minimum privileges and will only be used by the GE Digital APM Server to connect to the cubes. It is recommended that:

    • The password for this user should never expire.
    • The user should be restricted to change password.
    • The user should be restricted to log in to others servers (e.g.,meridium_ssas_user).
    		This step is required.
    5Add the user created in Step 4 to a role on all SQL Analysis Services databases that you want to access in GE Digital APM.

    The role should have read and drill-through permissions. If the Work History database already has a View role defined, then you should add the user to this role. For more information, consult the MSDN documentation regarding Roles and Permissions for Analysis Services.

    		This step is required.
    6 Verify that your event and asset criticality data meet the standard classification requirements, and modify the event or asset criticality data for the Work History cube as needed. This step is required.
    7 Localize the event and equipment values in GE Digital APM .This step is required only if you want to localize the event and equipment values in the Work History cube.
    8 Schedule cubes for processing on the SQL Server Analysis Server.This step is required.
    9 Update the existing Analysis Services Cube records so that GE Digital APM connects to the cube using the HTTP/ HTTPS access.This step is required.
  • Upgrade from any version V3.5.0 through V3.5.0.0.7.1
    StepTaskNotes
    1Migrate your SQL Server Analysis Services database and cubes to the following supported SQL Server Analysis Services versions:
    • 2012
    • 2014
    		This step is required only if you were previously using SQL Server Analysis Services 2008 R2.
    2Configure SQL Server Analysis Server for HTTP or HTTPS access using basic authentication.This step is required.
    3Deploy Work History Analysis Services database.

    This Work History cube is a replacement for the Equipment and Functional Location Work History cubes in the Meridium_Event_Analysis database.
    Important: Before executing this step, ensure that the Security User who will run the Analysis Services Deployment Wizard has been granted View permissions to the cubes associated with the Metric Views, and that the cubes are active.

    This step is required.

    4Create a Windows User on the Analysis Server or in your organization’s Active Directory.
    The user name requires minimum privileges and will only be used by the GE Digital APM Server to connect to the cubes. It is recommended that:
    • The password for this user should never expire.
    • The user should be restricted to change password.
    • The user should be restricted to log in to others servers (e.g.,meridium_ssas_user).
    		This step is required.
    5Add the user created in Step 4 to a role on all SQL Analysis Services databases that you want to access in GE Digital APM.

    The role should have read and drill-through permissions. If the Work History database already has a View role defined, then you should add the user to this role. For more information, consult the MSDN documentation regarding Roles and Permissions for Analysis Services.

    		This step is required.
    6 Verify that your event and asset criticality data meet the standard classification requirements, and modify the event or asset criticality data for the Work History cube as needed.This step is required.
    7 Localize the event and equipment values in GE Digital APM .This step is required only if you want to localize the event and equipment values in the Work History cube.
    8 Schedule cubes for processing on the SQL Server Analysis Server.This step is required.
    9 Update the existing Analysis Services Cube records so that GE Digital APM connects to the cube using the HTTP/ HTTPS access.This step is required.
  • Upgrade from any version V3.4.5 through V3.4.5.0.1.4
    StepTaskNotes
    1Migrate your SQL Server Analysis Services database and cubes to the following supported SQL Server Analysis Services versions:
    • 2012
    • 2014
    		This step is required only if you were previously using SQL Server Analysis Services 2008 R2.
    2Configure SQL Server Analysis Server for HTTP or HTTPS access using basic authentication.This step is required.
    3 Deploy Work History Analysis Services database.

    This Work History cube is a replacement for the Equipment and Functional Location Work History cubes in the Meridium_Event_Analysis database.
    Important: Before executing this step, ensure that the Security User who will run the Analysis Services Deployment Wizard has been granted View permissions to the cubes associated with the Metric Views, and that the cubes are active.

    This step is required.

    4Create a Windows User on the Analysis Server or in your organization’s Active Directory.
    The user name requires minimum privileges and will only be used by the GE Digital APM Server to connect to the cubes. It is recommended that:
    • The password for this user should never expire.
    • The user should be restricted to change password.
    • The user should be restricted to log in to others servers (e.g.,meridium_ssas_user).
    		This step is required.
    5Add the user created in Step 4 to a role on all SQL Analysis Services databases that you want to access in GE Digital APM.

    The role should have read and drill-through permissions. If the Work History database already has a View role defined, then you should add the user to this role. For more information, consult the MSDN documentation regarding Roles and Permissions for Analysis Services.

    		This step is required.
    6 Verify that your event and asset criticality data meet the standard classification requirements, and modify the event or asset criticality data for the Work History cube as needed. This step is required.
    7 Localize the event and equipment values in GE Digital APM .This step is required only if you want to localize the event and equipment values in the Work History cube.
    8 Schedule cubes for processing on the SQL Server Analysis Server.This step is required.
    9 Update the existing Analysis Services Cube records so that GE Digital APM connects to the cube using the HTTP/ HTTPS access.This step is required.

About Configuring a Cube for Usage Metrics Tracking

You can track the activity of the users in your system. Usage metrics are stored in the MI_SEC_LOG_EVENTS system table. When a user logs in to GE Digital APM, actions of the user are stored in batches for that session in the MI_SEC_LOG_EVENTS table.

The MI_SEC_LOG_EVENTS table records the following events:
  • Successful logins
  • Failed logins
  • Password changes
  • User account creation, activation, deactivation, modification
  • Session expiry
The following table describes the columns that exist in the MI_SEC_LOG_EVENTS table:
Column IDDescription
SECL_KEYStores the values that identify the events in the MI_SEC_LOG_EVENTS table.
SECL_EVENT_NMStores the names of the events.
SECL_USER_IDStores the user IDs of the users who attempt to log in to GE Digital APM.
SECL_ADMIN_IDStores the user IDs of the Administrators who create, update, and delete users.
LAST_UPDT_DTStores the value that identifies the date and time when a record was last updated.
Note: Usage metrics are recorded only for activities performed via GE Digital APM. Usage metrics are not recorded for activities performed in the GE Digital APM Administrative applications.

To view the usage metrics that have been tracked for your system, you must create a cube based upon the MI_SEC_LOG_EVENTS table. After you create the cube, you must join the MI_SEC_LOG_EVENTS and the MIV_MI_IS_A_USER tables. You must also join the MIV_MI_IS_A_USER and MIV_MI_HUMAN_RESOURCE tables.

Note: Before you use the cube in the Metrics and Scorecards module, you must enable usage metrics tracking via the Monitoring page in Configuration Manager .

About Scheduling Cubes for Processing

An Analysis Services cube is a combination of measures and dimensions that together determine how a set of data can be viewed and analyzed. A cube is a static object and initially represents the data that existed in Analysis Services for the selected measures and dimensions when the cube was created. To keep a cube current, it must be processed regularly, whereby the cube is updated with the most current data in Analysis Services.

To make sure that a cube always provides users with the most current data, you should schedule it for processing regularly, usually on a daily basis. One way to process cubes and shared dimensions successfully is to do so manually on the Analysis Server. Using this method, you can process shared dimensions first, and then process the related cubes. Processing cubes manually, however, is not a viable option if you have many cubes that you want to process on a daily basis.

Instead, a preferable option would be to schedule cubes for processing using Data Transformation Services (DTS). This functionality is available in the SQL Server Business Intelligence Development Studio, which is included in SQL Server Standard Edition. For details on creating a DTS package that can be used to process objects according to a custom schedule, see your SQL Server documentation.

Install SQL Server Analysis Services on the Server

SQL Server Analysis Services is the foundation for the GE Digital APM Metrics and Scorecards module because it serves as a storage and management mechanism for cubes, which can then be accessed and viewed via GE Digital APM. To support Metrics and Scorecards features, SQL Server Analysis Services must be installed on the machine that will serve as the Analysis Server. The Analysis Server must be set up as a machine that is separate from the GE Digital APM Application Server.

Where Does This Software Need to Be Installed?

SQL Server Analysis Services must be installed on the machine that will function as the Analysis Server. You do not need to install any SQL Server components on the Application Server to support the Metrics and Scorecards functionality.

Performing the Installation

SQL Server Analysis Services can be installed using the SQL Server Standard Edition installation package, which you may have received from GE Digital APM or from a third-party vendor, depending upon the licensing options you selected when you purchased the GE Digital APM product. Instructions for performing the installation can be found in the documentation included in the SQL Server Standard Edition installation package.

Creating the Analysis Services Database, Data Source, and Cubes

In addition to creating the Analysis Services database, data source, and cubes, the cubes must be processed before they will be available for use in the GE Digital APM system. For details on completing these tasks, consult your SQL Server documentation.

Migrate SQL Server Cubes

About This Task

If you are upgrading from a previous version of GE Digital APM and you have existing Metrics and Scorecards objects (e.g., Metric Views and KPIs) that are based upon SQL Server 2005 or SQL Server 2008 R2 Analysis Services cubes, you may be able to migrate your cubes while maintaining the proper functioning of your existing GE Digital APM objects.
  • If you have SQL Server Server 2008 cubes, you must migrate them to SQL Server 2012.
  • If you have SQL Server 2012 cubes, you can migrate them to SQL Server 2014.

The following workflow provides a general overview of the process for migrating cubes from an older version of SQL Server Analysis Services to a newer version of SQL Server Analysis Services. For more details, you should see your SQL Server documentation.

Important: Depending upon the complexity of your cubes, you may or may not be able to migrate them successfully. We recommend that you attempt to migrate them using the following procedure. If you review the cubes after the migration and determine that the migration was not successful, the cubes will need to be rebuilt. In that case, any KPIs and Metric Views that were based upon those cubes must also be rebuilt.

Procedure

  1. On the SQL Server Analysis Services Server where the older version of SQL Server Analysis Services is installed, open the SQL Server Management Studio window.
  2. Connect to the SQL Sever Analysis Services database that you want to upgrade.
  3. In the Object Explorer pane, right-click Databases, and select Backup.
    The Backup Database - <Database Name> window appears, where <Database Name> is the name of the database that you want to upgrade.
  4. To the right of the Backup file box, select the Browse button, and specify the location where the database will be backed up.
  5. Specify any additional settings, and then select OK.
    The selected database is saved to an .ABF file in the specified location.
  6. Open the SQL Server Management Studio window for the new version of SQL Server Analysis Services.
  7. In the Object Explorer pane, right-click Databases, and select New Database.
    The New Database window appears.
  8. In the Database name box, enter a name for the database that you are migrating to the new version of SQL Server Analysis Services.
  9. Specify any additional settings, and then select OK.
    The specified database is created, and a corresponding node appears in the Object Explorer pane.
  10. Right-click the node representing the new database, and then select Restore.
    The Restore Database window appears.
  11. In the Backup file, enter the file path or select the Browse button and navigate to the database file that you backed up in step 5.
  12. Specify an additional settings, and then select OK.
    Your SQL Server Analysis Services database is migrated to the new SQL Server Analysis Services version.
  13. In the GE Digital APM, in the Metrics and Scorecards module, modify the remaining properties of each Analysis Services Cube record, including selecting the appropriate new SQL Server Analysis Server. You can do by using the Manage Cubes page in the Metrics and Scorecards module.
  14. View existing objects (e.g. Metric Views and KPIs) that are based upon the migrated cubes to ensure that the correct data is being displayed. If the correct data is not displayed, rebuild the cubes and the objects that are based upon them. For details on rebuilding cubes, see your SQL Server documentation.

Deploy the Work History Cube

Procedure

  1. Copy the Cubes folder from the Release CD to the SQL Server Analysis Services server.
  2. On the SQL Server Analysis Services server, in the Cubes folder, select the Work History folder.
    The following files and folders appear:
    • Work_History.asdatabase
    • Work_History.configsettings
    • Work_History.deploymentoptions
    • Work_History.deploymenttargets
    • Work_History.asassemblylocations
    • MDXFunctions folder
  3. Run the Analysis Services Deployment Wizard program.
    The Welcome page appears.
  4. Select Next.
  5. When the wizard prompts you to choose the database file, navigate to the Work History folder, and then select the Work History.asdatabase file.
  6. Perform all steps of the wizard to deploy the Work History database to the SQL Server Analysis Services server.
    Note: For more information, refer to the MSDN documentation regarding Analysis Services Deployment Wizard.

About Modifying the Work History Cube

The baseline Work History cube provided with the Metrics and Scorecards module uses the following standard classifications for event and asset criticality data. If the event or asset criticality data in your database cannot be classified as one of following the standard IDs, the data, by default, will be classified as Unknown.

  • Event Type
    • Standard Event Types
      • ID: Miscellaneous; Caption: Miscellaneous
      • ID: PM/PdM; Caption: PM/PdM
      • ID: Repair; Caption: Repair
      • ID: Unknown; Caption: Unknown
  • Event Breakdown Indicator
    • Standard Event Breakdown Indicators
      • ID: N, Caption: N
      • ID: Y, Caption: Y
      • ID: Unknown, Caption: Unknown
  • Event Priority
    • Standard Event Priorities
      • ID: 1, Caption: Very Low
      • ID: 2, Caption: Low
      • ID: 3, Caption: Medium
      • ID: 4, Caption: High
      • ID: 5, Caption: Emergency
      • ID: Unknown, Caption: Unknown
  • Event Detection Method
    • Standard Event Detection Methods
      • ID: 0001, Caption: Continuous Condition Monitoring
      • ID: 0002, Caption: Corrective Maintenance
      • ID: 0003, Caption: Formal Inspection
      • ID: 0004, Caption: Operator Routine Observation
      • ID: 0005, Caption: Periodic Condition Monitoring
      • ID: 0006, Caption: Preventive Maintenance
      • ID: 0007, Caption: Production Interference
      • ID: 0008, Caption: Radar Operator Observation
      • ID: Unknown, Caption: Unknown
  • Asset Criticality Data
    • Standard Asset Criticality Data
      • ID: A, Caption: High
      • ID: B, Caption: Medium
      • ID: C, Caption: Low
      • ID: Unknown, Caption: Unknown

Modify the Event or Asset Criticality Data for Work History Cube

If the event or asset criticality data in your database does not match with the standard IDs used for the work history cube, then you have to modify the corresponding views on the server or map the event or asset criticality data to the standard event or asset criticality data using the corresponding families.

Modify the Non-Standard Event Type Data Using the View

Before You Begin

Procedure

  1. In the Views, select MIV_MI_FAC_WORK_HSTY view, and then run the following query to check if the Event Type data matches the standard classification defined.

    SELECT distinct MI_EVENT_TYP_CHR from MI_EVENT

  2. Verify if the results match the standard event type IDs defined by the Work History cube.
  3. If the results do not match, then modify the case statement CASE MI_EVENT_TYP_CHR in the view to display the standard event type IDs.

Example

Suppose the distinct Event Types returned by the query run in Step 1 are Miscellaneous, Repair ,PM/PdM, and Inspection and if Inspection event in your data should be PM/PdM event, then modify the CASE statement in the View as follows:
CASE MI_EVENT_TYP_CHR

 WHEN 'Miscellaneous' THEN 'Miscellaneous'

 WHEN 'PM/PdM' THEN 'PM/PdM'

 WHEN 'Repair' THEN 'Repair'

 WHEN 'Inspection' THEN 'PM/PdM'

 ELSE 'Unknown'

END AS EventType

Modify the Non-Standard Event Priority Data Using the View

Before You Begin

Procedure

  1. In the Views, select MIV_MI_FAC_WORK_HSTY view, and then run the following queries to check if the Event priority data matches the standard classification defined.

    SELECT distinct MI_EVWKHIST_ORDR_PRTY_C from MI_EVWKHIST

    SELECT distinct MI_EVWKHIST_RQST_PRTY_C from MI_EVWKHIST

  2. Verify if the results match the standard event priority IDs defined by the Work History cube.
  3. If the results do not match, then modify the case statement CASE ISNULL(MI_EVWKHIST_ORDR_PRTY_C, MI_EVWKHIST_RQST_PRTY_C) in the view to display the standard event priority IDs.

Example

Suppose the distinct Event Priorities returned by the query are 1, 2,3, 4,5, and M and if M in your data should be event priority 3, then you should modify the CASE statement in View as:
CASE ISNULL(MI_EVWKHIST_ORDR_PRTY_C, MI_EVWKHIST_RQST_PRTY_C)

WHEN 'Very Low' THEN '1'

WHEN 'Low' THEN '2'

WHEN 'Medium' THEN '3'

WHEN 'High' THEN '4'

WHEN 'Emergency' THEN '5'

WHEN '1' THEN '1'

WHEN '2' THEN '2'

WHEN '3' THEN '3'

WHEN '4' THEN '4'

WHEN '5' THEN '5'

WHEN 'M' THEN '3'

ELSE 'Unknown'

END AS Priority

Modify the Non-Standard Event Detection Method Data Using the View

Before You Begin

Procedure

  1. In the Views, select MIV_MI_FAC_WORK_HSTY view, and then run the following queries to check if the Event detection method data matches the standard classification defined.

    SELECT distinct MI_EVWKHIST_DETCT_MTHD_CD_C from MI_EVWKHIST

  2. Verify if the results match the standard event detection method IDs defined by the Work History cube.
  3. If the results do not match, then modify the case statement CASE MI_EVWKHIST_DETCT_MTHD_CD_C in the view to display standard event detection method IDs.

Example

Suppose distinct Event Detection Methods returned by the query are 0001, 0002,0003, 0004,0005,0006,0007,0008, and 0009 and if 0009 in your data should be 0001 event detection method, then you should modify the CASE statement in View as:
CASE MI_EVWKHIST_DETCT_MTHD_CD_C

WHEN 'Continous Condition Monitoring' THEN '0001'

WHEN 'Corrective Maintenance' THEN '0002'

WHEN 'Formal Inspection' THEN '0003'

WHEN 'Operator Routine Observation' THEN '0004'

WHEN 'Periodic Condition Monitoring' THEN '0005'

WHEN 'Preventive Maintenance' THEN '0006'

WHEN 'Production Interference' THEN '0007'

WHEN 'Radar operator Observation' THEN '0008'

WHEN '0001' THEN '0001'

WHEN '0002' THEN '0002'

WHEN '0003' THEN '0003'

WHEN '0004' THEN '0004'

WHEN '0005' THEN '0005'

WHEN '0006' THEN '0006'

WHEN '0007' THEN '0007'

WHEN '0008' THEN '0008'

WHEN '0009' THEN '0001'

ELSE 'Unknown'

END AS DetectionMethod

Modify the Non-Standard Event Breakdown Data Using the View

Before You Begin

Procedure

  1. In the Views, select MIV_MI_FAC_WORK_HSTY view and then run the following query to check if the Event Breakdown data matches the standard classification defined.

    SELECT distinct MI_EVWKHIST_BRKDN_IND_F from MI_EVWKHIST

  2. Verify if the results match the standard event breakdown IDs defined by the Work History cube.
  3. If the results do not match, then modify the case statement CASE MI_EVWKHIST_BRKDN_IND_F in the view to display the standard event breakdown IDs.

Example

Suppose the distinct Event Breakdown returned by the query is Y, N, and No and if No in your data is should be N event breakdown, then you should modify the CASE statement in View as:
CASE MI_EVWKHIST_BRKDN_IND_F

 WHEN 'Y' THEN 'Y'

 WHEN 'N' THEN 'N'

 WHEN 'No' THEN 'N'

 ELSE 'Unknown'

END AS Breakdown

Modify the Non-Standard Equipment Criticality Data Using the View

Before You Begin

Procedure

  1. In the Views, select MIV_MI_FAC_EQUIPMENT view, and then run the following queries to check if the Equipment Criticality data matches the standard classification defined.

    SELECT distinct MI_EQUIP000_CRITI_MTHD_IND_C from MI_EQUIP000

  2. Verify if the results match the standard equipment criticality IDs defined by the Work History cube.
  3. If the results do not match, then modify the case statement CASE MI_EQUIP000_CRITI_IND_C in the view to display standard equipment criticality IDs.

Example

Suppose distinct Equipment Criticality returned by the query in Step 1 is A, B, C, and H and if H in your data is actually A equipment criticality ID, then you should modify the CASE statement in the View as:
CASE MI_EQUIP000_CRITI_IND_C

WHEN 'HIGH' THEN 'A'

WHEN 'Medium' THEN 'B'

WHEN 'Low' THEN 'C'

WHEN 'A' THEN 'A'

WHEN 'B' THEN 'B'

WHEN 'C' THEN 'C'

WHEN 'H' THEN 'A'

ELSE 'Unknown'

END AS EquipmentCriticality

Modify the Non-Standard Functional Location Criticality Data Using the View

Before You Begin

Procedure

  1. In the Views, select MIV_MI_FAC_FNC_LOC view, and then run the following queries to check if the Functional Location Criticality data matches the standard classification defined.

    SELECT distinct MI_FNCLOC00_CRTCAL_IND_C from MI_FNCLOC00

  2. Verify if the results match the standard functional location criticality IDs defined by the Work History cube.
  3. If the results do not match, then modify the case statement CASE A.MI_FNCLOC00_CRTCAL_IND_C in the view to display standard functional location criticality IDs.

Example

Suppose the distinct functional location criticality returned by the query in Step 1 is A, B,C, and M and if M in your data should be B functional location criticality ID, then you should modify the CASE statement in the View as:
CASE A.MI_FNCLOC00_CRTCAL_IND_C

WHEN 'HIGH' THEN 'A'

WHEN 'Medium' THEN 'B'

WHEN 'Low' THEN 'C'

WHEN 'A' THEN 'A'

WHEN 'B' THEN 'B'

WHEN 'C' THEN 'C'

WHEN 'M' THEN 'B'

ELSE 'Unknown'

END AS FunctionalLocationCriticality

Map the Non-Standard Event Type Data to Standard Event Type IDs Using Queries for Event Type Dimension Family

This topic describes how to map the event type data available in your database to the standard event type data defined for a work history cube.

Procedure

  1. In the module navigation menu, select Tools, and then select Queries.
    The Query page appears.
  2. Select Create New.
    The Select a Family or Query window appears.
  3. Search for the Event Type Dimension family, and then select Add.
    The Design workspace appears.
  4. Select the SQL tab.
    The SQL workspace appears.
  5. Run the query SELECT [MI_DIM_EVENT_TYPE].[EventType] "EventType", [MI_DIM_EVENT_TYPE].[EventTypeCaption] "EventTypeCaption" FROM [MI_DIM_EVENT_TYPE].
    The standard event type data available in GE Digital APM appears in the query results.
  6. Run the query SELECT distinct MI_EVENT_TYP_CHR from MI_EVENT.
    The event type data available in your database appears in the query results.
  7. Verify if the event type data returned by the query in Step 6 matches the standard event type IDs returned by the query in Step 5.
  8. If the results do not match, perform the following steps to map the event type data available in your database with the standard event type ID available in GE Digital APM:
    1. In the SQL workspace, enter the following update query:
      UPDATE [MI_DIM_EVENT_TYPE] SET [MI_DIM_EVENT_TYPE].[EventTypeCaption] = '<New Data>' WHERE [MI_DIM_EVENT_TYPE].[EventTypeCaption] = '<Standard Data Caption>'
      Note: In this query:
      • <New Data> denotes the event type data that you want to map to the standard event type ID available in GE Digital APM.
      • <Standard Data Caption> denotes the captions corresponding to the standard event type data available in GE Digital APM.
    2. Replace <New Data> with a value that you want to map with the standard event type data available in GE Digital APM.
    3. Replace <Standard Data Caption> with the caption available for the corresponding event type ID to which the new event type data will be mapped.
    4. Run the query.
      The Execute Query window appears.
    5. Select Yes.
      The event type data is mapped to the standard event type ID defined for the work history cube.

Map an Event Type to a Standard Event Type ID

The following standard event type data is returned by the query run in Step 5.
EventTypeEventTypeCaption
MiscellaneousMiscellaneous
PM/PdMPM/PdM
RepairRepair
UnknownUnknown
The following event type data is returned by the query run in Step 6:
  • INSPECTION
  • PM/PdM
  • Reading
  • Repair
If you want to map the event type INSPECTION to the standard event type ID Miscellaneous:
  • Run the query UPDATE [MI_DIM_EVENT_TYPE] SET [MI_DIM_EVENT_TYPE].[EventTypeCaption] = 'INSPECTION' WHERE [MI_DIM_EVENT_TYPE].[EventTypeCaption] = 'Miscellaneous'.

    The event type INSPECTION is mapped to the standard event type ID Miscellaneous.

Map the Non-Standard Event Priority Data to Standard Event Priority IDs Using Queries for Event Priority Dimension Family

This topic describes how to map the event priority data available in your database to the standard event priority data defined for a work history cube.

Procedure

  1. In the module navigation menu, select Tools, and then select Queries.
    The Query page appears.
  2. Select Create New.
    The Select a Family or Query window appears.
  3. Search for the Event Priority Dimension family, and then select Add.
    The Design workspace appears.
  4. Select the SQL tab.
    The SQL workspace appears.
  5. Run the query SELECT [MI_DIM_EVENT_PRIORITY].[Priority] "Priority", [MI_DIM_EVENT_PRIORITY].[PriorityCaption] "PriorityCaption" FROM [MI_DIM_EVENT_PRIORITY].
    The standard event priority data available in GE Digital APM appears in the query results.
  6. Run the following queries:
    • SELECT distinct MI_EVWKHIST_BRKDN_IND_F from MI_EVWKHIST
    • SELECT distinct MI_EVWKHIST_RQST_PRTY_C from MI_EVWKHIST
    The event priority data available in your database appears in the query results.
  7. Verify if the event priority data returned by the query in Step 6 matches the standard event priority IDs returned by the query in Step 5.
  8. If the results do not match, perform the following steps to map the event priority data available in your database with the standard event priority ID available in GE Digital APM:
    1. In the SQL workspace, enter the following update query:
      UPDATE [MI_DIM_EVENT_PRIORITY] SET [MI_DIM_EVENT_PRIORITY].[PriorityCaption] = '<New Data>' WHERE [MI_DIM_EVENT_PRIORITY].[PriorityCaption] = '<Standard Data Caption>'
      Note: In this query:
      • <New Data> denotes the event priority data that you want to map to the standard event priority ID available in GE Digital APM.
      • <Standard Data Caption> denotes the captions corresponding to the standard event priority data available in GE Digital APM.
    2. Replace <New Data> with a value that you want to map with the standard event priority data available in GE Digital APM.
    3. Replace <Standard Data Caption> with the caption available for the corresponding event priority ID to which the new event priority data will be mapped.
    4. Run the query.
      The Execute Query window appears.
    5. Select Yes.
      The event priority data is mapped to the standard event priority ID defined for the work history cube.

Map Event Priority Data to a Standard Event Priority ID

The following standard event priority data is returned by the query run in Step 5.
PriorityPriorityCaption
1Very Low
2Low
3Medium
4High
5Emergency
UnknownUnknown
The following event priority data is returned by the query run in Step 6:
  • 1
  • 2
  • 3
  • 4
If you want to map the event priority data 1 to the standard event priority ID 5:
  • Run the query UPDATE [MI_DIM_EVENT_PRIORITY] SET [MI_DIM_EVENT_PRIORITY].[PriorityCaption] = '1' WHERE [MI_DIM_EVENT_PRIORITY].[PriorityCaption] = 'Emergency’.

    The event priority data 1 is mapped to the standard event priority ID 5.

Map the Non-Standard Event Detection Methods to Standard Event Detection Method IDs Using Queries for Event Detection Method Dimension Family

This topic describes how to map the event detection methods available in your database to the standard event detection methods defined for a work history cube.

Procedure

  1. In the module navigation menu, select Tools, and then select Queries.
    The Query page appears.
  2. Select Create New.
    The Select a Family or Query window appears.
  3. Search for the Event Detection Method Dimension family, and then select Add.
    The Design workspace appears.
  4. Select the SQL tab.
    The SQL workspace appears.
  5. Run the query SELECT [MI_DIM_EVENT_DETECTION].[DetectionMethod] "DetectionMethod", [MI_DIM_EVENT_DETECTION].[DetectionMethodCaption] "DetectionMethodCaption" FROM [MI_DIM_EVENT_DETECTION].
    The standard event detection methods available in GE Digital APM appears in the query results.
  6. Run the query SELECT distinct MI_EVWKHIST_DETCT_MTHD_CD_C from MI_EVWKHIST.
    The event detection methods available in your database appears in the query results.
  7. Verify if the event detection methods returned by the query in Step 6 match the standard event detection method IDs returned by the query in Step 5.
  8. If the results do not match, perform the following steps to map the event detection methods available in your database with the standard event detection method ID available in GE Digital APM:
    1. In the SQL workspace, enter the following update query:
      UPDATE [MI_DIM_EVENT_DETECTION] SET [MI_DIM_EVENT_DETECTION].[DetectionMethod] = '<New Data>' WHERE [MI_DIM_EVENT_DETECTION].[DetectionMethod] = '<Standard Data Caption>'
      Note: In this query:
      • <New Data> denotes the event detection method that you want to map to the standard event detection method ID available in GE Digital APM.
      • <Standard Data Caption> denotes the captions corresponding to the standard event detection method available in GE Digital APM.
    2. Replace <New Data> with a value that you want to map with the standard event detection method available in GE Digital APM.
    3. Replace <Standard Data Caption> with the caption available for the corresponding event detection method ID to which the new event detection method will be mapped.
    4. Run the query.
      The Execute Query window appears.
    5. Select Yes.
      The event detection method is mapped to the standard event detection method ID defined for the work history cube.

Map an Event Detection Method to a Standard Event Detection Method ID

The following standard event detection methods are returned by the query run in Step 5.
DetectionMethodDetectionMethodCaption
0001Continuous Condition Monitoring
0002Corrective Maintenance
0003Formal Inspection
0004Operator Routine Observation
0005Periodic Condition Monitoring
0006Preventive Maintenance
0007Production Interference
0008Radar Operator observation
The following event detection methods are returned by the query run in Step 6:
  • Inspection
  • Observation
  • Preventive Maintenance
  • Production Interference
If you want to map the event detection method Inspection to the standard event detection method ID 0001:
  • Run the query UPDATE [MI_DIM_EVENT_DETECTION] SET [MI_DIM_EVENT_DETECTION].[DetectionMethod] = 'Inspection' WHERE [MI_DIM_EVENT_DETECTION].[DetectionMethod] = '0001'.

    The event detection method Inspection is mapped to the standard event detection method ID 0001.

Map the Non-Standard Event Breakdown Data to Standard Event Breakdown IDs Using Queries for Event Breakdown Dimension Family

This topic describes how to map the event breakdown data available in your database to the standard event breakdown data defined for a work history cube.

Procedure

  1. In the module navigation menu, select Tools, and then select Queries.
    The Query page appears.
  2. Select Create New.
    The Select a Family or Query window appears.
  3. Search for the Event Breakdown Dimension family, and then select Add.
    The Design workspace appears.
  4. Select the SQL tab.
    The SQL workspace appears.
  5. Run the query SELECT [MI_DIM_EVENT_BREAKDOWN].[Breakdown] "Breakdown", [MI_DIM_EVENT_BREAKDOWN].[BreakdownCaption] "BreakdownCaption" FROM [MI_DIM_EVENT_BREAKDOWN].
    The standard event breakdown data available in GE Digital APM appears in the query results.
  6. Run the query SELECT distinct MI_EVWKHIST_BRKDN_IND_F from MI_EVWKHIST.
    The event breakdown data available in your database appears in the query results.
  7. Verify if the event breakdown data returned by the query in Step 6 matches the standard event breakdown IDs returned by the query in Step 5.
  8. If the results do not match, perform the following steps to map the event breakdown data available in your database with the standard event breakdown ID available in GE Digital APM:
    1. In the SQL workspace, enter the following update query:
      UPDATE [MI_DIM_EVENT_BREAKDOWN] SET [MI_DIM_EVENT_BREAKDOWN].[BreakdownCaption] = '<New Data>' WHERE [MI_DIM_EVENT_BREAKDOWN].[BreakdownCaption] = '<Standard Data Caption>'
      Note: In this query:
      • <New Data> denotes the event breakdown data that you want to map to the standard event breakdown ID available in GE Digital APM.
      • <Standard Data Caption> denotes the captions corresponding to the standard event breakdown data available in GE Digital APM.
    2. Replace <New Data> with a value that you want to map with the standard event breakdown data available in GE Digital APM.
    3. Replace <Standard Data Caption> with the caption available for the corresponding event breakdown ID to which the new event breakdown data will be mapped.
    4. Run the query.
      The Execute Query window appears.
    5. Select Yes.
      The event breakdown data is mapped to the standard event breakdown ID defined for the work history cube.

Map an Event Breakdown Indicator to a Standard Event Breakdown ID

The following standard event breakdown data is returned by the query run in Step 5.
BreakdownBreakdownCaption
NN
UnknownUnknown
YY
The following event breakdown data is returned by the query run in Step 6:
  • No
  • Yes
  • Unknown
If you want to map the event breakdown indicator Yes to the standard event breakdown ID Y:
  • Run the query UPDATE [MI_DIM_EVENT_BREAKDOWN] SET [MI_DIM_EVENT_BREAKDOWN].[BreakdownCaption] = 'Yes' WHERE [MI_DIM_EVENT_BREAKDOWN].[BreakdownCaption] = 'Y'.

    The event breakdown indicator Yes is mapped to the standard event breakdown ID Y.

Map the Non-Standard Asset Criticality Data to Standard Asset Criticality IDs Using Queries for Asset Criticality Dimension Family

This topic describes how to map the asset criticality data available in your database to the standard asset criticality IDs defined for a work history cube.

Procedure

  1. In the module navigation menu, select Tools, and then select Queries.
    The Query page appears.
  2. Select Create New.
    The Select a Family or Query window appears.
  3. Search for the Asset Criticality Dimension family, and then select Add.
    The Design workspace appears.
  4. Select the SQL tab.
    The SQL workspace appears.
  5. Run the query SELECT [MI_DIM_ASSET_CRITICALITY].[Criticality] "Criticality", [MI_DIM_ASSET_CRITICALITY].[CriticalityCaption] "CriticalityCaption" FROM [MI_DIM_ASSET_CRITICALITY].
    The standard asset criticality data available in GE Digital APM appears in the query results.
  6. Run the following queries:
    • For equipment criticality data, run the query SELECT distinct MI_EQUIP000_CRITI_MTHD_IND_C from MI_EQUIP000.

      The equipment criticality data available in your database appears in the query results.

    • For functional location criticality data, run the query SELECT distinct MI_FNCLOC00_CRTCAL_IND_C from MI_FNCLOC00.

      The functional location criticality data available in your database appears in the query results.

  7. Verify if the asset criticality data returned by the query in Step 6 matches the standard asset criticality IDs returned by the query in Step 5.
  8. If the results do not match, perform the following steps to map the asset criticality data available in your database with the standard asset criticality ID available in GE Digital APM:
    1. In the SQL workspace, enter the following update query:
      UPDATE [MI_DIM_ASSET_CRITICALITY] SET [MI_DIM_ASSET_CRITICALITY].[CriticalityCaption] = '<New Data>' WHERE [MI_DIM_ASSET_CRITICALITY].[CriticalityCaption] = '<Standard Data Caption>'
      Note: In this query:
      • <New Data> denotes the asset criticality data that you want to map to the standard asset criticality ID available in GE Digital APM.
      • <Standard Data Caption> denotes the captions corresponding to the standard asset criticality data available in GE Digital APM.
    2. Replace <New Data> with a value that you want to map with the standard asset criticality data available in GE Digital APM.
    3. Replace <Standard Data Caption> with the caption available for the corresponding asset criticality ID to which the new asset criticality data will be mapped.
    4. Run the query.
      The Execute Query window appears.
    5. Select Yes.
      The asset criticality data is mapped to the standard asset criticality ID defined for the work history cube.

Map Asset Criticality Data to a Standard Asset Criticality ID

The following standard asset criticality data are returned by the query run in Step 5.
CriticalityCriticalityCaption
AHigh
BMedium
CLow
UnknownUnknown
The following asset criticality data are returned by the query run in Step 6:
  • X
  • Y
  • Z
  • H
If you want to map the asset criticality data X to the standard asset criticality ID A:
  • Run the query UPDATE [MI_DIM_ASSET_CRITICALITY] SET [MI_DIM_ASSET_CRITICALITY].[CriticalityCaption] = 'X' WHERE [MI_DIM_ASSET_CRITICALITY].[CriticalityCaption] = 'High'.

    The asset criticality data X is mapped to the standard asset criticality ID A.

Localize the Event or Asset Criticality Values

By default, the Meridium Work History cube displays the event and asset criticality data in English. However, you can modify the event or asset criticality values to other languages supported by GE Digital APM. The examples in this topic explain how to modify event and asset criticality values, and how you can verify, in GE Digital APM, that those modifications have been implemented.

Before You Begin

  • Log in to SQL Server Management Studio and connect to the database.

Example: Localize the Event Type Values

Procedure

  1. In the Tables, select the table MI_DIM_EVENT_TYPE.
    The table values appear, displaying the event type ID and the event caption.
  2. In the EventTypeCaption column, select the cell for the event type that you want to localize, and then manually modify the caption.
  3. Save the modification, and then process the cube.
  4. Log in to GE Digital APM.
  5. Access the Metrics and Scorecards page and create a new Metric View.
    The design page for the Metric View appears.
  6. In the Metric Views design page, in the Rows/X-Axis subsection, select .
    The Add to Rows window appears.
  7. In the Event Type, select Event Type-Breakdown, and then select Event Type.
    The caption for the event breakdown values appears in the language to which you have modified.

Example: Localize the Event Breakdown Values

Procedure

  1. In the Tables, select the table MI_DIM_EVENT_BREAKDOWN.
    The table values appear, displaying the breakdown ID and the breakdown caption.
  2. In the BreakdownCaption column, select the cell for the breakdown that you want to localize, and then manually modify the caption.
  3. Save the modification, and then process the cube.
  4. Log in to GE Digital APM.
  5. Access the Metrics and Scorecards page and create a new Metric View.
    The design page for the Metric View appears.
  6. In the Metric Views design page, in the Rows/X-Axis subsection, select .
    The Add to Rows window appears.
  7. In the Event Type, select Event Type-Breakdown, and then select Breakdown.
    The caption for the event type values appears in the language to which you have modified.

Example: Localize the Event Priority Values

Procedure

  1. In the Tables, select the table MI_DIM_EVENT_PRIORITY.
    The table values appear, displaying the Priority ID and the Priority caption.
  2. In the PriorityCaption column, select the cell for the priority caption that you want to localize, and then manually modify the caption.
  3. Save the modification, and then process the cube.
  4. Log in to GE Digital APM.
  5. Access the Metrics and Scorecards page and create a new Metric View.
    The design page for the Metric View appears.
  6. In the Metric Views design page, in the Rows/X-Axis subsection, select .
    The Add to Rows window appears.
  7. In the Event Priority, select Priority, and then select Priority.
    The caption for the priorities appears in the language to which you have modified.

Example: Localize Event Detection Method Values

Procedure

  1. In the Tables, select the table MI_DIM_EVENT_DETECTION_METHOD.
    The table values appear, displaying the event type ID and the event caption.
  2. In the DetectionMethodCaption column, select the cell for the detection method that you want to localize, and then manually modify the caption.
  3. Save the modification, and then process the cube.
  4. Log in to GE Digital APM.
  5. Access the Metrics and Scorecards page and create a new Metric View.
    The design page for the Metric View appears.
  6. In the Metric Views design page, in the Rows/X-Axis subsection, select .
    The Add to Rows window appears.
  7. In the Event Detection, select Detection, and then select Detection Method.
    The caption of the Detection Method values appear in the language to which it was modified.

Example: Localize Equipment Criticality Values

Procedure

  1. In the Tables, select the table MI_DIM_ASSET_CRITICALITY.
    The table values appear, displaying the Criticality ID and the Criticality caption.
  2. In the CriticalityCaption column, select the cell for the caption that you want to localize, and then manually modify the caption.
  3. Save the modification, and then process the cube.
  4. Log in to GE Digital APM.
  5. Access the Metrics and Scorecards page and create a new Metric View.
    The design page for the Metric View appears.
  6. In the Metric Views design page, in the Rows/X-Axis subsection, select .
    The Add to Rows window appears.
  7. In the Equipment, select Criticality, and then select Criticality.
    The caption of the criticality values appear in the language to which it was modified.

Example: Localize Functional Location Criticality Values

Procedure

  1. In the Tables, select the table MI_DIM_ASSET_CRITICALITY.
    The table values appear, displaying the criticality ID and the criticality caption.
  2. In the CriticalityCaption column, select the cell for the caption that you want to localize, and then manually modify the caption.
  3. Save the modification, and then process the cube.
  4. Log in to GE Digital APM.
  5. Access the Metrics and Scorecards page and create a new Metric View.
    The design page for the Metric View appears.
  6. In the Metric Views design page, in the Rows/X-Axis subsection, select .
    The Add to Rows window appears.
  7. In the Functional Location, select Criticality, and then select Criticality.
    The caption of the functional location criticality values appear in the language to which it was modified.