Proficy Historian Migration Mapping

Important: There are some differences in how data is identified between the CIMPLICITY and the real-time Collector.

The following lists define how data is mapped from CIMPLICITY to Historian to resolve these differences.

DATA_Log migration mapping.

ALARM_LOG and EVENT_LOG migration mapping.

Mapping guidelines.

DATA_LOG migration mapping

The Historian Migration utility maps data from the CIMPLICITY DATA_LOG to Historian as follows.

Quality mapping

Data Type mapping

Point/Tag attributes mapping

Data attribute mapping

  1. Quality Mapping

CIMPLICITY
Quality Attribute Value

Historian
Quality, Subquality

IS_AVAILABLE and IS_IN_RANGE

and

STALE=FALSE

Good, ihOPCNonspecific

IS_AVAILABLE and IS_IN_RANGE

and

STALE=TRUE

Good, ihOPCLastKnowValue

NOT IS_AVAILABLE

Bad, ihOPCCommFailure

NOT IS_IN_RANGE

Bad, ihOPCOutOfService

DISABLE_WRITE

ALARMED

ALARMS_ENABLED

No effect on Historian quality

No effect on Historian quality

No effect on Historian quality

USER Quality flags

Bad, ihOPCNonspecific

  1. Data Type Mapping

CIMPLICITY Point Types

Historian Data Type

BOOL

SINT

INT

USINT

Integer

Double integer

Double integer

Double integer

REAL

UDINT

Double float

Double float

DINT

UINT

Double Integer

Double Integer

STRING

STRING_20

STRING_8

STRING_80

Variable String

Variable String

Variable String

Variable String

3D_BCD

4D_BCD

BYTE

Not supported

Not supported

Not supported

  1. Point/Tag Attribute Mapping

CIMPLICITY

Historian

Point_id

Tagname

_ENG

Engineering Units

FROM SQL Table

DataType

  1. Data Attribute Mapping

CIMPLICITY

Historian

Timestamp

Timestamp

_VAL

Value

_QUALITY

Quality

Note: Hi and Lo Engineering Units do not exist in CIMPLICITY SQL table; these fields are ignored during the migration.

ALARM_LOG and EVENT_LOG migration mapping

During the Historian migration fields in the ALARM_LOG and EVENT_LOG are mapped to be consistent with fields provided by the OPC Alarm & Event server.

CIMPLICITY

Historian

alarm_message

Description  

Project, resource, alarm_id

Source (project/resource/alarm_id)

timestamp

TimeStamp

generation_time

Endtime

Condition

Subcondition

Event Category

HIGH,MED,LOW,$SYS

Severity

Quality

Mapping Guidelines

AlarmType is as follows.

AlarmType

When read from

ihALARM_CONDITION

ALARM_LOG table

ihALARM_SIMPLE

EVENT_LOG table

Condition and SubCondition are as follows.

For the:

Condition and Subcondition

Alarm log

Exist, only for the Alarm log.

Tag alarm

Are set to Level to match the real time collector.

System tag

Use System.

EventCategory use the following.

For the:

EventCategory

Tag alarm

Level"

System alarm

System

Severity is configurable by user.

Default mapping is as follows.

CIMPLICITY

Historian

HIGH

$SYS

850

MED

500

LOW

150

DataSource is PEAE_MIGRATION.

Source is combination of project/resource/alarm_id.

More information

Proficy Historian migration.