Back-end integration combines the data transfer capabilities of the Internet with adequate security to safely transfer data between your business systems on public circuits. This is a difficult process because it requires an understanding of business rules that govern legacy system operations. It also requires robust security processes to transfer the information successfully and safely.

Successful backend integration requires a complete definition of interfaces between current and legacy systems. We use a rigorous methodology to develop interfaces to legacy systems that includes

• In-depth analysis of the legacy systems to determine the business rules that support back-end integration
  This is often the most difficult phase since business rules are not always documented or formally defined. Key players and end users must agree that the business rules are accurate and support the final product.
   
• Business process analysis for each legacy system to determine if integration and/or eventual replacement is desired or required
  It may be more economical to replace a system than to continue supporting it.
   
• New business rules are defined for automation of the interfaces
  This process answers questions such as
• What is the frequency of communication between systems?
• Is communication two-way or one-way (in which direction)?
• Is feedback required?
• Does the data require cleansing?

Our process has delivered many successful projects. It has been accepted by companies such as IBM and SAP as a viable method to integrate legacy systems into ERP systems and Customer Relationship Management (CRM) solutions.

Because this method uses the Internet to transfer data it requires an extensive knowledge of communications security. This knowledge includes information concerning the structure of firewalls to protect corporate computing assets and the architecture of VPNs to ensure that the transactions are not compromised. Our Networking and Security Group provides this assistance.

Our Maintenance Activity Cost Tracking System (MACTS) project illustrates the potential of the system. In this project CACI developed interfaces to legacy systems in all installations and then used FTP transfers to communicate between AS/400 ADABAS legacy systems and the resident application as an important part of the system design. Through these secure transfers CACI was able to provide cost visibility to an enterprise with a $400M annual budget.

For additional information contact Rick Dansey, 703-679-4286, rdansey@caci.com