What is built.
What is next.

OpenBGA Environmental LIMS is developed in the open. This roadmap lists what the project has built, what it is working on next and where it is heading after that.

It carries no dates. Work is grouped by what a laboratory needs and ordered by what stands between a laboratory and daily use. The order can change when laboratories say otherwise.

Reviewed November 2026

Built

The journey
is in place.

A sample can travel from receipt to an amended report with its custody, QC, review and release on record. These areas are implemented and covered by automated checks on synthetic data. The project has not yet made a stable release.

What OpenBGA Environmental LIMS has built
AreaWhat is in place
Custody and receiptClients, projects and chains of custody. Receipt inspection with containers, preservation checks, discrepancies and their dispositions. Custody events and corrections that keep their reason. Back to the roadmap
Methods and rulesVersioned methods, analytes and tests per matrix, with units, reporting limits and qualifiers. Holding-time and preservation rules, QC requirements and limits, all set by the laboratory. A holding-time limit per method, or per analyte where one method covers analytes with different limits. Starter files for common methods, each rule naming its public source, for the laboratory to check and edit before loading. Back to the roadmap
Bench workPreparation and analytical batches with their QC samples. Manual entry and mapped CSV, TSV or XLSX worksheet import, each keeping its source. A generic instrument run-list CSV of the batch’s assigned tests and recorded QC samples, with sample states and recorded preparation identities. Holding times computed from the rules, never typed. Results worked out from bench readings for dilutions, solids by weight, preparation factors, percent solids and moisture, dry-weight correction for soil, alkalinity and EDTA hardness titrations, and BOD bottle worksheets: the readings, the version of the calculation and the rounding stay with the result, the reporting limit follows the amounts prepared, and the laboratory sets the rounding. BOD keeps each bottle’s readings, entered seed correction and its source, and the analyst’s selection for the reported mean; it does not select usable bottles or calculate seed controls. Back to the roadmap
QC and reviewInstrument-reported calibration curves with exact standard points and explicit curve and verification links on result revisions. QC evaluated against configured limits, with a recorded disposition for each failure. Control charts and MDL studies. Independent technical review that can return work with a reason. Back to the roadmap
ReportsExplicit release authorization. Stored PDF versions with a content hash, and amendments that keep earlier versions. The laboratory's address, logo and certificate numbers on each new report. One exploratory electronic deliverable in the New York State format. Back to the roadmap
Client portalEach client sees its own projects, samples, reports and quotes, and can send a chain of custody ahead of the samples. Back to the roadmap
Sales and schedulingOptional client account-hold notices at receipt and report release, with an internal note and change history. Price lists, versioned quotes and internal draft invoices from received tests and price lists or matching accepted quotes, including their fee and discount lines, with billing snapshots and reasoned edits. Delivery targets with a schedule by due date, sample and container labels with barcodes, and subcontracted tests with an independent check of the source. Back to the roadmap
Laboratory recordsStandards, reagents and lots with stock movements. Equipment calibration and maintenance. Training and demonstrations of capability. Nonconformance and corrective action. Sample storage and disposal. Back to the roadmap
PlatformRoles and permissions checked on the server, an attributed audit trail, optional two-factor sign-in, help for every page and announcements. Import of clients, projects, methods, tests, limits and rules from spreadsheets saved as CSV, previewed row by row. Acceptance scripts a laboratory runs on its own installation and keeps as evidence. A container image and a documented backup and restore procedure. Back to the roadmap

Next

What daily work
still needs.

Five areas stand between the current software and a laboratory that runs its routine work in it. They are listed in the order the project intends to take them.

  1. A first stable release

    Laboratories are asked to evaluate with synthetic data. They need a version they can install, check and upgrade.

    • Versioned releases with upgrade notes and tested migrations
    Back to the roadmap
  2. Instrument data

    Results load today from CSV, TSV and selected XLSX worksheets that an operator maps. Laboratories expect instrument exports to load as they are, with the raw file kept beside the batch.

    • Import layouts checked against real exports from common instrument types, such as ICP, discrete analyzers, ion chromatography and TOC
    • Raw files stored with the batch, in storage sized for them
    • Vendor-specific run-list layouts; a generic CSV of batch tests and recorded QC samples is built, with column mapping and injection order left to the laboratory
    • Method-specific calibration fitting and run-sequence checks, including verification bracketing; recorded curves and one optional verification link per result revision are built
    Back to the roadmap
  3. Invoicing

    A commercial laboratory bills for its work. Internal drafts now take received tests and a price list or matching accepted quote, with quoted and manually added fees and discounts, billing details and edit history. Issuing invoices and accounting export remain.

    • Issued invoices; drafts from price lists or matching accepted quotes, with quoted and manually added fees and discounts, are built
    • Tax and due-date handling; draft billing contact, address, purchase order and payment terms already come from client, project and order records
    • Export to accounting software, which stays the ledger
    Back to the roadmap
  4. Notifications and client results

    The application sends no notifications today, and the portal shows status and report files. Clients want to be told, and to work with their numbers.

    • Email when samples arrive, when a receipt problem needs a decision and when a report is issued or amended
    • Reminders for staff, such as holding times at risk and work returned from review
    • Result tables in the portal, with download
    • Trends by sampling location, with results marked against limits the client supplies
    Back to the roadmap
  5. Electronic deliverables

    Many clients and agencies take data as a file in their own format, and accept it only against their own specification. One exploratory export exists.

    • A configurable CSV and Excel deliverable for client templates
    • The EQuIS-style four-file deliverable with reference values, passed through a named recipient's checker
    • Report packages with a QC summary, chosen per order
    • Permit summaries for discharge monitoring reports: averages, maximums and loadings. The permittee still files the report.
    Back to the roadmap

