Hid Mobile Access® App User Guide

HID MOBILE ACCESS® APP USER GUIDE PLT-02077, Rev. A.2 May 2020 HID Mobile Access® App User Guide hidglobal.com Copyright © 2014 - 2020 HID Global Corporation/ASSA ABLOY AB. All rights reserved. This document may not be reproduced, disseminated or republished in any form without the prior written permission of HID Global Corporation. Trademarks HID GLOBAL, HID, the HID Brick logo, the Chain Design, HID Mobile Access, and Seos are trademarks or registered trademarks of HID Global, ASSA ABLOY AB, or its affiliate(s) in the US and other countries and may not be used without permission. All other trademarks, service marks, and product or service names are trademarks or registered trademarks of their respective owners. Revision history Date Description Revision May 2020 Updates implemented: A.2 n Section 2.2.2 App Settings. Updated section. n Section 2.2.3 Recommended mobile device settings. New section for iOS device settings. n Section 2.3 Set up your Apple Watch for Mobile Access. Updated section. n Section 3.2.2 App Settings. Updated section. n Section 3.2.3 Recommended mobile device settings. New section for Android device settings. n Section 3.3 Set up your Android smartwatch for Mobile Access. Updated section. n Section 4.3 Open an access door using an Apple Watch. New section added. n Section 4.4 Open an access door using an Android smartwatch. New section added. n Section 6 Mobile Access information. Added data consumption figures for Mobile Access App settings. n Updated all reader images for HID® Signo™ readers. Contacts For additional offices around the world, see www.hidglobal.com/contact/corporate-offices. Americas and Corporate Asia Pacific 611 Center Ridge Drive 19/F 625 King's Road Austin, TX 78753 North Point, Island East USA Hong Kong Phone: +1 866 607 7339 Phone: +852 3160 9833 Europe, Middle East and Africa (EMEA) Brazil 3 Cae Gwyrdd Condomínio Business Center Green Meadow Springs Av. Ermano Marchetti, 1435 Cardiff CF15 7AB Galpão A2 - CEP 05038-001 United Kingdom Lapa - São Paulo / SP Brazil Phone: +44 (0) 2920 528 500 Phone: +55 11 5514-7100 HID Global Technical Support: www.hidglobal.com/support. 2 May 2020 Contents HIDMobileAccess®AppUser Gu ide 1 Overview 5 2 iOS devices 7 2.1 Download and register the iOS App 7 2.2 App menu items and settings (iOS) 9 2.2.1 App menu options 9 2.2.2 App Settings 10 2.2.3 Recommended mobile device settings 11 2.3 Set up your Apple Watch for Mobile Access 12 2.3.1 Add the Mobile Access complication to your Apple Watch 13 3 Android devices 15 3.1 Download and register the Android App 15 3.2 App menu items and settings (Android) 17 3.2.1 App menu options 17 3.2.2 App Settings 18 3.2.3 Recommended mobile device settings 19 3.3 Set up your Android smartwatch for Mobile Access 20 4 Open doors with HID Mobile Access 21 4.1 Open an access door using Tap 21 4.2 Open an access door using Twist and Go 21 4.3 Open an access door using an Apple Watch 22 4.4 Open an access door using an Android smartwatch 23 5 User Feedback 25 6 Mobile Access information 27 6.1 General 27 6.2 Mobile Access data consumption 27 6.2.1 iOS mobile devices 27 6.2.2 Android mobile devices 27 May 2020 3 PLT-02077, A.2 This page is intentionally left blank. 4 May 2020 Section 1 1 Overview HID Mobile Access® complements your company's existing access control solution by extending access control functionality to smart devices, allowing end users to securely and conveniently enter workplace locations using their mobile devices (smart phones, tablets, or wearables). When a user approaches a reader, the following modes of interaction can be performed with their mobile devices for access: n Tap: The mobile device is brought very close to, or touching, the reader (a similar user experience to using a physical credential). n Twist and Go: The mobile device holder initiates access by twisting the mobile device in a sharp 90 degree rotation in either direction (a similar motion to using a physical door handle). n App Specific: This entrance opening mode is specific to an application, for example, widget opening from a wearable such as a smartwatch. Tap Twist and Go May 2020 5 PLT-02077, A.2 This page is intentionally left blank. 6 May 2020 PLT-02077, A.2 iOS devices 2 iOS devices The following sections apply specifically to iOS mobile devices. For information on Android mobile devices see Section 3 Android devices. 2.1 Download and register the iOS App 1. Ensure your mobile device is connected to the internet (either via mobile data network or Wi-Fi) during device registration and Mobile ID (MID) delivery. 2. Open the invitation email you received from your site administrator, inviting you to participate in HID Mobile Access®. 3. Follow the instructions in the email to download the HID Mobile Access app from the App Store. 4. Open the Mobile Access App on the mobile device. 5. Tap Yes to accept the Privacy Notice and License and User Agreement. May 2020 7 iOS devices PLT-02077, A.2 6. Open the Mobile Access invitation email on the device and tap the invitation link. The invitation code will be automatically entered in the Mobile Access App User identification screen. Alternatively, to manually enter the invitation code at a later time, select Settings > Enter Invitation Code from the Mobile Access App menu options screen, see Section 2.2.1 App menu options. Note: Zero and one (0 and 1) are not used in the invitation code, to avoid confusion with the letters O and L. 7. Tap Register. 8. In order to allow access for your device, the site administrator will issue a MID, visible when you open the Mobile Access App on your device, and add you to the site Access Control System. Note: If a MID is not issued to your device and/or you are not added to the site Access Control System during the registration process then your site administrator will need to do this before the device can gain access. 8 May 2020 PLT-02077, A.2 iOS devices 2.2 App menu items and settings (iOS) 2.2.1 App menu options The following provides a description of the menu options available in the app. 1. Open the Mobile Access on your mobile device. 2. Tap the Menu icon [ ] to access the Mobile Access options screen. Menu options Description Home Access your mobile ID badge home screen Enter Invitation Code Enter the invitation code provided via email, to set up the device Licenses Displays the privacy policy, license and user agreement, and third-party licenses Settings Used to adjust the HID Mobile Access configuration settings About Provides application information, endpoint information, and device information Show warnings Select to show active notification warnings on the home screen Access log Provides a log of attempted and successful communication Video Tutorials Access to Tap, Twist and Go, and Smartwatch tutorials Contact Provides access to Mobile Access FAQs and the HID Mobile Access Solutions page Email diagnostics Use to email diagnostic information May 2020 9 iOS devices PLT-02077, A.2 2.2.2 App Settings The following provides a description of HID Mobile Access App settings (defaults are indicated). On the menu options screen, tap Settings to access the settings options. Setting options Description Allow Mobile Access when Tap to access options to allow mobile access when: App is in the foreground, the Device is unlocked, or Always (default setting) Twist and Go Enables/disables the Twist and Go function on the device (default is enabled) Open system settings Use to access the device system settings via the HID Mobile Access app Background operation The HID Mobile Access App is not automatically started after reboot on an iOS device. Once started, it will run seamlessly in the background but with exceptions and clarifications listed in the table below. If the app is forcibly closed, it will be necessary to restart the app in order to use HID Mobile Access. Operating mode Comments App in foreground Preferred mode of operation that works consistently. App in background + unlocked This mode works well but if issues occur, start or bring the app to the foreground. screen App in background + screen locked This background mode needs to be manually enabled in the App Settings to but lit up work properly. If the Mobile ID protection setting is disabled, doors can be opened without unlocking the device. App in background + black screen If the Mobile ID protection setting is disabled, the device will function, even with a black screen. 10 May 2020 PLT-02077, A.2 iOS devices 2.2.3 Recommended mobile device settings The following are the recommended device settings for an iOS mobile device. On the Mobile Access App Settings screen tap Open system settings: n Set Location to Always n Bluetooth: n For mobile devices running iOS version 13 or greater, set Bluetooth to Enabled n For mobile devices running iOS version 12 or less, set Bluetooth Sharing to Enabled n Set Background App Refresh to Enabled iOS version ≥ 13 iOS version ≤ 12 In addition to the above mobile device settings, it is also recommended that: n Location Services is set to On n Data Connection (internet connection) is set to On May 2020 11 iOS devices PLT-02077, A.2 2.3 Set up your Apple Watch for Mobile Access Firstly, make sure the Mobile Access App is installed on your mobile device and registered, see Section 2.1 Download and register the iOS App.

