Sample, test, specification, workflow and compliance controls
No duplicate laboratory record and no forced replacement of the customer's LIMS, ELN or QMS.
For LIMS, ELN, instrument and laboratory-software platforms
Keep your platform as the laboratory system of record. Add the FTIR investigation layer your customers still perform manually.
Your platform already manages samples, specifications, users, approvals and laboratory workflow. FTIR.fun adds spectroscopy-specific work after the spectrum arrives: identification, peak-level evidence, research comparison, QC mismatch investigation and structured scientific results that can return to the host record.
The integration value
Do more than return a hit list or FAIL flag. Return where the spectrum differs, which bands changed, the likely causes supported by the available evidence, what remains uncertain, and what should be checked next.
What your customer gets
A spectroscopy specialist inside the workflow they already use
Spectroscopy-specific investigation
Search and identification evidence, peak interpretation, grouped research analysis, qualified-history QC comparison and cause-oriented mismatch investigation.
A structured result, not another analyst tab
Conclusion, numerical findings, abnormal bands, interpretation, evidence, limitations, next checks and provenance can be consumed by the host workflow.
Integration Guide
Go from one host record to a returned scientific result
Use these steps for a first integration. A PoC should exercise the same path end to end with a real customer workflow.
1
Choose the host action
Start with one user action such as Identify spectrum, Explain peaks, Compare research groups or Investigate QC mismatch. Define the sample and business context the host will send.
2
Authenticate and submit
Create the integration credential, send the spectrum plus sample context, and receive the task identifier needed for the host record.
3
Track the task
Poll or receive task state without inventing progress. Preserve the host sample ID and FTIR.fun analysis identifier together so retries and review remain traceable.
4
Retrieve the complete result
Consume the machine-readable conclusion together with numerical findings, peak or region evidence, provenance, limitations, recommended confirmation and artifacts required by the selected workflow.
5
Render it in the host product
Attach the result to the existing LIMS, ELN or laboratory-software record. Keep approvals and disposition in the host while exposing the spectroscopy evidence to the analyst and reviewer.
Best first integration
QC mismatch investigation creates value beyond a generic spectral API
A LabVantage-type workflow
A raw-material lot fails the customer's routine FTIR conformity check. The LIMS sends the spectrum, material identity and qualified-history context to FTIR.fun. FTIR.fun compares the new lot with accepted historical lots, identifies abnormal regions and changed bands, evaluates contamination, degradation, supplier/material change, sampling, instrument and process explanations, links the findings to supporting spectral or literature evidence, and recommends the next confirmation. The structured result returns to the same deviation record for analyst and QA review.
Competitive difference
API access is not the differentiator. The scientific depth of the returned FTIR result is.
| Platform need | Typical existing capability | What FTIR.fun adds |
|---|---|---|
| Sample / workflow / approval | Core LIMS and ELN capability. | The host remains the system of record; FTIR.fun supplies the scientific analysis. |
| Spectral library search | Instrument and spectral-data products already return candidates and match scores. | Continue from retrieval into characteristic bands, evidence, conclusion strength and next checks. |
| QC exception | Instrument software flags the exception and LIMS/QMS controls the deviation. | Investigate the spectroscopy in between: qualified-history deviation, abnormal regions, changed peaks, causes, evidence and confirmation. |
| Research series | Files and general statistics may live elsewhere. | Keep groups and replicates, identify the spectral variables driving the difference, and connect them to material meaning. |
| Paper FTIR figure | Often remains an image or attachment. | Recover the curve as numerical spectrum data and continue directly into comparison and interpretation. |
| Customer-specific process | Broad platforms can be configured, but domain science still has to be built. | Provide spectroscopy-specific workflow logic, result fields and evidence for the partner's target customer segment. |
Regulated-platform fit
Return reviewable scientific evidence into the customer's controlled process
Host platform controls
- Authoritative sample and specification record
- Users, roles, approvals and electronic signatures
- OOS / deviation / CAPA state and final disposition
- Retention, audit and system-level validation controls
→
FTIR.fun supplies
- Source-spectrum and context identity
- Reference or qualified-history basis
- Method / analysis version and numerical findings
- Abnormal regions, changed bands and cause analysis
- Supporting evidence, limitations and next checks
Platform PoC
Prove one customer workflow end to end
Choose one high-value workflow and test the actual host action, API exchange, scientific result and returned user experience — not a generic API demonstration.
- One host record type and user action
- Representative spectra and business context
- Required request and returned fields
- Success criteria for the partner and end user