CMDB investments are all about identifying an organization's configuration items and understanding how they interact with one another. This simple transparency has a trickle down affect on so many operational areas that the value potential is incredible. However, actually tracking down each configuration item and entering it into the system can prove to be tricky. The result is gaps in how organizations can view their configuration from the top-down perspective offered by CMDBs. These gaps are becoming especially problematic as the Internet of Things (IoT) movement takes hold and wearable devices become commonplace.
The recent hype surrounding the Apple Watch is a clear example of how wearable devices are starting to become prominent. As more consumers begin using wearable technologies to integrate with their smartphones to interact with the world around them in new ways by running newly implemented services and applications, businesses need to be ready to respond. Failing to integrate wearables into your CMDB is one transparency hole you can't afford not to fill. Three reasons to integrate wearables into your CMDB include:
1. Understanding how Data Reaches End Users
Network visibility is one of the greatest advantages offered by CMDBs. An effective CMDB setup will include all of your IT resources, letting you see when data is moving within the corporate LAN, through the WAN and beyond enterprise firewalls into the cloud. This visibility has proven integral in helping organizations respond to enterprise mobility strategies, as it allows them to make sure they understand how data leaves the corporate network, which devices it is going to when it exits the firewall and what security measures they can take to keep that information safe in transit. The information provided here is also key because it helps companies create internal regulations to prevent some data types from being accessed by devices depending on where they are in relation to various firewalls.
Wearables add another layer of complexity to this process, and if you don't include them in your CMDB, you won't be able to easily understand how data reaches them and adequately protect information.
2. Prevent Against Productivity Losses
Wearable devices can be used as a last resort to help a worker access key data or applications in the field if their primary device fails for some reason. If somebody has a smartwatch, they may be depending on the device as a last line of defense. In this instance, if somebody forgets their tablet and tries to use their phone to access information they need for a customer interaction, you need to make sure that these interactions will be accounted for. You may even decide to make a quick change in response to an emergency situation.
CMDBs are vital tools when it comes to make these rapid, responsive changes without taking on risk. The visibility and transparency they offer lets you adjust the configuration to allow data or application access to a user facing an unexpected situation, but that is only possible if you are including wearable devices as a configuration item. If you don't prepare for emergency situations by putting wearables in your CMDB, you'll be left in a poor position to respond and face productivity losses.
3. This is Only the First Step Forward
The IoT is rising fast and wearables are only the first wave of connected device types that are going to find their way into the enterprise. Getting ahead of the trend now by including wearables as configuration items will make it easier for you to keep up as new technologies start making their way into the workplace.
We are in the middle of a connected device revolution, and your CMDB could end up being a key tool in helping you keep up with all of the change that is on the horizon.