How to use Pulse to performance optimize TM1

Over the years TM1 application expands. The common lifetime of TM1 in a company will start by a Profit&Loss and Balance sheet project, then expand to HR application, Cost allocation, Sales etc.. as the size and complexity of systems grow you need the right tools to understand your model, track what is happening and then diagnose issues as they arise.

View live information from your browser, no installs required and all users can access the content. Similar to TM1 top you can Cancel threads and disconnect users by providing valid credentials.

Because you can’t always have a look at the monitor, you can set up event notifications.
Proactively managing your TM1 server up until now has been very difficult if not impossible. Pulse for TM1 allows you to define alerts according to your own thresholds and requirements. Notifications can be delivered in a number of ways:

There are a number of alerts available, each can be defined to trigger according to day and time parameters as well as a threshold value. All types of alerts are defined in the following link.

Best practice is often talked about but rarely it is followed and enforced, developers all have their own ideas on how a system should be built. Pulse for TM1 allows you to validate your best practice rules against your model. This allows you to ensure consistency in design. A consistent system is one that is easy to maintain, saving countless hours and shortening the time taken for new developers to understand how it all fits together.
Shipped as part of Pulse there are 40 best practice rules that have been formulated with decade’s worth of collective TM1 consulting experience. You can use these straight out of the box on your own models or develop your own to fit your particular needs.

One of the main reasons for investing in TM1 and Cognos Express is to take advantage of its server side processing and remove the silos of information that reside in Excel Workbooks. After implementation it is usual for users to develop their own TM1 spreadsheets that may or may not be designed according to best practices.
Pulse for TM1 when combined with the Extend Toolbar allows you to log and report on what TM1 enabled spreadsheets are in use across your organisation. This is especially important to administrators and report analysts who can now know how often their reports are being used and the rate at which users are creating reports.
This same information can be used to analyse your user base and assess what type of training is required and who needs it. The client logging feature also logs whenever a Slice or Active Form is created from a cube view giving you the ability to determine who are the real “Power Users” within your organisation.
Pulse logs the follow information:
•    What action the user has taken: Opened a file, sliced from the cube viewer or created an Active Form from the cube viewer.
•    When they open or closed a file.
•    The user’s windows login.
•    The name of the computer.
•    The user’s TM1 login.
•    What cubes are being used in each sheet of the worksheet.
•    History of workbooks: ancestry and children (save as or file system copy) 

Automatically document each of your TM1 models and see the relationships within your model, as you never have before. These relationships are laid out in a graphical way that so you can navigate your way down to individual relationships and even lines of code.
Furthermore you can augment the information extracted directly from your model by Pulse with your own descriptions and commentary.
All of this content can then be quickly extracted from Pulse as a PDF to create Technical Documentation. 

Analyze your server performance

Pulse stores a plethora of information about your server, all information that can be viewed live or is summarized and stored in the internal database for later use and reporting. You can use this data to review your system and analyse performance on a week to week basis or by comparing and contrasting it over years. This gives you a complete insight into how your system has developed and evolved over time.

     Concurrent Usage Over Time
     Usage By User Type

The type of reports and information available is as follows:
•    Alerts: When and what alerts are being generated.
•    CPU: The use of CPU by the server and TM1 instances.
•    Memory: The level of memory use in megabytes.
•    Operations: A summary of information for any long running processes or threads. This can be TI processes, cube views or Excel workbook queries.
•    Sessions: Who and when users are logged into the system. Each user session is logged including how often they were running queries, waiting for locks or updating data.
•    Start-up: The amount of time for each TM1 instance to restart. This information is also used to estimate future server start up times. Persistent feeders and cube file size is also stored.
•    User Wait Time: When and how often people are waiting, a snapshot of the TM1Top log is stored when the maximum value is reached.
•    Users Waiting: How many users are waiting and when.
•    Concurrent Usage: The number of users logged into the system. Report on when your busy periods are and determine when you can access the system for maintenance or upgrades.