Feature vs. Solution Selling

December 3rd, 2007 by tom No comments »

Pardon me while I digress from talk about asset tracking to discuss my sales methodology. I wanted to share this with other people getting into technology sales, but also to help potential customers of my software understand how I work.

A long time ago I was a software developer who designed and built business applications, most recently mobile asset tracking applications like the one we sell here at AMI. Since starting AMI, though, I’ve moved out of software development and into software sales, and have learned a thing or two fumbling my way through that transition.

Feature Selling

As a developer, you are primarily concerned with features. What buttons does the application have and what do they do? An overly simplistic description of the developer’s view, I admit, but the point is the developer is all about implementing executable code that does something. The feature list represents the amount of work the developer put into the software, and the successful execution of those features is how a developer measures him or herself. Do all the features work as they are supposed to?

When I made the transition to sales, I was having trouble selling software because I was stuck on selling features to customers. I figured the more features we had the more likely it would be for a customer to buy. But it wasn’t working. I was rattling off feature after feature, but customers just weren’t getting it. They were having problems connecting the features I was showing them to their own work. They might have a vague sense that the software might help, but they couldn’t understand how to justify the expense.

Solution Selling

Eventually an advisor pointed out to me that people are not coming to buy features, especially when it comes to business applications like the ones I am peddling. Customers have pain, and what they are looking for is a painkiller; a solution to a problem.

Now I look at sales as selling solutions. When a customer comes to me asking for information about my products, I first figure out what problem they are trying to solve. It’s pretty easy to do. Just ask, what made you come looking for tracking software? Oh, you are having trouble keeping track of all the stuff that comes into your warehouse? Okay, I have a solution for that.

This conversation naturally leads into me pointing out the features of my product that are relevant to the customer’s problem. The good part is I don’t spend any time telling them about features they don’t care about. Truth is, a customer will buy a solution with one feature if it is the right feature. Think of Microsoft Word. How many of Word’s 5,4291 features do you actually use?

Find the customer’s problem and stay on that point. Sure, you can mention you have additional stuff included they may be interested in down the road, but first solve their immediate issue. If you succeed in that, the customer will feel they are dealing with a knowledgeable person, and gain trust in you and your product.  And better yet, you won’t be wasting their time or yours talking about stuff you don’t need to.

Sequence of Events

Another tip an advisor taught me was the sequence of events. When selling larger solutions with big sales cycles, very early come to an agreement with your customer as to the sequence of events that will lead to a deal. Figure out the customer’s problem and your proposed solution, and then come to an agreement on what the customer expects the steps to be all the way through the transaction.  If you set this expectation early, you will have a context in which to communicate with the customer all the way through the sales cycle.

An example:

  1. Verbal agreement to proceed to a proposal
  2. Customer receives proposal, reviews and responds within two weeks
  3. Update proposal if necessary within one week, review second draft with one week
  4. Upon mutual acceptance, develop formal contracts within two weeks
  5. Review and finalize contracts within two weeks
  6. Cut purchase order
  7. Deliver software and provide training

Obviously the steps and timeframes will vary wildly depending on your type of business, but you get the point. Set some goals and timeframes so you have some time bounds on what is supposed to happen and by when.

This approach helps both parties. The customer will have a roadmap in front of them they can understand and communicate to their business. You’ve helped map out a task list and made their job easier. All they have to do is follow the plan and have their problem solved.

This approach helps the salesperson as well because it gives you a context in which to communicate with the customer. Customers do not like to be hounded. None of us do. But if you have a plan communicated, then you can contact them without wasting their time. You are simply following the plan and helping keep things on track. You have a reason to call them versus simply calling because your CRM told you it’s time to bug them again.

Best of luck to everyone.  Salespeople and customers alike.  Just remember we all have the same goal in mind: to do good business.


1 SWAG. I’m just making up this number to make a point. I have no idea how many features Microsoft Word has.

Auditing your Asset Repository

October 9th, 2007 by tom No comments »

