SCHNEIDR

ClearSCADA - WITS Device Profile

Based on WITS XML suite version 1.4

1.1    DEVICE IDENTIFICATION Capabilities
1.1.1    Device Function:

Master Stations send DNP requests, while Field Devices send DNP responses. If a single physical device can perform both functions, a separate Device Profile Document must be provided for each function.
Master Station
Field Device
1.1.2    Vendor Name:

The name of the organisation producing the device.
SCHNEIDR
1.1.3    Device Name:

The model and name of the device, sufficient to distinguish it from any other device from the same organisation.
ClearSCADA
1.1.4    Device manufacturer's hardware version string: ----
1.1.5    Device manufacturer's software version string: 2017 (6.78)
1.1.6    Device Profile Document Version Number:

Version of the Device Profile Document is indicated by a whole number incremented with each new release.
3
1.1.7    Supported version of WITS: 1.2


1.2    COMMUNICATIONS Capabilities
1.2.1    Supports outgoing connections:

For Field Devices an outgoing connection is from the Field Device to the Master Station.

For Master Stations an outgoing connection is from the Master Station to a Field Device.
Yes
No
1.2.2    Maximum number of outgoing connections:

Devices can have up to ten connections. Enter zero if outgoing connections are not supported.
10
1.2.3    Supports incoming connections:

For Field Devices an incoming connection is from the Master Station to the Field Device.

For Master Stations an incoming connection is from a Field Device to the Master Station.
Yes
No
1.2.4    Incoming connection availability:

Incoming connections may not always be available, for example with a battery powered device.
Always
Never (outgoing connections only)
Periodic
1.2.5    Periodic availability start date/time:
1.2.6    Periodic availability end date/time:
1.2.7    Periodic availability repeat interval (minutes):
1.2.8    Supported connection types and modes:

Connection modes may apply to any connection type.

Network protocols may be supported over dial-up connections using PPP/IP.

NB. GPRS isn't classified as a dial-up connection type.

Network connections must support a minimum of 1 protocol and 1 end point type.

Modes of connection supported:
Permanent
On Demand

Types of connection supported:
Direct (e.g. radio or private wire)
Dial-up (e.g. PSTN or GSM)
Dial-up Network (e.g. PPP/IP)
Network (e.g. Ethernet or GPRS)

Network protocols supported:
IPv4 (TCP)
IPv4 (UDP)
IPv6 (TCP)
IPv6 (UDP)

Network end point types supported:
Listening end point
Initiating end point
Dual end point

1.2.9    Supports DNS:

Network information for an IP connection may be an IP address or a domain name.
Not applicable - no network connections
Yes
No
1.2.10    Supports scheduled connections: Not applicable - no outgoing connections
Yes
No
1.2.11    Scheduled connection repeat interval (minutes):

The Field Device may impose restrictions on the available repeat intervals.
None
Fixed at ___
Configurable, range ___ to ___
Configurable, selectable from ___, ___, ___
Configurable, other, describe __________
1.2.12    Supports callback:

Only 'On demand' connection can be used for callback.

Network connection must support the Field Device as the initiating end point (Field Device is either initiating end point or dual end point).

Network protocols may be supported over dial-up connections using PPP/IP.
Not applicable - no outgoing connections
Yes
No

Types of connection supported for callback:
Dial-up (e.g. PSTN or GSM)
Dial-up Network (e.g. PPP/IP)
Network (e.g. Ethernet or GPRS)

Network protocols supported for callback:
IPv4 (TCP)
IPv4 (UDP)
IPv6 (TCP)
IPv6 (UDP)

1.2.13    Connection timeout (seconds):

If this period passes whilst the device is connected without any requests being received, then the device may terminate the connection.
None
Fixed at ___
Configurable, range ___ to ___
Configurable, selectable from ___, ___, ___
Configurable, other, describe __________
1.2.14    Definition of communication port list:

List of all communication ports in the device.
None


1.3    HEALTH-CHECK Capabilities
1.3.1    Detects supply failure:

