Some Basic Consideration in the Design of an Air Pollution Monitoring System

Abstract

Quantified air quality and meteorological information provided by an air pollution monitoring system must be geared to the legally prescribed functions of the control agency. The network must be treated as a vital component of the total integrated data system that supports agency activities in air resources management and control. It should be closely interphased with data systems for emission inventory, registration and permits, violations and complaints, fuel use, emission reduction plans, land use, demographic projections, and urban planning. Compatibility with neighboring and statewide or regionwide data systems is essential for coordination of effort, especially under episode conditions.

The network should be planned on three levels, static, semi-automatic, and fully automatic, to provide monthly, daily, and up-to-the-minute measurements, respectively. Optimization of network specifications requires a three-way balance of hardware, control objectives, and agency resources (capital facilities, manpower, funding, etc.), of which the first two are realistically governed by the third.

A monitoring network could serve a wide range of functions, and there are pressures and temptations to cater to all possible users. A number of functions are listed; an order of priority should be determined. Experience shows that far more data tend to be generated than can be analyzed, assimilated, and utilized. Rapid data acquisition and on-line processing capabilities of present-day automatic networks could, without effective planning, result in mountainous backlogs of unassimilated information.

A systems engineering approach to planning will ascertain that preliminary requirements are critically scrutinized, and only genuine requirements that meet the test of constraints (natural environment, economic, legal, social, political constraints, and manpower resources) will be translated into performance specifications. By means of this approach, design characteristics that are extraneous or peripheral to the principal network functions can be identified as low priority luxuries, whereas seemingly expensive items may be justified on the basis of data reliability or long-range savings in operation and maintenance requirements.