Who this article is for: Authority users

Some discharge limits apply to a parent analyte that is really a list of compounds — Total Toxic Organics (TTO), VOCs, and similar. A compound group is a named list of those compounds attached to a parent analyte.

Bind a compound group to a sampling specification and SwiftComply adds the member results together on each sample report to produce the parent's value, rather than asking the industrial user to report one lump figure. The individual compounds stay visible, so you can see what made up the total.

Compound groups are supplied with SwiftComply and seeded from federal and EPA standards — 40 CFR 413 and 433, EPA 624 and 8260, and others. Their names carry the citation, so you pick them by the rule they come from:

You select from this catalog when configuring a sampling specification; the lists themselves are maintained by SwiftComply rather than edited in your organization.

One parent analyte per specification. A specification can only bind a compound group when it covers a single parent. If you select more than one parent analyte, SwiftComply tells you to split them:

If no group exists for that analyte, the picker is disabled and explains that no compound groups are available for it. The specification still saves — it just records that analyte on its own.

Once a specification is bound to a compound group:

A compound can belong to more than one group. Benzene, for example, sits in both TTO and VOCs. A single reported Benzene result counts toward every group whose list contains it, so a report carrying both specifications gets both totals from the one entry — you do not ask for it twice.

If a report covers a group-bound specification and none of the group's compounds are reported, SwiftComply raises a single missing-data nonconformance against the parent analyte — not one per compound. You get one item to chase rather than a list of twenty.

Compound group lists change when the underlying regulation changes. When SwiftComply revises a list, existing sampling specifications stay bound to the list they were configured with, so reports submitted earlier keep the compounds that applied at the time. New specifications pick up the revised list.

This means an older configuration and a newer one can legitimately hold different compounds for the same parent analyte.

Do I have to enter the parent analyte's total myself?

No. When a specification is bound to a compound group, the parent's value is summed from the member results automatically. Enter the individual compounds and the total follows.

Why is the compound group picker unavailable?

Either there are no compound groups available for the analyte you selected, or the list is still loading. If the analyte has no groups, the specification saves as a single entry for that analyte.

I selected two parent analytes and the picker disappeared.

A compound group can only be bound to a specification covering one parent. Split it into separate specifications — one per parent analyte — and pick a group for each.

Can I build my own compound list?

Not currently. The catalog is supplied with SwiftComply and seeded from federal and EPA standards. If a rule your program enforces is not represented, raise it with your CSM.

The same compound is in two of my groups. Will the user report it twice?

No. A single reported result feeds every group whose list contains that compound, so one entry satisfies both.

None of the group's compounds were sampled. How does that show up?

As one missing-data nonconformance against the parent analyte, rather than one for each compound in the list.