TEXTING ON A SMARTWATCH VERSUS A SMARTPHONE: A COMPARISON OF THEIR EFFECTS ON DRIVING PERFORMANCE A Dissertation by Joel Persinger Master of Arts, Wichita State University, 2014 Bachelor of Science, Eastern Kentucky University, 2005 Submitted to the Department of Psychology and the faculty of the Graduate School of Wichita State University in partial fulfillment of the requirements for the degree of Doctor of Philosophy December 2017 ©Copyright 2017 by Joel A. Persinger All Rights Reserved TEXTING ON A SMARTWATCH VERSUS A SMARTPHONE: A COMPARISON OF THEIR EFFECTS ON DRIVING PERFORMANCE The following faculty members have examined the final copy of this dissertation for form and content, and recommend that it be accepted in partial fulfillment of the requirement for the degree of Doctor of Philosophy, with a major in Psychology. _____________________________________________ Rui Ni, Committee Chair _____________________________________________ Alex Chaparro, Committee Member _____________________________________________ Barbara Chaparro, Committee Member _____________________________________________ Jibo He, Committee Member _____________________________________________ Jeremy Patterson, Committee Member Accepted for the College of Liberal Arts and Sciences _______________________________________________ Ron Matson, Dean Accepted for the Graduate School _______________________________________________ Dennis Livesay, Dean iii DEDICATION To my beautiful wife, who has pushed me to go further than I ever thought I could. She has truly carried me though graduate school with love and encouragement. iv ABSTRACT The National Safety Council reports that 6 percent or more car crashes involved text messaging from a smartphone. In addition, many studies have found that cell phone while driving increases crash risk by 2.8–5 times (Klauer et al. 2006; Redelmeier and Tibshirani 1997; Violanti 1998; Violanti and Marshall 1996).

