ESdat

The official product scope covers laboratory, field-program, data-logger, sensor, historical and regulatory-standard data. Validate the exact schemas, units, qualifiers, identifiers and source ownership needed for each contracted data stream.

The Field Management module supports plans, recurring schedules, staff assignment, status notifications, review and approval of monitoring rounds. Confirm this module, co-scheduling rules, allowed deviations and approval roles in the proposal.

Offline capture is documented for the Field App, which is an upgrade from the online Field Portal. Laboratory sample details in the app require Field Management. This is not evidence that the rest of ESdat works offline; pilot preparation, conflicts, attachments and receipt after synchronization.

Field-program documentation covers electronic chain of custody, planned analyses and containers, lab-request review and matching collected sample details to laboratory data. Advanced eQuote and eCOC integrations are available only with selected laboratories, so prove the named laboratory path.

Approved laboratories can upload reports for validation and loading, with errors returned to the user and laboratory and revised results loaded as issued. Coverage, turnaround, mappings, original-file retention and support responsibility must be confirmed for every named laboratory and region.

Official QA guidance lists frequency, field/interlaboratory/laboratory duplicates, blanks, spikes, surrogates, control and reference samples, inorganic checks, dilution factors and qualifiers. Results depend on correct sample typing, parent linkage and approved QA settings; the software does not decide fitness for use.

A Project Manager can approve or reject a lab report, with status, comments, date and approver shown. A later version cannot overwrite an approved report without rejection. Rejected results can still appear in data views unless filtered or deleted, so every operational and regulatory output needs an approved-data filter test.

Official guidance says edits to report details, samples and results record old and new values, date and person, including approval/revoke changes. Buyers should test export, retention and review of this history and distinguish an edit from a laboratory-issued replacement report.

ESdat provides compiled regional standards, site-specific standards, action levels and exceedance outputs. Its Server guidance explicitly makes the user responsible for verifying compiled data, suitability and compliance, so validate publisher, version, effective date, matrix, basis, units, location association and jurisdiction before use.

The reporting page documents customizable dashboards, chemistry exceedance tables, time-series graphs, trend analysis, common statistics and ProUCL export. Method selection, non-detect treatment, qualifiers and statistical interpretation remain specialist responsibilities.

ESdat documents map querying, Bing imagery, WMS/WFS and buyer basemaps, plus exports to ArcGIS, MapInfo and QGIS. Confirm coordinate reference systems, transformations, precision, layer permissions and completeness with surveyed control points.

User OData feeds support Power BI, Excel, Power Automate, Power Query and ArcGIS; the non-user Enterprise OData feed is additional-fee, ArcGIS can require its Data Interoperability Extension, and the ESdat API has an additional annual fee. Confirm authentication, service accounts, schemas, rate/volume limits and change management.