Blogs

Marek Kowalkiewicz

ThingFinder + MS Outlook = happier enterprise information workers
Marek Kowalkiewicz SAP Employee Active Contributor Silver: 500-1,499 points
Business Card
Company: SAP Research
Posted on Sep. 09, 2008 12:01 PM in Business Intelligence (BusinessObjects), Duet, Knowledge Management (KM), CRM, Emerging Technologies, ERP, SAP Research, Service-Oriented Architecture

Subscribe.Subscribe
Print. Print
Permalink Permalink
Share

You might have heard of Ubiquity, you might have used Xobni. Perhaps you have seen Gnosis.

What do these projects have in common? They try to help you make sense out of the documents you process. When writing emails, Ubiquity will quickly help you create and embed mashups. Xobni will analyse your inbox, provide sender statistics, show you related messages, and previously sent attachments. It will even get sender data from LinkedIn. Gnosis will analyse webpages you browse, identify mentioned entities (people, places, dates and so on) and give you related links that you can click on to get some more information.

What else do they have in common? People are very excited about them. Ubiquity is currently blogged about quite a lot. Xobni attracts a huge user base and is creating plugins for mail readers other than MS Outlook - in response to great demand. Gnosis is probably the first interesting application of named entity recognition that is appealing to casual and business users with hundreds of daily downloads on Firefox Add-ons site only (not counting the original source site).

One thing those applications lack is support for enterprise users. Ubiquitous is extensible, but the extensions seem to only be related to accessing content on the Web. Xobni users have to rely on extensions included in upcoming versions, but for obvious reasons (Xobni has nothing to do with enterprise software) it is unlikely that Xobni will cover enterprise software connections. And finally Gnosis, being able to recognize only "standard" entity types, is not helpful either.

YowieEnter Yowie.

For the past few months a team in SAP Research has been working on supporting enterprise information workers in a way similar to what the products mentioned above do. As the three products mentioned above did not yet exist "in the wild" when we were scoping our solution, it can be concluded that we have chosen a trend that is leading into a popular if not strategic direction. Our goal was to create an extension to business productivity software (we took MS Outlook as the first test field) that could apply known entity recognition methods in order to automatically link to information and propose activities related to the processed documents. In a way it is similar to what Duet does, however Yowie copes with unstructured information. An important requirement was to be able to access enterprise systems. Accessing Internet and desktop resources came naturally.

We named the project Yowie, to honour the Australian big foot being a hairy big thing that is our version of the big hairy audacious goal.

The project is currently reaching a state of mature research prototype, and so I thought I would share some of the information about Yowie with you.

Yowie is a Windows application that consists of a number of components. The closest to the end user is the MS Outlook plugin. It provides access to processed emails and also acts as a GUI for Yowie. The Outlook plugin relays email content to a local application running in the background that does all the processing. It contains an entity recognition engine, postprocessors and wrappers. The entity recognition engine is responsible for identifying potential candidate phrases in the email that could be enriched with information and links to actions (the ability to match information with actions is pretty unique to Yowie!). Postprocessors collect any additional information that could be required (for instance, when recognizing a human name, the postprocessor is responsible for disambiguation [which "John" do you mean?] and collecting email addresses and phone numbers from other sources). Finally wrappers take enriched entities and perform service calls, native application calls, scrap webpage information, and wrap it as HTML snippets that can be displayed back in the Outlook plugin.

There are some additional components of the system that are not relevant in this description. Importantly enough, we use Business Objects' Inxight ThingFinder as entity recognition system. It works amazingly well!

The whole system can be installed as one Windows application, and the process is virtually effortless.

Enough technology, here's how Yowie looks and works.

First, let's take a look at a "casual" email. There are a few things important here. The email mentions people (Marek, Konrad), a data (15/08/08), an address (45 Cleveland Street, Sydney), and a road name (Stuart Highway). The reaction of Yowie can be seen on the left side. It has recognised Marek as a person, however a check in the contacts folder has shown that the user knows more than one Marek - both are being shown. Since email and phone number for each of the Mareks is known, Yowie provides links to Skype calls and email generation. The recognised date triggers an option to create an appointment in the calendar. For the road (Stuart Highway), Yowie accessed a website of a road authority to find out that a section of Stuart Highway is under maintenance (mouse over needed to see the details). Since Sydney was mentioned in the email, Yowie has accessed a weather information web service and displays results of the web service calls, together with links to more information. And finally, the Sydney address has been located on a Google Map and shown to the user.

Yowie - casual

Second example I want to show you is our very recent development, where we have shown how Yowie can be integrated with an enterprise system. In this example, the author of the email mentions one Sammy. Yowie recognizes that Sammy is a person and, as in previous scenario, gets more information about him.

The collected email address of Sammy is checked against the database of customers in the ERP system and it turns out that it is a customer's email. Yowie retrieves that information and based on that provides some data about the customer. We call it a "customer fact sheet".

If you look closely at the screens below, you will see that we have extracted customer information and last products bought by that customer. The last screenshot shows the most recent development, where we use Business Objects technology to recognize intentions in emails (in this case that Sammy wants to buy a product).

