Functionality:     V3.6S Version 3.6 Standard of NCase monitors the NEAT Database for new events, filters those events based on user criteria, transforms the allowed events and passes the transformed event information to an intended TCP/IP recipient.     The NEAT Database (schema available in Extras), when queried for new Events results in an Event XML (sample available in Extras). The EventXML contains all the information known about the event and acts as the foundation of the data available to be passed on.     The filters used to make determinations about which events should be broadcast and which can be ignored are set on a per Outbound Channel basis. These filters are by: Fixed Asset, Floating Asset, Asset Type, Event Type, and Inbound Channel. Each outbound channel has its own connection type, filter set, transformation set and intended recipient.     Transformations are primarily performed by XSLT style sheets, however once the primary XSLT transformation has been performed, headers and footers (either as hexadecimal or alpha-numeric-symbolic text) and dynamically calculated length (as numeric-decimal or numeric-hexadecimal) may be added. The resulting data can be encoded as a hexadecimal for output and encrypted using a reflexive binary XOR encryption algorithm.     Once the Event data is transformed and massaged into the packet required by the target application, it is passed onto the TCP/IP connection (which may be set to connect on Event Detection or on load).   V3.6W Version 3.6 Web of Ncase performs the same functions as version 3.6 Standard. The difference between the two is the addition of an option to export the final transformed Event data to a waiting ASP or PHP Web Object. This Web Object must accept HTTP POST connection attempts.   V4.0 Version 4.0 of Ncase runs as a Windows Service that is configurable from a Windows GUI. The primary process of V4.0 is similar to that of V3.6W, however, additional functionality has been added. Two TCP/IP Servers are included in the Windows Service, the first allowing for remote administration, and the second allows for EventXML direct from NCompass 4.0 to be supplied, rather than through database connectivity. Event filtration has also been modified: In Ncase 4.0, Events are filtered based on EventXML Element values being equal to (or greater than and/or less than) a supplied value. If no value is specified, no filter determination will be applied to the element.     Additionally, the final transformation process has been stratified and operational ordering included to allow for the most flexibility possible.