Synectic 2024 Former Fort Devens Data Management Plan - Version 2.pdf

Former Fort Devens Data Management Plan, Version 2 January 2024

Synectics

Former Fort Devens Environmental Restoration Project Environmental Data Management System

Data Management Plan Version 2

January 2024

Prepared for:

US Army Corps of Engineers New England District 696 Virginia Road Concord, MA 01742

Prepared by:

Environmental Synectics, Inc.

301 Richards Boulevard Sacramento, CA

Synectics

January 2024

Table of Contents

1.0 Introduction

1.1 Scope

1.2 Definitions, Acronyms, and Abbreviations

2.0 Accessing the EDMS

3.0 Data Integrity

3.1 Metadata

3.2 Quality Assurance

4.0 Tabular Data

4.1 Required Data Types

4.2 Data Format

4.3 Tabular Data Submission Workflow

4.4 Data Submission Timeframe

5.0 Spatial Data

5.1 Required Data Types

5.2 Data Format

5.3 Spatial Data Submission Workflow

5.4 Spatial Data Submission Timeframe

6.0 Document Library

6.1 Required Document Types

6.2 Document Format

6.3 Document Submission Workflow

6.4 Document Submission Timeframe

7.0 Support

W912WJ-23-F-0090-2023-0001

Former Fort Devens Data Management Plan, Version 2 January 2024

1.0 Introduction

The Former Fort Devens Environmental Data Management System (EDMS) is an enterprise level, comprehensive, web-based data management system designed to support the investigation, remediation, and monitoring of environmental projects. The EDMS facilitates the acquisition and dissemination of data to a wide range of stakeholders, and has the capacity to store tabular data, spatial data, and supporting documentation. The EDMS can be used to plan and track sampling events, process data in an automated manner, validate analytical data, generate final reports, and view data in spatial systems.

The EDMS provides users with real time access to all contractor data, as it is being generated.

It provides a centralized repository to allow the sharing of data between contractors and between data types, reducing errors and improving consistency. Controlled submission and approval processes ensure data integrity. Upon approval, data is made available to end users for reporting and analysis, and for export to government repositories.

The intent of the EDMS Data Management Plan is to provide data management guidelines for current and future contractors. The goal of this is to ensure data retains its integrity and to promote long term retention and stewardship of the data.

1.1 Scope

This document addresses key elements of the EDMS as applied to tabular data, spatial data, and data documentation, including:

The document is intended for use primarily by contractors performing activities associated with data collection and submission.

Former Fort Devens Data Management Plan, Version 2 January 2024

1.2 Definitions, Acronyms, and Abbreviations

ADR Automated Data Review

COC Chain of Custody

CSV Comma-Separated Values (file type)

EDD Electronic Data Deliverable

EDMS Environmental Data Management System

MOR Memorandum of Resolution

NAD83 North American Datum of 1983

NARA National Archives and Records Administration

O&M Operations and Maintenance

OCR Optical Character Recognition

OU Operational Unit

PDF Portable Document File (file type)

QAPP Quality Assurance Project Plan

RCL Response to Comments Letter

SDG Sample Delivery Group

TAT Turn Around Time

TXT Text (file type)

XML Extensible Markup Language (file type)

2.0 Accessing the EDMS

The EDMS functionality is available to stakeholders through secure access on-line at https://synectics.net http://ftdevens.org/

Former Fort Devens Data Management Plan, Version 2 January 2024

3.0 Data Integrity

All data contained in the EDMS is ultimately owned by the government. Data is submitted and maintained by data generators (contractors, subcontractors, contract laboratories, data validators, etc.) who are responsible for the accuracy of the submitted data. As the EDMS is the final archive for the project data, in the event that a contractor no longer works on the project, their data (tabular or spatial) and related documents will reside in the EDMS in perpetuity.

3.1 Metadata

All data and documents shall be accompanied by metadata, describing the attributes and contents of the work, such that a user has enough information about the dataset to determine its suitability to meeting their needs. Metadata is also used by the EDMS for traditional archival and documentation purposes, along with data mining to identify data in user searches and queries. The individual uploading the data or document is responsible for ensuring the accuracy of the associated metadata.

