How to resolve 'Incorrect Model Class for Medical Device CI's' issue for Medigate SGC

[Anne Marie Duff]

Steps to follow for resolving the 'Incorrect Model Class for Medical Devices[cmdb_ci_med_device] CIs’ issue for the Medigate Service Graph Connector

Application Name: Service Graph Connector for Claroty xDome & Medigate

Version: 1.0.11

1. Install the latest available version of the Expanded Model and Asset Classes Application on your ServiceNow Instance. - This step can be skipped if it's already installed.
2. Upgrade the Integration Commons for CMDB Application to Version 2.12
3. Use IntegrationHub ETL to enable the new Cleanse Hardware Model with Model Number Transform Operation
4. Use IntegrationHub ETL to change the Hardware Class mapping for the Target Model ID field 
5. Reprocess the already existing xDome Records in the Staging Table
6. Verify that the Medical Devices[cmdb_ci_med_device] records are populated with a Medical Device Model class

1. Install the latest available version of the Expanded Model and Asset Classes Application on your SN instance

Navigate to the Expanded Model and Asset Classes Application listed in System Applications on your instance and click on the Install button.

Note: This step can be skipped if it's already installed.

2. Upgrade the Integration Commons for CMDB Application to Version 2.12

Navigate to the Integration Commons for CMDB Application listed in System Applications on your instance and click on the Upgrade button.

3. Use IntegrationHub ETL to enable the new Cleanse Hardware Model with Model Number Transform Operation

Open up the IntegrationHub ETL Application and do the following:

1. Double click on the Sg-xDome Devices Transform Map listed under the SG-xDome CMDB Application
2. Double click on the 2. Prepare Source Data for Map – Preview and Prepare Source Data Step to bring up the Raw Source Data Screen
3. Add a New Cleanse Hardware Model with Model Number Transform Step for generating Model Id by following the steps below: 
   • Click on the New Transform Button
   • Select the Use Source Column option from the New Transform Pulldown Menu
   • Select the Cleanse Hardware Model with Model Number option from the Transform Type Pulldown Menu
   • Enter a Column Name like e.g. model_ent_cleansed in the Output Column Name field  
   • Select manufacturer_cleansed_name from the Company Name Pulldown Menu
   • Select model from the Model Name Pulldown Menu
   • Click on the + icon to add the CI Class Field to the Transform
   • Select x_target_cmdb_class from the CI Class Pulldown Menu
4. Add a New Split Transform Step for parsing Model Name and Model ID from the Output of the above Cleanse Hardware Model with Model Number Transform Step by following the steps below:
   •        Click on the New Transform Button
   •        Select the Use Source Column option from the New Transform Pulldown Menu
   •        Select Split from the Transform Type Pulldown Menu
   •        Populate the Transform Description field to include the name of the column that you are splitting like e.g. model_ent_cleansed
   •        Select the name of the column you are splitting like e.g. model_ent_cleansed from the Input Column menu
   •        Populate the Character Separator field with |||
   •        For the Output Column Name 1, Output Column Name 2, Output Column Name 3, Output Column Name 4 fields enter meaningful names like e.g. model_ent_cleansed_manufacturer_id, model_ent_cleansed_manufacturer_name,  model_ent_cleansed_model_id, model_ent_cleansed_model_name
5. Remove the old Cleanse Hardware Model Transform Step from the Transform Map by doing the following:
   • Click on the Three Lines to the left of the model_cleansed column and select the Delete this and Downstream columns Pulldown Menu Option.

Note: Removing the Old Cleanse Hardware Model Transform step is not essential for changing how Model ID is Populated. Removing it will mean that a Redundant Transform Step isn’t being executed by the RTE thus not impacting Transformation Performance.     

4. Use IntegrationHub ETL to change the Hardware Class mapping for the Target Model ID field

Navigate back to the main Integration Hub ETL Screen, select the Map Data to CMDB and Add Relationships – Select CMDB Classes to Map Source Data Step and do the following:

1. Select Edit Mapping on the Hardware 1 Class
2. Scroll down to the Model ID Field
3. Populate the Source Column with the new model_ent_cleansed_model_id field that was created in Step 2, d.
4. Scroll down to the Model number Field
5. Populate the Source Column with the new model_ent_cleansed_model_name field that was created in Step 2, d.

5. Reprocess the already existing xDome Records in the Staging Table

Navigate to the Import Sets[sys_import_set] Table and do the following:

1. Search for a recent ISET for the SG-xDome Devices Data Source
2. Open this ISET record and click on the Reprocess Related Link
3. Click on the Transform Related Link

Following the steps above triggers the reprocessing of already existing records in the Medigate Staging Table by the RTE. The New Cleanse Hardware Model with Model Number Transform Step will be used instead of the Old Cleanse Hardware Model Step for populating Model ID.

Note: If this is your first time to run the SG-xDome Devices Import Schedule, then open the SG-xDome Devices Import Schedule record and click on the Execute Now pushbutton. This will trigger the a) Loading of Medigate Data into the Medigate Staging Table and b) Transforming the data from this Staging Table before populating it into the various Medigate Device CMDB Tables like e.g. Medical Devices[ cmdb_ci_med_device]

6. Verify that the Medical Devices[cmdb_ci_med_device] records are populated with a Medical Device Model class

Verify that performing all the above steps resolves the Incorrect model class for Medical Devices[cmdb_ci_med_device] Cis issue by doing the following:

1. Navigate to the Medical device models[sn_ent_medical_device_model] Table and confirm that it is populated with Medical Device Model Records
2. Navigate to the Medigate Medical Devices[cmdb_ci_med_device] Table and do the following:

• Open any of the Medical Device Records in the list
• Add the Model ID.Class field to the Form Layout
• Confirm that the new Class field shows Medical device model in the form instead of Hardware model

[David Casper]

I have been able to get this to create models in the correct asset class for another integration, but assets are not being created through the integration. 
If I create a CI manually with the same class/model the asset is created without issue. Anyone run into this?

[infosurahal]

Thank you for this detailed guide, Anne Marie! This step-by-step approach is incredibly helpful for addressing the 'Incorrect Model Class for Medical Devices' issue. I appreciate the clarity in the IntegrationHub ETL processes—especially the transformation steps. Has anyone encountered any challenges while reprocessing the xDome records? Would love to hear any tips or best practices!

[scottl]

The transform, "Cleanse Hardware Model with Model Number" does not work as expected and does not output the model number, and doesn't even add the model number to the newly created Hardware Model.  So what is even the point of it?

[Anne Marie Duff]

Hi Scott,

I recommend that you use the Integration ETL Hub Tool to confirm that Raw data is being populated in the SG-xDome Devices [x_claro_xdome_sgc_staging_devices] Staging Table.

1. Double Click on the Sg-xDome Devices Transform Map listed under the SG-xDome CMDB Application

2. Go to the 2. Prepare Source Data for Map – Preview and Prepare Source Data Step to bring up the Raw Source Data Screen

3.  Navigate to the manufacturer_cleansed_name and model fields in this Raw Data screen to confirm that they have data. These are the Source Fields that are used for the new Cleanse Hardware Model with Model Number Transform.

If you can see that the Raw Source data is there, I'd then double check that for the 3.c "Add a New Cleanse Hardware Model with Model Number Transform" Step above, that you completed the last 2 sections of this step to add the CI Class Field to the New Transform. i.e. 

• Click on the + icon to add the CI Class Field to the Transform
• Select x_target_cmdb_class from the CI Class Pulldown Menu

This part of the Step can be easily missed,

Hoping this helps,

Thanks,

Anne-Marie