Is their any example for understanding?
This question is tough to answer because of so many unknowns and possibilities. RPA is not a term well known to most of the PI Community, and I had to go look it up. I assume RPA mean Robotic Process Automation.
I am quite experienced with many things PI but even the phrase "OSI PI tools" needs better definition in order to address the question. To some people, something like PI SMT, PI Builder, or PI System Explorer are considered to be tools that OSIsoft has created. But those things are really Windows applications.
Since you posted this in the PI Developers Club, and specifically the AF SDF .NET subspace, I assume that you are a developer. Perhaps by tools what you are really asking is what PI Developer Technologies can be used with RPA. If that's the case, the question now is better defined and has a fairly standard answer.
Here are the most popular PI Developer Technologies:
AF SDK - It is the fastest performing of the technologies but is limited to Windows .NET Framework.
PI Web API - a RESTful service that is cross-platform. It is roughly 50% performance speed of AF SDK, but works on any platform that supports a modern web browser.
SQL Family - there are several OSIsoft offerings for SQL with PI SQL Client being the latest and most flexible. There are older ODBC and OleDB offerings. Some only support the PI Data Archive, whereas others support AF.
Which leads to the final answer to you, which is "It depends on your environment." That answer is not very satisfying but it is the same answer almost everyone gets when they say "I want to write a PI application for XXX" where XXX might be "my Java users" or "iPhones" or other.
If your RPA development also is a .NET, that is your are maybe using C# or VB.NET on a Windows desktop, then you can integrate your .NET RPA calls into AF SDK code. But if your RPA toolset is not .NET compliant, or if your environment is not Windows .NET, but it does support RESTful calls, then PI Web API is recommended.
I have found that if you always use TLA's without any further explanations, you instantly exclude a large portion of your audience, maybe even as much as 50%.
Next, you probably deny yourself feedback from a portion of the audience who actually have an idea of what you're talking about, because they are annoyed about the fact that you keep using this term without any further explanation
So a general tip to anyone presenting something, whether it's in public at a conference or just in an internet forum - do yourself a favor and just explain your TLA's the first time you bring them up, and you'll include everyone and possibly get better feedback on the subject.
If not, expect people to pick randomly from the list of 147 acronym definitions for RPA
Asle, my friend, allow me to point out the irony of your well written reply: you use TLA without defining TLA! Yikes.
Sneha: More importantly, can you describe what you are trying to do via RPA - what is the use case, and what needs to be integrated with PI?
Retrieving data ...