mhalhead

AF Development road map

Discussion created by mhalhead Champion on May 14, 2014
Latest reply on Jun 15, 2014 by mhalhead

Hi,

 

Now that Abacus (aka Asset Based Analytics - ABA) is out (very happy) I thought that I would try and bait OSIsoft into giving a bit more info on the AF roadmap (the techsupport roadmap is a bit light). Below is my wish list:

  1. Flexible output times for ABA. The current ABA implementation is limited to outputs at the time of execution. I would like to have more flexibility over the output time:
    1. The ability to specify a relative output time e.g. t+6h
    2. I would like to ability to be able to have multiple outputs. The same value is written to the PI archives at two different times e.g. y+6h+1s and t+6h. This would allow us to mimic the behaviour of a totalizer (we typically use the two point totalizers)
    3. I would like the output to be the result of a logical operation (i.e. an analysis template) or an attribute which could be static or calculated (Custom DR, Formula DR, Analysis, ...)
  2. Custom ABA routines. In other words a replacement for ACE.I do accept that the code will have to be re-written although the hard part being the business logic will remain the same.
  3. Future data - yes this is more an PI Archive feature but AF needs to support it. 
  4. On premise replication of AF template libraries - yes we are trialing PI CC for this already.
  5. Reference elements between different AF servers. Basically the same idea as having a referenced element but the elements are on different servers. E.g. you have an enterprise server with all the sites, then each operations has its own AF server with their detailed model. I would love to be able to reference the site's detailed model into the enterprise server with seamless navigation.
  6. The ability to "hide" attributes from users. We have a fair number of attributes that are infrastructure related and the bulk of the users don't need to see these; all they do is clutter up the interface for the normal users. 
    1. An extension to this would be to have more control over which attributes PI CC sends.
  7. The ability to add a "script" (or custom logic) to the create, update and delete of elements. The easiest use case I have is when I delete an element I would like it to go and clean up after its self; e.g. remove points (or set them to scan off) that it created.
  8. Overhaul of the Formula DR. Even with ABA Formulas in AF are still useful particularly as they are calculated on the fly with the inputs from the client. The UI could definitely do with a bit of a spruce up; I land up writing a number of them in notepad. 
  9. Models and connections. I would really like to see models and connections return to AF as a first class citizen rather than the only for SigmaFine status they currently have. I would also like to be able to reason over the models. A connectivity model gives another layer of context. 
  10. PI Notifications should be integrated into ABA and Event Frames. I know that this is already on the cards but I thought I should mention it anyway.
  11. I should probably mention more on EventFrames but the biggest thing for me on EF at the moment would be back filling events over an extended period; e.g. go and generate an EF for this condition over the past 5 years, 
  12. Last but not least a OLE-DB or ODBC interface into AF that is writable. 
This is just a list of the top of my head; I would say up to item 4 is in order of priority. Steve you shouldn't be out of a job in the near future. 

Outcomes