Formerly Used Defense Sites Chemical Database (FUDSChem) User Manual

Transcription

1 Formerly Used Defense Sites Chemical Database (FUDSChem) User Manual Version Prepared by: Environmental Synectics, Inc. Sacramento, CA

2 Table of Contents Introduction New Features FUDSChem Workflows FUDSChem Roles and Responsibilities Log In to FUDSChem Portal Electronic Quality Assurance Project Plan (eqapp) Data - eqapp Setup Tool Project PALs Copy QAPP Methods Matrix Sample Prep QC Elements PAL Associations Analyte Limits Holding Times Analyte Criteria QAPP Reports Worksheet # Worksheet # Worksheet # Worksheet # Establish Locations Manual Loading Bulk Loading Sampling Event Planning System Generated Chains of Custody and Bottle Labels Load Field Data FUDSChem Event Tracking Reports Event Status: All Data Types... 58

3 7.2 Event Status: Chemistry Event Status: Chemistry Detail Screen Electronic Data Deliverables (EDDs) Using FUDSChem Run Screening Checks Valid Value Errors Submission Errors Loading Flat Files Data Review / Approval Review Chemistry Data Data Validation Data Review Checklist Sample Qualification Validation Reports Review Validation Reports (USACE Role) Review Other Data Types Data Tables / Reporting Chemistry Results by Sample Delivery Group (SDG) Preliminary Chemistry Results Approved Project Tracking Create/Track Project(s) Create/Track Event(s) FUDSChem Library Upload Documents Search for Documents Retrieve Documents Maps FUDSChem Support Glossary Terms Coming Soon Appendix A Checks Performed on SEDD Files Appendix B Recommended Best Practice for Location Naming Appendix C Electronic Data Specifications

4 List of Figures Figure 1 FUDSChem Dashboard... 7 Figure 2 Communications Log... 8 Figure 3 Login Screen Figure 4 District Selection Dropdown Figure 5 TOOLS, Data - eqapp Setup Figure 6 Project Tab Figure 7 PAL Tab Figure 8 Copy QAPP Tab Figure 9 Methods Tab Figure 10 Matrix Tab Figure 11 Sample Prep Tab Figure 12 QC Elements Tab Figure 13 PAL Associations Tab Figure 14 Analyte Limits Tab Figure 15 Holding Times Tab Figure 16 Analyte Criteria Tab Figure 17 UFP QAPP Worksheets Figure 18 Worksheet # Figure 19 Worksheet # Figure 20 Worksheet # Figure 21 Worksheet # Figure 22 TOOLS, Data - Submission Figure 23 Selecting Location Data Type Figure 24 Location Interface Figure 25 Location Site X-Reference Interface Figure 26 Certify LDI File Figure 27 Select Event Planning Figure 28 Event Planning Main Tab Figure 29 Event Planning Assigned Methods Tab Figure 30 Event Planning Assign Field Samples Tab Figure 31 Assign Field Samples Interface Figure 32 Field Tracking Interface... 50

5 Figure 33 Data Submission ChemField Dropdown Figure 34 ChemField Interface - Locations Figure 35 ChemField Interface Add Field Data Figure 36 ChemField Interface Add Field QC Figure 37 ChemField Interface Lot Number Figure 38 Reports Event Tracking Reports Dropdown Options Figure 39 Event Status All Data Types Report (Dropdown Menu) Figure 40 Event Status All Data Types Report Figure 41 Event Status All Data Types Report (Key) Figure 42 Event Status Chemistry Report Figure 43 Event Status Chemistry Detail Figure 44 Tools Dropdown Figure 45 Data Submission SEDD Figure 46 SEDD Upload Files Pop-Up Figure 47 SEDD Errors Figure 48 SEDD Error Report VVL Errors Figure 49 SEDD Error Report Submission Errors Figure 50 Screen and Certify Figure 51 Zero Errors Figure 52 Reports Dropdown, Electronic Data Specification Figure 53 Electronic Data Specification Figure 54 Reports Dropdown, Results by SDG, Preliminary Figure 55 Export to PDF Figure 56 Data Review Checklist Figure 57 Sample Qualification Figure 58 Validator Detail Report Figure 59 Library File Submission Dropdown Figure 60 Library Pending Approval Tab Figure 61 View Library File Figure 62 Library File Approval Figure 63 Data Approval Dropdown Figure 64 Data Approval Figure 65 Environmental Data Reports Dropdown Figure 66 Chemistry Results by SDG Preliminary Report... 87

6 Figure 67 Chemistry Results by SDG Preliminary Report (Qualifier Definitions) Figure 68 Chemistry Results, Approved Report Figure 69 Event Tracking Reports, Project Tracking Figure 70 Project Tracking Report Figure 71 Tools, Data - Event Planning Figure 72 Create/Track Projects Tab Figure 73 Create/Track Event(s) Tab Figure 74 Library File Submission dropdown Figure 75 Library Submission Metadata Figure 76 Library Dropdown - Search Figure 77 Library Search Figure 78 Advanced Library Search Figure 79 Library Document Retrieval Figure 80 Library Document Retrieval (Retrieved Document) Figure 81 MAPS Tab Figure 82 Export to Google Earth Figure 83 Location Information Figure 84 Location Specific Data Type Report

7 Introduction FUDSChem is a comprehensive data management platform available to USACE personnel and contractors to support the investigation, remediation, and monitoring of Formerly Used Defense Sites. FUDSChem has the capacity to store all chemical, geological, and hydrogeological data associated with these sites. The system can be used to plan sampling events, track projects, validate analytical data, generate final reports, and view data in spatial systems. While all of these tools are available to contractors and USACE personnel, they are not always required. To determine what workflow has been chosen for a particular district, confer with the district s designated FUDSChem point of contact at the Corps. The project dashboard seen below provides a district level overview of activity on the FUDSChem portal. This window displays record counts for different data types, number of documents accessible in the library, and active users. Also available is a communications log and project calendar to facilitate collaboration on the FUDSChem portal. Figure 1 FUDSChem Dashboard Getting Started: To activate a project on FUDSChem, send a request to fuds.support@synectics.net with the FUDS property number and project name. The project will be activated and will show up in the appropriate dropdown menus. Page 7 of 115

8 1.1 New Features Since the last version of the user guide the following new features have been implemented: 1. eqapp Setup Tool (see Section 3.1) 2. Project Tracking interface and report (see Section 11.0 ) Information on updates will be noted in the communications log, shown in Figure 2. Figure 2 Communications Log 1.2 FUDSChem Workflows FUDSChem contains various tools to help meet data quality objectives and optimize data management efforts. The workflow models for contractor and USACE performed projects are provided in this section, and the box color indicates which organization is responsible for the action item. Section numbers of the User Manual that describe how to accomplish the task in the workflow are shown for each step associated with FUDSChem. Types of data that are required for active projects by the FUDS program are shown on each workflow. Recommended data types are also shown; USACE project managers need to determine which workflow will be used for their projects, along with which, if any, other data will also be required. This information will need to be communicated to Synectics at the time that the project is activated. Page 8 of 115

9 Historical data may be loaded into FUDSChem by the districts or their contractors as well. Any project with associated data in FUDSChem will be available to authorized users whether or not the project is active. Therefore, historical data acquisition does not require a separate workflow. Note that only projects for which data (including historical data) is being acquired will appear for users in the data submission tools. Though all projects will be visible on the dashboard for every user, a user is only able to load and manage data for projects where they have been given access permissions. USACE users generally have permissions on all projects in their district and therefore, will see more projects than a contractor user. Permissions are discussed in Section 1.3. The following pages cover a workflow overview that directs the user to four different paths for data acquisition into FUDSChem, as determined by the USACE Project Manager: 1A: Work performed by contractor FUDSChem used for data management, Automated Data Review, and reporting 1B: Work self-performed by USACE FUDSChem used for data management, Automated Data Review, and reporting 2A: Work performed by contractor Some or all data management, Automated Data Review, and reporting performed using systems external to FUDSChem; eqapp, location data, and validated data loaded to FUDSChem at the conclusion of the event 2B: Work self-performed by USACE Some or all data management, Automated Data Review, and reporting performed using systems external to FUDSChem; eqapp, location data, and validated data loaded to FUDSChem at the conclusion of the event Page 9 of 115

10 Environmental Data Flow in FUDSChem Funded Project Identified in Annual Work Plan Project Executed by Contract? YES Project Fully Utilizes FUDSChem? YES 1A NO NO 2A 2B NO Project Fully Utilizes FUDSChem? Decision Points Off-Page Connector YES 1B For New Projects, Required Field Data: CHEMFIELD, LDI For New Projects with Groundwater Data, Strongly Recommended Field Data:WCI, WINT, WMI, GWD Other situations may generate Field Data that is appropriate to capture in FUDSChem. Other specifications exist and should be used where appropriate.

11 5. 0) )

12 5. 0) )

13 5. 0)

14 5. 0)

15 1.3 FUDSChem Roles and Responsibilities The following table describes the main types of users that are active on the FUDSChem system, the tasks they would typically perform, and the specific security group memberships they must have in order to perform those tasks. The group memberships of any user can be viewed in the Team Directory by going to QUICK LINKS, Team Directory and clicking on the Permissions hyperlink. User Description Security Memberships General User General Users are not required to load, review or General Users approve any data types. These users have read-only access to all approved data, are able to run reports and export approved data for viewing in Google Earth. General users constitute the vast majority of all users on the system. Casual database users, such as project managers, risk assessors, geologists, hydrogeologists, project stakeholders and regulators typically require general user security membership only. Library User Library Users are able to upload electronic documents to the project library, assign any required metadata, and certify the document as being ready for review and approval. Documents are not available for general users until they have been approved. Laboratory User Submission User Data Validator Laboratory Users are responsible for screening and delivering the electronic data deliverable (EDD) and the electronic version of the laboratory report (PDF) for samples analyzed by the laboratory. Submission Users are responsible for screening and delivering a variety of different non-laboratory data types. In addition to submission of the electronic data, these users are also responsible for delivering supporting electronic documents (PDF) into the project library. Non-laboratory data types may include location, groundwater elevation, well stabilization parameters, well construction, etc. Data Validators perform manual and automated review of laboratory data. These users are responsible for reviewing ADR reports, manually adding and removing validation qualifiers, and uploading final validation reports to the project library. General Users Library Submission Users General Users Library Submission Users CHEMLAB Submission Users General Users Library Submission Users xxx Submission Users (ex: LDI Submission Users) General Users Library Submission Users CHEMVAL Review Users Page 15 of 115

