Skip to the content

Fit for Use Safety Requirements Specification

Are you using your SRS documentation to make your company safer on a daily basis?

It was difficult to get our safety requirements specification up to ISA-84 / IEC 61511 standards. Now, our plant has changed and so have the standards. We just don’t have the staff to maintain the data and use the information as needed.

- Controls Technical Lead

The Building Blocks

One of the largest challenges regarding a safety requirements specification (SRS) is that the information comes from so many different technical teams and resides in disparate locations/applications. Therefore, after start-up, it is only a matter of when the data becomes unsynced with reality.

A significant amount of SRS data is driven by the process hazard analysis (PHA) and/or layer of protection analysis. Over time, these studies are revalidated. Another substantial data driver is the safety integrity level (SIL) calculation that also references data about the instrumentation incorporated. Again, devices fail, data evolves, and your SRS is out dated within a blink of an eye.

To stay on top of your requirements, you need to centralize and synchronize your data such that each attribute lives in one location only. Look to our Real World Model to make safety simple.

 

Is your SRS fit for use on a daily basis?

Real World Model

aeSolutions has developed a patented data model that enables the seamless transfer from one process safety activity to the next. aeShield® enables users to keep their requirements synchronized and easily available to make better business decisions on a regular basis.

With resources continuing to get leaner and meaner, aeShield promotes templatization of safety instrumented functions (SIF) as well as equipment under control (EUC). This functionality allows companies to have their most SIS knowledgeable resources focus on building and maintaining best in class templates. With templates, project engineers can simply replace tags and modify process variables as opposed to writing subjective documentation that takes time to interpret.

Now companies can reduce the time to generate documentation, drive consistency across their assets, and ensure functional safety based on industry standards. With your SRS centralized, you can now focus on operations while bad actors can be flagged as inconsistencies from your documentation. As you drive towards big data, IIoT, and digitalization, ask yourself…. “Why don’t we use technology to support our process safety needs?”