Enterprise mobility and beyond
This is a modal window.
The media could not be loaded, either because the server or network failed or because the format is not supported.
Formal Metadata
| Title |
| |
| Title of Series | ||
| Number of Parts | 90 | |
| Author | ||
| License | CC Attribution 3.0 Unported: You are free to use, adapt and copy, distribute and transmit the work or content in adapted or unchanged form for any legal purpose as long as the work is attributed to the author in the manner specified by the author or licensor. | |
| Identifiers | 10.5446/47603 (DOI) | |
| Publisher | ||
| Release Date | ||
| Language |
Content Metadata
| Subject Area | ||
| Genre | ||
| Abstract |
|
00:00
Android (robot)Enterprise architectureRight angleProcess (computing)Data managementInformation securityTerm (mathematics)TwitterDifferent (Kate Ryan album)Arithmetic meanAreaHand fanPhysical systemMultiplication signShift operatorDemo (music)Video gamePresentation of a groupPoint (geometry)Functional (mathematics)TrailUsabilitySmartphoneInformationKey (cryptography)Limit (category theory)Enterprise architectureSound effectAndroid (robot)Variety (linguistics)Computer hardwareGame controllerComputer animation
02:56
Enterprise architectureAndroid (robot)Interior (topology)Configuration spaceWindowTerm (mathematics)InformationRemote administrationGame controllerRight angleComputer animation
03:20
Android (robot)Enterprise architectureRight angleGame controllerProjective plane
03:44
Android (robot)Enterprise architectureFunctional (mathematics)2 (number)Android (robot)Right angleProcess (computing)System callPoint (geometry)Set (mathematics)Cartesian coordinate systemWordCASE <Informatik>UsabilityComputer animation
04:31
Android (robot)Enterprise architectureSet (mathematics)CASE <Informatik>Functional (mathematics)Latent heatInformation securityGame controllerComputer animation
04:43
Android (robot)Enterprise architectureCASE <Informatik>System administratorNP-hardFunctional (mathematics)Computer animation
04:56
Android (robot)Enterprise architectureOperating systemMoving averageQuicksortTwitterSoftware developerData managementInternet service providerVideo gameCASE <Informatik>Right angleProjective planeFunctional (mathematics)GoogolVariety (linguistics)Process (computing)Food energySound effectAndroid (robot)Data compressionLevel (video gaming)Enterprise architectureComputer animation
06:34
Android (robot)Enterprise architectureMultiplication signTwitterFocus (optics)Mobile appInstance (computer science)Order (biology)Row (database)Right angleComputer animation
07:12
Android (robot)Enterprise architectureSoftware developerFunctional (mathematics)Computing platformSmartphoneEmailPort scannerProcess (computing)Mobile appCartesian coordinate systemMultiplication signCodeAreaSet (mathematics)Computer animation
08:36
Enterprise architectureAndroid (robot)Multiplication signTemplate (C++)Cartesian coordinate systemForm factor (electronics)Matching (graph theory)Operating systemCuboidQuery languageGUI widgetRevision controlPhysical systemProcess (computing)Computer animation
09:35
Android (robot)Enterprise architectureElement (mathematics)Bit rate
09:53
Android (robot)Enterprise architectureMultiplication signElement (mathematics)Digital electronicsRight angleGUI widgetGame controllerCartesian coordinate systemReal number
10:45
Android (robot)Enterprise architectureComputer animation
10:59
Android (robot)Enterprise architectureClient (computing)Cartesian coordinate systemQuery languageTemplate (C++)Computer animation
11:21
Android (robot)Enterprise architectureTemplate (C++)CASE <Informatik>InformationKey (cryptography)Cartesian coordinate systemComputer animation
11:53
Android (robot)Enterprise architecturePoint (geometry)Cartesian coordinate systemComputer animation
12:17
Android (robot)Enterprise architecturePoint (geometry)Online helpComputer animation
12:29
Android (robot)Enterprise architectureComputer animation
12:41
Android (robot)Enterprise architectureRemote administrationConnected spaceGoodness of fitSystem callPoint (geometry)Computer animation
13:45
Android (robot)Enterprise architectureCartesian coordinate systemRevision controlRemote administrationOrder (biology)Physical systemVapor barrierFormal languagePoint (geometry)CASE <Informatik>Right angleInformationComputer animation
14:40
Android (robot)Enterprise architectureEnterprise architecturePoint (geometry)Cartesian coordinate systemGame theoryData managementClassical physicsRevision controlComputer animation
Transcript: English(auto-generated)
00:03
Hi, guys. I'm Young. I'm a science engineer with SOTY. Thank you for being here at this ungodly hour. Since this is the very last session of this track, I wanted to give you a live demo and skip the PowerPoint presentation and lecturing mode, so feel
00:21
free to ask any questions that you come up with during the session. I will show you what our EMM is about. We have been developing this EMM for the past two decades, and we've seen a shift in the market, in the mobile device
00:41
market, where the trend is to minimalize fermentation. So operating system manufacturers and hardware manufacturers alike are trying to minimize the variety of different assets that you can choose of, and we will look at the effects of that trend. First of all, let me show you what EMM is all about.
01:05
Just by a show of hands here, who is familiar with enterprise mobility management, to give me a basic idea? Okay, we have one hand coming up. Is it really that you don't have any idea what EMM is all about, or are you just
01:21
very, very tired? All right, okay. Enterprise mobility management is all about managing mobile devices. Now, what does that mean? Managing mobile devices sounds like a marketing claim, and to be honest, it is actually that, right? Because managing mobile devices can be so many different things, and if
01:43
you talk to different customers from different verticals, you realize that there are so many different aspects to the term management. To cut this discussion short, there are two different general approaches to managing mobile devices. One is security and one is usability, right? Either you go using one very
02:04
general smartphone and limit all the functionality, secure your work process, or you go the other way, where people call it or tend to call it bring your own mobile device or BOD concept scenarios, where people are allowed to use the
02:21
devices for private purposes, and of course, on those devices, the key is to separate private from corporate data and make secure processes very, very easy to use, hence the term usability. Now, back in the days when Android 4,
02:41
Android 5 was around, the smartphone market or the device market was highly fragmented. Let me show you actually what I mean. So this is my device right here, my demo device. Mobile control is built in a way where in this console, you see all your devices that have been managed right now. If you click on a device, on any given device, you see detailed information to that device,
03:03
and of course, you can remote control the device in terms of supporting the device or just ensuring that the configurations that are intended for that device are actually set. So when I click on remote control, a secondary window
03:20
pops up, which is this one right here, and from this window, I can now control this device that I have at hand. I'm really sorry that I can't use this projector, but if I would use this projector, you wouldn't see my remote control session. So just believe me when I say this device right here that you are seeing. And to secure this device, we had to make use of
03:45
functionality and features which are called, which will be seen in a second. Bear with me. All right. Okay. So this is an unlocked Android device, right? So the user could go, could play around with it, could download applications.
04:01
I, as an end user, can now go to the settings and misconfigure the devices. Now, think of a use case where the device has actually been used in a warehouse scenario for corporate purposes. The end user might not like the English language, and as a German employee, I would change that language. Now, if an
04:21
English colleague would come along, the device wouldn't be usable for this colleague. Hence, my work process is in danger at that point. To limit this or to prevent this from happening, you could go the way, you could actually lock
04:41
down a device with Moby control to limit the device to one specific set of functionality intended by the administrator. This is the first use case that we have been talking about, the use case of hard security, right? So in this case now, I can't extend the status bar anymore. I can't press the home button to
05:01
get out of lockdown, and I can't even effectively reset the device. So in this use case, my work process is, as I mentioned, highly secured. Now, this was necessary back in the days of Android 4 and Android 5 devices, because when you
05:21
look at the market, you had all sorts of manufacturers of devices. Android wasn't always Android, right? When you looked at the Android from Samsung, from Zebra, from Honeywell, from Sony, from HTC, it was always something slightly different. So we had to come up with a solution to build certain APIs to kind of unify the management approach to that device. Now, with the development of
05:44
Android and the Android ecosystem, we see a trend of defragmentation, right? So there are more and more APIs coming along to unify the EMM approach or the management approach to those devices from the operating system level. Not from
06:03
the EMM level, but from the operating system level. Especially if you look at functionalities like Project Treble, for instance, to make life easier for end users and EMM providers alike. But if you look at the trend, right, if you look at the trend of defragmentation of the variety of assets, you're left
06:25
with the pressing question, why are we still talking about EMM then, right? Why am I here to talk to you about enterprise mobility management when Google is putting all those efforts into defragmentation of the mobility
06:42
market? Well, SOTY has been seeing the trend for quite some time. As I mentioned, we have been around for a long time. And we've thought about our future, obviously, and came to the conclusion that our main focus always has been the mobile work experience, so to speak. So in order to complement
07:03
that mobile work experience, we came up with certain other solutions such as a rapid app deployment tool, for instance. So if you think about it, the mobile work experience or mobile work is a fundamental aspect in our daily
07:22
life, right? If you think about yourselves, you check your emails on your phones, you communicate through your smartphone on the get-go. People in warehouse scenarios, in highly industrialized work processes are, again,
07:40
using mobile devices to scan bar codes, to gather data, to fulfill their daily work. So mobility is key to success. But just managing, just limiting the functionality of a device, just securing the access of
08:01
certain data on a device isn't enough anymore. So our approach is to complement the mobile work experience by supplying end customers with certain other solutions, such as, for example, the mobile application development tool that we have right here. I'll give you an example.
08:24
This Snap platform isn't supposed to be a app development tool. It's rather a handy tool for non-developers to come up with a very, very basic application in a very short amount of time. So when you think about, in my
08:42
example, a health care institute, to actually switch a patient query from pen and paper to an application, they would have to hire an application developer, deploy that application, or match that application to a certain
09:00
operating system or operating system version. Then they had to deploy that application to those devices and manage the application. Now, with SOTY Snap, you can easily come up with this kind of a template where you can choose the form factor of that device. You have certain
09:21
widgets to drag and drop into your application. So in my example, the end user would be asked for his name, but I could easily just drop a text box here to say, to state, or to just inquire something else, like how
09:45
cool is DroidCon, for example. And then I can put in a ratings element over here to actually let him answer to that question and so on so forth. So you get the basic idea, right? It's widget elements
10:02
that you drag and drop over here. You can populate that element with text. And then when you're done, you can just press publish, and this application gets published to all your managed devices in Moby control. Do we have time to actually look at it? Do you want to see it,
10:22
or do you get the basic idea of this? All right, cool. No, no, no, it won't take 30 minutes, obviously. Okay, cool. So let me show you on
10:45
my device real quick how it looks. Okay. So on the device, a
11:05
SolidSnap client gets installed. And if I open up that SolidSnap client, my patient query application appears over here. Obviously, there's an update. So if I press that, oh, yeah, I forgot to publish
11:22
this. But you can see where this is going, right? On the device, you can see the exact same template that we just created. And it's very, very easy to adapt. So think of a not too tech-savvy end customer who is in need of an application on their devices just to collect
11:42
information from their end customers, or from their patients in this case. The key here is it's easy to do, and it's very, very quickly deployed. Now, let's say there's a nurse, right? And the
12:01
nurse has this device in hand and has some issues with this application. Her approach would be to just say the application is broken or the device is broken, I can't work with it. And again, the mobile work experience is broken at that point. What we do at this point is we supply end customers with a mobility-centric
12:25
ticketing tool, which allows a help desk support guy, for example, to assist that nurse. So in my example, the nurse calls in and says, hey, I have a problem with that device. So the
12:43
support engineer just creates a new ticket and looks up the device who's calling in. So in my example, I am that nurse. So I look for my device. And SOTY Assist, again, connects to the EMM or complements the EMM. So through an API call, I just
13:02
look up the device. Unfortunately, my connection seems to be not that good. But anyhow, after I looked up that device, I can then again, yeah, okay, here we go. Okay.
13:32
Sorry for that. Okay. It seems like as if I am having technical issues. But okay, here you go. So if I click
13:43
remote control at this point, as a support engineer, I can now connect to my device. Now, when the nurse calls in tech support, right, the first challenge here again is the nurse might not be too tech savvy. The support engineer usually asks for questions like what kind of device do you have, what operating system are you running, what version of
14:02
that application are you running, right? And those are very, very technical questions. Now, in order to make the mobile work experience better or easier for the nurse, the support engineer now can just remote control it to the device, click on info, and sees all those informations, right? So the language barrier between tech
14:21
savvy support engineer and non-tech savvy nurse is overcome at this point very, very easily. Also, obviously, I can now assess what is actually going wrong. So I can ask the nurse, can you please repeat what you've been
14:40
doing? In that case, I can see, okay, maybe she's not using the correct version of that application. Maybe I missed pushing down an update, and so on and so forth. So the troubleshooting becomes very, very easy at this point. Yeah, and that pretty much concludes my very brief
15:03
overview of how we try to expand beyond the classic enterprise mobility management to make the mobile work experience better. Okido, do you have any questions at
15:24
this point? Coolio, then I should, uh, say we go enjoy the game.