16 User Description Security Memberships Project Chemist USACE Project Chemists have the responsibility for reviewing and approving qualifiers that were applied during the data validation process, and the overall review and approval of the laboratory data itself. Further, the USACE Project Chemist is generally responsible for the review and approval of electronic laboratory reports and data validation reports, after which they are available for viewing by general users. General Users Library Submission Users Library Review Users CHEM Review Users CHEMLAB Review Users CHEMVAL Review Data Manager User Administrator System Administrator Data Managers are responsible for the successful operation of the database, and are granted security memberships that allow them to create and manage events and monitor in real time activities taking place on the system. User Administrators are able to create accounts, reset passwords, and assign security memberships to individual users. Because of security considerations, these permissions are assigned to a very limited number of users. System Administrators have need for any or all of the security memberships listed, in order to provide end user support or perform system troubleshooting. Users General Users Library Submission Users Library Review Users Managers General Users Administrators As required NOTE: Due to difference in permissions, the screenshots in this user guide may show tools which the reader does not have permissions to see. Page 16 of 115

17 Log In to FUDSChem Portal 1) Navigate to FUDSChem.com 2) Select Login in the upper right hand corner of the window. 3) Enter Username and Password provided by Synectics, click OK. NOTE: To request access to a new district or property, or new permissions on an existing district or property, send request to fuds.support@synectics.net with the following information: full name, title, organization, phone number, physical address, district, property, project, and permissions. District administrators will eventually perform this function. If a contractor receives a new project from a new district, they will need to request access to that district and project as well. They will be able to use the same login for both districts and will select the desired district after logging in (see Figure 4). User dropdown menus will contain only the districts that the user has permission to access. Figure 3 Login Screen Page 17 of 115

18 4) Select the desired USACE district from the dropdown menu seen in Figure 4 below. Note that only districts the user has been given access to will show up in this dropdown menu, so it will look different from the screenshot below. The Formerly Used Defense Sites Program option is for internal use only and will not be accessible to most users. Figure 4 District Selection Dropdown Electronic Quality Assurance Project Plan (eqapp) The FUDSChem system houses an electronic version of the Data Quality Objectives (DQOs) contained in each project s USACE approved Uniform Federal Policy Quality Assurance Project Plan (UFP-QAPP). This DQO information is used during the initial screening process to ensure that incoming laboratory data is compliant with the project s UFP-QAPP, and in the Automated Data Review (ADR) process to identify quality control outliers as well as apply qualifiers to sample results. The electronic QAPP information is established during the planning process prior to the start of a FUDS project; the USACE project chemist is responsible for reviewing the electronic QAPP data to ensure consistency with the UFP-QAPP. The electronic QAPP tables can be viewed by selecting REPORTS, Environmental Setup Reports, and selecting the desired data table. NOTE: The project will be chosen in the dropdown menu once the new window opens for the report. Once approved by the USACE project chemist, the electronic QAPP information will be available through FUDSChem to all members of the project team. It is not downloaded or otherwise exported for use in pre-screening laboratory data, in order to ensure that all incoming data is screened against the approved criteria. However, the data is available in PDF or Excel format for inclusion in reports or for the laboratory s use in establishing project-specific valid values. The Data - eqapp Setup Tool is a mechanism for contractors to upload electronic QAPP information into the system. The project setup will be based off an approved UFP-QAPP that contains all DQOs for the Page 18 of 115

19 project (analytical methods, analyte lists, spike lists, surrogate lists, and associated evaluation criteria). This tool can also be used to create and export UFP-QAPP worksheets 12, 15, 18, and 19, and may also be used to aid in the development of the UFP-QAPP. Additional worksheets will be available in the future. Environmental Setup Reports, which summarize the current eqapp setup and are available in Excel and PDF formats, can be generated for the USACE project chemist to review. Synectics will also coordinate with the USACE project chemist to approve the electronic QAPP through the Data - eqapp Setup Tool. 3.1 Data - eqapp Setup Tool The Data - eqapp Setup Tool allows the user to make changes quickly and easily to a project setup. It is located under TOOLS, Data - eqapp Setup on the menu bar. Figure 5 TOOLS, Data - eqapp Setup Page 19 of 115

20 3.1.1 Project After navigating to TOOLS, Data - eqapp Setup, several tabs will be visible. The Project tab can be used to certify or approve a project setup, which will lock the setup to prevent changes. The Project tab also displays information such as the QAPP Status and the date and time when it was last certified and/or approved. In order to track versioning, if the user unapproves or uncertifies the eqapp Setup to make changes, they must first provide a reason for change. Additionally, the user may select other users to notify when the eqapp Setup is certified, approved, uncertified or unapproved. To begin a project setup, first select the Project Name from the dropdown in the upper left hand corner of the Data - eqapp Setup Tool. The Add Screen Check button, directly to the right of the Project Name dropdown, can be clicked to add screening checks to the project. Screening checks are discussed in Section 8.1. Figure 6 Project Tab Page 20 of 115

21 3.1.2 PALs The PALs tab displays a list of available Project Action Limits in the left hand column that can be copied into the project as project action limits or screening criteria. The list generally contains the two latest versions of the EPA Screening Limits. To add limits to the project, the user will choose the desired limit (1) and use the right arrow (2) to add it to the Destination Project Action Limits section (3) (see Figure 7). The user can add a custom PAL by creating a creating a csv file with the following columns: CAS, LIMIT, UNITS. CAS should contain the Chemical Abstracts Service (CAS) Number for the desired analyte. LIMIT should contain the numerical limit for that analyte. UNITS will contain the units. NOTE: The units in a custom PAL file should all be the same. Do not include mixed units in a custom PAL file (for example including mg/l and ng/l in the same file). An optional ANALYTENAME column may be added in front of the CAS column for user reference in populating the file. The file can be uploaded with this column in place or with it removed. Once the csv file is prepared the user will use the green + button to add a new custom PAL, then fill in the information outlined in the Custom Project Action Limit interface (4), and click the floppy disc icon to save. The custom PAL will appear in the Destination Project Action Limits section. While the custom PAL is highlighted, the user can click the up arrow icon to upload their csv file and add their custom values. After uploading the user should be sure to click the floppy disc icon to save again. To delete custom limits, use the red X button. NOTE: The user can check that the custom PAL values were uploaded correctly, by going to Reports, Environmental Setup Reports, Regulatory Limits. If the custom PAL values uploaded correctly they will be visible on this report. On the right (5) users can choose which PALs to prioritize within liquid and solid matrices. PALs can be moved up or down in priority by selecting the PAL and clicking the up or down arrows (6). On the lower right (7), the user can choose to change the Criteria Type terminology to Project Action Limit or Screening Criteria. Although PAL terminology will always be used for the eqapp setup interface, this selection will determine what terminology is used on reports. The user can also choose to have the system automatically update the project quantitation limit goals using the Update Project Quant Goals Rule. Selecting the Update Project Quant Goals by selected priority rule prioritizes according to the order limits appear in the priorities list (5). Selecting the Update Project Quant Goal to lowest applicable PAL rule prioritizes from lowest limit to highest limit, regardless of their order in the priorities list. Additionally, the user can choose to update project quantitation goals using the Update Project Quant Goals dropdown. The commonly used values of 1/3 or 1/10 of the PAL are available for selection. The project quantitation limits goals are listed on the Analyte Limits tab (see Section 3.1.9). Page 21 of 115

22 Figure 7 PAL Tab Copy QAPP The Copy QAPP tab displays a list of available analysis methods in the left hand column that can be copied into the project. These methods are automatically filled with default values and can be customized to fit the project. The methods may vary based on which source database and source project are selected in the list boxes. In the right hand column, the analysis methods that the user has already added to the project are displayed. The QSM Tests that appear in the project templates include the analytes and LCS/MS criteria that are provided in the QSM 5.0 or 5.1 documentation. Currently, only analysis methods included in QSM are available for selection. In the future, non-qsm methods will be vetted and approved by CX then added as options. At this time, if a non-qsm test is required, a similar test can be selected, and the method name can be changed to the correct name on the Methods tab. Subsequent tabs will need to be updated as well to reflect the correct parameters for the non-qsm method. All fields are populated based on the original method selected in the Copy QAPP tab, and do not update when the method or version is changed in the Analysis Method field. Choose the Source Project (1) and select the desired test. Next, use the right arrow (2) to add the selected test to the project. It may take a few seconds for the test to copy over to the project, but afterwards the new analysis method shows up in the list of tests for the project (3). Page 22 of 115

23 Tests can be removed by selecting the method in the right hand column and clicking the Delete button. Figure 8 Copy QAPP Tab Methods The Methods tab provides a grid view to modify the analysis level parameters for each analysis including Analysis and Leach Methods, List, List Name, Method Group, Technique, and Significant Figures (Sig Figs). The analysis method or version can be changed by clicking the text of the method code in the Analysis Methods column, and selecting from the dropdown. A leach method can also be specified if necessary. If multiple analyte lists are required, such as if a project needs a short list and a full list of analytes, the user can copy the method, change the list on the new version to list B, and edit the list names to specify long list or short list. Later, in the Analyte Limits tab, the user will be able to specify which analytes should be included on each list. The List Name is used to distinguish between similar tests with different analyte lists or QC requirements. The List Name can be edited by typing into the List Name field. Method Group, Sig Figs and Technique are pre-populated according to the original method selected in Page 23 of 115