Regardless of what type of asset tracking system you use, from time to time you should audit your database to ensure its accuracy.  It doesn’t matter how easy or effective your tracking processes are to follow: some assets will always fall through the cracks.  Technicians will grab assets off the dock and install them to close tickets.  Assets will simply be misplaced and never scanned.  Assets will be moved without anyone updating the database.

Unrecorded changes to your asset database will happen and should be expected.  You should therefore establish an audit process to check accuracy and true-up your database on a regular basis so that every location in your environment is visited on a schedule.

Audit Scope and Schedule

I recommend a rolling audit process, where a portion of your asset database is audited on a regular cycle. The cycle and scope of your audits will be based on the size of your organization and staff levels. However, a good starting place is to perform a monthly audit of 1/12th of your asset environment. In other words, slice your environment into twelve pieces, and audit one piece every month and don’t repeat a piece until all pieces are done. This ensures your entire asset environment is audited each year.

I’m over-simplifying here.  You will have to look at the physical layout of your environment and determine an audit schedule that fits you, but you get the idea.

Audit Process

Follow this process to audit each slice of your environment.

Collecting Audit Data

The process of collecting asset information during an audit must be fast and accurate.  Your personnel must be able to enter a room, scan in location information as quickly capture the asset tags or serial numbers of the assets at that location.  You need to be able to do this in a minute or less to minimize interruption to your and users and speed the audit process.  AMI recommends the use of mobile devices with barcode and/or RFID scanners which make it easy to collect asset information used by the audit.

  1. Deploy one or more users with mobile devices to the audit location.

  2. Enter the first room or cube and scan or enter the location data into the mobile device.

  3. If available, enter the user information that is responsible for the assets in that room or cube.  Ideally this can be done by scanning a badge number.

  4. Next, scan each of the asset tag of each asset at that location. Your mobile computer should be smart enough to detect when an unknown asset is scanned and audibly prompt the user to capture model and serial number to ensure “rogue” assets are added to the repository correctly.

  5. Save each “audit batch” to the mobile device database.

  6. Move to the next room or cube and repeat steps 2-4.

Comparing Audit Data

Once the audit data is collected, it must be compared to the repository for accuracy. Your exact reporting tools will depend on what software you have available, but you could simply use Excel or Access to build comparison reports.

The audit report should indicate:

  • Location accuracy percentage
  • User accuracy percentage
  • Cost center accuracy percentage
  • Detailed list of assets with non-matching data

Applying Audit Data

Once the audit reports have been generated and saved, you should apply the collected data to your database to “true-up” the data. Your asset tracking system should provide the means to apply collected audit data after audit reports have been generated.  Save off your reports to maintain a history of your asset tracking system accuracy, and rest confidently that your database will be maintained with a high degree of accuracy by knowing that all of your locations are visited on a regular shce

Barcode Scanner Types – Pros and Cons

September 25th, 2007 by tom No comments »

When selecting mobile devices for barcode scanning applications, take care to select the correct scanner hardware. Most devices come in multiple scanner configurations, and there are a few things to consider when choosing what type of scanner to purchase.

Scanner Types

Lasers

The traditional barcode scanner type is a laser that scans the barcode label and reflects back to the device. For one dimensional standard barcodes, lasers are my favorite. The upside is they scan at a longer distance and it is easier to target a specific barcode when a bunch of barcodes are stuck together in close proximity. The downside is they don’t support two-dimensional barcodes and cannot read damaged tags.

Imagers

The newer devices are shipping with what are called “Imagers.” These are basically cameras that take a picture of the barcode and analyze the image to “scan” the barcode. The benefit of Imagers is they support one and two dimensional barcodes so they are more flexible. Two dimensional barcodes can store more information in a smaller space. They can also be used to store multiple values within a single scan. Lastly, imagers are able to read somewhat damaged tags using fuzzy logic. This can be handy in certain environments. The downside is the scanning distance is shorter, and it often takes longer for the scanner to read the barcode. It is also difficult to isolate a single barcode when there are many close together. This can be extremely annoying in high-volume environments. You can see examples of two dimensional barcodes on UPS of Fedex packages. They look like boxes with little dots all over.

Positron Imagers

