Pros and Cons of Using Middleware with a Teller Cash Recycler
Determining the best way to operate teller cash recyclers (TCR) in your branch environment can be difficult. Understanding the available options is an elemental part of making an informed decision. Today, I'd like to discuss deploying TCRs in a soft interface or middleware format.
Application middleware attempts to address the functionality issues inherent in standalone applications while at the same time providing added functionality often lost in direct integrations. In these environments (much like standalone environments), application middleware is resident on the local PC. However, application middleware “maps” commands and command statuses to and from the TCR and teller application eliminating the need for double keying by the teller (save for balancing).
- Low cost - limited / no need for custom application development
- Minimal double keying - eliminate need to double key outside of balancing
- Application agnostic - not tied to specific application, protects investment
- Ease of use - simple to train, use, manage exception conditions
- Added step in balancing - need for added step, opportunity for error
- Enterprise rollout - can be cost-prohibitive in larger implementations
- Teller application changes - may threaten stability of “mapping”
- Support - generates need to support yet another application in branches
Soft interfaces can be an attractive alternative to lower-functionality standalone or more costly direct integration options. Educating yourself on the available integration strategies and carefully comparing and contrasting your options will ensure a smart choice is made!