Standard Interfaces usually come with a sample .Bat file. So, when you start configuring your first instance of e.g. PI Interface for OPC DA, the .Bat file will have some defaults as we suggest those. When you chose to create a new Instance from the executable, there will also be some defaults, if I recall this correctly. In the beginning, there is really no big difference between creating a new instance based on a .Bat file or based on the .exe file and for sure both options are reliable.
If you already have one or more instances of a PI Interface created, it is usually easier to copy the .Bat file, edit it and make the required modifications, save and load it into PI-ICU.
When you are configuring a PI Interface for the first time, please follow the instructions provided in the documentation e.g. PI Interface for OPC DA 2.7.2
No matter if you prefer the online version or the documentation file installed with the Interface, the instructions are pretty straight and easy to follow.
Purpose: Typically used for creating a fresh, new instance.
Process: When you create an instance from an EXE file, it sets up the interface with default settings provided by the executable.
Use Case: Ideal for setting up a new interface from scratch, especially if you are not modifying an existing configuration.
BAT File:
Purpose: Often used for creating instances based on existing configurations.
Process: A BAT file contains specific commands and parameters that can be edited to customize the interface instance. You can copy an existing BAT file, modify it as needed, and then load it into PI ICU.
Use Case: Useful when you want to replicate or slightly modify an existing interface instance. This method allows for more flexibility and customization based on pre-defined templates.
I am making an UFL instance for the first time. And there is like 2 instances already installed in PI ICU. 