Cheap devices ship with what are called Positron imagers. These are basically one dimensional barcode readers that are imager-based. They are horrible. They don’t scan tags well at all and I highly recommend that you never purchase a device with a Positron imager, unless you are looking for a headache and an expensive paperweight.

Recommendations

If you are using high-quality one dimensional tags only, I recommend going with a laser-based scanner. You will be happier with the performance after scanning a lot of tags.

If you need to support 2D tags, then buy a high-quality Imager-based scanner. Just be certain you are not purchasing a 1D imager like a Positron. Most Motorola mobile devices ships with both configurations of Imagers. Be sure to get the 1D/2D imager version. 

Asset Tracking vs. Asset Management

August 16th, 2007 by tom No comments »

Customers often ask what the difference is between Asset Tracking and Asset Management. Our company name is Asset Management International, but our flagship product, AssetTrack, is an Asset Tracking solution. What’s the difference?

Asset Tracking

Asset Tracking is a component of Asset Management, and is a required first step. Asset Tracking means knowing what every asset is, its location, who has it and its status. You can definitely track more information such as lease/warranty end dates, cost, PO information, etc., but bottom line is that Asset Tracking means you have a complete, accurate and current list of everything you own.

Every part of Asset Management described below relies on accurate asset data. Quite simply, you can’t manage what you don’t know you have! Because of this, Asset Tracking is the first step in a maturing IT organization, and since assets tend to move around frequently, keeping track of everything is no small step.

If you haven’t started an Asset Tracking program, don’t feel bad. You’d be surprised how many organizations still have no idea what they have, including some of the largest, most well-known companies in the world.

Asset Management

Asset Management goes beyond tracking. It involves using your asset data to make intelligent business decisions to save you time and money. In addition to asset data, Asset Management solutions store data about your contracts, service level agreements, purchasing history and more and relate this information to your assets records which are kept up-to-date by your Asset Tracking program.

When all this information is maintained accurately, you can use this knowledge to aid in:

  • Resource planning – You have access to asset information so that you can plan for new projects and ensure you have the assets you need on hand, without overbuying.
  • Vendor negotiations – If you know exactly how many users require a certain piece of software, you can negotiate lower prices that if you were to purchase an enterprise license. You can also understand what assets cost you the most in services and replace that equipment or purchase better service contracts to save you money in the long term. Without Asset Management, you have to trust your vendors to look out for your interests, which is not in their interest.
  • Migration/upgrade planning – When you roll out Vista, you better have a good handle on how many systems require a hardware upgrade to support it. Without this knowledge, your Vista migration will be much more expensive and possibly overwhelm your support team.
  • Compliance reporting – Internal and external auditing is a major headache for all organizations and compliance with Federal regulations like Sarbanes-Oxley and HIPAA are even more so. With an effective Asset Management program in place, complying with these regulations is far easier, since you have the information at hand.

Conclusion

Asset Tracking is the first step of Asset Management. Asset Tracking is where you start, and once you get that nailed you will mature into Asset Management. Don’t expect to take one giant step for mankind and have it all implemented in six months. I will take you years to get everything in place before your Asset Management program is fully matured. But don’t worry; Asset Tracking will get some serious benefits out of simply knowing what you own. From there you will naturally mature into Asset Management.

Hosted vs. Local Business Applications

July 11th, 2007 by tom No comments »

With ubiquitous availability of high-speed internet these days, hosted business applications are a viable alternative to locally installed applications.  There are a lot of benefits to using hosted solutions, the primary of which is lower cost to your organization.

In addition to allowing customers to install our software in a local network, AMI is soon to make its AssetTrack application available as a hosted service so customers don’t have to set up and manage a server environment of their own.  This service targets the small to mid-size organizations that need to save cash and don’t have as many integration requirements with complex systems.  I thought this would be a good time to compare and contrast hosted and non-hosted applications to give you an idea of some of the questions to ask when deciding which way to go.

Hosted vs. Non-Hosted Comparison

Here’s a few things to consider when deciding whether or not to use a hosted solution:

