documentation - holo|onecustom integrations custom integration describes the integrations that are...

3
Technical Documentation Structure The ’sphere’ consists of backend server systems and the individual modules (frontend applications), with which the users interact. These include Expert, Workspace and Task. The frontend applications are installed for various operating systems through their respective application stores and installers. Updates are delivered through the same channels, namely: Windows: Windows Installer HoloLens: Microsoft Store Android: Google Play Store iOS: App Store Mac OS Web Alternatively, holo|one also offers the option of setting up all applications directly for our custo- mers. Standardized Integrations Data integration describes the bi-directional connection of information systems already in use within your company, with the ones provided by holo|one. In order to minimize the effort needed for integra- tion, holo|one offers a standardized process for connecting to a selection of common services and applications. Custom Integrations Custom integration describes the integrations that are not included in the list of standardized systems currently supported. These require integrations to be specifically developed for a single company. Custom integrations can be provided by holo|one, but are not included in the licensing fees. These integrations are included in the licensing fee for ‘sphere’, and only have to be configured by the customer. Currently offered standard integrations: The server systems are provided, maintained and hosted by holo|one via Microsoft Azure. These are ‘invisible’ to the customer and responsible for functions such as data storage, connection between different devices and carrying out complex computations. Systems Employees EXPERT WORKSPACE TASK Customer Server Devices - Azure Active Directory - Salesforce - Microsoft OneDrive - Salesforce - SAP User Administration Data Integration

Upload: others

Post on 19-Jul-2020

15 views

Category:

Documents


0 download

TRANSCRIPT

Page 1: Documentation - holo|oneCustom Integrations Custom integration describes the integrations that are not included in the list of standardized systems currently supported. These require

Technical Documentation

StructureThe ’sphere’ consists of backend server systems and the individual modules (frontend applications), with which the users interact. These include Expert, Workspace and Task.

The frontend applications are installed for various operating systems through their respective application stores and installers. Updates are delivered through the same channels, namely:

• Windows: Windows Installer• HoloLens: Microsoft Store• Android: Google Play Store• iOS: App Store• Mac OS• Web

Alternatively, holo|one also offers the option of setting up all applications directly for our custo-mers.

Standardized IntegrationsData integration describes the bi-directional connection of information systems already in use within your company, with the ones provided by holo|one.

In order to minimize the effort needed for integra-tion, holo|one offers a standardized process for connecting to a selection of common services and applications.

Custom IntegrationsCustom integration describes the integrations that are not included in the list of standardized systems currently supported. These require integrations to be specifically developed for a single company. Custom integrations can be provided by holo|one, but are not included in the licensing fees.

These integrations are included in the licensing fee for ‘sphere’, and only have to be configured by the customer.

Currently offered standard integrations:

The server systems are provided, maintained and hosted by holo|one via Microsoft Azure. These are ‘invisible’ to the customer and responsible for functions such as data storage, connection between different devices and carrying out complex computations.

Systems Employees

EXPERTWORKSPACETASKCu

stom

erSe

rver

Dev

ices

- Azure Active Directory- Salesforce

- Microsoft OneDrive - Salesforce- SAP

User AdministrationData Integration

Page 2: Documentation - holo|oneCustom Integrations Custom integration describes the integrations that are not included in the list of standardized systems currently supported. These require

CompatibilityOur applications are compatible with a wide range of operating systems and devices. It is possible to use our solution on nearly all mobile devices, desktop computers and AR glasses. The use of different devices is possible, both within a compa-ny and across different companies, allowing for easy and effective collaboration.

BandwidthFor the connection of two or more devices when using Expert or Workspace, a working internet connection is required. To ensure the effective use of our software, even in remote areas, we value the usage of as little bandwidth as possible.

For minimum requirements, our solution needs only 0.2mbit/s and is usable starting with 2G. For optimal usage, the software requires 1.0-1.5mbit/s, which is only a fraction of a common 3G+ band-width. Data rates exceeding these thresholds have the advantage when it comes to downloading larger files, such as videos or complex 3D models.

Currently, we support iOS, Android, Windows, and MacOS. Support for Magic Leap One headsets will be coming in 2019. Our software can also be run as a platform independent browser solution. In order to make full use of the functions of our software, we recommend the use of specialised

