Kramer Electronics K-Touch - Manual (Page 5)

K-touch Admin - System Overview and Workflow 3
After you become more familiar with the system, you may find that an alternative
workflow suits you better. This is, of course, fine.
There are several important things to remember:
1. K-touch Admin is a tree-based server, so every section has i
ts own “parent”
(from whom you order licenses
) and several types of “child” entities:

Dealers - to whom you sell only licenses but not configured projects (if
you are allowed to do so). Dealers can also be used to divide the
licenses between two different offices of the same installer and in a
similar usage where you want each entity to have its own stock of
licensees. In order for a Dealer to be able to add Dealers under his
own server section, this option should be opened for him by his
“Parent” dealer
 Customers
– to whom you open design projects and sell a configured
installation, based on an order for configuration and programming.
Licenses sent to a customer’s projects can be “taken” back by the
dealer

Users
– each server section can be accessed by several users from
the same dealer. For example, several tech personnel, one purchaser
and two sales persons; each can have their own user name and
password with different permitted operations they can perform on
Admin, depending on their role in the organization.
2. The system is based on selling licenses – one license per touch device. You
order licenses through your normal ordering process and licenses are
subtracted from your account in two ways:

You sell/transfer them to one of your own dealers
 You assign them to a project of your customers
3. Once you use a license to download the screen design to the device for the
first time, you can re-sync the device to update the screen design of this
project. However, if the device is broken or misplaced, you cannot reuse the
license. You must use a new license to sync another device to the same
project.