Endeca was a business intelligence platform for analyzing unstructured data, acquired by Oracle and since discontinued.
N/A
MS SharePoint / SQL
Score 8.1 out of 10
N/A
MS SharePoint / SQL refers to Microsoft Sharepoint, a web-based collaborative platform, being used in tandem with Microsoft SQL Server to provide business intelligence analytics and reporting. They can provide BI content such as data connections, reports, scorecards, dashboards, and more.
Best fit for this product: - Advanced or Sophisticated Enterprise Search platform: If you spend effort on your search capabilities, Endeca is the tool. - If you are looking for capabilities to search and navigate similar to a relational-database system, then Endeca is not the best fit. - If you are spending effort to drive customer experience, especially around customer interaction with your web application, Endeca can help with that in a multichannel environment.
A simple and important scenario well suited is that you can configure alerts to notify you when the production server fails. another best feature is the report server is the central component of reporting services. For me something less appropriate is that the admin must ensure optimal performance for farm operations, they recommend that you install SQL Server on a dedicated server that does not run other farm roles and does not host databases for other applications.
Provides exact, correct counts of items in its dimensions.
Allows for flexible, out-of-the-box boosting of content (based on combo of any/all of: user profile, date, dimension being browsed and search keyword).
It has a reasonably good admin interface for the administration of boosting/promotion rules for the business user.
If the solution is implemented well and the business understands the purpose of the Endeca stack, it offers a great way for a business to explore and benefit from its existing data. From my experience, the Endeca solution has exposed data patterns to a business that were not thought about or explored before because of the lack of available tools to properly expose these patterns
This was a long-term buy-in from a corporate perspective, to remain in the SharePoint space. Migration is certainly possible, which is good for planning and having options further out. At this point, the only planned migration is to eventually move the architecture up to SharePoint/SQL 2013. At that point, we will be able to leverage some greater efficiencies, some enhanced content design and management features, and some more current social features. It is well worth a full consideration in any shop looking at a new implementation of or migration to SharePoint (although you will probably be considering 2013 versions or beyond in those discussions), but the platform should be a strong competitor to any alternatives. Realizing the capability of a fully-branded and customized website was not part of the original choice for the architecture at Lincoln, but seeing it implemented and functioning now with this capacity far beyond original expectations has certainly cemented plans to continue using it.
The system itself is very usable, and with proper training is very sensible in its organization and method of operation. There are some downsides in initial setup in the way things are imported (or not in some cases) in setting up properties and dimensions. Overall however it's amazingly flexible in terms of the content it can index and make available for search.
SharePoint is very complex. This makes usability somewhat difficult from an IT perspective. An IT generalist will be able to pick it up and run with basic tasks. More customized functions would require significant specialized training and therefore limit what a standard user would be able to achieve. From an end user perspective, it's pretty straightforward to use.
Support has been very good, and the trainers for the various Endeca courses have all been very willing to help long after the classes have been completed, so in the instances where we're waiting on support from Oracle, it's often that the members of their training arm can help us out as well.
It's been fantastic in terms of Premier Support so far. If there is an issue and if you report if the product has an issue, they will act upon it immediately. In some cases, if you design/develop something using the platform, Microsoft appreciates it and... publishes it on their public website. But you have to wait for some time if it is a non-Premier Support issue as you may experience delays.
The training is actually really good, and absolutely necessary - although this is software that has great documentation, the documentation itself is so vast, that it would be difficult to learn haphazardly, not to mention being incredibly time consuming to do so. Online training probably would have been fine except for the fact that having someone look over your shoulder to see where you're going wrong is helpful. This also allowed our team to sit in a single room and converse about functionality, etc. that would have been difficult to facilitate via an online class.
We did some online Q&A with the Oracle team, but I would definitely recommend doing an in person class if you have a large team that will be attending - there's definitely no replacements for a large class of technically oriented staff members who can drive conversation about specific topics that might surface.
There were some features we were hoping to get implemented in this particular release of Endeca, but were unable to facilitate those requirements due mostly to timeline. Having seen several other implementations, we will definitely have future iterations to add functionality and improve upon our implementation of Endeca. For the time being, we are satisfied with our implementation as it turned out.
Oracle Endeca was the best option that we evaluated by far. It gave us the most flexibility and ability to meet our objectives and had features that were not offered by the competing products we evaluated, but which we very much wanted, and this was why we decided to go with Oracle Endeca versus another platform
At the time of the two large projects, SharePoint was the enterprise solution so we were required to use that. We have since lobbied the enterprise teams to review and consider Atlassian Confluence and were successful. Confluence is cheaper than Sharepoint which is why we wanted to bring that in. The enterprise has now made Confluence an enterprise solution as an alternative to SharePoint. After using both I think SharePoint has many more add-ins than Confluence. It has much more customization ability than Confluence. SharePoint is not good for mobile readiness. Confluence is so there is a difference that might lead you to Confluence over SharePoint. I would also say that SharePoint is very document-centric and that Confluence has better KM than SharePoint does. even with the use of SQL Server. We were told that we could not use Google Drive even though it had features we liked.
It is a searching tool, and hard to estimate its impact on conversion.
It does its job regarding better searching; In terms of efficiency, it's hard to say: it has big learning curve. It requires a dedicated Endeca developer to work on it.
I've installed SharePoint in many different industries and each industry has seen greater collaboration among their teams both locally and nationally. The ability to collaborate more efficiently has reduced the need to have employees centrally located.
Companies which have used SharePoint in a end user training portal have had great ROI, since they can create the content once and share with all their users who subscribe to their training service. The web content management aspect of SharePoint is a very helpful feature.