A device may be able to detect when its supply has failed, for example a mains failure.
Yes
No
1.3.2    Detects battery voltage low:

A battery powered device may report that the battery voltage is below a particular threshold.
Not applicable - not battery powered
Yes
No

Low voltage threshold:
Fixed at ___
Configurable, range ___ to ___
Configurable, selectable from ___, ___, ___
Configurable, other, describe __________

Hysteresis for low voltage threshold:
Fixed at ___ (enter 0 if no hysteresis)
Configurable, range ___ to ___
Configurable, selectable from ___, ___, ___
Configurable, other, describe __________

1.3.3    Detects I/O failure:

For example an Analogue to Digital Converter (ADC) failure.
Yes
No
1.3.4    Detects when local user device is attached: Yes
No
1.3.5    Definition of Health-Check bits:

List of all vendor specific health-check bits. Actions may be static, Data set event with connection request or Data set event without connection request. Currently, each bit is always asserted and cleared by the Field Device (FD).
None


1.4    ANALOGUE POINTS Capabilities
1.4.1    Number of limits:

Analogue input/output points can have up to ten limits. Enter zero if analogue points are not supported.
10
1.4.2    Limit types:

Each limit may be a high (positive) limit or a low (negative) limit. The type of each limit may be fixed or configurable.
Limit 1:
Not Supported Low High Configurable
Limit 2:
Not Supported Low High Configurable
Limit 3:
Not Supported Low High Configurable
Limit 4:
Not Supported Low High Configurable
Limit 5:
Not Supported Low High Configurable
Limit 6:
Not Supported Low High Configurable
Limit 7:
Not Supported Low High Configurable
Limit 8:
Not Supported Low High Configurable
Limit 9:
Not Supported Low High Configurable
Limit 10:
Not Supported Low High Configurable
1.4.3    Hysteresis: Not Supported
Single hysteresis per point (all limits are the same)
Separate hysteresis per limit
1.4.4    Persistence Not Supported
Single persistence for entering and leaving state
Separate persistence for entering and leaving state
1.4.5    Enter state persistence: Not Supported
Single enter state persistence per point (all limits are the same)
Separate enter state persistence per limit
1.4.6    Leave state persistence: Not Supported
Single leave state persistence per point (all limits are the same)
Separate leave state persistence per limit
1.4.7    Persistence resolution: 1 ms
1.4.8    Supports overriding analogue input points: Yes
No
1.4.9    Supports overriding analogue output points: Yes
No
1.4.10    Raw value types:

Types of raw value supported by the device.
Integer
Unsigned integer
Single precision floating point
1.4.11    Supports scaling of analogue output points: Yes
No


1.5    COUNTER POINTS Capabilities
1.5.1    Number of limits:

Counter input points can have up to five limits. Enter zero if counter points are not supported.
5
1.5.2    Supports overriding counter points: Yes
No


1.6    BINARY POINTS Capabilities
1.6.1    Supports overriding binary input points: Yes
No
1.6.2    Supports overriding double-bit binary input points: Yes
No
1.6.3    Supports overriding binary output points: Yes
No
1.6.4    Persistence: Not Supported
Single persistence per point (all states are the same)
Separate persistence per state
1.6.5    Persistence resolution: 1 ms


1.7    PROFILES Capabilities
1.7.1    Supports profiles used with limits: Yes
No
1.7.2    Supports profiles used with control values: Yes
No
1.7.3    Maximum number of profiles:

Enter zero if profiles are not supported.
255
1.7.4    Maximum number of vectors per profile:

Range 0 to 1440 (one per minute). Enter zero if profiles are not supported.
1440
1.7.5    Interpolation time (minutes):

The valid Interpolation Times that can be used when calculating a Profile Control Value. Enter zero if profile control values or interpolation is not supported.
Fixed at ___
Configurable, range 0 to 240
Configurable, selectable from ___, ___, ___
Configurable, other, describe __________


