We use cookies to provide you with a better experience. If you continue to use this site, we'll assume you're happy with this. Alternatively, click here to find out how to manage these cookies

hide cookie message
Ovum: Comms enablement must drive your business processes

Ovum: Comms enablement must drive your business processes

But Ovum warns that many development platforms are "highly proprietary"

Article comments

Companies must take greater advantage of communications technologies to improve their business processes, says analyst Ovum.

In its "Achieving the True Business Value of Communications-Enabled Business Processes (CEBPs)" report, Ovum says CEBPs can drive business agility and ease mobility integration.

Ovum says communications enablement can "reduce the latency associated with human involvement in business processes, and provide many benefits, such as more efficient resource utilisation, faster time-to-value and more effective collaboration".

Ovum analyst Saurabh Sharma said: “The rapid proliferation of mobility solutions is creating complex integration issues that need new solutions.

"Lightweight mobile middleware is gaining ground as a suitable approach for integration of mobility solutions with enterprise IT systems and business processes.”

But Ovum warns that many CEBP development platforms are "highly proprietary" and do not provide all the necessary tools and interfaces to ease the complexity of communications and business process integration.

Customisation work done by system integrators to enable the integration of communications services with specific business processes adds to the total cost of ownership of unified communications and collaboration (UCC) solutions, says Ovum.

Such a way of working is not "sustainable in the long run", the analyst house says.

Sharma added: “CEBP development should not be approached as a one-off project. Instead, organisations should develop a strategy and roadmap, and prioritise business processes for communications enablement based on their business value."

He said, "Organisations should focus on leveraging existing integration architecture for the development of CEBPs and to enable integration between disparate applications. Service-oriented architecture (SOA) and event-driven architecture (EDA) are architectural prerequisites for CEBPs.”

Ovum says interoperability and integration remain a major barrier to CEBP adoption. This is because "only a few" CEBP development platforms support a wide range of open standards and protocols, such as session initiation protocol (SIP), voice extensible markup language (VoiceXML), asynchronous JavaScript and XML (Ajax), web services description language (WSDL), and extensible messaging and presence protocol (XMPP).

Share:

Comments

Advertisement
Advertisement
Send to a friend

Email this article to a friend or colleague:


PLEASE NOTE: Your name is used only to let the recipient know who sent the story, and in case of transmission error. Both your name and the recipient's name and address will not be used for any other purpose.


ComputerworldUK Knowledge Vault

ComputerworldUK
Share
x
Open
* *