3.2 Quality Assurance

All tabular data, spatial data and documents submitted to the EDMS go through several quality assurance steps after being submitted by the data generator.

In the case of tabular data, the EDMS screens the data for errors via a series of automated screening checks which evaluate the file format, adherence to valid values, logic of the file content, and adherence to project requirements. The data generator must resolve any errors before data will be accepted into the EDMS. Once errors are resolved, the data generator certifies the data as complete and correct, after which point it may no longer be freely edited.

Then it is reviewed and approved by an authorized reviewer before being released to all stakeholders.

In the case of spatial data, data generators are expected to take responsibility for their specific datasets during the development and maintenance phase of their data. Data shall be checked for completeness, validity, logical consistency, physical consistency, referential integrity, and positional accuracy. Metadata shall also be checked for accuracy.

In the case of documents submitted to the EDMS library, the data generator will certify them as complete and correct, then an authorized reviewer, as decided upon by the PDT, will review and approve each document and its associated metadata. Metadata may be edited by the submitter or the reviewer. Once approved, the document will be released to all stakeholders.

Former Fort Devens Data Management Plan, Version 2 January 2024

In all cases, data is expected to be loaded by the stakeholder who collected the data or who is responsible for creating it. Data generators must follow the programmatic Quality Assurance Project Plan (QAPP) to evaluate, monitor, and maintain the quality and integrity of the data. They are also responsible for ensuring the proper content and format of their data.

All data loaded to the EDMS is stored in an SQL Server database. As files of any type are uploaded, the unaltered file is stored in a binary format in a single table. In the case of tabular data, it is also loaded into the appropriate database table where it can be queried, used for reporting, etc. Other file types, such as PDF, are accessed directly from the binary file when opened or downloaded by the user. As files are loaded they are automatically indexed and cataloged to appear in search results.

The EDMS O&M contractor can only make changes to data if provided a written (email) request, and is required to maintain documentation of any such request and the changes that were associated with it.

Former Fort Devens Data Management Plan, Version 2 January 2024

4.0 Tabular Data

Tabular data is technical information loaded and stored in the EDMS database. It includes chemistry data, location data, well information, field data, lithology data, etc.

Contractors may download their own data or other contractors’ data for their use once it has been approved by an authorized reviewer and released to all stakeholders. They may query select datasets or download full datasets, by running reports. Various export formats are available. Data must be approved before it is available in the majority of reports formats.

Some unapproved report capabilities are available to aid in the review process. Supporting documentation can be similarly downloaded in addition to being searchable and browse-able in the library as well.

4.1 Required Data Types

Data that is deemed worth collecting is preserved in the database for future use. Required data types include those listed below. Additional data may be requested and submitted at the discretion of the USACE project team. Required data types may not apply to all samples or locations. For example, well construction interval data will only be required for well locations and is not applicable for non-well locations. Data types and when they are required are outlined below:

Data Type Required For

Chemistry Data All sampled locations

Data Validation Qualifiers All sampled locations

Environmental Measurements All well locations

Groundwater Levels All well locations

Location Definition Information All sampled locations

Location Site Cross Reference All sampled locations

Lithology All well and soil boring locations

Well Completion Information All well locations

Well Construction Interval All well locations

Well Maintenance Information All well locations receiving maintenance

Former Fort Devens Data Management Plan, Version 2 January 2024

4.2 Data Format

Data format specifications for tabular data are provided on the EDMS portal. They can be accessed by going to Reports | ADR and Submission Reports | Electronic Data Specifications (Fixed Width). The specifications note whether each field is required or optional, and which fields require valid values. A list of valid values for each data type can be found under Reports | ADR and Submission Reports | Valid Value Lists.

Accepted file types for data upload include fixed width (TXT) and CSV files. Alternatively, most data types support the option to create a file directly within the EDMS’s Data Submission interface.

The data tables store generic metadata on the relevant data type. No additional metadata is required from the contractor when it comes to tabular data.