1.8    RATE OF CHANGE Capabilities
1.8.1    Supports rate of change on analogue points: Yes
No
1.8.2    Supports rate of change on counter points: Yes
No
1.8.3    Supports no change detection on analogue points: Yes
No
1.8.4    Supports no change detection on counter points: Yes
No


1.9    EXTENDED DATA POINTS Capabilities
1.9.1    Supports minimums on analogue points: Yes
No
1.9.2    Supports maximums on analogue points: Yes
No
1.9.3    Supports means on analogue points: Yes
No
1.9.4    Supports integrals on analogue points: Yes
No
1.9.5    Supports state counters: Yes
No
1.9.6    Supports state runtimes:

Field Devices may compute state runtimes only on a periodic basis, thus affecting further processing such as the application of limits.
Yes
No

If Yes, provide details of how frequently the point is calculated:
Fixed at 1 second (i.e. Continuously)
Fixed at some other period ___ (secs)
Configurable, range 1 to 4294967295 (secs)
Configurable, selectable from ___, ___, ___
Defined by I/O scan rate of source point
Defined by Field Device wake-up period
Other, describe __________


1.10    ACTION INHIBIT DATA SET Capabilities
1.10.1    Supports the data set using a request selecting individual points: Yes
No
1.10.2    Supports the data set using a request selecting ALL points:
Yes
No
1.10.3    Supports the data set using a request that specifies a timeout on inhibits:

When timeout is not supported the request must always contain timeout of zero.
Yes
No


1.11    DATA LOGGING Capabilities
1.11.1    Supports data logging: Yes
No
1.11.2    Supported log types: Time Logs
Event Logs
1.11.3    Supports associated values:

A device may support storing associated minimum, maximum and/or mean values in its log files.
Yes
No
1.11.4    Log file overflow behaviour: Discard the oldest data
Discard the newest data
Other, explain __________
1.11.5    Detects log file filling:

A device may report that one of its log files is filling when its size exceeds a percentage of the maximum size. It will continue to report that the log files are filling until its size is below a percentage of the maximum size.
Yes
No

Filling threshold:
Fixed at ___ %
Configurable, range ___ % to ___ %
Configurable, selectable from ___ %, ___ %, ___ %
Configurable, other, describe __________

No longer filling threshold:
Fixed at ___ %
Configurable, range ___ % to ___ %
Configurable, selectable from ___ %, ___ %, ___ %
Configurable, other, describe __________

1.11.6    Supported periodic logging rates (minutes):
Fixed at ___
Configurable, range 1 to 65535
Configurable, selectable from ___ , ___ , ___
Configurable, other, describe __________
1.11.7    Supported periodic logging offsets (seconds):
Fixed at ___
Configurable, range 0 to 4294967295
Configurable, selectable from ___ , ___ , ___
Configurable, other, describe __________


1.12    APPLICATION PROGRAMS Capabilities
1.12.1    Supports application programs: Yes
No
1.12.2    Maximum number of applications:

Enter zero if applications are not supported.
255
1.12.3    Supports initialising applications: Yes
No
1.12.4    Supports stopping/starting applications: Yes
No
1.12.5    Supports pausing/resuming applications: Yes
No


1.13    CONFIGURATION Capabilities
1.13.1    Supports configuration download: Yes
No
1.13.2    Supports configuration upload: Yes
No
1.13.3    Supports firmware download:

A device that supports downloading firmware updates will recognise a file as being a firmware update based on the name of the file. The filename should include a path (if required).
Yes
Filename *.*

No
1.13.4    Maximum size of incremental configuration file (bytes): 104857600
1.13.5    Supports template bulk configuration: Yes
No
1.13.6    Activate bulk configuration:

A device may either cold restart or warm restart when a new bulk configuration file is activated.
Cold Restart
Warm Restart


1.14    POINT EVENT DATA SETS Capabilities
1.14.1    Supports generating point data set events (action 2): Yes
No
1.14.2    Supports generating point data set events and triggering connection request (action 3):
Yes
No