mobile gaming Victor Bahl 8.13.2012 internet & devices growth (obligatory slide) Apps are ~$10 Billion market, growing at ~100% per year Fun Fact: Getting to 1 M users: AOL: 9 years; Facebook: 9 months; “Draw Something”: 9 days Mobility & Networking, Microsoft Research bandwidth demand! 1 ~ 10 billion mobile devices in 2016 10B (1.4 devices / human) 6B 6 2007 2011 2007 2011 2016 2011-2016 ~ 18X growth in mobile data traffic2 (~ 10 exabytes / month) Source: (1) GSMA; (2) Cisco Visual Networking Index: Global Mobile Data Traffic Forecast Update, 2011–2016 Mobility & Networking, Microsoft Research gaming today Source: Strategy Analytics - Apptrax4 Mobility & Networking, Microsoft Research …but you already knew that Some things I heard today: . how game analytics was used to increase dwell time . how in-the-wild user behavior may be modeled (& used) . The challenges in getting to MMOG games . wireless peer-to-peer games . power management by making use of saliency All great stuff, let me say a few words about some things I didn’t hear ….. Mobility & Networking, Microsoft Research services behind the games Fun fact: in 2011 ~$12 billion was spent on social/mobile games in 2015 revenue is projected to be ~24 billion (19% CGR) Apps that connect to backends receive higher rankings and more downloads because they are likely dynamic with more fresh content and are more social and contextual - Kinvey Inc., 2012 Xbox LIVE 30% growth year over year 40+ Million Users 2.1 billion hours played per month 35 Countries 176,802,201,383 Gamer Points scored

