DNV SOFTWARE A LEADING PROVIDER OF SOFTWARE FOR

RISK

TARO

Taro
Feature Description

2 | Feature description | Taro 4 |

WWW.DNVSOFTWARE.COM

Date: February/2013

Prepared by DNV Software, an independent business unit of Det Norske Veritas

Det Norske Veritas AS. All rights reserved. This publication or parts thereof may not be reproduced or transmitted in any form or by any means, including copying or recording, without the prior written consent of Det Norske Veritas AS.

WWW.DNVSOFTWARE.COM

Taro 4 | Feature description | 3

TABLE OF CONTENTS
Overview ........................................................................................................................................................................ 4 Features .......................................................................................................................................................................... 4 Events ........................................................................................................................................................................ 4 Production/Flow ........................................................................................................................................................ 6 Production Compensation .......................................................................................................................................... 8 Logistics Operations .................................................................................................................................................. 8 Maintenance and Logistics ............................................................................................................................................. 8 Financial Data ............................................................................................................................................................ 9 Results .......................................................................................................................................................................... 10 Summary.................................................................................................................................................................. 10 Criticality ................................................................................................................................................................. 10 Units/Tanks Results ................................................................................................................................................. 10 System ..................................................................................................................................................................... 10 MAINTENANCE .................................................................................................................................................... 10 Powerful Graphical User Interface (GUI) .................................................................................................................... 11 MODEL BUILDING ............................................................................................................................................... 11 Results animation .................................................................................................................................................... 12 Table view of inputs ................................................................................................................................................ 13 1. Keeping updated ...................................................................................................................................................... 14 2. System Requirements ............................................................................................................................................... 15

4 | Feature description | Taro 4 |

WWW.DNVSOFTWARE.COM

OVERVIEW
Taro 4 is used for assessing process plant efficiency, availability and utilisation as a function of reliability, throughput and operations. It is specifically developed for the downstream industry with a transport logistic capability to capture complex interaction of multiple feed & product streams, storage tanks, transport logistics and operational strategies. Taro 4 predicts the performance of a system using simulation techniques. An Event-Driven algorithm is used to create lifecycle scenarios of the system under investigation accounting for its reliability, maintainability and operating policies. The simulator is inherently incorporated with a specially designed Figure 1 Petrochemical Unit algorithm to analyse the impact of each individual scenario on how the system performs. By studying performance results and how they respond to altering specific parameters in the design or its logistics, it is possible to optimise the system with respect to given constraints

FEATURES
Taro 4 provides a wealth of powerful features, both relating to the capability of the simulation and the usability of the software. The following pages summarize the key features of the Taro package; screen shots have been included to give an additional impression of the packages capabilities. Taro has been developed to model complex petrochemical and refinery process plants. It has a successful track record and proven ability to deal with complex production scenarios.

EVENTS
Events comprise any occurrences within a system's life that affect the behaviour of the system. Taro 4 provides three main kinds of events: Unscheduled events are unplanned and occur at random basis however, their occurrence usually corresponds to a particular statistical distribution. Example: Equipment Failures. Scheduled events that the frequency occurrence is known. Example: routine inspection Conditional events that are initiated by the occurrence of other events via a Boolean logic expression. Example: Warm up of an equipment in standby

The event impact on the production can be either partial or full loss. The unscheduled failures can model the following failure characteristics:

Exponential Distribution Normal Distribution Rectangular Distribution Triangular Distribution On Demand Failure (Parallel Block Standby Unit Switch Reliability) Weibull Distribution (Including age at start up, time delay, and time delay for first failure etc.) Cumulative Distribution Function Table (caters for raw failure data without distribution specified) Figure 2 - Statistical Distribution defining an Unscheduled Event

WWW.DNVSOFTWARE.COM

Taro 4 | Feature description | 5

Accordingly, the repair time can be modelled by the following methods

Constant Exponential Normal Log-Normal Rectangular Triangular Weibull (including time delay) Multi-shot life Seasonal repair Cumulative Distribution Function Table (caters for raw repair data without distribution specified) Conditional delay repair

Conditional event provides a powerful capability on the modelling of special logic, it includes the following types:

