Professional Documents
Culture Documents
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.
Page 2
The role of a schematic model for system design coordination - an AVEVA White Paper
The role of a schematic model for system design coordination - an AVEVA White Paper
It was clear from the beginning that, for some items, such as
pipelines, a separate representation was needed, due to the
structural difference from corresponding 3D items.
We wondered whether, in cases where there is a one-to-one
relationship between the schematic and 3D objects, (e.g.
equipment items and cables), the existing 3D objects could be used
and extended to support both the 3D and the schematic design. This
was a tempting approach, since it would reduce the frequency of
redundant objects. However, after careful evaluation, we proved
that having separate objects for the schematic and 3D instances
offered greater advantages in concurrent working, change
handling, workflow and data management.
Leading on from this design consideration, we found that the
related management tools would need to provide a high level of
functionality, and offer powerful features for the handling of the
relations between schematic and 3D manifestations.
The AVEVA Marine and AVEVA Plant design product model can,
through the addition of this data, be considered to include both a
schematic and a 3D model section in a single repository. The design
of the database schema for the schematic section was also adapted
to use as much of the concept and design philosophy from the
existing 3D model database as possible, thereby enabling the use of
common data management functions.
We also worked to ensure that the supporting data sources in the
form of Catalogues and Specifications could be referenced from the
schematic data as well as from the 3D design data. This ensures data
consistency and enables a flexible work process whereby Catalogue
selection can take place at the schematic stage and be reused, or
directly added, on the 3D side.
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
hierarchies (see Figure 2). These are the schematic group hierarchy
and the system hierarchy. The schematic group hierarchy can be
viewed as a user-defined folder structure in which the schematic
items can be categorised and organised in an arbitrary way.
T
T
T
T
T
In addition to the base objects, users can extend the data model
with user-defined hierarchies, object types and attributes. Such
user-defined items are still fully recognised, displayed and handled
by the standard application functions.
Topological information, such as connections from pipelines, HVAC
lines or cables to equipment items, and offline instrument
connections to various fittings, is captured and represented in the
data model. The offline instruments can also provide a link between
a main process system and a related control system.
System
Schematic Group
Equipment
Pipeline/
HVACline
Nozzle
Branch
Diagram
Offline Instrument
Instrument
Cable
Page 5
The role of a schematic model for system design coordination - an AVEVA White Paper
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
function for design managers to approve and set release status for a
system, a diagram, or parts thereof. Setting the release status
provides a signal to the 3D designers that the schematic
information is now ready to be used as a base for the 3D design.
The applications also contain functions for visualising the releaseand 3D-usage status, as well as warning or restraining the user from
modifying released data. Already released design information can
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.
Global
Synchronisation
Schematic Model
Viewer
Product Model DB
Spreadsheet
Import/Export
P&ID Manager
Schematic
Data
Schematic 3D
Integrator
3D Design
Data
Customisation APIs
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
Figure 4: The schematic model viewer can show a view of all systems connected to
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
Figure 6: The initial view created by the viewer shows the selected item together
with all connected items and generic branching points
Figure 7: Schematic Model Viewer showing valves and inline fittings at detail
level
Page 9
The role of a schematic model for system design coordination - an AVEVA White Paper
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
accomplished by tight online working against the database, where
items are created automatically as they are drafted on the diagram,
or in an offline fashion, where data can be imported from other
authoring tools.
This flexibility can support a distributed way of working with
partners, contractors, subcontractors, vendors and system
suppliers. The resulting set of data in the schematic model database
can be verified and consolidated by using the Schematic Model
Viewer, as well as the checking capabilities of P&ID Manager,
miscellaneous reports and other tools. This makes it possible to
ensure that all related data is complete and consistent.
The schematic model database also provides a base for the 3D
model, where schematic data can be reused on the 3D side.
However, a more concurrent working mode often has to be used
because of time constraints. In this case, the schematic model can
be of use anyway, to retrospectively check that the 3D model fulfils
the system design intent.
If the schematic model database is kept up to date with all changes
introduced, it can also provide a schematic as-built documentation
of the project, which can easily be navigated using the schematic
model viewer. This includes the possibility for other project
reporting functions or in-service and onboard applications.
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
Americas Region
Headquarters
AVEVA Inc
10350 Richmond Avenue
Suite 400
Houston, Texas 77042
USA
AVEVA GmbH
Otto-Volger-Str.7c
D-65843 Sulzbach
GERMANY
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