During signup for Beta testing, Beta testers were requested to select a particular configuration for testing. The reason for this was to limit the amount of data that needed to be loaded on the EPA Host System.

For each configuration submitted, monitoring plan, QA, and emissions data were loaded. As would seem fairly obvious, the data which can take a long time to load is the emissions data. We continue to improve the data loading performance, but it will still take a significant amount of time to load all of the emissions data that will need to be in place prior to the production release.

The monitoring plan data, on the other hand, does not take very long to load. Because of this, all monitoring plan data are currently loaded on the EPA Host System, and they are available to be accessed as long as a Beta tester has the access rights to the data. (Note, the monitoring plan data on the EPA Host System for Beta testing are from a "snapshot" taken in July of the current monitoring plan data. Any changes to the monitoring plan data made recently will not be reflected in the data seen in the Client Tool.)

The way that the Client Tool is designed, with access to the monitoring plan data, the Beta testers can work with any QA and emissions data that they can import into the Client Tool.

To provide Beta testers with more data, we can provide testers with access to additional monitoring plan data. Note, the access with not include QA and emissions data that can be retrieved from the EPA Host System. For more data, send an email to .

This is summarized in a new FAQ in the Client Tool section.

I do not see data for one of my facilities. How do I get access to data for that facility?

When Beta testers signed up for Beta testing, they were asked to indicate a configuration which they would like to test. This was done by submitting a facililty (by ORIS code) and configuration in their request to participate in Beta testing. This information was used for loading the data on the EPA Host System. For each configuration that was indicated, monitoring plan, QA, and emissions data were loaded.

However, access to the data is provided on a facility level. If a facility has more than one unit, the tester will have access to all of the units associated with that facility. The difference is that QA and emissions data will not be in the EPA Host System for these other units. That does not limit a tester from working with data associated withe these units. The monitoring plan data will be automatically retrieved from the EPA Host System, and the tester can work with QA and emissions data by importing it into their Client Tool.

Beyond the facility which was indicated in the request to participate in Beta testing, there might be additional facilities that you would like to test. In that case, send an email with the ORIS code to .

Labels: FAQ