Anyone can point me to any white papers on recommendations on build a new AF databases? What are the areas I need to focus and what should be the strategy?
As Robert Schmitz suggests, a solid best practice for actual development is to use templates throughout the hierarchy. The white paper offers a lot of hints on what makes a good AF Element and what to consider.
In terms of strategy and approaching the problem, I would review this post: https://pisquare.osisoft.com/message/104096-re-what-would-be-the-best-strategy-to-start-a-pi-af-implementation#comment-1…
I see both Roger Palmen and Jim Gavigan also posted in the linked topic, which is solid validation since they are very experienced with AF.
Thanks for reaching out to us on PI Square.
Here is the link to our white paper on building PI AF Templates.
Thank you Rob, this is a good paper on building part of it.
Thanks Dan, for sharing good discussion.
Step 1) know your purpose!
There is no one good way to build an AF database, it all depends...
Understand what you try to achieve in the long run, and what your first deliverable should be. Great plans don't return revenue, working implementations do.
Roger, I definitely know my purpose and I also understand it depends on the size, types etc. etc. It is always best to look for best practices, lessons learned and strategy that others have done. So that you don't reinvent the parts have already been done, you build on top of that.
Retrieving data ...