1 / 23

Automated Data Validation Using Florida ADaPT A Consultant’s Perspective Linda Hoffman

Automated Data Validation Using Florida ADaPT A Consultant’s Perspective Linda Hoffman lhoffman@hsweng.com HSW Engineering, Inc. Florida Society of Environmental Analysts Spring 2008 Meeting May 21–23, 2008. Topics Project data quality objectives Project library EDDs

azra
Télécharger la présentation

Automated Data Validation Using Florida ADaPT A Consultant’s Perspective Linda Hoffman

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript


  1. Automated Data Validation Using Florida ADaPT A Consultant’s Perspective Linda Hoffman lhoffman@hsweng.com HSW Engineering, Inc. Florida Society of Environmental Analysts Spring 2008 Meeting May 21–23, 2008

  2. Topics • Project data quality objectives • Project library • EDDs • Automated data review • Data qualifiers

  3. Data Quality Objectives • (DQOs) • MDLs • PQLs • QC acceptance criteria

  4. Project Library • (E-QAPP) • Establishes project QC acceptance criteria • Library should not be modified to minimize or preclude outliers by changing • MDLs • QC acceptance criteria

  5. Project Library cont’d • MDLs and QC acceptance criteria should be changed only when the project DQOs have changed

  6. Project Library cont’d • One ADaPT library per project • Regardless if multiple laboratories used • Project DQOs independent of • laboratories • field events

  7. Project Library cont’d • Labs to use library Client Analyte IDs • Use FDEP-SURR-0XX ID number • May be optional • May be the only one listed • Decide on a convention and communicate with the laboratory

  8. Project Library cont’d • Sort by ClientAnalyteID before adding analytes to library • Determine if analyte is listed multiple times with different names • Use the primary, most common name, rather than the synonym • Resort after adding the analyte • Example • Methyl-t-butyl ether (primary) • Methyl-tert-butyl ether (synonym) • MTBE (synonym)

  9. Project Library cont’d

  10. Project Library cont’d • Analyte not in SVL • Request DEP add analyte to SVL Example: Volatile fatty acids • Based on method 8015 • SVL = 8015 mod. • Analytes vary by laboratory • lactic acid • pyruvic acid • butanoic acid, etc.

  11. Project Library cont’d

  12. Project Library cont’d • Method not in SVL • Performed by lab SOP • Performed by modified EPA method • EDD lists EPA method • Comment indicating that method performed by laboratory SOP for NELAC compliance Example Method performed by modified 8270 by laboratory SOP 8270-ABC123

  13. Project Librarycont’d • Analyte in SVL but not in method • Lab reports additional analytes not listed in method • Add method to project library • Add additional analytes to library method • Add remaining analytes from master library (listed in method) to project library method

  14. Project Library cont’d Example: Create method 8270 project library Add OPPs to 8270 method in project library Add SVOCs from master library to 8270 project library Result is a library with expanded analyte list

  15. EDDs • Request ADaPT EDD in advance • Send library to laboratory • Receive EDD concurrent with PDF • Review laboratory error report

  16. EDDs cont’d • Correct critical errors • Laboratory amends EDD • Ignore non-critical errors • Optional for non-SFWMD projects

  17. EDD Critical Errors • Analyte name in library does not match EDD • Check analyte name / category • Use the primary name rather than the synonym • See previous example for MTBE

  18. EDD Critical Errors cont’d • MDL higher than specified in library • Due to dilution? • If yes, no action • If no, contact laboratory

  19. Automated Data Review • Correct critical errors • Laboratory amends EDD • Ignore non-critical errors • Optional for non-SFWMD projects

  20. Automated Data Review cont’d • Selection of QC parameters • Select all QC parameters • De-select MS/MSD • All data qualified based on MS/MSD results • Otherwise amend data review qualifiers • Time consuming to manually revise/remove qualifiers for each MS/MSD outlier

  21. Consultant’s Goal of Using ADaPT • To consistently apply DQOs to data • To qualify and interpret data outliers accordingly

  22. Summary • Know project DQOs • Project library changes only when DQOs change • One ADaPT library per project • Review error report • Review data qualifiers • Revise qualifiers as needed • Field report must be reviewed independently of ADaPT

  23. Thank You! Linda Hoffman lhoffman@hsweng.com HSW Engineering, Inc.

More Related