Search:
Site Map
Home
Left Middle
Left Bottom
Subscribe
Enter your email address and click the Subscribe button to receive updates via email.


If you are having problems subscribing, click here.
Follow ECMPS Support on Twitter
 
Twitter LogoClick here to follow ECMPS Support on Twitter.
ECMPS Support on Facebook
 
Find us on Facebook LogoClick here to check out the ECMPS Support page on Facebook. Click the "Become a Fan" link on the page to become a fan of ECMPS Support.
Recent Posts
Categories
Archives
 
Blog icon

ECMPS Support Blog


Brief History Lesson, Part 1 -- Tests

Tuesday, January 13, 2009

GlobeMost people do not get excited when the words "Test" and "History" are mentioned in the same sentence. It may conjure up images of sweating through a world history test in high school as you struggled to remember some obscure date that you "memorized" ten minutes before class began.

In ECMPS, the words "Test" and "History" should not cause any anxiety. Instead, they should remind you that the Client Tool is designed as an evaluation and submission tool. To function efficiently, the Client Tool tries to keep to a minimum the necessary data which are used to perform evaluations and to submit data. That is where Test History comes into the picture.

Test history is exactly that. It is a history of the QA tests associated with a particular monitoring plan configuration. The data in the test history report are either data submitted through the legacy systems, data submitted through ECMPS, or data which need to submit the data. The test history for any configuration can be viewed in the Test History report which is found in the QA and Certification Data module of the Client Tool.

When you view that report, you will notice that the Test History Report only includes a relatively small portion of the data which are part of a test. For instance, for a linearity test, each of the individual injection records is not included in the report. Instead, the test history only includes the essential information which the Client Tool needs for performing evaluations. The figure below shows an example of the information included in the test history report.

Detail from Test History Report for a Linearity Test

The test history information included for this linearity test include:
  • Monitoring location (unit, stack, or pipe)
  • Test number
  • Component ID
  • Component type
  • Begin date and hour
  • End date and hour
  • Span scale
  • Reason for the test
  • Test result
The last column is the Submission Availability Code (SAC) which is not part of reported data, but indicates the status of the data. If the SAC is "Submitted to EPA Host System", the test has already been submitted to the EPA, and it cannot be submitted again unless permission is granted to resubmit. In the case where permission has been granted to resubmit, the SAC would be "Resubmission Required" or "Permission to Resubmit Granted".

The test history is actually generated when the test is evaluated in the Client Tool. That is why you can view the test history of a test which has yet to be submitted. In that case, the SAC would be blank. Once the test has been submitted, the SAC would change to "Submitted to EPA Host System".

0 Comments:

Post a Comment

<< Home

 

This Web site is the property of Perrin Quarles Associates, Inc. a contractor to the U.S. Environmental Protection Agency.

  • Facebook link
  • Twitter link
  • RSS link