| Normal Use Baselines |
|
| |
| File based workflows often rely on inefficient manual processes that contribute to disorganized file systems. As an example, business users often use email as a mean to disseminate working files to other users. By using email or other manual process instead of relying on a well-organized file system, duplicate files and version control quickly convolute appropriate file based workflows. Such problems are vastly magnified in enterprises that have one or several of the following characteristics: |
| |
| |
- Large user populations
- Generate a significant volume of file based data
- A high degree of dynamic turnover of data
|
| |
| |
| In enterprises that generate vast quantities of files, the sheer volume of data quickly becomes unmanageable and increasingly error prone from an operational perspective. In such cases, automated processes are required to identify areas of concern that require human intervention. By establishing a baseline of normal use, automated monitors can actively monitor file system use and quickly identify non-conforming user practices. Baselines can be established around a wide variety of criteria to establish normal use. When abnormal use is identified, the Corporate File Manager guides users to the acceptable options to correct the non-conforming use. |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
