Patrick

Hi patjdixon - You do have the ability to push images directly into an Organizer Topic. To do this, first save the image using plt's savefig method: Lab_Pred_Fig.savefig('Awesome_Chart.png') Create an Organizer Topic Object: topic = spy.workbooks.Topic({'Name': "Charts"}) Add a page to the topic object: page = topic.document('Visualizations Using Data Lab') Add the image to the page. Note the semicolon on the end suppresses the output from the cell. page.document.add_image(filename='Awesome_Chart.png', placement='end'); Publish the Topic: spy.workbooks.push(topic) If you have an existing Topic, you can use spy.workbooks.pull() to pull in the object and follow the same methodology as above. Note I included a [0] index to reference the Topic document in the pull results. topic_search=spy.workbooks.search({'ID':'DFFC7BB8-9EE3-42DD-937A-2CE2FAAAB0E8'}) topic=spy.workbooks.pull(topic_search) page = topic[0].document('Visualizations Using Data Lab')

We've received reports from some users encountering errors when following the above guide. Below are solutions to two errors users have reported: 1) NameError NameError: name 'total_time_by_reason_code' is not defined To fix this, define the dataframes first by inserting the definitions towards the beginning of the script: total_time_by_reason_code=pd.DataFrame() percent_time_by_reason_code=pd.DataFrame() cum_percent_time_by_reason_code=pd.DataFrame() 2) Type Error when trying to plot the first bar chart TypeError: value should be a 'Timedelta', 'NaT', or array of those. Got 'int' instead. To fix this, the 'Total_Time_by_Reason_Code' series can be converted to hours by adding the following line of code: total_time_by_reason_code['Total_Time_by_Reason_Code'] = total_time_by_reason_code['Total_Time_by_Reason_Code'].dt.total_seconds()/(60*60) Note the original post performs this conversion at a later time in the script. That conversion is no longer needed and should be removed:

Hi Jesse - Unfortunately moving property columns to the left/top of metric columns in tables is not yet supported. There is an open developer request for this functionality. If you would like to be notified when this functionality becomes available (and advocate for prioritization), please send us a ticket to support@seeq.com referencing developer request #27076 so we can log your ticket against that request. Thanks, Patrick

