Content Management as an Enterprise Infrastructure
Mark B.: Hello and welcome. My name is Mark Brown and I'm a Senior Director in the Cloud Strategy Group at Oracle, and welcome to the next edition of WebCenter in Action.
Now before we dive into today's content, we just want to reiterate something that I think we all know intuitively, and that is the digital explosion over the last few years has really changed how business is done. Customer service is now expected not to be a phone call but to be an online capability that every customer facing organization provides.
Even internally, your employees have an expectation of support, not calling a helpdesk but to actually go and find recorded examples, or find the information that they need on the inside systems. And of course inside the firewall we still have to worry about compliance and security.
So what we call that is the digital engagement. So when we think about those requirements, what we're talking about is new priorities. I mentioned anywhere, anywhere, and that means from any device inside/outside, a huge challenge. Automation becomes key because sometimes with these new systems and partially finished processes that so much of the information is caught up in someone's head that how to do something, you've got to be able to automate those things. And then lastly, you need to be able to communicate in a powerful way across all these channels.
Oracle's answer to these challenges is to create a center of engagement through the product, Oracle WebCenter, where people, processes, and content can be tied together in a compelling way. And today, we're happy to welcome Emerson Process Management to talk about how they solve some of those problems that they've experienced in terms of this new way of doing business, and rather than me prattle on about it, let's introduce our two speakers.
Mark H.: Hi, I'm Mark Heindselman. I'm the Director of Knowledge for Emerson Process Management.
Michael: And I'm Michael Lawrence from Redstone Content Solutions, and I'll be handling the pieces based on the partner implementation features and services we provided to Emerson today.
Mark B.: Great, thank you guys and welcome. So as a quick overview, Mark will walk through a few of the things that Emerson was faced with. We'll talk about what we think were some of the keys to delivering this infrastructure platform, see a quick demo, and then I think Redstone wants to make us an offer for their services, and we'll call it a day.
So Mark, why don't you tell us about Emerson Process, and what you guys do, and some of the challenges you have?
Mark H.: Thanks, Mark. Emerson Process Management is a subsidiary of Emerson Electric. We have approximately 32,000 employees, global manufacturing locations and have an annual revenue of around $10 billion. The business generates products and services associated with the process control systems and software area, measurement instrumentation like temperature, pressure and flow meters, as well as analytical instruments, and control valves, and regulators. That's the primary business.
Enterprise content management as an infrastructure within Emerson Process, the focus was to try to come up with a single source of truth associated with managing content within the organization. Emerson is very focused on enterprise infrastructure applications, things like Oracle EBS, Oracle Fusion, Oracle CRM on demand, PeopleSoft. And WebCenter is the solution associated with content management, document management and business processes.
The objective is to improve user experiences and primarily efficiencies. Again, I'm going to say single source of truth, you're going to hear that several times today. That's important because what we have had in the past is multiple repositories of content, which lead to confusion or degrade our ability to provide information to the organization, efficiently and effectively. So the content management as an infrastructure is a critical part of providing that single source of truth.
We also needed this system, the infrastructure, to provide the ability to migrate and batch upload large amounts of content that come out of the business systems. Things like invoices, import/export documents, shipping documents, all kinds of trade documents that are all required by legal authorities to be retained and maintained for a period of time to support the business processes. And then ultimately make that information available through intranets and extranets so that we can service the customers and the internal employees that are servicing those customers as well.
So there are some business challenges associated with this whole process and the least of which is search and retrieval. Once you've got something stored, you have to be able to find it and pull it back. We also wanted to reduce the printing and shipping cost for all the documentation. Clearly if we can manage that content in a digital format and deliver it to the customer in an electronic format, it supersedes the ability of having to send that paper throughout the organization and to the customers.
We needed to provide immediate access. We needed to decrease manual processes and wherever possible, replace those manual processes with automated processes. We need to be able to respect the global security requirements for this information. There are some parts of the business in various world areas that have unique and special security requirements and consequently you have to be able to have a system that manages those requirements and is able to carry them out.
There is content conversion issues, various formats of content that we ultimately want to deliver in a single format so that it's a consistent way of getting to the information. So conversion is part of that process.
We also want to reduce or eliminate redundant copies. The ability again to have that single source of truth so we're not storing content that could be redundant on multiple systems in multiple world areas but having it be in that single source of truth. And finally, we needed to be able to manage version control and record retention.
Record retention is a critical aspect of this process because we are required by law from various parts of the organization and in various countries to retain records of this trade and business related content.
So our target solutions focused around a couple of core pieces of the Oracle stack and WebCenter, the WebCenter solution and within that stack, the content conversion or IVR process. Those are core pieces to the Oracle WebCenter content solution, and they are critical to our business.
We then needed to create some custom integrations to the Oracle Business Suite and to the CRM OD online CRM process, using either an XML or an ADF framework to get those integrations to work. We then needed to pull in the ability to capture content from multiple sources and in multiple ways, and we have a Kofax infrastructure that allows us to capture content from paper into digital format effectively and move it into the content system. And we have the ability to use a new batch management process for loading content from programmatic systems called Synergy Hub from Redstone Content Solutions. That gives us the ability to ingest thousands upon thousands of pieces of content that have various types of meta-data structure associated with that content, but do so in a consistent fashion, reusing components so that we can build new loaders efficiently and effectively through that process.
And finally then we needed a fast, effective search environment that gives us the ability to index that content quickly and allows us to search across millions and millions of pieces of content from thousands of users at a time effectively, and that's distributed Elasticsearch.
Michael: Thanks, Mark, for that overview. Now I just want to touch base on three of Mark's main points and how those tie directly into Redstone Content Solutions. So first, number one was their goal, creating an infrastructure based on enterprise content management. Number two was the challenge making content work for the business, and lastly the solution, leveraging Oracle WebCenter and custom development to achieve their vision.
Knowing where they were and where they wanted to go, Mark and Emerson needed a partner to execute on Emerson's vision. Redstone became a platinum partner of Oracle by specializing on those solutions that Mark needed to create his ECM infrastructure.
Now our reputation dates back to the Stellent days, and we continue building that reputation today. We do this through technical competency. We certify all of our developers in Java programming. We certify all of our project managers on our project manager certifications, as well as all the Oracle technologies and software solutions you see on the screen as well.
As important as it was for Mark to have an enterprise class system in place, it was just as important for his users to leverage the system effectively. So in addition to our services provided to Emerson, we've also provided training over the last few years, and our differentiator in training and the value we provide is in the customization of curriculum.
So we weren't just training Mark's staff on WebCenter but on how they use it, interact with it on a daily basis. We're one of the highest retainers in the industry, and you can visit our website to learn more about those services, about those training, and some things specific for Redstone.
All right, so let's pass it on to Mark first, and we're going to give a high-level overview of what enterprise content management is and how it's at the core and the center of everything. All right, Mark, take it away.
Mark H.: Thanks, Michael. To have an enterprise content management system as infrastructure, you must first have core content management. That's critical. There are certain pieces to core content management as depicted by this slide, which we define as part of the WebCenter content solution. WebCenter content provides us with document management, notated there by the DM, digital asset management there in the red, web content management in the yellow, records management in the green, and workflow and business process management in the light blue.
All of those pieces to the core content solution are critical for having enterprise content management as infrastructure. You can't do what you need to do in the enterprise content management solution area without this core content management. On top of that then you do need the following things that are in gray. You need an effective ingestion methodology and process, and that's one of the things we're going to talk about today.
You do need applications. You need to build on top of that, core content management, the capability to build those applications so that you can carry out the business requirements that the business needs. You then will need to do integrations. Integrations to other business systems, and in our case, most of those being Oracle related business systems.
And then lastly, you have to be able to find what you're looking for. You can have all this content ingested. You can build the applications, you can have integrations back to solutions of the business platforms, but if you can't find what there is and be able to display it and use it with the user, and it doesn't mean anything. So have an effective search solution is critical.
In the rest of the discussion today, we're going to be talking about those 4 gray areas, 2, 3, 4 and 5 in ingestion, applications, integrations, and search, as the key to enhancing the enterprise content management as an infrastructure.
Mark B.: Excellent. Thank you very much for the detailed overview and I'll just reiterate something that you said, and we'll go through those four areas around the outside of that little construct to the right. And that is, you can't actually have an effective digital engagement unless you have a single source of truth. Today's world, we expect to be able to sometimes make a phone call and that call center person better be looking at the same content that the maintenance guy is looking at, or that instructions on the website are pointing at. They all better be referring to the same PDF, especially in this business where we have physical devices installed that are doing work. So let's talk about each one of these in turn.
Michael: All right, so now we're going to take a look at content ingestion for Emerson, and what processes they use, and how they get their content into their system, and then Mark will give you a little bit of an overview on the benefits that they provide or these processes provide for Emerson.
So, on the screen, you can see four of the many ways that Emerson gets content into the system. We're all familiar with the out-of-the-box process. It's easy. It's manual and it handles all of the one-off check-ins that you might need to do. We also use capture software that converts paper-based content into electronic form prior to content ingestion, and as important as those are, they're not really those wow or a-ha processes. They're fairly common, and most people know how to use these.
Where we get a little bit more specific with Emerson is on these last two. So the EmailListener is the custom ingestion process that we've used at Emerson for email and email attachment integrations. So what knowledge workers at Emerson can do is they can forward or send email to the content server by attaching a specific email address and ingest those into the system attaching meta-data and other information based on the email address they forward that to. So it's really easy and there's not a lot of user training, everybody is pretty familiar with how to use their email.
Also Content Synergy Hub here standardized and eliminated more than 20 custom batch loaders for Emerson, bringing those all under the hood of one machine. Synergy Hub automates the bulk loading of content and meta-data from a wide variety of Emerson Systems while also providing centralized admin and error-reporting capabilities.
So Mark Heindselman, would you like to tell us a little bit more about the benefits that these content ingestion solutions provide Emerson?
Mark H.: Sure, thanks, Michael. First off, content ingestion has to be flexible, not one size fits all. Some users like to use a check-in screen, others like to use drag-and-drop off of their desktop or out of Outlook. Others would like to be able to send an email message into the system as they're replying back to a message to a user. All of those methods are supported within the discussion that you just had through both the out-of-the-box and some custom components from Redstone.
We also have the ability to put content in through programmatic based processes using the Content Synergy Hub. Which gives us the ability to basically build any kind of loader, ingestion loader that we need, from the component parts that are built inside Synergy Hub so that we can mix-and-match those components to do whatever we need to in terms of loading content.
So flexibility associated with content ingestion is critical because again, not one size fits all. We also need ingestion processes to be consistent. We need to be able to get the same meta-data regardless of the methodology we use to get the content into the system so that we've got all of the same index information ultimately to be used. That's critical.
It also has to be fast. Most users don't want to sit around and wait for 30 or 40 seconds. They want to be able to push their content into the system and be done with it, or we need lots of very fast programmatic systems that can load thousands upon thousands of documents per hour and process those documents along with whatever else is going on in the system.
And finally, we need this all to be cost-effective and cost-effectiveness in our case is a determination based upon what the user wants to do. If they are effective at putting content in one way, we want them to be able to use that, therefore leveraging their time and their effort in a way that gives them the most capability to get the content into the system.
Mark B.: Excellent. I think that's a great summary. And there's the one point that I wanted to just kind of reiterate was this idea of being flexible but consistent. In that if I'm sitting somewhere where one way of doing something is easier than the other, for example I can always forward an email or I can take a picture of some situation and attach it to an email and hit 'send' and know that that's exactly the same as if I uploaded it from a laptop. And there's no additional work. Then now you've created a system that lets me do work the way I'm comfortable, and that's so important to adoption of any kind of a content management system.
So let's move onto the next section and talk about the importance of the enterprise application. So now we get the content from wherever we need to get the content and we're putting it in a repository where it's managed. How do the apps play into that?
Michael: Great question, Mark, and you sort of touched on it, and beat me to the punch, but user adoption is one of the biggest aspects of implementing a system like Emerson's. So this slide represents five sample applications of the over 300 custom apps that they've built into their WebCenter content infrastructure, and similar to most organizations, Emerson wanted to know what their user adoption was.
So that's where the user contribution report comes into play. Emerson wanted to know whether or not it was being used, and by whom, and how much. As a result, the user contribution report was built. This enabled Emerson to monitor the user adoption rates for WebCenter content and the processes they were putting into place.
So one of the best and greatest attributes of WebCenter is its ability to scale and expand based upon growing and changing business needs. So Mark, can you tell us a little bit about some of these applications, user adoption and how Emerson has benefitted from the creation of all these custom applications?
Mark H.: Sure, Michael. You touched on one of the applications, and there were five on your list, but all of the applications that were listed there and many of the others, all kind of relate to or have the same kind of benefit, kind of structure. First off, the benefit of these processes allows the organization to, from an enterprise process, have visibility to what's going on. That's critical. The business does want to know what's taking place with the content, where it stands in terms of a status or a process, and so yeah, visibility is part of the benefit of an enterprise application. It allows us to see what's taking place.
Secondly, the ability to measure and improve adoption rates is part of the whole process. There's significant value if we can put together an application within the content structure that allows not just the content to be put into the system but rather that we solve the problem that the business is trying to carry out. Which may include not only checking in the content but also doing validation on meta-data, and being able to then workflow that item to parts of the organization that have to review or approve it. And if the item fails in the workflow process, being able to then be able to route that to the right place to then approve that content or get it approved so it can then finish the process.
So the whole idea there is to build the application that allows the adoption rates to be improved or be increased in such a way that the users want to and are willing to use the solution.
We also need to have consistent and auditable processes. Michael, we are an ISO 9000 organization. We have many outside firms coming into our organization and they want to see that number one, we have processes in place. Number two, that we follow the processes, and number three, that we can show them auditable ways that the processes have been carried out. And with a content management system that allows us to consistently follow the same process and has the ability for us to audit those processes as to what happens in each step of the process, it gives us that ability to support those requirements.
In one of the cases you mentioned there, something called the kuratula, we actually have improved the process so much that the organization which used to have a paper-based process that would potentially lose orders as they came into the system into the organization, we've eliminated the concept of lost orders. Those orders are now always, everyone knows where they're at. They know what step the process is in, where the order is at, and at the end of the process, they've also got a much cleaner order. They can get that item and that order through the system, it is then checked and reviewed, and it gives them, the manufacturing organization has to then fulfill that order, the ability to carry that order out or create that order with fewer and fewer errors.
And lastly, in that whole process, all of these things have helped us to improve our time to market. It gives us the ability to actually push orders, and quotes, and other content, or other parts of the organization get that information out so that we can meet the customer requirements quicker, more effectively, and faster.
Mark B.: So that's another outstanding overview of the challenges and the benefits. And I think the one thing that jumped out at me there was not only is it good business practice, managing say an audit from a government contract that wants to see those ISO 9000 things, but it's improving business agility. So doing the right thing from one perspective is helping in many other perspectives, and that's what a good system, a well-designed system is all about.
So let's move on and talk about some of those other integrations now. Now everything's in one place and it can be measured. So where else is it connecting?
Michael: Well one of the things that I'm excited about is that we're all on the same page today because I'm going to go and repeat what Mark Brown and Mark Heindselman have already said, and that's having a single source of truth. And that's one of the benefits of all of the integration that you can do with WebCenter is storing it in that single source of truth repository.
However, not many organizations and people out there are actually capable of accomplishing it quite like Emerson has done. Emerson used WebCenter content to be the single source of truth, and it integrates with many custom, third-party, and Oracle solutions. So we have a few big ones here listed on the screen. Oracle CRM on demand and Oracle E-Business Suite. We have also integrated the WebCenter content server with a number of ADF applications.
So Mark, can you shed a little bit more light on how Emerson leverages WebCenter content's ability to integrate with other enterprise solutions and what that means for Emerson?
Mark H.: Sure, Michael. Again, and you mentioned it, Mark Brown mentioned it. It is the concept of being a single source of truth. With all the content in the content repository inside WebCenter content, you can then create those integrations to other applications that are outside the content repository and allow those applications to then access that content as needed. We've done that in the case of E-Business Suite where we ingest accounts payable invoices through that process, and we actually then push the link to the invoice that's stored in WebCenter content into E-Business Suite so that the user who is in E-Business Suite, when they see that invoice, can actually click on it and pull the item up.
So that single source of truth again is allowing E-Business Suite to access that content. Same thing with CRM On Demand. We have large numbers of people using CRMOD to manage their engagements with customers, and so now users who are in an order or a code object inside CRMOD can actually run a query from CRMOD on that order object, and it runs a query in Oracle WebCenter content and pulls back all the documentation related to that order object. So they can see all the documentation and all the email messages and any other information that's related to that order object, right there in their CRMOD screen as a result screen from WebCenter content.
It also then helps us to eliminate duplicate data entry. Again, if everybody understands, we store it once and we store it in WebCenter content. We don't have people putting it in multiple locations causing redundancy, duplication and more commonly, confusion as to which is the most, what is the single source of truth, what is the right thing to be using.
And then it does give us that single point of access for content across multiple applications, and mostly it improves the knowledge workers' productivity. They don't have to go hunting all over the entire network to try to find something. They know if they go to any of these applications, any of these integrations that we've built, the content that they need, can be accessed from that integration back to the content store and allows the user to then get that information they need from a single source of truth.
Mark B.: Well I don't think I could have said it any better than you guys just did. I mean it's all about the appropriate interface for the job at hand. If I'm in accounts payable and I'm staring at E-Business Suite, I need that interface for that job, but I need to know that whoever else is accessing or feeding content into that environment, have one place to look at.
So let's look at the last one. Now we've got everyone in one place. We got all this good stuff. We got all these good ways of accessing it, but at the end of the day, being able to get things out right when you need it, is probably the most important aspect of any content system. So let's talk more about search and retrieval.
Michael: You're exactly right, Mark. Being able to restore information in WebCenter content is great, but without the ability to find it quickly when you need it, it really just becomes a glorified storage device instead of an enterprise solution.
Well, lucky for all of us, it's not just a storage device. WebCenter content is an enterprise solution in an application that empowers users and enables them to do their job in a better and more efficient mode. So once the content's in there, we're going to find it quickly with search and retrieval features in WebCenter content. And that's when we provide the real value is when the users get the information that they need and they can put it to use and put it to work, and really like we said earlier in the webinar, is make content work for the business. Just because it's a piece of content doesn't mean it can't provide value.
For example, Emerson's users are able to sort and manage search results through filters and facets, security, the people who are looking for the information are only provided the content that they have access rights to. You can do full text and meta-data searches, and it provides for a flexible indexing and rebuild process as well.
So Mark, can you provide us more on the search and retrieval features and benefits that Emerson's leveraging today?
Mark H.: Sure, Michael. Search is a critical piece. We have, in the last year, implemented an integration between Oracle WebCenter content and the Elasticsearch open source search tool, and we call that distributed Elasticsearch. It allows us to search and query against large content stores and provide fast, fast, fast search. Yes, did you get that? Fast.
We find the right things fast consistently. It is amazing. What used to take 15 or 20 seconds through the normal search that we had, now is sub one-second searches across 20 to 30 million items. We're able to sort the results of that information through field level values, and we're able to provide the security or the retrieval of that information to the right people, so security is respected as part of that process.
The other thing that has really been exciting about the distributed Elasticsearch is our ability to do multiple indices. We can build multiple indexes within the content store, and we can then have either faster searching, or we can pull those indexes together to create the ability to have one larger index. And again, all of that provides the ability to find the content. This indexing which used to take maybe weeks or months on our old index solution, now takes hours. So we can rebuild an index and have fresh index up within hours on 15 to 20 million records rather than weeks or months.
In the end, the excitement about this is the fact that users are ecstatic. They can go in and put in their search query against the content that they're looking for and get back in sub-one-second retrievals. That is a game changer. It makes their lives easier. It gives them a desire and a willingness to use the system because number one, they know that they're going to find what they want and they're going to find it fast.
Mark B.: I think that aside from the fast aspect, I think the key is search is an action we take when we don't have something we need. We don't go searching for the sake of searching, and to make that non-painful via the speed and the accuracy is a key to adoption. I mean that's been my experience over the last 30 or so years, and I think it bears, when you look at even in the kind of the global Internet market, that's how some companies have made their way. It's fast and it's accurate. So let's see it in action.
Mark H.: So today what we'd like to do is provide a bit of a demonstration for a couple of the technologies we've talked about. We're going to look at EmailListener, one of our ingestion processes, and we're going to look at distributed index or distributed Elasticsearch, our search technology, and these demos will show you the value of these technologies and how it's impacted the organization.
Content ingestion was the first piece that we needed to really put some meat into to allow users to get content in the system. And usually one way's not adequate. In our case, we have about seven different ways to get content in and not including custom applications. So we have four out of the box methods that are shown in green on this screen. We've got two or three scanning methods to get content in from a third-party piece of software, and then we have a couple of applications built by Redstone Content Solutions that allows us to get content in, both from a user standpoint and from an automated standpoint, through other systems.
Today we're going to demonstrate the process called EmailListener. This process is easy. It's natural for users to use. They just reply to an email message in their email box. It has extremely high adoption rates for users. If again, if all you've got to do is do a reply to a message, you can get people to do that because they already do it today. It's simple and straightforward for the admins to set up and keep up to date, and there's some good error handling processes in place to manage any failed items.
So let's just demonstrate how this thing works. So the first thing you need to know is you need to have an address to where you want to send this information. And so today, I'm going to show you, we're going to send something to an email box called Europe Holland Breischwik Logistics. It's an email address that we set up, pre-setup, and we've got that setup so we can send logistics information to that email box.
So you just have to grab the email address or know it, and go to your exchange or your email system, find the item that you want to have sent to that location. And that location in this case, logistics, is equivalent to a document type in the content server. So in this case, I'm just going to forward it. I could be replying to a message, send a reply to whoever I needed to do that with, and then paste this in the CC or the BCC, and typically I want to give it some unique information that allows me to find it in the system the way I want to find it. And notice I've got a couple of attachments here. Those will be filed in the system as well at the same time.
And once you've got your message ready to go, you've got the email address in to the box. You just hit enter, and that fires it off to the content server and any place else you want it to go. Notice already down here in my email, I've got to reply back. And I'll just go back to my inbox. Here it shows email check-in is successful.
So within just a second or two, from the time of sending that email out to the time at which I got the reply back, the item had been successfully checked into the content server. That is EmailListener. High adoption, easy to use, people love it.
In this demonstration, we're going to show you how you search. Search is a critical piece of enterprise content management. In our case, we use distributed Elasticsearch, which is the Elasticsearch software, open source search tool that Redstone Content Solutions has married up with and built an application around so it will work with Oracle Content Management or WebCenter Content.
It uses a single master index. It provides us with high-speed, fast indexing of the content, and it also gives the users the ability to do fast searches, getting results back in half a second or second and a half versus 20 or 30 seconds with the out of the box search. Users get to use the same search strings as they've always used. No changes for them in that process.
What happens is DES intercepts the search from the user's search screen before it goes to the SQL database, runs that search then gives the...runs the search against the DES inverted terms index. And then DES can also run multiple search terms at the same time, which speeds up the process significantly as compared to the out of the box SQL search.
DES uses the same result screens that are available from the content server. So there's no having them learn anything new, going to either the search or the result screens. It all looks like what they're used to using. In the end, it's fast searching for the users. And here's what it looks like. Let's give you a quick demonstration.
So we're on our main Internet page called OCM Internet, and we have a quick search box up here which searches across the entire collection, in this case about 19.1 million records. And we're going to look for an item. That item remember that we put in with using EmailListener where we put that in through that process. It said project marked test. I just put that in the search box, click quick search, and there it is. That's the item I put in back through EmailListener, and it provides that information back in less than a second and a half or thereabouts using the distributed index search.
And just to prove what it is, that was the message that I sent in, and you can open it up. And remember I told you it had other messages inside it? There they are, all just exactly the way I sent it into the content server from EmailListener.
So let's go back to our discussion about search. The results of search need to be fast. Search feeds need to be fast, and in our case, we get very fast searches with multiple terms, with millions and millions of records being searched. Our index rebuild speeds are fast. We used to take 3 months to index 17 million items. Now it takes nine hours. So we've got much faster high-speed indexing and searching, and mostly we have ecstatic users. They think it's great.
So why did Emerson choose Oracle WebCenter? Well, it is scalable, it's enterprise class, and it gives us the ability to grow our content management solution to the scale that we're going to need. We're at the point now where we're reaching some place between 30 and 50 million records in our environment, and we see that growing by another 30 to 50 million records over the next several years.
So enterprise content management through Oracle WebCenter is possible because of its scalability. And clearly, because we're an Oracle shop, we want the ease of integration into other technologies, particularly Oracle technologies, E-Business Suite, CRMOD, custom applications using ADF. Those are all part of the integration process, and we want and need that capability, and WebCenter provides us with that.
It also gives us a good low-cost, total cost of ownership position because we have been able to leverage this technology across the organization. It gives us that point of ownership cost that makes it palatable to put this technology in place, leverage it across the organization in a way that gives users great access with very little cost.
And probably the most important thing, it gives our end-users increased productivity. If we go back to the reason we're doing this, it's to provide that single source of truth for trade and business related content, it actually does that. It gives us the ability to put all of this content within the same scope or the same environment and allow users to be able to find it without having to look all over the network, and that's probably the biggest thing.
Decreasing the complexity for users to find content and being able to service customers efficiently and effectively, that is the bottom line, and WebCenter Content gives us that capability.
Michael: Thanks for that great demo, Mark, and the overview, and being with us today. Thank you, Oracle, for helping us put this together, and then thank all of you, fans and people out there looking to learn a little bit. Hopefully we provided you with some content and food for thought.
If you enjoyed what you heard and saw here today and you wish to learn more, here's how you can. What we've done is put together a total economic impact report for Emerson and how they use WebCenter Content. You can download this report by visiting the URL on the screen now. There's a long version and a short version. Both have access to the same report. Both things go to the same place. One is easier to remember and one's shorter to write down.
I encourage you to go there, download it, read through it and see what Emerson did and then maybe how that might apply to you in your WebCenter use cases. I'd also like to remind you about our WebCenter Whiteboard web series. All you have to do is Google "WebCenter Whiteboard" and let the learning begin as we highlight and draw out various WebCenter solutions on the whiteboard for you.
With that, I'll hand things back over to Mark Brown and Oracle to wrap things up, and thanks again, everybody.
Mark B.: Okay, and I can't thank you two enough, Mark from Emerson and Michael from Redstone. This is a great example of what is pretty traditional content management but taken to that next level with the understanding of the need for search, the understanding of the need for integrations. It's not just in place for compliant purposes, but it's actually an active part of the daily activity, and that to me is what's unique about this.
And for anybody else who's listening, who wants to get more involved and learn more about these types of solutions or other capabilities, the best way is to get involved in the community and there's five or six different links here. They're all fairly easy to remember. You could always pause the recording right now if you wanted to type in the links. And if you have any questions for Redstone, you can feel free to send them into the email address there. And then Mark and my email address is here. We'll get you connected with people that can tell you more if you need to learn more about these things.
So with that, we'll conclude this edition of WebCenter in Action and I thank our speakers, Mark and Michael, and that will be a wrap for today.