| |
|
IT Departments are busy places. How do we know this? well two of the people involved in writing
the software ran IT Departments - not only in Engineering Companies but also in
Legal firms.
A common problem is software that drains IT resources. We found that many
support calls to an IT Help desk can be eliminated by training and, for when people forget their training
- well documented, structured manuals.
Cogitar QCD Is designed on the following principles -
|
|
 |
|
A reduced IT overhead. |
|
|
Saving IT teams answering repetitive "easy" calls. |
|
|
Low maintenance - updates to be fast - and done in one place! |
|
|
Easy to tell from a users desktop what problem has been encountered. |
|
|
To not need a 24/7 IT presence. |
|
| |
|
|
| |
| |
|
This is a simple example of the level of
refinement we have built into the package.
Those who work with databases will have noticed
what this means.
If you don't know what it means, don't worry! - simple.
|
 |
|
|
|
|
R = Read |
|
|
|
U = Update |
|
|
|
I = Interrogate |
|
|
|
D = Delete |
|
|
|
All the above are database actions - on many packages
the IT Team would have to do a number of things to find out
this information.
But from a users desk, (or shadowing a user
if you work thin client) you can see which permissions are held
by the user. No going back to the admin console and having
to check.
Sounds a very small thing to be selling a product on?
It is not, its about an IT specialist been able to
eliminate a number of problems at one glance.
|
|
| |
|
|
| |
| |
|
Keeping support calls down is vital!
That's why we have invested time and money into the manuals.
Many manuals are long text documents, seen as
PCs moved away from text over
10 years ago with the adoption of GUI
why should the manuals to support GUI software,
have not done the same?.
As you can see - graphics and simply presented
information mean that when the IT Department
is not available the user can find and answer.
|
 |
|