4.3 Tabular Data Submission Workflow

The process for submitting data to the EDMS is:

• Digitize the QAPP

• Establish Locations

• Plan Sampling Event

• Submit Data

• Screen Data

• Review and Approve Data

Each of these steps will be discussed in depth in the following sections.

W912WJ-23-F-0090-2023-0001

4.3.1 Digitizing the QAPP

Before sampling, contractors must establish a Quality Assurance Project Plan (QAPP). This QAPP shall be digitized into an eQAPP at the beginning of the project and used to apply qualifiers to the chemistry data during the Automated Data Review (ADR) process.

4.3.2 Establishing Locations

Before sampling, contractors must first identify sampling locations. All tabular data submitted to the EDMS must be tied to a location. When establishing locations, in a Location Definition Information record, each location ID must be defined by unique coordinates and a unique name. Unless otherwise specified, spatial data shall use the State Plane Coordinate System, with the North American Datum of 1983 (NAD83), and units of US feet.

Location names and location naming conventions shall be approved by the government point of contact. The following naming convention shall be followed for any new locations submitted to the EDMS. Note that the database may contain historical locations from various sources that are not compliant with these guidelines.

As a naming convention, the first three characters of the location ID shall indicate the site. This is followed by a hyphen. The next two characters indicate the location type; for example: BH for Borehole, DP for Drive Point, EW for Extraction Well, LK for lake or pond, LY for Lysimeter, MW for Monitoring Well, SS for Surface Survey, TR for Trench, WT for wetland or swamp, etc., which can all be referenced by using the Valid Value Lists under Reports, ADR and Submission Reports, followed by a hyphen. Next, a three-digit incremental number (including leading zeros) is used to differentiate the locations.

Location ID Naming Convention The Location ID naming convention shall use the following format to indicate the Site, Location Type, and Location. Each segment is separated by a hyphen.

Figure 1 – Location ID Naming Convention

Note: The initial site reference may not be needed for simple projects that do not include multiple sites in their scope. However, when the scope covers multiple sites or multiple operational units (OUs), the government may choose to include a 3-character site indicator in their location names.

W912WJ-23-F-0090-2023-0001

Segment # Characters Used for Example

First 3 Site A15 Area of Concern 15

Middle 2 Location Type BH Borehole DP Drive Point EW Extraction Well LK Lake or pond LY Lysimeter MW Monitoring Well SS Surface Survey TR Trench WE Wetland or swamp

Last 3 Location 012 Incremental number, including leading zeroes

Once location IDs are established, they must be approved by the appropriate government personnel to make them available for use. All location data must be tied to a site with a unique site ID in a Location Site Cross Reference record. This record can be created for any locations that have an approved Location Definition Information file. New site IDs can be set up by the O&M Contractor, under the direction of the government.

Once Location Definition Information records and Location Site Cross Reference records are established and approved, additional data types such as well completion information, well construction intervals, well maintenance information and lithology, can be loaded as applicable. Most of these data types are only submitted during the location establishment phase and do not need to be collected at every sampling event. Well maintenance information only needs to be submitted when performed.

4.3.3 Planning Sampling Events

Contractors are expected to use the event planning tool to track their field sampling operations. Using this tool allows stakeholders to run event tracking reports and allows contractors to generate chains of custody and bottle labels directly from the EDMS. Using the event planning tool prepopulates most of the field sampling information described in the next section.

Event Management also allows contractors to plan locations for non-chemistry data types.

Field sampling information is defined by Field Sample IDs. Note that a location ID, as described in the above section, is different from a field sample ID. The location is the geographic coordinates where samples are collected. The samples themselves will each be assigned their own field sample ID. Depth and sampling date are not part of the location ID. These can be included in the field sample ID.

A Field Sample ID is a unique name established to represent a specific sample from a given location.

Former Fort Devens Data Management Plan, Version 2 January 2024

