From ADempiere
Jump to: navigation, search
This Wiki is read-only for reference purposes to avoid broken links.


These Extensions are proposed by URUKI to enhance the vertical offerings of Adempiere via integration with many third party applications to supplant some of the weaker / non existent functions within Adempiere.

--hayder 03:59, 17 June 2007 (EDT) Below is just a scratchpad for my ideas. once the community accepts some of these ideas then they can be moved to more appropriate locations within the wiki.

Verticals to integrate

Integration with Zimbra. For Customer relationship management, Project management, task management of individual employees within the organisation and to use zimbra as one of the facets for interacting with the adempiere system in addition to the client GUI / Web UI

integration with funambol Reports, chain of command (decisions) in workflows & tasks sent automatically to employees mobile phones via a funambol connector. This is another facet for user interaction with the adempiere system giving adempiere a truly always connected interface for end users. This feature would be one of the killer features.

integration with liferay-alfresco for managing documents & content in an audited / standardised manner with access via CIFS and yet attached to individual transactions within the adempiere system via the 'attachment' interface. The liferay system should be used (somehow) as the front end for customer access both for online shopping / media viewing but for customer support purposes.

integration with asterisk all companies need a CRM solution that integrates with telephony solutions. What better way to do than to integrate directly with the main OSS telephony solution. Please see centricrm as an example of what can be achieved. Alternatively integrate centric with adempiere (but centric is not a fully OSS solution)... perhaps we can replicate some of the missing functions from centric within Adempiere? Which approach is best?

Integration with Spago BI for Business intelligence. This has the advantages of making use of all the OSS BI tools out there (BIRT / JASPER etc...) and integrating it into JSR-168 portlets for use on the Liferay portlet 'front end' and also within Zimbra portlets.

Increasing Depth of knowledge and Standardisation

XBRL for COA and financial reporting use the XML Business Reporting Language (XBRL) as the basis for the chart of accounts and financial reports. Having such an integration would immediately put ADempiere into the league of suppliers able to provide ERP solutions for listed companies or companies awaiting listing or publicly audited accounts. This is a KEY feature. Making it to the XBRL web site as a contender would put ADempiere within the sights of companies and executives who've never heard of Sourceforge. That's where we want to be.

International Financial Reporting Standards (IFRS) compliance. The world is heading this way... XBRL is the format and here is the method http://en.wikipedia.org/wiki/International_Financial_Reporting_Standards . This was discussed in the European ADempiere forum, what was the result?

Addition of UNSPSC for the classification of products and services within ADempiere.Universal Standard Products and Services Classification. The UNSPSC Code is a coding system to classify both products and services for use throughout the global marketplace. The management and development of the UNSPSC Code is coordinated by ECCMA, the Electronic Commerce Code Management Association. The current version consist of more than 16.000 terms. This is already defined in a usable ontology that can be plugged into any protege based definition of the ADempiere AD. http://www.cs.vu.nl/~mcaklein/unspsc/

Changes to foundation

Ontology based foundation Using the Web Ontology Language and the Protege ontology editor to refactor the application dictionary to create a system even more easy to extend and expand than the legacy AD inherited from Compiere. The idea of AD is as valid today as at any time and will be valid for the foreseeable future. The use of an ontology to define the AD and the easy to use graphical editor Protege to define it would expand the possibilities for massively increasing the functionality of the system at a level of ease unheard of in the world of ERP. Please check out http://protege.stanford.edu/ to see exactly what I mean.