What does orchestration really get me?

[timhorn]

Ever since I started working in ServiceNow, our instances have always had an orchestration license, but I never really understood why (aside from the fact that someone sold it to us).   All of the real orchestration (integrating with external systems) has been done using custom SOAP/REST web services that we developed ourselves.   Is there a reason we need to keep the orchestration license?   I know this might sound stupid, but if we cancel orchestration will ServiceNow look at our use of web services and say "hey - you're really doing orchestration, and you can't do that without an orchestration license"?   I just don't want to make the recommendation to cancel it and wind up with egg on my face.   Also, is there something else it gives us that I haven't thought about - like maybe some kind of super-duper built-in orchestration health/usage/reporting interface?   Any thoughts would be appreciated.   Thanks.

[gauravchoudhury]

Hi Tim,

Orchestration automates simple or complex multi-system tasks on remote servers that are normally done manually. This automation of work saves time, removes repetitive tasks and reduces human error.

An Orchestration process can cross all management disciplines and interact with all types of infrastructure elements, such as applications, databases, and hardware. Orchestration combines the ServiceNow graphical workflow with the MID Server to run Orchestration-specific workflow activities.

It is an extension of a workflow; extends the workflow capabilities of the ServiceNow platform to communicate and orchestrate activities outside the ServiceNow instance. Workflows within ServiceNow equates to the coordination of a single instrument. Orchestration takes that coordination beyond that single instrument. It co-ordinates multiple systems to function together effectively to achieve a goal.

It lets you increase agility by automating IT and business processes for operations management. You can reduce tasks with Password Reset and Client Software Distribution, and improve end‑user productivity by giving users the ability to access services directly. Codeless automation and activity packs also automate and accelerate processes for employee onboarding, managed file transfer, and remediation.

An example to demonstrate how Orchestration can be used to automate common tasks.

Active Directory automation example: A set of six Orchestration Active Directory activities enables organizations to automate their on-boarding/off-boarding processes with auditable, self-documenting workflows that save time and eliminate mistakes.

You can also refer to this link that would give you more technical insights on orchestrations in ServiceNow.

I have also attached an Orchestration Datasheet with my response that would help you understand more of what it has to offer.

To sum it all up, I would recommend that you keep this plugin if this has already been included in your current contract offerings with ServiceNow.

[timhorn]

Hey Gaurav - thanks for that very complete reply.  

We really have no need for any of the current orchestration activities that we see in the workflow editor, since the things we're integrating with today are internal custom applications.   To support those integrations we've written our own web services.   At this point I'm mostly interested in understanding if ServiceNow looks at our custom integrations and says we need to pay for orchestration because what we're doing falls under the category of "orchestration" - even though we wrote it ourselves.   I know that sounds border-line paranoid, but I figured I should at least ask.

Tim

[gauravchoudhury]

Hi Tim,

To the best of my knowledge, ServiceNow will not charge on internal integrations as Orchestrations. Moreover, orchestration is generally a paid plugin. So anything you haven't paid for will not be available for you to utilise, unless you request for one.  

The charges are directly linked with the functional & technical dependency. If orchestration is not available in your environment, that means anything related to the functionality is not technically executable.  

Integrations are generally not considered amongst orchestration activities.

[Kalaiarasan Pus]

This is best to be asked to your sales representative. He should be able to answer this.