Incomplete RFC-IT Change Management Software

Incomplete RFC-Giva eChangeManager

Change request incomplete.  When a RFC requires more documentation, the Change Manager moves the status to “PENDING” and sets the Waiting Code to a waiting reason such as “Implementation Plan, Backout Plan and/or Test Plan. Giva eChangeManager automatically notifies the implementer. Notes in the Change History field indicate that the RFC needs more work before sending the RFC to the Change Advisory Board (CAB) for discussion and approval.

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
  • 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
  • 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