Jump to content

Leaderboard


Popular Content

Showing content with the highest reputation since 05/06/2020 in all areas

  1. 4 points
    Hi Esther, you can do this the following way: 1. Create a Periodic Condition (found in Tools - Pane): 2. Use Signal from Condition to calculate the total duration. Result: Regards, Thorsten
  2. 3 points
  3. 2 points
    Contextual data is often brought into Seeq to add more information to time series data. This data tends to be brought in as a condition, with the capsule properties of this condition containing different pieces of information. In some cases, a particular capsule property may not contain just one piece of information; it may contain different pieces that are separated based on some logic or code. Rather than having users visually parse the code to extract the segments of interest, Seeq can be used to extract the substring continuously. The code below extracts a substring based on its location in the property. This code is based on incrementing from left to right, starting at the beginning of the string. Changing the inputs will extract a substring from different positions in the property selected. //Inputs Section (Start and end assume reading left to right) $condition = $hex_maint //Recommend to filter condition to only include correct property values $property_to_capture = 'Reason Code' $start_position = 1 //Incrementing starts from 1 $number_of_characters = 2 //Including the start //Code Section $property_signal = $condition.toSignal($property_to_capture).toStep(2wk) //Change duration for interpolation $start_position_regex = ($start_position - 1).toString() //Regular exression indexes from 0 $number_of_characters_regex = ($number_of_characters - 1).toString() $property_signal.transform( $sample -> sample( $sample.getKey(), $sample.getValue().replace( '/.{'+$start_position_regex+'}(?<Hold>.{'+$number_of_characters_regex+'}.).*/','${Hold}') ) ) This alternative version is based on incrementing right to left, starting at the end of the string. //Inputs Section (Start and end assume reading left to right) $condition = $hex_maint //Recommend to filter condition to only include correct property values $property_to_capture = 'Reason Code' $end_position = 1 //Relative to end, incremented from 1 $number_of_characters = 4 //Including the end character //Code Section $property_signal = $condition.toSignal($property_to_capture).toStep(2wk) //Change duration for interpolation $end_position_regex = ($end_position).toString() $number_of_characters_regex = ($number_of_characters - 1).toString() $property_signal.transform( $sample -> sample( $sample.getKey(), $sample.getValue().replace( '/.*(?<Hold>.{'+$number_of_characters_regex+'}.{'+$end_position_regex+'})$/','${Hold}' ) ) ) Note the output of these formulas is a string. In the case that a numeric value is wanted, append .toNumber() after '${Hold}') Below is an example of the results. With this substring parsed, all of Seeq's analytical tools can be further leveraged. Some examples are developing histograms based on the values of the substring and making conditions to highlight whenever a particular value in the substring is occurring.
  4. 2 points
    Question: I have a scorecard metric displaying the maximum value of a signal during a given capsule. I have the Scorecard coloring red if the value is >2%. Is there any way to display a scorecard with just color coded cells containing no values? What I am seeing now: What I would like to create: Solution: In general, the approach to creating a blank scorecard with color thresholds is to create a string signal comprised of varying amounts of spaces for each threshold/band. Then you can apply that number of spaces as a color threshold in the Scorecard metric tool. 1) Create your "empty" string signal in Formula. In the example below, we have a baseline signal that is a completely empty string and we are splicing in a string containing two spaces any time the value of the original signal is greater than 2%. You can see that the empty string signal has what looks like a constant value each time the original signal is > 2%, but when you hover the cursor over the signal you see that it is actually blank. 2) Use Formula to create a scalar threshold value to select as your threshold in Scorecard. Note, in versions R22.0.47 and greater, string values are accepted as thresholds in the scorecard metric tool, so this step can be skipped. 3) Calculate your scorecard metric. For versions before R22.0.47, the tool input for the thresholds will look like this: For versions R22.0.47 and newer, you can use: 4) The final scorecard (validated against the original one containing values):
  5. 2 points
    Hi Greg Since you already have a condition identifying when your signal changes, to identify the magnitude of the change all you need to do is use Signal From Condition. Here is an example of how it might look: In this case i am using "Range" because it will always give me a positive value of the change in my power signal. If i wanted to know if it was positive or negative I would use "Delta" instead. Here i am using the Duration as my timestamp so i can more easily accomplish the next step- filtering the original change condition. Since you want to count the number of instances the value changes by more than some amount, we can then filter our original condition (the one that identified the change) so it only retains the capsules where the change was over your threshold. To do this i will use Formula: In this case, i am filtering my Load Swing to keep capsules where the swing is greater than 25kW. You can see the filtered condition is shown in blue where my original Condition is shown in green. From here, you can use the Scorecard Metric to count the number of the filtered capsules. Hope this helps!
  6. 2 points
    Hello Felix, every item you create in Seeq is scoped to the current workbook by default. If you add another worksheet to the workbook you may find the signal under the "Recently Accessed" section in the Data Tab: If not present under "Recently Accessed" you can also search for it as you do with other items. You can pin the item for better acceessibility by clicking on the the "Pin" icon next to it. Anonther section "Pinned" is added to the Data Tab containing all pinned items: However, you have to add the signal to the Display Pane if you want it to be displayed. In case you want the item to be availabe in other workbooks as well, you can change the scope of the item to make it availabe globally. Be carefull: This action cannot be undone! Hope this helps. Regards, Thorsten
  7. 2 points
    You want to duplicate the workbook (the entire workbench analysis) not the worksheet (A page in the workbook). Duplicating the workbook will allow you to change the formulas.
  8. 1 point
    When I have created valueless metrics in the past, I have taken advantage of the number format setting in the item properties tab. You can do this with the following steps. 1. Remove the units from the signal you want to use as the basis for your metric. See screenshot below for details. 2. Fill out the metric as you normally would with the desired thresholds. See example below. 3. After creating the metric go into the item properties of that metric by clicking on the “I” icon in the details pane. Once in the items properties tab for the metric click override number format and set the number format to “ “. (note there is a space between the quotes) See screenshot below for details.
  9. 1 point
    I have a piece of equipment that regularly goes through cycles and I want to compare the cycles. In this case I know the exact date and time of the equipment runs so I have used the Custom Condition tool to specify my Previous Run and Current Run. Custom Condition allows you to enter dates for the condition you are interested in. This can also be done in formula. To create the condition for my Next Run I used Seeq's formula because this run is currently on going and I do not know the end date. This approach allows me to specify that this condition end at now. condition(2d, capsule('2020-06-01T17:48Z', now())) Now that I have defined my Previous, Current and Next runs I want to calculate the run time of each of those periods. I can do this in Seeq's formula tool using the time since function. This will allow me to create a signal whose value is the time since the start time of a condition. This signal will end at the end of the condition. In this case my time counter will be in hours, if you wanted it in days instead you would change the 1h to 1d. timeSince($condition, 1h) I duplicated this formula three times for my previous, current and next runs. Remember, you can always duplicate a formula by clicking the "i" by item properties. You can compare the run lengths of the 3 runs by putting them on the same lane and same axis. You'll noticed my Next Run has just started so the time since for it is much smaller. Lastly, you can switch to capsule time view to compare the run length as well as different signals over the run. In this case we are looking at the temperature of each run as well as the run length. You could imagine using this approach to monitor heat transfer coefficients, reactor temperature, reactor conversion, or % sulfur removed.
  10. 1 point
    Question: How do you calculate the cusum using Seeq? Answer: CUSUM is short for "cumulative sum." It is a formula used to determine the gradual change in a series of quantities over time. It can be easily calculated in Seeq with a few steps using point and click tools or with one Formula. Steps using point and click tools: 1. Use Periodic Condition to define the periods over which you want to do the cusum (hours, days, weeks, etc.). 2. Use Signal from Condition to find the average of the signal over the periodic condition. 3. Use Formula to do the signal minus the average. 4. Use Signal from Condition to calculate the sum of this new signal over the periodic condition. This will be your final answer, the cusum. Formula: You can copy this into Formula, name your desired signal $signal in the formula tool, and use your desired periodic condition if different than days: $Periods = days() $average = $signal.aggregate(average(), $periods, durationkey()) $difference = $signal - $average $difference.aggregate(sum(), $periods, durationkey())
  11. 1 point
    Hi Jules, I guess converting your sawtooth signal to a continous one should work, so I modified the last formula a little bit: (($continousValues / 5000)-($continousValues / 5000).floor() == 0) // -> create capsules when continous signal can be divided by 5000 .growEnd(1y) // -> grow capsule to start of the next capsule .transform($c ->{ $c.setProperty('Values', $continousValues.count($c)) // -> create capsule property containing the count of samples inside the capsule .setProperty('ValueStart', $continousValues.getValue($c.getStart())) // -> create capsule property containing the value at start of the capsule .setProperty('ValueEnd', $continousValues.getValue($c.getEnd())) // -> create capsule property containing the value at end of the capsule }) The first part of the formula creates a capsule each time the value of the signal can be divided by 5000 (0, 5000, 10000, 15000, ...). These capsules are very short in duration, but can be extended to the start of the next capsule using grow(). The last part just adds some properties to the capsules used to validate the formula . Result should look like this: You may notice that the number of values is sometimes greater than 5000. I think this may occur because it counts the number of samples. If the value in the Historian does not change it may create another sample with the same value anyway. I guess the better values to check are the values at start and end of the capsule, which always can be divided by 5000. Regards, Thorsten
  12. 1 point
    Hi Jules, as I do not know your data I created an example based on the sample data generated within Seeq. Therefore I created a sawtooth signal resetting every 60 days. So you may have to do adjustments to that solution. . First step was transforming this to a continous signal using formula: $values.runningDelta().max(1).runningAggregate(sum(),years()).toLinear() More details can be found in this post from @Allison Buenemann: Last step is creating a condition that contains exactly 5000 samples: (($continousValues-($continousValues / 5000).floor()).runningDelta() == 0) // -> create capsules when counter % 5000 == 0 .growEnd(1y) // -> grow capsule to start of the next capsule .transform($c -> $c.setProperty('Values', $continousValues.count($c))) // -> create capsule property containing the count of samples inside the capsule Hope this helps. Regards, Thorsten
  13. 1 point
    Question: How do I normalize a signal in Seeq? Sometimes it can be helpful to view data on a normalized scale or used normalized inputs in a model. Solution: This solution is posted using R22.0.47 but is applicable to earlier versions. Slight modifications of the formula may be required for earlier versions. 1. Let's start by loading our signal... 2. Next we'll use Formula to create a normalized signal. In Formula we do the following steps Define the time period over which we will do the normalization Calculate the min and max values which occur during that time period Calculate the delta between the min and max Finally, calculate the normalized signal Here is the code snippet if you'd like to copy and paste... $timePeriod = capsule('2019-01-01T00:00-05:00', '2020-01-01T00:00-05:00') $max = $signal.maxValue($timePeriod) $min = $signal.minValue($timePeriod) $delta = $max - $min ($signal - $min) / $delta 3. View the results in Seeq. Note that I optionally created scalar boundaries at 0 and 1 to highlight the normalization of my signal...
  14. 1 point
    Hi Esther, based on the information you provided I would create a condition for each of the two durations you want to calculate. To do this in formula I first recommend you to rename the variables for better readability of the formula. For the first one ("ADD Durations for when equipment is stopped and in lag OR when the equipment is stopped or standby") you may use: ($stopped && $lag) || ($stopped || $standby) //-> can be shortened to $stopped || $standby For the second one ("ADD Durations for when equipment is stopped but not in lag or standby") try: $stopped && !($lag || $standby) Depending on what you want to do with the duration you may use different tools for calculation (e.g. Signal from Condition, Scorecard Metric, use of capsule properties, ...) Let me know if you need more help. Regards, Thorsten
  15. 1 point
    Hi Felix, You can embed the scorecard multiple times by clicking on the content in Seeq Organizer and copying and pasting another copy of it. You can then click on each of the copies and adjust the date range of that particular copy. My recommendation to create the scorecard you originally described is: 1) Create a simple scorecard metric calculating the average value of your signal. Remove the scorecard metric name column and set header to none. 2) Create a new Organizer Topic. Insert a table into that Organizer. Make the headings of the table columns the date ranges that you are interested in. 3) Configure your date ranges in Organizer Topic using the Create Custom Date Range Option. 4) Add your scorecard from workbench into Organizer Topic. Click on the scorecard metric value and copy and paste it into each of the other table cells. Then click on each scorecard individually to edit which date range is applied to it: The final scorecard looks like: Thanks, Allison
  16. 1 point
    Alternative Solution If you already have conditions with capsules that start (or end) at the peak max then you can use a Composite Condition followed by Signal from Condition. Here is how... 1. Use Composite Condition to join the two capsules. In this example the capsules start at the peak max so the join will be inclusive of A but not inclusive of B. 2. Use Signal from Condition to calculate the duration of the Peak-to-Peak capsules.
  17. 1 point
    Use Case Background In this Use case, we have 2 signals: Signal 1 and Signal 2. We'd like to use Seeq to calculate the offset (in time) of the peaks in the two signals. The following steps can be used to perform this calculation. Analysis Steps 1. Use the Value Search tool to create a condition for the peaks. 2. Use the Signal from Condition tool (twice) to calculate the maximum value of each signal during the Peaks condition. Be sure to place the timestamp of the statistic at the point of maximum value. 3. Finally, use the following syntax in Formula to calculate the offset between each set of peaks. The result of this Formula is a new time series signal with a sample reporting the offset for each pair of peaks.
  18. 1 point
    Hi John, The following method can be used to calculate an hourly average and standard deviation over the lagging 24 hours. 1. Create a periodic condition 24 hours in length that begins every hour. Periodic conditions this specific cannot be done in the Periodic Condition wizard tool, but can be done in Formula using the following syntax: periods(24h, 1h) 2. Use signal from condition to calculate an hourly average over the last 24 hours. Make sure to select end as where you want to put the timestamp of the summary statistic. 3. Use a similar method with signal from condition to calculate an hourly standard deviation over the last 24 hours. 4. Use formula to calculate an upper limit for your temp signal equal to your 24 hr lagging average + X*standard deviation. In this example we chose + 3 SD, so the formula syntax is $average + (3*$standardDeviation) 5. Use formula to calculate a lower limit for your temp signal equal to your 24 hr lagging average - X*standard deviation. In this example we chose - 3 SD, so the formula syntax is $average - (3*$standardDeviation) 6. Use the Boundaries tool to transform your upper and lower limit signals into shaded boundaries.
  19. 1 point
    Use Case Background Batch operations may be characterized by two conditions. The first condition represents the start of the batch and the second condition contains the end of the batch. Each capsule has the batch ID as a capsule property. The goal is to make a single condition that represents the duration of the batch by joining the start and end conditions. Solution 1 - Simple Join If the batches are orderly and the end of one batch does not overlap with the start of the next batch, then using the Join logic in the Composite Condition tool is the easiest option. However, if the end of one batch overlaps with the start of another, then some batches may not be joined. In the screenshot below the third batch on June 6 is not joined. Solution 2 - Use Formula to join based on matching the batch ID capsule property By using a transform in Formula all the batches in this scenario can be joined. In addition the batch ID property is assigned to the new capsules. Here is the Formula used to do this... Variables Name Item Type $startCond Start Condition Condition $endCond End Condition Condition Formula //Define the max time into the future to look for the end capsule $lookAheadTime = 2d //Resize the starting capsule to extend for the druation of the look ahead time $startCond.move(0s,$lookAheadTime) //Use a transfrom to take each start capsule and look for a matching end capsule and join by making a new capsule .transform( $startCap -> capsule($startCap.getStart(), //Get the start key for the capsule //Filter the end condition based on BatchID //Find the specific capsule by in the filtered condition using toGroup($startCap).first() //We can look for the first capsule because we only expect to find one capsule in the condition //Get the end key for the capsule using .getEnd() $endCond.filter($endCap -> $endCap.getProperty('BatchID') == $startCap.getProperty('BatchID')).toGroup($startCap).first().getEnd()) //Assign the property of the starting capsule to the new capsule .setProperty('BatchID', $startCap.getProperty('BatchID')) , $lookAheadTime)
  20. 1 point
    Use case: A piece of equipment has a start-up sequence in which it goes through different discrete states sequentially before completing the sequence and reaching steady state. When the equipment is off, the state is 0. When the equipment enters the start-up sequence it cycles through states 1-6 in the pattern "1-2-3-4-5-6". A successful start-up sequence will have all 6 states in the pattern "1-2-3-4-5-6." If a disruption occurs at any point in the start-up sequence the state number will read as state 7, thus a failed start-up sequence could have the pattern "1-7", "1-2-7", 1-2-3-7", etc. This use case describes methods to identify only the successful start-up sequences. Approach 1: If the signal for the state is numeric (e.g. with discrete numeric values of 0-7) 1. Create a new signal that is the running delta of the STATENUMBER signal. Use Seeq Formula and syntax: $statenumbersignal.runningDelta() 2. Create a new condition for all start-up sequences using value search for when the runningDelta signal just created is greater than zero. 3. Calculate the delta in your STATENUMBER signal over each start-up sequence. This value should always be equal to 6 or 7 as the sequence will either complete successfully (go to 6) or fail and end with a value of 7. Use the signal from condition tool to calculate this. 4. Create a new condition for when this delta in the STATENUMBER signal just created is equal to 6. This must be done in Seeq formula (there is a known issue in using value search for this operation) with the following syntax: $deltaInSTATENUMBERsignal.valueSearch(isEqualTo(6)) Approach 2: If the signal for the state is a string that is easily convertible to a numeric signal. This example is a string with discrete values "STAGE0", "STAGE6", etc. 1. In Seeq formula, use the replace() function with the following syntax: $StringSignalForStateNumber.replace('STATE','') 2. In a new Seeq Formula Window apply the toNumber() function to the signal created in step 1 with the following syntax: $SignalFromStep1.toNumber() - this will create a numeric signal with discrete values of 0-7. Approach 3: If the signal for the state is a string value, not easily converted to a numeric signal or if you wish to proceed using the string signal. 1. Use Value Search to identify STATE6 2. Use Value Search to identify STATE7 3. Use Composite Condition (union operator) to create a combined condition "finalStateinSequence" for the final state in sequence, either STATE6 or STATE7. 4. Use formula to create a condition for all start-up sequences (successful and failed). Syntax: $FinalStateInSequence.inverse().move(0,1h) This formula code is identifying all of the time when the final state in sequence condition is not true and extending those capsules by a short amount of time so that the final state value is contained within the "all start-up sequences" capsules. 5. Use Signal from Condition to identify the ending STATENUMBER value for each of the start-up sequences. 6. Identify your successful start-up sequences by doing a valueSearch in Formula to identify when the ending STATENUMBER is equal to STATE7. Formula syntax: $endingSTATENUMBERsignal.valueSearch(isEqualTo("STATE7"))
  21. 1 point
    Hi Chris Like Thorsten mentioned I would be careful using property transforms as this can impact everyone that wants to use this tag. I would use formula tool and then use the SetMaximumInterpolation Function to change the max interpolation to the value you are interested in.
  22. 1 point
    In reporting, users may be interested in creating a Scorecard that contains certain metric results over a variety of time periods, such as "April 2019", "Quarter 1", and "Year to Date", etc. This can be accomplished using the following steps: 1. Use Formula to create a condition that contains a capsule for each time period that you are interested in. Note that I assigned a property to each capsule; this text will be used as the column header in the scorecard: 2. Create a Condition based scorecard and add a metric for each item you are looking to calculate: 3. Finally, use the capsule property as the column headers:
  23. 1 point
    A common analytics need is to create a signal with numerical values that are based on an existing condition. Users often want to translate a condition (on/off, good data/bad data, running/down, etc.) to a numerical value to be used in calculations. For example, a user may want to multiply a process signal by a 0/1 value based on when the process is down/running. This technique can also be used to replicate "if" logic or "if / else" logic, where different values are returned depending on if the condition is true/false. Converting a condition to a signal value can be easily accomplished in Seeq using the Formula Tool and the splice function. Here is an example where we convert a condition to a signal of 0s and 1s: 1. Use the Value Search Tool to create a HOT condition for time periods when the Temperature signal is > 90 degrees F: 2. Use the Formula Tool to convert the HOT condition to a 1 (when condition is true) and a 0 (when condition is false): 3. View the results in the trend. The new signal in lane 2 has a value of 1 when the HOT condition is true. Otherwise the signal is 0. Additional Information Using Conditions and the Splice Function to Replace If Statements
  24. 1 point
    Hi Thorsten- In the first screenshot, the area of each box is actually the same, even though some boxes have different dimensions. As you observed, the size of your display impacts how the boxes are drawn. To adjust the box sizes via the API, please use the following steps: 1. On your Seeq installation, open the workbook that contains the Treemap and navigate to the API: 2. To get the ID of the asset that you would like to resize: a. Navigate to GET Assets b. Adjust the "limit" to 200 and click "Try it out!" c. In the Response Body, locate the asset to resize and copy the "id": 3. To resize the asset: a. Navigate to POST Item Properties b. Paste the asset ID into the "id" field. Use the following syntax in the "Body" field. [ { "unitOfMeasure": "", "name": "size", "value": 10 } ] The following screenshot shows a size 10, but this number may be adjusted. c. Click "Try it out!" 4. Navigate back to the Treemap and refresh the browser. The Treemap now reflects the adjusted size: Please let me know if you have any additional questions. Thanks, Lindsey
  25. 1 point
    The alternative to setUnits is convertUnits. The former just adds overrides the current value with the new unit, the latter applies the math needed to the existing values. For your case you should probably use ($a/($b+$c)).convertUnits('%')
  26. 1 point
    FAQ: All of my tag names are complicated combinations of letters and numbers. Is there a way that I could save my tags with useful names to use in later analyses without using the "available outside this analysis" check box? Solution: One popular way to do this is to create a dummy analysis where all you do is create aliases for your frequently used signals. Then, when you want to do an analysis using these tags, you can duplicate your dummy analysis, and begin a new analysis with all of your tags already having useful names. To create your new signal, open a Seeq Formula window and change the title to the alias that you want to give your particular tag. Then set the value of this new signal equal to the existing signal. See screenshot attached for an example using Seeq Formula to create an alias of "South Bridge-wall Temperature" for the tag-name "RK.HFGY_36_R901.PV".
  27. 1 point
    Hi Ilse Thorsten is correct about the Tree File Connector which will help build an asset structure. Depending on how big your analysis is you can duplicate the formulas you have done in the new worksheet and then update the signals they are based on. You can do this by clicking the i next to the signal or condition you want to copy: Then you will click duplicate: Then you will get a new signal or condition built off of the one you copied that you can rename and put the new signals you want to reference in. Morgan
  28. 1 point
    You can create more specialized periodic conditions using the "periods()" function in the formula tool. For example "periods(1min)" will give you one capsule every minute. That condition can then be used in the signal from condition tool. The periods function can also create overlapping or gapped capsules. For example, if you wanted to compare your actual signal against 5 minutes of data but do it every minute, you'd use "periods(5min, 1min)". (Then you'd probably want to align your signal from condition on the middle of the capsules)
  29. 1 point
    Hi Kevin Thanks for providing additional details. Here are some steps that can be used to create a bar graph: 1. Use Formula to create a condition around "now". Here I've created a condition that has 1 capsule which is always the past 3 hours: Note that the "now()" operator is new as of R21.0.41. 2. Use Signal from Condition to create a signal that identifies the Value at End of the input signal in the Now Condition. Here I've created 3 new signals for the Value at End of the Area A, Area B and Area C temperature signals. For the Area A temperature signal, I select to place the timestamp at the start of the capsule, middle for Area B, and end for Area C. This ensures that the data points do not overlap each other. Alternatively, you can adjust the timestamp of the data points in Formula, as well. 3. Use the Customize Menu to display the data points as bars: 4. Finally, combine the signals into a single lane for easier comparison: Be sure to enable Auto Update so the Workbench Analysis is updated with the latest information as new data is available. Please let me know if these steps work for you. Thanks, Lindsey
  30. 1 point
    FAQ: I've calculated a scorecard metric that I want to use in a calculation of a condition. While the scorecard metric is visible in trend view, it is not provided as a signal choice in the drop-downs on the tools or in the Seeq formula window. Can my scorecard metric be used in calculations of other signals/conditions? Answer: In the versions of Seeq currently available (R21.0.41 or earlier), the scorecard metric tool does not actually create a signal despite being able to be viewed in trend view. The signal from condition tool requires the same input arguments and produces the same outputs, but as a signal rather than a metric, which can then be used in the calculation of further signals and conditions using Seeq tools or Seeq formula. If there is a desire to use the calculated parameter (via either scorecard metric or signal from condition) in further calculations AND in view it in a scorecard, we recommend first using signal from condition to do the calculation of the parameter, then referencing your signal from condition in the scorecard metric tool (without actually calculating the metric).
  31. 1 point
    Issues with different devices can lead to shutdowns and failures. In this example we want to monitor the duration of each operation mode of an input signal. This example can be used to monitor all the conditions that can lead to inefficient device performance. In order to monitor all operation modes we need to, 1. Create all the modes using Value Search Tool. a. StartUp (input < 75) b. ShutDown (input > 95) c. SteadyState (75 < input < 95) 2. Create a continuous condition called “Mode” comprising all three (startup, steady state, shutdown), and assign a property to each capsule to identify the mode. for more information please look at the following link: Set property to a capsule $ShutDown = $Shutdown.setProperty("Mode", "ShutDown") $StartUp = $Start.setProperty("Mode", "StartUp") $steady = $Steady.setProperty("Mode", "Steady") combineWIth($StartUp, $steady, $ShutDown) 3. Finally, calculate the total time per mode using Histogram Tool. For more information on Histogram Tool please see the following link: Histogram Tool
  32. 1 point
    Rolling averages are frequently used in Seeq to smooth signals. Calculating a rolling average requires creating a Periodic Condition and then applying the Signal from Condition tool to aggregate the signal of interest over the bounding periodic condition. Sometimes, we want to calculate a rolling statistic over a time frame not listed in the Periodic Condition tool (anything < hours). To create a periodic condition for periods of time not offered in the tool, the Seeq formula tool can be used with the periods() function. For example, a 15 minute periodic condition can be created by entering "periods(15 min)" into the Seeq formula tool.
  33. 1 point
    Curious George- There are a couple of ways that you can get this information. Depending how you would like to view / use the information, the following methods may be used: 1. The easiest way to get this information is to add the Duration to the Capsule Pane display: This allows you to quickly view the duration of each of your capsules. 2. If you would like to use the capsule duration in additional calculations or have the capsule duration's trended over time, the Signal from Condition tool may be used to create a new signal that reports the duration of each capsule in the condition: 3. A third option, if you would like the capsule durations presented in a table, is to use Scorecard. First, navigate to Scorecard: Then, add a Condition based metric: Please let me know if you have any additional questions. Thanks, Lindsey
This leaderboard is set to Los Angeles/GMT-07:00
×
×
  • Create New...