Siebel OpenUI – UPT – Usage Pattern Tracking

Sharing a very interesting and new feature added in 15.5 version. This will greatly help in designing the UI Flows. Thanks John!!

Usage Pattern Tracking

By John Bedford-Oracle

Siebel Usage Pattern Tracking, a feature introduced in 15.5 is a framework module that packs immense potential. This feature allows Siebel administrators with the ability to configure live systems to capture information on how end users are using the application without adding performance or response time overheads.

The information gathered via this feature is invaluable as it can be analyzed, sliced and diced in many different ways to extract information that can be used to improve the end user experience, lower total cost of ownership and/or personalize the application down to the smaller unit.

The feature is capable of capturing user patterns that can be analyzed to determine for e.g. the 10 most visited views in the system, number of login/logoff sessions in a period of time, how many fields are really used in an applet, top 5 views where users spend the most time, the entire set of views all users have accessed over time, what was the user doing when they hit an error and what steps were performed getting to that point, etc. The possibilities are endless.

Chart showing user login across applications


Chart showing which applications are being accessed


Chart showing the most access views in the application


Chart showing the most access views in the application


Chart showing the most active events in an applet


There was a lot of excitement when Usage Pattern Tracking (UPT) was announced and we think this is a great new feature for our customers to start to utilize.

Some Additional information :

When UPT module receives an event to track, the configured RTE triggers an action. The action is based on a Business Service “Usage Pattern Service” which is written to batch the events into groups of 100 events and write them into a file. The value of 100 is the default value of System Preference UPT Max Record Count and can be changed to a maximum value of 1000.
To process the data from the files, a job should be created. Through this job, UPT Process Workflow is invoked, which triggers Business Service “Usage Pattern BG Service”. This reads the information from the .csv files and moves it to the correspondent Siebel tabels. As the files are processed by the job, they are purged in order to manage efficiently the diskspace. The information in the Siebel tables is then used to populate Usage Pattern Tracking View. 

The only recommendation that exists regarding the UPT tables is the one in Bookshelf where the following is stated:

The number of records in the S_USER_EVENT table and the S_USER_EVT_DTL table depends on the events that you configure for usage pattern tracking. It is recommended that you periodically move data from these tables. Your movement frequency depends on available memory and the level of user activity.
For reporting purposes, you can click the cogwheel icon and select the Export option to export the data from the Usage Pattern Tracking view to another application, such as Microsoft Excel.


Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Google+ photo

You are commenting using your Google+ account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )


Connecting to %s