Skip to main content

Integration guideInstrument export

Local Files

Capture instrument outputs and records from files or network shares.

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

Local Files to SealInstrument export

Seal reads
Exported files from a site computer or network share
Writes back
No
Source of truth
The exporting software
Set up
Seal Edge and an upload Script
Neil › File intake summary
draft

Show which exported files arrived and which records they created.

Neil

  • Once the connection is configured, I’ll use the records it provides and cite each one. Anything it doesn’t supply stays listed as missing.
Reads
Exported files from a site computer or network share
Returns
  • Files received, records created and rejected files
  • Missing or unmatched information
  • Next steps for your team to review
Illustrative work with Local Files: a request to Neil, the source it reads and the draft it returns for your review.

1What’s connected.

Collect exported files from a site computer or network share with Seal Edge. An upload Script configured for your folder and export layout decides which Seal records each file creates. Test it with a representative export before enabling ongoing collection.

Connection setup and permissions

Connect through Seal Edge or a scoped integration. The equipment model, software version and available interfaces determine the connection method.

Related blueprints

2Start with the job.

Tell us what Neil needs to do and which records it needs. We’ll confirm the interface, permissions and implementation scope with your team.

Discuss this connection →

3Before it goes live.

Access and any write-back

Define which records are in scope and whose permissions apply. Whether the connection writes back at all is a separate decision, with its own mapping and approval.

Data and failure handling

Agree the field mapping, identifiers, units and source of record. Test missing or duplicate data, interrupted transfers and recovery before relying on the connection.

Verification and release

Review the configured connection for its intended use. Keep the requirements, checks and evidence with the change, and approve the release through your team’s controls.

Read the assurance detail →