Later

Depth
and breadth.

Planned after the work above. The order here is looser, and a laboratory that needs one of these can move it forward.

  • Quality system records

    Assessors look past sample data to the laboratory's whole quality system. Equipment, materials, training and nonconformance are recorded today. These complete the set.

    • Proficiency testing: studies, reported results, scores and follow-up
    • Controlled documents: SOP versions linked to methods, with read acknowledgement
    • Internal audits, findings, complaints and management review
    • Checks at the point of use that a laboratory can turn on: a current demonstration of capability, equipment in calibration, lots within expiry
    • Method validation, measurement uncertainty and ongoing MDL verification
    Back to the roadmap
  • Management view

    Work queues show what is waiting. Managers also need to see how the laboratory is doing.

    • Turnaround, on-time delivery and backlog by stage
    • Due dates worked out from turnaround terms and the laboratory's working calendar
    • Holding-time misses and QC failure rates by method
    • Workload by method and analyst
    • Audit trail search by person, record and date
    Back to the roadmap
  • Drinking water programs

    Drinking water compliance results count only from a laboratory certified for the method and analyte, and many states take them electronically.

    • A register of certified or accredited scope per program, with results outside it marked
    • Public water system, facility and sampling point identifiers
    • Compliance sample types, such as routine and repeat samples
    • Electronic reporting to a state agency, starting with the format of EPA's Compliance Monitoring Data Portal
    Back to the roadmap
  • Microbiology

    Coliform and E. coli testing is routine in water and wastewater laboratories, and its results are counts or presence, not concentrations.

    • Presence or absence, most probable number and plate count results
    • Incubation start and read times checked against the method's window
    • Media, sterility and incubator temperature records
    Back to the roadmap
  • Sampling and field work

    Much of a laboratory's work repeats on a permit schedule and starts before the cooler arrives.

    • Recurring sampling plans, with expected and missed collections visible
    • Sampling locations kept per client and project
    • A bottle catalog, kit orders and pre-printed labels
    • Field measurements recorded with the sample, such as pH, temperature, residual chlorine and depth
    • Capture on a phone or tablet in the field
    Back to the roadmap
  • Trace organics and PFAS

    The first method set covers metals, nutrients and solids. Organic methods bring their own QC, and PFAS work adds isotope dilution at parts-per-trillion levels.

    • Surrogates, internal standards and tentatively identified compounds
    • Isotope dilution with labeled-standard recoveries, as EPA Method 1633A uses
    • Summed analytes, and branched and linear isomers
    Back to the roadmap
  • Integrations and scale

    A laboratory system works beside other systems and grows with the laboratory.

    • An API and webhooks for status, results and reports
    • Single sign-on, a sign-in policy the laboratory sets and a signature step at release
    • Background jobs for long imports and report runs
    • Stronger tamper evidence for the audit trail and issued reports
    Back to the roadmap

Exploring

Open
questions.

Directions the project is weighing. Each needs a laboratory that wants it and can test it.

More regulator formats
California GeoTracker EDF, Florida ADaPT, EPA's SEDD and the Water Quality Exchange. One at a time, each tested against the recipient's own specification. Back to the roadmap
Assisted review
Software that points a reviewer to unusual results or missing evidence. A person still makes every review and release decision. Back to the roadmap
AI assistant access (MCP)
A Model Context Protocol server, so an AI assistant can look up the records the signed-in person may already see, with the same permissions. Every change still happens in the application, with its audit trail. Back to the roadmap
Multi-site laboratories
Several locations within one laboratory organization. One organization per deployment stays the design. Back to the roadmap
Other disciplines
Whole effluent toxicity, radiochemistry and air. Only with a laboratory that runs them. Back to the roadmap

What shaped
the order.

Three things: the public rules a US environmental laboratory works under, what laboratories ask for when they choose a system, and what the project's own documents list as unfinished. Sources were checked in November 2026.

What laboratories ask for
Public requests for proposals from water utility laboratories list instrument interfaces, calibration records, proficiency testing, data migration and acceptance testing among their requirements. A commercial laboratory also has to bill. That puts bench work, instruments, invoicing and deliverables first.
Accreditation records
Laboratories accredited to the TNI standard or ISO/IEC 17025 keep records for proficiency testing, document control, audits, complaints and management review. The roadmap adds those records. It does not reproduce either standard.
Permit reporting
Clean Water Act methods set holding times, preservation and QC elements (40 CFR Part 136). Permittees file their discharge monitoring reports electronically (NPDES Electronic Reporting Rule), and the laboratory supplies the results, so the plan is a summary a permittee can file from.
Deliverables
A recipient accepts an electronic deliverable only against its own current specification and reference values. Formats are added one recipient at a time and are called supported only after that recipient's checker passes them.
Drinking water
Compliance samples must be analyzed by a certified laboratory (40 CFR 141.28). EPA's Compliance Monitoring Data Portal lets laboratories report to state agencies electronically.
PFAS
EPA Method 1633A measures 40 PFAS in water, solids, biosolids and tissue. Its data differs enough from metals and nutrients to be its own item.

Help set
the order.

Tell the project what your laboratory needs, or share an instrument export layout filled with invented values. Laboratory feedback moves items on this page.

OpenBGA Environmental LIMS supports laboratory records and quality systems. It does not certify compliance or accreditation, and nothing on this page is a commitment to a date.