12 Key Areas and Metrics
Performance OPtimization
The Reveille Difference
ECM Performance Optimization:
12 Key Areas and Metrics
| KEY AREA AND METRIC | WITH REVEILLE | WITHOUT REVEILLE |
|---|---|---|
| ECM Application Availability | Early warning of developing issues. Issue notifications, both internal and to cloud provider. Objective reports on content services application availability from user perspective. | User complaints about application outages. Reactive not proactive. Informal evidence to explain issue to cloud provider. |
| ECM Application Response Time | Early warning of developing response time issues. Notifications, both internal and to cloud provider. Response time dashboards. Objective reports on system response times. | User complaints about system response times. Reactive not proactive. Informal evidence to explain issues to cloud provider. Minimal evidence for application selection |
| ECM Resource Consumption | Performance base lines available. Performance Reports. Performance Dashboards Available. Information available to define Cloud System Requirements | No base line for application and system performance. Minimal performance reports focused on content services. Over designing requirements for new cloud system |
| User License Consumption | Understand system use, user volumes, access times, types of activity etc. Reports on system Usage. Right size user licensing needs. | Little understanding of system usage. No ability to track usage throughout the day. Point in time manual review and analysis of audit logs and app server logs. |
| User Adoption | Understand system use, user volumes, access times, types of activity, search details etc. Reports on application adoption and system usage. Understand application uptake and prioritize cloud migration. | Little understanding of system usage Minimal ability to track application usage throughout the day Use ad hoc feedback and best guess to infer application use |
| User Device Types | Reveille allows tracking of browser type Reveille allows tracking of device type | Details on security risk of using outdated browsers Understanding of device types accessing ECM applications for better device support planning and investment |
| Capture Operations | Early warning of capture issues Capture process visibility via Dashboard Batch Process Reporting Automated capture exception recovery | User complaints about content not available for document driven tasks No knowledge when content is not released to the cloud Reactive to batch processing issues Manual capture process exception recovery |
| Repository Operations | Early warning of performance issues System performance and usage dashboards with threshold notifications Reports on system performance and usage | User complaints about system performance Lack of information on content search, content processing and retrieval patterns Behind the curve on issue response |
| Application Integrations | Early warning of performance issues System performance and usage dashboards Reports on system performance and usage | User complaints about system performance Lack of information on content processing and storage Behind the curve on issue response |
| Suspicious Content Access | Understand system is use, user volumes, access times, types of activity Flag unusual behavior Raise event/case in security endpoint apps or SIEM | Little understanding of system usage patterns Unable to track content security breaches No ability to track user transaction patterns throughout the day |
| API Operations | Understand system use, user volumes, access times, types of activity Reports on API usage Audit and Charge Back Report | Little understanding of system usage Little understanding of API usage Unable to objectively cross charge |