acarlini548b

My feedback

  1. 15 votes
    Sign in Sign in with OSIsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  PI Connectors » UFL  ·  Flag idea as inappropriate…  ·  Admin →
    acarlini548b supported this idea  · 
  2. 10 votes
    Sign in Sign in with OSIsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  PI Developer Technologies » General  ·  Flag idea as inappropriate…  ·  Admin →
    acarlini548b supported this idea  · 
  3. 3 votes
    Sign in Sign in with OSIsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    2 comments  ·  PI Developer Technologies » PI Web API  ·  Flag idea as inappropriate…  ·  Admin →
    acarlini548b commented  · 

    I'm working in a business where asset changes are performed in a daily basis , and versioning is the only way to keep track and quickly compare the changes with real time process data. Versioning is a must in a controlled environment.

    After several tests on working with Element Versions I went out with the following statements, please feel free to comment on that :

    In order to keep track of relationship between real time data and their correspondent metadata stored in AF Element Attributes at a certain point in time the only simple solution is to create a new Element Version when this metadata changes. Another solution is to create a PI Point for every attribute that can be potentially altered during the asset change ( extremely expensive ).
    Element Versioning impact heavily in the database size as every new version is a new element ( new id ), but this depends on the size of the elements and the kind of data recorded on it
    Only PIAF SDK has methods to works with element versions, PI WEB API doesn't actually expose versioned elements but only the ones responding to default behaviour ( there is a bug in 2016R2 where PI Web API and PIAF SDK searches retrieves different element versions from the same query : PI Web API always show the latest one , or none )
    Enabling Audit Trail ( supported only by the Enterprise versions of MS SQL Server ) give you the ability to record all the changes in the elements and attributes, it will also heavily impact the database size and performance, but doesn't satisfy requirements in statement 1 until you use versioning too.

    Our current idea is to keep one AF database as element historian, and one AF database for realtime where only "active" element versions are kept.

    When we activate ( we have a configuration attribute "Status" for that ) one Element Version in the AF Historian it will be transferred to the AF Realtime database overriding the existing one.

    In this way if we want to make historical comparision between realtime data and metadata we will use the AF Historian Database, otherwise we will point to the AF Realtime database with the Active data.

    One of the pending issues is still the simplicity of getting and writing AF Element Versions with the web interfaces, PI Web API are not yet supporting element versions and we are looking forward to have that functionality

    acarlini548b supported this idea  · 
  4. 10 votes
    Sign in Sign in with OSIsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  PI Connectors » UFL  ·  Flag idea as inappropriate…  ·  Admin →
    acarlini548b shared this idea  · 
  5. 15 votes
    Sign in Sign in with OSIsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  PI Connectors » OPC UA  ·  Flag idea as inappropriate…  ·  Admin →
    acarlini548b supported this idea  · 
  6. 4 votes
    Sign in Sign in with OSIsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  PI Connectors » General  ·  Flag idea as inappropriate…  ·  Admin →
    acarlini548b supported this idea  · 
  7. 19 votes
    Sign in Sign in with OSIsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  PI Connectors » General  ·  Flag idea as inappropriate…  ·  Admin →
    acarlini548b supported this idea  · 
  8. 21 votes
    Sign in Sign in with OSIsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    2 comments  ·  PI Connectors » UFL  ·  Flag idea as inappropriate…  ·  Admin →

    I’m not sure why this would be needed. In the UFL connector you need to specify the name of the tag that you write to. And if that tag already exists, it will write to it. If that tag does not exist, then the connector would create that tag with your desired tag name. Why would you want the connector not to create that tag?

    acarlini548b supported this idea  · 
  9. 13 votes
    Sign in Sign in with OSIsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  PI Connectors » UFL  ·  Flag idea as inappropriate…  ·  Admin →
    acarlini548b supported this idea  · 
  10. 3 votes
    Sign in Sign in with OSIsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  PI Connectors » UFL  ·  Flag idea as inappropriate…  ·  Admin →
    acarlini548b shared this idea  · 
  11. 4 votes
    Sign in Sign in with OSIsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  PI Connectors » UFL  ·  Flag idea as inappropriate…  ·  Admin →
    acarlini548b supported this idea  · 
  12. 17 votes
    Sign in Sign in with OSIsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    2 comments  ·  PI Vision » AF Integration  ·  Flag idea as inappropriate…  ·  Admin →
    acarlini548b supported this idea  · 
    acarlini548b commented  · 

    I think most of the PI WebAPI examples available in PI Square already show how to build a light-weight Coresight, that means exactly an asset element & attribute browser and query editor.

    I would be more interested in adding light-weight editing functionalities in CoreSight , i.e. giving the ability to edit certain Elements and Attributes, that's currently possible only customizing it.

  13. 183 votes
    Sign in Sign in with OSIsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    19 comments  ·  PI Vision » Manual Data Entry  ·  Flag idea as inappropriate…  ·  Admin →
    acarlini548b supported this idea  · 

Feedback and Knowledge Base

Posted ideas will have one of the following statuses.
Full definition of these statuses can be found on the Home Page.
No status
NEEDS MORE DISCUSSION
RESEARCHING/EVALUATING
DECLINED
PLANNED
STARTED/IN DEVELOPMENT
IN BETA
COMPLETED