The role of a schematic model for

system design coordination

An AVEVA White Paper

Henrik Hultin
Per-Olof Nilsson
Per-Ola Åkesson
AVEVA AB Sweden
 The role of a schematic model for system design coordination - an AVEVA White Paper

Introduction

Pressures on plant designers and operators are constantly growing.

Projects have become increasingly larger, but with compressed time
schedules. Large projects are often executed using multiple
contractors at multiple locations and with multiple applications.

Similarly, in the shipbuilding industry designs are becoming ever

more advanced and thereby incorporating a growing number of
increasingly complex onboard systems. This, in combination with an
often flexible approach to project implementation, such as the use
of subcontractors and system suppliers, makes the proactive
management and consolidation of data from different sources an
absolute requirement.

In this paper, we describe an approach to meet these requirements

through the creation of a common schematic model, with related
application functions to represent and manage relevant system
design information for plant design and shipbuilding projects.

‘Pressures on plant designers and operators are

constantly growing. Projects have become increasingly
larger, but with compressed time schedules. Large
projects are often executed using multiple contractors
at multiple locations and with multiple applications...’

Page 2
 The role of a schematic model for system design coordination - an AVEVA White Paper

1. Plant and Ship System Design Challenges

Designs in both plant and shipbuilding are increasingly challenging.

Apart from the increased demands made by the design, there is also
a requirement for a more collaborative environment for the design
and development of these systems.

Many major EPCs and shipyards have globally distributed and

collaborating design locations. They are making more use of 'High
Value Engineering Centres' in the case of plant design, design
agents and subcontractors for ship system design, and specialist
system suppliers for turnkey and integration system solutions. Due
to time constraints and compressed schedules, this work is also
often carried out concurrently.

The challenge for the designer, whether an EPC or a shipyard, is how

to efficiently coordinate and handle the plant or ship system design
data. Data from several sources must be consolidated, and design
changes properly managed.

In shipbuilding, the growth in the complexity of ship designs is a

result of the need to better support their transportation functions,
and to offer operational, economical and performance advantages
to their owners and operators. The number of systems aboard
modern ships, especially the more advanced vessels such as
offshore, naval and special ships, is increasing.

These systems are also becoming more complex, in order to provide

faster operation and greater capacity, more automation, less
maintenance and, finally, a better performance for the Owner
Operator.

For large projects split between different engineering companies,

the P&IDs can be created with different authoring tools to minimize
the potential disruption to the companies working practises.

As a result, developing a consistent set of P&IDs for a complete

project as the design evolves is a complex task for project engineers
and designers. Approval of the latest versions of P&IDs and
highlighting of inconsistencies takes considerable time and, if not
carried out correctly, can lead to major design rework.

‘The challenge for the

designer, whether an EPC
or a shipyard, is how to
efficiently coordinate and
handle the plant or ship
system design data...’

Page 3
 The role of a schematic model for system design coordination - an AVEVA White Paper

2. Schematic model vs. 3D model

