The document discusses Texas Instruments' enterprise mobility strategy and requirements. It aims to enable mobile access to information to improve productivity while ensuring security, manageability, and cost-effectiveness. Key points include deploying mobile email to thousands of employees using a network operations center architecture with centralized management of handsets from a single point.

1. Enterprise Mobility at TI IT Operations, Texas Instruments Evan Miller IT Operations Strategy Director

2. Agenda Business Context Enterprise needs Usability Cost management Security In-building coverage Convergence

4. History of Innovation 1930s 1940s 1950s 1960s 1970s 1980s 1990s Produces first commercial transistor and designs first commercial transistor radio First integrated circuit demonstrated Invents first handheld calculator Introduces Speak and Spell Introduces single-chip Digital Signal Processor Demonstrates digital projection display system 2000 Technology for Innovators ™ TI’s DSP and analog technologies are creating innovative solutions for both today and tomorrow .

5. Business-Enabling Technology Revolutions 1960s 1970s 1980s 1990s 2000s 2010s 100’s of thousands Billions 100’s of millions Millions Users Mainframes and Serial Communications Minicomputers and the Local Area Network PCs and The Internet Mobile Handhelds and the Wireless Internet

6. TI Businesses Semiconductors Educational & Productivity Solutions 2005 TI Revenue* By Segment ($B): $12.3B Semiconductor $11.8 B Educational & Productivity Solutions $.5B * Continuing operations, excludes the divested Sensors & Controls business.

7. Digital Motor Control Segway Human Transporter Communications + Computing Signal Processing DSP and Analog Converged Devices Digital Video Recorder/Server Digital Still Cameras IP phones Wireless Infrastructure Smartphones Broadband Disk Drives 3G Wireless Bluetooth VoIP Gateway Digital TV PDAs Digital Radio Wireless LANs Digital Camcorders Digital Audio

8. Mobile Solutions Move the Business Boundary from Buildings … … to People.

9. Enterprise Requirements Usability If end users won’t use it, we won’t deploy it – Usability drives ROI Scalable IT Cost Model It can't just be inexpensive to purchase, it must be inexpensive to deploy and operate Security Only solutions that meet Information Security requirements get approval

10. Mobile E-mail Handset Growth

11. Benefits 1. Immediate access to time-critical information, improves workflow 29% 2. Downtime conversion into productive time: 196 hours/year/person $45 to $90 million annual productivity benefit globally Plus 10% more sales “face time” with customers generating approximately $250 million annual revenue

12. Coincidence or Correlation? 2,000 handhelds (Million)

13. Enterprise Handheld Value Stack Balanced design trade-offs between voice and data Business Apps. Browse Intranet Web Secure Push Email & PIM Mobile Phone Value stack Market Size

14. Beyond Mobile Email Location-based applications Maps and driving directions Browser-based applications Product catalog search Workflow approvals Instant Messaging -> Unified Communications Enterprise Communications

15. Standards One laptop supplier One PC/laptop OS WLAN standard: 802.11b/g Global cellular voice standard: GSM Global cellular data standard: GPRS/EDGE moving to UMTS/HSDPA

16. BlackBerry ® With TI High Performance Analog TI Standard Handsets Nokia E61 and E62 With TI OMAP®

17. IT Acceptance Pass/Fail Criteria For Enterprise Handhelds (One failure disqualifies device) Supported by BES or Goodlink Crashes less than once/week on latest firmware Implements TI handheld password policy Implements remote erase Over-The-Air activation Over-The-Air push email and calendar/contacts/tasks/notes sync If it has WLAN, IT can prevent connection to TI WLAN network At least 1 day battery life with light voice and data use Doesn’t accidentally erase (enter password multiple times) in holster/pocket User-upgradeable firmware/OS Quad-band or Tri-band international roaming Supported by Cingular or T-Mobile in the US Supported by operators in EMEA Supported by operators in Asia

