Hi Unmesh, welcome to the forum. It seems that you have a few misconceptions on how an ICS/SCADA system actually works, and more importantly, how OpenPLC works. So here are a few observations to help you out:
1) OpenPLC is installed as a service, which means that once it is installed, the Linux operating system does its best to keep it running all the time. That's why when you kill the process, another comes right up. You can control the OpenPLC service behavior (and any other service process on Linux actually) using the command
So for example, if you need to check if OpenPLC Runtime is running you type:
sudo systemctl status openplc
If you want to stop OpenPLC Runtime from running temporarily you type:
sudo systemctl stop openplc
And finally if you want to disable (remove service forever... i.e. it will never run again until you enable it back) OpenPLC Runtime service you type:
sudo systemctl disable openplc
You were never supposed to launch the ./ start_openplc.sh command. In fact, there isn't a place in the instructions that tells you to do that. This script is to be used only by the service daemon.
2) Your ScadaBR setup is messed up. Using 0.0.0.0 as IP address is never going to work. 0.0.0.0 is a non-routable meta-address used to designate an invalid, unknown, or non-applicable target. It doesn't make sense to use this address if you want ScadaBR to reach OpenPLC. What you need to use instead, is the IP address of the machine running OpenPLC. If OpenPLC and ScadaBR are running on the same machine, then you can use 127.0.0.1 which is the localhost address. Additionally, drop the extra :8000 port number parameter (I don't know where you got this). There is a specific field for you to insert the port number which is right below the "Host" field. The right value to put in there is 502 (which is already there). That's the default port used by Modbus, and that's how ScadaBR is going to reach OpenPLC. Finally, your update period is set to 5 minutes, which means you will have to wait a whole 5 minutes period to see something changing. If you want quicker updates, I recommend you changing that to something like 500 milliseconds or maybe 1 second.
3) The Monitoring section has nothing to do with ScadaBR. That page is used for you to monitor your program. It will display all your located variables (%QX0.0, %IX0.0, etc) and will change according to the program you have uploaded.
4) Why are you adding a slave device? From the 0.0.0.0:9090 IP address (which is also incorrect by the way) I imagine you're trying to add ScadaBR as a slave device of the OpenPLC. If that's the case, this is completely wrong. You don't add the Scada software as a slave of the PLC, it is the other way around. The Scada software is the master that pulls data from all slave PLCs. The configuration you are doing on ScadaBR to add a new data source is exactly to setup a slave PLC where to pull data from. You should use the "Slave Devices" functionality on OpenPLC only if you want to expand your I/O ports, adding for example, an Arduino board or another type of Modbus slave device.
In summary, don't worry about starting OpenPLC, it will start itself automatically. Fix the IP address on the ScadaBR configuration, remove all slave devices from the OpenPLC runtime, and you should be good.