One of the strengths of ZIM is that it can be adapted to your specific internal requirements efficiently,
creating a customized version that can be easily maintained.
Zylin can handle the entire adaptation process, but often
customers can perform the adaptation process themselves.
There are several levels of adaptation. The customer can choose to do the simplest adaptations
themselves, or call upon Zylin to do more advanced adaptations.
The customer decides what he wants to do himself
based upon available skills and resources.
Level 1 - Naming Processes, Projects, and Documentation
The simplest form of adaptation is to enter the names of processes, projects, and role memberships.
This is done directly in the web interface and is typically done by the customers superusers.
Another good investment is to document the installation. The goal here is to fully explain
to the normal user, how the ZIM installation should be used. This document explains
how generic ZIM components are used in the customers specific context. This can
include specific contact people, and internal customer-specific routines.
This helps the users to correctly register information, such that the reports
yield the best possible information and the handling of incidents works
Documentation of ZIM focuses on how a ZIM installation is built up, and is
not suitable for end users to understand how ZIM should be used in their
Level 2 - Configuration in the Web Interface
From the web interface, superusers can perform other adaptations such as deciding which
fields are compulsory and which should be present when registering incidents.
Level 3 - Standard Configuration Files
At this level a deeper understanding of ZIM is required. Typically
Zylin will create a draft of these configuration options, and superusers
and IT resources at the customer site will perform the changes.
Examples of level three complexity include more specialized handling of how incidents are registered,
specific policies for passwords, and the adaptation of customer-specific jargon.
Level 4 - Custom Development
Custom development is the most flexible, but also the method that requires the most
involvement from Zylin. Usually the customer will find that most adaptation
can be handled by the methods above.
In custom development, Zylin strives to ensure that the solutions are robust, and easily maintained,
such that the customer will not become stranded on an earlier version, or
that support or production environments become unwieldly.
Even at this level, the customer can choose to perform most of the work himself. The
hardest part is to find out precisely what changes are required. If the customer
has written a good user manual, Zylin's involvement will be greatly reduced.