The Field Sample ID can be a maximum of 30 characters in length, and is made up of uppercase alpha and numeric characters; the hyphen (-) and underscore (_) are the only allowable non-alphanumeric characters. Spaces should not be included in the Field Sample ID. Field sample IDs must be unique and cannot be reused in subsequent events for the same project.

The Field Sample ID should consist of the following elements:

1) Location ID

2) Unique timeframe indicator

3) QC indicator (if applicable)

The unique timeframe indicator should not be the exact date of sampling. This avoids rework, in the case that the sampling date changes. Instead a timeframe indicator of the year and quarter or year and month should be used.

An example of year and quarter is “_4Q2019” and an example of year and month is “_JAN19” or “_0119”.

QC indicator can be used to indicate field duplicates (e.g. “_FD”, “_DUP”), matrix spikes (“_MS”), matrix spike duplicates (“_MSD”), etc. Since these appendages need to be included in the character limit, we recommend making base sample IDs less than 25 characters.

Figure 2 – Field Sample ID Naming Convention

Segment # Characters Used for Example

Location

ID

Cannot exceed 15 characters Location ID A15-MW-012 An established location

Time Frame All three segments combined not to exceed 30 characters

Unique Timeframe Indicator

4Q2019 Year and quarter JAN19 Year and month abbreviation 0119 Year and month numerical

QC QC Indicator FD Field duplicate DUP Field duplicate MS Matrix Spike

NOTE: For resamples, the Field Sample ID should be updated to include an indication of resampling, such as adding "_R" to the end of the Location ID.

NOTE: In the case of blind field QCs, a QC indicator would be foregone in favor of a more subtle naming difference.

Former Fort Devens Data Management Plan, Version 2 January 2024

For samples that need to be further differentiated, it is recommended to append the depth interval that the sample was taken to the end of the Field Sample ID.

4.3.4 Submitting Data

Once field sampling has taken place, field data must be submitted in a Field Sampling (ChemField) file before the laboratory can upload their analytical data. The information contained in the field file will update live tracking reports, ensure completeness of laboratory deliverables, and support the Automated Data Review process. As a best practice, it is recommended that only one chain of custody be included per ChemField file. Information such as groundwater levels and environmental measurements can also be loaded as applicable. In most cases, these data types are required for standard well monitoring.

Contract laboratories are required to upload the associated laboratory data as an Electronic Data Deliverable (EDD) conforming to the EDMS specification, along with uploading a PDF of the associated laboratory report to the EDMS library.

Figure 3 – All Data Types Report

4.3.5 Screening Data

All types of tabular data are screened as part of the loading process. The EDMS evaluates the file format, adherence to valid values, logic of the file content, and adherence to project requirements. If errors are found, a link to an automatically generated error report is provided on the upload screen which notes the discrepancies. The error report will include information on the type of error found, along with sufficient detail to locate the problem records in the file.

The error report will direct the user to other reports that may be helpful for troubleshooting their errors. Errors must be resolved before the contractor can certify their submission.

W912WJ-23-F-0090-2023-0001

4.3.6 Reviewing Data

Following certification, the data becomes available for the data reviewer to review and approve, and the data generator will no longer have access to edit or delete the data. Once data is approved, it will become available to stakeholders through reports, maps, downloads, and queries.

Initiate ADR In the case of chemistry data, error-free submission of the laboratory EDD will automatically initiate the Automated Data Review (ADR) process. This process synchronizes the field data and laboratory EDD submissions and evaluates the laboratory data in accordance with the eQAPP. Initial validation qualifiers are applied automatically during this process.

Review Data Once the ADR process is finished, the data validator can begin reviewing data validation qualifiers. Unlike submission of all other data types, data validation does not require the upload of a separate file. Instead, once the laboratory certifies the EDD, the ADR automatically creates a data validation record for the data. The individual performing data validation uses the validation tools within the EDMS to review the qualifiers applied by the ADR and modify them as appropriate. Once complete, the initial data validator marks the qualifiers final within the interface.

Data Output Following the initial data validator’s finalization of the data qualifiers, a second reviewer chemist (from the validation contractor) will approve the EDD using the validation tools within the EDMS, at which time the chemistry data will become available to all stakeholders through all reports, maps, downloads, and queries. Some unapproved report capabilities exist to aid in review.

