Outstation Point Statistics

[Anonymous user]

📖 Home  Back  
The database tables CAdvOutstation and CPointSource each contain five database fields to monitor the processing load caused by each outstation / point source. These statistics are intended to provide an indication of the load on the system from telemetry, and identify which outstations / point sources are creating the greatest load.

The five fields for advanced driver outstations (such as SCADAPack Modbus and DNP3) are as follows:

Table Name	Field Name	Description
CAdvOutstation	PointProcessCount	Number of updates for outstation's points since last reset.
CAdvOutstation	PointHistoricCount	Number of historic updates for outstation's points since last reset.
CAdvOutstation	PointAlarmCount	Number of alarm updates for outstation's points since last reset.
CAdvOutstation	PointEventCount	Number of events for outstation's points since last reset.
CAdvOutstation	PointCountTime	Time from which point statistics are being measured.

The five fields for simple driver point sources (such as Modbus and OPC) are as follows:

Table Name	Field Name	Description
CPointSource	PointProcessCount	Number of updates for point source's points since last reset.
CPointSource	PointHistoricCount	Number of historic updates for point source's points since last reset.
CPointSource	PointAlarmCount	Number of alarms updates for point source's points since last reset.
CPointSource	PointEventCount	Number of events for point source's points since last reset.
CPointSource	PointCountTime	Time from which point statistics are being measured.

All of these fields are updated by the point processor when processing updates for the points on the outstation or point source (i.e. data retrieved from the outstation or point source, along with master station overrides).

• If a point update results in a state change which causes alarm(s) to be raised and/or cleared then the PointAlarmCount is incremented once for each alarm raised or cleared.

• If a point update results in a significant change and/or state change and is configured to log an event then the PointEventCount is incremented for each event logged. It is also incremented for any events logged relating to alarms being raised and/or cleared as a result of a state change.

• If a point update is stored in the historian then the PointHistoricCount is incremented.

• Every point update causes the PointProcessCount to be incremented.

Also, the database table CDBPoint contains two database fields to monitor the processing load caused by each individual point. The two fields are as follows;

Table Name	Field Name	Description
CDBPoint	ProcessCount	Number of times that the point has been updated, since last reset.
CDBPoint	ProcessCountTime	Time from which point statistics are being measured.

Every point update causes the ProcessCount to be incremented, including hand control of internal points.


The method ResetPointStatistics in the CAdvOutstation and CPointSource tables can be used to clear the outstation point statistics and/or all the individial point statistics and initialise the PointCountTime and ProcessCountTime fields to the current time. It is recommended that the statistics are reset periodically, such as once a week.

The method ResetProcessCount in the CDBPoint table can be used to clear the statistics for a single point and initiailise the ProcessCountTime to the current time.


Go: Home Back