If you will be using existing historical data from E-DAS Ambient systems, the AirVision ImportUtility can convert it to AirVision data with sites and parameters configured. The Import utility can be found in the "Utilities" section of the AirVision menu.



Select:
Data Type(s) to be converted
Date Range

Options are:
Use Site Long name if they exist (provides more descriptive name, now that we have more than 8 characters to use)
Append Logger ID to front of site name (also helpful)
Append Channel Number to front of Parameter name (sorts parameters by logger channel order, rather than alphabetically by SO2, NOX, etc).

The import utility can be run repeatedly over time, so it is recommended that you first just convert configuration and one day of hourly data as an initial test of your E-DAS files. After this, you can convert hourly data (generally 1-3 hours to import a year), and then do minute data (1-3 months at a time) as an overnight process.

Logbook Import
Because the Logbook was stored in MS Access, and MS Access report tools operate in peculiar environment, we were not able to integrate Logbook import as part of the Import tool. The Logbook will need to be imported via command line task, from the \Program Files\Agilaire\AirVision\Server directory:

E.g. (assumes LogBook.mdb)
Edasimporter /D LogBook /P C:\test

E.g. (alternate filename specified)
Edasimporter /D LogBook /P C:\test /F MyOtherFile.mdb

Once the data is converted, a minumum "quick start" checklist of configuration items would be:

• Add any COM ports and modems (if needed) in the Server Configuration. If you use purely IP polling, you can skip this step.
• Test "Link to Logger" connectivity
• Backpoll to test manual data collection
• Use the Task Wizard to set up some basic polling tasks
• Define Parameter Templates for key reporting parameters in the Site Configuration editor.
• Configure any desired report profiles (wind/pollution rose, Violation of standards, etc)
• Set up Users, User Groups, and Permissions