| |
|
| Many times, customers want to either extend their back office functionality
out to their field personnel and/or integrate field data with existing back office systems. Examples include integration with accounting/finance systems, payroll, ERP, CRM, data bases, etc. Through the use of Agilis’ Rapid Application Development (RAD) Tool, this integration work can typically be completed within days, not weeks or months. |
 |
| |
•
|
Integration Sheet
|
 |
 |
Agilis Systems supports a variety of integration mechanisms depending on the type and depth of integration desired as well as the technical assets available with the customer.
1. Web services:
This is Agilis’ preferred integration mechanism and involves the user making very simple URL calls. It is important to note that these are not SOAP based web services but rather the far simpler REST based calls. This means that the user can even type in a URL in their favorite browser and make a change in the Agilis system. There is little cost involved when this route is chosen.
2. Excel, CSV files:
For some users it is easier to send and receive excel or CSV files. Agilis supports this method as well. Agilis can provide the user with an FTP or Secure FTP account for which these files can be exchanged. The user can specify the format of the files they send Agilis – that is, the user can specify what information can be extracted from what column. There is some cost associated with this method, but not much more than the Web services approach.
3. Custom files:
The user may have some proprietary files that they might need Agilis to interpret and generate. Again, Agilis can provide the user with an FTP or Secure FTP account for which these files can be exchanged. This approach does have cost associated with it, and it depends on the type of file format.
4. Custom feed:
Agilis does support a completely custom integration approach. This can occur when, for example, the user wants to send work orders in real time using an existing system that does not fit any of the mechanisms above. This is obviously the most expensive integration method, but we
do support it.
|
|
|
|
|
