API RP 17N:2009 pdf download

API RP 17N:2009 pdf download.Recommended Practice for Subsea Production System Reliability and Technical Risk Management.
3.20
reliability
The ability of an item to perform a required function, under given conditions of production, environment, and usage, for a required time interval.
3.24
system availability
The ratio of time a system or component is functional or in a functional state to the total time it is required or expected to function.
3.25
urtanty
A state of having limited knowledge where it is impossible to exactly describe the existing state or future outcome(s).
3.26
uptime
The time interval during which an item is functional.
3.27
validation
The process that substantiates whether technical data and engineering models are within the required range of accuracy, consistent with the intended application.
3.28
verification
The process that determines the extent to which a procedure, task, physical product, or model conforms to its specification.
4 Abbreviations
The assessment of technical risk should seek to identify “chang& factors which introduce uncertainty to the ability of the equipment to operate reliably in the field.
5.2.3 Identification of Scope of Work
The scope of work for any given project stage is the list of activities which will address the identified technical risks. This will usually include activities such as:
— system availability analysis to confirm that design configurations meet economic targets;
— FMECA to identify, address and if possible, design out potential failure modes;
— design reviews to expose designs at various stages to expert opinion;
— testing and analysis to develop understanding of and demonstrate potential for functionality and reliability.
All activities should:
— add value to the project,
— be consistent with the project goals and strategy.
5.3 Plan
The plan establishes the detail of how the reliability scope of work is to be accomplished.
The reliability and technical risk management plan for each project stage will cover areas such as:
— resources (people, software/hardware, etc.);
— roles and responsibilities;
— deliverables for each activity;
— schedules and milestones.
As a project proceeds, the organizations involved will change. The plan should clarify the role/responsibility of the organization within each activity, in terms of:
— specifying requirements,
— completing the work,
— verifying the work meets the requirements.
The plan should only contain what is achievable within schedule and budget constraints. If it is necessary to omit previously identified activities, this should be with clear justification and understanding of the potential consequences (of carrying unmitigated risk).
5.4 Implementing the Plan
The process of implementing the activities at each project stage will involve breaking down the plan into a series of tasks or actions.
These actions need to be tracked and closed out to ensure completion.