Oracle Digital Assistant: The new incarnation for conversation interfaces by Vijay Kumaryenne


If you are following the Oracle Mobile and Chatbot Platform announcements you would have now realised that we have announced the availability of the Oracle Digital Assistant platform as a new SKU under the PaaS offerings.

In this post, I will delve deeper into the Oracle Digital Assistant offering and answer what I anticipate will be common questions about the changes.

So what is an Oracle Digital Assistant (ODA)?

It is synonymous to the earlier version of chatbots which is oriented towards having conversations with the human, however, the ODA recommends or completes certain task beyond conversations. The old chatbot framework was user-initiated, whereas, with the ODA, it can launch multiple Bots based on the incoming requests. So instead of friending numerous bots through a channel, I can now add ODA as my Admin or secretary and let it decide which skill to be initiated based on my needs.

In an enterprise context, there might be a need for a HR Bot/Skill that can execute HR related tasks like Employee Profile Update, Leave balance etc, a recruitment Bot for recruitment related activities, Procurement Bot that communicate with your backend procurement system and can place an order to acquire a new asset, a policy help desk to understand the company policies and procedures . Instead of rolling these multiple Bots on to the Company Intranet portal you can now add the Oracle Digital Assistant as an Employee Digital Assistant on your intranet page and let the digital assistant decide which skill to invoke based on the user input. So in a nutshell, Oracle Digital Assistant is a smart Multi-purpose Bot using AI for predictions and recommendations.

So what does that mean to the  Mobile Cloud Enterprise platform that Oracle had earlier? Well technically nothing has changed, we have decoupled the Mobile Platform and the chatbot Platform and now rebranded the SKU as Autonomous Mobile Cloud and Autonomous Digital Assistant. I think this the right foot forward, given that the Chatbot Development can focus on the Digital Assistant platform and make their releases happen while the Mobile Team can push their releases independently of the chatbot release. From a provisioning perspective, it is easy for customers who are focussed on Chatbot use cases can provision Autonomous Digital Assistant only and in use cases where there is a need to develop mobile applications customers can now provision the Autonomous Mobile cloud service. Read the complete article here.

Developer Partner Community

For regular information become a member in the WebLogic Partner Community please visit: ( OPN account required). If you need support with your account please contact the Oracle Partner Business Center.

clip_image003 Blog clip_image005 Twitter clip_image004 LinkedIn image[7][2][2][2] Facebook image Meetups

Technorati Tags: PaaS,Cloud,Middleware Update,WebLogic, WebLogic Community,Oracle,OPN,Jürgen Kress

Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s

This site uses Akismet to reduce spam. Learn how your comment data is processed.