Software Engineering ISSN: 2229-4007 & ISSN: 2229-4015, Volume 3, Issue 1, 2012, pp.-10-13. Available online at http://www.bioinfo.in/contents.php?id=76 ANDROID OPERATING SYSTEM NIMODIA C. AND DESHMUKH H.R. Babasaheb Naik College of Engineering, Pusad, MS, India. *Corresponding Author: Email- [email protected], [email protected] Received: February 21, 2012; Accepted: March 15, 2012 Abstract- Android is a software stack for mobile devices that includes an operating system, middleware and key applications. Android, an open source mobile device platform based on the Linux operating system. It has application Framework,enhanced graphics, integrated web browser, relational database, media support, LibWebCore web browser, wide variety of connectivity and much more applications. Android relies on Linux version 2.6 for core system services such as security, memory management, process management, network stack, and driver model. Architecture of Android consist of Applications. Linux kernel, libraries, application framework, Android Runtime. All applications are written using the Java programming language. Android mobile phone platform is going to be more secure than Apple’s iPhone or any other device in the long run. Keywords- 3G, Dalvik Virtual Machine, EGPRS, LiMo, Open Handset Alliance, SQLite, WCDMA/HSUPA Citation: Nimodia C. and Deshmukh H.R. (2012) Android Operating System. Software Engineering, ISSN: 2229-4007 & ISSN: 2229-4015, Volume 3, Issue 1, pp.-10-13. Copyright: Copyright©2012 Nimodia C. and Deshmukh H.R. This is an open-access article distributed under the terms of the Creative Commons Attribution License, which permits unrestricted use, distribution, and reproduction in any medium, provided the original author and source are credited.

Case 2:19-cv-00361-JRG Document 1 Filed 11/04/19 Page 1 of 70 PageID #: 1 IN THE UNITED STATES DISTRICT COURT FOR THE EASTERN DISTRICT OF TEXAS MARSHALL DIVISION § AGIS SOFTWARE DEVELOPMENT § LLC, § Case No. § Plaintiff, § JURY TRIAL DEMANDED § v. § § GOOGLE LLC, § § Defendant. § § PLAINTIFF’S ORIGINAL COMPLAINT FOR PATENT INFRINGEMENT Plaintiff, AGIS Software Development LLC (“AGIS Software” or “Plaintiff”) files this original Complaint against Defendant Google LLC (“Defendant” or “Google”) for patent infringement under 35 U.S.C. § 271 and alleges as follows: THE PARTIES 1. Plaintiff AGIS Software is a limited liability company organized and existing under the laws of the State of Texas, and maintains its principal place of business at 100 W. Houston Street, Marshall, Texas 75670. AGIS Software is the owner of all right, title, and interest in and to U.S. Patent Nos. 8,213,970, 9,408,055, 9,445,251, 9,467,838, 9,749,829, and 9,820,123 (the “Patents-in-Suit”). 2. Defendant Google is a Delaware corporation and maintains its principal place of business at 1600 Amphitheatre Parkway, Mountain View, California 94043, and may be served with process via its registered agent, Corporation Service Company at 251 Little Falls Drive, Wilmington, DE 19808. Upon information and belief, Google does business in Texas, directly or through intermediaries, and offers its products and/or services, including those accused herein Case 2:19-cv-00361-JRG Document 1 Filed 11/04/19 Page 2 of 70 PageID #: 2 of infringement, to customers and potential customers located in Texas, including in the judicial Eastern District of Texas.

