XML is the de facto standard for machine-to-machine communication. It’s even readable by mere humans, because it is written in plain English. The beauty and power of XML’s simplicity is easy to see; take a look at the following sample XML string:
<SecuritySystemMessage>
<EventType>Alarm</EventType>
<EventSpecifics>ForcedDoor</EventSpecifics>
<Location>LabSideDoor</Location>
</SecuritySystemMessage>
Velocity includes an XML writer that can be set to “broadcast” security system events and transactions across the network to other systems that are authorized to “listen.” The XML listener monitors the XML stream, watching for any events the customer has designated as important.
Then, if and when found, the key event (“forced door,” etc.) triggers one or more predetermined actions. Some of the many possible actions that might be initiated include: activate/move cameras, change recording modes, fire relays, turn on microphones, dial phones, post information to a webpage, send pages and emails, play recorded messages over the audio system, and run macros and other programs that initiate even more actions.
And with Velocity, interoperability works both ways: authorized third party systems can also send commands to the security system for execution. For instance, the data on a newly hired employee can flow automatically from the human resources system to not only the physical security system for instant credentialing and door access, but also to the IT system for instant assignment of network log-on rights and permissions.
Velocity utilizes XML for reporting and control, and an API for person/credential data interchange. For a more detailed technical explanation of XML and APIs, please refer to the Hirsch Interoperability White Paper. (pdf) |