In plant design as well as in shipbuilding, the use of a 3D product It was clear from the beginning that, for some items, such as
model (see Figures 1a and 1b) currently provides an accepted way of pipelines, a separate representation was needed, due to the
working. For shipbuilding, a common product model for hull and structural difference from corresponding 3D items.
outfitting is normally used. In some cases, separate models for hull
and outfitting are still used, with the data being transferred in We wondered whether, in cases where there is a one-to-one
various ways. relationship between the schematic and 3D objects, (e.g.
equipment items and cables), the existing 3D objects could be used
This offers many advantages, including space management with and extended to support both the 3D and the schematic design. This
collision checks, collaboration between different disciplines such as was a tempting approach, since it would reduce the frequency of
hole management, and a common and distinct source for various redundant objects. However, after careful evaluation, we proved
derived data, for example, production information. that having separate objects for the schematic and 3D instances
offered greater advantages in concurrent working, change
The concept of the 3D product model is commonly used and handling, workflow and data management.
accepted, but it is not usual to treat schematic data in the same
way. By this, we mean having a common database, usable by all Leading on from this design consideration, we found that the
schematic designers and disciplines, to create a continuous, related management tools would need to provide a high level of
consolidated and complete schematic model, closely integrated functionality, and offer powerful features for the handling of the
with the 3D model. Not only could such a schematic model offer relations between schematic and 3D manifestations.
advantages and benefits in the system design area similar to those
provided by a common 3D design product model, but it also offers a The AVEVA Marine and AVEVA Plant design product model can,
collaborative environment for different engineering disciplines to through the addition of this data, be considered to include both a
better support some of the design challenges described above. schematic and a 3D model section in a single repository. The design
AVEVA has been researching and developing this concept and has of the database schema for the schematic section was also adapted
created a Schematic Model Database with related functions. to use as much of the concept and design philosophy from the
existing 3D model database as possible, thereby enabling the use of
Our initial approach involved adding the schematic data to the common data management functions.
existing 3D product model database using existing hierarchies and
structures, thereby extending the scope of the product model to We also worked to ensure that the supporting data sources in the
include, not only the 3D spatial representation, but also the form of Catalogues and Specifications could be referenced from the
functional schematic representation. However, as the organisation schematic data as well as from the 3D design data. This ensures data
is system oriented rather than space oriented, we found that the consistency and enables a flexible work process whereby Catalogue
database schema would need to be structured accordingly. selection can take place at the schematic stage and be reused, or
directly added, on the 3D side.

Figure 1a: Ship machinery arrangement as part of 3D model Figure 1b: The third module for Shell/Esso's Fife Natural Gas Liquids Plant,
Mossmorran, designed by Costain Oil, Gas & Process Limited, using PDMS

Page 4
 The role of a schematic model for system design coordination - an AVEVA White Paper

2.1 DB Organisation

The schematic model database is organised using two main T Pipelines with branches, valves and fittings
hierarchies (see Figure 2). These are the schematic group hierarchy T Inline and offline instruments
and the system hierarchy. The schematic group hierarchy can be T HVAC lines with branches and HVAC fittings
viewed as a user-defined folder structure in which the schematic T Cables
items can be categorised and organised in an arbitrary way. T Diagram drawings, drawing templates and symbol libraries.

In parallel to this, there is a system hierarchy which represents the The diagrams are represented by proxy objects, which enable the
design systems of which the schematic items are members. database to manage the corresponding diagram documents and
their relation to the schematic items which appear on them.
The database also includes references between schematic items and
the drawings on which they are represented, and this can be used as In addition to the base objects, users can extend the data model
a third hierarchy. with user-defined hierarchies, object types and attributes. Such
user-defined items are still fully recognised, displayed and handled
2.2 Schematic Objects by the standard application functions.

The database can store and represent a number of base object types Topological information, such as connections from pipelines, HVAC
(see Figure 2) including those listed below: lines or cables to equipment items, and offline instrument
connections to various fittings, is captured and represented in the
T Equipment items having sub-equipment, nozzles (pipe data model. The offline instruments can also provide a link between
connection pieces) and electrical connections a main process system and a related control system.

Schematic Group System Diagram

Pipeline/
Equipment HVACline Offline Instrument Cable

Nozzle Branch

Valve & Fitting Instrument Figure 2: Simplified overview of schematic model DB schema

Page 5
 The role of a schematic model for system design coordination - an AVEVA White Paper

2.3 Data Management 2.4 Open Model

To fulfil the data management requirements of the intended A set of functions for importing and exporting data is provided,
collaboration support for the schematic model database, we used a allowing a flexible choice of P&ID authoring tools. Line lists,
data management platform developed in house. This platform equipment lists, valve lists, etc., can be imported using ordinary
provides support for distributed databases, transactions, spreadsheet files, or more advanced XML formats such as ISO 15926
versioning, traceability, and so on. (used in the plant design and offshore industries) can be used to
import pipeline network topology.
Such features enable the distribution of the schematic model
database globally between different collaborating parties and Drawings can be imported in different formats, but conversion to
subcontractors. Systems can be designed and consolidated into a the XML-based SVG format will provide a higher level of
single model, even if design teams are working in different functionality, such as the identification and highlighting of the
geographical locations. related schematic items. Corresponding spreadsheet format export
functions are also available.

