<?xml version="1.0" encoding="UTF-8"?>
<BarrierProject Name="Safety Barrier Legend.xml" ManCalculationMethod="NoEffect">
	<BarrierProjectDescription>Legend
Use this diagram to produce a legend of the symbols in your barrier diagram.

In the diagram you want to make the legend for, ensure that you have enabled: menu item "Options - Save Settings Locally"
Then open this project, and it will use the settings from your other project. Make sure in this Legend project that menu item "Options - Save Settings in Project" is disabled (By default it will be enabled each time you open it) before you save the legend file if you want to maintain the feature to use the local settings (from the project you want to make the legend for. If you want a specific legend with its own settings, of course you can use "Save As" with the "Options - Save Settings in Project" enabled. 

</BarrierProjectDescription>
	<AllManagementIssues>
		<ManagementIssue Name="1st ARAMIS Item, Manpower Planning and Availability" Performance="1">
			<Description>Manpower Planning covers allocating the necessary time (or numbers) of competent people to the tasks that have to be carried out, at the moment (or within the time frame) when they should be carried out. It also covers the process of planning and allocation of tasks over time, including coverage for:
Holidays, Sick leave, Peak loads, Ensuring breaks and rest pauses, and Limiting overtime and fatigue.

Personnel Availability ensures that personnell is available for all relevant tasks in relation to the functioning and management of barriers (operations, maintenance, emergency), including: 
Operating personnel, Maintenance personnel, Inspection &amp; testing incl. general plantwalk-rounds, Supervision, and Back-up &amp; emergency crews,.</Description>
		</ManagementIssue>
		<ManagementIssue Name="2nd ARAMIS Item, Competence and Suitability" Performance="1">
			<Description>Competence covers the knowledge, skills, and abilities of first-line and/or back-up personnel for the safe execution of safety-critical tasks related to barrier functioning or management. Competence covers the cognitive aspects of behaviour, which can be learned through training, experience and practice. They include:

Job content/safety, e.g.: Plant &amp; process knowledge:
- Operating procedures, critical tasks, action alternatives, skills
- Boundary of safety operations
- Hazards, safety consequences of actions, safety priorities
- Safety responsibility/task boundaries

Inspection &amp; testing procedures:
- Fault diagnosis &amp; response
- Emergency procedures
- Maintenance diagnosis
- Safe isolation and recommissioning
- Equipment dismantling, repair, testing &amp; reassembly

Other skills:
- Communications
- Team work
- Supervision/management
- Issuing instructions

Suitability covers physical attributes that are usually more permanent characteristics of an individual, though some can be modified or compensated for over the longer term. They include: Size, strength, dexterity, Physical condition, health, Visual acuity, colour blindness, and Hearing.</Description>
		</ManagementIssue>
		<ManagementIssue Name="3rd ARAMIS Item, Commitment, Compliance and Conflict resolution" Performance="1">
			<Description>Commitment and conflict resolution are concerned with:
- Information, training and discussion on what is important and has priority
- Rapid confrontation and correction of deviations from the desired working method, state or condition
- High (publicity) profile and reward for achievements on safety
- Appraisal schemes with explicit attention to safety performance
- Recurrent active attention to safety in meetings, discussions and actions
- Procedure violations
- Keeping to the prescribed operating envelope
- Safety and production/time pressures e.g. production pressures reducing scheduled maintenance/inspection, operations which come under time pressure for implementation, reluctance to declare emergencies or shutdown plant because of loss of production
- Safety critical maintenance priority over production
- Balancing production targets, resource availability/costs and inspection and maintenance requirements via e.g. time schedules and budget setting
- Safety budget (increased/decreased)</Description>
		</ManagementIssue>
		<ManagementIssue Name="4th ARAMIS Item, Communication and Coordination " Performance="1">
			<Description>The communication and coordination concerns itself with:
- Communication channels (phone, radio, minutes, reports, etc.)
- Coordination methods (e.g. meetings, supervision)
- Communication between: 
Different persons engaged on one task as team or working in sequence, and 
Shifts at changeover
- Communication about:
Work content
Barrier/plant status
Job instructions
Priorities
Who does what, where and when
Need for action or (back-up) personnel and equipment
- Communication systems for sharing operation/maintenance hazard concerns and experience</Description>
		</ManagementIssue>
		<ManagementIssue Name="5th ARAMIS Item, Procedures, rules, and goals" Performance="1">
			<Description>The procedures, rules and goals delivery system is occupied with identifying tasks that need (detailed) written rules and procedures, and subsequently providing and promulgating these. This system also delivers output goals for tasks that do not need a detailed procedure.
Procedures and rules are specific performance criteria, which specify in detail, usually in written form, a formalised 'normative' behaviour or method for carrying out an activity (checklist, task list, action steps, plan, instruction manual, fault-finding heuristic, form to be completed, etc.).
Output goals are performance measures for an activity, which specify what the result of the activity should be, but not how the results should be achieved. They are objectives, goals or outputs.
The procedures, rules and goals delivery system concerns itself with: Coverage (i.e. all safety situations), Accuracy, Readability/usability, Size/complexity/overload or rule sets, Clarity/ambiguity, Up-to-date, Indicating priorities.</Description>
		</ManagementIssue>
		<ManagementIssue Name="6th ARAMIS Item, Hard/software purchase, build, interface, install" Performance="1">
			<Description>Management of barrier (and spares) purchase, construction, installation and adjustment deals with the management process for ensuring that the hardware/ software barriers and barrier elements in agreement with specifications are acquired, either by purchase from outside, or by construction on site, are put in place and adjusted and that the spare parts or replacements purchased and stored for the maintenance phase of their life cycle are the correct ones and are in good condition when used. The process should pay explicit attention to the human factors aspects of the interface between barrier elements and their users in the case of mixed barriers.</Description>
		</ManagementIssue>
		<ManagementIssue Name="7th ARAMIS Item, Hard/software Inspection, Maintenance, and Replacement" Performance="1">
			<Description>Management of inspection, maintenance and replacement deals with the management processes for ensuring that the specified hardware/software barriers and barrier elements are kept in an effective state. It covers all hardware and software which has a function within any barrier designed to fulfill a safety function in the plant. It forms the part of the life cycle of these barrier elements from the point where they have been installed and adjusted and are ready for use. It covers all the activities which monitor the working of the barriers, detect the (chance of) deviation from the designed working and identify the need for work to be done to restore the functioning or replace the barrier (elements) with new ones.
This process also manages small modifications which are carried out at the same time as, and under the same management as the maintenance activities. Where the modifications are of a more major type, which are (or should be) dealt with by a change management process, these are covered by the protocol on learning and change.</Description>
		</ManagementIssue>
		<ManagementIssue Name="0th ARAMIS Item, Safety Culture" Performance="0.75">
			<Description>Safety culture can be assessed by questionnaire surveys of the personnel. Safety culture addresses the following issues:
Learning and willingness to report: the employees' willingness / reluctance to report accidents and incidents, their perception of feedback from reporting and dissemination of lessons learned.
Safety prioritisation, rules and compliance covering use of and familiarity with rules and instructions; the prioritisation of safety versus productivity and ease of work; the extent to which and the circumstances under which safety procedures may be violated
 Leadership involvement and commitment concerns both the avowed involvement and commitment of management and supervisors and team leaders as well as employee perception of their commitment and involvement 
Risk and human performance limitation perception concerns management and employee awareness of hazards, risks and human error potentials (fatigue, automation etc.) relevant to their work.
Felt responsibility concerns the employee's perception of who is responsible for safety at work including felt ownership of responsibility
Trust and fairness involves management's trust in employees and, crucially, employees' trust in top management and their immediate leaders and employee perception of fairness in the workplace
Work team atmosphere and support comprises employees' perception of teamwork and the 'spirit' in their respective teams; the extent to which the team gives its members support and help; and the extent to which respondents are willing to speak up and warn each other of dangers.
Motivation, influence and involvement comprises (i) work as meaningful; (ii) own influence on work planning and execution; (iii) motivation and involvement; and (iv) feeling informed and finding work predictable</Description>
		</ManagementIssue>
		<ManagementIssue Name="A Risk analysis and selection of safety barriers" Performance="1">
			<Description>This issue covers the process of risk assessment and selection of the barriers.
Definitions and coverage:
Barrier functions and elements - 
The process emphasises that barrier functions should first be defined (prevent, protect, mitigate), followed by a choice between all possible principles and forms of barrier which could fulfil that function. Most barrier forms chosen will be combinations of hardware and software elements with behavioural elements. Some barriers may be pure hardware, either passive, in which case it requires no activation after its installation (temporarily or permanently), or with active elements, which require adjustment and activation. A number of barriers may be purely dependent on behaviour, such as evacuation, or skilled dismantling of equipment. The elements out of which the complete barriers are constructed must consist (except in the case of passive barriers) of elements which perform the functions of detection or diagnosis of the need to respond, activation of the barrier and its response. Either hardware or behaviour elements can fulfil each of the functions and these can be combined in many different ways. The company must make its choices out of these combinations.
Coverage	-
The process should cover all accident scenarios which the company wishes to control, or wishes to demonstrate to regulators that it has controlled. The steps follow the normal processes of risk assessment, but emphasise more clearly the selection and specification of barriers to control the hazards. They also emphasise that barrier selection should take account of the whole life cycle of the barrier and its elements in deciding what is likely to be the most effective choice to make. 
</Description>
		</ManagementIssue>
		<ManagementIssue Name="B Learning and management of change" Performance="1">
			<Description>This issue deals with the management processes designed to achieve continuous improvement and adaptation of barrier performance to the current best practice and to the current state of the risks in the organisation.
Definitions and coverage:
Learning -
Learning is defined as the collection of information about the performance of a barrier (element) or management process relating to barrier performance, the analysis of the performance data, its comparison with desired performance and/or good practice, the drawing of conclusions about improvements and changes which are required to bring about better performance, and the implementation throughout the organisation of the changes. Learning should be triggered by both deviations from expected or desired performance within the organisation, as by comparisons with good practice outside it.
Change management -
Change management is designed to ensure that any changes to the technical, human or organisational aspects of the design, layout, functioning, control or management of the organisation are reflected in changes to the barriers provided to control risk and/or changes to the appropriate part of the life cycle or management processes which ensure the functioning of the barriers. This requires that the organisation specify and identify what will be considered to be ‘significant changes’ requiring assessment.
Incident, accident and failure -
Incident: any deviation from expected or desired operation or performance, which, if uncorrected, would lead to damage, injury or other undesired outcome, and which is defined as relevant to be recorded for the purposes of learning.
Accident: any deviation from expected or desired operation or performance, which leads to actual damage, injury or other undesired outcome.
Failure: any deviation of a barrier (element) or management process relevant to barrier performance which results in a partial or complete loss of function of that barrier (element) or management process.
Coverage	 -
The learning and change control system covers the performance of all barriers and their elements, whether they are achieved by hardware, software or behaviour. </Description>
		</ManagementIssue>
	</AllManagementIssues>
	<AllBarrierTypes>
		<BarrierType Name="1 EXCESSIVELY CONSERVATIVE DESIGN AND MECHANICAL REDUNDANCY">
			<Description>DETECTION: Not relevant
DIAGNOSE: Not relevant
ACTION: Hardware: Resilience and redundancy withstanding physical forces
DESCRIPTION
"Excessively conservative" means that the relevant characteristics of equipment (e.g. wall thickness) are at least a factor two more than what would be required using state-of-the-art or traditional standards used for that process. 
Redundancy means that under normal conditions forces are transmitted through multiple independent paths and each path has the capacity to perform the desired 
function alone. Evaluation of redundancy must consider whether the redundant systems can be affected simultaneously by an accident or deviation (independence). Redundancy that requires an active shift to another system must be perceived as an intervention (not permanent).
EXAMPLES
Over dimensioned wall thickness, fitted with double steering cables or rods, fitted with double electrical connections. 
FAILURE MECHANISMS
Material failure or installation errors, in particular following maintenance; slow degradation; process conditions that exceed even so the material strength, in particular following changes in process conditions; simultaneous (common cause) failure of redundant systems.</Description>
			<ManagementFactors>
				<ManagementFactor Name="1 Permanent Passive (Control)_6th ARAMIS Item, Hard/software purchase, build, interface, install" Value="0.43" Performance="1" ManagementIssue="6th ARAMIS Item, Hard/software purchase, build, interface, install"/>
				<ManagementFactor Name="1 Permanent Passive (Control)_7th ARAMIS Item, Hard/software Inspection, Maintenance, and Replacement" Value="0.17" Performance="1" ManagementIssue="7th ARAMIS Item, Hard/software Inspection, Maintenance, and Replacement"/>
				<ManagementFactor Name="1 EXCESSIVELY CONSERVATIVE DESIGN AND MECHANICAL REDUNDANCY_A Risk analysis and selection of safety barriers" Value="0.1" Performance="1" ManagementIssue="A Risk analysis and selection of safety barriers"/>
				<ManagementFactor Name="1 EXCESSIVELY CONSERVATIVE DESIGN AND MECHANICAL REDUNDANCY_B Learning and management of change" Value="0.05" Performance="1" ManagementIssue="B Learning and management of change"/>
			</ManagementFactors>
			<TypeSettings>
				<TypeOptions.Height Value="0"/><TypeOptions.Width Value="0"/><TypeOptions.VerSeparation Value="0"/><TypeOptions.GateSeparation Value="0"/><TypeOptions.HorSeparation Value="0"/><TypeOptions.Radius Value="0"/><TypeOptions.Brush.Color Value="12632256"/><TypeOptions.Brush.Style Value="bsSolid"/><TypeOptions.Pen.Color Value="0"/><TypeOptions.Pen.Width Value="1"/><TypeOptions.Pen.Style Value="psSolid"/><TypeOptions.Pen.Mode Value="pmCopy"/><TypeOptions.Font.Color Value="-16777208"/><TypeOptions.Font.Size Value="8"/><TypeOptions.Font.Name Value="Tahoma"/><TypeOptions.Font.Style Value="NormalFont "/></TypeSettings>
		</BarrierType>
		<BarrierType Name="2 PERMANENT PASSIVE BARRIER">
			<Description>DETECTION: Not relevant
DIAGNOSE: Not relevant
ACTION: Hardware: Strength or capacity to handle the deviation or threat.
DESCRIPTION
Passive Barriers are elements in a system that are constantly present (i.e. they do not need to be activated), and that are installed with the only reason to avoid or limit hazardous situations (i.e. the installation can in principle operate without those barriers). 
EXAMPLES:
Tank bunds, dyke, fire protection, drainage sump, fence, lightning conductors, collision barrier, edge protection, hardware protection against body parts entering hazard zones, edge protection.
FAILURE MECHANISMS: 
Lacking strength or capacity, construction error, slow degradation, human error causing flaws (e.g. open rain-water drains in tank bunds), removed (e.g. protection) or not installed or not re-installed after maintenance.</Description>
			<ManagementFactors>
				<ManagementFactor Name="2 PERMANENT PASSIVE BARRIER_6th ARAMIS Item, Hard/software purchase, build, interface, install" Value="0.43" Performance="1" ManagementIssue="6th ARAMIS Item, Hard/software purchase, build, interface, install"/>
				<ManagementFactor Name="2 PERMANENT PASSIVE BARRIER_7th ARAMIS Item, Hard/software Inspection, Maintenance, and Replacement" Value="0.17" Performance="1" ManagementIssue="7th ARAMIS Item, Hard/software Inspection, Maintenance, and Replacement"/>
				<ManagementFactor Name="2 PERMANENT PASSIVE BARRIER_A Risk analysis and selection of safety barriers" Value="0.05" Performance="1" ManagementIssue="A Risk analysis and selection of safety barriers"/>
				<ManagementFactor Name="2 PERMANENT PASSIVE BARRIER_B Learning and management of change" Value="0.1" Performance="1" ManagementIssue="B Learning and management of change"/>
			</ManagementFactors>
			<TypeSettings>
				<TypeOptions.Height Value="0"/><TypeOptions.Width Value="0"/><TypeOptions.VerSeparation Value="0"/><TypeOptions.GateSeparation Value="0"/><TypeOptions.HorSeparation Value="0"/><TypeOptions.Radius Value="0"/><TypeOptions.Brush.Color Value="12632256"/><TypeOptions.Brush.Style Value="bsSolid"/><TypeOptions.Pen.Color Value="0"/><TypeOptions.Pen.Width Value="1"/><TypeOptions.Pen.Style Value="psSolid"/><TypeOptions.Pen.Mode Value="pmCopy"/><TypeOptions.Font.Color Value="-16777208"/><TypeOptions.Font.Size Value="8"/><TypeOptions.Font.Name Value="Tahoma"/><TypeOptions.Font.Style Value="NormalFont "/></TypeSettings>
		</BarrierType>
		<BarrierType Name="3 PERMANENT BARRIER: ENERGIZED">
			<Description>DETECTION: Not relevant
DIAGNOSE: Not relevant
ACTION: Hardware: Capacity to perform the barrier function
DESCRIPTION	
These barriers are constantly present, but need an energy source to work. If activation is required upon certain conditions, consider classification as temporary barrier.
EXAMPLES	
Ventilation, active corrosion prevention, circulation of material, continuous inerting of systems, pilot flames, continuous addition of inhibitors. 
FAILURE MECHANISMS	
Not turned on/not activated, lacking capacity, lacking energy supply or material (gas) supply.
</Description>
			<ManagementFactors>
				<ManagementFactor Name="3 PERMANENT BARRIER: ENERGIZED_4th ARAMIS Item, Communication and Coordination " Value="0.13" Performance="1" ManagementIssue="4th ARAMIS Item, Communication and Coordination "/>
				<ManagementFactor Name="3 PERMANENT BARRIER: ENERGIZED_5th ARAMIS Item, Procedures, rules, and goals" Value="0.43" Performance="1" ManagementIssue="5th ARAMIS Item, Procedures, rules, and goals"/>
				<ManagementFactor Name="3 PERMANENT BARRIER: ENERGIZED_6th ARAMIS Item, Hard/software purchase, build, interface, install" Value="0.17" Performance="1" ManagementIssue="6th ARAMIS Item, Hard/software purchase, build, interface, install"/>
				<ManagementFactor Name="3 PERMANENT BARRIER: ENERGIZED_A Risk analysis and selection of safety barriers" Value="0.05" Performance="1" ManagementIssue="A Risk analysis and selection of safety barriers"/>
				<ManagementFactor Name="3 PERMANENT BARRIER: ENERGIZED_B Learning and management of change" Value="0.1" Performance="1" ManagementIssue="B Learning and management of change"/>
			</ManagementFactors>
			<TypeSettings>
				<TypeOptions.Height Value="0"/><TypeOptions.Width Value="0"/><TypeOptions.VerSeparation Value="0"/><TypeOptions.GateSeparation Value="0"/><TypeOptions.HorSeparation Value="0"/><TypeOptions.Radius Value="0"/><TypeOptions.Brush.Color Value="12632256"/><TypeOptions.Brush.Style Value="bsSolid"/><TypeOptions.Pen.Color Value="0"/><TypeOptions.Pen.Width Value="1"/><TypeOptions.Pen.Style Value="psSolid"/><TypeOptions.Pen.Mode Value="pmCopy"/><TypeOptions.Font.Color Value="-16777208"/><TypeOptions.Font.Size Value="8"/><TypeOptions.Font.Name Value="Tahoma"/><TypeOptions.Font.Style Value="NormalFont "/></TypeSettings>
		</BarrierType>
		<BarrierType Name="4 TEMPORARY BARRIER (PASSIVE OR ENERGIZED)">
			<Description>DETECTION: The effect does not depend on the detection of a deviation, but the barrier need to be present or working.
DIAGNOSE: Not relevant
ACTION: Hardware: Strength or capacity to handle the deviation or threat.
DESCRIPTION	
Barriers temporary put in place or temporary used, depending on a temporary situation (such as maintenance or repair works) or within a specific time spans or locations. Installation and use depends to a high degree on routines, procedures and rules.
EXAMPLES	
Barriers around repair work, blind flanges over open pipes, spades in pipes, inhibitors in substances, personal protection equipment (PPE: e.g. hard hats, safety goggles, safety clothing, safety gloves), clothes and shoes to avoid static electricity, earthing of tanks during (un)loading
FAILURE MECHANISMS	
Not put in place, not donned (PPE), not appropriate for the hazard (chemicals, heat, pressure, wrongly mounted.
</Description>
			<ManagementFactors>
				<ManagementFactor Name="4 TEMPORARY BARRIER (PASSIVE OR ENERGIZED)_1st ARAMIS Item, Manpower Planning and Availability" Value="0.29" Performance="1" ManagementIssue="1st ARAMIS Item, Manpower Planning and Availability"/>
				<ManagementFactor Name="4 TEMPORARY BARRIER (PASSIVE OR ENERGIZED)_2nd ARAMIS Item, Competence and Suitability" Value="0.18" Performance="1" ManagementIssue="2nd ARAMIS Item, Competence and Suitability"/>
				<ManagementFactor Name="4 TEMPORARY BARRIER (PASSIVE OR ENERGIZED)_4th ARAMIS Item, Communication and Coordination " Value="0.13" Performance="1" ManagementIssue="4th ARAMIS Item, Communication and Coordination "/>
				<ManagementFactor Name="4 TEMPORARY BARRIER (PASSIVE OR ENERGIZED)_5th ARAMIS Item, Procedures, rules, and goals" Value="0.09" Performance="1" ManagementIssue="5th ARAMIS Item, Procedures, rules, and goals"/>
				<ManagementFactor Name="4 TEMPORARY BARRIER (PASSIVE OR ENERGIZED)_6th ARAMIS Item, Hard/software purchase, build, interface, install" Value="0.22" Performance="1" ManagementIssue="6th ARAMIS Item, Hard/software purchase, build, interface, install"/>
				<ManagementFactor Name="4 TEMPORARY BARRIER (PASSIVE OR ENERGIZED)_7th ARAMIS Item, Hard/software Inspection, Maintenance, and Replacement" Value="0.08" Performance="1" ManagementIssue="7th ARAMIS Item, Hard/software Inspection, Maintenance, and Replacement"/>
				<ManagementFactor Name="4 TEMPORARY BARRIER (PASSIVE OR ENERGIZED)_0th ARAMIS Item, Safety Culture" Value="0.04" Performance="0.75" ManagementIssue="0th ARAMIS Item, Safety Culture"/>
				<ManagementFactor Name="4 TEMPORARY BARRIER (PASSIVE OR ENERGIZED)_A Risk analysis and selection of safety barriers" Value="0.03" Performance="1" ManagementIssue="A Risk analysis and selection of safety barriers"/>
				<ManagementFactor Name="4 TEMPORARY BARRIER (PASSIVE OR ENERGIZED)_B Learning and management of change" Value="0.03" Performance="1" ManagementIssue="B Learning and management of change"/>
			</ManagementFactors>
			<TypeSettings>
				<TypeOptions.Height Value="0"/><TypeOptions.Width Value="0"/><TypeOptions.VerSeparation Value="0"/><TypeOptions.GateSeparation Value="0"/><TypeOptions.HorSeparation Value="0"/><TypeOptions.Radius Value="0"/><TypeOptions.Brush.Color Value="12632256"/><TypeOptions.Brush.Style Value="bsSolid"/><TypeOptions.Pen.Color Value="0"/><TypeOptions.Pen.Width Value="1"/><TypeOptions.Pen.Style Value="psSolid"/><TypeOptions.Pen.Mode Value="pmCopy"/><TypeOptions.Font.Color Value="-16777208"/><TypeOptions.Font.Size Value="8"/><TypeOptions.Font.Name Value="Tahoma"/><TypeOptions.Font.Style Value="NormalFont "/></TypeSettings>
		</BarrierType>
		<BarrierType Name="5 RESPECT SAFETY ZONES AND WARNINGS">
			<Description>DETECTION: Detection relates to warnings and signs, not to detection of deviations (passive barrier as regards to deviations).
DIAGNOSE: Not relevant
ACTION: Behaviour: To respect markings and warning signs: refrain from entering danger zones and refrain from manipulating marked parts of installations.
DESCRIPTION	
Symbols, markings and warning signs (passive, i.e. not alarms) request to perform or refrain from certain behaviour. Implies in general refraining from certain actions (not touching, not operating, not entering not smoking). Respecting danger zones prevents people from getting hurt when deviations occur (mitigating barrier), Awareness of valves closing off dangerous substances may prevent erroneous operation. 
Note that the barrier consists of the behaviour itself, not the signalling.
Note that marking components such as valves in order to support correct operation is part of a management obligation to provide a sufficiently good human-machine interface and work place rather than a safety barrier.
EXAMPLES	
Not entering danger zones (e.g. at cranes or robot stations, open containers, rotating machinery) , refrain from operating valves, avoid contact with hot parts, respecting smoking prohibitions, obeying speed limits.
FAILURE MECHANISMS	
Not respecting signs and markings, lacking signs, unclear signs, and conflicts with work tasks.
</Description>
			<ManagementFactors>
				<ManagementFactor Name="5 Activated Barrier - Hardware on demand_ARAMIS Item 6 Hard/software purchase, build, interface, install" Value="0.5" Performance="0" ManagementIssue="6th ARAMIS Item, Hard/software purchase, build, interface, install"/>
				<ManagementFactor Name="5 Activated Barrier - Hardware on demand_ARAMIS Item 7 Hard/software Inspection, Maintenance, and Replacement" Value="0.5" Performance="0" ManagementIssue="7th ARAMIS Item, Hard/software Inspection, Maintenance, and Replacement"/>
				<ManagementFactor Name="5 RESPECT SAFETY ZONES AND WARNINGS_3rd ARAMIS Item, Commitment, Compliance and Conflict resolution" Value="0.1" Performance="1" ManagementIssue="3rd ARAMIS Item, Commitment, Compliance and Conflict resolution"/>
				<ManagementFactor Name="5 RESPECT SAFETY ZONES AND WARNINGS_5th ARAMIS Item, Procedures, rules, and goals" Value="0.09" Performance="1" ManagementIssue="5th ARAMIS Item, Procedures, rules, and goals"/>
				<ManagementFactor Name="5 RESPECT SAFETY ZONES AND WARNINGS_0th ARAMIS Item, Safety Culture" Value="0.08" Performance="0.75" ManagementIssue="0th ARAMIS Item, Safety Culture"/>
				<ManagementFactor Name="5 RESPECT SAFETY ZONES AND WARNINGS_A Risk analysis and selection of safety barriers" Value="0.1" Performance="1" ManagementIssue="A Risk analysis and selection of safety barriers"/>
				<ManagementFactor Name="5 RESPECT SAFETY ZONES AND WARNINGS_B Learning and management of change" Value="0.05" Performance="1" ManagementIssue="B Learning and management of change"/>
			</ManagementFactors>
			<TypeSettings>
				<TypeOptions.Height Value="0"/><TypeOptions.Width Value="0"/><TypeOptions.VerSeparation Value="0"/><TypeOptions.GateSeparation Value="0"/><TypeOptions.HorSeparation Value="0"/><TypeOptions.Radius Value="0"/><TypeOptions.Brush.Color Value="12632256"/><TypeOptions.Brush.Style Value="bsSolid"/><TypeOptions.Pen.Color Value="0"/><TypeOptions.Pen.Width Value="1"/><TypeOptions.Pen.Style Value="psSolid"/><TypeOptions.Pen.Mode Value="pmCopy"/><TypeOptions.Font.Color Value="-16777208"/><TypeOptions.Font.Size Value="8"/><TypeOptions.Font.Name Value="Tahoma"/><TypeOptions.Font.Style Value="NormalFont "/></TypeSettings>
		</BarrierType>
		<BarrierType Name="6 PREVENTIVE PROCEDURAL ACTION">
			<Description>DETECTION: Detection concerns attention to situations where the preventive action is required according to procedure, the deviation or threat is not detected.
DIAGNOSE: Not relevant
ACTION: Behaviour or hardware: To follow rules and procedures which apply to the situation at hand or (activate) automated sequencing through steps in a process.
DESCRIPTION	
The activity is performed as part of a procedure for some operation or step in a process in order to prevent dangerous situations, even when the dangerous situation not necessarily is present.
There may be overlap with “Temporary barrier” (e.g. making a ground connection and leaving it in place during the (un)loading), but this barrier focuses on actions performed prior to the hazardous activity, i.e. detached in time. 
EXAMPLES	
Venting of closed spaces before entering, venting/emptying hoses before detachment, earthing tankers before (un)loading to prevent static electricity, inerting vessels or reactors before taking into use. 
FAILURE MECHANISMS	
Not executing the action, incomplete or faulty execution. 
</Description>
			<ManagementFactors>
				<ManagementFactor Name="6 PREVENTIVE PROCEDURAL ACTION_1st ARAMIS Item, Manpower Planning and Availability" Value="0.29" Performance="1" ManagementIssue="1st ARAMIS Item, Manpower Planning and Availability"/>
				<ManagementFactor Name="6 PREVENTIVE PROCEDURAL ACTION_2nd ARAMIS Item, Competence and Suitability" Value="0.36" Performance="1" ManagementIssue="2nd ARAMIS Item, Competence and Suitability"/>
				<ManagementFactor Name="6 PREVENTIVE PROCEDURAL ACTION_3rd ARAMIS Item, Commitment, Compliance and Conflict resolution" Value="0.2" Performance="1" ManagementIssue="3rd ARAMIS Item, Commitment, Compliance and Conflict resolution"/>
				<ManagementFactor Name="6 PREVENTIVE PROCEDURAL ACTION_4th ARAMIS Item, Communication and Coordination " Value="0.25" Performance="1" ManagementIssue="4th ARAMIS Item, Communication and Coordination "/>
				<ManagementFactor Name="6 PREVENTIVE PROCEDURAL ACTION_5th ARAMIS Item, Procedures, rules, and goals" Value="0.18" Performance="1" ManagementIssue="5th ARAMIS Item, Procedures, rules, and goals"/>
				<ManagementFactor Name="6 PREVENTIVE PROCEDURAL ACTION_0th ARAMIS Item, Safety Culture" Value="0.08" Performance="0.75" ManagementIssue="0th ARAMIS Item, Safety Culture"/>
				<ManagementFactor Name="6 PREVENTIVE PROCEDURAL ACTION_A Risk analysis and selection of safety barriers" Value="0.1" Performance="1" ManagementIssue="A Risk analysis and selection of safety barriers"/>
				<ManagementFactor Name="6 PREVENTIVE PROCEDURAL ACTION_B Learning and management of change" Value="0.05" Performance="1" ManagementIssue="B Learning and management of change"/>
			</ManagementFactors>
			<TypeSettings>
				<TypeOptions.Height Value="0"/><TypeOptions.Width Value="0"/><TypeOptions.VerSeparation Value="0"/><TypeOptions.GateSeparation Value="0"/><TypeOptions.HorSeparation Value="0"/><TypeOptions.Radius Value="0"/><TypeOptions.Brush.Color Value="12632256"/><TypeOptions.Brush.Style Value="bsSolid"/><TypeOptions.Pen.Color Value="0"/><TypeOptions.Pen.Width Value="1"/><TypeOptions.Pen.Style Value="psSolid"/><TypeOptions.Pen.Mode Value="pmCopy"/><TypeOptions.Font.Color Value="-16777208"/><TypeOptions.Font.Size Value="8"/><TypeOptions.Font.Name Value="Tahoma"/><TypeOptions.Font.Style Value="NormalFont "/></TypeSettings>
		</BarrierType>
		<BarrierType Name="7 HARDWARE INTERVENTION">
			<Description>DETECTION: Hardware 
DIAGNOSE: Hardware
ACTION: Hardware 
DESCRIPTION	
Barriers that by means of direct mechanical-physical principles both detect the deviation and perform the necessary action.
EXAMPLES	
Pressure relief valves, bursting disks, sprinkler heads, explosion relief hatches 
FAILURE MECHANISMS	
Insufficient capacity (too small, too slow), wrong set point, blocked (including piping towards the barrier), stuck.
</Description>
			<ManagementFactors>
				<ManagementFactor Name="7 HARDWARE INTERVENTION_6th ARAMIS Item, Hard/software purchase, build, interface, install" Value="0.43" Performance="1" ManagementIssue="6th ARAMIS Item, Hard/software purchase, build, interface, install"/>
				<ManagementFactor Name="7 HARDWARE INTERVENTION_7th ARAMIS Item, Hard/software Inspection, Maintenance, and Replacement" Value="0.17" Performance="1" ManagementIssue="7th ARAMIS Item, Hard/software Inspection, Maintenance, and Replacement"/>
				<ManagementFactor Name="7 HARDWARE INTERVENTION_A Risk analysis and selection of safety barriers" Value="0.1" Performance="1" ManagementIssue="A Risk analysis and selection of safety barriers"/>
				<ManagementFactor Name="7 HARDWARE INTERVENTION_B Learning and management of change" Value="0.05" Performance="1" ManagementIssue="B Learning and management of change"/>
			</ManagementFactors>
			<TypeSettings>
				<TypeOptions.Height Value="0"/><TypeOptions.Width Value="0"/><TypeOptions.VerSeparation Value="0"/><TypeOptions.GateSeparation Value="0"/><TypeOptions.HorSeparation Value="0"/><TypeOptions.Radius Value="0"/><TypeOptions.Brush.Color Value="12632256"/><TypeOptions.Brush.Style Value="bsSolid"/><TypeOptions.Pen.Color Value="0"/><TypeOptions.Pen.Width Value="1"/><TypeOptions.Pen.Style Value="psSolid"/><TypeOptions.Pen.Mode Value="pmCopy"/><TypeOptions.Font.Color Value="-16777208"/><TypeOptions.Font.Size Value="8"/><TypeOptions.Font.Name Value="Tahoma"/><TypeOptions.Font.Style Value="NormalFont "/></TypeSettings>
		</BarrierType>
		<BarrierType Name="8 AUTOMATED INTERVENTION/SAFETY INSTRUMENTED SYSTEM (SIS)">
			<Description>DETECTION: Hardware 
DIAGNOSE: Hardware/software
ACTION: Hardware 
DESCRIPTION	
Automated intervention by a system of electrical/electronic/programmable electronic (E/E/PE) components, that on the basis of input from sensors is able to determine what intervention needs to be made, and activates actuators (like powered valves) to perform this intervention.
In order for an automated system to be considered to be an independent safety barrier (independent protection layer) the components that make up the automated system should not be part of the basic process control system (BPCS).
EXAMPLES	
Emergency shutdown system (ESD), emergency blowdown system, 
FAILURE MECHANISMS	
Component failure, software failure, design failure, common cause failure</Description>
			<ManagementFactors>
				<ManagementFactor Name="8 AUTOMATED INTERVENTION/SAFETY INSTRUMENTED SYSTEM (SIS)_6th ARAMIS Item, Hard/software purchase, build, interface, install" Value="0.43" Performance="1" ManagementIssue="6th ARAMIS Item, Hard/software purchase, build, interface, install"/>
				<ManagementFactor Name="8 AUTOMATED INTERVENTION/SAFETY INSTRUMENTED SYSTEM (SIS)_7th ARAMIS Item, Hard/software Inspection, Maintenance, and Replacement" Value="0.17" Performance="1" ManagementIssue="7th ARAMIS Item, Hard/software Inspection, Maintenance, and Replacement"/>
				<ManagementFactor Name="8 AUTOMATED INTERVENTION/SAFETY INSTRUMENTED SYSTEM (SIS)_A Risk analysis and selection of safety barriers" Value="0.1" Performance="1" ManagementIssue="A Risk analysis and selection of safety barriers"/>
				<ManagementFactor Name="8 AUTOMATED INTERVENTION/SAFETY INSTRUMENTED SYSTEM (SIS)_B Learning and management of change" Value="0.05" Performance="1" ManagementIssue="B Learning and management of change"/>
			</ManagementFactors>
			<TypeSettings>
				<TypeOptions.Height Value="0"/><TypeOptions.Width Value="0"/><TypeOptions.VerSeparation Value="0"/><TypeOptions.GateSeparation Value="0"/><TypeOptions.HorSeparation Value="0"/><TypeOptions.Radius Value="0"/><TypeOptions.Brush.Color Value="12632256"/><TypeOptions.Brush.Style Value="bsSolid"/><TypeOptions.Pen.Color Value="0"/><TypeOptions.Pen.Width Value="1"/><TypeOptions.Pen.Style Value="psSolid"/><TypeOptions.Pen.Mode Value="pmCopy"/><TypeOptions.Font.Color Value="-16777208"/><TypeOptions.Font.Size Value="8"/><TypeOptions.Font.Name Value="Tahoma"/><TypeOptions.Font.Style Value="NormalFont "/></TypeSettings>
		</BarrierType>
		<BarrierType Name="9 HUMAN INTERVENTION FOLLOWING ALARM">
			<Description>DETECTION: Hardware/software 
DIAGNOSE: Behaviour according to clear procedures ("Skill &amp; Rule based")
ACTION: Behaviour according to clear procedures ("Skill &amp; Rule based") (may include activation of powered components)
DESCRIPTION	
Actions of operators in response to clear instrument signals or alarms. There will be clear instructions describing the actions that are required to respond to the each of the alarms. The sensors, transmitters and actuators are part of the barrier system. 
In order for the alarm system to be considered to be an independent safety barrier (independent protection layer) the components that make up the alarm system should not be part of the basic process control system (BPCS).
EXAMPLES	
Manual shutdown or adjustment, evacuation, calling fire brigade on alarm, close/open (correct) valve
FAILURE MECHANISMS	
Failure of sensors, transmitters or software, flaws in instructions, wrong intervention, operator not present.
</Description>
			<ManagementFactors>
				<ManagementFactor Name="9 HUMAN INTERVENTION FOLLOWING ALARM_1st ARAMIS Item, Manpower Planning and Availability" Value="0.58" Performance="1" ManagementIssue="1st ARAMIS Item, Manpower Planning and Availability"/>
				<ManagementFactor Name="9 HUMAN INTERVENTION FOLLOWING ALARM_2nd ARAMIS Item, Competence and Suitability" Value="0.36" Performance="1" ManagementIssue="2nd ARAMIS Item, Competence and Suitability"/>
				<ManagementFactor Name="9 HUMAN INTERVENTION FOLLOWING ALARM_3rd ARAMIS Item, Commitment, Compliance and Conflict resolution" Value="0.2" Performance="1" ManagementIssue="3rd ARAMIS Item, Commitment, Compliance and Conflict resolution"/>
				<ManagementFactor Name="9 HUMAN INTERVENTION FOLLOWING ALARM_5th ARAMIS Item, Procedures, rules, and goals" Value="0.09" Performance="1" ManagementIssue="5th ARAMIS Item, Procedures, rules, and goals"/>
				<ManagementFactor Name="9 HUMAN INTERVENTION FOLLOWING ALARM_6th ARAMIS Item, Hard/software purchase, build, interface, install" Value="0.22" Performance="1" ManagementIssue="6th ARAMIS Item, Hard/software purchase, build, interface, install"/>
				<ManagementFactor Name="9 HUMAN INTERVENTION FOLLOWING ALARM_7th ARAMIS Item, Hard/software Inspection, Maintenance, and Replacement" Value="0.08" Performance="1" ManagementIssue="7th ARAMIS Item, Hard/software Inspection, Maintenance, and Replacement"/>
				<ManagementFactor Name="9 HUMAN INTERVENTION FOLLOWING ALARM_0th ARAMIS Item, Safety Culture" Value="0.08" Performance="0.75" ManagementIssue="0th ARAMIS Item, Safety Culture"/>
				<ManagementFactor Name="9 HUMAN INTERVENTION FOLLOWING ALARM_A Risk analysis and selection of safety barriers" Value="0.05" Performance="1" ManagementIssue="A Risk analysis and selection of safety barriers"/>
				<ManagementFactor Name="9 HUMAN INTERVENTION FOLLOWING ALARM_B Learning and management of change" Value="0.1" Performance="1" ManagementIssue="B Learning and management of change"/>
			</ManagementFactors>
			<TypeSettings>
				<TypeOptions.Height Value="0"/><TypeOptions.Width Value="0"/><TypeOptions.VerSeparation Value="0"/><TypeOptions.GateSeparation Value="0"/><TypeOptions.HorSeparation Value="0"/><TypeOptions.Radius Value="0"/><TypeOptions.Brush.Color Value="12632256"/><TypeOptions.Brush.Style Value="bsSolid"/><TypeOptions.Pen.Color Value="0"/><TypeOptions.Pen.Width Value="1"/><TypeOptions.Pen.Style Value="psSolid"/><TypeOptions.Pen.Mode Value="pmCopy"/><TypeOptions.Font.Color Value="-16777208"/><TypeOptions.Font.Size Value="8"/><TypeOptions.Font.Name Value="Tahoma"/><TypeOptions.Font.Style Value="NormalFont "/></TypeSettings>
		</BarrierType>
		<BarrierType Name="10 SITUATIONAL HUMAN INTERVENTION (PROCEDURAL)">
			<Description>DETECTION: Human  observation and interpretation
DIAGNOSE: Behaviour according to clear procedures ("Skill &amp; Rule based")
ACTION: Behaviour according to clear procedures ("Skill &amp; Rule based")
DESCRIPTION	
The hazardous situation is detected by human observation of (a combination) factors in accordance with clear rules and procedures. There are no clear alarms, the hazardous situation needs to be derived from a combination of inputs. Instrument failure can both be considered to be a part of the initiating deviation (a dangerous failure in the sense that a deviation does not show up) or as part of the barrier failure. 
This barrier also includes actions of supervisors supervising other operator’s tasks.
EXAMPLES	
To adjust hardware set-points, to warn others for action or evacuation, to disconnect tanks, hoses or pipes, to avoid escalation protection equipment with foam or fire-fighting water.
FAILURE MECHANISMS	
Failure of instruments or software, flaws in instruction, lack of attention, wrong intervention.
</Description>
			<ManagementFactors>
				<ManagementFactor Name="10 SITUATIONAL HUMAN INTERVENTION (PROCEDURAL)_1st ARAMIS Item, Manpower Planning and Availability" Value="0.29" Performance="1" ManagementIssue="1st ARAMIS Item, Manpower Planning and Availability"/>
				<ManagementFactor Name="10 SITUATIONAL HUMAN INTERVENTION (PROCEDURAL)_2nd ARAMIS Item, Competence and Suitability" Value="0.36" Performance="1" ManagementIssue="2nd ARAMIS Item, Competence and Suitability"/>
				<ManagementFactor Name="10 SITUATIONAL HUMAN INTERVENTION (PROCEDURAL)_3rd ARAMIS Item, Commitment, Compliance and Conflict resolution" Value="0.2" Performance="1" ManagementIssue="3rd ARAMIS Item, Commitment, Compliance and Conflict resolution"/>
				<ManagementFactor Name="10 SITUATIONAL HUMAN INTERVENTION (PROCEDURAL)_4th ARAMIS Item, Communication and Coordination " Value="0.25" Performance="1" ManagementIssue="4th ARAMIS Item, Communication and Coordination "/>
				<ManagementFactor Name="10 SITUATIONAL HUMAN INTERVENTION (PROCEDURAL)_5th ARAMIS Item, Procedures, rules, and goals" Value="0.09" Performance="1" ManagementIssue="5th ARAMIS Item, Procedures, rules, and goals"/>
				<ManagementFactor Name="10 SITUATIONAL HUMAN INTERVENTION (PROCEDURAL)_0th ARAMIS Item, Safety Culture" Value="0.15" Performance="0.75" ManagementIssue="0th ARAMIS Item, Safety Culture"/>
				<ManagementFactor Name="10 SITUATIONAL HUMAN INTERVENTION (PROCEDURAL)_A Risk analysis and selection of safety barriers" Value="0.1" Performance="1" ManagementIssue="A Risk analysis and selection of safety barriers"/>
				<ManagementFactor Name="10 SITUATIONAL HUMAN INTERVENTION (PROCEDURAL)_B Learning and management of change" Value="0.05" Performance="1" ManagementIssue="B Learning and management of change"/>
			</ManagementFactors>
			<TypeSettings>
				<TypeOptions.Height Value="0"/><TypeOptions.Width Value="0"/><TypeOptions.VerSeparation Value="0"/><TypeOptions.GateSeparation Value="0"/><TypeOptions.HorSeparation Value="0"/><TypeOptions.Radius Value="0"/><TypeOptions.Brush.Color Value="12632256"/><TypeOptions.Brush.Style Value="bsSolid"/><TypeOptions.Pen.Color Value="0"/><TypeOptions.Pen.Width Value="1"/><TypeOptions.Pen.Style Value="psSolid"/><TypeOptions.Pen.Mode Value="pmCopy"/><TypeOptions.Font.Color Value="-16777208"/><TypeOptions.Font.Size Value="8"/><TypeOptions.Font.Name Value="Tahoma"/><TypeOptions.Font.Style Value="NormalFont "/></TypeSettings>
		</BarrierType>
		<BarrierType Name="11 KNOWLEDGE-BASED HUMAN INTERVENTION (AD HOC)">
			<Description>DETECTION: Human  observation and interpretation.
DIAGNOSE: Behaviour on the basis of knowledge and reasoning ("Knowledge based")
ACTION: Behaviour
DESCRIPTION	
Intervention that requires a continuous knowledge-based assessment of the situation (e.g. during a rescue operation) and/or requires detailed analysis in cases where no procedures or rules apply.
This barrier type is provided for sake of completeness. Apart from use as a mitigating barrier (emergency response) at the far right-hand side of the diagram or bow-tie, prevention of foreseeable should be dealt with by procedures, i.e. “Rule and Skill-based” barriers.
EXAMPLES	
Fire-fighting, emergency response, to (re)gain control over a complex system (such as a nuclear reactor) and take it to a safe condition.
FAILURE MECHANISMS	
Wrong assessment, inadequate intervention, intervention too late, too early.
</Description>
			<ManagementFactors>
				<ManagementFactor Name="11 KNOWLEDGE-BASED HUMAN INTERVANTION (AD HOC)_1st ARAMIS Item, Manpower Planning and Availability" Value="0.87" Performance="1" ManagementIssue="1st ARAMIS Item, Manpower Planning and Availability"/>
				<ManagementFactor Name="11 KNOWLEDGE-BASED HUMAN INTERVANTION (AD HOC)_2nd ARAMIS Item, Competence and Suitability" Value="1" Performance="1" ManagementIssue="2nd ARAMIS Item, Competence and Suitability"/>
				<ManagementFactor Name="11 KNOWLEDGE-BASED HUMAN INTERVANTION (AD HOC)_3rd ARAMIS Item, Commitment, Compliance and Conflict resolution" Value="0.17" Performance="1" ManagementIssue="3rd ARAMIS Item, Commitment, Compliance and Conflict resolution"/>
				<ManagementFactor Name="11 KNOWLEDGE-BASED HUMAN INTERVANTION (AD HOC)_4th ARAMIS Item, Communication and Coordination " Value="0.83" Performance="1" ManagementIssue="4th ARAMIS Item, Communication and Coordination "/>
				<ManagementFactor Name="11 KNOWLEDGE-BASED HUMAN INTERVANTION (AD HOC)_5th ARAMIS Item, Procedures, rules, and goals" Value="0.09" Performance="1" ManagementIssue="5th ARAMIS Item, Procedures, rules, and goals"/>
				<ManagementFactor Name="11 KNOWLEDGE-BASED HUMAN INTERVANTION (AD HOC)_0th ARAMIS Item, Safety Culture" Value="0.13" Performance="0.75" ManagementIssue="0th ARAMIS Item, Safety Culture"/>
				<ManagementFactor Name="11 KNOWLEDGE-BASED HUMAN INTERVANTION (AD HOC)_A Risk analysis and selection of safety barriers" Value="0.01" Performance="1" ManagementIssue="A Risk analysis and selection of safety barriers"/>
				<ManagementFactor Name="11 KNOWLEDGE-BASED HUMAN INTERVANTION (AD HOC)_B Learning and management of change" Value="0.05" Performance="1" ManagementIssue="B Learning and management of change"/>
			</ManagementFactors>
			<TypeSettings>
				<TypeOptions.Height Value="0"/><TypeOptions.Width Value="0"/><TypeOptions.VerSeparation Value="0"/><TypeOptions.GateSeparation Value="0"/><TypeOptions.HorSeparation Value="0"/><TypeOptions.Radius Value="0"/><TypeOptions.Brush.Color Value="12632256"/><TypeOptions.Brush.Style Value="bsSolid"/><TypeOptions.Pen.Color Value="0"/><TypeOptions.Pen.Width Value="1"/><TypeOptions.Pen.Style Value="psSolid"/><TypeOptions.Pen.Mode Value="pmCopy"/><TypeOptions.Font.Color Value="-16777208"/><TypeOptions.Font.Size Value="8"/><TypeOptions.Font.Name Value="Tahoma"/><TypeOptions.Font.Style Value="NormalFont "/></TypeSettings>
		</BarrierType>
	</AllBarrierTypes>
	<AllGenericBarriers/>
	<AllConditions>
		<Condition Name="Input to OR 2" ExpectedFreq="0" Visible="False" EventOrCondition="Undetermined" Severity="" TypeOf="Initial">
			<Description></Description>
		</Condition>
		<Condition Name="Input to OR" ExpectedFreq="0" Visible="False" EventOrCondition="Undetermined" Severity="" TypeOf="Initial">
			<Description></Description>
		</Condition>
		<Condition Name="Output from OR" ExpectedFreq="0" Visible="False" EventOrCondition="Condition" Severity="" TypeOf="Consequence">
			<Description></Description>
		</Condition>
		<Condition Name="Input to AND" ExpectedFreq="0" Visible="False" EventOrCondition="Undetermined" Severity="" TypeOf="Initial">
			<Description></Description>
		</Condition>
		<Condition Name="Input to AND 2" ExpectedFreq="0" Visible="False" EventOrCondition="Undetermined" Severity="" TypeOf="Initial">
			<Description></Description>
		</Condition>
		<Condition Name="Output of AND" ExpectedFreq="0" Visible="False" EventOrCondition="Condition" Severity="" TypeOf="Consequence">
			<Description></Description>
		</Condition>
		<Condition Name="Initial condition or Initiating event" ExpectedFreq="0" Visible="True" EventOrCondition="Undetermined" Severity="" TypeOf="Initial">
			<Description>SEE THE PROJECT DESCRIPTION</Description>
		</Condition>
		<Condition Name="Intermediate event or situation" ExpectedFreq="0" Visible="True" EventOrCondition="Undetermined" Severity="" TypeOf="Intermediate">
			<Description>SEE THE PROJECT DESCRIPTION</Description>
		</Condition>
		<Condition Name="input to barrier" ExpectedFreq="0" Visible="False" EventOrCondition="Undetermined" Severity="" TypeOf="Initial">
			<Description></Description>
		</Condition>
		<Condition Name="Consequence" ExpectedFreq="0" Visible="True" EventOrCondition="Undetermined" Severity="" TypeOf="Consequence">
			<Description>SEE THE PROJECT DESCRIPTION</Description>
		</Condition>
		<Condition Name="Invisible input to barrier" ExpectedFreq="0" Visible="False" EventOrCondition="Undetermined" Severity="" TypeOf="Initial">
			<Description>SEE THE PROJECT DESCRIPTION</Description>
		</Condition>
		<Condition Name="Condition on success of the barrier (optional)" ExpectedFreq="0" Visible="True" EventOrCondition="Undetermined" Severity="" TypeOf="Intermediate">
			<Description>SEE THE PROJECT DESCRIPTION</Description>
		</Condition>
		<Condition Name="Condition on failure of the barrier" ExpectedFreq="0" Visible="True" EventOrCondition="Undetermined" Severity="" TypeOf="Intermediate">
			<Description>SEE THE PROJECT DESCRIPTION</Description>
		</Condition>
		<Condition Name="Input to event tree branch" ExpectedFreq="0" Visible="False" EventOrCondition="Undetermined" Severity="" TypeOf="Initial">
			<Description></Description>
		</Condition>
		<Condition Name="event tree outcome 1" ExpectedFreq="0" Visible="False" EventOrCondition="Undetermined" Severity="" TypeOf="Consequence">
			<Description></Description>
		</Condition>
		<Condition Name="Outcome 2" ExpectedFreq="0" Visible="False" EventOrCondition="Undetermined" Severity="" TypeOf="Consequence">
			<Description></Description>
		</Condition>
	</AllConditions>
	<AllCommonElements>
		<CommonElement Name="Driver's action to engage emergency brake" PFD="0">
			<Description></Description>
		</CommonElement>
		<CommonElement Name="Emergency brake" PFD="0">
			<Description></Description>
		</CommonElement>
		<CommonElement Name="MTB functioning" PFD="0">
			<Description></Description>
		</CommonElement>
		<CommonElement Name="MTB obtaining sufficient adhesion/friction" PFD="0">
			<Description></Description>
		</CommonElement>
		<CommonElement Name="Wrong speed indication to ATC and to engine driver" PFD="0">
			<Description>This is NOT a reason to fail for the WSP, but it expresses the dependenc between proper working WSP, manual intervention by the driver, and proper engagement of the ATC</Description>
		</CommonElement>
		<CommonElement Name="WSP system Common Cause" PFD="0">
			<Description></Description>
		</CommonElement>
	</AllCommonElements>
	<BarrierDiagrams>
		<BarrierDiagram Name="Legend">
			<Description>Legend</Description>
			<BarrierGraphSize UpperLeftX="-47" UpperLeftY="-41" LowerRightX="473" LowerRightY="626"/>
			<DiagramBarriers>
				<Barrier Name="Barrier" BarrierType="1 EXCESSIVELY CONSERVATIVE DESIGN AND MECHANICAL REDUNDANCY" ManagementFactorType="Default" PFD="0">
					<Description>SEE THE PROJECT DESCRIPTION</Description>
					<AbsPos X="83" Y="89"/>
					<Links/>
					<DemandCondition Name="input to barrier"/>
				</Barrier>
				<Gate Name="OR gate" TypeOf="OR" Visible="True">
					<Description>SEE THE PROJECT DESCRIPTION</Description>
					<AbsPos X="303" Y="229"/>
					<OutputCondition Name="Output from OR"/>
					<InputConditions>
						<ConditionReference Name="Input to OR"/><ConditionReference Name="Input to OR 2"/></InputConditions>
				</Gate>
				<Gate Name="AND Gate" TypeOf="AND" Visible="True">
					<Description>SEE THE PROJECT DESCRIPTION</Description>
					<AbsPos X="90" Y="229"/>
					<OutputCondition Name="Output of AND"/>
					<InputConditions>
						<ConditionReference Name="Input to AND"/><ConditionReference Name="Input to AND 2"/></InputConditions>
				</Gate>
				<Gate Name="init gate" TypeOf="OR" Visible="False">
					<Description></Description>
					<AbsPos X="143" Y="549"/>
					<InputConditions>
						<ConditionReference Name="Initial condition or Initiating event"/></InputConditions>
					<OutputCondition Name="Intermediate event or situation"/>
				</Gate>
				<Gate Name="Inter out" TypeOf="OR" Visible="False">
					<Description></Description>
					<AbsPos X="293" Y="549"/>
					<InputConditions>
						<ConditionReference Name="Intermediate event or situation"/></InputConditions>
					<OutputCondition Name="Consequence"/>
				</Gate>
				<Barrier Name="Barrier with success and failure conditions" BarrierType="1 EXCESSIVELY CONSERVATIVE DESIGN AND MECHANICAL REDUNDANCY" ManagementFactorType="Default" PFD="0">
					<Description></Description>
					<AbsPos X="210" Y="89"/>
					<DemandCondition Name="Invisible input to barrier"/>
					<ConditionOnFailure Name="Condition on failure of the barrier"/>
					<ConditionOnSuccess Name="Condition on success of the barrier (optional)"/>
					<Links/>
				</Barrier>
				<Gate Name="success out gate" TypeOf="OR" Visible="False">
					<Description></Description>
					<AbsPos X="380" Y="16"/>
					<InputConditions>
						<ConditionReference Name="Condition on success of the barrier (optional)"/></InputConditions>
				</Gate>
				<Gate Name="Failure output gate" TypeOf="OR" Visible="False">
					<Description></Description>
					<AbsPos X="380" Y="89"/>
					<InputConditions>
						<ConditionReference Name="Condition on failure of the barrier"/></InputConditions>
				</Gate>
				<EventBranch Name="Event tree branch" VisibleName="True" HideVisibility="False" FormatProcent="False">
					<Description></Description>
					<AbsPos X="163" Y="429"/>
					<InputCondition Name="Input to event tree branch"/>
					<OutputSets>
						<OutputSet ConditionName="event tree outcome 1" Text="Alternative 1" Probability="0.25" NodeOffSet="0"/><OutputSet ConditionName="Outcome 2" Text="Alternative 2" Probability="0.75" NodeOffSet="0"/></OutputSets>
					<Links/>
				</EventBranch>
			</DiagramBarriers>
			<InitialConditions>
				<ConditionReference Name="Input to OR 2"><AbsPos X="256" Y="249"/></ConditionReference><ConditionReference Name="Input to OR"><AbsPos X="256" Y="209"/></ConditionReference><ConditionReference Name="Input to AND"><AbsPos X="43" Y="209"/></ConditionReference><ConditionReference Name="Input to AND 2"><AbsPos X="43" Y="249"/></ConditionReference><ConditionReference Name="Initial condition or Initiating event"><AbsPos X="43" Y="549"/></ConditionReference><ConditionReference Name="input to barrier"><AbsPos X="46" Y="89"/></ConditionReference><ConditionReference Name="Invisible input to barrier"><AbsPos X="173" Y="89"/></ConditionReference><ConditionReference Name="Input to event tree branch"><AbsPos X="126" Y="429"/></ConditionReference></InitialConditions>
			<IntermediateConditions>
				<ConditionReference Name="Intermediate event or situation"><AbsPos X="223" Y="549"/></ConditionReference><ConditionReference Name="Condition on success of the barrier (optional)"><AbsPos X="310" Y="16"/></ConditionReference><ConditionReference Name="Condition on failure of the barrier"><AbsPos X="310" Y="89"/></ConditionReference></IntermediateConditions>
			<Consequences>
				<ConditionReference Name="Output from OR"><AbsPos X="350" Y="229"/></ConditionReference><ConditionReference Name="Output of AND"><AbsPos X="137" Y="229"/></ConditionReference><ConditionReference Name="Consequence"><AbsPos X="383" Y="549"/></ConditionReference><ConditionReference Name="event tree outcome 1"><AbsPos X="193" Y="429"/></ConditionReference><ConditionReference Name="Outcome 2"><AbsPos X="193" Y="359"/></ConditionReference></Consequences>
		</BarrierDiagram>
	</BarrierDiagrams>
	<AllMeasures/>
	<ProjectSettings>
		<Version Value="1.1.2824"/><KeepOptionsProject Value="False"/></ProjectSettings>
</BarrierProject>