A SURVEY ONMOBILE OPERATING SYSTEM AND MOBILE NETWORKS Vignesh Kumar K1, Nagarajan R2 (1Departmen of Computer Science, PhD Research Scholar, Sri Ramakrishna College of Arts And Science, India) (2Department of Computer Science, Assistant Professor, Sri Ramakrishna College Of Arts And Science, India) ABSTRACT The use of smartphones is growing at an unprecedented rate and is projected to soon passlaptops as consumers’ mobile platform of choice. The proliferation of these devices hascreated new opportunities for mobile researchers; however, when faced with hundreds ofdevices across nearly a dozen development platforms, selecting the ideal platform is often met with unanswered questions. This paper considers desirable characteristics of mobileplatforms necessary for mobile networks research. Key words:smart phones,platforms, mobile networks,mobileplatforms. I.INTRODUCTION In a mobile network, position of MNs has been changing due todynamic nature. The dynamic movements of MNs are tracked regularlyby MM. To meet the QoS in mobile networks, the various issuesconsidered such as MM, handoff methods, call dropping, call blockingmethods, network throughput, routing overhead and PDR are discussed. In this paper I analyse the five most popular smartphone platforms: Android (Linux), BlackBerry, IPhone, Symbian, and Windows Mobile. Each has its own set of strengths and weaknesses; some platforms trade off security for openness, code portability for stability, and limit APIs for robustness. This analysis focuses on the APIs that platforms expose to applications; however in practice, smartphones are manufactured with different physical functionality. Therefore certain platform APIs may not be available on all smartphones. II.MOBILITY MANAGEMENT IP mobility management protocols proposed by Alnasouri et al (2007), Dell'Uomo and Scarrone (2002) and He and Cheng (2011) are compared in terms of handoff latency and packet loss during HM.

NIST Special Publication 800-101 Revision 1 Guidelines on Mobile Device Forensics Rick Ayers Sam Brothers Wayne Jansen http://dx.doi.org/10.6028/NIST.SP.800-101r1 NIST Special Publication 800-101 Revision 1 Guidelines on Mobile Device Forensics Rick Ayers Software and Systems Division Information Technology Laboratory Sam Brothers U.S. Customs and Border Protection Department of Homeland Security Springfield, VA Wayne Jansen Booz-Allen-Hamilton McLean, VA http://dx.doi.org/10.6028/NIST.SP. 800-101r1 May 2014 U.S. Department of Commerce Penny Pritzker, Secretary National Institute of Standards and Technology Patrick D. Gallagher, Under Secretary of Commerce for Standards and Technology and Director Authority This publication has been developed by NIST in accordance with its statutory responsibilities under the Federal Information Security Management Act of 2002 (FISMA), 44 U.S.C. § 3541 et seq., Public Law (P.L.) 107-347. NIST is responsible for developing information security standards and guidelines, including minimum requirements for Federal information systems, but such standards and guidelines shall not apply to national security systems without the express approval of appropriate Federal officials exercising policy authority over such systems. This guideline is consistent with the requirements of the Office of Management and Budget (OMB) Circular A-130, Section 8b(3), Securing Agency Information Systems, as analyzed in Circular A- 130, Appendix IV: Analysis of Key Sections. Supplemental information is provided in Circular A- 130, Appendix III, Security of Federal Automated Information Resources. Nothing in this publication should be taken to contradict the standards and guidelines made mandatory and binding on Federal agencies by the Secretary of Commerce under statutory authority.

NIST Special Publication 800-101 Revision 1 Guidelines on Mobile Device Forensics Rick Ayers Sam Brothers Wayne Jansen http://dx.doi.org/10.6028/NIST.SP.800-101r1 NIST Special Publication 800-101 Revision 1 Guidelines on Mobile Device Forensics Rick Ayers Software and Systems Division Information Technology Laboratory Sam Brothers U.S. Customs and Border Protection Department of Homeland Security Springfield, VA Wayne Jansen Booz Allen Hamilton McLean, VA http://dx.doi.org/10.6028/NIST.SP. 800-101r1 May 2014 U.S. Department of Commerce Penny Pritzker, Secretary National Institute of Standards and Technology Patrick D. Gallagher, Under Secretary of Commerce for Standards and Technology and Director Authority This publication has been developed by NIST in accordance with its statutory responsibilities under the Federal Information Security Management Act of 2002 (FISMA), 44 U.S.C. § 3541 et seq., Public Law (P.L.) 107-347. NIST is responsible for developing information security standards and guidelines, including minimum requirements for Federal information systems, but such standards and guidelines shall not apply to national security systems without the express approval of appropriate Federal officials exercising policy authority over such systems. This guideline is consistent with the requirements of the Office of Management and Budget (OMB) Circular A-130, Section 8b(3), Securing Agency Information Systems, as analyzed in Circular A- 130, Appendix IV: Analysis of Key Sections. Supplemental information is provided in Circular A- 130, Appendix III, Security of Federal Automated Information Resources. Nothing in this publication should be taken to contradict the standards and guidelines made mandatory and binding on Federal agencies by the Secretary of Commerce under statutory authority.

