Create the naming rules plugin

To create a new naming rules plugin

1. Create a RealTime Developer Environment (refer to the AVEVA Enterprise SCADA Shared Components Developer documentation).

2. Open <path to environment>\Tools\source\VirtualRTU.Examples.sln.

3. Rename or copy any projects or solutions as desired.

4. Create classes implementing rules interfaces for analog inputs, setpoints, digital inputs, commands, flow rates and volumes, as required. For each rule, provide implementation of filter (method AppliesTo) and derivation (method DerivesFrom). An example of the analog input rule implementation is shown below.

   using OASySDNA.VirtualRtu.Configuration.NamingContract;

   namespace OASySDNA.VirtualRTU

   {

   public class AnalogInputNamingRule : IAnalogNamingRule

   {

   public bool AppliesTo(IAnalogId analogId)

   {

   return analogId.Name != null && analogId.Name.StartsWith("ANA");

   }

   public string DeriveFrom(IAnalogId analogId)

   {

   return analogId.Name.Substring(3);

   }

   }

   }

   In the above example the derivation rule (trim first three characters) will be applied to an analog input, if its point name starts with "ANA".

You can provide multiple derivation rules for the same telemetry item type (for example, it is common to have different rules for deriving command texts corresponding to digital commands targeting valves and pumps).

Note: The filters implemented through AppliesTo method in rules classes should be mutually exclusive, that is, there should not be a point for which multiple different rules could apply.

The table below details telemetry types on which rules are applied and an explanation of input parameters of the AppliesTo and DeriveFrom methods, as well as derivation results.