The solution can be installed in multiple instances on R-Tech servers or on servers of the client’s specification. This means that there can be multiple instances running in parallel (e.g. training and real production instances).
An example of an Saas-oriented agreement is shown below:
===================================================================================
Software as a Service Agreement (SaaS)
between
(“Client”)
Contact Client: xxxx
and
Steinbeis Advanced Risk Technologies GmbH, Willi-Bleicher-Straße 19, 70174 Stuttgart, GERMANY
Reg.: Stuttgart HRB 725454 (“Consultant”)
Contact Consultant:xxxx
1 Scope of the agreement and delivery
This SaaS Agreement covers:
a. The purchase of the iRiS-Software as a service as described in details in Annex 2 (the „Software“)
b. Customized modules meeting the Client’s needs (see Annex 1).
c. Four one-week trainings for up to Client's administrators/trainers will be conducted following the testing of the Software at Client's premises (the “Training”).
2 Terms of delivery/schedule
The Software will be delivered as per tentative Time plan below. The total duration of the Agreement related to the customization and maintenance of the purchased Software covers the period of 18 months. Any changes and/or modifications will be discussed and mutually agreed in writing, based on the discussions during the project meetings.
3 Acceptance procedure for the software
Acceptance and receipt of the delivery shall be performed by the Project Managers of the Client and the Consultant, by signing the Records of performed delivery/service, within 15 days of the successful implementation of the Software at the Client premises, at the conclusion of the 6 month period foreseen by this offer. The acceptance procedure should use the standard Consultant forms. The liability of the consultant is limited to the re-work of all jointly recognized defects.
4 Implementation of the Software
The Software will be made functional and tested at the Client’s premises. Responding the Client’s request the installation of the software will be cloud-based, at the cloud platform chosen by the Consultant (see the details below). The Consultants personnel will be deployed in South Africa as needed to discuss, align and implement the time plan or any measures/actions for Client-specific requirements. The kick-off meeting will be planned as telephone conference/video conference.
During the initial 6 month period, the Software will be deployed on the Consultants servers. This will ensure quick modification/implementation of any Client-specific requirements, as well as corrections and improvements. Following the 6 month period, the Software may be installed on Client or cloud-based servers, at Client request/preference.
5 Use of the Software
The number of Client users accessing the software is unlimited (Client employees as users, only). The Client may use the system to input data, analyze, load, display, print and reproduce views obtained from the Software and distribute them at his/her will. The ownership of the input data and the software results is exclusive to the Client. Please refer to item 9 for further information.
6 Duration of Agreement
The duration of the agreement is 18 months, staring on March 31, 2017, and not restricted geographically as long as the provisions of item 8, 9 and 10 are met and applied. The stipulations related to the ownership of IPR and the restrictions (item 10) apply without any limitation on time.
7 Client responsibility at delivery/implementation
During the time foreseen for this project, it is required to have one dedicated Client representative to support the Consultant’s implementation team to ensure the Client’s fulfillment of requirements for a successful implementation of the software (e.g. ensuring quality of data that has to be imported into the Software Database).
8 Maintenance of the Software
For the duration of this agreement, the Consultant will correct all defects and possible issues found and implement the improvements agreed by both parties. Possible prolongation is subject to subsequent agreements.
9 Further development and configuration of the Software
The Consultant agrees to:
a) Customize its existing Software (iRiS) to meet the Client’s requirements. Ownership of IPR related to the base version of the Software remains with the Consultant
b) Client’s access to further joint development/modification the Software. Ownership of IPR related to modifications of the base Software to Client requirements (the Client-module), and any further joint developments will be the subject of a separate Joint Venture Agreement, as stated below
c) Allow an unlimited number of the Client’s employees to use the Software (also for, e.g. internal/external consulting; the use of the software by users not in the direct employ of the Client is explicitly forbidden).
A respective joint IPR (Intellectual Property Rights)/Joint Venture Agreement between the Client and the Consultant will be prepared to specify the foreground IPR (joint ownership) for any joint development in the software and will include the options such as a Memorandum of Understanding (MoU) or Joint Venture. Without the IPR agreement, the above mentioned items (b) and (c) are not allowed.
10 Restrictions
The Client shall not:
· Disclose any relevant information (e.g. software documentation or training handouts) to third parties (e.g. other consultants of the Client, or similar)
· give third parties access rights for the use of the software
· contravene the general rules of software licensing
Any exceptions must be based on separate agreements, concluded in writing and signed by the Client and the Consultant.
11 Skill Development & Localization
The Consultant will engage a local South African student/trainee and an Client EIT and involve and train them in this proposed project. A SD&L report will be prepared by the Consultant to present involvement of the local trainee and the fulfillment of the SD&L activities.
12 General Terms and Conditions
For any issues not specified or covered by this Agreement, the Steinbeis/EU-VRi Terms and Conditions in Annex 1 apply.
By signing, both parties agree to implement this agreement in good faith.
The Client
| | | |
| Place, Date | | Name |
| As witness: | | |
| | | |
| Place, Date | | Name |
| | | |
| Place, Date | | Name |
The Consultant
| | | |
| Place, Date | | Name |
| As witness: | | |
| | | |
| Place, Date | | Name |
| | | |
| Place, Date | | Name |
Annex 1: Terms and Conditions
Annex 2: Software Specification
Annex 1 Standard Terms and Conditions
Terms and Conditions
of
Steinbeis Advanced Risk Technologies / EU-VRi
1. Applicability
(1) These standard terms and conditions shall apply to all contracts between StC and its Clients in respect of services (Leistungen), in so far as not otherwise explicitly agreed upon in writing.
(2) These standard terms and conditions shall only apply, if the Client is a merchant and the contract is made within his trade business, or if the Client is a legal person or a trust under Public Law in the meaning of § 310 para. (1) Sentence 1 BGB (German Civil Code).
(3) The standard terms and conditions of StC shall apply exclusively. Contrary or deviating terms of the other party shall only be binding if and to the extent that StC explicitly consents to their validity in writing. The standard terms and conditions of StC apply, even if StC fulfills the order of the Client without reservation in the knowledge of contrary or deviating terms of the Client. Deviating agreements apply only to a particular agreement and not to future agreements, unless otherwise explicitly agreed upon in writing.
(4) The standard terms and conditions shall also apply to all future agreements between StC and its Clients for services (Leistungen).
2. Scope of orders
(1) The services (Leistungen) of StC will be provided in any one case within the scope determined in the offer which remains open until the conclusion of the contract as services (Dienstleistungen) and/or project-services (Werkleistungen) in accordance with the applicable statutory requirements unless otherwise provided in these standard terms and conditions. StC provides services (Dienstleistungen) (consultation and support of the Client) at its own responsibility. The Client is, however, himself responsible for the results desired and achieved by him. In the case of project-services, StC is responsible for the results to be achieved as well as the management, control, and observation of the provision of the service.
(2) StC and the Client are each authorized to apply in writing for modifications to the agreed upon scope of services. StC and/or the Client shall examine the possibility of implementing this modification after service of the application therefore. The result of this examination shall be communicated to the other party in writing without delay. StC is authorized to invoice its costs to the ordering party, in so far as the ordering party's application for modification requires a comprehensive and costly examination. The contractual adjustments necessary for such an examination and/or for a modification to the agreed upon scope of services shall be set forth in a supplementary agreement.
3. Fulfillment of orders
(1) Orders shall be fulfilled observing the current state of science and technology.
(2) Only StC is authorized to direct its employees.
(3) StC is authorized to obtain the services of third parties for the fulfillment of orders. StC alone, however, remains directly obligated to the Client.
4. Duties of the Client
(1) The Client shall provide StC in sufficient time before the fulfillment of the order, without charge, all information, materials, devices, documents and things, plans, etc., necessary for the fulfillment of the order, and shall do so, if necessary, at its own cost.
(2) In so far as StC carries out its duties at the location of the Client, the Client shall provide the personnel of StC, or of the third parties mandated by StC access to all space, installations (hardware, software, networks, etc.) and other instrumentalities, during the usual business hours and within operational rules of access without cost, which is ordinarily necessary for StC to provide the service. If need be, the Client will obtain functional work stations (Arbeitsplätze), at no cost to StC, for the employees of StC or for third parties mandated by StC.
(3) The Client will furthermore participate in anyway necessary in the fulfillment of the order.
(4) If the Client does not or does not timely fulfill his obligations under paras. (1) - (3) and if this leads to delays and/or additional work, the agreed upon time frame and/or the agreed upon remuneration shall increase accordingly.
5. Remuneration and payment times
(1) The services and project-services will be invoiced at the unit price or on a time-and-materials basis as set forth in the offer after completion and/or acceptance of the services (Leistungen), unless another form of invoice and payment is agreed upon in the offer. In the case of services (Dienstleistungen) and project-services on a time-and-materials basis, the accruing hours worked and travel time shall be invoiced at the applicable hourly rates and the used materials at the prices applicable at the time of the service (Leistung). Other costs, especially commuting, food, and lodging, will be additionally invoiced. Estimated prices for services (Dienstleistungen) and project-services on a time-and-materials basis contained in the offer are non-binding.
(2) Value-added tax shall be invoiced separately at the applicable value-added tax rate.
(3) Invoices are payable upon receipt and in full. Unless otherwise agreed, the Client shall be in default of payment, if invoices are not paid within 30 days after the date of invoice.
(4) In case of default, interest shall be payable at the rate of 8% above the base rate of the European Central Bank. The right to claim further damages shall not be excluded.
(5) Multiple Clients are jointly liable.
(6) The Clients can only set off non-appealable or unchallenged counterclaims or counterclaims recognized by StC.
6. Acceptance
(1) Project-services shall be accepted within 15 days by the Client as soon as StC has demonstrated compliance with the agreed-upon description of services (Leistungsbeschreibung). Immaterial deviations do not authorize the ordering party to refuse acceptance. The obligation to cure defects within the scope of liability for warranties remains unaffected thereby.
(2) Confirmation of compliance with the agreed upon description of services shall be prepared by both parties by the mutual execution of a protocol of acceptance.
(3) Placing the result of the project (des Werkes) in operation and/or the productive use of the project or of parts of the project shall be deemed to be an acceptance.
7. Warranties in the case of project-services
(1) StC warrants that project-services are performed free from defects of material or of title. In particular the project-services performed are in accordance with the agreed-upon description of services (Leistungsbeschreibung) and with the agreed-upon scope of services (Leistungsumfang).
(2) In case of defects of the project-services, StC shall be liable as follows:
a) At the discretion of StC, StC shall cure the defects or perform new project-services.
b) In the case of failure to cure within a reasonable time, the Client may at his own choice reduce the payment or, insofar as the value or usability of the project should be substantially reduced, demand rescission of the contract, provided that claims for further damages remain unaffected hereof.
c) In the case of defects of material or of title, the Client shall notify StC immediately hereof in writing.
(3) The limitation period for warranty claims shall be twelve months. In case the legal provisions in § 438 para. (1) No. 2, § 479 para. (1) or § 634a para. (1) No. 2 BGB (German Civil Code) provide for longer limitation periods, these shall prevail.
(4) Statements in documentation, prospectuses, project descriptions, etc. do not constitute warranties or guarantees. Warranties or guarantees require the explicit written confirmation of StC in any case.
(5) Apparent errors such as typographical errors, calculation errors, defects of form, etc., which are contained in a report, expert opinion, or other professional utterance of employees of StC may be corrected by StC at any time.
8. Liability
(1) The limitations on liability of para. (1) do not apply, where a liability is mandatory under legal provisions, e.g. under the German Product Liability Act (Produkthaftungsgesetz), in case of intentional or negligent actions, in case of damages to life, body or health of persons and in the case of breach of material contractual obligations. In the case of breach of essential contractual obligations, the liability for damages shall be limited to the contract-typical and foreseeable amount and shall be subject to the limitation period applicable for warranties under it. 7. para. (3) above, unless in the case of intentional or grossly negligent actions or in the case of damages to life, body or health of persons. The aforementioned regulations shall not imply a change of the burden of proof at the expense of the Client.
(2) StC shall be liable in the case of project-services for the damages of the Client caused by delay, if a firmly agreed-upon time for the complete fulfillment of performance is exceeded for reasons of StC. The damages amount to be paid shall be limited, on the merits, to the proved damages of the Client and, in amount, to 0.5% for every accomplished week of delay, totaling however not more than 5% of the total payment for that part of the service not timely completed. The Client shall be obliged, upon the request of StC, to declare within a reasonable time, whether he rescinds the contract because of the delay of the project-services and/or claims damages instead of performance or requests continued performance of the services.
(4) In so far as the liability of StC is limited, this shall also apply to the employees of StC and to any third parties mandated by it.
(5) The Client shall notify StC in writing of any damages for which StC may be responsible, and give StC the opportunity to examine the damages and their cause.
9. Confidentiality
(1) The parties shall not make economic, technical and other information and knowledge, either made available by the respective other party in the preparation and execution of orders or otherwise having come into the knowledge of the parties, available to third parties
(2) The obligation in accordance with para. (1) does not apply to information and knowledge, which
- was known to StC before the issuance of the mandate,
- StC legally received from third parties,
- was generally known upon the issuance of the mandate,
- became known subsequently without a breach of the obligation in accordance with para. (1)
(3) The obligation under para. (1) applies to both parties after the expiration of the mandate for another two years.
10. Data Protection
The parties shall process or use personal data of the respective other party only for contractually agreed upon purposes under the observation of statutory requirements.
11. Inventions
(1) Inventions, which are jointly made by the employees of StC and the Client during the execution of a mandate as well as protected privileges issued therefore stand at the joint disposal of the parties. Prior inventions brought in, and/or made solely by any one party will remain in the ownership of the respective party.
(2) Inventions which are made during the fulfillment of an order by employees of StC as well as protected privileges issued therefore belong to StC. Inventions which are made during the execution of a mandate by the employees of the Client as well as protected privileges issued therefore belong to the Client.
(3) The grant of licenses to inventions in the sense of paras. (1) and (2) and to the protected privileges issued therefore requires a special written agreement.
12. Work product
(1) The transfer of ownership (Eigentum) and use rights in work product of any kind achieved within the framework of the scope of services (Leistungsumfang) agreed upon in the offer and notified to the Client, as, for example, documentation, reports, planning documents, evaluations, drawings, program materials, etc., requires a special written agreement.
(2) StC carries no responsibility if technical documentation provided to it by the Client or within the Client's mandate breaches existing copyrights, industrial property rights, or other rights of third parties. The Client is alone liable if rights of third parties are violated by the fulfillment of its mandate. The Client shall indemnify StC against all claims of third parties for any such violation upon demand. The value of this liability is capped at the value of this contract. Item no. 8 herein remains unaffected.
13. Termination
(1) Contracts can be terminated at any time on 30 days' notice to the end of a calendar month.
(2) The termination of contracts for good cause is possible at any time.
(3) In those cases of termination under paras. (1) and (2) the Client shall pay the remuneration minus that part of the remuneration for the agreed-upon scope of services, which was saved by the termination. StC has an additional claim to payment for the services and costs which accrue in connection with the termination, also in respect of third parties.
(4) If the termination occurs for reasons to be attributed to StC, then StC has a claim to payment for the services (Leistungsumfang) brought up to that time only in so far as they can be used by the Client.
(5) Termination requires the written form in any case.
14. Issuance of documents and things,
retention right
(1) The Client may demand the return by StC of the documents and things issued to it after expiration of a mandate. StC may refuse this return, until all of its claims under the agreement have been satisfied, in so far as such retention of particular documents and things in light of the facts and circumstances, especially in terms of the relative immateriality of the amounts owed, does not violate public policy.
(2) StC can produce and retain duplicates or copies of documents which it returns to the ordering party.
15. General provisions
(1) Agreements are concluded in written form. Side agreements are only effective if they have been confirmed in writing by StC.
(2) The transfer of rights and duties under the agreements by the Client to third parties, excepting direct divisions and/or subsidiaries of the Client, requires the prior written consent of StC.
(3) Jurisdictional venue is Stuttgart.
Annex 2: Software Specification
ClientRBI Software
Risk-Based Inspection (RBI), Remaining life assessment, inspection planning materials data management …
The Software’s purpose is to support engineers dealing with life management of primarily equipment under pressure in power plants. It should support the users in all steps of their work: data and documentation management, engineering analysis, decision-making and preparation of reports.
The Software is based on the Client RBI procedure, while referring to recognized methodologies (USA, EU), widely used nowadays by the leading industrial companies, and the use of the state-of-the-art methods and software tools (all intra/extranet based). The solution helps users to understand the basic problems and concepts, and to apply these efficiently in the shortest possible time and, in most of the cases without having to replace their existing system.
Software structure
The Software incorporates the Client RBI procedure and references the state-of-the-art US and EU standards in the field of RBI, including prEN 16991 (formerly CEN CWA15740 RIMAP) and API 580/581. It is comprised of different modules, depending on the field of use. These include:
· Client RBI Procedure (Level 1, Level 2 and Level 3.1)
o Baseline risk assessment tools, based on the Client RBI procedure, with database storing plant (component) and inspection data, RBI analyses, user management
o Level 3.1 risk modelling based on Client RBI procedure
· RBI Dashboard
o Assessment overviews
o Report templates
o Pre/post-outage risk (performance) review
· API 581 Modules
o Qualitative unit/system-based approach (QLTA)
o Component-based qualitative (Level 1) assessment
o Component-based semi-quantitative (Level 2) and Financial Risk (Level 3) assessment
Software Requirements
Client-specific requirements resulting from the Gap Analysis, Pilot Phase 14 stations involved in the Rollout Phase can be implemented into the Software. They will be specified and agreed upon separately. A detailed time plan defining the development and implementation of additional and Client-specific modules will be developed contingent upon agreement between Client and R-Tech.
In addition, the Software is compatible with prEN 16991, the new EN standard (“ex-RIMAP”) and The Client procedure for Risk Based Inspection.
RBI Functionality
RBI Analysis Levels
The solution covers all levels, from screening analysis, over more detailed semi-quantitative and quantitative analysis, to the full-scale quantitative RBI analysis of equipment items.
Equipment Types for Analysis
All types of equipment items as covered by the Client RBI Process and guidelines.
Consequence of Failure Evaluation
The consequence of failure is determined for each equipment and damage mechanism and includes the following relevant components: safety consequence, business consequence and environmental consequence.
Consequence of failure is expressed as consequence category and/or as a numerical value (potential loss of life, safety area, damage area, business interruption time, cost etc.)
Damage Mechanisms
Degradation rates are either evaluated by the Software or set by the user. The available power industry-specific degradation mechanisms covered by the Client RBI Damage Mechanism guidelines, including:
· Cracking-type mechanisms, such as
o Corrosion Fatigue (CF)
o Stress Corrosion Cracking (SCC)
o Thermal Fatigue (TF)
· Aging-type mechanisms, such as:
o Creep (C)
o Temper Embrittlement (TE)
o Short-Term Overheating (STO)
· Wall-loss type damage mechanisms, such as:
o External Corrosion (EC)
o Oxidation (OX)
o Pitting Corrosion (CP)
· …
Defined and systematized according to e.g. the prEN 16991, the new EN standard (ex-CWA 15740:2008/2011 RIMAP) (Table 1).
Risk Ranking
Risk values are allocated to each item analyzed for each possible damage mechanism and consequence of failure. Risk is expressed as a numerical value and also displayed in a risk matrix as a combination of a probability category and a consequence category.
Inspection Planning
· Inspection planning is performed in accordance to South African Regulation, allowing the possibility of extension of the prescribed (36 month) internal inspection and static pressure testing interval.
· Cost-benefit analysis for proposed inspections (i.e. risk-based NPV – Gain-Loss).
· Optimizing inspections with respect to component criticality.
RBI Reporting
· Standard reports available: risk reports, component summaries, inspection plan reports, etc.
· The user is able to generate custom reports.
Data for RBI Analysis
Asset Data Structures
· Station/Plant (e.g. Kendal, Matla, Lethabo, …)
· Unit (e.g. U3, U4, U6, …)
· Area (e.g. Boiler, Turbine, Gen Elec, …)
· System (e.g. Auxiliary Steam System, HP Bypass System, …)
· Equipment/Component (e.g. piping, pressure vessels, …)
· The issue of Client unique component IDs and naming conventions (e.g. system, subsystem, equipment type for SANS categorization,…) has to be resolved jointly with Client.
Data Input and Verification
· Data may be input either directly or by means of electronic transfer
· Entry Form (with verification)
· Spreadsheet Entry Form with verification
· Capability to import data from external software (pre-specified formats)
Table 1: Damage mechanisms defined and systematized according to prEN 16991, the new EN standard (ex-CWA 15740:2008/2011 RIMAP)
| Event, problem, issues | ID and type of damage or disturbances / deviations, functional problems | Subtypes / specifics / further details / examples | | Common terms** | Client Guideline Terminology |
| MATERIAL DAMAGE RELATED PROBLEMS | I. Corrosion/erosion/environment related damage, leading to: | |
| I.A Volumetric loss of material on surface (e.g. thinning) | I.A1 General corrosion, oxidation, erosion, wear, extended thinning | EC, E, FAC | CPE, E, EC, FAC, FAE, FLAC, GC, CP, IC, UIC/UFC, SOE, OX |
| I.A2 Localized (pitting, crevice or galvanic) corrosion | IC | CVC |
| I.B Cracking (on surface, mainly) | I.B1 Stress corrosion (chloride, caustic, etc.), cracking | SCC | SCC |
| I.B2 Hydrogen induced damage (incl. blistering and HT hydrogen attack) | | HD |
| I.B3 Corrosion fatigue | CF | CF |
| I.C Material weakening and/or embrittlement | I.C1 Thermal degradation (spheroidization, graphitization, etc. incl. incipient melting) | | G, |
| I.C2 Carburization, decarburization, dealloying | | |
| I.C3 Embrittlement (incl. hardening, strain aging, temper embrittlement, liquid metal embrittlement, etc.) | EMB | TE, SPE, SAE, HE |
| II. Mechanical or thermo-mechanical loads related, leading to: | |
| II.A Wear | II.A1 Sliding wear | W | FRE |
| II.A2 Cavitational wear | E | CV |
| II.B Strain / dimensional changes / instability / collapse | II.B1 Overloading, creep | C | C, SF, SAC |
| II.B2 Handling damage | PC | |
| II.C Microvoid formation | II.C1 Creep | C | C |
| II.C2 Creep-fatigue | | CRF |
| II.D Micro-cracking, cracking | II.D1 Fatigue (HCF, LCF), thermal fatigue, (corrosion fatigue) | F, VF, TF, CF, TMF | MF, TF |
| II.D2 Thermal shock, creep, creep-fatigue | LTCCG | LTCT, SOH |
| II.E Fracture | II.E1 Overloading | | |
| II.E2 Brittle fracture | BF | |
| III. Other structural damage mechanisms | G, GC, SRF, WD, CB, DMW | DMW, SRF, FOD |
| DISTURBANCES / DEVIATIONS / PROBLEMS (not related to structural materials) | IV. Fouling / deposits (without fluid flow disturbances) | |
| V Fluid flow disturbances |
| V.A High / low fluid flow (HFF/LFF) |
| V.B No fluid flow (NFF) |
| V.C Other fluid flow problems (OFFP) |
| VI. Vibration (VIB) |
| VII. Improper dimensioning, improper clearances |
| VIII. Man made disturbance (deliberate and unintentional) |
| IX. Fires, explosions and similar |
| X. Damage and/or loss of function due to other causes |
| X.A External leakage (EXL*) |
| X.B Improper start or stop - failed to start/stop (FTS*) |
| X.C Failed while running (FWR*) |
| X.D Overheated (OHE*) |
| X.E Other (OTH*) |
| * acronyms broadly corresponding to those used in OREDA [33]. ** Damage mechanisms labelling as commonly used in practical RBI – analysis (here a power plant example), EC – External Corrosion, E – Erosion, FAC – Flow Accelerated Corrosion, IC – Internal Corrosion, SCC – Stress Corrosion Cracking, CF – Corrosion Fatigue, EMB – Embrittlement, W – Wear/Fretting, C – Creep, PC – Plastic Collapse, F – Fatigue, VF – Vibration related Fatigue, TF – Thermal Fatigue, TMF – Thermo/mechanical Fatigue, LTCCG – Low Temperature Creep Crack Growth, BF – Brittle Fracture, G – Graphitisation, GC – Graphitic Corrosion, SRF – Stress Relief Cracking, OH – Overheating, WD – Welding Defect, CB – Casting Defect, DMW – Dissimilar Metal Weld Failure |
RBI Data Output
The data output will include the following:
· Item analyzed
· Possible damage mechanisms
· Probabilities of failure for each component and the respective damage mechanisms
· Consequence of failure for each component
· Risk ranking (discrete and matrix)
· High-level inspection and test plan, including proposed inspection/test dates and techniques
· Value/Cost of Risk
· Results of risk assessment and inspection/test plans available to external software
RBI Data Customization
· Probability category definition
· Consequence category definition
· Generic failure frequency data
· Inspection priority definition
· Inspection costs
· Using the actual degradation rates for each equipment
Inspection Data Management
Asset Data, Resources and Document Management
· Configuring asset data hierarchies such as functional hierarchy, geographical hierarchy, inventory group and equipment class grouping
· Specifying equipment design and operating data using standard datasheet templates
· Adding/editing/deleting equipment basic attributes such as equipment type/priority class/specification description/asset ID/department and engineering drawing
· Recording component and parts list and relevant technical data
· Allowing searches for specific component by “keyword” and sort by component ID/component type
· Company organization hierarchy, including Software users/resources & permissions
· Attaching and viewing documents such as Image files, Visio/AutoCAD drawings, PDF files, Excel files at the various levels of the asset hierarchy.
Inspection Scheduling
· Provision of high-level inspection work scopes
· Generation of automatic work-list and next inspection date based on schedule
· Provision of Shutdown list for inspection work
Inspection management Reports
· Overall component risk reports
· Individual Component-level reports (2-pager)
· Risk-ranked lists
Data Security- Access Mode
· Site Administrator Access Mode
· Standard User Access Mode
· Viewer only Access Mode
User Interface Requirements
· Users shall access the Software through the web or optionally through the operator’s intranet
· Ability to operate in a networked environment. The database shall be accessible through a client server or web access
· Import input data from R-Tech template file types, e.g. XLS (MS Excel), XML, etc.
· Export of results for use/viewing in other software, e.g. MS Excel, MS Word, Adobe PDF, etc.
· The Software allows multiple concurrent users on network
| Software Look and Feel |
| |
| Component based Level 1 – screening |
| |
|
The Level 1 screening analysis is performed quickly on a large number of components, in order to screen out components with low levels of risk.
Assessment of each component is carried out considering the most likely damage / failure mechanism and the worst case failure scenario. Level 1 assessment represents a conservative high level qualitative estimate. |
|
| |
| Level 2 assessment - multiple DMs: |
| |
|
| Utilizing a similar methodology to the Level 1 assessment, the Level 2 procedure contains more specific criteria and an expanded scoring system. Not all of criteria available in the Level 2 analysis may be applicable to all potential damage mechanisms, but the selected criteria cover the majority of the main damage influencing conditions. A significant difference from the Level 1 analysis is the fact that all feasible damage mechanisms that could affect the component(s) are considered, instead of just one dominant DM. |
|
|
|
| Level 3.1: Risk Modelling – Bowtie |
| |
| Risk and mitigation factor / action modelling based on the Client RBI process and guidelines, for components with multiple damage mechanisms and consequence scenarios. Short-term high risk components are subjected to detailed consideration by the appropriate SME team. The evaluation process considers the various factors which can influence the PoF and CoF score, and their effectiveness. |
|
| |
| RBI Dashboard |
| |
|
| The RBI Dashboard expands on the capabilities of the RBI Software and enables the quick and successful implementation of the Client RBI Process and Workflow. A quick and precise overview is possible, thanks to logical structuring of plants, units, areas, analyses and components in a tree structure. Individual components can be searched for among a vast database, thanks to advanced filtering options. |
| |
|
The RBI Dashboard can quickly display the required pertinent information to highlight results and progress, or relevant indicators, such as:
· number of assessed components vs number required to be assessed, · number of components located in the respective risk categories. Custom overview breadth is supported – From a single plant area in a single unit, to the entire fleet if required. |
|
| |
|
| The RBI Dashboard serves as an extension of the Client RBI Process/Guideline, and enables the review and comparison of pre- and post- outage RBI results. Key information can be quickly filtered, calculated and displayed, such as: Number of DMs pre- and post-outage Comparison of pre- and post- outage PoF, CoF, Risk (Sum and Average) Assessment of all components, or only inspected within x past years. |
|
|
|
|
| API 581 Technical Modules |
| |
| The iRiS RBI software suite consists of the following modules: 1. API 581 qualitative analysis (unit/system-based) system for a system/unit-based approach (screening) 2. API 581 qualitative (component-based) – Level 1, semi-quantitative – Level 2 and Level 3 analysis modules |
| |
|
| API 581 qualitative analysis system for unit-based approach (screening) – QLTA: R-Tech’s QLTA is based on the Workbook for Qualitative Risk Analysis given in Appendix A of the API581 Base Resource Document QLT is used to determine the Likelihood and Consequence Category for a given system / unit, and is subdivided into the following sections: Part A: Likelihood Category
Part B: Damage Consequence Category
Part C: Health Consequence Category The final consequence is determined as the highest category derived from Part B or C. For multiple fluids, the exercise should be repeated, to derive separate risks for each hazardous material. The material with highest risk should be considered first during the component-based Qualitative assessment. |
| |
| API 581 component-based qualitative (Level 1 and semi-quantitative (Level 2 and Level 3) analysis modules iRiS RBI performs all the tasks necessary to determine the risk rank of the equipment and optimize the inspection plan, according to API581, based on the qualitative approach (level 1) or semi-quantitative (Level 2 and Level 3) approach. |
|
|
|
|