Former Fort Devens Data Management Plan, Version 2 January 2024

4.4 Tabular Data Submission Timeframe

Digitization of the eQAPP should be completed 90 days prior to sampling, but must be completed 7 days prior to the start of sampling.

Location data shall be submitted for pre-established locations 30 days prior to sampling.

Location data for planned samples shall be submitted 30 days prior to sampling, with the understanding that estimated or placeholder values will be used for coordinates, elevations, establishing date, etc. Estimated values will be updated within 7 days of surveying.

One-time data entry associated with location creation, including lithology data found on boring logs or well construction intervals found on well construction logs, shall be submitted 30 days prior to sampling in the case of pre-established wells, or 21 days after drilling completion in the case of new wells.

Non-chemistry data such as environmental measurements and groundwater levels shall be submitted within 30 days of sampling.

Validated chemistry data shall be approved in the EDMS within 60 days of sampling. Within that timeframe, routine laboratory turnaround times are 21 days. Routine data validation turnaround times are 21 days from the date the data is uploaded into the database by the laboratory.

Requirement Responsible Party Total Time from Sampling

Digitization of the eQAPP Contractor 90 days prior to sampling

Load location data into the EDMS Contractor 30 days prior to sampling

Complete Event Planning in the EDMS Contractor 7 days prior to sampling

Load field data into the EDMS Contractor 7 days after sampling

Update estimated location data based on survey Contractor 7 days after sampling

Load well construction data into the EDMS Contractor 21 days after boring completion

Load environmental measurement data into the

EDMS

Contractor 30 days after sample collection

Load laboratory Electronic Data Deliverable (EDD) and laboratory report PDF into the EDMS

Contract Laboratory 21 days after sampling

Validate data and apply qualifiers through the EDMS module, load data validation report PDF into the EDMS

Contract Validator

21 days from EDD upload ~42 days after sampling

Approve validated chemical data, making data available in the EDMS for all stakeholders

Government Chemist 60 days after sampling

W912WJ-23-F-0090-2023-0001

Figure 4 – Data Submission Timeframe

Exceptions to these timelines include reporting of critical data required for modeling and risk assessment, which may require expedited upload to the EDMS. The above timeframes are highly recommended expectations, but actual TATs are subject to contract details.

Former Fort Devens Data Management Plan, Version 2 January 2024

5.0 Spatial Data

Spatial data is any data with a positional reference. Since all data within the EDMS must be tied to a location, all data within the EDMS includes a spatial component. The EDMS is designed to accept and manage a variety of spatial data, including GIS layers from numerous sources. GIS vector and raster data layers are stored in the document library. Previously collected spatial data is available for download by all users. The user can search for a particular set of spatial data in the library and download it to their local computer. Once it is downloaded, the user can unzip the data package and view the data in their own third-party software.

The user can also use the Export to Google Earth tool in the EDMS to export location, chemistry, and environmental measurement data to view in Google Earth.

Figure 5 – Data Overlay in Google Earth

5.1 Required Data Types

Contractors are responsible for the capture, collection and generation of their spatial data.

This includes digitizing, scanning, registering, or otherwise processing vector and raster data.

It is important that contractors ensure the quality of the format of their data and adhere to naming conventions.

It is recommended that contractors minimize the quantity of data layers submitted to the system. Therefore, contractors shall consider merging, appending, or otherwise organizing common data layers when appropriate.

The following data is required for submission to the EDMS.

• Spatial data layers used in final reports or agency draft reports

• Plume data layers

• Other data layers upon request

The following spatial data is not required for submission, unless specifically requested.

• Draft materials

W912WJ-23-F-0090-2023-0001

• Specific points, data, or features provided on a map that are not part of a data layer

5.2 Data Format

The EDMS requires that all spatial data have the same standard coordinate system. Unless otherwise specified, spatial data shall use the State Plane Coordinate System, with the North American Datum of 1983 (NAD83), and units of US feet. Spatial Data should be uploaded to the EDMS library as zipped files containing data in one of the following formats:

