More and more clients seek out the obvious benefits of cross-platform integration, and it is the manufacturers desire to give the clients what they want; however, It has been my experience that manufacturers will put out a product and promise integration whether it actually works or not. I was blown away by how common this practice actually is. Here is anexample:
A leading intrusion manufacturer we will call “Burg” recently parted ways with their OEM partner that developed their management software for their high end intrusion panels. These panels are able to not only act as in intrusion system but also a fire alarm and a small access control system. Their OEM software package integrated all three plus added dynamic mapping, live event monitoring, and system reports. When the relationship was about to expire the Burg developed their own software and took it a step further and integrated all of their offerings: intrusion, large access control, and surveillance.
It was about 99% complete when the initial roll-out date was met. It was those customers that wanted dynamic mapping that received the raw end of the stick. Apparently they wanted to import an AutoCAD file; however, due to a time constraints they relied on a common conversion software known as Whip!. Normally this would be acceptable, but in this instance AutoCAD announced that they would not longer support Whip! Files two months before the release date of the new software. After word got back, Burg announced an apology and promised that every effort was being made to correct the small issue in the next revision.
I find it interesting how many integrators actually take the manufacturers for their word on what they are able to deliver. It is essential to bench test a solution before installation if you are installing it for the first time, or at least have a manufacturers rep demo the integration.
