Differences
This shows you the differences between two versions of the page.
Next revision | Previous revision | ||
dev:technology:platforms:specs_desktop [2016/06/17 10:39] 127.0.0.1 external edit |
dev:technology:platforms:specs_desktop [2024/03/04 15:50] mihaela |
||
---|---|---|---|
Line 1: | Line 1: | ||
- | ====== | + | ====== Requirements for Desktop |
+ | |||
+ | This page describes the hardware requirements for iTwin Capture Manage and Extract desktop product. | ||
+ | |||
+ | The iTwin Capture Manage and Extract solution doesn' | ||
+ | However, make smart choices in relation to the volume of data to be processed and the expected performance. | ||
+ | |||
+ | ===== Screen Resolution ===== | ||
+ | |||
+ | Best layout and user experience guaranteed on screen resolution 1920 x 1080 or higher, without Display Scaling. | ||
- | 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 ===== | ===== Operating System ===== | ||
- | Orbit provides OSX and Windows, | + | For more information about Windows, Linux, and Java requirements, see [[dev:technology: |
===== Computing Power ===== | ===== Computing Power ===== | ||
- | Depending your expectations, type and volume of used resources (e.g. point cloud, imagery, base maps, ... ), here' | + | Minimum: 64 Bit OS, 16 GB ram, Quad-core. |
+ | |||
+ | ===== Software ===== | ||
+ | |||
+ | No additional software requirements. \\ | ||
+ | Required dependencies are packaged with the installation. | ||
+ | |||
+ | iTwin Capture Manage and Extract is pure Java. The Java Runtime Engine (JRE) is included with the iTwin Capture Manage and Extract installation. \\ | ||
+ | Java doesn' | ||
- | * Minimum : 64 Bit OS, 4 GB ram, Dual core processor(s) | ||
- | * Recommended : 64 Bit OS, 8 GB ram or more, Quad core processor | ||
===== Graphics Card ===== | ===== Graphics Card ===== | ||
- | Orbit desktop products use the Java Runtime Engine (JRE) and CPU to process graphic requests. \\ | + | iTwin Capture Manage and Extract uses the Java Runtime Engine (JRE) and CPU to process graphic requests. |
- | The used JRE is embedded in the Orbit Installation so you do not need seperate installations for Java.\\ | + | |
- | On Windows, DirectX should have version 9 or higher. | + | |
- | Orbit desktop products | + | iTwin Capture Manage and Extract product |
- | If no 3D graphics card is available, complex 3D requests will be processed by the JRE using CPU. | + | If no 3D graphics card is available, complex 3D requests will be processed by the Java Runtime |
- | Virtual environments (like Citrix, Virtualbox, VMWare, etc.) are still struggling to incorporate movies | + | Virtual environments (like Citrix, Virtualbox, VMWare, etc.) are still struggling to incorporate movies, the use of moving high-resolution |
- | For example, smooth viewing and roaming through high resolution spherical images or free navigating through a 3D point cloud requires an adequate frame refresh rate. These actions can be compared with watching | + | For example, smooth viewing and roaming through high-resolution spherical images or free navigating through a 3D point cloud requires an adequate frame refresh rate. These actions can be compared with watching |
When using Citrix we do advise XenApp, including video optimization and a 1GB network connection. | When using Citrix we do advise XenApp, including video optimization and a 1GB network connection. | ||
+ | |||
+ | ===== Internet Connectivity ===== | ||
+ | |||
+ | iTwin Capture Manage and Extract desktop standalone product requires online connectivity. \\ | ||
+ | |||
+ | === Orbit Online Activation === | ||
+ | |||
+ | [[https:// | ||
+ | |||
+ | The Orbit desktop Standalone products, Orbit-licensed, | ||
+ | |||
+ | === Login and Upload to Orbit 3DM Cloud === | ||
+ | |||
+ | https:// | ||
+ | [[https:// | ||
+ | |||
+ | The iTwin Capture Manage and Extract and iTwin Capture Import and Upload Tool products require online connectivity to the 3D Mapping Cloud services to log in and upload data. | ||
+ | |||
+ | === Base Maps === | ||
+ | |||
+ | [[https:// | ||
+ | |||
+ | iTwin Capture Manage and Extract and iTwin Capture Import and Upload Tool products require online connectivity to use Microsoft BING maps. \\ | ||
+ | BING maps are shipped by installation but are not mandatory to operate the application. \\ | ||
+ | |||
+ | === 3D Annotations === | ||
+ | |||
+ | [[https:// | ||
+ | |||
+ | The iTwin Capture Manage and Extract and iTwin Capture Import and Upload Tool products require online connectivity to use the 3D Mapping Cloud' | ||
+ | 3D Mapping Cloud Annotations are shipped by installation but are not mandatory to operate the application. | ||
===== Disk space ===== | ===== Disk space ===== | ||
- | No special | + | No special |
- | Much more attention is required to organize the large volumes | + | More attention is required to organize the huge volume |
- | ===== Data Storage | + | ===== Storage |
**Storage** \\ | **Storage** \\ | ||
- | Orbit requires a file-based storage system. Can be either local or network storage system that supports direct file access. \\ | + | The iTwin Capture Manage and Extract |
- | On importing | + | On importing |
- | **File Access | + | **File |
- | Orbit requests result in direct file access, performance is particularly determined by the disc speed and disc access. \\ | + | iTwin Capture Manage and Extract |
- | Slow discs or slow connections will create a bottleneck. | + | Slow discs or slow connections will create a bottleneck. |
**Big files** \\ | **Big files** \\ | ||
Line 51: | Line 94: | ||
For larger volumes of data we advise to use one optimized central storage system (e.g. raid systems on server side) conform the volume of data and expected number of users. Make a wise decision, the slowest link will define the speed of use. This could be your network and not the data storage. \\ Note that you may host the mapping data on hardware other than the Orbit desktop installation. As long as there is a fast connection (1gb or more) between both, this will be no problem. | For larger volumes of data we advise to use one optimized central storage system (e.g. raid systems on server side) conform the volume of data and expected number of users. Make a wise decision, the slowest link will define the speed of use. This could be your network and not the data storage. \\ Note that you may host the mapping data on hardware other than the Orbit desktop installation. As long as there is a fast connection (1gb or more) between both, this will be no problem. | ||
- | |||
- | ===== Internet Connection ===== | ||
- | |||
- | The Orbit desktop Standalone requires online connectivity to the Orbit License Service to operate, see [[technology: | ||
- | Orbit desktop Clients do not require online access but require connectivity with their Orbit Server, see [[technology: | ||
- | ===== Software requirements ===== | ||
- | |||
- | No requirements. | ||
- | |||
===== Example configuration ===== | ===== Example configuration ===== | ||
Line 65: | Line 99: | ||
* Viewing Purposes : \\ 64bit, dual core, intel i5 processor or equivalent, 4 GB memory, 2 USB3 connections. \\ | * Viewing Purposes : \\ 64bit, dual core, intel i5 processor or equivalent, 4 GB memory, 2 USB3 connections. \\ | ||
* Processing Purposes : \\ 64bit, quad core, Intel i7 or equivalent, 8GB Ram or more, 1TB hard disk, 2 or more USB 3 connections. | * Processing Purposes : \\ 64bit, quad core, Intel i7 or equivalent, 8GB Ram or more, 1TB hard disk, 2 or more USB 3 connections. | ||
- | * Heavy Duty Processing Purposes : \\ 64bit, quad core or more, Intel i7 or equivalent, 16 or 32 GB Ram, 500GB or 1TB SSD, 4 or more USB 3connections. | + | * Minimal |
Last modified:: 2024/03/04 15:50