Figure 6 – Data File Formats

• Shape file (SHP)

• Geographic modeling file (KML)

• Map locations file (KMZ)

• Extensible markup file (XML)

All spatial data uploaded to the EDMS library must have an accompanying metadata file in XML file format.

The metadata must contain all required fields, a description of data accuracy and completeness, lineage (history of changes, processes used to create data), and full attribute information. Plume metadata must also include an “As of” date, being the most recent date that the tabular data pulled from the EDMS was used to model the plume.

Spatial data files shall follow the naming convention of SITEID_LayerType_AsOfDate. The “As of” date shall follow the format YYYY-MM-DD (e.g., 2018-02-10). All associated files or folders in an upload are to be contained in a single zip file for each submittal. Metadata is to be included in the zip folder.

Figure 7 – Spatial Data Naming Convention

Former Fort Devens Data Management Plan, Version 2 January 2024

5.3 Spatial Data Submission Workflow

As spatial data, along with its metadata, is created by the data generator over the course of a project, data shall be checked for completeness, validity, logical consistency, physical consistency, referential integrity, and positional accuracy. Metadata shall also be checked for accuracy.

Once it has been checked, data is zipped in a zip file. The zip file is uploaded to the EDMS library. The library submission interface allows contractors to select files from their local machine and fill out several mandatory high-level metadata requirements as part of the upload process.

Required metadata includes document title, publication date, access level, file category, file subcategory, author organization and coverage site. Additional, non-required metadata fields are also available. In the event that a required field is not populated, the file will not be able to be certified.

Certain metadata fields require valid values, which are provided in the interface dropdown menus. Users may contact the O&M contractor to request additional options be added to the look-up values in these specific metadata fields if the value needed does not currently exist.

5.4 Spatial Data Submission Timeframe

Spatial data used in reports is to be posted to the EDMS within two weeks of submittal of the document. Spatial data used for presentations, such as plume layers, shall be posted to the EDMS within two weeks of the presentation.

The government may request expedited upload of spatial data layers to the EDMS based on program needs.

Former Fort Devens Data Management Plan, Version 2 January 2024

6.0 Document Library

The EDMS provides a document library which allows for storing, searching, and viewing of project-related documents. Documents may be downloaded from the library or opened in a separate window for viewing. Document Library organization is to be controlled by the appropriate government personnel.

6.1 Required Document Types

Documentation to be submitted to the EDMS include those that are part of official distribution and those that may become part of the digital administrative record, which can be found at https://www.nae.usace.army.mil/missions/projects-topics/former-fort-devens-environmental-cleanup/. Examples of such documents include:

• Agency draft documents

• EPA comments

• Final Documents

• Memoranda of Resolution (MOR)

• MOR Approval – EPA

• Official correspondence letters

• Response to Comments Letters (RCL)

Additionally, supporting documentation for technical data must be submitted to the EDMS library. Examples of such documentation include:

• Boring logs

• Chains of custody

• Data validation reports

• Field log sampling forms

• Laboratory reports

• Well construction diagrams

For example, each well location shall have an associated boring log and well construction diagram.

Each SDG shall have an associated laboratory report and data validation report.

Exceptions shall be approved by the government. Supporting documentation shall be searchable on a location by location basis or on an SDG by SDG basis. All electronic data submitted to EDMS should have an accompanying hardcopy documentation uploaded to the EDMS library.

https://www.nae.usace.army.mil/missions/projects-topics/former-fort-devens-environmental-cleanup/

Former Fort Devens Data Management Plan, Version 2 January 2024

6.2 Document Format

