About Concurrent Safe State Hazards

When you create an Instrumented Function, you will define the safe state of the instrumented function, which is responsible for modifying the process in the event that the condition of the process is in an unsafe state. In other words, if a given process is approaching an unsafe condition, the instrumented function that monitors that process will change the process to a condition that is specified as the safe state for that process. For example, if the temperature reaches an unsafe level, the cooling system will be triggered to bring the temperature down to a safe state.

In some cases, if a given process is in its associated safe state at the same time as a different process, while the individual processes are in a safe state, the combination of these conditions could trigger a hazardous event. For example, assume that to reach a safe state in a Flare system, the steam valve needs to vent. Now assume that two steam valves need to vent at the same time. In this case, the Flare system can become overloaded due to both processes reaching their safe states concurrently.

In Meridium Enterprise APM, the combinations of safe states that can lead to hazardous events are referred to as concurrent safe state hazards. You can document the concurrent safe state hazards that exist for instrumented functions via the Instrumented Function record. In other words, for each instrumented function that participates in a potentially hazardous relationship, you will need to define the concurrent safe state hazard(s) for that instrumented function.

The Concurrent Safe States section of the Instrumented Function allows you to manage all the concurrent safe state hazards that exist for an instrumented function. To define concurrent safe state hazards for an instrumented function, you will need to:

Copyright © 1993-2015 Meridium, Inc. All rights reserved.