OSIsoft Cloud Services

Welcome to the OSIsoft Cloud Services feedback page!

We created this forum to hear your ideas, feature suggestions and feedback around our cloud offerings. For more information on OSIsoft Cloud Services, please refer to: https://cloud.osisoft.com/

Please note that your ideas and comments posted here are visible to all other users.

  • Hot ideas
  • Top ideas
  • New ideas
  • My feedback
  1. Send OCS data to PI System

    The ability to collect data directly into OCS (Cloud) but then route some data back to on premises PI Systems for merging with that data.

    34 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

    EVALUATING  ·  8 comments  ·  Data Egress  ·  Flag idea as inappropriate…  ·  Admin →
  2. OCS to IP.21 Data Egress

    Ability to egress OCS data to an on prem IP.21 system for the purposes of ensuring operators on the plant floor can visualize this data with their existing displays for real time decision making.

    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  ·  Data Egress  ·  Flag idea as inappropriate…  ·  Admin →
  3. Allow Multiple Data Archives per PI to OCS Agent

    Allowing data transfer for tags from multiple PI Data Archives with one agent will help to cut down on the number of agent services, and therefore machines, that need to be involved to send data from PI to OCS.

    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  ·  Data Egress  ·  Flag idea as inappropriate…  ·  Admin →
  4. Always supply millisecond component of timestamp in response payloads

    OCS returns a timestamp with no ‘milliseconds component’ if milliseconds is zero. This places a (small) burden on the client application to code for both possibilities … milliseconds present in the timestamp field and milliseconds not present. This places a small burden on some clients such that they have to code for both possibilities. It would be nice to have a consistent expression of time in response payloads.

    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  ·  Data Egress  ·  Flag idea as inappropriate…  ·  Admin →
  • Don't see your 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
TELL US MORE
EVALUATING
PLANNED
IN DEVELOPMENT
COMPLETED
DECLINED