Proteus Integration Highway
To help those organisations that have based their core software strategy around products such as SAP, J D Edwards, and SAGE etc. and require extended WMS functionality and a highly cost efficient deployment, Proteus have successfully provided logistics companies with the capability to interface customised Proteus WMS modules with core third party systems.
Generally these provide real time response, linking seamlessly to third party core systems. Such projects, and indeed our development processes, have passed vigorous vetting and testing by major account customers who provide testimony to our well developed and proven skill-sets.
Further information is provided on our website news section, specifically the GKN case study which was based on an SAP integration project - http://www.proteussoftware.com/news/gsk-pharmaceuticals-gets-boost-they-...
Integration of Legacy Systems with Proteus Warehouse Management Systems Software
Over 90% of Proteus implementations involve integration with existing legacy systems by way of a data interchange. The process is non intrusive and does not create or change data directly contained with the legacy database.
The systems are usually set-up to be loosely coupled allowing them to run independently without any dependency on the other system being available. The transfer of data can be available on demand (real time) or scheduled upon a user specified frequency.
Audit trails are provided whenever data is imported or exported. The audit provides details of date and time of transfer, file details where appropriate, the data transferred and the result of the validation of incoming transfers.
Proteus uses a separate integration ‘layer’ which manipulates data received into the required formats, determined by a systems specification, which is agreed by Proteus and the legacy system provider.
Files are can be transferred from the legacy system to the Proteus Server via several methods including, FTP, WAN Transfer, LAN Transfer, AS2 or Sonic.
Data Extraction from Legacy Systems - Process
Existing legacy system will export the data to an agreed format of specific file type. Typical file types include CSV, Pipe separated, EDI, XML etc.
The files will be transferred via the desired method from the Legacy system server to the Proteus server.
The Proteus ‘Integration Engine’ will process and extract the required information from the data files to create or update the Proteus database as per the systems specification.
Data typically extracted from Legacy systems and imported into Proteus include, Customers, Suppliers, Items, Distribution Orders (Sales Orders) and Expected Receipts (Purchase Orders).
Data Export to Legacy Systems - Process
Proteus can also provide information to Legacy systems in a variety of file types to an agreed format, e.g. CSV, Pipe Separated, EDI, XML etc.
Data typically extracted from Proteus and imported into Legacy systems include, Stock Movements, Stock Receipts and Despatched Orders.
The files will be transferred via the desired method from the Proteus server to the Legacy system server.
The legacy system provider will program a separate integration gateway to manipulate and filter the data before updating the legacy system database.
Working with Multiple Systems
The Proteus system can function simultaneously with multiple systems – each running a different application in real time. e.g. Transport System, Back Office Financials, Information to Carriers etc.
The Proteus integration process has successfully undergone intensive testing by various blue chip organisations including Danone and Glaxo Smith Kline. This has included the cycling of outbound information to multiple international points of distribution (running legacy ERP systems) and the concurrent return of information to the Proteus database via those systems.
For further information please contact Linda Rodway on +44 (0) 121 717 7474, who can arrange a detailed discussion with our Technical Director, Tony Pearson.