This instrument failed calibration. Which batches used it during the period under investigation, and what evidence do we need to assess the impact?
Once the scoped transfer supplies the calibration record, I’ll match the instrument to its recorded uses in Seal and prepare the batch list for quality review.
Supplied calibration record and equipment-use history
Calibration impact assessment
- Batches using the instrument in the selected period
- Calibration and equipment-use references
- Missing evidence and questions for quality review
1What’s connected.
Bring ProCal calibration records into equipment checks and investigations in Seal. Match instrument identities to the equipment used in your processes, so Neil can help assess overdue calibrations and potential batch impact.
Connection setup and permissions
ProCal provides a Data Exchange Utility and ProCal Connector. We scope the connection around your installed edition, licensed tools and available exports; this is a custom integration, not a guided Seal connector.
Agree the instrument identifiers, calibration fields, transfer frequency and source timestamps before mapping records into Seal. Start with reading evidence; changes to ProCal need separate configuration.
- Provider API and integration documentation
- Connecting integrations in Seal
- API documentation
- Scripts documentation
Related blueprints
2Start with the job.
Selected instrument and calibration records supplied by your configured transfer. Confirm which dates, results, approval states and certificate references are included. Missing or stale evidence stays visible in the receiving equipment check.
3Use calibration evidence in the work.
Once the connection and equipment mappings are configured:
- Check an instrument before use
- Compare the supplied calibration due date with the planned run and flag gaps for the equipment owner.
- Assess an out-of-tolerance result
- Trace the instrument to recorded uses in Seal and prepare the batch list and evidence for quality review.
- Prepare calibration follow-up
- Collect overdue items and unresolved evidence into a work list for the metrology team.
4Connection questions
Can we connect our existing ProCalV5 installation?
We assess your version and Data Exchange or export configuration with your team. The interface and fields are confirmed before implementation; this listing does not assume a REST API or automatic access to every calibration record.
5Before 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.