 |
Before data is transferred it passes through a series of filters |
|
|
| NCase has an extensive list of selections to determine the transaction events that will be passed on to other systems. The events filters can be a broad as all events of all tags, or as limited as a single type of event of only one tag. NCase filters can also be configured to include future tags or readers as soon as they are added to the system. |
|
 |
Converges the data into a format that you customize, including encryption options |
|
|
| NCase structure definitions allow for the flexible determination of what pieces of data are sent to other system as part of the event transaction. The options include all information gathered from the tag as well as reader location and date/time of event transaction. |
|
 |
The data is then broadcast to 3rd party applications with an Ethernet of web application |
|
|
| NCase has many options on the formatting of the data structure of the outgoing information. These can include the addition of pre and/or post processing packet headers and footers, conversion to hexadecimal, extensive formatting using XML style sheets, and encryption. Information packets can be either sent to an Ethernet address, originating or receiving, or to a web address via HTTP post or SOAP web service. |
| |
| |