![\"\"](\"https:\/\/oihelp.corporate.ifs.com\/help\/wp-content\/uploads\/2018\/12\/word-image-135.png\")
<\/p>\nThe Data components pass input data through to another component, and can direct the process flow according to various circumstances.<\/p>\n
The ConfidenceOf component retrieves the confidence value of the input data point, as an integer value from 0 to 100 (a percentage). If the confidence value does not exist, the process assumes a confidence value of 100 and continues.<\/p>\n
<\/p>\n
The confidence of entity values is taken from the underlying historian, with the Adaptor mapping the historian's \"data quality\" value to a confidence. For example, some historians report a confidence as a percentage directly, whereas others have a status (such as good or bad) which is mapped to a value of 100 or 0 respectively.<\/p>\n
Properties<\/p>\n
This component has no additional properties.<\/p>\n
Inputs<\/p>\n
Flow The component that acts as a trigger for this component should be connected to this pin.<\/p>\n Number The data point for which to retrieve the confidence value. This input is required. Not connecting this pin will produce an error.<\/p>\n Outputs<\/p>\n Number\u00a0 The confidence value of the input, between 0 and 100. Not connecting this pin will produce a warning.<\/p>\n Example<\/p>\n In the following example, the temperature is split into two flows. One flow checks to see if the confidence is greater than 90%. If not, an event is raised and the state of the entity changes to Low Confidence.<\/p>\n If the confidence is greater than 90%, the temperature value is checked to see if it is greater than 50. If it is, an event is raised and the state of the entity changes to Above. Otherwise, an event is raised and the state of the entity changes to Below.<\/p>\n The Get Discrete Single component retrieves the value of the current data point from an input data stream that has a discrete<\/em> process data type.<\/p>\n Module Properties<\/p>\n This component has no additional properties.<\/p>\n Process Properties<\/p>\n Process Data Type<\/p>\n You should ensure the process data type is set to Discrete.<\/em><\/p>\n Default State<\/p>\n You can specify one of the states in the process to be the default or \"normal\" state for the process.<\/p>\n Inputs<\/p>\n Flow\u00a0 The output pin of another component, typically an event, should be connected to the flow pin for this component.<\/p>\n Input An Input or Primary Input component that retrieves a data stream.<\/p>\n Outputs<\/p>\n Number\u00a0 If the data point retrieved is a number value, the process follows this path.<\/p>\n Text\u00a0 If the data point retrieved is a text value, the process follows this path.<\/p>\n NoData\u00a0 If the input stream contains no data, the process follows this path. Note that this pin will not be triggered while testing the process.<\/p>\n Example<\/p>\n In the following example, data is fetched from three sources. Discrete data is obtained as the primary input, which is evaluated against min and max values from two different continuous data sources. If the primary input does not contain any data points, the state of the entity changes to No Data<\/em>.<\/p>\n The Get Single component retrieves the value of the current data point from an input data stream that has a continuous<\/em> process data type.<\/p>\n Module Properties<\/p>\n This component has no additional properties.<\/p>\n Process Properties<\/p>\n Process Data Type<\/p>\n You should ensure the process data type is set to Continuous.<\/p>\n Default State<\/p>\n You can specify one of the states in the process to be the default or \"normal\" state for the process.<\/p>\n Inputs<\/p>\n Flow\u00a0 The output pin of another component, typically an event, should be connected to the flow pin for this component.<\/p>\n Input\u00a0 An Input or Primary Input component that retrieves a data stream.<\/p>\n Outputs<\/p>\n Number\u00a0 If the data point retrieved is a number value, the process follows this path.<\/p>\n Text\u00a0 If the data point retrieved is a text value, the process follows this path.<\/p>\n Example<\/p>\n In the following example, a temperature value is retrieved from an input stream. We are expecting a number, so if a string is supplied then the process terminates with an error. If a number is supplied, the process continues to run until it raises an event.<\/p>\n The Get Window component retrieves an historical period of data from the input data stream for a specified period.<\/p>\n For example, you might want to retrieve all the data from the previous 24 hours, or you may want to get the last 10 data points.<\/p>\n Module Properties<\/p>\n This component has no additional properties.<\/p>\n Process Properties<\/p>\n Data Windowing Type<\/p>\n You must specify a Data Windowing Type for the process to pass validation. The Data Windowing Type must be consistent with the data types retrieved by the process.\u00a0Options are:<\/p>\n Note<\/strong>: If you don\u2019t specify a large enough data window, you may get more data than you asked for because of the way data is cached in Sentinel. Ensure that the number of data points or time period is larger than the largest period you go back. E.g. If your input period is 1 week, ensure the Time Period specified in the Data Windowing options is larger than 1 week. Similarly, if your input retrieves 10 data points, ensure the Data Points specified in the Data Windowing options is more than 10.<\/p>\n Inputs<\/p>\n Flow\u00a0 The component that acts as a trigger for this component should be connected to this pin.<\/p>\n Data Stream\u00a0 An Input or Primary Input component that retrieves a data stream. This input is required. Not connecting this pin will produce an error.<\/p>\n P\u00a0 The period of data to retrieve. This can either be a number of data points or a time period, as specified in the Data Windowing property. This input is required. Not connecting this pin will produce an error. You could connect to any component that produces either a number or a time period, such as:<\/p>\n Outputs<\/p>\n Data Set An array of values retrieved from the input data source. Not connecting this pin will produce a warning.<\/p>\n Example<\/p>\n In the following example, we compare the first and last value of a given time period. The process retrieves a 24-hour window of data using Get Window, then uses Get First<\/a> to get the first value of that window, and then compares it with the current value.<\/p>\n The Get Window From component retrieves an historical period of data from the input data stream for a specified period, ending at a specified time.<\/p>\n For example, you may want to get the all the data for the previous week, ending on the last day of the week.<\/p>\n Module Properties<\/p>\n This component has no additional properties.<\/p>\n Process Properties<\/p>\n Data Windowing Type<\/p>\n You must specify a Data Windowing Type for the process to pass validation. The Data Windowing Type must be consistent with the data types retrieved by the process. Options are:<\/p>\n Note<\/strong>: If you don\u2019t specify a large enough data window, you may get more data than you asked for because of the way data is cached in Sentinel. Ensure that the number of data points or time period is larger than the largest period you go back. E.g. If your input period is 1 week, ensure the Time Period specified in the Data Windowing options is larger than 1 week. Similarly, if your input retrieves 10 data points, ensure the Data Points specified in the Data Windowing options is more than 10.<\/p>\n Inputs<\/p>\n Flow\u00a0 The component that acts as a trigger for this component should be connected to this pin.<\/p>\n Data Stream\u00a0 An Input or Primary Input component that retrieves a data stream. This input is required. Not connecting this pin will produce an error.<\/p>\n end The ending timestamp to look back from. This input is required. Not connecting this pin will produce an error.<\/p>\n P The period of time for which to retrieve data. For example, 7 days. This input is required. Not connecting this pin will produce an error.<\/p>\n Outputs<\/p>\n Data Set An array of values retrieved from the input data source. Not connecting this pin will produce a warning.<\/p>\n Example<\/p>\n In the following example, the input data is compared with the data from the previous day to see if it is above or below. We use the Get Window From component to retrieve the previous day's data, ending at the current timestamp.<\/p>\n The previous day's value is obtained by using the Get First component to retrieve the first value in the data set supplied by Get Window From.<\/p>\n We then compare that value with the current value obtained by the Get Single component.<\/p>\n The Get Window Start Filter component retrieves an historical period of data from the input data stream for a specified period, starting at a specified time.<\/p>\n For example, you may want to get the first week worth of data from the previous month.<\/p>\n Module Properties<\/p>\n This component has no additional properties.<\/p>\n Process Properties<\/p>\n Data Windowing Type<\/p>\n You must specify a Data Windowing Type for the process to pass validation. The Data Windowing Type must be consistent with the data types retrieved by the process.\u00a0Options are:<\/p>\n Note<\/strong>: If you don\u2019t specify a large enough data window, you may get more data than you asked for because of the way data is cached in Sentinel. Ensure that the number of data points or time period is larger than the largest period you go back. E.g. If your input period is 1 week, ensure the Time Period specified in the Data Windowing options is larger than 1 week. Similarly, if your input retrieves 10 data points, ensure the Data Points specified in the Data Windowing options is more than 10.<\/p>\n Inputs<\/p>\n Flow\u00a0 The component that acts as a trigger for this component should be connected to this pin.<\/p>\n Data Stream\u00a0 An Input or Primary Input component that retrieves a data stream. This input is required. Not connecting this pin will produce an error.<\/p>\n P\u00a0 The period of data to retrieve. This can either be a number of data points or a time period, as specified in the Data Windowing property. This input is required. Not connecting this pin will produce an error. You could connect to any component that produces either a number or a time period, such as:<\/p>\n start The starting timestamp to look forward from. No data is returned before this time. For example, we could specify the start time to be the time that the process came out of suppression. This input is required. Not connecting this pin will produce an error.<\/p>\n Outputs<\/p>\n Data Set An array of values retrieved from the input data source. Not connecting this pin will produce a warning.<\/p>\n Example<\/p>\n In the following example, Get Window Start Filter is used to retrieve the Daily Oil data for the first week of the year. The values obtained over that first week are averaged. If the average is greater than 100,000, an event is raised and the state of the entity changes to Above, otherwise an event is raised and the state of the entity changes to Below.<\/p>\n The Merge component is used to merge together one or more data flows. Any input data that is received is forwarded as the output data.<\/p>\n When the process flows backwards through the Merge component to retrieve data, the process always follows the top pin only.<\/p>\n Properties<\/p>\n Num Inputs<\/p>\n The number of input pins for this component. You can specify up to 16 inputs.<\/p>\n Inputs<\/p>\n Mixed\u00a0 Any data type to forward to the output pin.<\/p>\n Outputs<\/p>\n Mixed\u00a0 Any data type to forward to the connected component. Not connecting this pin will produce a warning.<\/p>\n Example<\/p>\n In the following example, the input temperature is checked to see if it is above 28. If it is, an event is raised. When this event is raised, the text Above Event is sent to the log.<\/p>\n If the temperature is not higher than 28, a different event is raised. When this event is raised, the text Below Event is sent to the log. The Merge component is used as a pathway to join the two flows and send the relevant text to the log.<\/p>\n The Pass Through component forwards the input to the output.<\/p>\n Properties<\/p>\n This component has no additional properties.<\/p>\n Inputs<\/p>\n Flow\u00a0 The component that acts as a trigger for this component should be connected to this pin. This pin must be connected. Not connecting this pin will produce an error.<\/p>\n Mixed\u00a0 Any data type to forward to the output pin. This input is required. Not connecting this pin will produce an error.<\/p>\n Outputs<\/p>\n Mixed\u00a0 Any data type to forward to the connected component. Not connecting this pin will produce a warning.<\/p>\n Example<\/p>\n In the following example, the input temperature is checked to see if it is above 28. If it is, an event is raised. When this event is raised, the text Above Event is sent to the log.<\/p>\n If the temperature is not higher than 28, a different event is raised. When this event is raised, the text Below Event is sent to the log.<\/p>\n The Pass Through component is used as the bridge to send the relevant text to the log.<\/p>\n The Relay component sends the input data to one of the output pins, depending on the Boolean input.<\/p>\n Properties<\/p>\n This component has no additional properties.<\/p>\n Inputs<\/p>\n Flow\u00a0 The component that acts as a trigger for this component should be connected to this pin.<\/p>\n Boolean The Boolean value that determines which output pin should be followed. This input is required. Not connecting this pin will produce an error.<\/p>\n Mixed\u00a0 The data value that is to be sent to the output pin. This input is required. Not connecting this pin will produce an error.<\/p>\n Outputs<\/p>\n T\u00a0 If the Boolean value is True, the process follows this path. Not connecting this pin will produce a warning.<\/p>\n F\u00a0 If the Boolean value is False, the process follows this path. Not connecting this pin will produce a warning.<\/p>\n Example<\/p>\n In the following example, the Relay component is used to direct the flow to raise an event and change the state to Above or Below as required. It also takes the temperature value and passes it through to the event for use as metadata in the Sentinel event report.<\/p>\n The Sequence component iterates the process over each output connection, from the first pin at the top to the last pin at the bottom, passing the input data to each pin.<\/p>\n The process first follows the first pin, and once that process has finished the process returns to the Sequence component and commences the second path, and so on until the last path is completed, or until the iteration is stopped prematurely by an End<\/a> or Error<\/a> component on one of the process paths.<\/p>\n Properties<\/p>\n Num Outputs<\/p>\n The number of output pins for this component. You can specify up to 16 outputs.<\/p>\n Inputs<\/p>\n Flow\u00a0 The component that acts as a trigger for this component should be connected to this pin.<\/p>\n Mixed\u00a0 The input data, of any data type, to send to the output pins. This input is required. Not connecting this pin will produce an error.<\/p>\n Outputs<\/p>\n Mixed\u00a0 The output pins direct the data flow. Missing output connections will be skipped in the process flow.<\/p>\n Example<\/p>\n The following example is similar to that used in Flow Sequence. Temp 1 is checked against Temp 2. If Temp 1 is greater than Temp 2, the following things happen:<\/p>\n The Split component is used to send a data point to several components simultaneously. The process flow, however, follows the top pin. The data point is sent to the other components in preparation for further processing, to avoid repeated calls to fetch data.<\/p>\n Note<\/strong>: It is important to locate the Start component after <\/strong>the Split component, otherwise the process flow will only ever follow that of the top pin.<\/p>\n Properties<\/p>\n Num Outputs<\/p>\n The number of output pins for this component. You can specify up to 16 outputs.<\/p>\n Inputs<\/p>\n Mixed\u00a0 A single data point, of any data type, which is to be split into multiple data flows. This input is required. Not connecting this pin will produce an error.<\/p>\n Outputs<\/p>\n Mixed\u00a0 The data point is sent to all output pins simultaneously. Not connecting this pin will produce a warning.<\/p>\n Example<\/p>\n In the following example, the Split component is used to send the temperature data to three components:<\/p>\n The Switch component forwards the input data point to the \u2018T\u2019 pin only if the Boolean<\/a> input is True. If the Boolean input is False, the flow follows the \u2018F\u2019 output pin.<\/p>\n Properties<\/p>\n This component has no additional properties.<\/p>\n Inputs<\/p>\n Flow\u00a0 The component that acts as a trigger for this component should be connected to this pin.<\/p>\n Boolean The Boolean value that determines whether to send data to the \u2018T\u2019 pin. This input is required. Not connecting this pin will produce an error.<\/p>\n Number\u00a0 The data value that is to be sent to the \u2018T\u2019 pin, if the Boolean value is True. This input is required. Not connecting this pin will produce an error.<\/p>\n Outputs<\/p>\n T\u00a0 If the Boolean value is True, the process follows this path. Not connecting this pin will produce a warning.<\/p>\n F\u00a0 If the Boolean value is False, the process follows this path.<\/p>\n Example<\/p>\n In the following example, the Switch component is used to direct the flow to raise an event and change the state of the entity to Above, only if the Temperature is greater than Max. It also takes the temperature value and passes it through to the event for use as metadata in the Sentinel event report.<\/p>\n The TimestampOf component retrieves the timestamp of the input. If the input does not have a timestamp, the process ends.<\/p>\n Properties<\/p>\n This component has no additional properties.<\/p>\n Inputs<\/p>\n Flow\u00a0 The component that acts as a trigger for this component should be connected to this pin.<\/p>\n Mixed\u00a0 The input which has a timestamp. This input is required. Not connecting this pin will produce an error.<\/p>\n Outputs<\/p>\n Date Time The timestamp of the input. Not connecting this pin will produce a warning.<\/p>\n Example<\/p>\n In the following example, the timestamps of both inputs are retrieved. The first timestamp is written to memory, and the second timestamp is processed by the attached component.<\/p>\n The Value Writer component is used to write a data point to an entity.<\/p>\n Properties<\/p>\n This component has no additional properties.<\/p>\n Inputs<\/p>\n Flow\u00a0 The component that acts as a trigger for this component should be connected to this pin.<\/p>\n name The name of the entity. This input is required. Not connecting this pin will produce an error.<\/p>\n value\u00a0 The value to write to the entity. This input is required. Not connecting this pin will produce an error.<\/p>\n Note<\/strong>: This value must<\/em> have a timestamp.<\/p>\n Outputs<\/p>\n![\"\"](\"https:\/\/oihelp.corporate.ifs.com\/help\/wp-content\/uploads\/2018\/12\/word-image-18.png\")
<\/a><\/p>\n<\/a><\/p>\n<\/a><\/p>\n<\/a><\/p>\nGet Discrete Single<\/h2>\n
<\/p>\n<\/a><\/p>\n<\/a><\/p>\n<\/a><\/p>\n<\/a><\/p>\n<\/a><\/p>\n<\/a><\/p>\nGet Single<\/h2>\n
<\/p>\n<\/a><\/p>\n<\/a><\/p>\n<\/a><\/p>\n<\/a><\/p>\n<\/p>\nGet Window<\/h2>\n
<\/p>\n\n
<\/a><\/p>\n<\/a><\/p>\n<\/a><\/p>\n\n
<\/a><\/p>\n<\/a><\/p>\nGet Window From<\/h2>\n
<\/p>\n\n
<\/a><\/p>\n<\/a><\/p>\n<\/a><\/p>\n<\/a><\/p>\n<\/a><\/p>\n<\/a><\/p>\nGet Window Start Filter<\/h2>\n
<\/p>\n\n
<\/a><\/p>\n<\/a><\/p>\n<\/a><\/p>\n\n
<\/a><\/p>\n<\/a><\/p>\n<\/a><\/p>\nMerge<\/h2>\n
<\/p>\n<\/a><\/p>\n<\/a><\/p>\n<\/a><\/p>\nPass Through<\/h2>\n
<\/p>\n<\/a><\/p>\n<\/a><\/p>\n<\/a><\/p>\n<\/a><\/p>\nRelay<\/h2>\n
<\/p>\n<\/a><\/p>\n<\/a><\/p>\n<\/a><\/p>\n<\/a><\/p>\n<\/a><\/p>\n<\/a><\/p>\nSequence<\/h2>\n
<\/p>\n<\/a><\/p>\n<\/a><\/p>\n<\/a><\/p>\n\n
\nIf not, the process returns to the next output pin of the Sequence.<\/li>\n
\nIf not, the process returns to the next output pin of the Sequence.<\/li>\n<\/a><\/p>\nSplit<\/h2>\n
<\/p>\n<\/a><\/p>\n<\/a><\/p>\n\n
<\/a><\/p>\nSwitch<\/h2>\n
<\/p>\n<\/a><\/p>\n<\/a><\/p>\n<\/a><\/p>\n<\/a><\/p>\n<\/a><\/p>\n<\/a><\/p>\nTimestampOf<\/h2>\n
<\/p>\n<\/a><\/p>\n<\/a><\/p>\n<\/a><\/p>\n<\/a><\/p>\nValue Writer<\/h2>\n
<\/p>\n<\/a><\/p>\n<\/a><\/p>\n<\/a><\/p>\n