Tracker Data Logging

  • Tracker data logging files overview.
  • Common Tracker data logging tables.
  • Important PRT logging tables naming requirement.
  • Steps to edit Tracker data logging files.
  • RCO Site logging summary overview.

Tracker data logging files overview

  • Two files contain configuration information about PRT and RCO data logging.
Datalog.idt Lists the tables that PRT and RCO log to.
Data_field.idt Defines the fields in each table.
  • Configuration information is passed back and forth between the Database Logger and these configuration files.

If you change a logged field that has other fields after it then you need to update the offset field to reflect the change in size. So if you change the ATTR_NAME record to a field_len of 32 you need to change the offset field of the ATTR_VALUE to 68.



A Tables are listed in the Database Logger.
B The same list displays in the datalog.idt.


Fields listed for the ALARM_LOG in the data_field.idt are the columns in the CIMPLICITY alarm logging file, ALARM_LOG.

Common Tracker data logging tables

Tables that will almost always be listed and defined include:

Table Name Logs:
EVENT_LOG Alarms for events
PRT_GRP PRT groups
PRT_REG PRT regions
SPLIT RCO information
$DEFAULT Point data
PRT_ITEM_ATTR Extended attributes
RCO_SITE1 An RCO site. Note: The RCO site name is used instead of RCO SITE1.

Important PRT logging tables naming requirement

  • Three tables that are automatically included in the datalog.idt and data_field.idt are:




The PRT in these file names refers to the PRT service ID .

If your project uses a different service ID, replace the PRT with your service ID.


  1. You used the POMS Wizard to create a POMS project.
  2. The service ID that POMS uses is OMPRT_DC.
  3. The three PRT log table names need to be changed to:




  • Each RCO site that should be logged must be added to both the datalog.idt and data_field.idt files.

Steps to edit Tracker data logging files

Step 1 Edit the datalog.idt.
Step 2 Edit the data_field.idt.