24 the Copy QAPP tab, but can also be edited as necessary. NOTE: If an action has not be saved, red triangles will earmark the upper left hand corner of those fields to indicate that changes were made to the data that are not yet committed to the database. To commit the changes to the database, click the Save Changes button. Clicking the Cancel Changes button will revert any uncommitted changes back to the original values. If the Analysis Method is changed using the Analysis Method dropdown, all other fields may need to be edited accordingly. All fields are populated based on the original method selected in the Copy QAPP tab, and do not update when the method or version is changed in the Analysis Method field. If a test needs to be removed, select it with the checkbox on the left hand side and click the Delete button. Figure 9 Methods Tab NOTE: The top row of the grid contains filters. To filter the grid, enter the criteria in the filter text box at the top of the column. The columns can also be sorted by clicking the column name. There is also a Field to Replace tool at the top of this tab. The Field to Replace tool replaces the values for the column selected in the list box, for all selected rows in the grid. See Section on QC Elements for an example of using the replace tool Matrix The Matrix tab provides a grid view to modify Matrices and Units, and allows the user to specify container types, number of containers, preservation, and label group. In most cases, the default units, Page 24 of 115

25 container, and preservation for the QSM Setups come from the EPA methods, and will be populated based on the original analysis method selected in the Copy QAPP tab. NOTE: If the analysis method selected in the Copy QAPP tab was changed in the Methods tab, the values listed here may need to be updated accordingly. The label group number determines how samples are grouped, allowing the lab to identify which samples are intended for which matrix. Additionally, the label group determines which analyses are listed together on the same label on system generated bottle labels. The label group can be set to any number as long as samples in the same group have the same number. If multiple container or preservation options are needed for a method, the user can create a separate list for each option. See Section for information on how to create multiple lists for a method. If a matrix needs to be removed, select it with the checkbox on the left hand side and click the Delete button. To add a new matrix, select an existing test matrix to copy, and then use the Copy Selected Rows list box to select the new matrix. Figure 10 Matrix Tab Page 25 of 115

26 3.1.6 Sample Prep The Sample Prep tab provides a grid view to modify the preparation or extraction methods associated with each matrix. The default preparation methods for the QSM Setups are from the EPA methods in most cases, and will be populated based on the original analysis method selected in the Copy QAPP tab. Note: If the analysis method selected in the Copy QAPP tab was changed in the Methods tab, the values listed here may need to be updated accordingly. If a preparation method needs to be removed, select it with the checkbox on the left hand side and click the Delete button. To add a new preparation method, select a test matrix using the checkbox on the left hand side, and then use the Copy Selected Rows list box to select the preparation method to add. Figure 11 Sample Prep Tab Page 26 of 115

27 3.1.7 QC Elements The QC Elements tab provides a grid view to modify the QC elements and validation flags associated with each analysis method. A majority of the default flags for the QSM Setups are from National Functional Guidelines 2017, and will be populated based on the original analysis method selected in the Copy QAPP tab. Note: If the analysis method selected in the Copy QAPP tab was changed in the Methods tab, the values listed here may need to be updated accordingly. To add a QC Element, use the method dropdown (1) to select the method to add to, then click the Add QC Element to Method button. This will add a new blank QC element record for the specified method. To specify the QC element, click into the QC Element column in the blank record (2), and select the element from the dropdown. Likewise, enter the QC rule and flags by clicking into the appropriate column in the blank record and selecting from the dropdown. Multiple rows can be edited at once by selecting the appropriate rows and using the Field to Replace tool (3) at the top of the tab. For example, to change the Upper Control Flag for all Matrix Spike Duplicates, select each Matrix Spike Duplicate row by clicking into the checkbox to the left of that row. In the Field to Replace dropdown, select Upper Control Flag, and type the desired value into the New Value textbox. Clicking the Replace button will replace the former Upper Control Flag value with the newly specified value in all selected rows. If a QC Element needs to be removed, select it with the checkbox on the left hand side and click the Delete button. Page 27 of 115

28 Figure 12 QC Elements Tab PAL Associations The PAL Associations tab allows the Project Action Limits or Screening Criteria entered for the project in the PAL tab to be associated with the methods already selected for the project. With these associations, the system can update Project Quantitation Limits for each analyte according to the preferences indicated in the PALs tab. NOTE: The units for the Project Action Limit or Screening Criteria must match the units for the selected method in order to associate. If the user needs to apply separate PALs to different samples under the same method (for example Groundwater PALs and Surface Water PALs) they will need to create separate lists (a Groundwater list and a Surface Water list) under the Methods tab. They can then associate the appropriate list with the appropriate PAL. Page 28 of 115

29 Figure 13 PAL Associations Tab Page 29 of 115

30 3.1.9 Analyte Limits The Analyte Limits tab provides a grid view for modifying the analytes and associated reporting limits for each test matrix by selecting from the Analysis Method to Edit list box (1) in the upper left hand corner. The default analyte list for each Analysis Method/Matrix is determined by the QSM version selected in the Copy QAPP tab. Note: If the analysis method selected in the Copy QAPP tab was changed in the Methods tab, the analyte list displayed here may need to be updated accordingly. To add an analyte, select Add New Analyte(s) from the list box in the middle (2), and determine the number of rows to add in the next list box. Clicking the Add button will add the desired number of rows as new blank records. To specify the analyte, click into the analyte field on the desired row (3), and select the analyte from the dropdown. Upon clicking the Save Changes button, the Analyte Name field and CAS field will fill in automatically. The criteria for all other fields, including Analyte Type, must be selected manually. NOTE: When specifying an analyte for a new record, part or all of the analyte name can be typed into the Analyte field (3) to search the dropdown for that analyte. To add a new surrogate, choose Add New Surrogate(s) from the middle list box and follow the same process as adding a new analyte. The Surrogate Code field identifies which surrogates should be associated with which analytes. In most cases, the surrogate code should be set to 1 for all analytes and surrogates, to indicate that all analytes can be qualified by all surrogates. In cases where analytes are associated with their own surrogate (as may be the case with acids and bases), the analyte(s) and the corresponding surrogate should be given a unique surrogate code. If an analyte needs to be removed, select it with the checkbox on the left hand side and click the Delete button. The default reporting limits are zero for all analytes because these limits are laboratory specific. The limits may be completed by hand for each analyte by typing into the appropriate column in each analyte row (4). Reporting limit criteria can be edited for multiple analytes at once by selecting the appropriate analytes and using the Field to Replace tool (5) at the top of the tab. alternatively, the user may export the limits using the Export/Import Analyte Limits tool (6) in the upper right corner. Selecting Export allows the user to export all analytes in an Excel spreadsheet with columns for each limit. The user can edit the limits in Excel, then select Import and upload the edited file to update the limits within FUDSChem. NOTE: For successful reimport, do not add or delete records. Edit only the four analyte criteria limits. Do not modify method or analyte names or other fields. Page 30 of 115

31 Figure 14 Analyte Limits Tab Page 31 of 115

32 Holding Times The Holding Times tab provides a grid view for editing the holding times associated with each analyte per analysis method. First, select an Analysis Method to edit from the dropdown list (1). Specify the holding times for test, prep, and leach as well as the units for each analyte, by typing into the appropriate field in that analyte row (2). The default hold times are from the EPA methods in most cases. The rejection factor in the right most column is a factor used with the hold times to calculate the Gross Hold Time values. NOTE: National Functional Guidelines does not use Gross Hold times, so for NFG projects, the rejection factor is 1. In other projects, the Gross Hold times may be 200% of the hold time, therefore the rejection factor would be 2. If analytes were added in the Analyte Limits tab, the Hold Times and Rejection fields for the added analytes will be blank and must be populated manually. NOTE: The Field to Replace tool can be very helpful on this tab when adding or changing holding times for many analytes. Figure 15 Holding Times Tab Page 32 of 115

33 Analyte Criteria The Analyte Criteria tab provides a grid view for editing the QC Criteria associated with each analyte. The criteria for each QC element comes from QSM in most cases. The Analyte Group value is currently not used. First, select the desired Analysis Method/Matrix from the Analysis Method to Edit list box (1) in the upper left hand corner. Edit the QC criteria for each element as necessary, by typing into the appropriate field in that analyte row (2). QC criteria can be edited for multiple elements at once by selecting the appropriate element rows and using the Field to Replace tool (3) at the top of the tab. Alternatively, the user may export the criteria using the Export/Import Analyte Criteria tool (4) in the upper right corner. Selecting Export allows the user to export all analytes in an Excel spreadsheet with columns for the rejection points and control points. The user can edit these in Excel, then select Import and upload the edited file to update the criteria within FUDSChem. NOTE: For successful reimport, do not add or delete records. Edit only the control and rejection points. Do not modify method or analyte names or other fields. To add a QC element for a given analyte, select the analyte in the select analyte dropdown in the middle (5), then select the QC element to add in the next list box. Clicking the Add button will add a new record for the specified analyte QC element. If criteria need to be removed, select them with the checkbox on the left hand side and click the Delete button. Alternatively, the user may mark criteria Inactive using the checkbox on the far right (6). The system will treat inactive criteria as if they have been removed, but the user can easily uncheck the box to reactivate, instead of re-adding deleted criteria. NOTE: Analytes that are deleted and re-added will not be pre-populated with default values. Page 33 of 115

34 Figure 16 Analyte Criteria Tab Page 34 of 115

35 3.2 QAPP Reports There are several reports available that can be used to generate UFP-QAPP Worksheets based on the information entered into the eqapp Setup. The UFP-QAPP reports are located under REPORTS, UFP QAPP Worksheets on the menu bar. Figure 17 UFP QAPP Worksheets Page 35 of 115