Common (the effect happens concurrently with the trigger(s)) Common During Repair (effect happens concurrently with the trigger(s) during repair duration). Independent (effect is triggered once trigger occurs, and the repair of effected event is independent of trigger(s)) Sequential (effect occurs immediately after the finish of the trigger repair) Concurrent (similar to common type, with different counter of occurrences) Replace Last (effect will replace the event which causes the trigger) Replace All (effect will replace the complete trigger set).

Additionally, the following types of logic representing the interaction between events can be modelled: Tank level management Flow rate management Feedstock supply fluctuations Customer demand fluctuations Bulk transport operating status changes Batch operations status changes

Figure 3 Example of failure mode definition and Scheduled Activity definition

6 | Feature description | Taro 4 |

WWW.DNVSOFTWARE.COM

PRODUCTION/FLOW
Taro has been developed to cover petrochemical and refinery plants and, therefore, is set-up at unit level with flow routing, blending and yield rules. Each unit/tank/berth/bulk transport is termed a Sub-network.

Figure 4 - Example of feeds and yield rates Each Sub-network (SubNet) that represents a Process unit has its own specific product yield slate, along with a preferred set of blending rules, which form the recipe for the yields. A nodal mass balance within each SubNet is maintained along with flow balance across the entire plant. Disposal rules can be set-up to manage the flow mass balance in the event of abnormal circumstances occurring, e.g. shut-in host, dump to slop tank, flaring excess etc. Minimum flow rates can also be set for all processes. Feed recipes (blends) can be set-up to allow mix ratios to be maintained or alternate mixes used when certain feedstock supplies are impaired. Distribution of new products for a process can have many alternate routes depending on priority and the ability of the recipient to receive the product. Re-cycle loops are also supported. A sub-network can also represent storage tanks, docks, bulk transport logistics, suppliers, customers and mixing manifolds. An overview of an example network of SubNets is shown in Figure 5.

Figure 5 - Example network of a Refinery

WWW.DNVSOFTWARE.COM

Taro 4 | Feature description | 7

Feedstock into the plant can be either constant, batched via bulk transport or have a fluctuating distribution, a number of distributions are supported. Product sales can be either limited by the process or driven by a sales demand profile, various demand distributions and sampling time steps are supported.

Figure 6 - Example of SubNet rate profile Having defined the overall process flow arrangement for the plant. Equipment is then placed in each sub-network by specifying equipment layout, redundancy, reliability and repair.

Figure 7 - Example of SubNet content showing the equipment groups

Figure 8 - Example of equipment configuration in an equipment group

8 | Feature description | Taro 4 |

WWW.DNVSOFTWARE.COM

PRODUCTION COMPENSATION
A very important part of Taro is the ability to define a comprehensive set of rules stating how the plant will be run under various abnormal or transient states, i.e. in the event of tank top-outs, bottom-outs, planned shutdowns, degraded equipment or unit capacity, alternate feed mixes, over-supply, under supply etc. Compensation mechanisms include boosting and buffering in order to claw-back lost contract volumes within stipulated contract periods. When the demand profile or the production profile cannot be satisfied and a shortfall occurs, it might be possible to boost the production or draw from buffers to recover the losses.

LOGISTICS OPERATIONS
Taro includes the ability to set-up bulk transport logistics for feedstock, sales and inter-process movements. Complex berthing and tanker fleet arrangement are supported along with shipping logistics. Shipping can be either dedicated or on a call up basis triggered by level control in storage. Bad weather and various hold-up scenarios can be included in the bulk transport logistics, discretely for any berthing, disembarking or round trip travel.

Figure 9 - Example of part of a network with ships and berths

MAINTENANCE AND LOGISTICS

Three main kinds of maintenance can be modelled in Taro: Corrective Maintenance Preventive Maintenance Opportune Maintenance Associated with the maintenance modelling, the following kinds of resources are modelled: Crew Vessel Safety Spare parts Accessories The resources can be constrained by:

Figure 10 - Maintenance Setup

Available number Shift or seasonal availability Available time span

WWW.DNVSOFTWARE.COM

Taro 4 | Feature description | 9

