Morgan Bowling

Tom, I believe if you share the read only link with them instead of the url in the address bar you should get the behavior you were hoping for. If I am not understanding please elaborate. Morgan

Hi Tom Thanks for reaching out. Instead of sending the link in the address bar, if you click the "Get Link" button in the right hand corner. You can send your colleagues a view only link to the workbook as seen in the picture below. This should assist with the question you are asking. If not, please let me know.

Hi Aleksander I would recommend you open a support ticket at Support@seeq.com or our portal to get assistance from our support team. Morgan

Hi Chad, Thanks for reaching out. The Analytics Engineer for your account will reach out to you shortly via email! Morgan

In versions R22.0.48.00 and later users now have coloring options available to them in capsule time. This simplifies the first section of this solution where coloring by condition. For more information on the new capabilities visit our Knowledge Base

For the second part of your question. You will first need a capsule that captures the time period you are interested in. We usually recommend a Weekly Periodic Condition. Once you have the weekly periodic condition you have two options: Signal from Condition: use this tool to count the number of times the conditions are true each week. You then can use the 'i' in the details pane to get to item properties. At the bottom you can duplicate the first signal from condition and do another one that switches out the count statistic for the total duration statistic. You will need to do this for each of your items. Scorecard Metric: Use this option if you want a table view. You will follow similar options to generate the scorecard. In this case we will use a conditional scorecard. You will repeat the same procedure for duplicating using the i by item properties and switching the statistic from count to total duration. The skills you have asked for here are covered in our Interactive Training which you may want to visit here -- https://www.seeq.com/interactive-training/story.html Morgan

Hi Felix You can use Seeq's formula tool to do this. In this case I have 3 string signals (Compressor Stage for Areas A, B and C). I want to know when Area A and B are both off at the same time Area C is in Stage 1. Instead of doing the Value Search in the tool, I do it in formula. If you don't know how to do the value search in formula you can always do it in the tool and then click the 'i' by it in the details pane to get to Item Properties where you can see the formula used. Once I do my three value searches $condition1= $cs.ismatch('Off') $condition2 = $cs2.ismatch('Off') $condition3= $cs3.ismatch('Stage 1') I then do a composite condition. In this case I want to know when all three are true so I use intersection but you can always search for combining conditions to get more options. $condition1.intersect($condition2).intersect($condition3) The whole formula is below: $condition1= $cs.ismatch('Off') $condition2 = $cs2.ismatch('Off') $condition3= $cs3.ismatch('Stage 1') $condition1.intersect($condition2).intersect($condition3) This this tells me when Area A and B are both off at the same time area C is running in stage 1.

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.

Hi Marta I believe our support team has followed up with you separately. If you need anything else please let me know. Morgan

Hi Felix To this this I would recommend making an organizer topic and there you can embed your scorecard twice and it can reference two different date ranges: In this case I have embedded by scorecard 4 times and each time it is embedded (current, last shift, last day, mtd) has a different date range applied to it: Let me know if this helps or if you have further questions.

Thanks Adam. Can you attach a video to this post or file a support ticket with a video of the behavior at Support@seeq.com? If not, please send me a time that works to do a screenshare for with me (morgan.bowling@seeq.com) so I can get this documented for our IT team.

Hi Adam The behavior you should be seeing is in the attached video. If I understand correctly, you aren't experiencing this behavior? Journal Link.mp4

Hi Tomasz Do you mean like the below? You can just do a formula with the value if you would like. The formula below will return a scalar. 120F If you want it to be a signal to you could do the below formula instead 120F.tosignal() Let me know if this doesn't answer your question.

Elaborating on this, If you just want to grab the first character of your string you can do $siganl.replace('/(.).*/','$1') and the second character would be $siganl.replace('/.(.).*/','$1') and so on. Morgan

Hi Milan I have sent you a separate email in order for us to connect and assist with your use case. Morgan

Hi Ali There is one last step to combine them into one signal. That is using our Forecast Splice Function as seen below. You can do this in a separate formula as seen above or combined or by updating your original formula as seen below.

