Connect your systems.Put your knowledge to work.

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; the review stays in the system you agree.

A record that originates outside Seal keeps its source identity, original units and version. An organisation library opens the original with the reader’s own permissions in that system, and a copy supports the work in Seal without replacing the source system’s complete history.

Neil works through the same connections, within the permissions of the person asking. A question about a batch can draw on its ERP, LIMS and MES records, with each fact traced to its source. In Slack and Microsoft Teams, each person connects their own identity, so Neil follows their Seal permissions there too.

How each connection is qualified, from service-account access to data freshness and write-back, is set out under connected systems in the regulatory guide.

Each answer is assembled from the records where they live. A material trace follows lot RM-118 into B-041 and B-044, with their lab evidence and open reviews; B-045 is planned with RM-119 and is outside it.

A change keeps the history intact. B-041 and B-044 executed on v04 and keep it, with their open reviews. B-045, still planned on v04, is the candidate for v05, which needs release and training before it runs.

A point-to-point interface copies a value from one system into another. The ontology keeps what the value is about: the 92.1% viability belongs to sample S-018, measured with method VIAB-07 v03, from batch B-041, which consumed material lot RM-118 and ran under MBR-014 v04.

That context lets your team and Neil investigate across systems instead of reconciling exports. The connection guides show how source records map into Seal.

CC-019 follows a 52-minute post-mix hold against the 45-minute limit. It proposes an elapsed-time check and an exception route at transfer, with verification at 44, 45 and 46 minutes and for a missing timestamp. The limit stays at 45 minutes, and the original batch disposition is a separate review.

In line with the EU’s draft GMP Annex 22 on AI, Neil is not used in GMP execution. It helps set up configuration, which your team verifies and releases under change control. See how Neil fits Annex 22 and a process evolve with AI.