Documentation standards of this EDMS are to be upheld by the National Archives and Records Administration (NARA) standards which can be referenced at (https://www.archives.gov).

Documents are to be submitted in Adobe Acrobat Portable Document Files (PDF) format.

Multipart files shall be merged into a single PDF prior to upload. The use of special characters such as ampersand (&), quotation marks, commas, etc. in the PDF name is not allowed.

The EDMS requires PDF files be optimized. This is most easily done when producing a new PDF, but can be done for existing PDF files as well. When producing a new PDF, there are typically customizable options to specify how the source material is transformed into the PDF format. One such option is linearization and is typically described as “Optimize for Web Viewing” or “Fast Web View.” This option must be selected for the resulting PDF to be able to be “byte served” over the web for page-at-a-time delivery, which results in faster download times.

To check if a PDF has Fast Web View:

1) Open the file and go to File, Document Properties.

2) Click the Description tab.

3) The lower right of the dialog box should include a “Yes” or “No” for Fast Web View.

To include Fast Web View when creating a new PDF document or to add Fast Web View to an existing document:

1) Choose Edit, Preferences.

2) On the left side in the Categories dialog box, choose Documents and under Save Settings, select

“Save As optimizes for Fast Web View.” This option may be set by default. Click OK.

3) Choose File, Save As and select the same file name and location.

Documents uploaded to EDMS should also be text recognized. This can be done by using Optical Character Recognition (OCR) software which is usually included in Adobe for PDFs. This is especially important for scanned documents such as Chain of Custodies (COCs) or field forms. Text recognizing the document will allow it to be searchable in the EDMS library.

Document titles should follow the below naming conventions.

Document Type Naming Convention Example

Boring Log Boring Log, [Well Location ID]

Boring Log, A15-MW-012

Chain of Custody Chain of Custody, [COC ID Number]

Chain of Custody, 011519A

Note: The location of the Preferences section and Optimization features may vary based on the version of Adobe Acrobat. Please refer to Adobe Help for more information.

W912WJ-23-F-0090-2023-0001

Data Validation Report Data Validation Report, [SDG Number]

Data Validation Report, SDG 280-115217

Groundwater Collection Log Groundwater Sample Collection Log, [Event Name]

Groundwater Sample Collection Log, Long Term Monitoring, AOC 32/43A Spring 2019

Laboratory Report Laboratory Report, [SDG Number]

Laboratory Report, SDG 280-115217

Laboratory Sample Receipt Laboratory Sample Receipt, [SDG Number]

Laboratory Sample Receipt, SDG 280-115217

Well Construction Diagram Well Construction Diagram, [Well Location ID]

Well Construction Diagram, A15-MW-012

Other For other documents, use the title of the document as the name

6.3 Document Submission Workflow

Once documents are optimized, they are uploaded to the EDMS library. The library submission interface allows contractors to select files from their local machine and fill out several mandatory high-level metadata requirements as part of the upload process. Required metadata includes:

1. Document title

2. Publication date

3. Access level

4. File category

5. File subcategory

6. Author organization

7. Coverage site

Additional, non-required metadata fields are also available. In the event that a required field is not populated, the file will not be able to be certified.

Certain metadata fields require valid values, which are provided in the interface dropdown menu under Reports | ADR and Submission Reports | Valid Value Lists. Users may contact the O&M contractor to request additional options be added to the look-up values in these specific metadata fields if the value needed does not currently exist.

Contractors have the ability to re-classify, modify metadata, re-title files, and delete files until they are approved by an authorized reviewer. When a document is approved by an authorized reviewer, it becomes available for reference in the EDMS library.

Former Fort Devens Data Management Plan, Version 2 January 2024

6.4 Document Submission Timeframe

Project documents shall be submitted to the EDMS within one week of the release date of the draft or final version. Supporting documents detailing well drilling, such as boring logs or well construction diagrams, shall be uploaded when the data they support is certified. Laboratory reports shall be uploaded when the data they support is certified. Data validation reports shall be uploaded when the data qualifiers they support are marked final (see Section 4.4).

The government may request expedited upload of certain documents to the EDMS library based on program needs.

7.0 Support

For EDMS support, please contact the O&M Contractor, Synectics, at 916.737.4010 between the hours of 6 am and 6 pm Pacific Time, or send an email to the Synectics Point of Contact listed on the Former Fort Devens dashboard. Training sessions may be scheduled upon request.

7.0 Support