Web interface

Product Overview

More about the XLT

Comparison & Pricing

Energy Management

Expert System

Request live access

Log in to the live site

The XLT: How does it work over the web?

The XLT Communicates with OEM’s through a web server at ACI Webs in Blacksburg, Va. Requests are made and responses are sent in XML form for allowed recipients. An example is at the bottom of this page.

At the server in Blacksburg, the web server that provides data service has several functional elements:

• The Flash interface in your browser interacts with a Web Service (SOAP) on the primary servers at ACI in Blacksburg.



• The Web Service communicates with a dedicated server object that communicates with the XLT. An XML command from the Web Service to the server “Opens” the site. This opening loads the site data-base into memory, and starts to read all transient data in bulk from the site XLT. It can cover all data in ~8-10 seconds.



• The server itself provides answers to XML requests. It is important to note that there is no required/fixed order or pattern to these requests, they are completely free form inside the bounds of XML structure and the XLT protocol. The server supplies data directly from the site for run-time info, and from a local database for setpoints & configuration info.



• A companion program is constantly checking for changes to data-bases in the sites (~5 min intervals). Any time a change is found, the site database is reloaded to the server (~45 seconds).



• The only IP address the VPN at the SuperMarket Chain’s IT system ever sees or allows is the server in Blacksburg, creating a very high security level.

Version History and Planned Improvements

The web software development has been rapid, spanning four versions in just over one year. To see our user-friendly web interface, look at the screenshots on our Demo registration page, and register for a live demonstration yourself. You'll receive a username and password via email, and you'll be free to explore the data from our stores, seemlessly communicating with RMCC, Com-Trol, and EIL controllers.

• Version 1: Initial prototype. UDP to web & flash. Rendered circuit status on floorplan. December 2006-January 2007.



• Version 2: Flash & UDP for circuit floorplan, alarms, suction, condensors, HVAC. January 2007 - March 2007



• Version 3: Flash & Server XML exchange. Rewrote all XLT interaction to use a caching service. Took advantage of improved speed to add weather, store schedules, Lights, Lighting schedule & HVAC schedule. Added two live stores with XLTs, connected via VPN to Blacksburg, in addition to the demonstration controllers in Blacksburg. Added user administration with 9 authorization levels and administration. Created web tools to administratively add stores & modify circuit & light layouts. March 2007 - August 2007



• Version 4: Expanded existing services to allow write-back of change data: setpoints, analog offsets, overrides, schedules, holidays, relay overrides. All integrated with authorization-level permissions and site security. August 2007 - January 2008.



• Future versions:



• Version 5: Incorporate alarm receiving & distribution, graphing, expert system and real-time energy mapping. (in Development, May 2008)



• Version 6: Incorporate dynamic query engine for ad-hoc queries, global changes, and additional management tools. (in Planning)

Sample interaction with the XLT controller through our Web Services architecture

Request:

Response:

<?xml version='1.0' encoding='UTF-8'?> <XLT CHANNEL='GE0204'> <GET Request='31,1,201,0,3'/> <GET Request='31,1,105,0,3'/> <GET Request='3,1,1,0,2'/> <GET Request='3,1,9,0,3'/> <GET Request='3,1,111,0,3'/> <GET Request='3,1,112,0,3'/> <GET Request='3,1,113,0,3'/> <GET Request='3,1,13,0,3'/> <GET Request='3,1,202,0,3'/> <GET Request='3,1,7,1,32'/> <GET Request='3,1,7,1,36'/> <GET Request='3,1,7,1,2'/> <GET Request='3,1,7,1,3'/> <GET Request='3,1,7,2,2'/> <GET Request='3,1,7,2,3'/> <GET Request='3,1,7,3,2'/> <GET Request='3,1,7,3,3'/> <GET Request='3,1,214,1,3'/> <GET Request='3,1,214,2,3'/> <GET Request='3,1,214,3,3'/> <GET Request='3,1,214,4,3'/> <GET Request='3,1,214,5,3'/> <GET Request='3,1,214,6,3'/> <GET Request='3,1,211,0,3'/> <GET Request='3,1,212,0,3'/> <GET Request='3,1,213,0,3'/> <GET Request='3,1,216,0,3'/> <GET Request='3,1,217,0,3'/> </XLT>

<?xml version='1.0' encoding='UTF-8'?> <XLT Channel='GE0204'> <GET Response=“XLT-GE0204"/> <GET Response=“Com-Trol 6K"/> <GET Response="A01 14'MD FF"/> <GET Response=“Dripdown"/> <GET Response="Hot Gas"/> <GET Response="Disc Air"/> <GET Response="Solenoid"/> <GET Response=" -2.9"/> <GET Response=" -8.0"/> <GET Response=“ 5.0"/> <GET Response=“-20.0"/> <GET Response="MDFF 1-1"/> <GET Response=" -4.3"/> <GET Response=“ -6.2"/> <GET Response=“ 1.7"/> <GET Response="NO_EXIST"/> <GET Response="NO_EXIST"/> <GET Response=" 8:00"/> <GET Response="16:00"/> <GET Response="None"/> <GET Response="None"/> <GET Response="None"/> <GET Response="None"/> <GET Response=" 60.0"/> <GET Response=" 0:20"/> <GET Response=" 0:05"/> <GET Response=" 0:00"/> <GET Response=" 0:00"/> </XLT>