Sales Force Automation using the i-PAQ on the .NET platform

1. Sales Force Automation using the i-PAQ on the .NET platform Group 14 52 Deepak Mansukhani 53 Ritesh Aswaney 54 Sachin Mahajan 55 Deepti Ahuja Dept. of Information Technology Guide : Mr. Ravi Kadam

2. AGENDA • Problem Statement & Requirements • Technology • Use Cases • Architecture & Design

3. INTRODUCTION • Pivotal role of sales representative • Traditional IT systems for sales • Today’s customers’ expectations • Transition from IT-centric to end user- driven operation • Computing capability to mobile sales force • Possible technologies : Mobile phone, Laptop, PDA

4. COMPARING POSSIBLE SOLUTIONS • WAP mobile phone : low cost, limited visibility and less storage • Laptop-based software : high cost, cumbersome on-the-move, huge storage • PDA-based software: moderate cost, extreme ease of operation, good storage

5. PROBLEM FORMULATION • To capture information on the move • To seamlessly integrate captured data with the Sales and Distribution system • To satisfy the mobile computing needs of the sales personnel • To design a compact, space efficient package

6. FUNCTIONAL REQUIREMENTS • Customer/prospect information • Product information • Price list • Yesterday’s stock position • Order status • Customer outstanding payment • New scheme information • Order entry • Synchronization routines

7. NON FUNCTIONAL REQUIREMENTS • Display should be clear and legible • Response time should be low • Minimal keyboard entry, providing menus for selection

8. CHOICE OF TECHNOLOGY • 2 prominent groups of PDAs : • working on Microsoft Windows CE OS • working on Palm OS • We have selected the IPAQ for deployment and the .Net framework for development • .Net supports PC as well as devices for deployment environment • Scores over other environments by making available the Compact version of its .Net framework

9. WHAT IS .NET • .Net is an integrated suite comprising the .Net framework, .Net products and .Net services • .Net framework’s 3-tier platform • Base tier (Common Language Runtime): enables interoperability & language integration • Executable instructions compiled into EXEs and DLLs in the form of hardware-independent MSIL. • Metadata and IL enables code to be self-describing • JIT compilation enables code execution on any desired platform or device

10. Source Code Compile Developers Machine Exe / DLL Target Machine Class Class Loader Libraries JIT Compiler Managed Call to an Native Un-compiled Code Method Security Execution Check COMPILING IL WITH JIT COMPILERS

11. COMPACT .NET FRAMEWORK • Device emulators • New emulator for Windows CE Pocket PC runs a true implementation of the real OS • Enables easy development and testing of applications meant for the device • 3 kinds of code in creating .Netcf systems: • application code (MSIL) • device extensions • device profiles • Easy implementation and invocation of Web services

12. USE CASES • Accept order from customer • Update PDA with new information • Update orders from PDA into system • Display and retrieval for existing customer • Display product catalogue

13. Customer contacts salesman for an order Validate customer’s ID and credit limit Salesman enters product details (product id,SKU, quantity) If product valid and stock available, system shows rate and value Value should not exceed credit limit Save order ACCEPT ORDER FROM CUSTOMER

14. UPDATE PDA WITH NEW INFORMATION • Salesman contacts operator for synchronization • Validate salesman • If valid, synch routine invokes corresponding Web service • Updated rates, stocks, schemes, etc. are displayed for existing and new products • Log off application Web server

15. UPDATE ORDERS FROM PDA INTO SYSTEM • Salesman contacts operator • Synch routine invokes corresponding Web service • Validate customer • Trail for all orders transferred • No update if credit limit exceeded • IPAQ updated for customer’s new credit limit and orders’ status • Exit

16. DISPLAY AND RETRIEVAL FOR EXISTING CUSTOMERS • Customer contacts salesman for display/retrieval • Validate customer • Software retrieves order and payment details for that customer • Exit

17. DISPLAY PRODUCT CATALOGUE • Salesman contacts prospective customer • Customer specifies product of interest • Salesman enters product id, name or SKU • If valid, relevant details displayed • Display further information if required • Salesman enters prospective customer details,if interested

18. TOP LEVEL COMPONENT ARCHITECTURE DIAGRAM PDA SYNC PC AT DEPOT WEB SERVICE SALES & DISTRIBUTION SYSTEM

19. SALES INFORMATION CAPTURE ON PDA Data Storage Database SQL CE Access DB Class Library Invoke SQL SP Stored Procedure SQL Data Entry Invoke BT Business Tier VB.NET Winform VB.NET

20. CLASS DESIGN CustomerManager PaymentManager • AddCustomer • SearchCustomer • ModifyCustomer • DeleteCustomer • AddPayment • SearchPayment • DeletePayment OrderManager ProductManager • AddOrder • SearchOrder • ModifyOrder • DeleteOrder • SearchProducts • DisplayProducts

21. SYNCHRONIZATION • Periodic hookup with PC for upload/download • PDA uses ActiveSync to connect to the sync component on PC • Sync component invokes Web Service • Web Service synchronizes with the S & D System

22. Thank You