top of page

Integrating PHA LOPA Outputs into Effective SIS Engineering

We can help you pick up your PHA/LOPA which maybe been put to the side and provide the services to set you up for the safety system design phase. Standard SIS deliverables include the review of specification, confirming that the SIL levels are what they should be, and that the proof testing procedures are correctly documented to support your regular testing intervals. 


Transcript: "aeSolutions has a full suite of offerings and the safety lifecycle, from the PHA LOPA aspect in the upstream design all the way through into the detailed engineering phase. Our group SIS engineering (Safety Instrumented Systems) sits kind of right in the middle between the two, you have the PHA LOPA upstream and you've got the detailed design downstream. We take what the PHA LOPA outputs. We massage it a little bit to get it into a more meaningful list of safety functions, for example. And then we can take that through the conceptual design phase where it goes into SIL calculations and SRS's and cause and effects and gets that into a into a package that can ultimately be handed downstream into the design phase.

Everything we do here is developing standard SIS deliverables by making sure that all the specifications are correct. All the safety integrated levels are what they should be. All the proof testing procedures are correctly documented. So that our clients can have regular testing intervals with the necessary equipment that they need to be testing.

One of the things that we've seen a lot of our clients do is they'll do the PHA LOPA and then they'll take that information and they'll essentially file it away and do very little else with that. And one of the challenges that we've seen is the SIS needs to be designed against that document and so we can take that document either from an internal study or from a client and help pick it up and do the rest of the upstream engineering on it. Where we identify, what are your safety functions look like, how many sensors o you have? And get that into a more defined safety function that can ultimately be? Hand it off to the design team. The other aspects that we run into is a lot of times I'll do the front end engineering all the way through. You know, for example an SRS data sheet, but then they don't do things with it and ultimately the intention behind that is not only to use as an operating manual for your safety function, but you also want to use that as the guiding document in the design phase so that you ensure that everything that you're doing in the design. This matches what you intended it to do on the on the front end."


Want all our best content in your inbox?
Sign up now!
Sign up now!

aeSolutions sends out an email newsletter ever other month of our most popular blogs, webinar, whitepapers, and more.

bottom of page