10 Keys for 'Easy to Use' Video Management Software

Author: John Honovich, Published on Jan 02, 2010

In this report, we examine well established usability principles for software, how they are routinely violated and what can be done. Contrary to common suggestions, the answer is not more training, ignoring it because engineers can use it as is or simply dismissing the need as a matter of opinion.

Training = Failure

If Video Management Software requires experienced security professionals to be formally trained on using it, than it is not easy to use. Easy to use software enables users to quickly experiment and learn the interface as the user explores it. Multi-day training classes should be considered a vice, not a virtue, reflecting software with poor interface design.

Expert Users Do Not Prove A VMS is Easy to Use

It is common to hear experienced engineers talk about how their favorite VMS is 'intuitive'. This certainly is possible but misses the point. Software ease of use is measured by the time and difficulty new users have to learn software, not the ease with which experts who use an application regularly have using it.

Easy to Use is Not Simply A Matter of Opinion

Many people think 'easiness' is just a matter of taste or opinion (Joe's favorite color is blue but Mary's is pink, etc., etc.)

To the contrary, human-machine interaction and user interface design has been developed over the past 50 years. There are broadly agreed upon principles that software developers should follow. Here are a few of the most cited works in the field:

It is likely that many VMS developers are simply ignoring these well established principles.
 
Video Management Ease of Use

In this premium report, we examine the most basic principles and demonstrate how they are routinely violated resulting in user experiences that are both frustrating and cumbersome. We analyze and demonstrate issues with two of the largest IP video providers - Mobotix and Milestone.

End users and integrators should consider difficult to use VMS software to be primarily the fault of the software developers, not of users.

** **** ******, ** ******* **** *********** ********* ********** *** software, *** **** *** ********* ******** *** **** *** ** done. ******** ** ****** ***********, *** ****** ** *** **** training, ******** ** ******* ********* *** *** ** ** ** or ****** ********** *** **** ** * ****** ** *******.

Training = *******

** ***** ********** ******** ******** *********** ******** ************* ** ** formally ******* ** ***** **, **** ** ** *** **** to ***. **** ** *** ******** ******* ***** ** ******* experiment *** ***** *** ********* ** *** **** ******** **. Multi-day ******** ******* ****** ** ********** * ****, *** * virtue, ********** ******** **** **** ********* ******.

Expert ***** ** *** ***** * *** ** **** ** ***

** ** ****** ** **** *********** ********* **** ***** *** their ******** *** ** '*********'. **** ********* ** ******** *** misses *** *****. ******** **** ** *** ** ******** ** the **** *** ********** *** ***** **** ** ***** ********, not *** **** **** ***** ******* *** *** ** *********** regularly **** ***** **.

Easy ** *** ** *** ****** * ****** ** *******

**** ****** ***** '********' ** **** * ****** ** ***** or ******* (***'* ******** ***** ** **** *** ****'* ** pink, ***., ***.)

** *** ********, *****-******* *********** *** **** ********* ****** *** been ********* **** *** **** ** *****. ***** *** ******* agreed **** ********** **** ******** ********** ****** ******. **** *** a *** ** *** **** ***** ***** ** *** *****:

** ** ****** **** **** *** ********** *** ****** ******** these **** *********** **********.
 
Video ********** **** ** ***

** **** ******* ******, ** ******* *** **** ***** ********** and *********** *** **** *** ********* ******** ********* ** **** experiences **** *** **** *********** *** **********. ** ******* *** demonstrate ****** **** *** ** *** ******* ** ***** ********* - ******* *** *********.

*** ***** *** *********** ****** ******** ********* ** *** *** software ** ** ********* *** ***** ** *** ******** **********, not ** *****.

[***************]

A *** ***** **********

**** *** * ***** ********** ** **** ** ****:

  • Spatial ********: Related tasks should be physically close to one another. For example, selecting cameras and controlling PTZs should be very close and physically separated from configuring cameras. It's shocking how often this is violated by VMS systems.
  • Visual ****: ***** ****** ** **** ******* ****** (****, ****, ***********) that ******** *** *** *********. *** **** ************ ***** ******** (click ** * **** ****, ***** ***** ** * ******, etc.), *** **** ********* ** **** ** *** * **** to **** *** *** **** ********** *** ******** *** **** need.
  • Make **** ******** **** ******** ******* ** ******: A system can have hundreds of features but the handful used the most (like selecting cameras and searching video) should be far more prominent than most others. We are amazed at how often VMS vendors bury the most frequently used functions in long series of rarely used controls.
  • Provide ***** ****** *** ********: The UI should make it easy to understand where the user is at and what is causing any problems. It's absurd that many VMS systems do not clearly show whether the system is in live or playback mode. Similar problems exist with error messages, especially when a VMS cannot connect to an IP camera. The messages are often written in technical terms ("cannot connect to the database") is unhelpful for most integrators and users.

