Press Releases-Coming Soon

RRA Articles

The Interface Isn't Working.....  

By RRA Consultant Lynelle Harper

Ever get that call?  That's what the end-user sees. When is the last time a message was received? I don't know.  Where to start, where to start. Yes, the interface is up and running. Yes, messages are passing. No, there are no error messages. If it were only this simple.

There are so many things that can cause an interface to appear to be not working. Two of the bigger contributors are upgrades or maintenance releases, and downstream system changes. Like many clients, there are about a gazillion projects going on, with not enough time or resources to go around. And the bigger an organization gets or the number of projects on that To Do List keeps growing, the more likely it is that the communication about that small system change, seems to never make it where it needs to go.

We would probably all agree that interfaces are considered to be one of the mission critical systems, so how did this get missed? Interfaces are often overlooked simply because they run so well that people only notice them when they are missing or not passing the expected data.

What can we do to make sure we don't get calls like this? Here are some guidelines that can be used for any system:

·        If you are upgrading your primary system, be sure to do a thorough gap analysis between the new standard product and your existing system with changes. (by the way, are  all of your changes documented?). It may take time today, but it will definitely payoff in the future.

·        Read through the release or maintenance documentation. These should provide details on what changes have been made. For interfaces, this means reading about the other modules or applications that you have interfaces with, for example, Orders/Results, ADT/REG, etc.

·        Document your changes.

·        If you are an upstream or downstream system, and you are planning system changes, do include analysis of the interface(s), and working with the interface team.

·        For upgrades and installs, it is highly recommended to have at least one full time person dedicated to the interfaces, in terms of performing the gap analysis, change analysis, coordinating changes, communications between the interface engine group, application teams, and downstream/upstream systems. This person should be knowledgeable in interfaces, as well as the various applications and associated systems.

·        Document your changes.  

·        Don't forget to test prior to integration testing, even if there doesn't appear to be any changes.

And finally, communicate!

Following these guidelines will help ensure that your interfaces continue to run silently successful!