1 Reply Latest reply on Aug 30, 2013 3:49 PM by tlebay

    Multistate Values

      What is the most sought after feature of Coresight that OSIsoft hears users want?

       

      Almost every conservation of Coresight I have ends up with the question "so how I do multistate the values" or "can I change the colour of the value". Although ProcessBook hosting may bring that feature (any confirmations???) still doesn't address core functionality of Coresight providing that capability.

       

      Could the Cog schema be expanded to include Multistate Sets and persist those along with displays in the SQL database? You either have user definable sets, sets based on Digital States Sets from PI Servers, or sets based on AF Enumeration Sets. I know it is likely technically more challenging than it sounds but this is one missing feature that is frustrating - amongst the general extensibility topic.

       

      Example Cog:

       

       

       
      <COG xmlns="http://xml.osisoft.com/context/cog" Version="1.0">
      
        <Databases Version="1.0">
          <PI Id="myPIServer" Node="rhys001" ConnectionTimeout="0" ConnectionType="PI3" DataAccessTimeout="0" />
        </Databases>
      
        <Datasources Version="1.0">
          <PIData Id="\\myPIServer\DigitalTag001" DbRef="myPIServer">
            <Tag Name="DigitalTag001" />
          </PIData>
        </Datasources>
      
        <Symbols Version="1.0">
          <Symbol Id="sym1">
            <Datasource Ref="\\myPIServer\DigitalTag001" />
             <MultiState Ref="Set2" />
          </Symbol>
        </Symbols>
      
        <Groups Version="1.0" />
        <Contexts Version="1.0">
          <Range StartTime="*-5h" EndTime="*" />
        </Contexts>
      
        <MultiStateSets Version="1.0">
           <MultiStateSet Id="Set1" Type="AFEnumerationSet" DbRef="myAFServer" Ref="AFEnum001">
                <State Id="State 0">
                     <Lower>0</Upper>
                     <Upper>1</Upper>
                     <Color>System.Drawing.Color.Red</Color>
                </State>
                <State Id="State 1">
                     <Lower>1</Upper>
                     <Upper>2</Upper>
                     <Color>System.Drawing.Color.Green</Color>
                </State>
                <State Id="State 3">
                     <Lower>2</Upper>
                     <Upper>3</Upper>
                     <Color>System.Drawing.Color.Blue</Color>
                </State>
           </MultiStateSet>
           <MultiStateSet Id="Set2" Type="DigitalStateSet" DbRef="myPIServer" RefName="DigSet001">
                <State Id="State 0">
                     <Lower>0</Upper>
                     <Upper>1</Upper>
                     <Color>System.Drawing.Color.Red</Color>
                </State>
                <State Id="State 1">
                     <Lower>1</Upper>
                     <Upper>2</Upper>
                     <Color>System.Drawing.Color.Green</Color>
                </State>
                <State Id="State 3">
                     <Lower>2</Upper>
                     <Upper>3</Upper>
                     <Color>System.Drawing.Color.Blue</Color>
                </State>
           </MultiStateSet>
           <MultiStateSet Id="Set2" Type="UserDefined">
                <State Id="State 0">
                     <Lower>-50</Upper>
                     <Upper>50</Upper>
                     <Color>System.Drawing.Color.Red</Color>
                </State>
                <State Id="State 1">
                     <Lower>50</Upper>
                     <Upper>10000</Upper>
                     <Color>System.Drawing.Color.Green</Color>
                </State>
                <State Id="State 3">
                     <Lower>10000</Upper>
                     <Upper>Single.MaxValue</Upper>
                     <Color>System.Drawing.Color.Blue</Color>
                </State>
           </MultiStateSet>
        </MultiStateSets>
        
      </COG>
      

       

        • Re: Multistate Values
          tlebay

          Multi-state has been one of the most requested features to add to PI Coresight, and we have definite plans to add it.  Some of the functionality was even in the product during the first public demo at our Users Conference back in 2010.

           

          As you suggest, we are hoping that the ProcessBook viewing feature we are currently working on will meet some of this need.

           

          A big part of why we have not yet delivered on this feature, as a core part of the product, is that we want to protect another core feature of the product; that is fast and easy display creation.  You can see from ProcessBook that there is a significant amount of UI needed to configure and manage multi-state behavior, not to mention a fair amount of time for the user to configure it. And the way this works today in ProcessBook (and the suggestion you have with saving the configuration in a COG) is that the configuration gets saved with a specific display, so the work can't be reused anyplace else.

           

          We have been talking with the PI-AF team for quite awhile on how to leverage AF to make this a better, more valuable experience.  The vision is to have the multi-state configuration stored in PI-AF so that PI Coresight, and other clients, can pick the information up and use it anyplace the data item in question is used. When you add a data item to a display in PI Coresight the multi-state behavior would be configured automatically.

           

          We understand that a global setting will not always work for a specific display or use case so we expect to allow a PI Coresight user to modify a multi-state for a specific display.  This allows a user to have a starting point from the system setting, but still have enough control to meet a more specific need.

           

          Ideally we will have an easy work-flow that will allow settings from an individual display to be promoted to a public setting.  This will give a way for subject matter experts to institutionalize their knowledge using familiar tools (rather than the Admin tools required today).

           

          We are looking at this type of experience not only for multi-state but Notification and Events as well.