36 3.2.1 Worksheet #12 Worksheet #12 provides Measurement Performance Criteria. Figure 18 Worksheet #12 Page 36 of 115

37 3.2.2 Worksheet #15 Worksheet #15 displays Action and Reporting limits. Figure 19 Worksheet #15 Page 37 of 115

38 3.2.3 Worksheet #18 Worksheet #18 displays Sampling Locations and Methods. Figure 20 Worksheet #18 NOTE: If a project does not have locations established, this report will not run. Information on how to establish locations is found in Section 4.0. Page 38 of 115

39 3.2.4 Worksheet #19 Worksheet #19 displays Sample Containers, Preservation, and Hold Times. Figure 21 Worksheet #19 Establish Locations To successfully enter data into FUDSChem, the user will need to populate the Location Definition and Site Location Cross Reference tables. These tables are the foundation for all successive data loaded into FUDSChem. A clearly defined location and an associated site ensure that data will join seamlessly to the correct geographic point. All data loaded into FUDSChem will add layers of definition to a given location, ensuring that reports over time will accurately display the trend characteristics of that location. FUDSChem supports loading of location data using either the manual loading interface that will create a compliant data file, or by bulk loading data that has been formatted for loading. Both mechanisms are described in this section. Locations can be loaded as a single point or as a polygon, used in cases such as incremental sampling. The instructions below detail the process for adding single point locations. The process is the same for loading locations as polygons, differing in location classification set to Decision Unit and a KML polygon file imported via the Select KML File to Import button within the LDI Editor interface. Page 39 of 115

40 NOTE: Historical data can be loaded and linked to locations by entering the locations in FUDSChem and providing a table containing field sample ids and corresponding locations to the district's Synectics point of contact. In the event that location information is not available at the beginning of a sampling event (as may be the case with surveyed location data) locations may be added with placeholder data, so that other data types that depend on entering the LDI file are not held up. Entering placeholder data is not ideal, and the user should be sure to go back and add in the real data as soon as it is available. If data is not available to fill in placeholders the contractor should discuss what to do with their FUDS point of contact. Recommended placeholders for dates are 1/1/1990. Recommended placeholders for dropdown fields are Unknown if the data was not recorded or Historical if the data is not currently available but may be recovered at a later date. Recommended placeholders for coordinates are 0, however an Estimated coordinate type is available and users are encouraged to estimate coordinates from GIS programs, figures, etc. rather than use placeholders. 4.1 Manual Loading 1) Using the TOOLS, Data Submission interface, select the desired Project Name, Event Name, and select Location Definition (LDI). Figure 22 TOOLS, Data - Submission Page 40 of 115

41 Figure 23 Selecting Location Data Type Page 41 of 115

42 2) Clicking on Create a File will display the window below; location information can be manually entered and loaded through this interface (see (1) in Figure 24). Once all fields are populated, click Save (2). If a user wishes to create more than one location with similar attributes, select the location in the Choose a Record to View pane at the bottom of the LDI Editor interface, select Copy (3) at the top of the interface to make a copy of that record, and make the appropriate edits to the new record. NOTE: The Loc. ID dropdown next to the Add, Copy and Delete buttons does not need to be edited by the user. Field names with an asterisk (*) appended to the end are required for successful upload into FUDSChem. For required fields that do not appear to apply, check the dropdown for an NA option. Dropdown lists can be expanded to show the next 10 items in the list by clicking on Items 1-10 out of # at the bottom of the dropdown list. Figure 24 Location Interface 3) Close the window, and check the box to the left of the filename, and click Screen to run the compliance checks and verify that all required fields have valid entries. If errors are present after screening, refer to Section 8.1 for guidance on troubleshooting. Once the file is error free, check the box to the left of the filename and click Certify (see Figure 26). Page 42 of 115

43 4) In order to make full use of FUDSChem, a Site Location Cross-Reference file must be created for each location. Using the TOOLS, Data Submission interface, select the desired Project Name, Event Name, and select Site Location X-Reference (SLX). 5) Click on Create a File. Enter the information using the dropdown menus. Once all fields are populated click Save. If a user wishes to create more than one record with similar attributes, select the location in the Choose a Record to View pane at the bottom of the SLX Editor interface, select Copy at the top of the interface to make a copy of that record, and make the appropriate edits to the new record. 6) Close the window, and check the box to the left of the filename, and click Screen to run the compliance checks. If errors are present after screening, refer to Section 8.1 for guidance on troubleshooting. Once the file is error free, check the box to the left of the filename and click Certify. Figure 25 Location Site X-Reference Interface NOTE: The Location Definition Information file must be approved before the Locations will be selectable under the Location ID dropdown. For details on approving data, see Section 9.0. If the Event LOCIDs Only box is checked, next to Location ID, the user may not be able to select their desired location in the dropdown menu. Uncheck the box to see all approved locations. In the case of FUDSChem, the user should select the FUDS property as the Site for the Site Identifier dropdown. Page 43 of 115

44 4.2 Bulk Loading 1) To create a flat file to load data in bulk refer to Section ) Once the file is ready, using the TOOLS, Data Submission interface, select the desired Project Name, Event Name, and select the desired data type, such as Location Definition (LDI), Location Site X-Ref (SLX), or the appropriate data type from the Data Type dropdown. 3) Select Upload File, select the type of file from the File Type dropdown menu, click Upload, and select the desired data file. Once the file is uploaded, check the box to the left of the filename, and click Screen (1) to initiate the error checks. If errors are present, refer to Section 8.1 for guidance on troubleshooting. Note that any changes will need to be made to the file outside of FUDSChem, then the file will need to be reuploaded clicking edit within the interface will not save any changes, as the original file will not be altered Once the file is error free, check the box to the left of the filename and click Certify (2). Figure 26 Certify LDI File NOTE: To access the specification for Location data necessary to create a flat file, navigate to REPORTS, ADR and Submission Reports, Electronic Data Specification, and select the appropriate values from the dropdown menus. More information can be found in Section 8.2. Page 44 of 115

45 Sampling Event Planning FUDSChem contains an optional integrated event planning module to aid in the tracking of sampling events from collection through validation. These tools allow users to plan locations for non-chemistry data types, assign field sample IDs, and track samples based on planned or potential SDGs. Use of event planning ensures accurate joining of field and lab data and allows for the use of quality control summary and completeness reports. Using these FUDSChem tools allows the user to frontload the data management effort to conserve time and resources spent on tracking as well as creating final reports. The more tools used to manage data in FUDSChem, the more complete and accurate the final output will be. 1) Select Data Event Planning from the TOOLS dropdown on the FUDSChem dashboard. Figure 27 Select Event Planning 2) To create an event select the Create/Track Events tab. Select Copy and update the event information (Event Name, Start Date, etc.) and click Save. Synectics will set up the first event whenever a new project is added to FUDSChem. NOTE: Check that the Event Name says Copy of to confirm the event was in fact copied and you are not just changing the information of an existing event. Page 45 of 115

46 3) Select the Main tab, select appropriate event from Event dropdown menu (center column); highlight all locations desired for sampling in left column, click right arrow (1) to move locations to selected event. Select the appropriate type of data from the Data Type dropdown menu (right column); highlight locations desired for that data type in center column, click right arrow (2) to move locations to the selected data type. Most users will select the Data Type Laboratory (SEDD 5.2) at a minimum. NOTE: On most PCs holding down the SHIFT or CTRL key allows the user to select multiple lines at once. If new locations are installed or the location is established but not entered in FUDSChem you will create a new location as outlined in Section 4.0. Figure 28 Event Planning Main Tab Page 46 of 115

47 4) Select Assign Method(s) tab, highlight location(s) desired for method or method group assignment, check method(s) checkbox, select Add New Method(s). The methods available for selection are those developed in the electronic Quality Assurance Project Plan. If desired methods are missing from this section, there are two options for adding them. If missing methods are listed in the UFP-QAPP, please contact the contractor project chemist and request that the methods be updated. If missing methods are not listed in the UFP-QAPP, the Corps chemist over the project will need to give written approval on the change before methods can be updated. Figure 29 Event Planning Assigned Methods Tab Page 47 of 115

48 5) Select Assign Field Samples tab, select desired sampling event from Event dropdown menu, and click Add/Edit Samples. Using this interface, the user can assign field sample IDs, matrices, depths, sample types, sampling methods, sampling organizations, labs, and sampling statuses. 6) The user may populate the Field Sample ID by hand, or use the Replace Field Sample ID option at the very bottom of the window. The user can use the Columns dropdown to choose a column to include in the sample ID (for example choosing Location will add the location name to the field sample ID) and use the right arrow to add that column to the Replace Field Sample ID box. Additional text can be appended and the system can be set to auto-increment numbers at the end of sample IDs. Figure 30 Event Planning Assign Field Samples Tab 7) The dropdown menus at the top of this interface contain valid values in alphabetical order that allow the user to bulk populate the associated fields for a group of sample records. To bulk populate, select the desired locations (1), click the checkbox to the left of the sample record (2), and click the plus sign (3) to the right of each valid value dropdown. 8) Alternatively, if the user already knows the valid value that they want to enter, they can use the Column to Replace option in the lower left. In the dropdown, choose which column to replace, then enter the text into the Replace With box and click Replace to add that text the desired column for all selected samples. 9) Scroll to the right to check which methods should apply to each sample, or use the Check All Methods button (4) to check all available methods for every sample. NOTE: Valid values are maintained by the FUDSChem Operations and Maintenance contractor. Requests for additions should be sent via to fuds.support@synectics.net. Page 48 of 115

