Customer Case Study Cab Building Process for Mobile Device Management Present By: Jeremy Laudermilk LyondellBasell Tom Perry Schneider Electric
Mobile App: Please take a moment Check into Session by: Select Detailed Schedule Select the specific session Click on Check in Take Session Survey by: Select Detailed Schedule Select the specific session Scroll Down to Survey and Provide Feedback
Introductions Jeremy Laudermilk LyondellBasell, Jeremy has been with LyondellBasell for 1 ½ years working as a Functional Developer for mostly Maintenance and Engineering applications including IntelaTrac. Prior to LyondellBasell, Jeremy has had 19 years of broad experience as a Software Engineer in Aerospace, Law Enforcement, Government and Healthcare industries. Tom Perry Schneider Electric, Tom has been with Schneider Electric for 2 years working as a Professional Services SR. IT Consultant for IntelaTrac. Before joining Schneider Electric Tom supported Maintenance and Engineering applications including IntelaTrac as a SR. IT Analyst for LyondellBasell for 7 years. Tom has a lot of experience working with Cab Files (loading 600+ handhelds), Handheld Platforms, Mobile Device Management Software, and enterprise application support.
Agenda What is a CAB? Execution of a CAB What is Possible in CABS CAB Build Process CAB Process Documentation What is Mobile Device Management? Benefits of Mobile Device Management Customer Testimonials for Mobile Device Management LyondellBasell Mobile Device Management Case Study
What is a CAB Definition: Use: A CAB (.cab) refers to a Cabinet File. A Cabinet file is a library of compressed files stored as a single file. Cabinet files are used to organize installation files. We use CAB files to install Mobile IntelaTrac and IntelaTrac s prerequisite software on Windows Mobile OS devices. Delivery: CAB files are delivered or copied to the device by using either a SD/MicroSD card or by using Microsoft Mobile Device Center with a USB Cradle/Cable connected to a computer and a mobile device.
Executing a CAB File Handheld Boot Process: Warm Boot: A warm boot is essentially restarting the handheld. Cold Boot: A cold boot is equivalent to shutting down the handheld. Clean Boot: A clean boot is a process of restoring the handheld to factory settings. It removes all installed software. Installation/Execution of CAB File: In most cases the CAB files are installed after a Clean Boot. This is an automatic process with little involvement from the end user. In some cases the CAB files are installed by manually executing(clicking on) the CAB file.
What is Possible in CABs? Customizations: Time Zone Settings Language Settings WiFi Network Settings Keyboard Mapping (Intermec CN70 and Ecom Ci70) IntelaTrac Specific Settings (Sync Server, Peripheral Configuration, WOR Cost Center) Lockdown Software (AppCenter and Launcher)
CAB Build Process Reliability Improvements On Site Modification (if needed) Verify Customizations Customer Request Completed CABs Delivered CAB Document Complete Download Tested Base CABs Established Best Practices for Mobile Platforms Improved Base CAB Testing Improved Customer Communication Customize Base CABs to Customer Specs Improved Custom CAB Testing
CAB Process Documentation Customer Customization Questionnaire Best Practice Configuration Example
What is Mobile Device Management Mobile Device Management: is utilizing a software package to manage the mobile devices in a companies IT environment Vendors for Mobile Device Management Software SOTI MobiControl Intermec Smart Systems Avalanche by Wavelink Airwatch by VM Ware Intune by Microsoft
Benefits of Mobile Device Management Supports Multiple Mobile Platforms (Windows Mobile, Android, ios) Device Lockdown Features Remote Access to Mobile Device Remote File Transfer Scheduled File Transfer Setting Time Zone Configuration Active Directory Integration
Customer Testimonials for MDM Based on my research and discussions with the SOTI rep, I see greater ease in managing multiple fleets of devices using different builds. I also see managing updates as being much easier, as the devices will pick up changes to the builds when the next connect to the system. SOTI offers mobile support for IPhone, Android as well as windows, so you can manage your BYOD (Bring Your Own Device) environment as well. Finally, centralized management of the deployed software, as well as the hardware is a win-win in my book. Joe Korinek, Systems Analyst, Ascend Performance Materials
Customer Testimonials for MDM SOTI has made the investigation process into handheld problems much easier, mainly because of the remote ability to review the handheld from any location. Handheld inventory is more precise, I know if a handheld is being used on other units. Notes can be left on handhelds for a single device, unit or sent out globally to the entire refinery. Reviewing handheld info for Back Up - Main Battery Status, RAM and Connect Disconnect Status is used frequently. I like that I can restart the handhelds with SOTI remotely, and I m working on automating this process. Mike Chafardon, PBF Energy IntelaTrac SuperUser, who supports 2 sites Delaware City Refining, DE with 70 HH and Paulsboro Refining, NJ with 50 HH
Customer Testimonials for MDM Avalanche is the go to system for managing everything on the IntelaTrac mobile devices. It will install IntelaTrac, it will install the small utility applications (stop watch, Adobe reader, etc). It will also deploy system settings as needed: time zones, WIFI settings, etc. This will allow for a very centralized and efficient way of managing the handheld devices. I m sure you have witnessed many IntelaTrac upgrades whereby the handheld upgrades took forever and were labor intensive. I think the biggest opportunity is to have Avalanche manage these upgrades as well. Imagine having a package tested and ready to go on our server, and then having Avalanche perform the mobile upgrades automatically. Aaron De La Riva, Western Refining, Systems Analyst, who supports 2 sites with 30 handhelds each.
Mobile Device Management Case Study
MobiControl Manager How is it used? Currently using MobiControl to manage Multiple device types and models Over 400 currently active devices 4 distinct software applications running on pool of devices Devices distributed at over 17 separate locations Locations span two continents Distribute and apply software updates to handheld devices Troubleshoot issues Train users remotely
Managing over 400 devices remotely Devices grouped in Hierarchical tree structure Application Location Use MobiControl to apply company policies at any level/group Update Schedules Security Deployment Server Priority Connection Settings Time/Time Zone Synchronization
MobiControl Management Console MobiControl Management Console: Is a web interface allows for easy deployment Allows you to create a folder structure for your environment It gives you a quick status view of mobile devices that are online Provides IP Address, storage space Allows you to expand more details of the mobile device
Lockdown Devices (Security) Authentication Policy: Allows us to set a password for the MobiControl kiosk screen on the handheld. The kiosk screen for MobiControl is an HTML document that can be customized. Displays the serial number of the device in the top left corner.
Keep in contact with those devices Out of Contact Device Policy: Allows for us to disable a device if the device is not connected within a certain time period In our case after 96 hours we wipe the device
Disable Features Device Feature Control Policy: This Policy allows us to disable device features such as bluetooth or phone By group or individual device
Configuration From the handheld you can review MobiControl s configurations and attempt to make a connection to the MobiControl server.
Remote Access to a Mobile Device Remote Access is as easy as right clicking on an online device. Online device seen as a Blue Screen on the device icon.
Remote Control of the Device Browse the Mobile Device just like using Windows Explorer. Cut/Copy/Paste files and folders.
Remote Wipe of a Mobile Device Within MobiContol you can remotely wipe a device. This will auto execute cab files on some handheld devices. It is not the same as a clean boot. It does remove installed programs, but does not reset the device to factory defaults. Right Click Send - Script Use Built In Wipe Device Script.
Other Capabilities Use of Rules and Packages: Rules and Packages allow for auto deployment of the following on a schedule or when a device comes online. Automatically add new devices Deploy packages Synchronize files Collect data Set Alerts
2014 Schneider Electric. All Rights Reserved. All trademarks are owned by Schneider Electric Industries SAS or its affiliated companies or their respective owners. 28