***** *** *** *** **** **********/****** ** ** ****** *** they ***** ** *** **** ********** ******** **** ** **** world *** *******.

***** *** *** **** ******* ** *** ******* ** ****** followed ** ******* ******** *** ********** ** *** *********.

Mobotix **** *****

********* *** ** *** ******* ** ***** *********. ***** ******** centers ****** ** *** ******* ******** ***** ********* *** *******' cameras *** ***** **** *** *******.

******* ****** * ***** ********** ******* -************************. **** ** **** ******* *********** ********** *** ****** ****** stands *** ******* ** ** ******** *** ******* *********** **** less ************* *****.

** *** ***** *****, ** ******* ******** ****** **** ******. We ********* *** ********** ******* ********** *** *** ********** ** ********.

Milestone **** *****

********* ** ****** ************ ** *** ** *** *** ******* of *** ******** ********. **'* **** *** ** *** ******/**** mature *********. ******* ****, ***** **** **** ***** ******* ********,******** ********** ******* **** ******** ********* ******.

*** *** ** ****** ***** ***** *** ** ******** *** demonstration ** ****** ** **** **********, ************** *** **************.

Examining ********* **********

*** ****** ***** *** *** ** ************* *** ***** * principles ** *****: (*) ******* ********, (*) ****** **** ****** features ******* ** *** *** (*) ********* ***** ****** *** feedback.

***'* ******* **** **** **** *********** ********** *** ***** ******* to *** ********:

  • "** ******** ******, ** ***** ********* **** ** *** ********, so *** ******** ******* ** ******* ** ** * **** investment ***** ****** *********." ***** *** ******** ********* **** ***** products ** *** **** ************* ******* ** ***** ********* ******* feature ***** **** ****, * *** ******** ** **** ***** are ** **** *********, ** ********** *** ******* ** ***** to **** *** *** *** ** ****.
  • Design *** *** ********, ******* *** *** ********: A pithy maxim from Alan Cooper emphasizes that systems can have numerous features but the system must make the most common cases, the easiest to access and use.
  • ****'* ***- "******** **** *** **** ******** ** ******* **** ** a ****** **** ** * ******** ** *** ******** *** the **** ** *** ******." *** ********* *********** ** **** principle ** **** ** ******** **** *** ****** ******* ******** should ** ***** ** **** ***** *** *** **** ****** ones ****** ** *** *******.
  • ****'* ***- "********* *** **** ** ***** *** * ****** ** make * ******** ** * ****** ** *** ******** ******* he ** *** ***." ******* **** *** **** ******* *** provide ** ** ******, *** **** ********* *** *********** ** becomes ** **** * *********. **** *** ******* ***** **** rows ** ***** ***** *** ****** **** **** ******** ******* power. *******, *** **** *****, **** ******* ******* ********** ** determining ***** *** ******** **** **** **.
  • Beware ** *********** *****: “Whatever language you know, you have to learn the meaning of an icon anew. There's a reason why humans invented phonetic languages where just a few symbols can be combined to produce any word." It's common for VMS systems to use numerous icons (see MxEasy as the worst/best example of this). It may appear that this saves space but what it likely does for most users is cause them to hover over each icon repeatedly trying to remember what the meaning of the icon is.
  • "** ** ********* ****** *** ** ******** *** **** *** features ******, **** ******* ** *********.” **** *** ******** ***** to ******* ******* ******** ** ******* ********, ******** ***** *** overloads *** ****** **** *****, ** ****** ***** ** ******** the ******** ** **** ******* (*****, *** ****** *** * perfect ******* ** ****).
  • User's ********** ** ******** ****: Users can become very frustrated and believe an application is broken if it takes more than a few seconds to respond. Developers who become acclimated to such long delays often over look this. However, for a new user, they have no idea that this is normal and routinely assume the system simply does not work. This problem frequently happens in VMS software both during searches and when logging in to user applications. If the developer cannot eliminate this, clear feedback should be provided (e.g., a percent done display that accurately reflects progress). See a **** ** ******** **** **** ***** *******.
 
*******, *** ******** ***** **** *** ******** ****** *** *** limitations ** ****** *****. ********** ** ** ***********, **'* ********** that ****, ** *** **** *****, ** ***** ********** ******** will **** ******* *********/** ******. ** **** ***** **** **** smaller ********** **** ***** **** ****** *** ****** *** ** users. ***** ** *** ********* ***** ****, ** ** ********* that ******* ****, ********** *** ******** **** **** ** ******** *** users **** *** ********* *****.
 
