Ten RTLS Pitfalls
In This Chapter
Working with an abstract business case
Miscalculating the integration costs
Placing the location sensors ineffectively
Running pilots that omit asset types
Neglecting the business process
Choosing not to deploy enterprise-wide
Underestimating maintenance overhead
Planning for too much too soon
Ignoring privacy concerns
Fewer than ten years of rapid and enthusiastic evolution have led to several RTLS technologies based on standards and supported by a large selection of products and services. The promise of an RTLS has become apparent to many inventive solutions providers and users, resulting in companies actively looking to transform their processes with an RTLS. To ensure success, new RTLS users should follow classic guidelines for technology adoption and project management as they move from a pilot to a commercial implementation, and at the same time, use the lessons discovered by early adopters of an RTLS.
In this chapter, I want to make you familiar with the ten most common pitfalls companies and users run into with RTLS implementations. Regardless of your industry and the specific business applications your RTLS will address, by recognizing these pitfalls, you can ensure the short-term and long-term success of your system and truly drive value innovation to achieve both your short-term tactical goals as well as your long-term strategic goals.
Failing to Determine Compatibility
One of the most common pitfalls ...