HostedNon Hosted
CostGenerally hosted applications have a much lower setup cost since you are not purchasing a license of the software for a local installation.  Generally hosted applications are billed as a recurring service, which spreads lower payments over monthly or quarterly recurring billing cycles, but in general the total cost of ownership of a hosted applications will be much less.Locally installed applications generally carry a higher price up front, with support and maintenance fees incurred annually.  Since customers are purchasing an outright license for the software, software vendors need the bulk of money up front.
IntegrationSince data resides on an external server, your integration options may be limited.  However, well designed web services API’s make integration with hosted applications relatively easy, so determine whether your vendors provide programmatic access to data when evaluating integration potential.Locally hosted applications give you access to data directly via ODBC database access, local APIs including web services.  Since you control the server, you have multiple ways to access data.  This of course depends on the application and you should always check your software manufacturer’s warranty policies, but in general, locally hosted applications provide you a much higher level of integration capability.
PerformanceSince you’re running the application over the internet and generally sharing server space with other customers, a hosted application can provide lower performance than local hosted applications running on your 1000Mbit network.Locally hosted applications can be run on dedicated servers over a high-speed network and generally provide higher performance.
MaintenanceHosted servers are under the management of the service provider, making it much easier for your software manufacturer to apply service packs and other patches to minimize down time.  Maintenance is included with your recurring monthly or quarterly fee so there is no cost to your organization for maintaining the software.Maintenance is your responsibility, so there are costs associated with maintenance contracts as well as labor.   You will need to manage testing and server downtime, so be sure to calculate this into your decision.
Data SecuritySince your data is hosted by your software provider, you must therefore understand their data security policies and ensure your vendors provide secure data access and encryption of data during transfer.Internally hosted applications maintain data within your company network, giving you increased control over who has access to the data.  However, locally hosted applications can have lazy administrators that don’t have the same priority of data security, and can just as easily leave sensitive customer data exposed.  Just because your application is local, doesn’t mean it’s secure.

Advanced Shipping Notices

June 14th, 2007 by tom No comments »

If you are a large IT customer that orders a high volume of hardware and software, receiving assets can be difficult and time consuming.  With hundreds or even thousands of hardware assets arriving at your receiving docks every month, how much time and energy does it take to properly tag and enroll each asset into your asset repository?  Quite a bit, potentially.

One way to reduce this time and increase the accuracy of your asset database is to get your vendors to send electronic Advanced Shipping Notices (ASN) ahead of shipments.  ASN files are generally CSV or XML files that are delivered electronically to you ahead of shipments that contain one record for each asset in the shipment.  These files are formatted in a way that can be imported into your repository using an automated process.

Each asset record in the ASN file should have, at very least, the following information:

  • Serial number
  • Model name and/or number
  • PO number

Additional information like cost, tracking number, warranty or lease end date can also be included in ASN files.

Getting it Working

To get an ASN system up and running, you have to do the following:

  1. Contact your vendor and determine their ability to generate and deliver ASN files
  2. Determine the format of vendor ASN files
  3. Provide delivery information to your vendor (FTP site, Email inbox, etc.)
  4. Set up a process to import ASN files into your repository automatically
  5. Load ASN information into receiving mobile devices ahead of receiving

Most commercially available asset repositories have some way to import data and numerous third-party products are available to help you automate ASN imports.  Developing your own ASN import process is a relatively easy task for internal development teams.

Benefits of Using ASN Files

Saving Time Receiving

If you create asset records in your repository by importing ASN files, then at the receiving dock all you have to do is scan the serial number barcode to update the status of each asset record to “Received.”  You don’t have to capture the model or PO information since that information was sent to you by the ASN.  This reduces the time to receive assets and also the number of errors from selecting the wrong model from the product catalog or scanning the wrong PO number.

Preventing Over-Ordering

If you create asset records as soon as items are shipped by your vendors, you can generate reports showing you assets that are inbound.  This can help prevent over-ordering, since you can see that you have assets already on order that could be used to fulfill your requests.

Measuring Vendor and Employee Performance

