BiLog: Uniqueness...Report Security Best Practices

Body

Likewise, your Version 7 users are similar in that they use Maximo, but they are each unique individuals with a broad range of skills sets and job requirements.  Because of this diversity, you should carefully evaluate report security – and which users have access to report execution and creation.   This can help you prevent unnecessary, costly performance errors of run-away queries from users who are not trained or skilled in ad hoc report creation.
When reviewing your Maximo users varying skill sets and job requirements, they can be placed into different reporting categories including -  

1. Non Report Users:   Users who utilize the system for viewing data, querying or status input only.  They either do not require the ability to execute reports for their job, or they require a very structured functionality process, which does not include report execution.
   
2. Individual Report Users:  Users with specific job requirements, requiring limited access to a small set of reports.

3. Application Report Users:  Users with a broader range of job requirements, and who work extensively in a specific set of Maximo applications.

4. Super Report Users: Users whose primary focus is on analyzing data to improve business processes, or to provide data to supervisors/managers.  These users are very familiar with the Maximo database and a variety of software tools.


Report best practices include granting each of these groups of users varying levels of report security as shown to the left.  This insures they have the functionality required to perform their job, while also insuring they are not executing actions which could negatively impact system performance or other users.  
 
For example, the ‘Individual Report Users’ who has very specific job requirements, and hence limited access to a small number of applications within Maximo – would only require access to a small number of reports.  Therefore these users should not be granted ‘All Report Security Access’.  Instead, they should only be granted security access to run a small, selected number of reports, and should not be granted access to create QBR reports. 



For additional details on the varying levels of report security at the Individual, Application and All Reports level, reference either the V75   or V71 Report Feature guides.  For additional details on QBR, Ad Hoc Reporting, reference their version specific guides here: V75 QBR Guide,   V7116+ QBR Guide or the V71 QBR Guide

Also, for details on Setting Report Object Structure Security, which is the basis of QBR reporting, click here .   For additional reporting best practices on data analysis, click here