On the screen above, the "Customer details" link will open SAP transaction displaying customer data.

Clicking on the links for each product above will take you to an SAP transaction showing more details about a product.

On the screenshot above, clicking on the plus icon (far right, "Order Product" column) will open a new SAP transaction for entering orders with pre-filled customer and product information.

The most interesting part is that Yowie is very extensible. Each part of what you see in the Yowie window can be removed and new components can be easily created. Outlook is thus just the proof-of-concept starting point as Yowie could also work with any other office application, e.g. MS Word, Excel, Adobe Reader, a web browser, an Open Office application, you name it. With the current set of technologies we use, it is pretty straightforward to implement new scenarios. Since what Yowie does is analysis of unstructured information, it looks like an interesting add-on to what Duet currently offers...

Marek Kowalkiewicz  Active Contributor Silver: 500-1,499 points Marek is a Research Program Manager at SAP Research. He works in sunny Brisbane (Australia).


Comment on this articleWhat do you think?
Comment on this weblog
Showing messages 1 through 5 of 5.

Titles Only Main Topics Oldest First

  • Duet 3 ( Duet Enterprise)
    2009-11-25 03:06:02 Rakesh Dube Business Card [Reply]

    Hi,
    How this integrate with the DUET 3 in future specially when SAP and Microsoft is providing platform for development. Please see announcement


    http://www.duetresources.com/duetenterprise.html


    I am also interested in understanding where Yowie sit in SAP roadmap.
    thanks
    Rakesh


  • Availability
    2008-09-25 06:20:12 Luis Marrufo Business Card [Reply]

    Marek,


    I've used Xobni in the past and I'm very excited to see that SAP is developing a similar product, but one that can that integrate with enterprise applications. A couple of questions:


    1. Will Yowie have the ability to link simultaneously to ECC, BI and CRM?


    2. When will Yowie be available?


    Thank You,


    Luis


    • Availability
      2008-10-27 16:42:07 Marek Kowalkiewicz SAP Employee Business Card [Reply]

      Hi Luis,


      Thanks for your interest, and sorry for that delay on my side.
      Regarding your questions:
      1. Absolutely! You can create any module you need and then simply add it to Yowie (currently it's as easy as pasting a file in the Yowie folder. Of course development of modules is a bit more time consuming, but our experience shows that an average new module for Yowie can be developed in 1/2 day by an experienced developer.


      2. Currently Yowie is a research prototype, and as you may be aware, it might take a while until the functionality is shipped as a product. Some of the SAP customers though participate in our beta programs, and this could be one way of getting Yowie sooner.


      cheers,
      Marek

  • Ubiquity & Genesis & How to extend Yumie?
    2008-09-09 23:09:37 Daniel Koller Business Card [Reply]

    Two comments from my side:
    - Ubiquity does currently not have enterprise specific content, this is related to the fact that you would have to provide company-/enterprise-specific content. (which Ubiquity allows quite easily) --> you would just have to create some hookups for the relevant functions.


    Is there a tutorial e.g. how a link has to be formatted to open a certain trainsaction with local SAP GUI? --> this would make is easier to create a prototype


    - Are you aware of the Genesis project from Adobe Labs? What I read, this goes into a similar direction, even if the Genesis thing seems to rely largely on the Flex technology.


    How do plan to make it possible to extend yumie? Some of the ',agic' from projects such as Ubiquity comes from the fact, that you do not need to be the top expert in XYZ to extend the solution, which brings in a kind of community generated movement forward.


    Kind regards,


    Daniel

    • Ubiquity & Genesis & How to extend Yumie?
      2008-09-14 17:52:34 Marek Kowalkiewicz SAP Employee Business Card [Reply]

      Hi Daniel,


      Thanks for your comments!


      Regarding your points:
      1) Ubiquity requires you to enter commands. The difference to Yowie is that Yowie recognizes the needs automaticaly. Sure, you could try to paste the contencts of your email to the Ubiquity command window, but I don't really think it would work nicely. It seems that Ubiquity is still quite far from what we have already achieved in the demo. However, it must be said that Ubiquity is much more open. Creating a new component to Yowie will take a few hours of development, as opposed to maybe one hour for Ubiquity.
      2) Genesis - I haven't heard of that. Thanks for mentioning! I think it is an extremely exciting project when it comes to supporting enterprise workers' tasks. I'd be very keen to try how we could get Yowie to suggest Genesis workspaces.
      3) In the enterprise scenarios, the ability to extend such systems has to be limited. First, because of a need to protect systems from denial of service "attacks". Imagine a scenario where one employee creates an extension that queries a server and than that extension is distributed to all other employees who find it exctiting and decide to use it. It might crash that server, and the it people will not be very happy. Another reason is that we are talking about mashing up sensitive internal information with public one. But having said that, with the current prototype, creating an extension to Yowie is a matter of writing one C# class, compiling it as a .dll and copying to a Yowie folder. Looking at Ubiquity tootorials, the complexity of the task is very similar. I totally support community generated evolution, and I think in some scenarios it is a certainly valid approach.


      Many thanks for inspiring comments!


      Cheers,
      Marek


Showing messages 1 through 5 of 5.