Business Benefits of SOA and Multi-Channel Access
Multi-Channel Access Reduces Staffing Costs
Evolutionary migration from monolithic applications to multi-channel systems based on an SOA provides the opportunity to reduce staffing costs by moving some service delivery activities from human-intensive processes to less expensive self-service processes.
Multi-Channel Access Eliminates Obsolete and Expensive Infrastructure
Evolutionary migration from monolithic applications to multi-channel systems based on an SOA provides the opportunity to re-engineer existing processes and eliminate obsolete and expensive infrastructure.
For example, eliminating brittle departmental client/server applications and replacing them with more robust, scalable enterprise services can save money by reducing administrative costs and allowing for greater server consolidation. Consolidating numerous departmental Web servers can do the same. In addition, replacing Motif applications (and the expensive and obsolete X/Windows servers) with .NET Framework client applications can simultaneously reduce costs, improve response times, and improve employee productivity.
In all of these cases, the savings can be substantial, given the fully burdened cost for each server (fully burdened costs include amortized costs of hardware, storage, network connections, software licenses and maintenance costs for security software, management software, backup software, personnel costs for system administrators, facilities costs for floor space, and power, air conditioning, and disaster recovery costs, which include replicated hardware/software facilities at a remote disaster recovery site).
Service-Oriented Architecture Reduces Costs and Improves Efficiency
Evolutionary migration from monolithic applications to multi-channels systems based on an SOA opens up opportunities for application migration and consolidation that in turn reduces costs and improves organizational efficiency. This is possible because an SOA defines the business services in a manner that is independent of a particular legacy application or packaged application.
Here is a typical application migration scenario: Consider an existing application that is expensive to maintain and that no longer delivers the functionality needed to meet new business requirements. An SOA infrastructure allows the application to be wrapped as a set of business services and then incrementally replaced with a less expensive, easier-to-maintain application that delivers better overall capabilities.
Here is a typical application consolidation example: Consider an organization that has numerous customer care systems. Each one requires its own separate hardware infrastructure, administrators, user training, and so on. An SOA infrastructure allows all of these customer care systems to be seamlessly consolidated to one or two systems along with the savings in hardware, administrative costs, reduced user-training costs, and reduced software maintenance fees.