For the import of pipeline networks and drawings, the AVEVA P&ID
Manager application is used. This application makes it possible to
check each batch of data for consistency and, when a complete
model has been created, this can be consolidated and further
checked for overall consistency. By establishing the schematic
model and using the related tools, this task is much easier than
checking a large number of separate P&ID sheets and making sure
the interconnections are correct.

In addition to the import and export interfaces, the schematic

‘...Information about major model database provides a set of public .NET APIs which enable
custom developed software to interface with it for online reading
items, as well as estimates and writing of data. This can be used to extend existing
for pipe lengths and types/ applications, for the custom development of applications operating
directly on the schematic model data, for analysis tools, or for ERP-
numbers of fittings, can type system integration.

be obtained by using Information about major items, as well as estimates for pipe lengths
and types/numbers of fittings, can be obtained by using the .NET
the .NET APIs or the APIs or the import/export functions. This information is useful for
import/export functions...’ early ordering and material planning.

Page 6
 The role of a schematic model for system design coordination - an AVEVA White Paper

3. Connection to 3D

The Schematic Model applications include a number of features to

manage the release of information to 3D. This includes a flexible
‘Already released design
function for design managers to approve and set release status for a information can be revised and
system, a diagram, or parts thereof. Setting the release status
provides a signal to the 3D designers that the schematic re-released in a controlled way,
information is now ready to be used as a base for the 3D design.
allowing revisions to be
The applications also contain functions for visualising the release-
and 3D-usage status, as well as warning or restraining the user from
implemented and released while
modifying released data. Already released design information can parallel work is continuing on
be revised and re-released in a controlled way, allowing revisions to
be implemented and released while parallel work is continuing on the 3D side...’
the 3D side.

P&ID Authoring Tools Global

Synchronisation

Schematic Model
Viewer

Product Model DB
P&ID Manager Spreadsheet
Import/Export

Schematic
Data

3D Design Customisation APIs

Schematic 3D Data
Integrator

Figure 3: The schematic model as part of the complete product model DB, together with related functions

Page 7
 The role of a schematic model for system design coordination - an AVEVA White Paper

4. Schematic Model Viewer

Given the schematic model database and its capability to represent A set of main goals for a visualisation tool was defined as follows:
a continuous schematic model for the whole ship design, the next
question was whether it would be possible to view and visualise the T It should illustrate the connectivity of items in the database in a
contents of the database in an intuitive and easily understandable neutral way not related with the subdivision and layout of
way. As this data can originate from a number of different P&IDs individual P&IDs
and other diagrams, as well as being imported from various sources, T It should provide a consolidated view of multiple systems
there is no single drawing that illustrates the complete schematic T It should provide a navigable view and not a static picture
model. T It should be possible to start with a limited view in scope as well
as detail, and then expand and drill down on request
Although the connectivity can be seen in the various P&IDs and T It should be easy and intuitive to use.
other diagrams, these documents are most often organised in such
a way that a single diagram only shows a single system or even part Based on these goals, research was done in the area. We quickly
of a single system and does not provide a complete overview of found that a traditional 'tree' view (Explorer) control is suitable for
interconnected systems. In ship design there are many cases of showing predefined hierarchies, but cannot illustrate the full
equipment items that are related to more than one system. The connectivity of the model. It must be considered that the topology
most obvious example in shipbuilding is perhaps the main engine of the piping network includes such features as loops.
which is connected to a number of supporting systems, including a
cooling water system, a fuel oil system and a lubrication system After examining different alternatives, we decided to look more
(see Figures 4 and 5). closely at the Mind Map® style of diagram and a variant, known as a
'wheel' diagram. When investigating existing applications of this
style of diagram, we found that inspiration could be taken from
computer network administration applications which, in many
cases, exhibit features similar to what we wanted to accomplish.

Figure 4: The schematic model viewer can show a view of all systems connected to Figure 5: A closer view showing one of the systems to the engine
an equipment item, in this case, the main engine in a ship

Page 8
 The role of a schematic model for system design coordination - an AVEVA White Paper

4.1 Creating an initial layout

