The cost for implementation is a one-time payment, the hosting is a monthly fee.
A | B | C | D | E | F | G | |
Nr. | (all prices in CNY) | internal
use (only AHK employees are using this module) |
external
use (non-AHK users are using the system) |
use on website | modified module | ||
Modules | implementation |
hosting | implementation | hosting | implementation | hosting | |
0 | contactmgr | - | - | - | - | - | - |
1 | bookmarks | 2000 | + 20 | + 1000 | + 10 | + 1000 | + 20 |
2a | calendar (view mode) | 2000 | + 20 | + 1000 | + 10 | + 1000 | + 20 |
2b | calendar (multi user) | 4000 | + 40 | + 2000 | + 20 | + 2000 | + 40 |
3 | news | 4000 | + 40 | + 2000 | + 20 | + 2000 | + 40 |
4 | forum | 4000 | + 40 | + 2000 | + 20 | + 2000 | + 40 |
5 | knowledge base (kb) | 4000 | + 40 | + 2000 | + 20 | + 2000 | + 40 |
6a | DMS (view mode) | 4000 | + 40 | + 2000 | + 20 | + 40 | |
6b | DMS (multi user) | 8000 | + 80 | + 4000 | + 40 | + 80 | |
7 | 6000 | + 60 | + 3000 | + 30 | + 60 | ||
8 | infolog | 8000 | + 40 | + 4000 | + 80 | + 40 | |
9 | sitemgr | - | - | 10000 | + 100 | + 200 | |
10 | registration |
- |
- |
1000 |
+
10 |
+ 20 |
The AHK Company Directory has already the modules
and the basic hosting.
For this project we can use the knowledge base (KB).
If only AHK staff is working on it and if no modification is needed we calculate 4000 CNY for implementation and rise the monthly hosting fee by 40 CNY. The hosting part is because of updates. For each module we have to do some updates etc.
If external users (e.g. many companies, GTZ, journalists...) are working with kb (e.g. read and write articles) then we add 2000 CNY for implementation. This is because we cannot train external users as well as AHK personnel. As soon as people are working with the system who have no training we must improve the usability of the system. Depending on the users we probably will have more questions and problems. AHK users can ask a colleague, but "single" users in certain companies cannot.
If the articles appear on the website we add another 2000 CNY. This is because we have to improve the usability even more. The template for internal use is more "standard" (e.g Byron) than the individual template (e.g. AHK) on the website. The creation of the template is not included In this surcharge, it is only to publish the articles in the (existing) website template without bugs or usability problems.
(CNY) | implementation | hosting |
(basic system installation, currently GCD) | (another contract) | (another contract) |
kb standard version | 4000 | + 40 |
use on the website (the articles are published on the website) | + 2000 | |
sub-total | 6000 | + 40 |
e.g. GTZ and other companies have access to kb for writing articles | + 2000 | + 20 |
sub-total | 8000 | + 60 |
Modification, e.g. automatic creation of an abstract (probably 4000) | 4000 | + 40 |
Modification, e.g. publication for different target groups* (probably 2000) | 2000 | |
Modification... | ||
Modification... | ||
sub-total | 14000 | + 100 |
* This feature is already available, but therefore you have to login as 2 different users which is not convenient (you need 2 usernames).
As many improvements are not clear now, we cannot calculate them today. I guess that most of the modules already meet the requirements by 80 %. So I recommend to start with the module "as is". We can try to improve a module before offering it to production mode, but this is difficult, time-consuming and expensive. Sometimes the improvements are not needed or even bad. Usually it is better to let people work a certain period of time on the standard version and then improve the module according to the results of the trial period. The user gets the feeling what he needs. And improvements which are really needed are easier to calculate.
Furthermore improvements are easier to calculate if there is an expected revenue. E.g. we can create special member or subscriber areas. You can compare the costs for implementing this feature with the expected revenue by charging the visitors (members or subscribers). Or we offer a RSS newsfeed etc.The important part at the beginning is e.g. the way the data (documents, articles...) is stored. We strongly recommend to use open standards such as html, open document, text, png, jpg... E.g. if we use the knowledge base for storing articles we have them all as html files. With or without modification of the kb we can access the articles in future. The same principle we use for the LDAP database (companies contacts). The data format is open standard and we didn't make a proprietary format out of it. So you can use all contacts in future with other software or systems. The data format is independent from special features (modifications) of the contactmgr module.
The basic egroupware system is growing and improving daily. Our special modules too and we still have a long list of ideas and improvements, even if we realise them step by step. For many improvements it is only a matter of time that we can offer them. In this case some improvements are available for a very low price. This is, because we must reduce the number of different modules and versions sometimes in order to make the maintenance easier.Please have a look at the kb in the GCD system. We will help you to put some articles there and to make soem trials that you can get the feeling if this way of storing articles is meeting your requirements.
Training - if needed - is always extra. Same with documentation, manuals and tutorials. Usually we will provide the customer with standard tutorials which show how to use the modules, and with guidelines which include standard settings and recommendations. Optional we can create a tutorial exactly on your system, for your users and for your purpose.