49 Sample number will automatically be set to 1 for all samples. If there are two samples from the same location with the same sample type on the same day (for example 2 field duplicates from the same parent or two Trip Blanks) the second sample should be changed to sample number 2. However, it is rare that this will occur. 10) To add Field Duplicates or MS/MSDs, select the parent sample and click Copy Rows (5). On the new row, change the Field Sample ID if applicable. Change the Sample Type to reflect whether the sample is a Field Duplicate, MS or MSD. If applicable, change the methods required. 11) To add Field QCs, a generic FIELDQC location will need to be added. It can be selected and the information can be filled out to include the Field QC in Event Planning. Please note however, that at this point the Field QC is not associated with samples yet and will not be used to automatically qualify samples unless a lot number is assigned in the Field Sampling tool (see note at the end of Section 6.0). 12) If samples will be sent to multiple labs for different analyses, select the appropriate samples and click Copy Rows (5). In the new Rows change the Lab to the second laboratory. Change the methods to reflect which laboratory will be performing which analysis. 13) Once all information is correctly entered, click Save Changes (6) and close the interface. Entering data into this tool will pre-populate electronic chains of custody that can be generated for the event and will ensure seamless joining of field and laboratory data. Figure 31 Assign Field Samples Interface Page 49 of 115

50 14) The Field Tracking tab is used to populate event specific tracking information such as Sampling Frequency, Review Type, Validation Turnaround Time, and Laboratory Turnaround Time. Select the tab and click Add/Edit Field Tracking Info. Highlight the desired locations in the Location(s) box (1) in the upper left to add to the grid. Select locations using the checkboxes to the left of each row and add Frequency, Review Type, or ERPIMS Status via the dropdown menus (2). Click the + button next to each dropdown menu to add the selected attribute to the selected samples. Other data can be bulk populated using the Column to Replace tool (3). To use this tool, select all applicable sample rows, then choose a column to replace in the Column to Replace dropdown. Type the desired value into the Replace with textbox, then click the Replace button to add the value to the selected rows. Once data is entered, click Save Changes and close the interface. 15) Once a laboratory Sample Receipt Confirmation has been received, the user can populate the SDG and lab receipt date as well. This information is viewable using the event tracking reports (see Section 7.0). NOTE: This interface is used by multiple agencies. For FUDS projects, ERPIMS Status should always be set to Not Required. Dates must be entered month first, then day, then year, with dashes or slashes in between. The current year is added automatically if a year is not specified. Figure 32 Field Tracking Interface 5.1 System Generated Chains of Custody and Bottle Labels FUDSChem contains a report to create system-generated chains of custody and bottle labels that can be sent out with field team during sampling. Go to TOOLS, Data Submission, and choose Project Name, Event Name, and a data type of Field Sampling from the dropdown, and click Create a File. Select all locations that have been selected for sampling and move them from the Locations column over to the right hand column using the right arrow. Select the sampling Log Date. Click Save. Page 50 of 115

51 NOTE: Locations will only show up if they have been moved to the event column in the Event Planning Tool (Section 5.0). If the Event Locations Only box is unchecked all locations for the project will appear. 1) Move to the Add Field Data tab. The information entered into Event Planning will automatically populate. Select all rows and click Replace. Once in the replace window select COC ID from the Column to Replace dropdown. Enter the COC ID and Replace in Selected Rows. Save and then Submit File. Note that Submitting the file does not certify it the file will still be editable. Do not certify, more information will be added to the file after sampling has occurred and completed chains of custody have been returned. NOTE: If a file is closed without clicking Submit it will not be selectable for editing or screening in the grid. However, it can be recovered by clicking Edit Files (next to Create a File) and selecting the latest file. 2) To create system generated chains of custody go to REPORTS, Environmental Data, Chain of Custody Report. Select Project, Event, Chain of Custody, then select View Report. There is the option to save this chain of custody in a few different formats including PDF and Excel. Information on points of contact and ship to address can be entered into FUDSChem by a Synectics user and will automatically display at the top of the Chain of Custody. 3) To create system generated bottle labels go to REPORTS, Environmental Data, Bottle Labels (Preferred Size). Select Project, Event, and Chain of Custody then select View Report. There is the option to save the bottle labels in a few different formats including PDF and Excel. 4) The chains of custody and bottle labels can be shared by using the FUDSChem Share Files tool. To use the tool go to QUICK LINKS, Share Files. Click Upload; choose the desired file, title the file with a clear and relevant name. There is an option that allows the uploader to choose Users to Notify. The chosen recipient(s) will receive a system-automated when the file is ready for them to download. NOTE: "Field Sample ID" must be entered before COC can be generated. Page 51 of 115

52 Load Field Data In order to take advantage of the field tracking tools and reports available in FUDSChem, field data must be entered into FUDSChem throughout the course of the sampling event. The information contained in the field file will update live tracking reports, ensure completeness of laboratory deliverables, and support the Automated Data Review process. 1) To load chain of custody data, navigate to the TOOLS, Data Submission interface, select the appropriate Project Name and Event Name, and select Field Sampling (ChemField) from the Data Type dropdown. Figure 33 Data Submission ChemField Dropdown Page 52 of 115

53 2) Clicking Create a File will open the interface seen below. Highlight the locations in the left column (1) that are included on the chain of custody, click the right arrow to bring the locations to the right column, enter the sampling date (2), and then click Save (3). NOTE: Locations will only show up if they have been moved to the event column in the Event Planning Tool (Section 5.0). If the Event Locations Only box is unchecked all locations for the project will appear. Figure 34 ChemField Interface - Locations Page 53 of 115

54 3) Select the Add Field Data tab at the top of the window to navigate to the electronic chain of custody. This interface will be prepopulated with the information previously entered in event planning. Enter sampling times (1); then check the box next to each sample, click Replace (2) at the top of the window, and populate fields that are consistent between samples (Lab Shipped Date, COC ID, Sampler Initials, etc.) If the user did not enter information into event planning, they will also have to fill in the Field Sample ID, Matrix, Sample Type, Sampling Company, Sampling Method, and Lab, as well as check the desired methods. Valid values for these fields can be found by going to Reports, ADR and Submission Reports, Valid Value Lists and selecting Field Sampling as the data type. NOTE: The Add Field Data tab is very wide and may exceed the limits of some monitors. The user may select the Hide Columns button to temporarily hide columns that they are not working on in order to make the interface less wide. 4) To add Field Duplicates or MS/MSDs, select the parent sample and click Copy Rows (3). On the copy, change the Field Sample ID if applicable. Change the Sample Type to reflect whether the sample is Field Duplicate, MS or MSD. If applicable, change the methods required. 5) If samples will be sent to different labs for different analyses, select the appropriate samples and click Copy Rows (3). In the new rows change the Lab to the second laboratory. Change the methods to reflect which laboratory will be performing which analysis. Figure 35 ChemField Interface Add Field Data Page 54 of 115

55 1) To add field QC (Trip Blanks, Equipment Blanks, and Ambient Blanks), check the box next to each sample associated with the blank. Click Add Field QC at the top of the interface, enter the sample date and time (1), sample type (2), and sample name (3). Select the associated method(s) associated with the blank (4) by highlighting them (note that on most PCs the user can highlight multiple selections by holding down the CTRL key while clicking), then select Insert Field QC Record (5). When finished click Save and then Submit File. Note that Submitting the file does not certify it the file will still be editable. Figure 36 ChemField Interface Add Field QC Page 55 of 115

56 NOTE: The lot number associated with the sample type (Trip Blank Lot (TBLOT), Equipment Blank Lot (EBLOT), and Ambient Blank Lot (ABLOT)) will be populated for the samples associated with that blank, and Automated Data Review will qualify on this basis. If the user added Field QCs previously in Event Planning, they can manually enter the TBLOT, EBLOT, or ABLOT as applicable to associate the Field QC with the samples. Figure 37 ChemField Interface Lot Number FUDSChem Event Tracking Reports Selecting Event Tracking Reports from the REPORTS dropdown menu will provide access to the following reports: Event Status: All Data Types, Event Status: Chemistry and Event Status: Chemistry Detail. Selecting one of these reports will prompt the user to choose their project, event and other information in a dropdown menu, such as the one pictured below. These reports are only available if the user has completed the Event Planning steps for the project. These reports track a sampling event from the event planning stage through the validation and approval stages. Using FUDSChem s event tracking reports will aid in assessing project completeness, and ensure continuity between the field team, lab personnel, project managers, and project chemists. The following reports are generated by live queries, and as such require no additional updates beyond event planning and data loading. These reports can be customized based on district specific needs. Keep in mind that by clicking the save icon located on the report interface, the report can be exported in XML, CSV, PDF, MHTML, Excel, TIFF, or Word format. NOTE: The screen, certify, and approval tasks are performed by different parties. For example, the laboratory might screen and certify the chemical analytical data, but the USACE chemist is the one to approve the data. Therefore the color coding that indicates which step in the process the data is at can also indicate which party is currently working on the data. Page 56 of 115

57 Figure 38 Reports Event Tracking Reports Dropdown Options Figure 39 Event Status All Data Types Report (Dropdown Menu) Page 57 of 115

58 7.1 Event Status: All Data Types The Event Status: All Data Types report displays all locations associated with a given event, grouped by site, and their requested data types. As event planning is populated, an X will appear to the right of that location in the column for the requested data type. For example Figure 40 indicates that location MW- 477S in Camp Richards was scheduled to be sampled for chemical parameters (Chem) and Groundwater parameters (GWD). Once data has been loaded for each location and data type, the rectangular area around each X turns orange, indicating that the data type has been successfully loaded into the system for the location. Upon approval of the data, the rectangle will turn green. Other data types visible on this report include Lithologic Descriptions (LTD), Well Construction Intervals (WCI) and Environmental Measurement Information (EMI), among others. Figure 40 Event Status All Data Types Report Page 58 of 115

59 Figure 41 Event Status All Data Types Report (Key) Page 59 of 115

60 7.2 Event Status: Chemistry The Event Status: Chemistry report tracks a location s status from the analysis planning stage through the validation and approval stages. This report organizes locations by site and requested analyses; it reflects the status of each location based on the color coded legend. NOTE: Once the cell for a given sample turns green, the Chemistry Results report can be run for that sample. All preliminary Chemistry reports are also available after a SEDD is certified and the cell turns yellow. (See Section 10.0 for details on these reports). Figure 42 Event Status Chemistry Report Page 60 of 115

