RFC Team Approval-IT Change Management Software

Posted: June 29, 2010 6:56 PM
Categories: Insights For CIOs & IT Directors , Software as a Service-SaaS, Help Desk Best Practices

RFC Team Approval -Giva eChangeManager

In this example, according to the business rules setup, 3 approvers are required for an RFC to be approved. Dave Swing, Jim King and Bart Barthold all gave their approval on the same day. They are all users with approval rights, but not Change Managers or Emergency Committee members. The “Team Approval Date” is the date that the last person approves the RFC.

To learn more, view the eChangeManager demo!

Client Success

50% reduction in time to deploy Giva's change, incident, problem, asset management and knowledgebase modules
60% reduction in the 5 year Total Cost of Ownership (TCO)
Saved at least 1 FTE due to lower ongoing administration
Saved 1 week per month due to easy to use reports

Learn More Download PDF

Increased to 90% achievement in meeting service level agreements
70% reduction in generating reports and admin; eliminated 35 hours/month
50% faster to create/assign a service request
60% increase in information captured during the initial phone call
50% increase in the number of service requests created due to intuitive design

Learn More Download PDF

80% increase in productivity by using Giva's dashboards and reports
60% increase in meeting service level agreements
45% increase in the number of the calls logged due to Giva's intuitiveness and ease of use
50% increase in productivity by using Giva's integrated custom forms

Learn More Download PDF