ERPJEWELS.COM

Particulars

Remarks

ETL tools (through ODBC connections) (Data transformation power)

This is very basic already present in SQL 2k5 and MS Excel pivot table also. Even small companies like ours can do in-memory data transformations easily http://www.baanboard.com/baanboard/showthread.php?t=28569 and given it to clients/ users freely. Further disk based data transformation like Baan report exist since 4 years in ERPJewels. So it’s very important to give only due and appropriate weightage to this functionality.

Data Warehousing / Cube creation and rebuild

Cube creation and maintenance are native part of existing databases like SQL 2005 standard edition (Analysis services) and Oracle(Discoverer). Separate data warehouse may not at all be warranted.In ERPJewels cube creation and maintenance is rightly delegated to databases only.

Slice and dice Multi-dimensional data browser tool

That already exists in data browsers for the cube in a database and spreadsheets like MS Excel pivot table. With capacity enhancements in MS Excel, these are formidable and indomitable.

Pre-built analytics

These are not always of widespread use to client. They hardly use tiny portion of it and that too with lot of customization in it. These are very basic reports which users always use it even without those tools but with lot of effort. So careful considerations be given to the extent of usability for pre-built reports, customizations required therein, possibility to buy only portion of it useful for customer, the cost it takes to build such reports internally.

Pre-built applications on cube

This is something good if customer really needs it and uses it. Till recently pre-built applications were never given and majority of existing installed base does not have any pre-built applications on cubes. If there is strong application requirement and there is perfect match for the same out of the box, pre-built applications can be bought separately.

One-version of truth.

This is actually no deliverable. This is basically an advice not to use spreadsheet due to possible problems. Spreadsheet must be used from BI tools only. While there is some degree of truth / merit in this theory / advice, BI tools have oversold this theory at heavy premium and in the process restricted spreadsheet usage in an enterprise. In reality users always need spreadsheets / Excel. So BI tools have to offer integrations to spreadsheets / Excel. In the whole process, the company looses lot of time and money with no satisfaction. Nowadays it’s a well established idea to let user judge the usability and accuracy of data in spreadsheet. and not limit his/her data access in MS Excel. While customer must accept and appreciate the importance of this advice (One version of truth), they must not buy any limitations on integrations with spreadsheets in the name of this theory and pay for the same.

ERPJewels leaves the compliance / non-compliance of one version of truth theory to user. Reporting tool has the capability to deliver the analyses results in web page which can be hosted in intranets and user can only view and NOT change anything .

Operational reporting tool with little integrations with native reporting / tools

Companies have heavily invested in ERPs and making them use new operational reporting tool from BI tool vendor is a ‘Rip and replace’ technology approach with lot re-training and re-work involved.. It’s not a plug and play ‘BI for the masses’ kind of idea. In ERPJewels there is very good native integration with ERP tools and native Baan reporting .

SOA

Till now nobody sold these SOA components along with BI. But in future it can be sold to make it integrated with disparate systems. Bolting on separate SOA when existing tools can take care off it nicely is again a rip and replace approach to BI leading to overall higher TCO (good learning curve and re-work). First adding heterogenity and then adding SOA to resolve heterogenity is not an advisable strategy.