API RP 17N-2009 pdf free download

API RP 17N-2009 pdf free download.Recommended Practice for Subsea Production System Reliability and Technical Risk Management.
3.9 failure mode The effect by which a failure is observed on the failed item [i.e. the loss of a required functionality (e.g. loss of containment)]. 3.10 fault State of an item characterized by inability to perform a required function, excluding the inability during preventive maintenance or other planned actions, or due to lack of external resources. NOTE A fault is often a result of a failure of the item itself but the state can exist without a failure. 3.11 installation hardware The system or equipment used to install subsea production hardware. 3.12 maintainability Ability of an item under given conditions of use, to be retained in, or restored to, a state in which it can perform a required function, when maintenance is performed under given conditions and using stated procedures and resources. 3.13 maintenance free operating period MFOP The time that a system can operate without a specified failure event that demands a maintenance intervention, where the failure occurrence is to a given level of probability. 3.14 maintenance record Set of data that contains all failure, fault, and maintenance information relating to an item. 3.15 package A named system, subsystem, or defined set of components considered as a single entity for the purposes of a design study or for procurement (e.g. subsea tree, control system). 3.16 process An arrangement of tasks directed towards a specific objective. 3.17 production availability The ratio of actual production to a reference (e.g. planned) production level over a specified period of time. 3.18 qualification The process of confirming, by examination and provision of evidence, that equipment meets specified requirements for the intended use. 3.19 redundancy Existence of more than one means to perform a required function (e.g. by duplicating items).
5.2 Define The initial step is to identify the project’s reliability goals and prioritize reliability and technical risk management effort within the project. This should include the following activities. 5.2.1 Goals, Strategy and Requirements It is important for the project to be clear on what it is aiming to achieve and why. This can be defined as: — the reliability performance that the project would like to achieve (goals), and/or — the reliability performance that the project must achieve in order to meet the business objectives of the project (requirements). Goals and requirements may be expressed in words (qualitative) or numerically (quantitative). The strategy is the general approach the project will take to deliver the stated goals and requirements in a way that adds value for the project. For example, the strategy may be to: — extend the life of equipment before failure (reliability strategy); — minimize the time to restore failed equipment to an operable state (maintainability strategy); — use operational mitigations, such as spare capacity, to reduce the effect of system failure (risk mitigation strategy). This RP recommends implementing a reliability and technical risk management program which combines all of the above, although the focus is on managing risks through improved design and manufacture. 5.2.2 Assessment of Technical Risk The risk assessment effort should be tailored to the level and source of technical risk in the project and the project stage being considered. The assessment of technical risk will take different forms during different stages of the project, for example: — a simple high level technical review may filter out equipment with technical uncertainty; — consequence/severity analysis can be used to identify equipment with the greatest impact on production or safety and environment; — identification of potential failure modes (or risk of failure) (e.g. by FMECA);