We decided that the navigation should start with an equipment item The process described above results in an initial view with the
selected by the user. From this item, the system would automatically selected equipment item in the middle and connected equipment
find all connections in the database and display each connection as items around it, and the branching topology visible in the
a graphical subtree. Each subtree would then be traversed through interconnecting lines and branch points (see Figure 6).
all branches until other equipment items or branch ends were
encountered. 4.2 Navigation and drill-down

Branching points (such as tees, olets or three-way valves) were From the initial view it is possible to navigate interactively along the
represented by a generic branching point symbol. For the connection network, expanding and collapsing subtrees and re-
equipment items, a set of customer definable rules have been centring on other equipment items. By this process, the user can
created. By using these rules, the application can select and display proceed from system to system and explore the complete schematic
an appropriate graphical symbol for each equipment item. As the model.
Schematic Model Viewer is a dynamic viewer tool and is not
displaying a static P&ID layout, we decided not to use the In the initially generated overview layout, only equipment items
traditional P&ID symbols, but to go, instead, for a more illustrative and generic branching points are shown. To go into more detail, and
style. see inline parts such as valves, reducers and other fittings, the user
needs simply to press one button (see Figure 7). Alternatively,
The pipeline network can also contain circular layouts. To handle right-clicking on an item in the Schematic Model Viewer allows the
this, we introduced an algorithm by which the connected items were user to list the diagram drawing(s) on which this item exists, and to
placed in a primary subtree, and the looping connection was open and view the selected drawing(s). This provides another form
illustrated by a diagonal line to a member of another subtree, or at of drill-down.
another location in the same subtree.
The Schematic Model Viewer also provides standard features,
If the layout generated by this mechanism is not what the user including the viewing of database attributes for the selected item,
wants, they can easily reverse the link, so that the item in question and the facility to manually rearrange the auto-generated layout by
will move and become a member of the other subtree, or the other drag-and-drop.
part of the same subtree.

Figure 6: The initial view created by the viewer shows the selected item together Figure 7: Schematic Model Viewer showing valves and inline fittings at detail
with all connected items and generic branching points level

Page 9
 The role of a schematic model for system design coordination - an AVEVA White Paper

5. Relation with the 3D model 5.2 Comparing 3D design data with schematic
data
Clearly, a set of management functions was needed for the data of
the two models, schematic and 3D. These functions would have to The Schematic 3D Integrator includes functions to compare the
include the creation of 3D data based on the schematic model, schematic data with the 3D design data. The comparison can find
comparison functions including reporting, and functions for missing and unmatched items on both sides, as well as differences
managed updates to existing data following design changes. An in attribute values, and topology and connectivity (for instance, an
important aspect to this would be to support parallel working and incorrect branching model or incorrect sequence of fittings in a
not restrict it to a predefined sequence of events. For these branch).
purposes, the AVEVA Schematic 3D Integrator application was
developed (see Figure 8). As these functions are, in many cases, Using the Integrator, the user can view the diagram as well as the
part of a workflow that is handled by existing design applications, related 3D data. If a schematic item is selected, the corresponding
an important design decision was to implement this application as 3D item is also selected and highlighted, and vice versa. This makes
an add-in, which could be integrated into existing design it easy for the user to see the relationship between corresponding
applications. This means, for instance, that a 3D piping engineer items and to understand any anomalies.
does not have to leave the 3D piping design application to compare
the current 3D design with the corresponding schematic design. It is also important to point out that this comparison can be
performed even if the 3D data has not been created from schematic
5.1 Creating 3D design data data using the Integrator. In many cases, the strict sequential
working procedure between schematic design and 3D design cannot
The consolidated data in the schematic model database can be used be applied, and it must still be possible to compare the models.
as a base for the 3D layout design of the related systems. The
Integrator add-in allows the schematic model data to be exploited 5.3 Managed updates
as a base for the automatic creation of 3D design data.
If any inconsistencies or anomalies are found by the comparison
A customer-configurable rule-based implementation means that between the schematic model and the 3D model, either can be
this creation is adaptable to customer preference and design rules, updated from the other in a controlled way. This forms the basis for
including automatic pipe routing. The automatically created data the management of design changes, and ensures that they are
can then be further elaborated and modified by the 3D piping properly applied to both the schematic and the 3D design models.
engineer, to accomplish a final 3D design. By applying this
procedure, the 3D design can be elaborated quicker and with less
effort, and the logical correctness of the 3D model can be
increased.

