NOC Services

Welcome to the Network Operation Center (NOC) Services feedback page!

We created this forum to hear your ideas, feature suggestions and feedback. 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.
  1. Stop monitoring deprecated products and subsystems

    Please stop monitoring deprecated products and subsystems, especially when the successor is also monitored by NOC. This will help steer customers towards using the successor by removing some of their reason to continue using the deprecated products and subsystems.

    1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  General  ·  Flag idea as inappropriate…  ·  Admin →
  2. PI Agent should use TLS 1.2 or TLS 1.3 instead of TLS 1.0

    PI Agent currently uses TLS 1.0 to communicate with other PI Agent services in the crosslink configuration. TLS 1.0 is known to be insecure. Please update PI Agent so that it uses TLS 1.2 or TLS 1.3.

    1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    IN DEVELOPMENT  ·  2 comments  ·  Security  ·  Flag idea as inappropriate…  ·  Admin →
  3. Include PI SDK in the PI Diagnostics install kit

    If you run the PI Diagnostics install kit without PI SDK already installed, the installation will fail with an error message stating that PI SDK is required. Other install kits include a copy of programs that they require. Please include PI SDK in the PI Diagnostics install kit.

    In the longer term, PI Diagnostics should be rewritten to use PI AF SDK or be replaced with a product that does not use PI SDK. A modern PI server may need PI SDK only for PI Diagnostics.

    1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  General  ·  Flag idea as inappropriate…  ·  Admin →
  4. Allow customers to close NOC cases where all alarms are resolved

    Currently, even when all alarms in a NOC case are resolved (as indicated in the description of the case), the status of the case is "Waiting On Customer". When a case is in this state, a customer cannot close it.

    Most of the time, when all alarms are resolved, the case can be safely closed. Please allow customers to close NOC cases where all alarms are resolved.

    2 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  General  ·  Flag idea as inappropriate…  ·  Admin →
  5. Allow Enterprise Agreement customers to download the Managed PI install kit & documentation

    Currently, not even Enterprise Agreement customers have access to the Managed PI install kit & documentation. Customers have no idea if their version of Managed PI is out of date and it is a burden to try to find this out and install the latest version. Specifically, the customer must contact tech support or book a Field Service Engineer visit, and the engineer may give the customer only temporary access to the files for the upgrade. This is a waste of the customers' time and of OSIsoft's time, since the upgrade can be done without OSIsoft's help. Generally, the initial…

    1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  General  ·  Flag idea as inappropriate…  ·  Admin →
  6. For NOC Interface Alerts, it would be beneficial to include the Interface Point Source and Point Location.

    Customer has many sites and PI Mills to monitor. By knowing the point source and point location where the Interface is having an issue, they can quickly see if data is still flowing, then that would give them more time to look into the issue and respond to the alert.

    4 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  Reporting  ·  Flag idea as inappropriate…  ·  Admin →
  7. Improve the security of sis1.osieanoc.com

    sis1.osieanoc.com is what receives customer data from the PI Agent service. The Qualys SSL Server Test shows that this connection suffers from more than a few security blunders. It scores a B out of a maximum of A+.
    https://www.ssllabs.com/ssltest/analyze.html?d=sis1.osieanoc.com

    Please make the necessary security improvements to bring this score up to A+ and ensure that no yellow text appears in the test results.

    2 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Security  ·  Flag idea as inappropriate…  ·  Admin →
  8. NOC Site Contact assignment email

    If multiple recipients get the original NOC email alert, then if a site contact is assigned the other recipients should be emailed as such so that they are aware someone else is handling. Instead I am left with a inbox of NOC alerts that have to click through to determine if they are resolved, closed, or otherwise being dealt with by somebody else

    1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Reporting  ·  Flag idea as inappropriate…  ·  Admin →
  9. Provide RESOLVED status in NOC Email Subject line

    Currently my email subjects from NOC look identical for new and resolved cases. It would be a tremendous time saver to write Closed or Resolved into the Subject of the emails - especially when I have an event that causes several incidents to be created in a small timeframe.

    2 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  General  ·  Flag idea as inappropriate…  ·  Admin →
  10. Allow only HTTPS connections to the PI Diagnostics UI web pages

    Please allow only HTTPS connections to the PI Diagnostics UI web pages, similar to the PI Connector administration pages. Not only is this more secure, but it would also open up the possibility of using the PI Diagnostics UI on a remote computer.

    1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Security  ·  Flag idea as inappropriate…  ·  Admin →
  11. Monitor PI Web API and PI Web API Crawler

    Occasionally, an issue occurs with these programs that prevents tags from being searched in PI Vision. It would be helpful to know about such an issue soon after it occurs and fix it before any user notices rather than learn about the issue from a frustrated user.

    2 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    2 comments  ·  General  ·  Flag idea as inappropriate…  ·  Admin →
  12. Monitor PI SQL Data Access Server (RTQP Engine)

    Unlike its predecessor, PI OLEDB Enterprise, the PI SQL Data Access Server (RTQP Engine) is not monitored by NOC, which may be a deterrent for any customer that is considering an upgrade from the former to the latter. PI SQL Data Access Server (RTQP Engine) is also one of the only PI Server services that is not monitored by NOC, which is an inconsistency.

    Please monitor the PI SQL Data Access Server (RTQP Engine).

    2 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  General  ·  Flag idea as inappropriate…  ·  Admin →
  13. Fix PI Diagnostics so that it does not require restart after alarm

    At times, an alert generated by the NOC does not clear until the PI Diagnostic Services is restarted. It would be more convenient if this restart was not needed when the alarm clears.

    2 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  General  ·  Flag idea as inappropriate…  ·  Admin →
  14. Write a description for the PI Diagnostics Service and the PI Diagnostics UI Service

    When you open the Services program (services.msc), the PI Diagnostics Service and the PI Diagnostics UI Service both do not have a description. Please provide one.

    1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  General  ·  Flag idea as inappropriate…  ·  Admin →
  15. Replace PI Diagnostics Prerequisites 2.5.0.0 when installing PI Diagnostics 2.5.4.0

    If you install PI Diagnostics 2.5.4.0 when you have PI Diagnostics 2.5.2.0 already installed, PI Diagnostics x64 Prerequisites 2.5.4.0 and PI Diagnostics x86 Prerequisites 2.5.4.0 will not replace their existing 2.5.0.0 counterparts. Instead, the 2.5.0.0 counterparts are left as-is. Please change the PI Diagnostics install kit to replace the 2.5.0.0 versions of PI Diagnostics Prerequisites with the 2.5.4.0 versions.

    1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  General  ·  Flag idea as inappropriate…  ·  Admin →
  16. Prevent temporary drives from being monitored

    Currently if you have hard drives monitored by the NOC, if you attach a temporary hard drive, the NOC will begin to monitor it. This can be a nuisance to the customer if the drive has low disk capacity but is only being used for a short period of time. A potential solution would be to have a feature where customer can have the option to automatically monitor new drives.

    5 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  General  ·  Flag idea as inappropriate…  ·  Admin →
  17. Replace "All machines for your PI System" with ServerName if a system is a single server

    Customer does not want to see that "All machines for your PI System" 219876543 down, if system 219876543 only consists of one PI Server. Customer would like if we could refine our System alerts if PI Agent is only down for a single machine.

    1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Reporting  ·  Flag idea as inappropriate…  ·  Admin →
  18. Limit log file transfer to only essential context

    For remote assets, transferring the entire log files could be taxing on the network. Limit the transfer to aspects of the log that are essential for troubleshooting.

    1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  General  ·  Flag idea as inappropriate…  ·  Admin →
  19. Health tags for monitoring managed PI services

    Customer would like health tags to monitor PI Agent and PI Diagnostics Services in order to monitor and record their activity.

    1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  General  ·  Flag idea as inappropriate…  ·  Admin →
  20. Scheduled NOC reports to customer

    I would like to get a monthly report 12:00 am the first day of the month to 11:59 pm the last day of the month that includes both ITSM Incidents and NOC Incidents, showing the Site, System, Machine, object and issue (along with criticality) grouped by system/machine/objectissue with a count of occurences and average duration. That way we could review our monthly performance and trending the first week of each month.

    8 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  Reporting  ·  Flag idea as inappropriate…  ·  Admin →
← Previous 1 3

NOC Services

Categories

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
TELL US MORE
EVALUATING
PLANNED
IN DEVELOPMENT
COMPLETED
DECLINED