By using ASNs, you can also measure the performance of your vendors, shipping companies and receiving personnel.  You can do this by measuring the time it takes for assets to be received after the asset records are imported by ASN files.  If the time delta is significant, you can determine whether the shipping company or the receiving process is slow.  This can help you improve your service levels to your customers by identifying bottlenecks in the procurement process.

Asset Identification and Tagging

May 29th, 2007 by admin No comments »

One issue that comes up again and again from my customers is how to properly identify and tag assets.  Most people have worked at companies that use asset tags, but I’m seeing more and more companies try to use Dell service tags or serial numbers instead of a new asset tagging scheme.

I thought I should take a moment and explain the pros and cons of asset tagging, and some of the tidbits we’ve learned to ensure you identify and tag assets properly.

Asset Identification

Asset Tags vs. Service Tags/Serial Numbers

As I mentioned above, some companies that have IT hardware from a single vendor like Dell have chosen to use the manufacturer’s service tag or serial number as the asset identifier.  Makes sense because why apply a new tag when the vendor has done that for you already?

I always recommend using asset tags.  Here’s why:

  • Manufacturer tags are only guaranteed to be unique for assets from that one vendor.  As soon as you try to enroll assets from other manufacturers into your asset repository, you have the potential for a tag conflict.  Unlikely, but possible.
  • Tag placement is extremely important.  Have you ever tried to scan a Dell service tag on a laptop that is in a docking station?  You can’t.  You have to undock the laptop which disturbs your end user and makes collecting tags during an inventory or audit very time consuming.  With asset tags, you can ensure tags are accessible on all installed or stored devices.

Asset Identification Recommendations

Use MOD137-Compliant Tag Values

By using your own tags, you can implement MOD137 numbering schemes, which we whole-heartedly recommend.  By using MOD137-compliant tags, your scanners and forms can automatically detect errors in data entry, such as when keying in an asset tag with a keyboard, or when reading an asset tag over the phone to your IT desk.  This also enables your barcode scanners to automatically know that you scanned the correct barcode for an asset, vs. accidentally scanning the product code or serial number.

Use Pre-Printed High-Quality, Durable Tags

Use a polyester or vinyl tag material with aggressive adhesive to ensure the longest life of the tag and to prevent users from removing them.  Have the tags printed by a printing company vs. using your own barcode printer.  The amount of money you spend on the service will pay for itself by ensuring tag quality and uniqueness vs. messing around with your own label printer and software.

Use Meaningless Unique Values for Asset Tags

Make sure you do not put any meaningful information within a tag value.  For example, I’ve seen customers use asset tag value that include the building ID where the asset is installed.  I’ve seen others where they concatenated the user id and the location id of the asset.  That’s great and all, but what happens when the asset moves?  You have to reapply the tag which blows away your asset history and is a tremendous pain to your techs.

So, don’t put meaningful information in tag values . . . ever.

Asset Tag Placement

When affixing tags to hardware assets, place them in accessible locations so that techs can scan the barcodes when the equipment is installed or stored.  For all asset types, consider the installed position of the asset and ensure that the tag is easily accessible by the handheld barcode scanner when the equipment is in use. For example, ensure tags on laptops can be scanned when the laptop is connected to a docking station underneath a monitor. Your particular tag placements will vary based on your asset types and installed configurations.

For Desktops and Laptops, I recommend placing the tags at the top front of the chassis and laptop lid respectively per the illustrations below:

DesktopsLaptops

The IT Asset Lifecycle

May 24th, 2007 by tom No comments »

When developing asset tracking solutions, the first place to start is to define the various stages assets go through as they are procured, used and eventually disposed by your company.  I call this the “Asset Lifecycle.”   By first defining your asset lifecycle, you can quickly see the places where you need to put in tools and processes in place in order to keep your asset repository up to date.

My experience with asset tracking is primarily with IT equipment, so the asset lifecycle I define below has a few stages which are specific to computer assets such as Staging.  In a generic sense, though, the following asset lifecycle applies to any fixed asset you bring into the company.

Asset Lifecycle Diagram

The following diagram shows the stages of the asset lifecycle as I see it:

IT Asset Lifecycle

