Skip to main content

SAP. Veeva. LabWare. AVEVA PI. Empower. Seal works with the systems you keep.

Seal reads your ERP, LIMS, historian and document systems where they are, and Neil works across them.

Find your systems.

Search 180 systems and instruments. Each page says how it connects and what it can read or write.

Lab instruments

If your system is not listed, Seal’s REST API and Scripts can connect it, and we can review its interfaces with you.

Each connection is scoped before it goes live.

You decide what Seal may read, whether anything is written back and which system stays the source of truth.

ConnectionScopeWrites backSource of truthFor example
Organisation libraryCaptured versions of selected recordsNoThe source systemSharePoint, SAP
Instrument exportExported results, mapped by a ScriptNoInstrument softwareEmpower, Agilent
Historian gatewayCurrent values and history windowsNoThe historianAVEVA PI, DeltaV
Provider APISelected records your edition exposesIf separately approvedAgreed when scopedMasterControl, Maximo
Seal API and ScriptsRecords in the direction you agreeIf agreedAgreed when scopedSnowflake, Power BI
Seal applicationPull requests, as change recordsStatus and approvalSeal, for approvalGitHub
Neil actionActions your account exposesEach call is approvedThe source systemVeeva Vault
Office add-inThe Office file you connectEdits you acceptYour file, saved in OfficeExcel, Word

Write-back is a separate decision, with its own mapping, review gates and audit evidence; a successful API response does not itself establish an approval. A record from outside Seal keeps its source identity, original units and version.

Neil works through the same connections, within the permissions of the person asking. In Slack and Microsoft Teams, each person connects their own identity. How each connection is qualified is set out under connected systems in the regulatory guide.

The question spans systems.
Bring the answer together.

Start with one process, connect the systems you keep and move more work into Seal when you’re ready.

What is holding up batch review?

Neil

  • Two batches. Two different follow-ups. Both remain open for review.
Batches › B-041
Lab evidence
S-018
Result
92.1%

Transfer hold

Assess the hold exception

Batches › B-044
Lab evidence
S-021
Result
Pending

Transfer hold

Obtain the QC result

QuestionNeil preparesYour team decides
What is holding up batch review?The evidence and the hold investigationQA: open items and disposition
Which batches used lot RM-118?Affected batches, results and open workThe actual exposure
What would a new transfer check affect?The check, its impact and its testsThe version, before release

Each answer is assembled from the records where they live. A change keeps the history intact: batches that ran on v04 keep it, and v05 needs release and training before it runs.

A shared ontology for the whole operation.

Identify samples, batches and materials one way across your systems. Source identities, original units and versions stay attached.

Viability
92.1%Source: 0.921 fraction
Sample
S-018Source: SMPL_018
Batch
B-041Source: 0041
Measured with
VIAB-07Method v03
Material consumed
RM-118Material lot
Executed under
MBR-014Procedure v04
The viability result belongs to sample S-018 and uses method VIAB-07 v03. The sample belongs to batch B-041, which consumed material lot RM-118 and executed under MBR-014 v04.

A point-to-point interface copies a value from one system into another. The ontology keeps what the value is about, so your team and Neil investigate across systems instead of reconciling exports. The connection guides show how source records map into Seal.

Connection guides.

Each guide takes one connection: what to collect, how it maps to Seal and the checks to run. See all connection guides.

See your systems working together.

Book a demo