*** ********* ****** ***** **** ************, ********, ********* *** ***** come **** **** ******'* "***** ****: *** ********** ** *********** ******."
 
  • *** ******* **designing *** '******* *****', *** *** ************* ******** ******** ***** *****. This identifies the common danger of developers to assume that their users are technically proficient as themselves and willing to spend time and energy figuring things out. Even with integrators, this cannot be assumed as integrators deal with many product lines and have large numbers of technicians they need to train.
  • ****** **** ******** ******** *** ****** *** ****. ** ** example, * **** ******* *** *** ******** ** "***, * 43 **** ******** ***** *** ******** ** *** **** ***** out ** **** ******, ********** ***** * *****, *** ****** a ****** ** *** **** ***** ********* ************ *** ****** sales. ** *** * **** ** ** ****, **** ** moderately ** **** ****** *****." **** ******* ***** **** ** much ******* *** **** ** ********** * '****' **** ***** face. ***** *** **** ***** ** ****** *** *** *** software *** ****** *** **** *** ******* ************ **** *** computer ******** ***** **** **** *** ********** ***** ********** ****** for.
  • ****** *** ******** ***** *** *********. **** * ****** ********: "The ***** ***** ** **** **** ******** **** ***** ******* 3 *** * ** *** *******, *** *** ***** ** any ***** *** **** ** ** *** ******." * ** amazed ** *** ********* **** **** ***** *** ***** **** scenario ** ** **** *** *******. ** ******** *** ************ usability *** ****** *********, ******* ***** ** **** '******' ** use.
Login to read this IPVM report.
Why do I need to log in?
IPVM conducts unique testing and research funded by member's payments enabling us to offer the most independent, accurate and in-depth information.

Related Reports

Panasonic Unified Surveillance Strategy Analyzed on Nov 17, 2017
Panasonic is now a "Unified Surveillance" offering, as their ASIS 2017 booth proclaimed: Looking to make a comeback in the security industry,...
PoE UPS Tested (Energy Reconnect) on Nov 15, 2017
In security, backup power is important, but most often requires UPS systems or extra cabling to devices for low voltage power. Now, some have...
Axis Commits To Long-Term Firmware Support on Nov 15, 2017
With the rise of cyber security awareness, and a general increase in hardware reliability, "software warranties" may prove more valuable than...
Hikvision NVR 4.0 Improvements Tested on Nov 14, 2017
Hikvision has released firmware version 4.0 for select NVRs, touting two years of research and development, and claiming "the new generation GUI...
Mobile Credentials (BLE / NFC / Apps) Guide on Nov 14, 2017
One of the biggest trends in access for the last few years has been the marriage of mobile phones and access cards. In this guide,...
Long Range Access Control Readers Tutorial on Nov 10, 2017
One of the classic challenges for access control are parking lots and garages, where the user's credential is far from the reader. With modern...
Hikvision 4K IR PTZ Tested (DS-2DF8836IV-AELW) on Nov 10, 2017
The IR PTZ trend continues, now with 4K resolution, with Hikvision releasing its DS-2DF8836IVAEL-W camera, a 4K 1/1.9" PTZ model specifying 200m IR...
Selecting Access Control Readers Tutorial on Nov 09, 2017
Given the variety of types available, specifying access control readers can be a daunting process. However, focusing on a few key elements will...
Milestone XProtect Essential+ Free VMS Tested on Nov 09, 2017
Milestone continues to expand its aggressive free and low-cost offerings, with this year, Milestone releasing XProtect Essential+, part of their...
Top 2017 Trends - Cyber and Analytics on Nov 09, 2017
The 2 clear top 2017 trends, according to IPVM integrator statistics are: Cyber Security Video Analytics This is a change from 2016...

Most Recent Industry Reports

Panasonic Unified Surveillance Strategy Analyzed on Nov 17, 2017
Panasonic is now a "Unified Surveillance" offering, as their ASIS 2017 booth proclaimed: Looking to make a comeback in the security industry,...
Amazon Cloud Cam Is Poor (Tested) on Nov 17, 2017
Retail behemoth Amazon has entered the surveillance market with the Amazon Cloud Cam, the eyes of its just-announced Amazon Key delivery...
Nest Secure Alarm System Tested on Nov 16, 2017
Google's expansion continues, this time into home security with their Nest subsidiary's move into alarm systems. They paid more than a...
Dahua Forbes 'Next Web Crisis' Vulnerability Dispute on Nov 16, 2017
The buffer overflow vulnerability in Dahua products is not in dispute, in fact we covered it when it was first published. What is in dispute is...
Isonas Cofounders Split, Launch Partner/Competitor on Nov 16, 2017
Breaking up is hard to do, especially when door access security is at stake. But that is exactly what has happened at Isonas. Senior employees...
Hikvision China Criticizes The WSJ on Nov 15, 2017
Hikvision, through the Chinese government's authoritative news service, has criticized the WSJ investigation into Hikvision. In this...
Axis Commits To Long-Term Firmware Support on Nov 15, 2017
With the rise of cyber security awareness, and a general increase in hardware reliability, "software warranties" may prove more valuable than...
Hikvision NVR 4.0 Improvements Tested on Nov 14, 2017
Hikvision has released firmware version 4.0 for select NVRs, touting two years of research and development, and claiming "the new generation GUI...
Vivotek Remote Stack Overflow Vulnerability on Nov 14, 2017
A stack overflow vulnerability in Vivotek cameras has been discovered by bashis, the security researcher who has also found vulnerabilities in...

The world's leading video surveillance information source, IPVM provides the best reporting, testing and training for 10,000+ members globally. Dedicated to independent and objective information, we uniquely refuse any and all advertisements, sponsorship and consulting from manufacturers.

About | FAQ | Contact