Great Lakes Regional Toxic
Air Emissions Inventory
Steering
Committee Conference Call Minutes
Feb. 22, 2007
Participants
Illinois:
Indiana:
Michigan: Jim Lax and
Allan Ostrander
Minnesota: Chun Yi Wu
New York: Carlos
Mancilla
Ohio: Tom Velalis
Ontario: Cong Doan
Pennsylvania:
Wisconsin: Orlando Cabrera-Rivera
GLC: Jon Dettling
EPA:
Other: Mark Young
Update from Mark
Young on RAPIDS database design
Has been working on the scripts to
build the database and re-build it whenever necessary. These scripts will be
able to re-create the tables. Mark would like to discuss with GLC some of the
standards we should be using for the tables. Jon noted that the new server is
now running and only needs a few configurations to be done before it is ready
for the group to use.
Mark has also been looking at the
calculation protocols and some technical issues with exponents. He has had some
trouble dealing with large negative exponents.
Orlando noted that he has been
working on a list of calculation methodologies that he'll be sending for use in
ensuring the software is able to hand them. Following the
discussion on confidential data at the last in-person meeting, Orlando mentioned
that the current RAPIDS system has the allows to flag the confidential data at
all levels. Mark responded that he's
been working on incorporating this.
The database design will likely be
close to being in final form in the near future and the group can start putting
data into it. At that point, it's likely that many additional issues will be
identified to be addressed.
Allan asked whether there was a
work plan in place for the RAPIDS design and programming work that he could
share within his department. They are considering developing a new system and
would like to judge how the new RAPIDS may play into that. Jon noted that the
documentation they do have is significantly out of date and
should be revisited. He committed to get something to the group within the next
week or two. He also noted that MDEQ staff are welcome to call him or try to
set up a time to have a call with Mark and/or other members of the group on the
topic. Allan noted that Lori Franz of their office may be interested in talking
to Mark or others. Mark emphasized that the development
direction from his perspective is for the GLC priorities at the regional level,
although he's eager to talk to as many people at the states as possible to
generate ideas, etc. Jon also emphasized that the intent is to build a system
that the states can and will use, so working with states to identify potential
synergies is important. The only catch is that the project will depend on decisions
made by the group and the GLC and so if states plan to rely heavily on RAPIDS,
they will need to accept the decisions of the group in terms of its
development.
Chun Yi asked about the
availability of RAPIDS 3.0 to compile the 2008 inventory. Jon responded that
although the RAPIDS 3.0 usage may be limited for the 2005 inventory, it should
certainly be well developed in time for the 2008 inventory. Chun Yi suggested
that like Michigan, Minnesota is also looking at the possibility
of developing or maintaining a new system. Several other states already have in
recent years and others are moving in this direction.
Update on GLC
server
There was another issue with the
GLC's older server in early February. The back-up power unit failed and when
the server was restarted there was a parity error between the server and the
storage array. There is a low level of confidence that the storage array will
perform adequately in the future and so the GLC has decided to replace it
rather than continuing to rely on it. This will cause a slight additional delay
in getting the repository functional again, but should provide more reliability
over the coming period prior to having the new system ready to serve the
repository function. Some group members expressed an interest in getting access
to the repository in the near future to run some queries and make some updates.
Jon will look into the prospect of making this available sooner, while the
details of the equipment replacement are being worked out.
BaP report: final
comments and plans for release
Jon sent an additional update to
the report late last week that includes the changes to forest fire emissions
for ON and MN. The only other change in this version is the inclusion of a
reference regarding creosote treated wood emissions. The EPA had some
information suggesting this may be a large PAH source. While it appears that
this is true, the reference cited shows that it is lower weight PAH and not
benzo(a)pyrene that are primarily emitted.
Ontario has
sent some additional minor comments and Minnesota
and Wisconsin
are developing some comments. These last changes should be sent to Jon by
Monday so that he can send a final draft to the group for agency approval. The
final will likely released in about 2 weeks (March 8th) or slightly thereafter.
Area source
methodologies
MI - Won't be joining an EPA
group; Dennis will be looking at Lamp Breakage.
MN - Will be joining the solvent
group.
NY - Carlos will check with some
colleagues to see if they are planning to participate on any EPA groups.
OH - Won't be jointing and EPA
groups
WI - Someone will join the
residential wood combustion group and Orlando
will be looking into pesticide methodologies.
Cong asked about standardizing the
methodologies, and posting them on the FTP site. Jon agreed to post on the FTP
site the set of methodologies that Orlando
recently sent him by email. The issue was raised of whether it's advantageous
to have shorter or longer methodology documents. Jon expressed that a combined
approach may be the most effective. There's a possibility to have a 1-page
coversheet on each methodology that has the bare essentials and a more expanded
document could contain the background information that might be needed for a
fuller understanding of the methodology and where to obtain the needed
information. It was reiterated that there is a need to identify methodologies
at this stage of the RAPIDS programming to ensure the system is able to handle
them.
The next meeting time and location
was set as May 8-9 or 9-10 in Madison,
Wisconsin. Orlando will begin working on setting up the
logistics for the meeting. Others should begin making their travel
arrangements.
The next conference call will be
2:00 Eastern, March 7.