This shows a centralized Action Log for all SCADA Nodes in the project with Action Log to ODBC enabled. This is very similar to the Action Log in VIEW and ViewDAQ, but applied to all SCADA Nodes and Projects. The Action Log monitors Power User, General User, and Restricted User actions on the SCADA node. Action Log To ODBC must be enabled in the SCADA node properties.
The Action Log shows:
· User changes to Tags (e.g. setpoint changes, auto/manual and equipment changes).
· User Log-ins to SCADA Node using VIEW and ViewDAQ
For more information on the Action Log in VIEW, see the System & Template Displays section. For information on Project User logins and database changes, see System Log.
From the Project Manager, Project Users can see the Action Log from the 'Project Home' page.
Users can also see this Action Log from VIEW using the
Right Click -> Tools -> System Action Log.
All Users can also see this Action Log
from ViewDAQ using the menu bar:
Tools -> System Action Log.
The Action Log can be sorted and filtered by Time, Date, tag, computer, node and IP addresses.
An optional Tag Name Patterns field is to let users search for patterns using wildcard characters when “All Tags” is highlighted. The wildcard characters are database dependent (.e.g Access, SQL Server, Oracle, MySQL) used to store ODBC data. For an Access database, use % (percent symbol) to match any number of characters and _ (underscore) to match any single character.
An HTML report is printed.
The HTML report displayed can be copied and pasted into EXCEL, WORD and other office applications preserving the cell, column and other formatting.
Data can be exported to EXCEL (VIEW and ViewDAQ to EXCEL 2000 or later, the Project Manager requires EXCEL 2002 or later). See 21.3.2 Export to EXCEL from ODBC Log
The default number of records per page for log displays is to 600.
The system display used by VIEW and ViewDAQ is bwActlog.uti.
The data is contained on the Project Node at drive:\WebAccess\Node\bwPDATA.mdb
The database table is BwActionTable: User action log table.
a. ProjNodeId : Unique ID for a SCADA node.
b. LogDate : Date of the record was recorded.
c. LogTime : Time of the record was recorded.
d. Priority : Not Used.
e. TagName : Tag name, if it is tag related record.
f. Description : Tag Description
g. Action : Description of the User Action
h. UserName : The user who made the action
i. NodeName : The node that this action happened.
j. NodeIP : The IP address of the node where the action happened.