Frequency Mobilisation time Travel time Restocking time - for spare parts A maintenance task scheduling is embedded in the simulator, which determines the resource mobilisation, manages the movement of resources and prioritises jobs based on the user input. When building the model the user provides the resource set up, the constraints and individual job priorities.

FINANCIAL DATA
In Taro the user can take into consideration revenues and expenditures in order to get financial impact results. This includes:

Product pricing with an option to vary this over time Capital Expenditure (CAPEX) Operating Expenditure (OPEX) - manpower, spares and extras etc. Annual Discount Rate

10 | Feature description | Taro 4 |

WWW.DNVSOFTWARE.COM

RESULTS
Depending on the modelling details, Taro presents rich information of the simulation results. Following are the main entries of the results:

SUMMARY
Potential sales efficiency Production profile Average efficiency Actual volume produced Total production losses Average loss/annum

CRITICALITY
Event Criticality Element Criticality Subsystem Criticality

Figure 11 - Production Profile graph

UNITS/TANKS RESULTS
Buffer Efficiency Summary Buffer Statistics Plant Performance Summary SubNetwork Outage Summary SubNetwork Production Rate Diary SubNetwork Lifecycle LogSystem Performance Signature System Performance

SYSTEM
Performance Signature System Performance Figure 12 - Performance Signature graph

MAINTENANCE
Resource Utilisation Consumption of Spares Crew Maintenance Statistics Crew Utilisation Crew Skill Utilisation Trade Man-hours Statistics Job Summary per Element Category Maintenance Workload per Location Level One Priority Jobs

WWW.DNVSOFTWARE.COM

Taro 4 | Feature description | 11

POWERFUL GRAPHICAL USER INTERFACE (GUI)

MODEL BUILDING
A user friendly interface is provided by the application to provide every convenience for the user to build up a model. The particular features include:

Hierarchical view of the total asset Background image and annotation Symbols used to represent branches/systems/equipment in familiar ways to ease understanding including option to import own images to use Graphical representations of input data such as distribution curves and reservoir profiles Equipment catalogue where equipment, groups and branches can be added to or used from by simple drag and drop actions View Menu gives the ability to revert from one View of the application to other quickly.

Map View

Equipment Catalogue

Figure 13 - Asset View with Equipment catalogue and Map View

12 | Feature description | Taro 4 |

WWW.DNVSOFTWARE.COM

RESULTS ANIMATION
The GUI is responsible for presenting the progress of the simulation, managing and illustrating the results. There is also an animation feature to allow users to replay details of the simulation activities to ensure the correct operating rules are being adhered to.

Figure 14 - Screenshot of result animation

WWW.DNVSOFTWARE.COM

Taro 4 | Feature description | 13

TABLE VIEW OF INPUTS

All the failure mode, scheduled activity and conditional element data can be viewed and edited in tables where grouping, sorting and column selection makes model building easier and quicker. The Equipment and Activity table provide support for: Sorting by multiple fields Outlook style grouping Manipulating the layout of the fields, re-sizing, re-ordering, and hiding Copying/pasting cell data Copying/pasting failure modes Adding/Deleting failure modes Adding Equipment/Activity Items

Figure 15 - Equipment Table

14 | Feature description | Taro 4 |

WWW.DNVSOFTWARE.COM

The recently added Conditional table allows: Editing Conditional effects, consequences, repair times and maintenance resource requirements Adding trigger sets and configuring ANY/ALL/AND logic and trigger count for the ANY condition Drag and drop addition of triggers or trigger groups to a trigger set Deleting triggers from a trigger set from right-click menus Finding and highlighting a trigger on the Asset Hierarchical Tree from right-click menus

Figure 16 - Conditional Table

KEEPING UPDATED
Taro comes with an Application Updater utility that keeps track of major and minor releases as these become available.

Figure 17 - Application Updater

WWW.DNVSOFTWARE.COM

Taro 4 | Feature description | 15

SYSTEM REQUIREMENTS
The specification for Taro is as follows:

Minimum Requirements Windows XP SP3* Windows Vista (32 !it ve"sions# Windows $ (32/%& !it ve"sions# Inte' Pentium IV A() At*'on XP - ./ 011 (23 -

Recommended Windows $ (%& !it ve"sions#

Operating System:

Computer Processor**: Computer Memory: Cloc speed !M"#$ %nternet &ro'ser Screen Resolution: Screen colour depth "ard dis space !M&$ Media Pointing de(ice Microso)t *+cel

Inte' +o"e i, Inte' +o"e i$ & ./ o" mo"e 3.23 o" *ig*e"

Inte"net E4p'o"e" %514 (Inte"net E4p'o"e" 0 o" 6 "ecommended#5 7*is does not *ave to !e set as you" de8au't !"owse"9 !ut you must *ave it insta''ed5 A "eso'ution wit* a minimum *eig*t o8 $21 pi4e's (2ig*e" "eso'ution "ecommended to view mo"e on t*e asset view sc"een# %,,3% (-% !it# and *ig*e" %,1 (/ (p'us a"ound -./ o8 tempo"a"y dis: space# +) o" )V) ;<( d"ive (ic"oso8t (ouse o" compati!'e Some 8eatu"es depend on *aving (ic"oso8t E4ce' insta''ed5 7*e p"oduct is tested wit* <88ice XP and mo"e "ecent ve"sions5

*Windows XP SP2 is accepta!'e i8 Windows Insta''e" 35- is insta''ed5 7*is is avai'a!'e t*"oug* Windows =pdate ** >ote? simu'ation time is "e'ated to t*e p"ocesso" speed so t*e 8aste" t*e +P= t*e soone" t*e simu'ations "un5

16 | Feature description | Taro 4 |

WWW.DNVSOFTWARE.COM

THIS IS DNV SOFTWARE DNV Software is a leading provider of software for managing risk in the energy, process and maritime industries offering solutions for design, engineering, strength assessment, risk and reliability, QHSE and asset integrity management. DNV Software is part of DNV and almost 300 DNV offices in 100 countries enable us to be close to our customers and share best practices and quality standards throughout the world.

DNV SOFTWARE OFFICES

Contact e-mail: dnv.software@dnv.com Support: software.support@dnv.com

Oslo NO-1322 Hvik Norway Tel: +47 67 57 99 00 Beijing 7/F, East Tower Prosper Centre, Chaoyang District No. 5 Guang Hua Road Beijing 100020 P.R. China Tel: +86 10 6562 7792 Busan 7th Floor, Kolong Bldg, 36-7 Namcheon 1 Dong, Suyong Gu, Busan 613-815 Republic of Korea Tel:+82-51-610-7792 Dubai Bur Juman Office Tower, 14th Floor, Trade Center Road, Dubai, United Arab Emirates Tel: +971 4 352 6626 Ext 308 Gdynia ul. uycka 6e, 81537 Gdynia, Poland Tel: +48 58 5115000

Glasgow The Helix Building, 1st Floor, Kelvin Campus, West of Scotland Science Park, Maryhill Road, Glasgow G20 0SP United Kingdom Tel: +44 (0) 141 945 6970 Houston 1400 Ravello Drive, Katy Houston, Texas 77449 USA Tel: +1 281 396 1700 London Palace House 3 Cathedral Street London SE1 9DE United Kingdom Tel: +44 (0)20 7716 6525 Marseille 8 rue Jean-Jacques Vernazza, 1 Marseille France Tel: +33 4 91 13 71 66 Mumbai Emgeen Chambers 10, C.S.T. Road Vidyanagari, Kalina Santacruz (East). Mumbai 400098 India Tel: +91 22 26676667

Paris 69 rue Chevaleret 75013 Paris France Tel: 033 1 44 24 40 10 Rio de Janeiro Rua Sete de Setembro 111/12 Floor 20050006 Rio de Janeiro Brazil Tel: +55 21 3722 7232 Shanghai House No. 36 1591 Hong Qiao Road Shanghai 200336 P.R. China Tel: +86 21 3208 4518 Singapore DNV Technology Centre 10 Science Park Drive Singapore 118224 Singapore Tel: +65 6508 3284 Stavanger Rosenberggata 99 Veritasbygget N-4007 Stavanger Norway Tel: +47 51 50 60 00