Christian Leroux
My feedback
-
14 votesChristian Leroux
supported this idea
·
-
102 votesChristian Leroux
supported this idea
·
-
2 votesChristian Leroux
supported this idea
·
-
19 votes
Global configuration for an append write behavior is underway. I look forward to bringing you additional updates once they are available.
Christian Leroux
supported this idea
·
-
32 votes
Development is underway for enabling deletes with PI System Connector. I look forward to bringing you additional updates when they are available.
Christian Leroux
supported this idea
·
-
63 votesChristian Leroux
supported this idea
·
-
20 votesChristian Leroux
supported this idea
·
-
1 voteChristian Leroux
shared this idea
·
-
23 votesChristian Leroux
supported this idea
·
-
3 votesChristian Leroux
supported this idea
·
-
17 votesChristian Leroux
shared this idea
·
-
46 votes7 comments · PI Integrators » PI Integrator for Business Analytics · Flag idea as inappropriate… · Admin →
For supporters of this idea, what is the downstream client tool that consumes the data prepared by the PI Integrator? Is the concern about disk space or how to only display data for a specified time range?
For the former, this seems to be a different type of “rolling” reporting use case that we do not currently have a solution for. In the mean time, as Rory mentioned below, a stored procedure on SQL would work if this idea is intended for SQL writers.
For the latter, is it possible to create “rolling timespans” for your graphs, reports, tables, etc.? For example, here’s a video on how to create calculated measures for a table based on last day or month of data: youtube.com/watch?v=NevFWL2JoMU
Christian Leroux
supported this idea
·
-
22 votesChristian Leroux
shared this idea
·
An error occurred while saving the comment -
23 votes
An error occurred while saving the comment Christian Leroux
commented
This is important at the time of accessing and controlling/configuring the PI Adapter via its REST endpoint API. We don't want to pass along the user/password if required in clear text in the connection.
Christian Leroux
supported this idea
·
-
22 votesChristian Leroux
shared this idea
·
-
3 votesChristian Leroux
shared this idea
·
-
3 votesChristian Leroux
supported this idea
·
-
20 votesChristian Leroux
supported this idea
·
-
29 votes3 comments · OSIsoft Cloud Services » Community Data Sharing · Flag idea as inappropriate… · Admin →
We have started development on Community Management features and Stream data sharing in OSIsoft Cloud Services (OCS) to enable sharing of operational data across tenants.
As part of the Community creation workflow, we are working on a way that Communities are formed without exposing other customer accounts/tenants in the process.
Additionally, Namespaces can now be used to segregate customer data (if you’re providing a service to those customers), or the data can be stored in their own OCS tenant/account and then shared via Community data sharing functionality (when it becomes available).
Christian Leroux
supported this idea
·
-
54 votesChristian Leroux
supported this idea
·
We make use of strong naming convention for all our tags, using sets of prefixes/sufixes to properly position our PI tags in AF hierarchies.
We are making use of the PI Adapter against the PI WebAPI endpoint. Now with the PI Adapter health & diagnostic PI tags that are auto-created when 'EnableDiagnostics' is set to "True" in the auto-created AF DB for this purpose, the auto-naming of these PI tags does not permit a configuration of the naming using a set of prefixes that would help us locate better in our data landscape the position of the PI Adapter.
What we need is to be able to in further PI System Monitoring AF models to be able to re-use these PI Adapter health & diagnostic tags efficiently using substitution params in order to easily create analytics and visualization against AF Elem templates to monitor the whole PI Adapter fleet (potentially hundreds).
Without this prefix we have to map each PI tags manually to the correct AF attribute for our PSM purposes, which is absolutely against our good PI practice in terms of creation and maintenance.