Orca picks up where Cherwell leaves off for full change request automation including:
Routine Configuration Changes
Here’s how Orca’s bi-directional integration with Cherwell works:
Orca is constantly on the lookout for configuration drift or compliance issues. When a compliance or drift issue is found, Orca automatically creates a change request in Cherwell – identifying within the implementation plan the set of configuration changes necessary to bring the issue out of drift or back into compliance. After the change request has been approved, Orca takes over the ticket and performs the execution of the implementation plan. Orca updates the ticket details and status through to completion – ultimately identifying if the execution of the change request was successful or unsuccessful and then closing the ticket.
Video: Automate Change Requests in Cherwell with Orca
Click lower right icon to expand view
Did you know?
Cherwell integration can be turned on for
Or entire environments
For example, you may not want Cherwell change requests for Development servers, but you definitely want them for Production. A perfect job for Orca.
In summary, Orca manages and integrates everything from “Opening” through “Completion” of a Cherwell Change Request.
Without Orca’s Cherwell integration,
You spend time waiting to…
Triage the incoming ticket queue
Determine the correct ticket assignment
Start the approval workflow
Determine the work needed to complete the ticket
Determine the responsible team(s) to fix the issue
Either 1) manually fix the issue, or 2) use a point tool to fix the issue
Update the ticket once they’ve made the appropriate change
With Orca’s Cherwell integration,
Orca has already automatically…
Identified configuration drift and/or compliance issues
Kicked off an automated job to fix the issue
Created the ticket in Cherwell and workflowed any required approvals
Fixed the problem
Updated the ticket with the proper details and completed the ticket