Our customers know better than us what they need. The prototype phase provides them with opportunities to gain knowledge of what they really want. It often happens on the one hand that the requirements first defined are not precise enough, or are based on expectations that seem great, but are unrealistic because the workload needed to make them happen is too costly to be deployed on full scale. On the other hand, there may be ways forward that were not thought of at the beginning of the project, that may provide a viable alternative. The fact that we are using a sample of data provided by our customers help them, and us, to gradually come to the same page.
When prototyping is completed, we can provide to our customers a realistic estimate of the workload needed for full deployment.
The second phase is to set up a fully-deployed application, including update and review policies.
The fully-deployed application is made of scheduled production runs, that can be typically one per day, per week, or per month, or on demand each time a participating document is being updated. We are equipped to provide updates typically in a 4 hour interval after the modified sources are sent to us.
When we provide regular updates, we include maintenance that allows us to fix some bugs that happen generally because the source documents are not 100% compliant with the ones we have designed. Even when the document structure is the same, there may be slight changes in the content that trigger unexpected behavior from the application, and we fix it whenever such discrepancies are detected.
We also provide premium services, when requirements change, to incorporate these new requirements into the application. The rate of the changes depend on the nature of the requirement.
Because we own the software that is processing the applications, we don't charge for software development. Some of our customers may benefit from add-ons we developed because another customer has asked for it. This model lets us keep our costs low.
Our customers may instead require that we develop applications exclusively for them. In that case, we'll charge for the time it takes to d
evelop the specific applications plus a premium to guarantee that this application won't be used for others.
To help you decide the product you need, we start by designing a prototype. A prototype contains a small, but diversified, amount of information, and implements the navigation model we design with you to fit your requirements.
The prototype is a first step, that is used to finetune the requirements and the presentation of the final product and enables to have a precise estimate of the amount of effort and the cost it would take to deploy the application.
When the prototype phase is completed, we deploy the application on full scale.
We proceed on making adjustments that fit customers' specifications.
Our customers at that point know what they need.
We customize further our applications including navigation tools, search techniques to provide maximum relevance for the users.
We set up the automatic production process that will allow us to provide updates, as frequently as needed.
Updates are performed at the pace needed by each our customers. We can provide daily, weekly, or monthly updates, or on a per-case basis, as needed. Each update consists in our customers sending us their modified information, so that we can send them back a new version of the output files.
Updates can be done very quickly if documents provided to us are valid against the XML structure that they belong to. New documents, conformant to an existing structure, can be provided as part of the update.
When errors are detected, we report them to our customers so that they can be either corrected in the source documents, or on our side, with precise specifications on ways to proceed.
Updates can also be done on the knowledge layer of the topic map.
We include maintenance as part of our services. Maintenance costs guarantee our customers that our deliverables will be provided smoothly and reliably. These costs cover our ability to backup our information, redundancy in our servers to prevent failures on the Internet, and correction of bugs that may affect the production process.
Any change in the requirements will be considered a new task, and is not covered by maintenance.