Extended Markup Language (XML) Protocol Driver for OASyS

The Extended Markup Language (XML) Protocol Driver for OASyS (hereafter referred to as "the driver") receives RealTime data external to the AVEVA Enterprise SCADA system via input files and inserts it into the analog, status, rate, multistate, and gascontract tables.

The driver collects data from a file imported through one of the following three applications:

• Gas Contract Nominations - Imports Gas Contract Nomination data by importing the contents of a text or XML file.

• Point Import - Updates RealTime point data by importing the contents of a .CSV file.

• XML Point Import - Updates RealTime point data by importing the contents of an XML file.

Gas Contract Nominations, Point Import, and XML Point Import pass imported data into the first ports of three port pairs used by the OASyS DNA Socket Server Relay Service. Each port pair is dedicated to one of the three import applications. Omnicomm then retrieves data through the second ports of the three dedicated port pairs. As its name suggests, the OASyS DNA Socket Server Relay Service acts as a relay system to pass data between these three import applications and Omnicomm. The service must be running for data import to work successfully. For further information on this service, refer to OASyS DNA Socket Server Relay Service.

The driver supports the following AVEVA Enterprise SCADA RealTime features:

• Polling for RealTime variables (read current analog, status, rate, and multistate points)

• Report by Exception – secure processing of reports by exception of RealTime data from remote devices

  Note: While the Advanced Database Editor (ADE) exposes all of the above features, each feature must be separately licensed to work.

Configuration steps to use the driver with the import application:

1. Create a connection record to communicate with the import application.

2. Create a remote record to represent the import application.

3. Configure the xmlproto record automatically created for the new remote record.

4. Connect the remote record to the relevant connection so the system knows how to communicate with the import application.

5. Start the OASyS DNA Socket Server Relay Service, if not already running.

   Note: Each of the applications requires its own unique connection record and remote record.