Enterprise Application Integration
Using EAI (Enterprise Application Integration) software Seiki is able to offer an intelligent interfacing solution that can optimise data exchanges between different software products. EAI serves to connect ERP/MRP/PPS/CAD-CAM systems or other databases and software to the Seiki Scheduler database, in order to automate the task of data entry. A number of optional and mandatory data sets are required to provide the interface between the SQL database of the Seiki Scheduler and other systems’ data sources, e.g. SQL database, Microsoft Access or CSV files. This data exchange may be configured to run either in a single direction or bi-directionally, depending on your requirements.
As well as being able to run manually, the EAI can also be configured to run automatically via a user configurable schedule. This may be at a set time each day or after a specific interval. You also have the flexibility to split the interface configuration into a number of sections, each with their own schedule regimen. For example, Company information may be exchanged once a day but Works Order information can be exchanged more frequently, such as every four hours.
Data Exchange Methods
ODBC – This is by far the most common method of importing data from external systems and can be used with many standard database platforms as well as some spreadsheet applications including Microsoft SQL Server (v6 onwards), Oracle, Microsoft Access, Microsoft FoxPro and Microsoft Excel. A detailed structure or schema of the external database, along with expert knowledge would need to be made available to configure the interface correctly. Where this information is not readily available and documented, it may be necessary to request assistance from the external system’s vendor or agent directly. In these circumstances, any additional costs incurred would be the responsibility of the customer.
Comma Separated Value (CSV) Files – An alternative method of providing data to be imported into the Scheduler database is via one or more CSV files. These files are structured such that each records line of data represents a single record, with each record having the individual field values separated by commas. This method differs from the ODBC method above in that the data import now becomes a two stage process. Firstly, the external system is required to generate the appropriate CSV file(s) which is usually the responsibility of the customer to configure and schedule this activity. Secondly, having recognised the presence of the CSV file(s), the EAI product reads the content