This is a continuation of the Asset Groups Part 1 post. If you are not familiar with Seeq Asset Groups, it’s recommended to read Part 1 first. This post explores how to configure calculations directly in an Asset Group. In the previous post we covered how to create a basic Asset Group from a collection of unorganized tags. By mapping these tags to an Asset as an Attribute, we can trend, swap, calculate, and visualize analytics across the configured Assets. Once an Asset Group is configured, calculations can be generated and swapped provided they are based on the signals that were configured in the Asset Group. Note that the calculations in Part 1 were not configured as a separate Attribute in the Asset Group, but rather are a dependency of the signals in the Asset Group. To illustrate, navigate to “Location 1” in the Asset Group created in Part 1 and note that while the two signals are listed, the newly created “High Temperature” condition is not a dedicated item in the Asset Group. This is because the calculation was not created in the Asset Group, but instead relies on signals (Attributes) from Assets in an Asset Group. Now let's explore how to configure calculations directly in Asset Groups. Make sure your trend/treemap view is set to Location 1. (If it is not, swap the asset to Location 1 by Navigating to “Facility Temperature Monitoring” in the Data tab and clicking the swap icon next to Location 1) 1) In the Data pane, click “Reset” and then edit the Asset Group created in Part 1. 2) Click on “Add Column” followed by “Add Calculated Item”. 3) Users are given two options for the calculation type – “Existing Seeq Item” and “Build Formula from scratch”. Select “Existing Seeq Item”: 4) A search modal will appear. Under “Recently Accessed” you should see the previously created “High Temperature” condition. You can also search for it by name. Once located, select it, and click “Next” to copy the formula syntax directly into the Asset Group. 5) Seeq will automatically map the associated column(s) to the variable(s) in the formula syntax. Give the Column (Attribute) a name and click “Add Calculated Item”. 6) Note the new column that was added with an f(x) symbol to denote that it’s a formula rather than a mapped tag. The formula can be viewed and edited by clicking on the f(x) icon. Click “Save” to save the Asset Group. 7) In the Data pane, navigate to Location 1 in the Asset Group – note the newly created condition is now listed directly in the Asset Group. Creating the condition directly in the Asset Group offers two main benefits: a. Items can be easily discovered, added, and removed from trends by navigating through the Asset Group b. Each Asset gets its own version of the item, meaning it can be modified to be different for each individual Asset. More on this next. 8 ) Add the newly created condition (“High Temperature AG Condition”) to the details pane and remove the previous “High Temperature” condition. If you are still in Treemap view, re-assign the priority color for the new condition. 9) Click the edit icon to edit the High Temperature AG Condition for Location 1, then change the limit from 100 to 110, and click “Execute”. This will update the condition criteria for Location 1. Location 2 & 3 will retain the previous limit of 100. 10) To verify, Asset Swap to Location 2 via the Data tab and edit “High Temperature AG Condition”. Notice the Formula for Location 2 still retains the original limit of 100. 11) Individual Formula modifications can also be done directly in the Asset Group. Let’s edit the Asset Group via the Data pane by clicking on the “Edit” icon. 12) Click on the f(x) icon for Location 1 & notice the limit of 110 configured earlier. 13) Close the dialog box click the f(x) for Location 2. Note the limit is set to 100. Let’s change it to 90 and click “Save”. This will change the limit for Location 2. Location 1&3 will remain unaffected, which you can verify by clicking the respective f(x) button for those locations. 14) Asset Group calculations can also be added without referencing a pre-existing item. Seeq refers to this as building a Formula from scratch. To do so, click on “Add Column -> Add Calculated Item”. This time, select “Build Formula from scratch” from the modal. 15) Let’s create a Low Temperature Condition that will trigger if the Temperature is less than 40 deg F. Click the “Add Calculated Item” to add it to the Asset Group. 16) Save the Asset Group and navigate to the Asset Group in the Data pane to verify the new condition has been added. 17) (Optional – Seeq version R55 and later) Edit the Asset Group to add additional Assets which will automatically generate the same analysis for the added source tags. You can rename the newly added assets and map underlying tags associated with the other Assets. Once assets are named and tags mapped, save the updated Asset Group. The additional Assets will be displayed in the Asset Group and can be trended, swapped, and displayed the same way.

