====== IT Requirements for Orbit Server =====

The Orbit Mapping solutions do not require special hardware. \\  
Do make smart choices in relation to the volume of data to be processed and the desired performance. \\

===== Operating System =====

Either Windows or Linux, see : [[112:technologies:platforms:index|]].

===== Computing Power  =====

Depending your expectations, type and volume of used resources (e.g. point cloud, imagery, base maps, … ), number of concurrent users and the data network configuration, here's a guideline :

Orbit Feature Production Server 
  * Minimum : 64 Bit OS, 8 GB ram, Quad core processor
  * Recommended : 64 Bit OS, 16 GB or more ram, Quad core processor

Orbit Publisher Server (single unit)
  * Minimum : 64 Bit OS, 8 GB ram, Dual core processor
  * Recommended : 64 Bit OS, 32 GB or more ram, Quad core processor or higher
  * Notes :
    * Required RAM for Orbit Publisher can be calculated at about 7.5 MB per concurrent user (per image).
    * Multiple scalable single units can be combined using a load balancer.

===== Graphics Card =====

No requirements.

===== Data Storage and File Access =====

The Orbit Server will require file access. 
One exception for mobile mapping resources were data access can be either direct client file access or served by the Orbit Server. 

===== Internet Connection =====

The Orbit Server requires online connectivity to the Orbit License Service to operate, see [[112:technologies:licenses|]]. \\
===== Network Connection =====

^  Network speed  ^^^^^ ^  Copy time  ^^^
| Units | Gigabit per second | Megabit per second | Kilobit per second | kilobytes per second | | file of 500 kB | file of 1 MB | file of 5MB |
| ::: | Gbit/s, Gb/s, Gbps | Mbit/s, Mb/s, Mbps | kbit/s, kb/s, kbps | kB | | compressed | LB3 | LB5 |
| 1kb | 1 *10-6 | 1*10-3 | 1 | 0.125 | | 66 minutes | 136 min | 680 min |
| 100kb | 0.000 8 |0.8 | 800 | 100 | | 5 seconds | 10.2 seconds | 51.2 seconds |
| 1mb | 0.001 | 1 | 1 000 | 125 | | 4 seconds | 8 seconds | 41 seconds |
| 100mb | 0.1 | 100 | 100 000 | 12 500 | | 0.04 seconds | 0.08 seconds | 0.41 seconds |
| 1gb | 1 | 1 000 | 1 000 0000 | 125 000 | | 0.004 seconds | 0.008 seconds | 0.041 seconds |

The network speed units are expressed in Bits per second (no Bytes). In the rightmost columns the equivalent copy time is calculated for one file e.g. a panorama image. Note that this is in ideal conditions, only if the entire network capacity can be used.

=== Connection between Orbit Server - desktop Client ===

**Network Connection** \\
In a production environment it is important to have a fast network connection between Orbit Clients, 
the Orbit Server and, if applicable, the data server.
At least a 1 GBit connection is recommended. 

**Port** \\
Orbit Server - desktop Client communication requires one port to operate, default configuration port 1100. \\
If required this can be reconfigured. 

=== Connection between Orbit Publisher - publishing Clients ===

**Internet/Intranet Connection** \\
When hosting a Publisher, take the Server upload and Client download speed into account relative to the average size of the images and the amount of images to be served within a given time frame. 

**Port** \\
Orbit Publisher (server) - publishing Client communication requires one port to operate, default configuration port 1100. \\ 
If required this can be reconfigured, but we do advise to use a reverse proxy : [[112:technologies:platforms:specs_publisher|]]
\\ 
===== Software requirements =====

**Flash** \\
Flash 11.0 or higher is required to load the server management tool "EOS Console". The EOS Console can be started via http on any connecting device. 

**Database** \\
For Asset Inventory Feature Production only. \\
When doing Feature Production in Client-Server a single central database is required. \\
Orbit supports any by Java [[112:technologies:basic_concepts:spatial_databases|]]. Opensource and community databases are supported as well, MySQL is advised. 


===== Example Configurations =====

==== Orbit Feature Production Server ====

  * Server : 64bit, 12 to 16GB Ram \\
  * Client : 64bit, Intel core i3 / i5 or equivalent \\
  * Network connection : minimum 1 gigabit, recommended 10 gigabit or more. \\

==== Orbit Publisher Server ====

Panorama and Oblique Publisher for 100 concurrent users :
  * Requires 500 MB network throughput / second
  * Requires 4 GB RAM

Above specs are only for Panorama or Oblique image services. Other server activities that require power and RAM :
  * Map data, image and vector resources
  * Any use of Point Cloud
  * General services

Total required hosting hardware - for 100 concurrent users :
  * Minimum 8 GB RAM, recommended 12 GB or more
  * Minimum 1 GB LAN or higher, direct to backbone
  * Robust and high performance RAID discs