Hi Adam, I understand your confusion in this area concerning the display range. I will take this feedback and work with the team to write up a Story Board on this that we will review with our development team. In the meantime, for calculations related to contracts and accounting I would recommend you use conditions made through the Periodic Condition tool. In the advanced options of periodic condition you can also select a time zone or shift to align with shift schedules. You can also generate these using the formula tool using the Periods function. Both the formula "periods(1month)" and "months()" will return you true calendar months. The same goes for "periods(1year)" and "years()". Thank you for reaching out and we appreciate the feedback. Morgan

There are times when you may need to combine two capsule series to form a single capsule series. We've seen this is batch processing where a parent batch has two or more child series, perhaps representing operations or phases. For reporting or other purposes a capsule series where each capsule starts at the beginning for a capsule and ends at the end of another capsule. In this example we have a Parent Condition, Phase 1 Condition and Final Phase Condition. Say we want to be able to actual the average time starting when Phase 1 begins and Final Phase ends. In this case we can "join" together the Phase 1 and the Final Phase using our Composite Condition Tool. You should now see that the Combined Condition starts at the beginning of Phase 1 and ends at the end of the Final Phase. Now that we have identified this period of interest we could do a variety of calculations using the Signal from Condition tool. These calculations could include average duration of the Combined condition, maximum temperature during the combined condition, etc. You may notice in the Capsules pane that the "children" didn't inherit the Batch ID of the Parent. If you want advice on how to complete this you can reference this article. --Morgan

Hi Atul In order to edit the scorecard, you can click the Pencil next to the metric in the details pane. Once you click that you will want to update the Condition it is referencing to match the other two Conditions. I have answered your question about the Organizer Topic Date Ranges on your other post: If you have any other questions please let us know.

Hi Atul Organizer Topic is very flexible to your needs as a user. If you want the last 3 days of data you could configure the date range as the below: This will provide you the last 3 days of data, offset 0 minutes in the past and can auto-update once a day. You can also configure different pieces of content in your report to have different date ranges: Below you can see I have a date range for the Last 3 Weeks as well as the Last 3 Days: In order to update your content: 1. Click on the content 2. Click the Seeq Q 3.Select which Date Range you want to be applied to your content. If you need anything else let me know. --Morgan

Hi Ali Thank you so much for reaching out. We actually did a webinar with this use case a while back and I have linked that here -- Predictive Analytics with Seeq (you are welcome to watch the whole thing but the solution overview starts ~7 minutes). That prediction was just based off of DP but you could also use other variables in your model as well. In order to get your prediction to go into the future I also suggest you take a look at the below Seeq.org post. This should get you started in the right direction. If you have more questions once you get into the details please feel free to reach out on here or email support@seeq.com Happy predicting! Morgan

Robert, you are correct. You have to export each sheet separately at this time. I can file this as a feature request and tag you in it.

In Seeq's RXX.0.44.00 and later we now offer a connector to the NOAA Weather Service. This can enable your team to perform analysis for weather-dependent processes. For more information on this connector, please visit our Knowledge Base Article -- NOAA Weather Connector

We often do calculations where we are interested in having one result if one condition is true and a second result if another condition is true. In this post we will discuss how to do this calculation in Seeq. We will create a new single signal which runs different calculations during different periods of time. This technique can be used to replicate "if" logic or "if / else" logic currently being used in excel. Example existing code from excel or other systems IF Temperature > 90 then show a result of (Temperature * 100) IF Temperature < 90F then show a result of (Temperature + 10) Step 1: Identify two modes of operation In the Tools tab identify the following conditions using the Value Search tool: Step 2: Use formula to reconstruct "if/then statement" using Seeq's Splice Tool Local Variables: Name Item Type $Temperature Temperature Signal $HighTempCondition Greater than 90 Condition Seeq Formula: $HighTempCalc = $Temperature * 100 $LowTempCalc = $Temperature + 10 $LowTempCalc.splice($HighTempCalc,$HighTempCondition) Section 1 - $HighTempCalc This is a local variable which is to be run during periods of high temperature Section 2 - $LowTempCalc This is a local variable which is to be run when NOT in periods of high temperature Final - $LowTempCalc.splice($HighTempCalc,$HighTempCondition) Combine your two series. Use the LowTempCalc series, unless you are in the High Temperature condition, in which case use the HighTempCalc Content Verified DEC2023