‘The AVEVA Schematic

3D Integrator includes
functions to compare the
schematic data with the
3D design data...’

Figure 8: The AVEVA Schematic 3D Integrator,

showing a 3D model machinery arrangement,
together with the corresponding diagram, and
tables of related data

Page 10
 The role of a schematic model for system design coordination - an AVEVA White Paper

6. Conclusions

The schematic model database provides a good platform for

compiling all relevant schematic data for a project. This can be
‘This flexibility can support a
accomplished by tight online working against the database, where distributed way of working with
items are created automatically as they are drafted on the diagram,
or in an offline fashion, where data can be imported from other partners, contractors,
authoring tools.
subcontractors, vendors and
This flexibility can support a distributed way of working with
partners, contractors, subcontractors, vendors and system
system suppliers. The resulting
suppliers. The resulting set of data in the schematic model database set of data in the schematic
can be verified and consolidated by using the Schematic Model
Viewer, as well as the checking capabilities of P&ID Manager, model database can be verified
miscellaneous reports and other tools. This makes it possible to
ensure that all related data is complete and consistent. and consolidated by using the
The schematic model database also provides a base for the 3D
Schematic Model Viewer, as well
model, where schematic data can be reused on the 3D side. as the checking capabilities of
However, a more concurrent working mode often has to be used
because of time constraints. In this case, the schematic model can P&ID Manager, miscellaneous
be of use anyway, to retrospectively check that the 3D model fulfils
the system design intent. reports and other tools. This
If the schematic model database is kept up to date with all changes
makes it possible to ensure that
introduced, it can also provide a schematic as-built documentation all related data is complete
of the project, which can easily be navigated using the schematic
model viewer. This includes the possibility for other project and consistent...’
reporting functions or in-service and onboard applications.

Looking further, we believe that current developments in this area

have great potential. This concept can be extended and enhanced in
many different ways, only a few of which have been implemented so
far.

This article has been adapted from a paper given at the International Conference on Computer Applications in Shipbuilding (ICCAS 2007), in September 2007, organised
by the Royal Institution of Naval Architects (RINA). It is reprinted with the permission of RINA.

Page 11
AVEVA Group plc
High Cross
Madingley Road
Cambridge, CB3 0HB Headquartered in Cambridge, England, AVEVA Group plc and its operating
UK subsidiaries currently employ more than 800 staff worldwide in England,
Australia, Austria, Brazil, Canada, China, Dubai, France, Germany, Hong Kong,
Tel +44 (0)1223 556655 India, Italy, Japan, Malaysia, Mexico, Norway, Russia, Saudi Arabia, Singapore,
Fax +44 (0)1223 556666 Spain, Switzerland, Sweden, South Korea and the USA.

Americas Region Asia Pacific Region Europe, Middle East and Africa Region
Headquarters Headquarters Headquarters

AVEVA Inc AVEVA Asia Pacific Division AVEVA GmbH

10350 Richmond Avenue Level 59, Tower 2 Otto-Volger-Str.7c
Suite 400 PETRONAS Twin Towers KLCC D-65843 Sulzbach
Houston, Texas 77042 50088 Kuala Lumpur GERMANY
USA MALAYSIA

Tel +1 713 977 1225 Tel +60 (0)3 2176 1234 Tel +49 (0)6196 5052 01
Fax +1 713 977 1231 Fax +60 (0)3 2176 1334 Fax +49 (0)6196 5052 22

www.aveva.com

AVEVA believes the information in this publication is correct as of its publication date. As part of continued product development, such information is subject to change without prior notice and is
related to the current software release. AVEVA is not responsible for any inadvertent errors. All product names mentioned are the trademarks of their respective holders.

© Copyright 2009 AVEVA Solutions Limited. All rights reserved. WP/SCHEMOD/09