|
Wireless Application Service Providers - WASP
Hype and Reality of W-ASP -
Cautionary Factors -
It appears that (in early 2001) there is tremendous hype about W-ASP as
if it is going to solve all problems with wireless application implementation
and it is the only way to go forward. Early experience with general-purpose ASPs
is just emerging and it is mixed. The following experience represents cautionary
notes:
Cost and Time Overruns
Typically, cost and time estimates by marketing types from W-ASPs are lower
than what they ultimately end up with. There are lots of extras hat are
not covered in the contract. Therefore, an organization should be cautious of cost overruns in the following areas:
-
Deployment takes longer than agreed upon.
-
Maintenance costs for unexpected hardware or end-user devices.
-
Interruptions of day-to-day operations, resulting in indirect costs.
-
Technology is not compatible with next generation technologies.
Performance
Response times and throughput generally lag the expectations. Ensure that
the vendor has used good design and analysis before giving estimates. Deja Vu!
Keeping ownership and control of customers
The wireless ASP could detach an organization from its customers by sending
them to a third-party source for wireless service. For example, an organization
wanting to deliver an m-commerce solution should ensure that it has control over
business aspects of application development - business logic, the look and feel of its enrollment site,
content and customer interface. By working closing with the W-ASP, an organization could, for example,
launch a branded application in an effort to build customer recognition.
Transfer of Knowledge
If the W-ASP’s training program does not adequately transfer knowledge to
end-users, workers will become frustrated, resulting in inefficiencies and,
ultimately, a slow return on investment.
SLA and Contracts
There do not exist enough examples and templates for contracts for wireless ASP.
Use common sense that applies to outsourcing - wireless is just a network
technology component. Rest of the infrastructure is still the same. You
should ensure that W-ASP contracts are well-written and cover all eventualities.
Tie down expectations from different organizations in a consortium - also the
responsibilities.
|
