SCADA Monitoring Requirements
Posted: Thu Nov 03, 2011 6:22 pm
Hi,
We would like to monitor the following attributes of SCADA Infrastructure.
Could you please let us know, whether your tool supports our below requirements ?
Applications
• Wonderware - ArchestrA (Engines, IOS/AOS/GR status), Intouch error log files
• I/O Server connectivity status (DAS, OPC) – These are the I/O Servers used for the historians and HMI’s to access data from the PLC’s (protocol conversion)
• Application and System event and error Logs
Instrumentation & I/O
• Hart Diagnostics – Information that comes directly from the instrument, via the HART protocol. Typically would use instrumentation asset management software, but the information could be programmed to be stored in the PLC.
• Instrument Trending (drift) – Meaning that the process has not changed, but the transmitter value indication is drifting. Preferably, this would be a function of the instrumentation asset management software, but could be inferred to a lesser extent based on historian data.
PLC’s
• Analog limit range deviations – Analog values are outside the programmed limits, indicating an instrument failure or data error.
• PLC Battery status – a bit from the PLC a good or bad battery status
• Channel loading – Refers to a Proprietary network channel that is reaching capacity. Could be Modbus, ControlNet, DeviceNet, etc.
• CPU faulting – PLC CPU faulted.
• CPU Loading – PLC CPU reaching capacity
• Heartbeat monitoring – This is a continuous signal from the PLC indicating the presence of the hardware and valid network connection. This could be a communication good/bad value, or an analog that is expected to change value within a given period of time.
• PLC key switch position – The Allen-Bradley PLC’s have a key switch that indicates if the PLC program is locked or not, to modifications of the logic and can be monitored externally. Modicons have a two position switch which can be monitored as will.
• Module failures – monitor logic or system tags for module errors and failures
• Temperature in PLC enclosure, server room – This is typically a transmitter installed within an enclosure or server room, and connected to a PLC, to be monitored as an analog value.
Network and interface adapters (proprietary) – refers to Modbus, ControlNet, DeviceNet, etc.
• Comm Bridges/repeaters status – Intend is to monitor network hardware for failures. May need to use PLC vendor software, or infer this from other data.
• ControlNet Status / errors – monitor network for errors
• DeviceNet Status / errors – monitor network for errors
• Modbus Network Monitoring – monitor network for errors
• Latency – Determine if network is having problems resulting in slow response time.
• Network Loading – Is the network reaching capacity?
• Network Availability - Up or down
HMI’s / OIT’s
• AutoLogon information – Is the AutoLogon functionality working? Is the registry still setup correctly? Need to identify failure of Autologon.
• CPU faulting
• CPU Loading
• Disk Usage %
• Intouch status – utilize Wonderware log files or other methods to determine errors.
• Memory Usage – Reaching capacity?
• Page Faults
• Scan overruns
• System Logs – event viewer, application logs, etc.
Process Control Network – refers to the Process Control LAN/WAN
• Comm Bridges/repeaters status
• Ethernet IP Status
• Latency
• Network Loading
• Network Availability - Up or down
• Ping status
• Radio comm status – up or down
• Radio diagnostics
• Radio efficiency (total good)
• Router metrics
Historians and other servers
• backup and archive successful status for each server
• Analog limit range deviations – Are values outside of tag configured range?
• CPU faulting
• CPU Loading
• Disk Usage %
• IDAS/MDAS state faults – refers to the data access engines within Wonderware’s historian. Need to monitor health and status. Could use SQL and log files.
• InSQL server status – up / down
• Memory Usage
• Null Count – data integrity. Are tags getting values?
• Page Faults
• Scan overruns
• SQL errors
• SQL Job status
• SQL server status
• System Logs
• Terminal server - App performance monitoring
• Terminal server - Intouch status
• Terminal server - Length of session time
• Terminal server - number of active users
• Terminal server - number of idle sessions
• Terminal server - time stamp logged on
General
• Alarm notifications of system / network / device health
• Antivirus Reports
• Communication failure
• Identify point of network/system failure – allows directing resources to point of failure
• OPC Tool Status – OPC applications such as Kepware, Matrikon, Wonderware DAS – running or not. Applies to other data access I/O Servers as will.
• Power Status (Monitor Primary source as well as backup)
• Security Monitoring - White List Monitoring or equivalent
• System time (PLC, HMI, Server sync) – Determine if system clocks are in sync between PLC, HMI, Servers.
• UPS Status – monitor UPS errors
Regards,
Ramesh
We would like to monitor the following attributes of SCADA Infrastructure.
Could you please let us know, whether your tool supports our below requirements ?
Applications
• Wonderware - ArchestrA (Engines, IOS/AOS/GR status), Intouch error log files
• I/O Server connectivity status (DAS, OPC) – These are the I/O Servers used for the historians and HMI’s to access data from the PLC’s (protocol conversion)
• Application and System event and error Logs
Instrumentation & I/O
• Hart Diagnostics – Information that comes directly from the instrument, via the HART protocol. Typically would use instrumentation asset management software, but the information could be programmed to be stored in the PLC.
• Instrument Trending (drift) – Meaning that the process has not changed, but the transmitter value indication is drifting. Preferably, this would be a function of the instrumentation asset management software, but could be inferred to a lesser extent based on historian data.
PLC’s
• Analog limit range deviations – Analog values are outside the programmed limits, indicating an instrument failure or data error.
• PLC Battery status – a bit from the PLC a good or bad battery status
• Channel loading – Refers to a Proprietary network channel that is reaching capacity. Could be Modbus, ControlNet, DeviceNet, etc.
• CPU faulting – PLC CPU faulted.
• CPU Loading – PLC CPU reaching capacity
• Heartbeat monitoring – This is a continuous signal from the PLC indicating the presence of the hardware and valid network connection. This could be a communication good/bad value, or an analog that is expected to change value within a given period of time.
• PLC key switch position – The Allen-Bradley PLC’s have a key switch that indicates if the PLC program is locked or not, to modifications of the logic and can be monitored externally. Modicons have a two position switch which can be monitored as will.
• Module failures – monitor logic or system tags for module errors and failures
• Temperature in PLC enclosure, server room – This is typically a transmitter installed within an enclosure or server room, and connected to a PLC, to be monitored as an analog value.
Network and interface adapters (proprietary) – refers to Modbus, ControlNet, DeviceNet, etc.
• Comm Bridges/repeaters status – Intend is to monitor network hardware for failures. May need to use PLC vendor software, or infer this from other data.
• ControlNet Status / errors – monitor network for errors
• DeviceNet Status / errors – monitor network for errors
• Modbus Network Monitoring – monitor network for errors
• Latency – Determine if network is having problems resulting in slow response time.
• Network Loading – Is the network reaching capacity?
• Network Availability - Up or down
HMI’s / OIT’s
• AutoLogon information – Is the AutoLogon functionality working? Is the registry still setup correctly? Need to identify failure of Autologon.
• CPU faulting
• CPU Loading
• Disk Usage %
• Intouch status – utilize Wonderware log files or other methods to determine errors.
• Memory Usage – Reaching capacity?
• Page Faults
• Scan overruns
• System Logs – event viewer, application logs, etc.
Process Control Network – refers to the Process Control LAN/WAN
• Comm Bridges/repeaters status
• Ethernet IP Status
• Latency
• Network Loading
• Network Availability - Up or down
• Ping status
• Radio comm status – up or down
• Radio diagnostics
• Radio efficiency (total good)
• Router metrics
Historians and other servers
• backup and archive successful status for each server
• Analog limit range deviations – Are values outside of tag configured range?
• CPU faulting
• CPU Loading
• Disk Usage %
• IDAS/MDAS state faults – refers to the data access engines within Wonderware’s historian. Need to monitor health and status. Could use SQL and log files.
• InSQL server status – up / down
• Memory Usage
• Null Count – data integrity. Are tags getting values?
• Page Faults
• Scan overruns
• SQL errors
• SQL Job status
• SQL server status
• System Logs
• Terminal server - App performance monitoring
• Terminal server - Intouch status
• Terminal server - Length of session time
• Terminal server - number of active users
• Terminal server - number of idle sessions
• Terminal server - time stamp logged on
General
• Alarm notifications of system / network / device health
• Antivirus Reports
• Communication failure
• Identify point of network/system failure – allows directing resources to point of failure
• OPC Tool Status – OPC applications such as Kepware, Matrikon, Wonderware DAS – running or not. Applies to other data access I/O Servers as will.
• Power Status (Monitor Primary source as well as backup)
• Security Monitoring - White List Monitoring or equivalent
• System time (PLC, HMI, Server sync) – Determine if system clocks are in sync between PLC, HMI, Servers.
• UPS Status – monitor UPS errors
Regards,
Ramesh