MOBILE OPERATING SYSTEM TRANSITION Insights and Considerations Mobile Operating System Transition – Insights and Considerations | 1

MOBILE OPERATING SYSTEM TRANSITION Insights and Considerations Mobile Operating System Transition – Insights and Considerations | www.honeywellaidc.com 1 Introduction A shift in the mobile operating system landscape has occurred over the last several years. The transition from legacy Windows® is well underway. While there remain several distinct choices on the roadmap, the tradeoffs and compromises associated with each have become clearer. This paper will elaborate on these points and provide the reader with guidance on recommended solutions. Mobile Operating System Transition – Insights and Considerations | www.honeywellaidc.com 2 Table of contents 3 Mobile Operating System History 4 Legacy Operating Systems 5 Android Enterprise Evolution 6 How Honeywell Helps 8 Android Lifecycle Management 10 Conclusion and Recommendations Mobile Operating System Transition – Insights and Considerations | www.honeywellaidc.com 3 Mobile Operating System History For the open source Android operating system, Google OEMs and third parties began developing extensions that enabled device management capabilities, provided more control over user actions, and added support for Ten years ago, operating systems for mobile devices in the enterprise space were provided by Microsoft. Windows CE and Windows Mobile (later Windows Embedded Handheld) offered industrial Wi-Fi features and capabilities needed for enterprise deployment, while a robust ecosystem of networks and developer tools and third-party offerings allowed customers to create the solution needed barcode scanning to effectively operate and manage their businesses. Apple had only recently shown the first capabilities. iPhone®. Google acquired Android™ a few years earlier and had yet to see a phone come to market. Other options available at that time were largely focused around the white collar professional user and proved largely unsuitable for the unique needs of the purpose-built enterprise environment.

The Application of Personal Digital Assistants as Mobile Computing Device on Construction Site Kenji Kimoto, Kazuyoshi Endo, Satoru Iwashita and Mitsuhiro Fujiwara Konoike Construction Co., Ltd., Research Institute of Technology 1-20-1 Sakura, Tsukuba-Science City, IBARAKI 305-0003, Japan. @konoike.co.jp . Kogakuin University, Department of Architecture, 1-24-2 Nishishinjuku, Shinjyuku-ku, TOKYO 163-8677, Japan. [email protected] ABSTRACT: Construction managers need to access the real construction site to manage the construction project. They have recently handled various types of digital information such as drawings, specification, checklists and daily reports. They usually use sheets of paper and/or field notes. As a result, a gap in time and space between the outdoor construction site and the office, which leads to the low efficiency, occurs. This paper reports the application of PDA (Personal Digital Assistants) as mobile computing device for construction managers on construction sites. First, this paper describes the aim and the essential element of the mobile systems. This also shows the analysis of necessary functions as mobile computing device through the discussion with construction managers, and the concept of development of this computer-aided engineering system. Secondly, this paper describes the outline of below subsystems with PDA: Progress Monitoring System, Inspection System and Position Check System. Subsystems have two programs: the data input program in PDA and the output program in PC. Finally, this paper indicates the development of more refined process of construction management with the mobile computing device on construction site. • Progress Monitoring System has been built for construction managers to monitor the progress of works.