61 7.3 Event Status: Chemistry Detail The Event Status: Chemistry Detail report is a comprehensive event tracking report that reflects the statuses of all samples requested at a location. Differing from the previous report, the Chemistry Detail provides an expanded view of detailed sample information including but not limited to: Field Sample IDs, Beginning and Ending Depths, Matrices, Sample Types, Sampling Methods, Chain of Custody IDs, Laboratory Shipped and Receipt Dates, and Sampling Statuses. This report also displays well counts for each site, indicating the number of wells requested for a given analysis, the number of requested wells not sampled for that analysis, and the total number of wells requested for an analysis among all sites in an event. The sampling status field can be manipulated through the Event Planning interface, and changed to reflect the status of any given field sample; statuses include but are not limited to: Scheduled, Sampled, Dry Well, and No Access. NOTE: Once all cells for a given site turn green, or are otherwise noted as not sampled under the sampling status field, the Chemistry Results, Approved report is ready to run for the entire site. (See Section 10.0 for details on this report Page 61 of 115

62 Figure 43 Event Status Chemistry Detail

63 Screen Electronic Data Deliverables (EDDs) Using FUDSChem All data (Chemistry, Field, Location, Site, Well Construction, Lithology, etc.) are screened through the Data Submission interface. FUDSChem allows users to create non-chemistry files manually through built-in interfaces, or upload external files that conform to the FUDSChem electronic data specifications. All files follow the same process for screening, but in this example we will focus on screening EDDs. 1) To screen a file using FUDSChem, navigate to the TOOLS menu on the project dashboard, and scroll down to select Data Submission. Figure 44 Tools Dropdown Page 63 of 115

64 2) In the Data Submission interface, select the desired Project Name, Event Name, and Data Type, in this case Laboratory (SEDD 5.2)(SEDD 5.2 2a 5), from the dropdown menus shown in Figure 45. Figure 45 Data Submission SEDD 3) Click Upload File, select the file type from the Type of File dropdown menu, click Upload, and then select the desired file. NOTE: For all historical data, or any data that has been previously validated (i.e. reviewed SEDD files), select Historical Data prior to uploading. This will ensure that previously reviewed data will not cycle through Automated Data Review. In Workflows 2A and 2B, the user will not wish to process with ADR as the user will be loading validated SEDD files. It is necessary to indicate this on upload, because a different set of screening checks will apply. This set of checks only verifies the validity of the file structure and does not compare to the eqapp or previously entered field data. See Figure 46. Files that will be validated using the FUDSChem tools should be sure to check the Process with ADR box. Users with questions on SEDD files are advised to go to HELP, SEDD Clarifications. Page 64 of 115

65 Figure 46 SEDD Upload Files Pop-Up Page 65 of 115

66 8.1 Run Screening Checks All data types are screened against format, content and logical requirements of the particular data type. Here we will focus on screening SEDD files in particular. There are two classes of checks, Errors and Warnings. If the error count is not zero, the user cannot certify that they have completed the screening process. Warnings are items that may indicate data anomalies, but will not prevent the user from Certifying that they have completed the screening process. 1) Select the check box to the left of the Filename, and then click Screen. 2) If errors are found during the screening process, the number of errors will be displayed in the Error column. Figure 47 SEDD Errors Clicking on the number of errors will open up an error report. All errors identified during the screening process must be corrected before the file (data) can be certified. It is recommended that the lab make any changes that need to be made directly to the SEDD file. Synectics does not edit SEDD files. To see the SEDD file from the Data Submission interface, select the Export button to the left of the Filename of the desired SEDD file. The SEDD will export and can be opened and used to compare to the error report accessed by clicking on the number of errors in the Error column. NOTE: This report outlines all errors preventing the EDD from screening successfully. These errors are divided into three classes: Valid Value, Logical and Submission. All valid value and some logical checks must pass before the submission checks can begin. Therefore, it is possible to resolve all of the errors in the first pass, then receive additional errors when the submission checks process. Common errors and their solutions can be found by going to HELP, SEDD Troubleshooting. Page 66 of 115

67 8.1.1 Valid Value Errors The initial screening process will reveal all valid value errors that exist in the EDD. This will identify all values (i.e. AnalyteName, ClientMethodID, etc.) that do not align with those indicated in the SEDD Valid Value Specification. Once all valid value errors have been resolved, the error report will display any submission errors that exist in the EDD. NOTE: The sources of the valid values begin with the SEDD valid values specified by the EPA. For fields that are not associated with SEDD valid values, such as ClientMethodID and AnalyteName, and all non-sedd data types, other published agency valid values lists are used. If no valid value is available, then custom values can be added. In order to view the valid values for FUDSChem go to REPORTS, ADR and Submission Reports, Valid Value Lists. Once in the valid value report select the desired Data Table and Data Type from the respective dropdown menus. This report will provide the valid value and description for each data type within each data table, including but not limited to Location Definition, SEDD 5.2, Groundwater Level, and Environmental Measurement. NOTE: To request a valid value, please send a request to fuds.support@synectics.net. The error report shown below indicates a valid value error based on an invalid QC Type. The system identifies an invalid value based on this data element and notes a Valid Value Error (VVL) as the query type. In this case, a QC Type of Client_Sample was entered into the field. To resolve this error, replace the value Client_Sample with the correct QC Type found in the Valid Values List, then follow step 1 of Section 8.1 to rescreen the file. Page 67 of 115

68 Figure 48 SEDD Error Report VVL Errors Page 68 of 115

69 8.1.2 Submission Errors Submission errors are divided into two classes: logical and project specific. The system performs a series of logical checks on the file assuring that all data elements are logically populated. For example, this will ensure that the date/time of analysis is after the date/time of collection. Project specific errors include missing analytes from those included in the electronic QAPP and disagreement with previously loaded event planning and field collection data. The error report below indicates an example of a logical submission error based on existing fields. Based on the existing Data Element combinations in the database, the system identifies these records as existing and throws a logical error (LE) as the query type. To resolve this error, remove the records in the EDD that were previously screened into FUDSChem. A full list of all possible errors at the time of this publication is found in Appendix A Checks Performed on SEDD Files. Figure 49 SEDD Error Report Submission Errors Page 69 of 115

70 Complete File Screening Process 1) Navigate to the Data Submission interface, and ensure that number of errors is 0. 2) Select the checkbox to the left of the desired file, and click Screen. Once the status of the file is Ready to Certify, select the checkbox once more and click Certify. Figure 50 Screen and Certify Page 70 of 115

71 Figure 51 Zero Errors NOTE: Upon completion of SEDD file submission, follow Section 12.1 to upload the PDF laboratory report to the document library and notify the appropriate USACE chemist. Page 71 of 115

72 8.2 Loading Flat Files This section provides access to specifications for all data types accepted by FUDSChem. These specifications include a Laboratory format for non-sedd historical chemistry data, location data, environmental data, and geologic data. Bulk loading of compliant files is done in accordance with the procedures described in Section 4.2. Compliant files can be loaded in fixed width or CSV formats using the FUDSChem Electronic Data Specifications. The electronic data specifications are stored within FUDSChem and instructions on accessing them are detailed below. They are also available at the end of this document in Appendix C Electronic Data Specifications. 1) Navigate to the REPORTS dropdown menu, select ADR and Submission Reports, and then click Electronic Data Specification. Figure 52 Reports Dropdown, Electronic Data Specification 2) Select the desired data type from The Electronic Data Type Dropdown menu, and click View Report. This report displays all fields associated with a given data type. It also indicates if the field is required, the field width, and a short description of the field. Page 72 of 115

73 Figure 53 Electronic Data Specification 3) Based on the electronic data specification, populate the file with all required fields, then follow the screen, troubleshoot, and certify process outlined in the Section ) If using a TXT file, insert the data separated by spaces in the order listed. Make sure data is fully contained within the Start Position and End Position. If the character count for the data is not long enough to fill the entire column width, add spaces at the end. When VVL is marked True, be sure to look up the valid values that can be used for that data type. Put each data point on a new line. 5) If using a CSV file, use the FieldNames as the column headers in Excel. Use the column width as the allowed character count for each column. If the character count is not reached, there is no need to add spaces at the end, as was the case for TXT files. When VVL is marked True, be sure to look up the valid values that can be used for that data type. Put each data point on a new line. NOTE: Since CSV files use commas to separate each column, commas cannot be entered into the text of any column in a CSV file. Page 73 of 115

74 Data Review / Approval All data loaded into FUDSChem should be reviewed by different user than the one who submitted it to ensure data quality. Submission and review users should be pre-determined by the contractor. Permissions will be assigned accordingly to encourage quality control of all data submitted to FUDSChem. Permissioned review users are required to approve data before it can be released to FUDSChem for final reporting and exporting. Laboratory data is approved by the USACE chemist after the data validator has finalized the validation qualifiers. Once the data validator has finalized the qualifiers, the USACE project chemist will review and approve the validation report and the associated chemistry data. Data is processed with ADR on an SDG by SDG basis. However, there are provisions to evaluate all SDGs in the event for QC elements such as equipment blanks that may apply to multiple SDGs. This is necessary because the user is not required to load data in a particular order, and as such, there is no way to tell if an SDG will be associated with a blank in another SDG that has not yet been loaded. These reports are discussed in Section Review Chemistry Data 1) To review chemistry data, navigate to REPORTS, select Environmental Data, then Chemistry Results by SDG, Preliminary. Figure 54 Reports Dropdown, Results by SDG, Preliminary Page 74 of 115

