Refinery Safety Instrumented Systems (SIS) Designer

Refinery Safety Instrumented Systems (SIS) Designer MCP Connector for Claude

A+

Design and validate safety instrumented systems (SIS) following IEC 61511 standards.

4 tools Official Updated Oct 1, 2026 Official Vinkius Partner

This MCP server provides specialized tools for refinery safety engineering. It allows AI agents to perform critical safety calculations including calculate_sil_requirement to determine target risk reduction, evaluate_voting_logic for hardware architecture, calculate_proof_test_interval for maintenance scheduling, and analyze_sif_reliability to validate if a design meets its safety targets. All calculations adhere to IEC 61511 methodologies for Safety Instrumented Functions (SIF).

iec-61511silsafety-instrumented-systemsrefineryreliability-engineering

4 tools expose this connector's capabilities to your AI agent.

calculate_proof_test_interval

Determine the safe interval between mandatory system tests

calculate_sil_requirement

Determine the target SIL level required for a specific process hazard

evaluate_voting_logic

Determine the appropriate hardware architecture (voting) for a SIF

analyze_sif_reliability

Assess whether a proposed SIF design meets the necessary safety targets

See how to talk to your AI agent using Refinery Safety Instrumented Systems (SIS) Designer.

What is the required SIL if the risk reduction factor needed is 150 and the current risk is 0.1?

The required target SIL is SIL 2.

Calculate the proof test interval for a configuration with a PFD of 0.001 and a component failure rate of 0.0001.

The recommended proof test interval is 1000 days, with a maximum safe interval of 1200 days.

Is a 1oo2 configuration with two sensors having a failure rate of 0.002 compliant for SIL 2?

Yes, the design is compliant with the target SIL 2.

Yes, all calculations for SIL, voting logic, and proof test intervals are based on IEC 61511 methodologies.

Related Connectors

Edison Experimentation Prover

Edison Experimentation Prover MCP

1 tools Official

A team chose paper filing because 'best practice.' No pilot. No alternatives tested. 8 months later, 14,000 submissions/day — 47 hours behind on retrieval. Emergency migration under pressure. Cost: 3x the estimate, 6 weeks frozen. Edison tested 3,000+ filament materials before carbonized bamboo — he did not pick the 'obvious choice.' This tool forces experimentation: test alternatives with measured criteria, iterate beyond the first solution, build the ecosystem, prove viability under real conditions, and document dead ends.

A+ View details →
Delivery Integrity Prover

Delivery Integrity Prover MCP

1 tools Official

Forces AI agents to reflect on task execution, matching prompt requirements to actual changes, verifying logs, and declaring gaps before claiming completion.

A+ View details →
Task Completion Enforcer Prover

Task Completion Enforcer Prover MCP

1 tools Official

An AI was asked to build 5 API endpoints, write tests, and update documentation. It built 3 endpoints, left TODO comments in the tests, never touched the documentation, and declared 'Done! Let me know if you need anything else.' The user spent 40 minutes finding the gaps. This happens every single day, on every LLM, in every coding session. This tool forces five completion axes: requirement extraction, completion evidence, gap identification, continuation execution, and final verification against the original request.

A+ View details →
Critical Thinking Prover

Critical Thinking Prover MCP

2 tools Official

AI agents accept premises without questioning, analyze from one perspective, cherry-pick evidence, ignore consequences, and present uncertainty as certainty. This tool forces rigor: surface assumptions, apply competing frameworks, weigh counterevidence, trace ripple effects, bound confidence.

A+ View details →