Aspirationally, Avaya’s Agile Communications Environment (ACE) is the essence of Recombinant Communications (RC) packaged as enterprise software. As described by product marketing director Sajeel Hussain, ACE came into existence where “UC typically breaks down,” referring to the “siloed”, multivendor IT and communications environments where “nothing works together.” It ships as shrink-wrapped software designed to abstract the underlying communications layer and present it as simple Web services which developers can integrate into their own solutions using their choice of RESTful programming environments.

In other words, Web developers can build communications-enabled apps “without knowing anything about communications.” Genius!

As characterized by Hussain, ACE is the product of marketing “pull” that crosses several functional areas in an enterprise. Demand starts at the functional level, where platform incompatibilities may have thwarted a departmental head’s efforts to reap the benefits promised by providers of “unified communications.” ACE comes to the rescue with shrink-wrapped “connectors” for Cisco, Avaya (including the vestiges of the Nortel CMS line), Tandberg (video endpoints), IBM SameTime, and Microsoft OCS. Thus Avaya makes it possible to overcome incompatibilities with a single DVD that runs on a couple of servers and carries a list price of $10,000-$12,000 for the core license plus per user fees of $50-$100.

As for common use cases, Hussain provided profiles of implementations at a number of global businesses. For example a multi-branch global bank provided a form of “follow-me” connectivity by providing “hot desks” for itinerant executives. The service integrates a voice network that includes IP-PBXs from both Avaya and Cisco with presence management and call origination based on IBM Sametime. In other instances, the ACE SDK was used to “communications enable” business processes and workflows with APIs to CRM and knowledge management systems to support better medical care or customer care in financial services.

Architecturally, ACE resides “on top of” Aura, Avaya’s branded middleware SIP-based communications. Hussain explained that Avaya’s product offering has changed so that ACE will emerge as the application development environment for Aura as well as multivendor environments, and that the “lower layer toolkit (back into Aura Session Manager) will be ACE.”

Hussain, who is a veteran of the “Nortel side of Avaya”, was especially pleased that ACE is now a part of Avaya’s DevConnect program, referring to Avaya’s community of 3rd party developers, acknowledging that this sort of program was “missing at Nortel.”

Avaya is on the right track with ACE. It is putting tools into the hands of the people that are driving enterprise-wide innovation and making sure that key elements of Avaya’s existing fabric for call-handling, voice processing and multi-media interactions remains entrenched in multi-vendor solutions. The short list of supported vendors – IBM, Microsoft, Cisco/Tandberg – is not as “open” as might be ideal, but it does represent a high percentage of Avaya’s current market space.

Categories: Articles

Tags: Cisco, Avaya, IBM, Collaboration, Recombinant Communications, Microsoft