75 2) Using the dropdown menus choose the appropriate Site and Event, and the desired SDG(s), result type, locations, methods, and contaminants of concern. Click View Report. 3) The report will show chemistry data, along with red text explaining that this is unapproved data and may change when validation is complete. 4) From here, the user can export the data as PDF or Excel for review. Figure 55 Export to PDF NOTE: For information pertaining to the review of PDF laboratory reports, refer to Section Data Validation FUDSChem contains all tools necessary to review, qualify, and assess the quality of analytical data, as well as the tools to generate a presentation quality data review report that displays these findings. As soon as a laboratory certifies a compliant SEDD 5.2 2a file into FUDSChem, Automated Data Review (ADR) is triggered and performs a data quality assessment based on the electronic QAPP. ADR checks the data for outliers and applies qualifiers based on the parameters set in the eqapp information. Findings of this assessment can be accessed in a series of reports identified in Section below. Generally for Data Validation, the validator will keep the Chemistry Results by SDG, Preliminary Report (see Section 9.0) open in one window and use it, along with the lab report, to fill out the Data Review Checklist (see Section 9.1.2). If the validator finds a data point in the Chemistry Results by SDG, Preliminary Report that needs to be qualified, or that needs the qualifier removed or edited, the validator will update the qualifiers in the Sample Qualification tool (see Section 9.1.3). Page 75 of 115

76 9.1.2 Data Review Checklist The Data Review Checklist tool allows validators to enter SDG specific information that will be displayed on the cover page of a final data validation report. Additionally, this tool contains data review questions specific to the analytical method and data review level that can be answered by a validator to satisfy predetermined levels of manual review. A default checklist is provided by the Corps, but additional questions may be added by a district chemist with authority to change for all projects. Department of Defense data review guidelines are being implemented and information about that implementation will be provided in the 2019 update to the User Guide. 1) To access this tool, navigate to TOOLS, and select Data Review Checklist. 2) Choose an SDG (1) on the left. 3) Choose the Data Review QC Level (2) in the SDG Details section. All other information in this section is optional. Click Save SDG Details (3). 4) Once an SDG and Data Review QC Level are chosen and saved, select a Test Method (4). General Comments (5) for the test method can be entered to the right of this dropdown. The Additional Comments for Test Method section has its own save button, so be sure to click Save Comments (6). Selecting a test method will also populate a list of questions at the bottom of the interface. Each method will have its own list of questions. 5) Read the questions and choose Yes, No or N/A. Additional comments can be added if applicable. A small red arrow will appear over any information that has not yet been saved. When all information is filled out, click Save Changes (7). NOTE: The data review checklist includes a section to list the personnel involved in the review. The section for Second Reviewer should be filled in with NA if there is no second reviewer on the project. Page 76 of 115

77 Figure 56 Data Review Checklist NOTE: It can be useful to have the Validator Detail report (REPORTS, select ADR and Submission Reports, then Validator Detail Report) open while filling out the Data Review checklist Sample Qualification The sample qualification tool is used to modify, add, or remove qualifiers, as well as approve data into production. 1) To modify, add, or remove validation qualifiers, navigate to TOOLS, and select Data Sample Qualification. 2) Choose the applicable Project, SDG, Test Method and Preparation Method. The user may manually edit the samples in the grid, but it is recommended to use the buttons listed below instead. 3) The Apply Qualifiers by Batch button can be used to add qualifiers to an entire batch at once. 4) The Apply Contamination Qualifiers button can be used to apply qualifiers for blank contamination. Page 77 of 115

78 5) The Apply Qualifiers with Outliers button can be used to manually add an outlier to the data. 6) The Archive Records by Batch button allows the user to archive unwanted samples so they do not show up on reports. 7) Upon completion of validation, the qualifiers are re-finalized by selecting Finalize SDG Qualifiers. Figure 57 Sample Qualification Page 78 of 115

79 9.1.4 Validation Reports FUDSChem contains data validation reports that are used to support a data validator throughout the review process. These reports reflect the findings of the ADR process, and reflect qualification changes made by the data validator. 1) To view qualifiers applied during the initial Automated Data Review, navigate to REPORTS, ADR and Submission Reports, and select Validator Detail Report. This report contains laboratory batch information by SDG, field batch information, outliers, qualified results, detected results, rejected results, reporting anomalies, and data review questions. Figure 58 Validator Detail Report 2) To generate a final validation report, navigate to REPORTS, ADR and Submission Reports, and select ADR Report. 3) From the Status dropdown, the user can set the desired status of the SDG, which changes which SDGs are available to select in the next dropdown. Choosing Certified (Not Approved) will bring up SDGs that have not yet been validated or are in the process of validation. Choosing Finalized will bring up SDGs that have been validated and for which the data validator has finalized the qualifiers. Choosing Approved will bring up SDGs for which data has been validated and approved by the Corps. 4) Select the desired SDG. Set the True/False options. Marking True for 2 nd Signature on Report will insert a line for a second reviewer to sign the report. This should be used in the event that two people are doing validation. Selecting True for Display Modified Qualifications Table will insert an additional table into the report which shows which qualifiers were modified by hand. Selecting True for Display Trace Values Table inserts an additional table into the report with displays results marked as trace. Page 79 of 115

80 5) This report contains information previously entered on the Data Review Checklist, a summary of all quality control elements found in the laboratory file, validator comments entered via the Data Review Checklist, outliers, qualified results, rejected results, and data review questions. It also contains information on which qualifiers were entered by hand and which were automatically applied by the system s ADR. This report is an accepted final data validation deliverable for many districts, and is designed such that no additional formatting is needed prior to delivery. To determine if this validation report is accepted in a particular district, the project team can reach out to the designated USACE point of contact. Signatures of data reviewers can be encrypted into FUDSChem and inserted into the final report if desired. NOTE: Upon completion of validation, follow Section 12.1 to upload the final data validation report to the document library and notify the appropriate USACE chemist Review Validation Reports (USACE Role) 1) To begin the approval process, the USACE chemist will navigate to the TOOLS dropdown menu and select Library File Submission. Figure 59 Library File Submission Dropdown Page 80 of 115

81 2) Select the Pending Approval tab. Figure 60 Library Pending Approval Tab Page 81 of 115

82 3) To view a validation report, click on the file type icon or click on the file name. Figure 61 View Library File Page 82 of 115

83 4) To approve a validation report, select the notepad icon to the left of the report desired for approval. Select the Notify on Approval dropdown menu, and select the users you wish to notify upon approval of the report. Once the appropriate users have been chosen, select Save & Approve to complete the approval process (names are redacted in Figure 62). An automated will be sent to the selected users informing them that the report is complete and available for viewing in the document library. Figure 62 Library File Approval Page 83 of 115

84 9.2 Review Other Data Types The Data Approval tool is used to review or approve all data types. It can be used to review or approve chemistry data if it was not approved during the sample qualification process outlined in Section 9.1.3, as may be the case with historical chemistry data or validated SEDD files, such as may be found in workflows 2A and 2B. 1) Navigate to the TOOLS dropdown menu and select Data Approval. Figure 63 Data Approval Dropdown Page 84 of 115

85 2) Select the desired project in the Project dropdown menu and select the Pending Approval tab. Figure 64 Data Approval 3) To review the data choose a file type and select the number of records. 4) If a correction is needed, the preferable approach is to select the green back arrow and notify the data submission user that there are errors to be corrected. Once corrected repeat steps 1 through 3. 5) Once everything is correct, click the notepad icon to approve the data. Data Tables / Reporting Selecting Environmental Data from the REPORTS dropdown menu will provide access to several chemistry and non-chemistry reports suitable for inclusion into final deliverables. These reports allow project chemists, project managers, and permissioned users to view preliminary chemistry results prior to the completion of validation, and final chemistry results after the data has been approved by the project chemist. Keep in mind that by clicking the save icon located on the report interface, the report can be exported in XML, CSV, PDF, MHTML, Excel, TIFF, or Word format. Examples of reports are listed below, and are organized by data type. NOTE: Reports are updated periodically and those shown below were current as of the time of the publication of this document. Changes will reflect in each version of the user guide. Page 85 of 115

86 FUDSChem Report Examples: Figure 65 Environmental Data Reports Dropdown Chemistry Results Approved By Location Type By SDG, Preliminary MAROS Export Report Validated Data Export, Approved Validated Data Export, Unapproved With Regulatory Limits, Finalized Non-Approved Groundwater Water Levels Water Levels Chart Environmental Measurement Field Parameters Field Parameters Chart Well and Borehole Coordinates and Elevation Lithologic Description Lithologic Description Review Well Construction Interval Well Construction Interval Review Page 86 of 115

87 10.1 Chemistry Results by Sample Delivery Group (SDG) Preliminary Upon successful submission of a SEDD 5.2 file by a contract laboratory, an Automated Data Review (ADR) process is automatically initiated. FUDSChem s ADR compares the loaded EDD to the electronic QAPP, summarizes outliers, and applies preliminary validation qualifiers to associated results. Upon completion of the ADR process, the Chemistry Results by SDG Preliminary report is ready to run. This report provides users the ability to display preliminary chemistry results organized by site, event, SDG, result type (Detect or All Results), location(s), method group, contaminants of concern, and analyte display (Vertical or Horizontal). Also visible on this report are Field Sample IDs, Sample Beginning and Ending Depths, and Sampling Dates. All detects are displayed in bold font, and associated qualifier flags are visible as well. Please keep in mind that these results are preliminary, and are subject to change prior to the completion of data validation. Figure 66 Chemistry Results by SDG Preliminary Report Figure 67 Chemistry Results by SDG Preliminary Report (Qualifier Definitions) Page 87 of 115