An asset starts off as being On Order and moves through these various lifecycle stages until the asset is eventually Disposed.  The color coding shows you which organization has physical possession of the asset at each stage.  The arrows between lifecycle stages show how assets may move from one stage to another.  These arrows are the business processes that you must evaluate to ensure your asset database is properly updated as the status of assets change.

Lifecycle Stages Defined

The following list describes each of the stages as I define them.  As we get further into building asset tracking solutions together, I will be using these definitions to explain how the solutions should work.

On OrderOn Order assets are those which have been ordered but have not yet been shipped by the vendor.
ShippedAn asset is Shipped when it is in transit from the vendor to your company. The vendor should provide an Advanced Shipping Notice (ASN) as assets are shipped. An ASN is an electronic file which can be sent to your company and imported into the repository ahead of the receipt of equipment. When the asset is shipped, the vendor will invoice for the asset, so a financial obligation is created.
ReceivedAn asset is Received once your central receiving facilities take possession of the asset. An asset may be received when it is first shipped from a vendor, or if it is returned from a remote employee. Received assets can then be stored in the warehouse or forwarded to the Staging/Configuration department for installation to an end user.
StoredStored assets are usable assets in a stock location. Fulfillment coordinators should check for Stored assets to determine what assets are available to fulfill new equipment requests.
InstalledInstalled assets are asset currently deployed to end users and in use.
In RepairIn Repair assets are those that have been returned to a vendor for repair, and are expected to be returned to your company.
RetiredRetired assets are assets that are no longer of use to your company but have not yet been properly disposed. Retired assets are still in the possession of your company and may be retained for a certain period to keep employee data while a new asset is used. Retired assets must be properly disposed before the assets are taken off the books.
ReturnedA Returned asset is one sent back to a vendor, such as a lease return or item returned for credit.
DisposedA Disposed asset is one that has been (or at least should have been) officially wiped of data, transferred to a disposal company and the disposal company has provided an official certificate of disposal ensuring the asset has been properly. Once an asset is Disposed, it may be removed from the fixed asset and taxable property registers. The asset record remains in the asset repository for reporting purposes.

Developing an Asset Tracking Solution

The goal of your asset tracking solution is to maintain a current and accurate inventory of your IT assets.  To do this, you must ensure that your asset repository is updated as assets move between the stages in the asset lifecycle.

For example, when assets are received at your receiving dock, you need to update the assets in the repository with the receiving location and update the status of the assets to Received.  The way to accomplish this is to take look at your current receiving process, and figure out an easy way to have your receiving clerks update your asset database.  In this case I always recommend a mobile barcode scanner to quickly capture the serial numbers of the incoming assets, and establish a process for easily updating the asset records with the scanned information.

To complete your asset tracking solution, look at the ways that assets move between lifecycle stages, evaluate your current processes and design ways to make it easy to update your asset database.  If your employees comply with the process as defined, you will be able to maintain an accurate asset database over time.  Enforcing compliance is not easy, so be sure to establish an audit process and reporting tools to identify which employees are not following the defined process.  Once you weed out the bad apples you’ll have a streamlined tracking solution that works smoothly.

Barcodes vs. RFID

May 22nd, 2007 by tom No comments »

Everyone’s asking me about RFID for asset tracking these days, specifically whether it’s better than using barcodes. I understand why. The ROI promise of RFID is very compelling. Theoretically RFID promises that you can know where everything is without any manual effort, so why would you spend money on a barcode-based system that requires users to run around scanning stuff.

There are a few things to consider:

  • Is RFID ready for tracking IT assets?
  • What’s the cost?
  • What are the limitations?

This article will tell you what I’ve found as I’ve worked with various RFID vendors and enterprise customers on asset tracking solutions. The bottom line is there are some things you need to know before you can get ROI out of RFID. RFID will make sense in certain applications, but in others it will never make sense.

Hopefully I will demystify some of it for you by pointing out some pretty obvious questions to ask.

How Does RFID Work?

