Agilaire’s commitment to its agency customer base has always been that agencies under active support would always receive upgrades to meet EPA reporting requirements related to the managed data / assets that are not feasible through other systems or external measures.

To this end, Agilaire will be updating the AirVision product to meet the new format requirements of the average/sample data transactions.  For users with the Monitor Assessment module, support will also be provided for QA transactions previously covered under that module.

Fortunately, the underlying database structure that supports our existing Asset Tracking module already contains most of the necessary fields, and the structure for tracking when an analyzer or sampler moves from one site to another, and supporting the required temporal reporting.

More specifically:

• Existing assets have fields for manufacturer and model. Right now these are free-form fields, and will need to be aligned with a specific list of EPA codes to add new fields for “UP Manufacturer“ and “UP Model.”  These will be available on the parameter configuration screen, as well as in the Asset Tracking module.  A transitional script tool may assist users in translating existing freeform selections to the EPA standardized list, but some manual review and override will likely be required.    After some time, the legacy manufacturer/model free-form fields can be removed.
• A new field will be added to the parameter settings for the Feed ID.   This will likely be initially built from a concatenation of the monitor code and POC code, but the user will have the freedom to override and edit this, if desired.
• The asset tracking module currently has space for 3 unique asset identifiers- serial number, an asset tag, and a third identifier for optional use. We will likely add a fourth field for “UP identifier”, and will pre-fill the value with the asset tag (or the last five digits, if longer).  Again, this will just be an attempt to pre-fill for convenience, but the user may edit the value if desired.

The combination of these new fields will support the UP data transactions.

The current design of the AirVision database already treats the asset entity as separate from the site/parameter record.  For users with Asset Tracking, they will continue to use their Asset Tracking Editor to move assets to and from different sites.

For users without the Asset Tracking module, a new editor will be added, allowing assets to be created, modified, and assigned to particular sites in parameters. Once assigned, they can also be moved, and AirVision will automatically track the time period that a particular asset has been used at a particular site/parameter combination.

The UP data report will then look at this table to know which assets to use for each hour, and combine with normal data records from the parameter with the correct asset meta data (make, model, feed, equipment ID) for each reporting record (hour/sample).    The same process can be used to create the fields for the QA transactions.

Yes, an Excel spreadsheet will be provided for agencies not already using Asset Tracking.   Users can fill out with the manufacturers, model numbers, and unique IDs. The spreadsheet will then generate insert scripts to add the initial records into the asset table. A second script can then be generated to perform the initial site and parameter assignments.

Up to now, we have been on pause for development, pending finalization of the format and Meta data requirements by EPA and their contractor. Based on the most recent call, it appears these requirements are sufficiently finalized to move forward.  The meta data spreadsheet can be provided by the end of September to allow user sufficient time to collect and enter data in preparation for the upgrade.  Code changes will likely commence in September, again with necessary pauses to confirm finalization of EPA requirements, but if requirements are indeed finalized by EPA by the end of September, we see no issue having a release available in early January, far in advance of the EPA deadline.

Yes, all existing forms in the monitor assessment module have had both date and time available from the initial design, so this is easily supported.

These fields are currently optional, and not expected to be reported for static sites, as they would not change hour by hour.    For mobile sites, a new site property will be added to designate a site as a mobile site, and if selected the UP data report will look for data from other parameters at the site with the parameter templates LATITUDE and LONGITUDE, and use the values from those parameters to report that information for the other measurements.  AirVision will only report those optional fields for sites marked as mobile sites.