Adding the Relay and the DCM framework to the "legacy"IEC 104 Connector in order to improve the architecture management and security

PI Connector for PI System Health creates a LOT of different point sources for the Pi points it creates on the Data Archive. Some customer may prefer to not have so many point sources show up for one interface/connector. Adding a method to reduce/condense point sources pre-point creation would eliminate to need to edit the point sources manually afterwards.

Update to the Wonderware and UFL connector to handle illegal char only changes the PI tag. The AF still updated with the original char change. (i.e. \ to %19i). The AF element need to match the PI tag name and need done for all connectors.

Support collecting units and description from the Siemens Simatic PCS 7 system and writing them to the AF attribute and the PI Point attributes.

Add the function to able to act as (“scanner”).
At this moment the connect can only act as an adapter, that means that It can't collect data from other device that also are connector is an adapter.
https://www.odva.org/Technology-Standards/EtherNet-IP/Overview

Certain RTUs limit the number of Boolean/Discrete values they return independently of the number of floats they return. The PI Connector for Modbus has a configuration option for “Maximum Response Data Bytes” but it applies to all register types. Enhance the maximum response data byte size configuration to provide an option to configure the max byte size by register type.

As an advanced user, I would like to be able to specify a user-defined data type for the array sent to the PI Connector for EtherNet/IP.  For example, if I have a 32-bit array composed of one INT and two SINTs, I would like to be able to configure the connector to parse this array correctly. Currently the data type specification of the array is limited to one data type (DINT, INT, FLOAT, or SINT).

Parameters k (Maximum number of outstanding I format APDUs) and w, cannot be adjusted, while vendors recommend customers to set it to k=12 and w=8

We would like to discrimnate when the meta data around the data item changes on the source. The digital states related to it, the description, etc. If these change, the connector will change them on our PI server.

Currently PI Data Archive.does not discriminate it just blows away the current configuration and reloads everything from the source overwritting our custom changes.

Would like to see states of alarms captured as child Event Frames of the parent alarm Event Frame that is currently created. Today this data is only captured in tags.

String data, such as serial numbers, are supported by the EtherNet/IP protocol and are often collected to help understand what was being made by a piece of equipment at any given time.

Need EtherNet/IP connector to be able to read and write.
Currently EtherNet/IP connector is read only.

When configuring the PI Connector for Redfish, it will default to port 443 for the target Redfish Server. Servers are commonly installed on custom ports. Currently, the port needs to be manually edited in in DataSource.config.json.

In case of an interruption, the PI Connector has the current capability of backfilling any tag data from the source OpenPCS 7 system.

Condition data leading to PI Event Frame creation from the connector should also support similar backfilling capability to avoid data loss.

Allows customers to leverage the PI Connector relay for improved security, ease of deployment and maintenance when PI Connector for Siemens SIMATIC PCS7 is implemented in a process network with DMZ communication to the corporate network.

Implement TLS encryption between the IEC61850 Connector and the target IED(s) as per TS 62351.

Some organisations enforce connection to the external network to be made through a proxy server.