Here’s a quick primer on how RFID works. It’s not rocket science even though it seems like magic. Truth is you’ve been exposed to RFID a lot and haven’t realized it, such as in EZ-Pass tollbooths on the east coast, or your friendly neighborhood Banana Republic doorway.

Tags

Every asset in your environment that you wish to track has to have its own RFID tag. This tag stores the ID for the asset (and possibly additional information but we’ll get to that in a later post) and it emits that ID value as a radio frequency which can be detected by an RFID reader.

There are two types of RFID tags: Active and Passive.

Active Tags

Active tags are self powered and emit a signal over a much wider area. These tags are bulkier and also much more expensive. Anywhere from a few bucks up to $70 per tag. The upside is these tags can be read from a long distance, and are therefore the right choice for high-value assets like your Lincoln Navigator or Nuclear Warhead. ; Active tags can also be read by your favorite mobile device hardware, which is great for performing a warehouse inventory or sweep of your IT installed user environement.

Passive Tags

Passive tags are not self-powered, and therefore require an activator. These tags are much less expensive (people are claiming to have found .10c tags at high volume though I haven’t seen that yet). These tags also have a much smaller read range, though that is improving.

Mobile readers won’t work with Passive Tags because there is not enough power in a mobile device to activate the tag. There are “Mobile” readers that attach to forklifts, but that’s not the kind of mobile reader I’m talking about here.

Readers

So what kind of readers are available? There are two: Fixed and Mobile.

Fixed Readers

Fixed readers are for your doorways, such as entry/exit points in your enterprise or warehouses. Fixed readers come with an Activator and Antenna. The Activator excites the RFID tag so that it emits its signal. The Antenna then reads that signal and sends it upstream over your network to your interested RFID middleware.

Fixed readers cost around $5. There are slightly cheaper models and much more expensvie models like readers embedded in pavement, etc., but figure about $5K per location for fixed RFID reader hardware.

Mobile Readers

Motorola/Symbol, Intermec and other mobile device manufacturers make RFID mobile readers. They don’t do “Active” tags.

Does RFID Work for IT Assets?

No RFID system is going to be able to read all RFID tags on common IT equipment like laptops and desktops in every location in your environment. There are many physical factors to consider with how effective reads will be with your particular assets. For IT equipment, it’s all about metal.

Laptops

If you stick an RFID tag on a laptop with a metal case, there must be a .25 inch space between the RFID chip and the metal case. Tag manufacturers create tags with foam backings to create this space, but think about it. Are your end users going to be okay with a .25 inch padded tag stuck on the top of their laptop? Um, no. They’re going to rip it off as soon as they can. Else the tag will get ripped off as they slide the machine in and out of their laptop bag.

Also, when storing laptops in a warehouse, how do you store them? In a stack, right? That will be interesting with a .25inch padded tag on each laptop. And since you store your laptops in a stack, the metal from the other laptops will cause the same problem with the reads that the padding was supposed to protect.

Warehouses

When you’re picking assets from the warehouse, how do you select and assign a particular asset to a user? With an RFID reader, you’re going to pick up all the assets in range. But what if I want to select just this one? This is an issue where barcoding makes much more sense, since with line-of-sight scanning you can easily target a single device. And with barcodes you can use scan sheets to select users, locations or other values from your database without manual data entry.

On the other hand, if you wanted to quickly count which assets are in your warehouse, a quick scan using an RFID system would do that much more quickly. But with the limitations I described about stacked laptops and mobile readers failing to read passive tags, the technology just isn’t there yet.

Bottom Line

RFID isn’t ready for tracking IT assets. It will be in the next five years, though.  Here’s some tips for you in the meantime.

Use Smart Tags

At that time companies will want to use a hybrid solution called “Smart Tags” that have both a barcoded IDs and RFID chips embedded and synchronized with the same data. In this scenario, you can use both barcode readers for targeted, focused scanning as well as RFID for wide-net audits or automatic detection of movement throughout your enterprise.

Understand the Price

Today, figure $1MM to implement a full RFID tracking system in a single major building in your enterprise. This will get all your entry and exit points covered with fixed readers, RFID tags on all your gear and the professional services required to get all the technology connected to your network and backend systems.