By using a common, standard set of APIs to communicate between the business- and service-orchestration layers within a provider domain, numerous cost and operational benefits are realized by both the provider as well as the technology suppliers for both the business applications and the service-orchestration functions.
For example, a technology provider of service-orchestration functionality has to work to ensure they can interface with multiple and often proprietary business applications, including commercial applications and provider-developed custom applications. This need adds significant development cost and product-management costs for the technology provider; it can limit their compatibility for some providers as well as slow down implementation to support custom integration.
Similarly, business-application technology providers, or in some cases providers themselves when using custom-developed applications, have to develop the ability to interface with different, and often proprietary service-orchestration software. Having common, standard APIs, increases the agility of the provider, as well as lowering development and testing costs, and speeding implementation.
Common, industry-standard APIs can significantly reduce costs for both service providers and technology peers of business-application and service-orchestration software.