In the initial phase of the construction of an FCS-Platform, the
Platform Administrator (pAdmin) takes the key role. Before we go any
further with the individual functions and options, it is important to
understand the differentiation between the roles of the
System-Administrator ("sAdmin), Platform-Administrator ("pAdmin), and
the normal User ("User):
System administrator ("s-admin")
Platform administrator ("p-admin")
Users
FCSs functional hierarchy can be illustrated using an analogy of the construction and use of a house:
- The purchaser (designer) announces what the house (in our case, the platform) should look like.
- The system administrator (builder) transfers a ready-made house (platform) to one or more platform administrators (new owners).
- The platform administrator sets the house rules, divides the users
into groups, sets the password for each user, and can also structure
the arrangement of the house (the platform arrangement).
- A few users move throughout the house, inhabit the house, help with its arrangement, expand or change it, etc.
Forms of use: both ASP and self- installation are possible.
FCS offered as ASP solution: The
server remains located at factline, furthermore, the functions of the
system-administrators are taken over by factline. The system can also
be installed on the server of the customer over an Intranet or the
Internet; in this case the customer is the system administrator.
-> proceed to:
|
