Evaluating ADempiere

This Wiki is read-only for reference purposes to avoid broken links.

⇐ Table of Contents{{#if: | | [[{{{2}}}]] }}{{#if: | | [[{{{3}}}]] }}{{#if: | | [[{{{4}}}]] }}{{#if: | | [[{{{5}}}]] }} | Evaluating ADempiere{{#if: | | [[{{{next}}}]] }} ⇒

This page is incomplete. Please help adding more relavant content to the page. Create a user account in Adempiere wiki today. You can click on the edit button and start fixing the content.

(Just starting this page. Please add info if you have it. MJMcKay 11:38, 5 July 2010 (UTC))

Evaluating ADempiere for use in an enterprise will be a major task for any new user. There are a number of levels of evaluation that should be considered:

• Hardware system requirements;
• Supporting software requirements;
• Personnel requirements - how many IT staff will be required to support the software;
• Information Technology compatibility with existing systems;
• Level of complexity and implications for training and support;
• Fitness for the intended purpose:
  • Included functionality;
  • Extendability - can new required functionality be added;
  • How much "new" functionality must be developed;
• Business process mapping - can current business processes be "mapped" to the application processes or will the business have to adopt new processes to suit the software;
• Are support and consulting services available;
• Maturity of the software;
• Availability of documentation - both technical and end-user;
• Availability of the source code;
• Cost and fees - ADempiere if free but licensing costs may be only a small portion of the overall cost of an ERP implementation;
• Risks of adoption;
• Change management implications;
• Implementation process and support for legacy systems and data;
• Time to implement;