Selmane

Jaswin, I guess you have 3 capsules back-to-back in your trend so I would join them or ignore the gaps between them to have a single horizontal bar. Can you share here how you created the yellow capsules? I would also recommend you set up an office hours session where you will be able to share your screen. Thanks, --Selmane

What did you use for the last parameter "Select where to place the timestamp of the summary statistic"? Duration choice should give you the below result. Also, make sure that you don't have very small capsules before nd after the big ones. Check your capsules pane.

Hello Jaswin, You can use the "Signal from Condition" tool to get this sample. The bounding condition is actually the yellow condition in your trend. let me know if you can get what you want from it.

@Kyle Lee you can also duplicate the Workbook to have it in another one but this will be a copy. So any update in the new workbook won't be reflected in the original one and vice versa. As @Kin How shared, the best thing to do here is to create an Asset Tree. Thanks

Hello Alvio, Do you have a condition in the Asset Group representing the Batch or Lot Number? If not, I recommend creating it with the Lot Number as capsule property. I think what you are trying to do is straightforward in Seeq but not easy to troubleshoot in this forum. I recommend creating a support ticket here or booking an office hours slot with aSeeq Analytics Engineer here. If you are not able to do it, then please share some screenshots for your asset group, the conditions you have and the lot number signal. Thanks, --Selmane

Hello Aymen, You can use the Join option of the composite condition and by excluding the second condition to achieve this. Let me know if this works for you. --Selmane

Hello Brighton, Spy.pull() is the only method available in Seeq Data Lab to retrieve data from the data source. Speed of data retrieval is affected by multiple factors: The number of time series you are pulling The time range you are pulling data for The type of data source you are using For the tests you are doing, can you be more precise on the data source and the time range you are pulling data for? Thanks, --Selmane

Hello, Be careful to two things: When you create the condition, make sure you name your property correctly: $signal.toCondition('Grade Code') Then pay attention to single and double quotes: $condition.keep('Grade Code', isEqualTo('Grade 106')) Let me know if this helpful.

Hello Ricardo, Are you sure the second condition has capsules in the desired timeframe? If yes, then please open a support ticket in https://seeq.atlassian.net/servicedesk/customer/portal/3 and we will be able to dig dipper on this matter with our support team. Thanks, --Selmane

@ARiebel you should be able to do it in R58, I was able to reproduce it (see below screenshot): Are you clicking on Condition table button as shown below?

Hello Swapnil, I think some screenshots would be interesting here. Question for you: which tool/formula are you using to get the signal value during that timestamp? Is it working well in workbench? Is the problem only when you export to Excel? Can you share a screenshot of the Excel document? For more in-depth support, I suggest you create a support ticket on https://support.seeq.com or attend an Office Hours session. Thanks, --Selmane

Hello Dayyan, Please consider using the Periods formula instead of months. The syntax for it could be something like: periods(6months,6months, '2017-01-01T00:00:00','CET') Change CET by the timezone you are in. To analyze the fluctuations, it would be good to share a graph and see what this looks like to give you an advice. I hope this helps, --Selmane

You can also convert your signal interpolation to step using the tostep() formula: $signal.tostep(1d) with 1 day being the max interpolation for the signal. You can make it longer or shorter according to the frequency of your signal. The step-interpolated signals can be exported to OData before the enhancement shared by Kin How above.

Hello David, On my previous comment, the export will help you get the signals and conditions in Power BI and then you will need to recreate your table in Power BI. I have found a feature request to get exactly what you want: getting the table directly to Power BI. Please open a Seeq support ticket so we can link it to the development request and give you updates when we progress on it. --Selmane

Hello Mohammad, Was this working before? Are you able to search for the data but not able to pull? The error message (502) Bad Gateway - Connection to 'OSIsoft AF: AF PROD' is offline indicates that Seeq Data Lab is unable to establish a connection to the specified OSIsoft AF (Asset Framework) server, which in this case is named 'AF PROD'. This could be due to various reasons such as network issues, the server being down, or configuration problems with the connection settings in Seeq. Here are some steps you can take to troubleshoot and resolve the issue: Check Network Connectivity: Ensure that the Seeq server has network access to the OSIsoft AF server. This might involve checking firewalls, routing, and whether the OSIsoft AF server is reachable from the Seeq server. Verify OSIsoft AF Server Status: Make sure that the OSIsoft AF server is running and accessible. You can try to connect to the AF server using other tools or from a different machine to confirm that it is operational. Review Connection Settings: In Seeq, check the connection settings for the OSIsoft AF server to ensure that they are correct. This includes the server address, credentials, and any other relevant configuration details. Check Seeq Server Logs: Review the logs on the Seeq server for any additional information about the connection failure. The logs may provide more detailed error messages that can help identify the root cause. Restart Services: If the connection settings are correct and there are no network issues, try restarting the Seeq services and the OSIsoft AF server to see if this resolves the connection problem. Contact Support: If you are unable to resolve the issue, contact Seeq support for further assistance. They can help diagnose the problem and provide guidance on how to fix it. Remember to perform these troubleshooting steps in a systematic manner, checking the simplest and most likely causes first before moving on to more complex investigations. I hope this is helpful, --Selmane