The File Import module is used to load XML files generated by data acquisition and handling systems (DAHS) into the Client Tool database.
To begin an import, click the file import module button in the Menu Panel in the lower left corner of the screen. Click the start an import link in the Module Action Panel. The file import: select files screen will appear in the Working Panel.
Only properly formatted XML files with valid XML syntax can be successfully added to the file import: select files grid of the Client Tool. Additionally, all XML files added to the grid must have a valid Facility ID (ORISPL) and Unit/Stack/Pipe ID to be validated for import into the Client Tool.
To select a file for import, click the add file button in the lower right corner of the screen. Select one file or multiple files from the standard Windows file dialog box and click the open button. The file(s) will appear in the file import: select files grid. To remove a file from the file import: select files grid, highlight the file in the grid and then click the remove file button. To select multiple files, hold the ctrl button while clicking files. Once you have selected the correct files, click the import button in the bottom right corner of the screen. The file import: files to be imported screen will display all files selected for import.
The status of the import for each file will be displayed and updated on the files to be imported screen throughout the import process in the status column on the right side of the screen. As the files are processed, a link will appear in the status column that displays the results of the import. To view the details of the import process, click the link in the status column to the view the File Import Validation Report.
It is important to note that for monitoring plan data, the import process merges the data from the imported file with data that is stored in the Client Tool database. Imported monitoring plan data do NOT overwrite existing data. Because the Client Tool must maintain the complete monitoring plan history, imported monitoring plan data are merged with existing data so that the monitoring plan history can be maintained in cases where only the active monitoring plan data are imported into the Client Tool. Imported QA files are also merged with any data that is already in the Client Tool.
Importing an Emissions file will completely replace any emissions data for the associated monitoring location for the given quarter. This includes Emissions Comments. In order to preserve Emissions Comments, it is necessary to submit them along with the rest of the emissions file. Otherwise, Emissions Comments will be overwritten if a new emissions XML file is imported.
Tutorials: To watch various tutorials that briefly explain some of the main aspects of the ECMPS Client Tool, visit the ECMPS Support website.
Feedback: Did this help topic answer your question? Can it be improved? Click here to let us know.