18. User Acceptance Criteria For Enterprise Handhelds Renders local languages? Good international roaming? Acceptable call quality? Holds weak signal? Easy bluetooth headset pairing? Browser speed? Browser compatibility and rendering? Doesn't accidentally dial numbers in holster/pocket? Do data or configuration settings lost after device replacement? Good battery life under light voice and email use? Very stable? Size acceptable? Weight acceptable? Read screen in sunlight? Read screen in darkness? Easy text input? Easy navigation? Easy voice dial? No need to sync to PC

19. TI Mobile Handset Servers Lewisville Freising Bangalore Hong Kong

20. Support Executive support group for corporate officers Regional help desks for everyone else (“Level 1” support) 2nd level support provided by organizations providing infrastructure service Mobile Solutions 2nd level support group continually teaching help desk to handle more of their load

21. Automation Ticket system Knowledge base Ordering Billing & re-billing Upgrade Repair/replacement Server accounts Process improvements begin Improvements save 18 FTE Goal: save 21 FTE by 2Q07 Also improves user experience

22. Automate Customer Tasks

23. US Handset Order Process User can walk up to one of three locations in Dallas, or order on web End users order device with credit card – TI may or may not reimburse End users can order operator service with cost center number Cost center manager gets email notification – can reject Web order arrives 3-5 days Business process varies by country Similar for Germany, France, Japan End user “fend for yourself” other countries

24. Managing Mobile Network Operators Set clear expectations Measure and report performance Meet quarterly to review performance Cost Technology Roadmap Availability Quality of Service Meet monthly to review operational service issues Meet weekly with suppliers who fall below a “B” grade

25. Security Application server Mobile Server Internet Mobile Network Operator Server-enforced password policy Remote erase, remote management Outbound Connection through firewall Nothing listening in firewall / DMZ End-to-end encryption Server Network Operator

26. In-Building Wireless Coverage 2M sq feet covered with GSM towards 10M sq ft by 2009 10M sq feet covered in the US with Nextel iDen 15M sq feet covered globally with 802.11b/g The enterprise should pay for cell coverage in the building, not the operator. Why? Control over-design, cost, expansion, and integration Negotiating position Do a RFP and get bids …big cost differential between in-building suppliers

27. Fixed-Mobile Convergence TI could save potentially $1M annually Mobile international LD reduction Bill auditing, fewer desk phones to deploy and manage Alternative solutions LD access number and PIN: already have it, employee use is declining IP Softphone over VPN on laptop: already deployed, portable but not mobile, call quality issues, higher support costs, hard to use Voice over VPN over Wi-Fi on a handheld: requires special handset, hotspot hunting, violates TI WLAN security policy, roaming issues, call quality issues, higher support costs, hard to use Or …

28. Join Networks No change to user behavior or handset Cell calls across the corporate network Call logging Mobile extension features

29. Q&A

30. Why A NOC Architecture? Security architecture keeps the handheld outside the firewall Reduces need for centrally managed anti-virus, client firewall, patch management Middleware is separate from Email infrastructure TI upgrades our exchange infrastructure on a 2-year cycle Mobile middleware needs to be upgraded twice a year Management architecture Centralized management from a single point Over-The-Air activation and upgrades

31. Why not WLAN support on mobile devices? An active WLAN radio allows layer 3 (IP) inside the TI firewall PEAP while inside TI, VPN while outside TI The IT Security policy is to either Keep the device outside the firewall, or Enforce and guarantee the installation of Managed anti-virus Managed client firewall Managed security patch update Managed device password policy enforcement software Mobile devices are outside the firewall Inside-the-firewall support would cost Two more TI headcount Three more CHD contractors 18 months to implement Over $300k in software and hardware for 1000 units PEAP/VPN access to TI has a more difficult user experience The plan is to disable the WLAN radio with by the end of 3Q before supporting WLAN devices

32. Why A NOC Architecture? Security architecture keeps the handheld outside the firewall Reduces need for centrally managed anti-virus, client firewall, patch management Middleware is separate from Email infrastructure TI upgrades our exchange infrastructure on a 2-year cycle Mobile middleware needs to be upgraded twice a year Management architecture Centralized management from a single point Over-The-Air activation and upgrades