|
This is the 4th article in a series on using Mobile computing. There are many considerations for firms to consider when building mobile and wireless-internet based systems. It is a complicated topic and involves ego’s, hardware, software, networks, processes and most importantly making profit !
Topics to be covered
|
1.
|
Processes and methodologies to follow
|
|
2.
|
Vertical markets where wireless and mobile is driving profit
|
|
3.
|
Hardware, devices and selection criteria firms need to use
|
|
4.
|
Software, applications and selection criteria firms need to use
|
|
5.
|
ROI models
|
|
6.
|
Real World examples and Case Studies of Wireless architectures
|
|
7.
|
The Future of Standards, devices and networks and their impact on business productivity and processes in Canada
|
3. Hardware Devices and Selection Criteria
Once I understand Wireless and Mobile computing and know that it can help me make money what follows?
The networks have become more reliable and devices are now better, faster, lighter, with multiple capabilities; cell, data, email, internet, and processing capacity. Prices for network access, hardware and software are falling. Count on prices for hardware, devices, networking gear, and infrastructure parts to continue to fall. Embedded chipsets, dual modems, more volume and slowly increasing demand justifies the economic forecast that hardware will continue to become more affordable. The question is what hardware and which devices does a firm choose to buy? There are 2 critical aspects: the business problem that we are trying to solve and the end user device that will be used by our people to automate and solve that problem.
This sounds easy but in reality many people get too caught up in the ‘complexity’ of the system and they worry too much about the plumbing. In looking at wireless and mobile systems we can see quickly that there are many levels of hardware needed to build a Wireless Local Area Network, and a Wireless Wide Area Network [WWAN]. Consider the simple architecture below. The first diagram is the internal WLAN hooked into an existing legacy. We then take that system and extend it to the Net and to other non-LAN systems.
From a WLAN to a Mobile/Internet System:
The WLAN setup is rather pretty simple. You need to:
 Analyze the warehouse or office area, and design where the access points go to optimize the transmission of RF signals - Decide on 802.11 a, b or g standards
- Get or use existing hardware units like a laptop, desktop, or PDA running a wireless interface card [NIC] that connects to an access point, which is connected via cable to the LAN server.
- Have a firewall between the WLAN and your existing LAN systems.
- Have some security such as WEP or WPA on the device/access point side and if needed a server with encryption or key based security access as well.
For a small office you can set up a WLAN for a few thousand dollars and most existing hardware can be wirelessly enable via air cards and wireless modems to enable you to access your systems
The complications arise when you take the WLAN and extend it outside your office, or warehouse and link it with the internet and other non-LAN systems. Now you will need to:
1. Identify what information is to go outside the WLAN and LAN and to whom.
2. Identify security protocols and security by ‘roles’ or by hierarchy [who can see what]
3. Decide what the end user in the mobile system wants to do with the data and
how fast they need / want data.
4. Work with IT to get the right budget for the right products.
Technically we need to:
1. Follow a design methodology to help you build a business
2. Layer in security and the various levels in a coherent ‘Design Plan’ to understand
what information goes where, and who can see it.
3. Buy the right products at all levels:
a. Network level
b. Router level
c. Servers
d. Software applications
e. Firewalls
f. Network monitoring/Security tools
g. End user hardware
The choices on product for the above will be determined by the following;
1. Budget - you need to buy hardware, software, training, outside help,
tools, and manage people’s transition to the new system.
2. Number of people and end users, which will impact of course the budget
and size of the network you are building.
3. Business Costs or Revenues that will flow from using such a system,
which may make the investment a profit-making project.
4. Current internal resources and product knowledge - what products will
my people be able to use or get trained quickly to use ?
5. Use Wi-Fi standard and certified only products.
6. End users - this is the critical choice. If the people using the system
don’t gain benefit from it then the system will be rejected and pushed back. We need speed, security, ease of use, good display, and high network bandwidth.
I would not worry however, too much about the plumbing. With some outside help and research you will be able to focus in on 1 or 2 products at each level of the architecture that will suit the # of users, the budget and ease of deployment you will be looking for. [ is a good place to start looking and reading reviews of the infrastructure products as is
The critical question is ‘What will my End User want to use and use effectively?’
You need to get end users testing devices and software almost from day one to get them to buy in and help you design and build a system that works. The end user device choice will also depend on:
- What do we use today ?
- What OS do we want to standardize on ?
- Can I buy new or do I need to use what we have plus a few add-ons ?
- Where are they using the devices – does the hardware need to be totally idiot proof ? or able to withstand people dropping them, punching them or using them as square baseballs ?
Wide Array of Possible Choices for the End User:
Low End - [Retail, Executive, Emailing based or Query based]
Palm [Palm OS], RIM [Java], Cell Phones [Java OS, Symbian]
Mid Tier - [Field Forces, Business Applications in the Field]
Pocket PC [Mobile 2003 OS], Palm [Palm OS], Tablets [XP], Smart Phones [Java], Laptops [Win 2000]
Higher End - [Heavy Outside usage - Logistics, Warehouse, Temperature sensitive]
Symbol [Mobile 2003], Intermec [Mobile 2003], Psion [Symbian], Falcon [Dos], Percon [Dos], various Laptops [Win 2000]
Within each category there are a range of Prices and functionality offered. Best thing in my view is to:
1. Standardize on Pocket PC unless you have a RIM user base and ONLY
need to query and email.
2. The more RAM and Mhz the better. Keyboards a bonus.
Use the device to run an application not be a paper weight.
3. Standardize on ONE hardware vendor and software package
per business application.
4. Use well-known Vendors with good support and maintenance packages.
5. Get end users to test a few devices and see which one suits
the environment the best.
6. Choose a good Prime outsource partner to help you with the entire process
in hardware, software, networking gear, design and implementation.
Navigating through the maze is hard. But the critical choice that you must make first is I believe the weapon of choice for your end users as well as the business problem you are trying to solve. The system, design, tools, and product choices all stem from these two basic considerations.
Craig Read
 |
Craig is a director of IT at a Toronto based mobile and wireless firm. Craig also founded the Toronto Wireless User Group which now has well over a hundred members www.torwug.org He can be reached at
|