Have you ever wanted to scale calculations in Seeq across different assets without having to delve into external systems or write code to generate asset structures? Is your process data historian a giant pool of tags which you need to have organized and named in a human readable format? Do you want to take advantage of Seeq features such as Asset Swapping and Treemaps, but do not have an existing Asset structure to leverage? If the answer is yes, Asset Groups can help! Beginning in Seeq version R52 Asset Groups were added to configure collections of items such as Equipment, Operating Lines, KPIs, etc via a simple point-and-click tool. Users can leverage Asset Groups to easily organize and scale their analyses directly in Workbench, as well as apply Seeq Asset-centric tools such as Treemaps and Tables across Assets. What is an Asset Group? An Asset Group is a collection of assets (listed in rows) and associated parameters called “Attributes” (listed in columns). If your assets share common parameters, Asset Groups can be a great way to organize and scale analyses instead of re-creating each analysis separately. Assets can be anything users want them to be. It could be a piece of equipment, geographical region, business unit, KPI, etc. Asset Groups serve to organize and map associated parameters (Attributes) for each Asset in the group. Each Asset can have one or several Attributes mapped to it. Attributes are parameters that are common to all the assets and are mapped to tags from one or many data sources. Examples of Asset/Attribute combinations include: Asset Attribute(s) Pump Suction Pressure, Discharge Pressure, Flow, Curve ID, Specific Gravity Heat Exchanger Cold Inlet T, Cold Outlet T, Hot Inlet T, Hot Outlet T, Surface Area Production Line Active Alarms, Widgets per Hour, % of time in Spec It’s very important to configure the name of the common Attribute to be the same for all Assets, even if the underlying tag or datasource is not. Using standard nomenclature for Attributes (Columns) enables Seeq to later compare and seamlessly “swap” between assets without having to worry about the underlying tag name or calculation. Do This: Do Not Do This: How to Configure Asset Groups in Seeq Let’s create an Asset Group to organize a few process tags from different locations. While Asset Groups support pre-existing data tree structures (such as OSI PI Asset Framework), the following example will assume the tags to not be structured and added manually from a pool of existing process tags. NOTE: Asset Groups require an Asset Group license. For versions prior to R54, they also have to be enabled in the Seeq Administrator Configuration page. Contact your Seeq Administrator for details. 1) In the “Data” tab, create a new Asset Group: 2) Specify Asset Group name and add Assets You can rename the assets by clicking on the respective name in the first column. In this case, we'll define Locations 1-3. 3) Map the source tags a. Rename “Column 1” by clicking on the text and entering a new name b. Click on the (+) icon to bring up the search window and add the tag corresponding to each asset. You can use wildcards and/or regular expressions to narrow your search. c. Repeat mapping of the tags for the other assets until there’s a green checkmark in each row d. Additional source tags can be used by clicking on “Add Column” button in the toolbar In this case, we will add a column for Relative Humidity and map a tag for each of the Locations 4) Save the Asset Group 5) Trend using the newly created Asset Group The newly created Asset Group will now be available in the Data pane and can be used for navigation and trending a. Navigate to “Location 1” and add the items to the display pane by clicking on them. You can also change the display range to 7 days to show a bit more data b. Notice the Assets Column now listed in the Details pane showing from which Asset the Signal originates We can also add the Asset Path to the Display pane by clicking on Labels and checking the desired display configuration settings (Name, Unit of Measure, etc). c. Swap to Location 2 (or 3) using the Asset Swapping functionality. In the Data tab, navigate up one level in the Asset Group, then click the Swap icon ( ) to swap the display items from a different location . Notice how Seeq will automatically swap the display items 6) Create a “High Temperature” Condition Calculations configured from Asset Group Items will “follow” that asset, which can help in scaling analyses. Let’s create a “High Temperature” condition. a. Using “Tools -> Identify -> Value Search” create a condition when the Temperature exceeds 100 b. Click “Execute” to generate the Condition c. Notice the condition has been generated and is automatically affiliated with the Asset from which the Signals were selected d. Swap to a different Asset and notice the “High Temperature” Condition will swap using the same condition criteria but with the signals from the swapped Asset Note: Calculations can also be configured in the Asset Group directly, which can be advantageous if different condition criteria need to be defined for each asset. This topic will be covered in Part 2 of this series. 7) Create a Treemap Asset Groups enables users to combine monitoring across assets using Seeq’s Treemap functionality. a. Set up a Treemap for the Assets in the Group by switching to the Treemap view in the Seeq Workbench toolbar. b. Click on the color picker for the “High Temperature” condition to select a color to display when that condition is active in the given time range. (if you have more than one Condition in the Details pane, repeat this step for each Condition) c. A Treemap is generated for each Asset in the Asset Group. Signal statistics can optionally be added by configuring the “Statistics” field in the toolbar. Your tree map may differ depending on the source signal and time range selected. The tree map will change color if the configured Condition triggers during the time period selected. This covers the basics for Asset Groups. Please check out Part 2 on how to configure calculations in Asset Groups and add them directly to the Hierarchy.

Hi John - this stems from a change in tzlocal 3.x. https://github.com/regebro/tzlocal/issues/109 It is not affecting Seeq servers as they are still on 2.x. A workaround is to enforce tzlocal==2.0 on your local environment until this is fixed. We are actively working on getting this addressed on the Seeq side.

Excellent tweak - that makes sense!

Hi Yassine - Below is one way to approach this problem: Q1: Refer to the below linked article on how to create a running count of capsules. For your use case, start by creating a Yearly Periodic Condition in your time zone of choice. Next, create a signal with a set sample rate (I picked 1 day in this case, but you can make it shorter): Then create a signal from condition to count each Maintenance Interval using the average of the signal during the maintenance capsule (which will be 1, so effectively, you're counting a single instance for each maintenance interval): Finally, create a running sum of the capsules over the yearly period w/ max interpolation of 1 year: This will result in a step signal with a continuing count of maintenance intervention capsules: Q2: To perform your yearly MTBF calculation, you can create a signal for your current running hours and start of year running hours by using the Max and Min Aggregation in Signal to condition: With those signals available, Yearly MTBF can be calculated using Formula: