Scenarios

The What

Scenarios - a new kind of smart insight - has been released to Willow App. Activate uses Willow's AI capabilities to analyze our suite of insights and identify groups of issues with a pre-analyzed and identified root cause, upstream impact and downstream impact. The output of this is a Scenario.

The Why

Scenarios dramatically reduce the number of insights users need to action. Instead of actioning, say, 64 standard insights, scenarios will combine them into a single actionable output with an identified root cause and upstream & downstream impact analysis. Activate has pre-analyzed the 64 standard insights and determined that their issues are related to the root of the scenario, and thus they can be tackled as one.

This will reduce insight overwhelm and drive users to action and savings faster and more efficiently.

What's Changed

Main Page

On Insights, there now exist 3 tabs: All Insights, Scenarios and Standard.

All Insights contains both your standard and scenario insights. You may expand the Scenario rows to see the standard insights analyzed within the scenario. The table is sortable, filterable and has customizable columns. The KPIs for Needs Action, In Progress, Successfully Actioned and Unsuccessfully Actioned count scenarios and standard insights not included in scenarios. Therefore, standard insights that are analyzed in scenarios are not included in the counts. This is because scenarios and the standard insights listed within them should be considered as one actionable object.

The Scenarios tab contains only scenarios in both card and table view. Each scenario has a unique name generated by the LLM depending on the issue it is summarizing. Scenarios have a priority, category, and resolution type visible on the card. The Grouped Insights metric on the bottom left of the card counts the number of insights analyzed in the scenario. Ticket counts appear on the bottom right of the card. The KPIs at the top of the page are only inclusive of scenarios on this tab.

Standard is the insights experience Willow has historically maintained - a list or card view of individual insights and skills with impact scores. Though, now, some standard insights may be related to Scenarios which is indicated in the Scenario column of the table view. The KPIs on the Standard tab are inclusive of all standard insights, regardless of if they're in a scenario or not.

Scenario Node

Clicking on a scenario will bring a user to the scenario node page which provides detail into the issue at hand. On the Overview tab, users will see the description of the issue as well as the upstream. & downstream impact analysis powered by Willow's Copilot. Twin details will display the primary twin or root cause asset of the issue described with its location, recent insights and tickets. Recommendations are listed in the bottom left as a sort of checklist for the user to go through in order to resolve the issue at hand. On the far right, there's a summary panel with general information related to the scenario.

In the middle, there is a graph showing a visual representation of the assets and their related insights included in the scenario.

The Insights tab shows the full view of the Insights Graph as seen on the previous page. Clicking on each node of the graph provides further detail into the asset and its insights relevant to the scenario.

The insights are also available to view in a table format by using the toggle in the upper right of the view.

The time series tab contains our large time series experience, allowing users to better navigate the multitude of points that come along with a scenario.

Lastly, the Actions tab allows users to view the actions and comments taken on the scenario.

Actioning Scenarios

There are two ways you can action a scenario. A user may use the Actions menu on the top right of the node page and selecting New Ticket. As usual, this will pre-populate the ticket with the recommendations, description, linked scenario and the analyzed insights.

Alternatively, a user may action a scenario by choosing a specific recommendation they want to action. They may do so by selecting Create Ticket on a particular recommendation. This will bring up the ticket form with the prefilled scenario info and only the selected recommendation is attached. A user may choose to add additional recommendations if they wish. After saving the ticket, it will appear against the recommendations it's attached to.

All actions taken on a scenario will appear in the Actions tab in the left panel with the listed recommendations on each ticket. In the middle panel, users may leave comments on the scenario for reference or collaboration with other team members.

Scenarios and Standard Insights can have multiple actions taken on them, meaning users can create multiple tickets to address the scenario and the standard insights analyzed within them.

Actioning Standard Insights

Nothing has changed in the way of actioning Standard Insights. This experience has been maintained for consistency of the workflow.