Augmented Reality glasses, such as the Microsoft Hololens. These devices rely on complex sensor arrays and powerful hardware in order to carry out demanding spatial computing tasks.

Examples include connections to Internet of Things (IoT) applications, other sources of sensory data or to a firm‘s in-house ERP-System (such as SAP).

In order to guarantee quick and reliable integra-tions between our data and systems with those of our clients, we work alongside the Swiss company JLS DIGITAL AG.

JLS specializes in data integration and employs over 70 trained experts. In partnership with JLS, we are able to conduct any custom integration quickly and reliably.

Possible individual Integrations:

Sensor Data

Personnel Management

Database System

Other Information Systems

Dat

a ra

te (

mbi

t/s )

0.8 mbit/s:Full HD

0.32 mbit/s:896 x 504 px (= Hololens Standard)

0.2 mbit/s:640 x 320 px

2G 3G 4G 4G (LTE) 5G

0.256 0.375

3G+ (HSDPA)

7.2

HSDPA+

42

150

450 10 k

Page 3: Documentation - holo|oneCustom Integrations Custom integration describes the integrations that are not included in the list of standardized systems currently supported. These require

Servers and Hosting All data is saved via Microsoft Azure which serves a three-fold role as a cloud computing platform: 1) Infrastructure-as-a-Service, 2) Platform-as-a-Ser-vice, and 3) Software-as-a-Service. Azure is furthermore divided into six different functions. Among these, two functions are of key relevance to us: Computing and Storage.

Computing describes the opportunity to carry out CPU-intensive tasks on external servers that are hosted by Microsoft. A sample use case for this is to automatically convert CAD-Models from clients into AR-compatible models that are supported in our applications. Likewise, it is also possible to carry out these operations on a customer‘s servers, should this be requested.

Storage refers to how the data can be permanent-ly saved in databases which are on servers hosted by Microsoft or otherwise.

Computing through Azure

Azure Server

Customisedcomputing

Customer Server

As this is part of their core business, Microsoft Azure is exceptional concerning uptime as well as data security. Azure guarantees an uptime of 99.9% (which leads to a yearly downtime of only 8 hours and 46 minutes, which very little in compari-son to competitors). This is valid for computing, as well as storage.

Microsoft also holds more data security certificates than any other cloud provider. Microsoft Azure adheres to a large number of international and industry specific data security standards, among them ISO 27001, HIPAAA, and many more. Several different impartial instances such as the British Standards Institute regularly check that these standards are upheld.

Concerning our applications, Microsoft’s only role is the provision of physical server hardware on which holo|one’s software is installed. Upon customer request, all server systems can be set up on servers of their choice, including compa-ny-owned servers and internal networks.

Classified Environments & DataWhen dealing with sensitive information and files, holo|one offers the option to require files to be whitelisted in order to be available in AR. File management and whitelisting can be done in our Management Portal web application.

When using Expert in classified environments, it is further possible to restrict the camera feed around sensitive workspaces. Users are able to spawn holographic barriers around themselves, prior to and during calls, effectively blocking out part of the camera feed. Barriers are treated as common 3D models and are transmitted with maximum opacity. They may only be manipulated or deleted by the user who placed them.

Data SecurityIn order to ensure absolute data security we take several measures:

Every data-based communication is encrypted at all times. Encryption happens over the common-place Hypertext Transfer Protocol Secure (HTTPS), which ensures that no one is able to ‘listen in’ on the communication taking place. Furthermore, all databases are set up behind an individually customizable firewall, which prevents external influence. Only internal communication is possible.

Our Expert module, which transfers audio and video data, uses a peer-to-peer technology, which means that all data is transferred directly from one device to the other – there is no server in the middle at all, internal or external. There is no place where data could be saved or intercepted with malicious intent. This data transfer is also safely encrypted and not viewable by third parties.

Sensitive data is never saved in clear text format. Through hashing and salting, credentials such as passwords and other login data are encrypted and rendered unreadable, in case of unauthorised access.

Aarauerstrasse 255600 Lenzburg

+41 62 521 37 [email protected]