Skip to main content

Manufacturing systems integrations

Use Tulip table rows and Ignition gateway data in batch reviews and investigations, with each system keeping its own record.

Illustration of a seal beside a laptop showing a data table and an evidence binder linked by a red thread.

What these systems hold.

Shop-floor systems hold what happens on the line: Tulip apps store what operators record in tables, and an Ignition gateway exposes data from its installed modules.

A batch record must document each significant step, with dates, equipment, in-process results and the people who did and checked the work (21 CFR 211.188). The quality unit reviews those records before a batch is released, and any unexplained discrepancy is thoroughly investigated (21 CFR 211.192). Shop-floor data helps only when it can be matched to the batch and step it describes.

What Seal reads and writes back.

Tulip is an organisation library: Seal reads selected rows from one table with an API token scoped to tables:read, and never writes to Tulip. Table rows carry no app completions, signatures or audit trails, so a status column is not evidence that a step was signed. Ignition is scoped against the gateway’s OpenAPI specification: Seal reads approved read-only routes, and the connection grants no control of equipment.

Seal
  1. TulipSource of truth

    Reads Captured versions of selected records

  2. IgnitionSource of truth agreed when scoped

    Reads Selected records your edition exposes

2 connections

Blueprints that use these records.

Start with one source.

Tell us what Neil needs to do and where the records live. We’ll scope the connection with your team.

Book a demo