88 10.2 Chemistry Results Approved Upon approval of the data by a USACE chemist, the data is released to FUDSChem for access by the users via the Chemistry Results, Approved report. This report provides project chemists the ability to display final chemistry results for a specific site, organized by event, analyte, and result type. Once all data in a given site or SDG has been approved, that data is released to FUDSChem and this report can be generated. Keep in mind that by clicking on the save icon, this report can be exported into several different formats including PDF. NOTE: Preliminary reports are available for data that has been certified but not yet approved. These reports allow the contractor's use of the data prior to USACE approval. Figure 68 Chemistry Results, Approved Report NOTE: The Chemistry Results, Approved Report can only be generated once the data for that SDG has been approved by a project chemist. To verify approval, navigate to the Event Status: Chemistry Detail report, and verify that the cells for the desired samples and/or sites have turned green. A query tool can be provided to users who are skilled in use of the SQL language. Users may query to locate data limited by specific criteria (for example all samples taken within a specific date range). In order to access data through the use of the query tool, which allows the user to interact with their data using SQL language, and to learn more about creating successful queries, please contact Synectics at fuds.support@synectics.net. Page 88 of 115

89 Project Tracking FUDSChem includes a project tracking functionality that gives a summary of the steps of a project and when they were completed. This summary is available in the form of the Project Tracking Status Report. The majority of the information on this report is filled out by the Synectics point of contact, though other users are invited to fill out the comments section. Information on how to update the report is found in sections 11.1 and ) This report can be accessed by clicking the Project Tracking Report link on the left hand side of the dashboard. 2) In the Project Tracking Report, the dropdowns will automatically prefill with Current District Only for Project Type, Active for Project Status, Active for the Event Status, and the date will be set to one week prior to today s date. Click view report. Figure 69 Event Tracking Reports, Project Tracking NOTE: A user will only be able to see projects for which they have permissions. Changing the Project Type to Non-FUDS for a FUDSChem user will result in an empty report. Along with the permissions-based dashboard link, CX and District Managers will also have access to this report for all projects in a district, regardless of their project permissions. These users will have a link to the Project Tracking report located under Reports Event Tracking Reports. Page 89 of 115

90 Figure 70 Project Tracking Report

91 3) The layout of the Project Tracking Report can be viewed in Figure 70. On the left hand side of the report (1) is the project name and number as well as other project information. 4) The key team members section (2) shows the main points of contact for the project. 5) The project level steps (3) include the status, such as In Progress, Not Applicable or a name and date to signify that the step is complete. (A1) Set Up Database: This step is marked complete when all key team members are identified and have been offered FUDSChem logins, and the project workspace has been created within FUDSChem. This step is performed by Synectics. (A2) QAPP Setup: This step is marked complete when the contractor has set up eqapp within FUDSChem and has certified it. Hard copy documentation is approved in the FUDSChem library for reference. This is a mandatory step, performed by contractor and assisted by Synectics. (A3) Historical Data: This step is marked complete when completed data from past events has been entered and approved. This step may or may not apply. (A4) Location Data: This step is marked complete when the contractor has added information on sampling locations into FUDSChem. It is a mandatory step, performed by contractor. (A5) Other Data/Documents: This step is marked complete when data from boring logs and well construction diagrams is entered into FUDSChem, and supporting hardcopy pdfs are added to the FUDSChem library. This is an optional step (determined on by the project contract), performed by contractor. 6) Project level comments (4) can be added by contractor or Corps users with the proper permissions. Refer to Section 11.1 for adding project level comments. 7) The event name and sampling dates are displayed (5). 8) The event level steps (6) include the same status options as the project level steps. (B1) Event Plan: Event planning may be used by the contractor to create system-generated Chains of Custody for their field team, and allow special event tracking reports to run. This step is optional, but recommended as the user will have to enter all of the same data in the next step if it is not done here. (B2) Field Data Entry: The contractor enters Chain of Custody information into the system. Note: any information entered into event planning automatically carries over into this step. This step is mandatory if using FUDSChem s built-in Automated Data Review. (B3) Field Params/Water Levels: This step is complete once the contractor has entered Groundwater Levels and Field Measurements associated with any sampled wells. Does not apply for projects that do not include wells. (B4) Laboratory Data: This step is complete once the laboratory has screened and certified their SEDD 5.2 file in FUDSChem and has added a lab report to the FUDSChem library. This step is mandatory for any projects with chemistry data. (B5) Validation Report: This step is complete when the data validator has reviewed the data, finalized the qualifiers and added a data validation report to the FUDSChem library. It is recommended to use FUDSChem s internal ADR and internal validation tools to validate data. (B6) USACE: This step is complete once the Corps has approved the chemistry data within FUDSChem. Once data is approved it will show up on final reports. (B7) Event Closed: This step is complete once Synectics determines that all event data has been uploaded and that all SDGs have a matching lab report and data validation report. 9) Event Comments (7) can be added by the contractor and Corps users, depending on permissions. Refer to Section 11.2 for adding event level comments. NOTE: The Project Tracking Report can be downloaded by clicking the floppy disc icon. Any column with an up and down arrow in the upper right corner can be sorted alphabetically by clicking on that arrow. Page 91 of 115

92 Steps that do not apply to a project can be marked as Not Applicable. For example, an event with soil samples would not have groundwater measurements collected. Information that has been updated since the Date chosen in the report header will be shown in blue. Comments can be added on the project or event level. Users with Project Setup Permissions can add comments by going to Tools, Data - Event Planning. NOTE: This menu link to edit the report is expected to be updated soon. Figure 71 Tools, Data - Event Planning Page 92 of 115

93 11.1 Create/Track Project(s) To add project level comments, go to the Create/Track Project(s) tab and click Add New Record in the Comment section at the bottom of the page. This tab will also be used to update the Key Team Members for an event. Figure 72 Create/Track Projects Tab Page 93 of 115

94 11.2 Create/Track Event(s) To add event level comments, go to the Create/Track Event(s) tab and click Add new record in the Comment section at the bottom of the page. Event step statuses such as sampling start and completion, event planning, and event closeout are updated in this interface. Figure 73 Create/Track Event(s) Tab NOTE: When entering a comment, the user should choose a Comment Type from the dropdown, add the date, and write their full name in the Owner box so the comment is easily identifiable. After updates have been made, select Save Changes in the lower left. Page 94 of 115

95 FUDSChem Library The FUDSChem library acts as a repository for all hard copy data that is entered into FUDSChem. Please note that the FUDSChem library is not a replacement for FRMD and any required files must be placed in FRMD according to standard document protocol. All PDFs should be processed with Optical Character Recognition (OCR) prior to upload to allow in-text searching. It is important that the metadata for all documents is populated during the upload process including coverage/site, event name, installation name, and publication date. The metadata supports advanced searching in FUDSChem, allowing users to filter the returned documents by the attributes of interest Upload Documents 1) To upload a document to the FUDSChem library, navigate to TOOLS and select Library File Submission. Figure 74 Library File Submission dropdown Page 95 of 115

96 2) Select Upload, choose a document, click the notepad icon, populate the appropriate metadata fields (as shown in Figure 75), select a document review user from the Assigned Reviewer dropdown menu (1), and click Save & Certify (2). Figure 75 Library Submission Metadata NOTE: The publication date should be filled out with the date on which the file was created, not the date it was uploaded to FUDSChem. Page 96 of 115

97 12.2 Search for Documents 1) To search for a document in the library, select the desired project under the LIBRARY dropdown menu, and then select the desired document type. 2) If you do not know what section of the library the desired document is in, select Search from the LIBRARY dropdown. NOTE: Choosing Miscellaneous from the LIBRARY dropdown allows the user to access and download reference documents such as User Guides. Choosing Electronic Data allows the user to access and download data that was entered into the system via data submission, either by hand or by flat file. Figure 76 Library Dropdown - Search Page 97 of 115

98 3) Enter the document name, coverage site, publication date or installation name in the search box, and click the Search button. To narrow or organize search results, select the desired search filters from the Show All File Types and Sort by System File Name dropdown menus. Figure 77 Library Search NOTE: Documents must be Approved in the library before they are searchable. Page 98 of 115

99 4) Users also have the option for a more detailed search. This tool can be accessed by selecting Advanced Search from the LIBRARY dropdown. Here the user can choose from many search options including file type, search text, search dates, and file properties to help the user find the document they are looking for in the library. Figure 78 Advanced Library Search Page 99 of 115

100 12.3 Retrieve Documents 1) To retrieve a document from the library, click on the document name in the library interface seen below. Figure 79 Library Document Retrieval 2) Clicking on the document name will open a new window. This window allows the user to view the document as a PDF or save it to a personal file. Right clicking on the document name will allow the user to choose several options for naming the file when it downloads, including Save target as server filename and Save target as title filename. Page 100 of 115

101 Figure 80 Library Document Retrieval (Retrieved Document) Page 101 of 115

102 Maps Coordinate information entered into FUDSChem can also be used to map locations in Google Earth through a secure connection. This allows the user to view sampling locations spatially without requiring GIS software. From FUDSChem, location information can be viewed in Google Earth by navigating to MAPS, Export to Google Earth. Figure 81 MAPS Tab Page 102 of 115

103 Once in the Export to Google Earth Interface, the various projects with layers available for export will be visible in the Select Layers to Include box. The user can click Expand All (1) to show all projects available for export, check the individual boxes (2) to choose the desired project(s) to view in Google Earth, then click Export Data (3). Figure 82 Export to Google Earth Note: Although GIS software is not required to view locations in Google Earth, GIS kml files can be imported into the FUDSChem library to add additional layers. Uploading documents to the library is covered in Section Page 103 of 115

104 Once the file is open within Google Earth, the user can check locations or layers in the Places bar (1) on the left to make them visible. Clicking on a location either in the Places bar or on the map will pull up a balloon with basic information on that location (2). Figure 83 Location Information Data types entered into FUDSChem for the selected location will also be listed (3). Clicking on the number next to a data type will open a report similar to the reports available in FUDSChem, showing that data for the selected location. Since the connection to Google Earth is secure, the user will be prompted to provide their FUDSChem login information before being able to access any data. Like reports in FUDSChem, these reports can be exported in XML, CSV, PDF, MHTML, Excel, TIFF, or Word format by clicking the save icon. Page 104 of 115