BookmarkSubscribeRSS Feed

SAS Visual Investigator and Scenario Administration

Started ‎09-29-2017 by
Modified ‎10-02-2017 by
Views 6,088

SAS Visual Investigator now has a component called Scenario Administrator. Scenario Administrator provides fraud detection authoring and surveillance capabilities to the SAS Visual Investigator product. Scenario Administrator is a data-driven tool, designed to allow users to explore their data and author surveillance strategies and decision flows to generate Alerts with the SAS Visual Investigator interface.


The illustration below from the SAS Visual Investigator 10.2: Using the Scenario Administrator guide depicts the Scenario Administrator Process. In this article, the steps that are performed within the Scenario Administrator user interface (steps 1 – 5) are reviewed. Step 6 which is performed in the SAS Visual Investigator user interface will be discussed in a future article. 






1.  Create Flow

When you create a flow, select one or more data sources.   Only external and internal entity sources can be selected.  Children entities and data setup as Transactions cannot be selected.  The Scenario Administrator uses this data during the scenario design, test, and flow run process.




The screenshot above depicts that the data source for the scenario flow is the customer table.  


  1. Design Scenarios and Scorecards

Design a scenario by completing the necessary configuration information and assigning rule(s) to trigger an alert. There are three types of scenarios you can design:


  • Record-level Scenario – allows you to surveil data by individual records in the dataset. The output is all records in the dataset.
  • Grouping Scenario – allows you to surveil data at an aggregated level for one or more columns in the data. The output is one row per unique grouping.
  • DATA Step Scenario – allows to you use SAS DATA Step code to design your scenarios thus offering you more flexibility than is offered by the user interface. The output is dependent on the code.






The screenshot above depicts a grouping scenario that looks for households with more than one address for its customer records by:

     (A) grouping the customer records by their household number

     (B) creating and address_cnt column that aggregates the customer records by address

     (C) triggering the scenario if the address_cnt is greater than 1.  



  1. Test Scenarios

Run a test of the scenario against the assigned data. This enables you to verify the effectiveness of the scenario configuration.  



  1. Review Results

Review the scenario test results and examine its associated statistical information. If necessary, fine-tune the scenario by modifying its configuration settings.  For example, you may want to modify the rule(s) that trigger the alert.







 The screenshot above depicts the test results for the households with different address grouping scenario.  The results show that 42 of 627 households had different addresses at the time this test was performed.  


If necessary, repeat steps 2 through 4 to create additional scenarios for your flow. You can also create a scorecard, which performs further processing on the event triggers that are generated by the scenarios within the flow.  Creating a scorecard provides you the flexibility to only create alerts for data that meets a certain a threshold (score).





The screenshot above depicts a scorecard for a Scenario Administrator flow.  This scorecard is based on two scenarios and its score is based on the sum of the score from those two scenarios.  When this flow is executed, if that score is greater than or equal to 100, then an alert will be triggered and displayed in SAS Visual Investigator.  



  1. Publish and Run Completed Flow

Publish and run the flow to trigger alerts in SAS Visual Investigator application.  A flow must be published and have the status of Available in order to be executed.  Published flows can also be versioned.  In addition, publishing a flow gives you a URL to run the flow outside of the SAS Scenario Administrator.





  1. Investigate, Disposition, and Triage Generated Alerts

When the flow run is complete, you can perform further review and analysis of the alerts generated in SAS Visual Investigator. For more information, refer to the Understanding Alerts section in SAS Visual Investigator: User’s Guide.  This topic will be covered in a future article.    



This article covered how to create Alerts in SAS Visual Investigator using Scenario Administrator, refer to this article by Bobbie Wagoner on how to create alerts manually in SAS Visual Investigator.  For more information on Scenarion Administration refer to the SAS Visual Investigator 10.2: Using the Scenario Administrator guide.  Note:  The SAS Visual Investigator documentation requires an access key, if you do not already have one, contact SAS Technical Support.


Hello Team,


We have a requirement for which we need your help:


The requirement is to have custom controls (visualizations like bar chart / line chart) on the landing page (home page) of SAS VI.

The said custom control should fetch data from the Alert table directly.


Can we do this in SAS VI? if yes, requesting you to share the steps.



Dipan Arya

I haven't worked with custom controls in Visual Investigator, but here is a link to the documentation on custom controls.  Hope this helps!

Thanks you very much for your information.


I was trying to open a document  but the portal is asking access key. 

can you please help me with access key?




You need to contact SAS Technical Support for access keys to documentation.

Hi All,


I am trying to create a grouping scenario in SAS VI : Scenario Administration (V 10.2.2)


The scenario is working fine but I am not able to check the option " Include triggering transactions information"


Could there be any particular reason? 

My guess is that the entity you are grouping on may not have any triggering transaction data.  However, it is best to bring up your particular scenario with Tech Support if needed.

Good day. I'm facing a problem with field and data labels when importing data from 'postgreSQL'.

I thought that file labels and data labels in VI are supposed to be entered as the comments of columns and the table respectively from the data as saved in 'PostgreSQL' automatically when importing external entities and dataset from 'PostgreSQL' into VI.

However, when I had imported data into VI in reality, the labels were entered with actual names of columns and tables not from their comments.

So I checked the structure of the dataset in SAS EG and found out that nothing was entered in the 'data set label'. I guess maybe that's why the labels were sourced from names.

So I have two questions about this problem.

1. How can I let the labels are automatically entered as comments of PostgreSQL DATA?

2. How do I check which parts VI refers to the labels and manipulate it?

@KIIMCL - Sorry I haven't worked with Visual Investigator in over 2 years.  I would suggest you post your question in this Community Forum or open a track with Tech Support.

Version history
Last update:
‎10-02-2017 12:03 PM
Updated by:



Secure your spot at the must-attend AI and analytics event of 2024: SAS Innovate 2024! Get ready for a jam-packed agenda featuring workshops, super demos, breakout sessions, roundtables, inspiring keynotes and incredible networking events.


Register by March 1 to snag the Early Bird rate of just $695! Don't miss out on this exclusive offer. 


Register now!

Free course: Data Literacy Essentials

Data Literacy is for all, even absolute beginners. Jump on board with this free e-learning  and boost your career prospects.

Get Started

Article Tags