Sign in or 
| Version | User | Scope of changes |
|---|---|---|
| Oct 7 2009, 3:59 PM EDT (current) | vikrantsharma1 | 183 words added |
| Oct 7 2009, 3:58 PM EDT | vikrantsharma1 |
Changes
Key: Additions Deletions
Our Agilaire customers have requested that AirVision handle new and more complex data relationships such as managing data from parameters in a hierarchical fashion.For example, PM filter data that may exist both as a total mass/concentration value, but also may consist in detailed breakdowns from speciation monitors or XRF (X-ray fluorescence) lab data. Ideally, the speciated values should not exist as simply separate database parameters be tied to the overall mass/concentration value in a parent-child relationship. AirVision supports these relationships as part of its original design, a feature unique in its industry rathter than as an afterthought or modification to an existing database.
Parameter configuration also allow the designation of a parent parameter to form parent-child relationships that can be used to drill down in the data editor. A typical example is designating analyzer diagnostic parameters, such as sample flow and box temperature, to be children of the primary analyzer pollutant value (e.g., NOx), so that a suspect reading could be investigated by drilling down in the data editor. Another use could be to group parents & children in a columnar data report.
Parameter configuration also allow the designation of a parent parameter to form parent-child relationships that can be used to drill down in the data editor. A typical example is designating analyzer diagnostic parameters, such as sample flow and box temperature, to be children of the primary analyzer pollutant value (e.g., NOx), so that a suspect reading could be investigated by drilling down in the data editor. Another use could be to group parents & children in a columnar data report.
