Migrate Signals

You can migrate signal definitions to the Signal Catalog individually, or perform a mass migration for all signals that do not have any conflicting configuration. Start the migration with the signals without conflicts, then migrate the signals with conflicts one after the other.

The Signal Catalog migration can be done in incremental steps; you do not need to migrate all signals in one batch.

Warning

Signal migration cannot be reverted.

Note

Migrating signals changes the process for PDC changes and adding new signals, see Add New Signal.

In the Catalog column, the Signal Catalog table shows whether a signal key is Not in Catalog, and indicates Conflicts within signal definitions if there are any. The View summary toggle shows the total number of signals Without conflicts, In Catalog, and Use standard metric key.

Requirements

• Migrating the signal properties requires the Models:Admin permission set (see Models Subject) for the DataPortal.
• Signal definitions are stored at the tenant, so the user must be a member of a tenant organization (see Tenant).
• Only valid signal definitions are considered for migration. A valid signal definition:
  • Has no conflicts.
  • Uses a predefined unit; custom units are not supported.
  • Has boundTo: machine, not model.
  • Is a standard signal present in the standard Signal Catalog, or a custom signal using the value.* prefix.

Note

In the DataPortal, signal definitions are not strictly validated against the Proemion Standard Metrics.

Migrate All Signal Definitions Without Conflicts

1. Open Settings > Machine Data Management > Signal catalog.

   

   Figure 1: Signal Catalog table

2. Click Migrate signals to catalog in the upper-right corner.

   Note

   This button is not shown once all signals have already been migrated.

3. Confirm the dialog window that displays the number of signals to be migrated.

✓ When the signal definitions are valid, i.e. meet the Requirements, the success message shows the number of successfully migrated signals. In the Signal Catalog table they get the label In Catalog and can then be managed in the UI, see View and Edit or Delete Signal Details.

Migrate Specific Signal Definitions

1. Open Settings > Machine Data Management > Signal catalog.

2. Click View Signal Details at the end of the row of the desired signal key to open the details page.

   

   Figure 2: Signal definition - Not in Catalog

3. Click Migrate to catalog in the upper-right corner.

   If the signal key does not meet the Requirements, it is not eligible to migrate and the button is greyed out:

   

   Figure 3: Signal not eligible to migrate

4. Confirm the dialog window to start the migration.

✓ A success message indicates the successful migration. In the Signal Catalog table the signal key then gets the label In Catalog.

Migrate Signals With Conflicts

Note

You can display the non-migrated signal definitions by filtering the table on the Not in Catalog option in the Catalog column.

For the general procedure, see Resolve Conflicts. The following sections give guidance on resolving frequently occurring migration conflicts. Contact Service and Support if you run into problems not covered here.

Signal Label Conflicts

Choose the most appropriate signal name. If the conflicting signal names are completely different, this could be a case of two different signals using the same key. Resolve this conflict by updating the PDCs first.

Figure 4: Signal label conflict

Unit Key Conflicts

If custom units are used, check whether an appropriate standard unit is available and select it. If no appropriate standard unit is available, check with support whether it can be added. Otherwise, choose the most appropriate custom unit.

If completely different units are used, resolve the conflict by updating the PDCs first; the PDC transformers and the historical data may also need to be adjusted. Contact support for assistance in that case.

Warning

Be careful when resolving conflicts on different units. The wizard suggests changing units that are assigned wrongly to Proemion Standard Metrics signals, which results in the wrong unit being displayed. Resolve this conflict by updating the PDCs first.

Figure 5: Unit key conflict

Data Type Conflicts

This conflict most likely results from different signals using the same signal key. Resolve it by updating the PDCs first.

Format Conflicts

Check what is the most reasonable formatting for this signal, and use the highest precision formatting.

Figure 6: Format conflict

Min/Max Conflicts

Check the machine's signal specification for the correct values, and use the most narrow range that is still reasonable for this signal.

Logical Type Conflicts

Check the machine's signal specification for the correct signal type, and use the most reasonable signal type. If the options are Measurement or a specific type, usually choose the specific type. Set signals that are counters as Counter with the direction setting.

Figure 7: Logical type conflict

Organization Type Conflicts

Check which organization types the signal should be restricted to, and use the most narrow range.