The esCollate system has been developed with Microsoft .NET technology using a layered architecture.
The layers are:
MS SQL Database
The database has three instances, they are:
The Configuration database contains the data entered through the Administration application. This data is not made visible to the client applications until an Apply Configuration process is completed. Therefore it is possible to make make a series of changes to the Configuration database without these changes being applied to the Runtime database until the Administrator is satisfied that the changes are correct.
The Runtime database contains all of the production data collected by esCollate, except for the data stored in the Binary Files.
The Export database contains a summary of the data in the Runtime database in a format that is easy to understand. The purpose of the Export database is to provide the customer with a database they can use for reporting and for synchronising external systems.
The Binary Files are a purpose built set of files that are optimised to store large numbers of fixed format records. Binary Files are used to store data collected from Sensors such as the Down Time and Production Count records.
esCollate Server Software
The esCollate Server software includes:
The esCollate Configuration server services requests from the Administration application and interfaces with the Configuration database.
The esCollate Runtime server services requests from the esCollate client applications and interfaces with the Runtime database and Binary Files.
The esCollate Report server services requests from the esCollate Reports application and interfaces with the Runtime database and Binary Files. The Reports server also manages the Export database and automated CSV file exports.
The esCollate Server Manager provides:
The Data Collector server communicates with the Data Collector client to collect data from an OPC interface. The Data Collector server interfaces with the Binary Files and the Runtime Server.
The following attributes are common to many components:
The Name attribute is a unique identifier for the component. The Name attribute is sometimes displayed in buttons with the Factory Client or Production Scheduler application and care should be taken not to make names too long. For example the Line Name and Line Area Name attribute are displayed on buttons and regularly accessed. If these Names are too long it can be awkward for the User to make selections.
The Description attribute can be used to provide additional descriptive or identifying information. For example Product descriptions can help the User verify that they have selected the correct Product when creating an Activity.
The User Reference is a text attribute that is not used within any esCollate application. The User Reference is intended to be used to store customer specific information for use by the customer. The User Reference attributes are included in all exported data so that they can be used to collate data or coordinate data with other applications.