A Spectrus structure assignment is not compound identification

An assignment links records; it does not settle identity

ACD/Labs says Spectrus applications can connect full structures, fragments, Markush structures, or atoms to spectra and chromatograms, and describes tools for candidate search and computer-assisted elucidation. That is official provider documentation, not an independently verified identification result. A displayed link can represent a proposed assignment, imported annotation, predicted match, reviewer conclusion, or reuse of an earlier record. The state and author must remain visible.

Build an assignment record around the sample and analytical question. Include sample and aliquot identity, custody, material or batch context, preparation, instrument and configuration, acquisition method and version, raw-file identifier and checksum, processing method and parameters, derived-data version, reference library and version, candidate structure or fragment, match or reasoning output, exclusions, confidence or uncertainty, analyst, review state, and intended use. Keep the software object distinct from the approved laboratory conclusion.

Normalization must retain the path back to native evidence

The Spectrus page describes native support for many formats, a common analytical format, and normalization for AI or machine-learning uses. Normalized data can improve cross-instrument work, but conversion may change metadata, precision, units, encoding, peak representation, acquisition context, or vendor-specific fields. Store the original native object, converter and version, mapping rules, validation result, warnings, omissions, timestamps, and the relationship between each normalized and derived record.

A reviewer should be able to move from the structure assignment back through processed spectra or chromatograms to the original observation and metadata needed for reconstruction. If a format is only partially supported, a file is reprocessed, or a mapping changes, the system should preserve both versions and identify dependent assignments, reports, models, or decisions that require review. Accessible data are not necessarily complete, correct, contemporaneous, or fit for the intended scientific use.

Define the scientific review and exception path

Identification criteria depend on analytical technique, sample, purpose, method, expected alternatives, reference material, spectral quality, orthogonal evidence, and applicable laboratory procedure. Software can organize candidates and evidence, but the laboratory decides what constitutes tentative, probable, confirmed, rejected, or unresolved identity. The record should name the qualified reviewer, criteria used, discrepancies, required second technique or standard, override reason, signature or approval state, and any later correction.

Test ambiguous cases: co-eluting components, isomers, low signal, contamination, incomplete fragments, library-version change, conflicting NMR and mass-spectrometry evidence, reprocessed data, a renamed sample, and an analyst who lacks approval authority. The interface should not convert the highest-ranked candidate or a structure drawn on screen into a definitive conclusion. Downstream reports and decisions should receive the reviewed state and uncertainty, not only a structure identifier.

Reconstruct one conclusion across techniques and revisions

A buyer demonstration should begin with a representative native file and follow acquisition context, import, normalization, processing, candidate generation, structure assignment, orthogonal evidence, review, report, correction, and later reuse. Ask a second scientist to reconstruct why the conclusion was reached using the retained records. Then change a processing parameter or library version and verify that the system creates a new result and flags affected conclusions instead of silently replacing history.

Lab Systems Index reviewed the registered ACD/Labs Spectrus page on September 5, 2026. It supports the documented platform and data-handling capabilities, but it does not establish a customer's configuration, format fidelity, method suitability, data integrity, candidate accuracy, identification, validation, compliance, scientific validity, productivity, or outcome. This is clean current-source operating analysis, not a verified post-cutoff release.

Enterprise buyer test

Translate this change into the exact population, record type, workflow stage, decision owner, effective date, and evidence that could be affected. Ask current or prospective providers to demonstrate the named workflow with representative data and an exception—not a polished feature tour. Record what official documentation establishes, what a provider states, what the team observes, and what remains unresolved.

A defensible review also identifies the dependency outside the product. Authority interpretation, policy configuration, data quality, integrations, human judgment, approval rights, release governance, training, and retained evidence may remain customer or service responsibilities. The evaluation should preserve those boundaries instead of treating a technology claim as the complete operating model.

What we will watch next

Lab Systems Index will watch the named source and affected market records for later evidence that changes status, scope, availability, implementation timing, workflow consequence, or the limits of the initial report. A later announcement does not silently overwrite this dated account; the change ledger preserves the sequence.