PI Cloud Connect
Welcome to the
PI
Cloud Connect
feedback page!
We created this forum to hear your ideas, feature suggestions and feedback on PI Cloud Connect. Please suggest your most important features and design change ideas on this site, and vote for your favorite ideas.
Please note that your ideas and comments posted here are visible to all other users.
- For bugs, please open a case with OSIsoft Tech Support through myOSIsoft Customer Portal (https://my.osisoft.com) instead of sharing them on this site.
- For documentation feedback and bugs, please report to documentation@osisoft.com instead of sharing them on this site.
-
Identify a subscription's name from its GUID
- When PI Cloud Connect (from subscriber end) create PI tags on a destination PI server, the exDesc of those tags show the GUID of the subscription that owns it. But there's no built-in way to identity the subscription's name based on the GUID.
It seems reasonable to expect to find a subscription and their GUID in the PI Cloud Connect admin website ➔ Subscriptions ➔ details.
– But it's not there, or anywhere else.In the event that one needs to fix an issue that involves a subscription's GUID, it is important to be able to easily identity the subscription…
2 votes -
PICC Admin Portal Log Availability
It would be useful for the PI Cloud Connect (PICC) portal to include logs related to user activity on the portal such as subscriptions, users, or publications added or removed. The current logs are local and service specific. An enhancement of PICC logging on the portal would be very helpful.
2 votes -
Send email to customers before an upgrade is started
Currently, the customers are expected to monitor the PI Square post here for see updates about a release : https://pisquare.osisoft.com/community/all-things-pi/pi-cloud-connect/release-notes.
The problem with this is that:
1) Not all customers are aware of this expectation
2) Customer will have to login to see the releases which is not very user friendlyIt might be better to send the information via email.
6 votes -
Options for Detail Error logging
I would like to see increased level of logging to identify potential issues with the operation of PICC especially since the alarms page is deprecated.
1 vote -
Health Monitoring options in PICC
As a customer I want to be notified when there are issues with PICC instead of having to actively query the health of PICC, so that I can be aware of issues immediately.
3 votes -
Data Transfer status & validation option
As a customer I want an easy way to validate that all the data from publisher side went to the subscriber side, so I know if there are any issues.
1 vote -
Add support for TLS 1.3 on picloudservices.com
This will make the website faster and more secure.
2 votes -
Add support for HTTP/2 on picloudservices.com
HTTP/2 will make the website load faster. OSIsoft's other websites use it.
HTTP/2 check:
https://http2.pro/check?url=https%3A//www.picloudservices.com/2 votes -
Don't generate audit records for every event on initial subscriber backfilling.
On initial PICC subscription setup, when the subscriber is backfilled with historical data, audit records are created for each event.
It seems be expected due to the nature of the initial setup of the subscription. Points are first created, with a "Pt Created" system digital state and a current timestamp. Data is then backfilled with older timestamps, out-of-order, and generates audit records. Afterwards, real time data collection occurs with current timestamps, in-order, and doesn't generate audit records.
The audit record generating for out-of-order data on the initial backfill of a new subscription can be overwhelming and generate too many audit…
2 votes -
PI Cloud Connect support for tag annotations
As a PI Cloud Connect Subscriber, I would like annotations from the Publisher to be replicated so that I can have all of the information associated to the PI Tags
3 votes -
Provide SSAE SOC2 reports for PI Cloud Connect and OSIsoft Cloud Services
Prior to be able to adopt PI Cloud Connect, many of our customer cybersecurity teams request OSIsoft to provide SSAE SOC2 cybersecurity audit reports. Currently OSIsoft does cybersecurity audits, but these are not specifically SOC2 audits. This is a request to provide these audits that better fit into the industry trend seen at our customer base.
4 votes -
PI Cloud Connect should be able to write to more than one Data Archive
I am a subscriber who receives data from multiple organizations in different (>15) subscriptions. Due to needing the data to be located in different Data Archives as each is for a different business area, one instance of PI Cloud Connect should be able to write to multiple Data Archives, instead of just to the default data server on its node.
15 votes -
Improve PI Cloud Connect's Security Headers score
PI Cloud Connect currently scores an A from Security Headers. However, this can be improved to an A+ by addressing the issues in the link below.
https://securityheaders.com/?q=www.picloudservices.com&followRedirects=on2 votes -
Submit picloudservices.com for HSTS preloading
To help ensure that no insecure HTTP requests are attempted against picloudservices.com, please consider submitting it for HSTS preloading.
https://hstspreload.org/?domain=picloudservices.comBefore that can happen, some redirects must be set up. http://picloudservices.com should redirect to https://picloudservices.com, and https://picloudservices.com should redirect to https://www.picloudservices.com.
Since picloudservices.com is used for a much narrower purpose than osisoft.com, the barrier to submission for HSTS preloading should be much lower.
1 vote -
Allow administrators to remove systems from the PI Cloud Connect portal that are no longer in use
As an administrator, if I were to move my PI Cloud Connect nodes to new machines, I would like the ability to clean up my tenant portal by removing old system names that are still present.
12 votes -
Ability to Specify Multiple PI Data Archives for PI Cloud Connect
When setting up PI Cloud Connect subscriptions it would be nice to specify the PI Data Archive tags get created on along with the AF Server and Database to create elements. In our case, we have multiple AF Servers that are linked to different PI Data Archives. Additionally, I don't really like that the default PI Data Archive gets used. What if a user were to accidentally change that?
4 votes -
Send automatic e-mail notification about error status of data transfer
Problems as:
- PI Cloud Connect node cannot connect to PI Data Archive,
- Account/Password has been expired (service not running properly),
- Publications not sending data,
and so on. Would be reported to administrators automaticky.6 votes -
Limit IP ranges on nodes
As a PI Cloud Connect user, I would like to screen receiving Vendors via their account, but by also by limiting connections to a specific IP or IP range for connections.
2 votes -
Extend the history recovery max period for PI Cloud Connect to longer than 30 days
Allow history recovery for PI Cloud Connect to be longer than the current max of 30 days
18 votes -
Support group managed service account with PI Cloud Connect agent
Allow administrators the ability to configure the PI Cloud Connect agent on-prem to configure a group managed service account (gMSA) for the Windows Service account.
Use of a gMSA reduces IT burden since the rotation of credentials with strong credentials is handled automatically. Furthermore, gMSAs generally improve security as they are hardened by default.
4 votes
- Don't see your idea?