Clarification on Manual Migration 29049670 (Doc ID 2603292.1)

Last updated on JUNE 21, 2023

Applies to:

Goal

Question

What needs to be done for this migration? This needs clarification.


Migration:
NMS has historically allocated the first 11 bits of a 32 bit integer for NMS specific (internal) purposes. NMS has consumed the 11 bits and would like to consume more and as such the quality codes allocated specifically to NMS has gone from 11->16. This will impact projects with SCADA integration in that any SCADA specific (external) quality codes mapped into NMS will need to be mapped to the higher (>2^^15 non-NMS) bits. This will generally involve updates to the following NMS configuration tables:

quality_rules - how to display quality codes in NMS

scada_synonyms - how to translate external (SCADA) qualities into NMS.
-----------------------------------------------------------------------------------------------------------

  The ICCP configuration currently uses quality codes that now fall into the reserved range but it is unclear how the 8 bit quality code from ICCP is mapped to quality codes in NMS.

IccpAdapter.prm:

INSERT INTO quality_rules
( priority, value, string, description, color, location, symbol, off_nominal )
values (2, 2048, 'B', 'Blocked', 80, 1, -1, 'N');
INSERT INTO quality_rules
( priority, value, string, description, color, location, symbol, off_nominal )
values (2, 4096, 'S', 'Substituted', 80, 1, -1, 'N');

What needs to be change to avoid reserved bits in the quality codes?
 

Solution

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.