Overview This method will provide a simple visualization of externally determined control limits or help you accurately calculate new control limits for a signal. Using these limits we will also create a boundary and find excursions for how many times and for how long a signal deviates from the limits.These created signals can be used in follow-on analysis search for periods of abnormal system behavior. In this example we will be creating average, +3 Std Deviation and -3 Standard Deviation boundaries on a Temperature Signal. Setup Signals In the Data tab, select the following: Asset → Example → Cooling Tower 1 → Area A Signal → Temperature Option 1: Manually Define Simple Control Limits From the Tools tab, navigate to the Formula tool. The Formula can be used to easily plot simple scalar values. If you already have calculated values for the upper and lower limit just enter them in the formula editor with their units as shown in the screenshot below. Formula - Simple Upper Limit 103F Formula - Simple Lower Limit 70F Option 2: Calculate The Control Limits From the Tools tab, navigate to the Formula tool. In formula we are going to define the time period over which we want to calculate our control limits as well as the math behind those limits. Step 1 - Calculate the upper limit Variables Name Item Type $Series Temperature Signal Formula $calcPeriod = capsule("2018-01-01T00:00:00-06:00","2018-05-01T00:00:00-06:00") $tempAve = $Series.average($calcPeriod) $tempStdDev = $Series.standardDeviation($calcPeriod) $tempAve + 3*$tempStdDev Description of Code $calcPeriod → This is the time range over which we are going to calculate the average and standard deviation of our signal. The start and end time of our period must be written in ISO8601 format (Year - Month - Day "T" Hour : Minutes : Seconds . Fractional Seconds -/+ Timezone) $tempAve → Intermediate variable calculating the average of the temperature signal over our calculation period $tempStdDev → Intermediate variable calculating the standard deviation of the temperature signal over our calculation period $tempAve + 3*$tempStdDev → Example control limit calculation Step 2 - Duplicate your formula to calculate the lower limits Click the info icon in the details pane next to your calculated upper limit signal. From the info panel select duplicate to create a copy of the formula. With this copy simply edit the formula to calculate the lower limit. $calcPeriod = capsule("2018-01-01T00:00:00-06:00","2018-05-01T00:00:00-06:00") $tempAve = $Series.average($calcPeriod) $tempStdDev = $Series.standardDeviation($calcPeriod) $tempAve - 3*$tempStdDev **Alternate method number three -- if you wanted $calcperiod to actually changed based on the previous month or week of operation you could use signal from condition based off a periodic condition to achieve this solution. Step 3 - Visualize Limits as a Boundary Using the Scorecard Metric to connect the process variable and upper and lower limits. Select Temperature as your item to measure. Add threshold for your upper and lower limits. Default is to add a fixed value. By clicking on the scalar icon to the left of the green "x", you can select a signal as your threshold limit. You can change the colors of the different threshold or color only the area between the threshold as shown below. Once you click execute, you will see a new scorecard metric with the shaded area between the boundaries and the original signal. Step 4 - Create Capsules when Outside the Boundary Using the Value Search tool, create a condition for when the signal is outside the limit signals. Name your new condition, select temperature as the input signal, select <> not between, click on the scalar icon to select a signal as your limit, and use the upper and lower limit signals as your upper and lower limit, respectively. Step 5 - Create a Scorecard to Quantify How Often and How Long Boundary Excursions Occur Create a Scorecard to count how many and how long and what % of total time these excursions are occurring. Create each metric using the Scorecard Metric tool and the Count, Total Duration and Percent Duration statistics. Use a Condition Based scorecard to get weekly or monthly metrics. Step 6 - Plot how these KPIs are Changing Over Time By creating a signal which plots these KPIs over time we can quantify how our process variable is changing relative to these limits. To begin, determine how often you would like to calculate the KPI per Hour/Day/Week/Month and create a condition for those time segments using the Periodic Condition tool. In the screenshot below we are creating a weekly condition with capsules every week. Using the Signal from Condition Tool count the number of Outside Simple Boundary capsules which occur within each weekly capsule. This same methodology can be used to create signals for total duration and % duration just like in the scorecard section above. For each week the tool will create a single sample. The timestamp placement and interpolation method selections will determine how those samples are placed within the week and visualized on the chart. The scorecard metrics that you created above can also be trended over time by switching from Scorecard View to Trend View. Content Verified DEC2023