Longterm Data Visualization for Wireless Networks

As an engineering organization acquires tools, they also acquire essentially screens. The more screens a user has, the more likely he isn't going to utilize them. This then doesn't bring into the question the tools that were acquired and not used necessarily, but potentially just too many tools for the end user. If every tool is using a map to display data for instance, how many mapping front ends are required? As engineering tool platforms move off the desktop, tools in essence just produce data.

Measuring Network Voice Quality


Promoting Tools --- You Already Own

Every organization needs to purchase tools. Typically a long drawn out process where a lot of people review, critique, and ask for changes, inclusions, and items to be removed. Now that you've got your shiny new tool you just need to figure out how to get everyone to use it. Some place it at the feet of the tool vendor, some to training departments, but few have a method of universal acceptance. Sometimes this is just fighting human nature and the resistance of change, while other times it is simply communication.

The Engineering Cost of Tools

The wireless industry has embraced the need of tools for every aspect of an engineers job tasks. There is tool to run designs, visualize the customer issues, adjust parameters, recommend changes, and just about anything else an engineer my do. Most of these tools were created to fill a need whether through creating efficiency, incorporating a knowledge set, or expanding a capacity. Every tool has costs and typically creates some sort of savings, but what is the long term cost. Not in term of support, maintenance, continued development; rather, in terms of engineering know-how.