Orbit Core Server Framework

EOS is short for 'Enterprise Orbit Server'.

EOS is Orbit's core server technologies for central storage, management and maintenance of corporate spatial resources, users & permissions, workspaces and licenses. Local, corporate wide or for internet/intranet use.

All Orbit products are able to access remote EOS resources and instantly become client/server applications, providing access to corporate resources.
Most Orbit products are available both in Standalone as in Client-Server setup.
EOS is also the backbone of Orbit publishing extensions for the web and mobile devices.

The installation of the Orbit Server is always in cooperation with the Orbit Support Team.

The EOS Console is the user interface for the administrator to manage the Orbit server, Datasets, Users and User groups, Workspaces, Extensions and Licenses:

• Orbit EOS Console

• Orbit Enterprise Service
• Orbit Server side Services
• Orbit License Server
• Orbit desktop Client Installation

• Raise available Memory for Orbit

• Orbit Client Server Schemes
• Roles and Permissions

• Datasets & Workspaces

Configuring GIS resources into EOS, makes the dataset real time available for multiple concurrent users of any connected Orbit client.

It is possible for multiple users to add, edit and remove dataset objects and to complete object attribute data without overwriting each others work.
The Orbit EOS Server reads and writes. All dataset update requests are treated one by one by the server. None of the client computers need to have direct access to the server resources.

Its only possible to update the spatial component and attribute component. Neither the dataset structure nor the dataset legend can be managed by multiple users at the same time.
To change its structure or the legend is necessary to have local access to the resource .

Multiple operators can work simultaneously using the structures as prepared by the administrator :

• Only the administrator is able to define the structures on how to work.
• All operators are forced to follow the structures as prepared by the administrator.

Advantages are numerous :

• Only one person must be fully trained to manage and prepare resources.
• Only one person will define the workflow which results in a uniform output.
• One effort can be re-used by all operators : one dataset structure, one dataset legend, one dataset list.
• This extremely reduces time needed to train operators
• This reduces time lost by inefficiency of operators
• …

Using the Orbit EOS console the administrator manage remotely the Orbit EOS configurations :

• Manage Resources and set Permissions
• Manage Users and Usergroups and set private Roles and Permissions
• Manage Workspaces with DatasetList and Extensions

EOS makes it possible to manage and protect your resources (Permissions) and to define the level of use for users (Roles).
Read more about it on this page :Roles and Permissions