IN THE COMMON PLEAS COURT DELAWARE COUNTY, OHIO CIVIL DIVISION STATE OF OHIO ex rel. DAVE YOST, OHIO ATTORNEY GENERAL, Case No. 21 CV H________________ 30 East Broad St. Columbus, OH 43215 Plaintiff, JUDGE ___________________ v. GOOGLE LLC 1600 Amphitheatre Parkway COMPLAINT FOR Mountain View, CA 94043 DECLARATORY JUDGMENT AND INJUNCTIVE RELIEF Also Serve: Google LLC c/o Corporation Service Co. 50 W. Broad St., Ste. 1330 Columbus OH 43215 Defendant. Plaintiff, the State of Ohio, by and through its Attorney General, Dave Yost, (hereinafter “Ohio” or “the State”), upon personal knowledge as to its own acts and beliefs, and upon information and belief as to all matters based upon the investigation by counsel, brings this action seeking declaratory and injunctive relief against Google LLC (“Google” or “Defendant”), alleges as follows: I. INTRODUCTION The vast majority of Ohioans use the internet. And nearly all of those who do use Google Search. Google is so ubiquitous that its name has become a verb. A person does not have to sign a contract, buy a specific device, or pay a fee to use Good Search. Google provides its CLERK OF COURTS - DELAWARE COUNTY, OH - COMMON PLEAS COURT 21 CV H 06 0274 - SCHUCK, JAMES P. FILED: 06/08/2021 09:05 AM search services indiscriminately to the public. To use Google Search, all you have to do is type, click and wait. Primarily, users seek “organic search results”, which, per Google’s website, “[a] free listing in Google Search that appears because it's relevant to someone’s search terms.” In lieu of charging a fee, Google collects user data, which it monetizes in various ways—primarily via selling targeted advertisements.

White Paper: Securing and Managing Wearables in the Enterprise Streamline deployment and protect smartwatch data with Samsung Knox Configure White Paper: Securing and Managing Wearables in the Enterprise 2 Introduction: Smartwatches in the Enterprise As the wearable device market heats up, wrist-worn devices Industries as varied as healthcare, such as smartwatches are leading the pack. According to CCS Insight, forecasts for global sales of smart wearable devices finance, energy, transportation, will grow strongly over the next five years, with the global public safety, retail and hospitality market reaching nearly $30 billion by 2023.1 are deploying smartwatches for While smartwatches for fitness and activity tracking are popular, consumer demand is only part of the equation. added business value. Enterprises are also seeing business value in wearable devices. In a report by Robert Half Technology, 81 percent of CIOs surveyed expect wearable devices like smartwatches to Samsung has been working to address these concerns and become common tools in the workplace.2 has developed the tools to make its Galaxy and Galaxy Active smartwatches customizable, easily manageable and highly secure for enterprise users. This white paper will look at how these tools address key wearable security and manageability challenges, as well as considerations for smartwatch 81% deployments. of CIOs surveyed expect wearable devices like smartwatches to become common tools in the workplace. Industries as varied as healthcare, finance, energy, transportation, public safety, retail and hospitality are deploying smartwatches for added business value, such as hands-free communication for maintenance workers, task management, as well as physical monitoring of field workers in dangerous or remote locations.

9 Apple and Nokia: The Transformation from Products to Services In the mid- to late 2000s, Nokia flourished as the world’s dominant mobile phone – and mobile phone operating software – producer. Founded in 1871 originally as a rubber boots manufacturer, by 2007 Nokia produced more than half of all mobile phones sold on the planet, and its Symbian mobile operating system commanded a 65.6 percent global market share. 1 But within half a decade, Nokia would falter and be surpassed in the smartphone market not only by Apple’s revolu- tionary iPhone but also by competitors including Google and Samsung. And in September 2013, Nokia would sell its mobile phone business to Microsoft for $7 billion. 2 Apple literally came out of nowhere – it sold exactly zero mobile phones before the year 2007 (the year Nokia held more than half of the global market share) – but by the first quarter of 2013, Apple had captured almost 40 percent of the US smartphone market and over 50 percent of the operating profit in the global handset industry.3 In fiscal year 2013, Apple would sell five times more smart- phones than Nokia: 150 million iPhones compared to Nokia’s sales of 30 million Lumia Windows phones. 4 In contrast to Nokia, Apple real- ized it wasn’t just about the mobile device itself, it was about leveraging software to create a platform for developing compelling mobile experi- ences – including not just telephony but also music, movies, applica- tions, and computing – and then building a business model that allows partners to make money alongside the company (e.g., Apple’s iTunes and AppStore) and, in so doing, perpetuate a virtuous cycle of making the iPhone attractive to customers over multiple life cycles through ever-ex- panding feature sets.