General System Requirements mymcs Apps

Size: px

Start display at page:

Download "General System Requirements mymcs Apps"

Bernice Lang
5 years ago
Views:

1 General System Requirements mymcs Apps Document status Document owner LIVE Thomas Verdyck Goals Get insight on the minimal hardware & software requirements needed for running an app of the mymcs Software suite. Help the support team to easily tackle performance related service tickets. Help Sales staff, Project engineers and MCS customers to define requirements during (pre) project scoping. Recommended devices MCS does not recommend any specific device for using mymcs apps. The scope of test devices MCS uses to develop high qualitative apps changes dynamically every month based on worldwide benchmarks of typical and popular devices. This way we makes sure our apps are always fully tested on a wide range of devices. All apps which comply to the rules described below are theoretically ready for use. MCS however does recommend running a small scale proof of concept before acquiring large numbers of devices, especially when opting for devices. vendors are free to implement their own version of the operating system without being bound to any common standards. In practice this means obscure vendors phones and special phone editions of common vendors should be tested thoroughly. Common market devices are always compliant to these rules. Software Requirements (OS version) Operating system Windows - Phone Version 4.4.X and up 9.X and up Windows Phone 8.1.X Windows 10 mobile Windows - Tablet Windows 8.1 PRO (at least Update 1 must be installed) Windows 8.1 Enterprise Windows 10 PRO & Enterprise Software Requirements (Other) Operating system Windows - Phone Windows - Tablet Comments Users must allow installation of apps from unknown sources. (Allow installation of non-market apps.) Users must specifically trust "MCS NV" as a trusted app developer in order to launch apps. The mymcs Dashboard app must be installed prior to the installation of any other app. The mymcs Dashboard app manages tasks in the background for all future Windows Phone mymcs apps. MCS must be trusted as app developer by adding a workplace account for MCS. The user's tablet/desktop must be added to the company s Active Directory domain in order to run mymcs apps. The AD user must at least have local admin rights in order to complete the installation. Alternatively, the apps can be installed via distributed deployment systems like: Active Directory Group Policies, Device Management tools etc.

2 More information about the app installation process can be found in the app installation manuals. Hardware Requirements Benchmarking (AnTuTu Benchmarking app) General Score UX - Data Secure UX - Data Process UX - Image Process UX - I/O Performance RAM (general) CPU Mathematics CPU Common Use CPU Multi-Core CPU Model CPU cores: 4 CPU frequency: 1,4 MHz RAM 1,5 GB Resolution (phone) 720 X 1028 (5") Resolution (tablet) 768 x 1280 (7") DPI 300 dpi Mobile Connection 3G HSDPA 850 / 900 / 1900 / 2100) 3G connection (or higher) is highly recommended. WLAN Wi-Fi a/b/g/n Wifi connection is highly recommended. Benchmarking (AnTuTu Benchmarking app) General Score

3 UX - Data Secure UX - Data Process 750 UX - Image Process 190 UX - I/O Performance RAM (general) CPU Mathematics 800 CPU Common Use CPU Multi-Core CPU Model Dual Core 1 GHz (Apple A5) RAM 512 MB Resolution (phone) 640 x 960 (3.5") Resolution (tablet) 768 x 1024 (7,9") DPI 330 Mobile Connection 3G HSDPA 3G connection (or higher) is highly recommended. WLAN Wi-Fi b/g/n Wifi connection is highly recommended. Windows Benchmarking (Basemark OS II) Overall 470 System 590 Memory 880 Graphics 230 Web 400 CPU Model Quad Core CPU (ARMv7) RAM 512 MB Resolution (phone) 640 x 960 (3.5")

4 Resolution (tablet) 768 x 1024 (7,9") Mobile Connection 3G HSDPA 3G connection (or higher) is highly recommended. WLAN Wi-Fi b/g/n Wifi connection is highly recommended. Data usage mymcs Room Display Operation Data usage Real life example for a day for 5 meetings Refresh calendar (assuming 5 meetings in a day) 6KB For a refresh interval of 5 minutes, the app will refresh the screen (60*24)/5 = 288 times in a day. Book meeting using MRD End meeting manually Extend meeting 100KB + 6KB 20KB + 6KB 30KB + 6KB Total usage= 6KB*288 = 1.8 MB per day Assuming 5 meetings are booked per device per day, the total usage will be around 50 0 KB per day Assuming 3 meetings were explicitly ended via the device ended before the scheduled end time, total data used will be 100KB per day Assuming 2 meetings per day are extended via the device, total data usage will be 100 KB per day Conclusion Taking the above example of daily usage as an approximate, the monthly data usage will be 2.5 MB * 30 days = 75 MB per month. If we take into account that the usage varies considerably per device, and accounting for data usage during initial setup, a MB per month data plan will be more than sufficient. If the planned usage for the customer is differs much from the above example, data usage can be calculated based on the data usage volumes mentioned above. Server & Network Requirements General The mymcs Mobile apps require a direct connection to the mymcs Web Portal. The apps handle authentication and other communication via web service hosted as part of the mymcs Web Portal installation. It is important to take the following into account: 1) Intermediate (3rd party) login methods implemented for additional security and/or SSO purpose ( e.g. Windows Authentication through NTLM or any others) are not supported. In case such an intermediate step in authentication is required, MCS can create a custom app which specifically supports the required 3rd party authentication. Please contact your account manager for more information. 2) The app needs to be able to communicate with the mymcs Web Portal. When the mymcs Web Portal is deployed on an internal network which is not accessible from outside the network, the app will only be able to connect successfully when residing in the same network. 9.0

5 App Transport Security (ATS) In 9 Apple is pushing for more security in all apps, and will no longer allow the use of http. When a user attempts to make a connection using http, the system will automatically use https instead. If the https version is using security that Apple considers weak, or the server just doesn t support https at all, the request will fail. Apple's expectations for secure connections: Transport Layer Security (TLS) must be at least version 1.2 Connection ciphers are limited are limited to those that provide forward secrecy Certificates must use at least an SHA256 fingerprint with either a 2048 bit or greater RSA key, or a 256 bit or greater Elliptic-Curve (ECC) key. Read more here: Questions Below is a list of questions to be addressed as a result of this requirements document: Question Outcome Not Doing

General System Requirements MCS Apps

General System Requirements MCS Apps Document status Document owner LIVE Thomas Verdyck Goals Get insight on the minimal hardware & software requirements needed for running an app of the MCS Software suite.