AVEVA ERM-Design Integration User Guide For AVEVA Marine

AVEVA ERM-Design Integration
User Guide for AVEVA Marine

Disclaimer
1.1 AVEVA does not warrant that the use of the AVEVA software will be uninterrupted, error-free or free from viruses.
1.2 AVEVA shall not be liable for: loss of profits; loss of business; depletion of goodwill and/or similar losses; loss of
anticipated savings; loss of goods; loss of contract; loss of use; loss or corruption of data or information; any special,
indirect, consequential or pure economic loss, costs, damages, charges or expenses which may be suffered by the
user, including any loss suffered by the user resulting from the inaccuracy or invalidity of any data created by the
AVEVA software, irrespective of whether such losses are suffered directly or indirectly, or arise in contract, tort
(including negligence) or otherwise.
1.3 AVEVA's total liability in contract, tort (including negligence), or otherwise, arising in connection with the
performance of the AVEVA software shall be limited to 100% of the licence fees paid in the year in which the user's
claim is brought.
1.4 Clauses 1.1 to 1.3 shall apply to the fullest extent permissible at law.
1.5 In the event of any conflict between the above clauses and the analogous clauses in the software licence under
which the AVEVA software was purchased, the clauses in the software licence shall take precedence.
Copyright
Copyright and all other intellectual property rights in this manual and the associated software, and every part of it
(including source code, object code, any data contained in it, the manual and any other documentation supplied
with it) belongs to, or is validly licensed by, AVEVA Solutions Limited or its subsidiaries.
All rights are reserved to AVEVA Solutions Limited and its subsidiaries. The information contained in this document is
commercially sensitive, and shall not be copied, reproduced, stored in a retrieval system, or transmitted without the
prior written permission of AVEVA Solutions Limited. Where such permission is granted, it expressly requires that
this copyright notice, and the above disclaimer, is prominently displayed at the beginning of every copy that is made.
The manual and associated documentation may not be adapted, reproduced, or copied, in any material or electronic
form, without the prior written permission of AVEVA Solutions Limited. The user may not reverse engineer,
decompile, copy, or adapt the software. Neither the whole, nor part of the software described in this publication
may be incorporated into any third-party software, product, machine, or system without the prior written
permission of AVEVA Solutions Limited, save as permitted by law. Any such unauthorised action is strictly prohibited,
and may give rise to civil liabilities and criminal prosecution.
The AVEVA software described in this guide is to be installed and operated strictly in accordance with the terms and
conditions of the respective software licences, and in accordance with the relevant User Documentation.
Unauthorised or unlicensed use of the software is strictly prohibited.
Copyright 2003 to current year. AVEVA Solutions Limited and its subsidiaries. All rights reserved. AVEVA shall not be
liable for any breach or infringement of a third party's intellectual property rights where such breach results from a
user's modification of the AVEVA software or associated documentation.
AVEVA Solutions Limited, High Cross, Madingley Road, Cambridge, CB3 0HB, United Kingdom.
Trademarks
AVEVA and Tribon are registered trademarks of AVEVA Solutions Limited or its subsidiaries. Unauthorised use of the
AVEVA or Tribon trademarks is strictly forbidden.
AVEVA product/software names are trademarks or registered trademarks of AVEVA Solutions Limited or its
subsidiaries, registered in the UK, Europe and other countries (worldwide).
The copyright, trademark rights, or other intellectual property rights in any other product or software, its name or
logo belongs to its respective owner.
Page 2
© Copyright 2003 to current year. AVEVA Solutions Limited and its subsidiaries. All rights reserved.
AVEVA ERM-Design Integration
User Guide for AVEVA Marine
Contents Page
1 Preface
..................................................................................................................... 10
1.1 ..............................................................................................................................
About This Document 10
1.2 .............................................................................................................................. 11
Audience
1.3 ..............................................................................................................................
Summary of Chapters 11
1.4 Product
..............................................................................................................................
Training Information 12
1.5 ..............................................................................................................................
Technical Support 12
2 Introduction
..................................................................................................................... 14
2.1 ..............................................................................................................................
Overview of AVEVA ERM-Design Integration 14
2.2 Integration
..............................................................................................................................
Supported 17
2.3 ..............................................................................................................................
Notification Workflow Overview 18
2.4 ..............................................................................................................................
Integration Concepts 19
2.4.1 Notification ...........................................................................................................
Filtering 20
2.4.2 Design Project Id
........................................................................................................... 20
2.4.3 Sent To Application
........................................................................................................... 21
2.4.4 External ...........................................................................................................
Reference Id 21
3 AVEVA.....................................................................................................................
ERM-Design Integration Capabilities 24
3.1 Handling
..............................................................................................................................
Multiple Projects 24
3.2 .............................................................................................................................. 25
Prevalidation
3.3 ..............................................................................................................................
Partial Import in AVEVA ERM 26
3.4 ..............................................................................................................................
Update/Rework Information on Part Lists 26
4 Software
.....................................................................................................................
Requirements 27
5 About.....................................................................................................................
Settings Dialog Box 28
6 Configuring
.....................................................................................................................
Design Application and AVEVA ERM for Integration 35
6.1 ..............................................................................................................................
Configuring Design Application for AVEVA ERM-Design Integration 35
6.1.1 Set Up Project for AVEVA ERM-Design Integration
........................................................................................................... 36
6.1.2 Set Up Admin Module
........................................................................................................... 36
6.1.3 Set Up ...........................................................................................................
Lexicon Module 41
6.1.4 Install...........................................................................................................
and Set Up AVEVA Integration Service 44
6.1.5 Configure Design Application for AVEVA Integration Service
........................................................................................................... 44
6.1.6 Set Up AVEVA Marine - Hull Design to Material Handling mode
........................................................................................................... 45
6.1.7 Set Up Work Package to Assembly Mapping in AVEVA Marine - Hull

........................................................................................................... 46
6.2 Configuring Design
..............................................................................................................................
AVEVA ERM for AVEVA ERM-Design Integration 46
Page 3
6.2.1 Configure Integration
........................................................................................................... 47
6.2.2 Configure Material Definition
........................................................................................................... 49
6.2.3 Configure
...........................................................................................................
Material Control 50
6.2.4 Set Up External Source Applications
........................................................................................................... 50
6.2.5 Set Up AVEVA Integration Service
........................................................................................................... 52
6.2.6 Set Up
...........................................................................................................
Drawing Catalogue and Part List 54
6.2.7 Set Up
...........................................................................................................
Projects 55
6.2.8 Set Up Material Type Defaults
........................................................................................................... 57
6.2.9 Set Up Fabricate Types
........................................................................................................... 58
7 List of.....................................................................................................................
Source Tables Used 59
8 About.....................................................................................................................
Material Mapping 61
8.1 Material
..............................................................................................................................
Category Mapping 62
8.2 ..............................................................................................................................
Supporting PML Functions 63
8.3 ..............................................................................................................................
Create a New Mapping 64
8.4 ..............................................................................................................................
Material Mapping Settings 65
8.5 Exporting
..............................................................................................................................
Material Category Mappings to Excel 66
9 Performing
.....................................................................................................................
Basic Tasks Using AVEVA ERM-Design Integration 67
9.1 ..............................................................................................................................
Processing Messages in AVEVA ERM 67
9.2 ..............................................................................................................................
Importing Data in AVEVA ERM Manually 68
9.3 Importing
..............................................................................................................................
Notifications Manually in Design Application 68
9.4 ..............................................................................................................................
Navigating to the Data in Design Application 69
10 Integration
.....................................................................................................................
with AVEVA Catalogue Manager 70
.............................................................................................................................. 70
10.1 Overview
10.2 Information
..............................................................................................................................
Transferred 71
10.2.1 Material Description
........................................................................................................... 71
10.2.2 Component ...........................................................................................................
Weight 72
10.2.3 Data ...........................................................................................................
from Bolt Table (applicable only for Bolt Specifications) 73
10.2.4 Specifications........................................................................................................... 73
..............................................................................................................................
10.3 Integration Workflow - Data Transfer from AVEVA Catalogue Manager 74
10.3.1 Approve ...........................................................................................................
or Republish Specifications in AVEVA Catalogue Manager 74
10.3.2 Verify...........................................................................................................
Locations for Importing Specifications 75
10.3.3 Import Specifications in Design Application
........................................................................................................... 75
10.3.4 View ...........................................................................................................
Specifications 76
10.3.5 Provide Feedback
........................................................................................................... 78
11 Standard
.....................................................................................................................
Material Integration 79
11.1 Concept
..............................................................................................................................
Description 79
..............................................................................................................................
11.2 Overview of Transfer Process 80
..............................................................................................................................
11.3 Information Transferred 81
..............................................................................................................................
11.4 Integration Workflow – Data Transfer to AVEVA ERM 81
11.4.1 Configure a filter for standard materials
........................................................................................................... 81
Page 4
11.4.2 Update the status of the standard materials
........................................................................................................... 83
11.4.3 Publish the standard materials
........................................................................................................... 83
11.4.4 Import...........................................................................................................
the standard materials into AVEVA ERM 83
11.4.5 Verify...........................................................................................................
the imported data in AVEVA ERM 84
11.4.6 Provide feedback on data processing in AVEVA ERM
........................................................................................................... 84
11.4.7 Process
...........................................................................................................
the feedback 85
..............................................................................................................................
11.5 Integration Workflow – Data Transfer from AVEVA ERM 85
11.5.1 Publish the standard materials in AVEVA ERM
........................................................................................................... 86
11.5.2 Import the standard materials
........................................................................................................... 87
11.5.3 Verify...........................................................................................................
the imported data 88
11.5.4 Provide ...........................................................................................................
feedback on data processing 88
11.5.5 Process the feedback in AVEVA ERM
........................................................................................................... 88
12 Raw Plates
.....................................................................................................................
Integration 89
..............................................................................................................................
12.1 Concept Description 89
..............................................................................................................................
12.3 Information
..............................................................................................................................
Transferred 90
..............................................................................................................................
12.4 Integration workflow – Data Transfer to AVEVA ERM 91
12.4.1 Configure ...........................................................................................................
a filter for the raw plates in AVEVA Marine 91
12.4.2 Update ...........................................................................................................
the status of the raw plates in AVEVA Marine 92
12.4.3 Publish the raw plates in AVEVA Marine
........................................................................................................... 92
12.4.4 Import the raw plates into AVEVA ERM
........................................................................................................... 92
12.4.5 Verify...........................................................................................................
data in AVEVA ERM 93
12.4.6 Provide ...........................................................................................................
feedback on data consumption in AVEVA ERM 93
12.4.7 Process the feedback in AVEVA Marine
........................................................................................................... 94
..............................................................................................................................
12.5 Integration workflow – Data Transfer from AVEVA ERM 94
12.5.1 Publish the raw plates in AVEVA ERM
........................................................................................................... 94
12.5.2 Import ...........................................................................................................
the raw plates in AVEVA Marine 95
12.5.3 Verify...........................................................................................................
data in AVEVA Marine 96
12.5.4 Provide feedback on data consumption in AVEVA Marine
........................................................................................................... 96
12.5.5 Process ...........................................................................................................
the feedback in AVEVA ERM 97
13 Raw Profile
.....................................................................................................................
Integration 98
13.1 Concept
..............................................................................................................................
Description 98
..............................................................................................................................
..............................................................................................................................
..............................................................................................................................
13.4 Integration Workflow – Data Transfer to AVEVA ERM 100
13.4.1 Configure a filter for the raw profiles in AVEVA Marine
........................................................................................................... 100
13.4.2 Update the status of the raw profiles in AVEVA Marine
........................................................................................................... 101
13.4.3 Publish ...........................................................................................................
the raw profiles in AVEVA Marine 101
13.4.4 Import ...........................................................................................................
the raw profiles into AVEVA ERM 102
13.4.5 Verify data in AVEVA ERM
........................................................................................................... 103
13.4.6 Provide feedback on data consumption in AVEVA ERM
........................................................................................................... 103
........................................................................................................... 103
..............................................................................................................................
13.5.1 Pre-setup steps in AVEVA ERM
........................................................................................................... 105
Page 5
13.5.2 Publish the raw profiles in AVEVA ERM
........................................................................................................... 105
13.5.3 Import the raw profiles in AVEVA Marine
........................................................................................................... 106
13.5.4 Verify
...........................................................................................................
data transferred in AVEVA Marine 109
........................................................................................................... 110
........................................................................................................... 110
14 System
.....................................................................................................................
Hierarchy Integration 111
..............................................................................................................................
14.2 Overview
..............................................................................................................................
of Transfer Process 113
..............................................................................................................................
..............................................................................................................................
14.4.1 Publish ...........................................................................................................
system hierarchy from AVEVA ERM 115
14.4.2 Import system hierarchy
........................................................................................................... 116
14.4.3 Provide feedback on data processing
........................................................................................................... 116
14.4.4 Process ...........................................................................................................
feedback in AVEVA ERM 117
15 Project
.....................................................................................................................
Component Integration 118
15.1 Concept
..............................................................................................................................
Description 118
..............................................................................................................................
..............................................................................................................................
..............................................................................................................................
15.4 Integration Workflow – Design Application to AVEVA ERM 120
15.4.1 Set up material type on EQUIPMENT
........................................................................................................... 121
15.4.2 Set up systems on EQUIPMENT
........................................................................................................... 121
15.4.3 Configure ...........................................................................................................
a filter for project components 123
15.4.4 Update ...........................................................................................................
the status of the project components 123
15.4.5 Publish the project components
........................................................................................................... 124
15.4.6 Import the project components in AVEVA ERM
........................................................................................................... 124
15.4.7 Verify the imported data in AVEVA ERM
........................................................................................................... 125
15.4.8 Provide ...........................................................................................................
feedback on data processing in AVEVA ERM 125
15.4.9 Process the feedback
........................................................................................................... 125
..............................................................................................................................
15.5 Integration Workflow – AVEVA Engineering to AVEVA ERM 126
15.5.1 Set up ERMCategory for tags in AVEVA Engineering
........................................................................................................... 126
15.5.2 Set up ...........................................................................................................
systems in AVEVA Engineering 126
15.5.3 Update status of Equipment in AVEVA Engineering
........................................................................................................... 127
15.5.4 Set up AVEVA ERM to import data from AVEVA Engineering
........................................................................................................... 127
15.5.5 Import ...........................................................................................................
data into AVEVA ERM 127
15.5.6 Verify ...........................................................................................................
the imported data in AVEVA ERM 127
15.6 Integration
..............................................................................................................................
Workflow – AVEVA ERM to AVEVA Engineering 128
15.6.1 Publish the project components in AVEVA ERM
........................................................................................................... 128
15.6.2 Import ...........................................................................................................
the project components in AVEVA Engineering 128
16 Transfer
.....................................................................................................................
of Advance Bill of Material from AVEVA Diagrams to AVEVA 129
ERM
16.1 Concept
..............................................................................................................................
Description 129
..............................................................................................................................
Page 6
..............................................................................................................................
..............................................................................................................................
16.4 Integration Workflow - Data Transfer to AVEVA ERM 130
16.4.1 Update ...........................................................................................................
the status of ABoM 131
16.4.2 Import ABoM data in AVEVA ERM
........................................................................................................... 131
........................................................................................................... 132
17 Part List
.....................................................................................................................
Integration 133
..............................................................................................................................
17.2 Overview
..............................................................................................................................
of Transfer Process 134
17.3 Pipe..............................................................................................................................
and HVAC Spool 135
17.3.1 Information ...........................................................................................................
Transferred 135
17.3.2 Integration ...........................................................................................................
Workflow - Data Transfer to AVEVA ERM 135
17.4 Fabricates
.............................................................................................................................. 140
17.4.1 Information Transferred
........................................................................................................... 140
17.4.2 Integration ...........................................................................................................
Workflow – Data Transfer to AVEVA ERM 141
..............................................................................................................................
17.5 Outfitting Part List 145
........................................................................................................... 145
17.5.2 Integration workflow - Data Transfer to AVEVA ERM
........................................................................................................... 147
18 Hull Material
.....................................................................................................................
Control 151
..............................................................................................................................
18.2 Concept
..............................................................................................................................
Description 151
..............................................................................................................................
18.3 Synchronize Hull Plates and Profiles Catalogue 153
18.4 Hull..............................................................................................................................
Units 153
18.4.1 Information ...........................................................................................................
Transferred 153
18.4.2 Integration Workflow – Data Transfer to AVEVA ERM
........................................................................................................... 154
..............................................................................................................................
18.5 Allocating Material for Nesting 158
........................................................................................................... 158
18.5.2 Integration ...........................................................................................................
Workflow - Data Transfer from AVEVA ERM 159
18.6 Nesting
..............................................................................................................................
Information 163
........................................................................................................... 163
........................................................................................................... 164
..............................................................................................................................
18.7 Publish Actual Material Usage to AVEVA ERM 168
18.7.1 Concept Description
........................................................................................................... 168
........................................................................................................... 170
18.7.3 Integration Workflow - Data Transfer to AVEVA ERM
........................................................................................................... 170
19 AVEVA
.....................................................................................................................
ERM Planning and Assembly Planning 177
19.1 Concept
..............................................................................................................................
Description 177
..............................................................................................................................
19.2 Transfer AVEVA ERM Work Packages to AVEVA Marine 177
19.2.1 Information ...........................................................................................................
Transferred 178
19.2.2 Integration ...........................................................................................................
Workflow – Data Transfer from AVEVA ERM 179
19.3 Outfitting
..............................................................................................................................
Assembly Part List 183
........................................................................................................... 184
19.3.2 Integration ...........................................................................................................
Workflow - Data Transfer to AVEVA ERM 185
Page 7
..............................................................................................................................
19.4 Transfer Hull Plate and Profile Part List from AVEVA Marine to AVEVA ERM 191
19.4.1 Information ...........................................................................................................
Transferred 192
19.4.2 Integration ...........................................................................................................
Workflow – Data Transfer to AVEVA ERM 193
20 Deletion
..................................................................................................................... 200
..............................................................................................................................
..............................................................................................................................
20.2 Delete Workflow (Initiated in Design Application) 201
20.2.1 Design ...........................................................................................................
application sends CanDeleteRequest 202
20.2.2 AVEVA ERM processes CanDeleteRequest
........................................................................................................... 203
20.2.3 Design application processes

........................................................................................................... 204
CanDeleteAcknowledgement/CanDeleteError
20.2.4 AVEVA ERM processes Delete
........................................................................................................... 204
..............................................................................................................................
20.3 Delete Workflow (Initiated in AVEVA ERM) 205
20.3.1 AVEVA ...........................................................................................................
ERM sends CanDeleteRequest 205
20.3.2 Design application processes CanDeleteRequest
........................................................................................................... 206
20.3.3 AVEVA ERM processes CanDeleteAcknowledgement/CanDeleteError 206
...........................................................................................................
20.3.4 Design ...........................................................................................................
application processes Delete 207
21 View.....................................................................................................................
AVEVA ERM Data in Design 208
21.1 Overview
.............................................................................................................................. 208
..............................................................................................................................
21.2 Only ERM configured 209
..............................................................................................................................
21.3 Both AVEVA NET and ERM configured 209
..............................................................................................................................
21.4 View Live Data as Pseudo Attributes 210
Page 8
Page 9
AVEVA ERM-Design Integration User Guide for AVEVA Marine
CHAPTER 1 - Preface
1 Preface
This chapter provides an introduction to this guide, specifies the intended audience,
provides the summary of chapters and lists the related documents for the guide. The
chapter also provides information about product training and how to contact technical
support.
1.1 About This Document

The AVEVA ERM-Design Integration User Guide for AVEVA Marine™ describes the transfer
of different material information between AVEVA Marine and AVEVA Enterprise Resource
Management™ (AVEVA ERM™) and how the integration between the systems is done.
The guide contains information about the following:

· Overview of AVEVA ERM-Design Integration
· Configuring AVEVA Marine for AVEVA ERM-Design Integration
· Configuring AVEVA ERM for AVEVA ERM-Design Integration
· Notification mechanism used in AVEVA ERM-Design Integration
· Concepts and workflows related to the following:
o Integration with AVEVA Catalogue Manager™
o Standard material integration
o Raw plates integration
o Raw profiles integration
o Systems integration
o Project component integration
o Advance Bill of Material(ABoM) integration, if you have AVEVA Diagrams™
o Outfitting integration
§ Fabricates (steel structure) integration
§ Pipe and HVAC spool integration
§ Outfitting part list integration
o Hull material handling
§ Hull unit integration
§ Allocation of plates and profiles for nesting
§ Integrating nesting information
§ Hull actual material usage
Page 10
CHAPTER 1 - Preface
§ Hull plate and profile part list integration

o AVEVA ERM planning and assembly planning
§ Transfer of AVEVA ERM work packages to AVEVA Marine
§ Integration of outfitting assembly part list
o Integration of delete operations for standard materials, raw plates, raw
profiles and project components
1.2 Audience
This guide is intended for users who are responsible for configuring and using AVEVA
ERM-Design Integration. The guide assumes that you have the functional and technical
knowledge in using AVEVA Marine, AVEVA ERM, AVEVA Engineering™, AVEVA Diagrams
and AVEVA Integration Service™.
1.3 Summary of Chapters

The following table contains the summary of chapters in this guide.
Chapter Summary
Introduction Contains an introduction to AVEVA ERM-Design Integration,
the list of concepts for which the integration is supported
and an overview of the notification workflow.
AVEVA ERM-Design Describes the various capabilities of AVEVA ERM-Design
Integration Capabilities Integration.
Software Requirements Contains the software requirements for installing and using
AVEVA ERM-Design Integration.
About Settings Dialog Box Provides information about the Settings dialog box in AVEVA
Marine through which most configurations are made.
Configuring Design Contains procedures for enabling AVEVA Marine and AVEVA
Application and AVEVA ERM for integration.
ERM for Integration
List of Source Tables Contains the list of source tables used for integration.
Used
About Material Mapping Explains the Material Category concept and contains
procedures for setting up material category mapping in
AVEVA Marine.
Performing Basic Tasks Contains procedures for performing some of the basic tasks
Using AVEVA ERM-Design for using AVEVA ERM-Design Integration.
Integration
Integration with AVEVA Describes the workflow for importing data from AVEVA
Catalogue Manager Catalogue Manager.
Page 11
CHAPTER 1 - Preface
Chapter Summary
Standard Material Describes the concept and provides the workflow for
Integration transferring standard materials.
Raw Plates Integration Describes the concept and provides the workflow for
transferring raw plates.
Raw Profile Integration Describes the concept and provides the workflow for
transferring raw profiles.
System Hierarchy Describes the concept and provides the workflow for
Integration transferring system hierarchies.
Project Component Describes the concept and provides the workflow for
Integration transferring project components.
Transfer of Advance Bill Describes the concept and provides the workflow for
of Material from AVEVA transferring Advance Bill of Material (ABoM) data from
Marine to AVEVA ERM AVEVA Marine to AVEVA ERM.
Part List Integration Describes the concept and provides workflows for
transferring pipe spools, HVAC spools, fabricates and
outfitting part lists.
Hull Material Control Describes the concept and provides workflows for
transferring hull units, allocating material for nesting, nesting
information and publishing actuals to AVEVA ERM.
AVEVA ERM Planning and Describes the concept and provides workflows for
Assembly Planning transferring AVEVA ERM work packages to AVEVA Marine,
and integrating outfitting assembly part lists and hall plate
and profile part lists from AVEVA Marine to AVEVA ERM.
Deletion Describes the concept and provides the worklow for delete
operations.
View AVEVA ERM Data in Contains procedures for viewing AVEVA ERM data in Design.
Design
1.4 Product Training Information

For information about product training courses, see the Product Training section of
AVEVA's website (http://www.aveva.com/training), or contact the nearest AVEVA
Regional Support Centre (http://support.aveva.com/support).
1.5 Technical Support

If you encounter software issues or have suggestions for software improvements, contact
AVEVA Helpdesk (https://avevahelpdesk.aveva.com), and register a support incident.
Page 12
CHAPTER 1 - Preface
After you register a support incident, we will know your identity (from your customer ID)
and the details of the incident. We will endeavour to fix the software issue or consider
the software improvement suggestion as soon as possible, and notify you about the
status of the incident.
If you are an accredited user of the AVEVA products, you are entitled to use AVEVA
Helpdesk for which you should have valid login credentials. For any other queries, contact
the nearest AVEVA Regional Support Centre (http://support.aveva.com/support).
Page 13
CHAPTER 2 - Introduction
2 Introduction
This section contains an introduction to AVEVA ERM-Design Integration.
2.1 Overview of AVEVA ERM-Design Integration

AVEVA ERM-Design Integration provides easy and effective transfers of material
information between AVEVA Marine and AVEVA ERM. AVEVA ERM-Design Integration
uses a robust notification mechanism that helps in seamless interactions between the
sender and receiver applications and thus ensures effective transfers of data.
You can access AVEVA ERM-Design Integration as shown in the following images.
Hull Design module
Page 14
Outfitting module
Page 15
Paragon module
The options in the AVEVA ERM Integration menu can be used in the following ways:
Option Function
Settings Use to configure the settings for the integration. For more
information, see About Settings Dialog Box.
Material Category Use to map the material categories in AVEVA Marine and
Mapping AVEVA ERM. For more information, see About Material
Mapping.
Publish to AVEVA ERM Use to publish data to AVEVA ERM.
Notifications Use to view the notifications received from AVEVA ERM.
Page 16
2.2 Integration Supported

The list of concepts supported by AVEVA ERM-Design Integration for AVEVA Marine is as
follows:
· Importing data from AVEVA Catalogue Manager
· Transfer of standard materials between AVEVA Marine–Paragon and AVEVA ERM
· Transfer of raw plates between AVEVA Marine–Paragon and AVEVA ERM
· Transfer of raw profiles between AVEVA Marine–Paragon and AVEVA ERM
· Transfer of systems from AVEVA ERM to AVEVA Marine
· Transfer project components from AVEVA Engineering to AVEVA ERM
· Transfer of Advance Bill of Materials (ABoM) information from AVEVA Diagrams
to AVEVA ERM
· Transfer part list information from AVEVA Marine–Outfitting to AVEVA ERM
o Outfitting part list
o Pipe spool part list
o HVAC spool part list
o Fabricate part list
· Transfer Hull material information from AVEVA Marine–Hull Design to AVEVA
ERM
o Hull units
o Hull plate and profile part list information
o Nesting information
· Transfer of steel reservation information between AVEVA Marine and AVEVA
ERM
· AVEVA ERM planning and assembly planning
o Transfer of AVEVA ERM work packages to AVEVA Marine
o Integration of outfitting assembly part list
· Integration of delete operations for standard materials, raw plates, raw profiles
and project components
Page 17
2.3 Notification Workflow Overview

AVEVA ERM-Design Integration uses a notification mechanism that helps to improve the
transfer of data between AVEVA Marine and AVEVA ERM. Notification Service of AVEVA
Integration Service is used to send and receive notifications.
When the sending system publishes a change, an ‘Update’ notification is sent to the
receiver system using the notification mechanism. The receiver system can process this
notification by fetching the corresponding data and importing it. If data is successfully
imported, an ‘Acknowledgement’ notification is sent back to the sending system. In the
case of an error during import, an ‘Error’ notification is sent. Both ‘Acknowledgement’
and ‘Error’ notifications contain information about the data in such way that the sending
system can also update the published status of the data. In this way, data already
transferred will not be sent again until it is changed and re-published.
Currently, the following scenarios are possible:

· AVEVA Marine to AVEVA ERM
Page 18
· AVEVA ERM to AVEVA Marine
2.4 Integration Concepts

This section describes the following concepts used in integration:
· Notification Filtering
· Design Project Id
· Sent to Application
· External Reference Id
Page 19
2.4.1 Notification Filtering

In AVEVA Marine, notifications are filtered on Project user logged on and Application
Name (as identified in AVEVA ERM in screen s14001). An AVEVA Marine user has access
only to the notifications of the Project user logged on.
2.4.2 Design Project Id

Based on the project definition in the s10001 Projects screen, an AVEVA ERM project
(ABC) has a relation to an integration design project (Design-ABC). This is a one-to-one
relation. Design Project Id information is transferred between AVEVA Marine and AVEVA
ERM together with all the concepts. Design Project information is present in the
notification summary and in the details of the data exposed between system.
Concepts like RawPlate, RawProfile and StandardMaterial are not project specific in
AVEVA ERM. For this reason, when any of these concepts are published from AVEVA ERM,
the ‘Update’ notification generated will not have any value for Design Project. All the
others integration concepts published from AVEVA ERM to AVEVA Marine, are project
specific. When the data is published for project ABC, and Update notification is generated
with Design Project Id (Design-ABC).
Page 20
When an ‘Update’ notification is received in AVEVA ERM from AVEVA Marine, the
‘Acknowledgement’ or ‘Error’ notification that AVEVA ERM generates as an answer
contains the design project that was on the data from ‘Update’ notification. This applies
to all concepts supported in the integration.
2.4.3 Sent To Application

Records defined in AVEVA ERM in the s14001 Integration Service screen for different
transfer concepts contain the application information. From the perspective of AVEVA
ERM, the application to which a notification is sent (‘Sent To Application’) is decided
based on design project and (transfer) concept Id, according to the configuration defined
in the s14001 Integration Service screen for this project and concept Id.
When a record in s14001 Integration Service screen for the service infrastructure Id and
design project cannot be identified, the notification is sent to the application defined as
default in the s00033 External Source Applications screen.
2.4.4 External Reference Id

ExternalReferenceId information represents the dabaconid value as known in AVEVA
Marine for an element. This information is transferred and stored in AVEVA ERM and is
used for identification of the element.
The following concepts support this feature: Standard material, project component, raw
plate, raw profile, drawing, design specification, fabricate and hull unit.
Example 1: Standard Material created and published from AVEVA ERM and imported in
AVEVA Marine.
Step 1: Create and publish a new standard material in AVEVA ERM. An ‘Update’
notification is generated from AVEVA ERM to AVEVA Marine with the number of
components available.
Page 21
Step 2: AVEVA Marine processes the ‘Update’ notification, queries the data from AVEVA
ERM and imports data into AVEVA Marine.
Step 3: AVEVA Marine generates an ‘Acknowledgement’ or ‘Error’ notification. Both

types of notifications include a value in ExternalReferenceId corresponding to the
dabaconid of the components.
Step 4: AVEVA ERM automatically processes the ‘Acknowledgement’ or ‘Error’

notification and updates the value of External Reference for the element.
For all the concepts supporting this feature, the External Reference information can be
verified in AVEVA ERM in the Integration tab in the External Reference field.
Example 2: Standard material created and published from AVEVA Marine. When
standard materials are published from AVEVA Marine, External Reference is part of the
information exported, and mapped into the import run in AVEVA ERM and this way, the
elements are created with External Reference information.
External Reference feature is applicable to AVEVA ERM 13.0 and later and AVEVA Marine
SP5 Fix1 and later. If you are using a version prior to these, you need to synchronise the
data manually.
For this purpose, a manual import needs to be run in AVEVA ERM. For more information
on how to run a manual import, see Importing Data in AVEVA ERM Manually.
Page 22
After running this synchronization, AVEVA ERM will be updated with all the missing
External References for the concepts that were already transferred. This will allow a
proper identification of data already transferred when present in any further updates.
This synchronization should be run only once, and no notification was implemented for
the transfer. Details about the updates applied can be seen in the s22050 Data Import
screen in the Audit Summary and Audit Detail sections.
Page 23
CHAPTER 3 - AVEVA ERM-Design Integration Capabilities
3 AVEVA ERM-Design Integration Capabilities

AVEVA ERM-Design Integration provides capabilities for the following tasks while
transferring data:
· Handling of multiple projects
· Prevalidation in AVEVA Marine
· Partial Import
· Update/rework information on part lists
3.1 Handling Multiple Projects

AVEVA ERM-Design Integration uses the following information in handling multiple
projects:
· Integration Design Project Id: Integration Design Project Id (or, design project Id)
defined in s10001 Projects
· Integration Details: Integration details defined in s14001 Integration Service
Based on the project definition in the s10001 Projects screen, an AVEVA ERM project has
a one-one relation to an integration design project. Design Project Id information is
transferred between AVEVA Marine and AVEVA ERM together with all the concepts.
Design Project information is present in the notification summary and in the details of the
data exposed between the systems.
The raw plate, raw profile and standard material concepts in AVEVA ERM are not project-
specific. For this reason, when these concepts are published from AVEVA ERM, the
‘Update’ notification generated will not contain a value for the Design Project Id. All the
others integration concepts published from AVEVA ERM to AVEVA Marine are project-
specific. When the data is published for a project, an Update notification that is generated
contains the Design Project Id. The ‘Acknowledgement’ or ‘Error’ notification that AVEVA
ERM generates as an answer to an 'Update' notification also contains the design project.
Records defined in AVEVA ERM in the s14001 Integration Service screen for different
transfer concepts contain the application information. From the perspective of AVEVA
ERM, the application to which a notification is sent (‘Sent To Application’) is decided
based on design project and (transfer) concept Id, according to the configuration defined
in the s14001 Integration Service screen for this project and concept Id.
Page 24
When a record in s14001 Integration Service screen for the service infrastructure Id and
design project cannot be identified, the notification is sent to the application defined as
default in the s00033 External Source Applications screen.
3.2 Prevalidation
During the transfer of data, AVEVA ERM rejects the import of data if any mandatory fields
are not set. To avoid publishing of invalid data, and to ensure successful publishing of
data to AVEVA ERM, a prevalidation is performed in AVEVA Marine before publishing the
data to AVEVA ERM.
Prevalidation looks for errors and warnings in a similar way as AVEVA ERM would if such
data would be transferred, and displays the errors in red and warnings in amber.
Data with errors cannot be published; the errors must be corrected before publishing the
data to AVEVA ERM. The following screenshot provides an example for an error.
Though data with warnings can be published to AVEVA ERM, the import may fail.
Therefore, the warnings must also be fixed before importing the data into AVEVA ERM.
Data sent with a warning is rejected by AVEVA ERM import unless the referred data is not
first imported into AVEVA ERM. The following screenshot provides an example for a
warning.
Page 25
3.3 Partial Import in AVEVA ERM

In general, only full imports are possible in AVEVA ERM, which means that if any error
occurs during an import, no data is imported. However, partial import is possible for
transfers of standard material, project component, outfitting, fabricate, pipe spool, HVAC
spool and steel structure concepts.
During a partial import, AVEVA ERM creates two notifications:

· An ‘Acknowledgement’ notification containing the information for the data that
was successfully imported
· An ‘Error’ notification containing the information for the data that could not be
successfully imported
3.4 Update/Rework Information on Part Lists

If AVEVA Marine has published a drawing or 3D-model (part list) information to AVEVA
ERM, and if, later, the drawing needs rework in AVEVA Marine, then updates on the
drawing (part list) are published to AVEVA ERM by publishing the drawing again. The
items that existed for a part list in the initial transfer but not present in the second set of
data are deleted from AVEVA ERM. Deletion of lists on drawing or 3D-model is supported
for Outfitting, Fabricate, Pipespool, HVACspool and SteelStructure transfers.
Acknowledgement or Error notifications are generated according to the results of the

import. If an Error notification is generated from AVEVA ERM because the updates were
not allowed, a manual process is needed to synchronise and clean up the data.
Page 26
CHAPTER 4 - Software Requirements
4 Software Requirements
This section contains the software requirements installing and using AVEVA ERM-Design
Integration.
The current version of AVEVA ERM-Design Integration is supported on the following
program versions:
• AVEVA Enterprise Resource Management (AVEVA ERM) 14.2
• AVEVA Marine 12.1.SP5 Fix 10
• AVEVA Integration Service 1.5.2
Page 27
CHAPTER 5 - About Settings Dialog Box
5 About Settings Dialog Box

The Settings dialog box contains the options to configure the settings of AVEVA ERM-
Design Integration and the integration process. You can perform the following tasks
through the Settings dialog box:
• Configure filters for transferring data to AVEVA ERM
• Define general settings needed for the integration process
• Specify settings for the mapping of components in AVEVA ERM to components in
your application
The navigation for the Settings dialog box in various modules is as follows:
· Outfitting: Display > AVEVA ERM Integration > Settings
· Hull Design: View > Addins > AVEVA ERM Integration > Settings
· Paragon: Display > AVEVA ERM Integration > Settings
The following image provides the user interface of the Settings dialog box.
Page 28
Filter Configuration
The Filter Configuration tab contains the settings to configure the components for
integration. User can provide any number of settings. The following fields are required for
each entry in the Filter Configuration tab:
UI Element Description
List Based On User defined name to differentiate between different settings.
Select Element The element type(s)for which the filter is being configured.
Type
Status Definition The status definition used for integration. Must always be "/
PublishingStatus".
Filtering Status The status of the elements at which they can be published to the
preview screen.
Publishing The status at which data is available to AVEVA ERM. Must be “/
Status Published” for all concepts except Hull Unit. For Hull Unit, the value
must be "/Identified".
Select Transfer The DB view or PML function through which data is made available to
List AVEVA ERM. Default DB views and PML functions are available for
each configuration.
Import & Material Mappings Settings
Note: This tab is available only in the Paragon module. For the Hull Design and Outfitting
modules, the Work Package To Assembly Mapping tab is available. For information about
this tab, see Work Package To Assembly Mapping.
Page 29
Through the Import & Material Mapping Settings tab, you can specify if you do not want
certain fields to be updated by AVEVA ERM. You can do this by selecting the required
check boxes. The attributes that you select in the Select fields to be protected from ERM
area are protected from any updates from AVEVA ERM sent to AVEVA Marine.
In the Fully Validated Status box, if you select any value other than “[Not in Use]”, the
components with that status cannot be updated by AVEVA ERM. For AVEVA ERM to
update the components, you must select the value "[Not in Use]". The following values
are available in the list of values (LoV): /preliminary, /valid
For information about Material Mapping Settings, see Material Mapping Settings.
Page 30
Import from AVEVA Catalogue Manager
Through this area, you can configure the locations for importing data from AVEVA
Catalogue Manager. For information on the types of data you can import and the
workflow used for the integration, see Integration with AVEVA Catalogue Manager.
To configure the locations:

1. For the Import Descriptions at box, select the location in the Catalogue
Explorer where you want to import the material descriptions. The material
descriptions must be imported to a Catalogue database (CATA) in the
Catalogue World. After selecting the location, click CE. The selected location is
added to the box.
Note: The location for the material descriptions can be set only to a top level
CATA element in the Catalogue World.
2. For the Import Weights at box, select the location in the Catalogue Explorer
where you want to import the weights. The weights must be imported to a
Property database (PROP) in the Property World. After selecting the location,
click CE. The selected location is added to the box.
Note: The location for the weights can be set only to a top level PROP element
in the Property World.
3. For the Import Bolts at box, select the location in the Catalogue Explorer
where you want to import the bolts. The bolts must be imported to a
Catalogue database (CATA) in the Catalogue World. After selecting the
location, click CE. The selected location is added to the box.
Note: The location for the bolts can be set only to a top level CATA element in
the Catalogue World.
4. For the Import Specifications at box, select the location in the Catalogue
Explorer where you want to import the specifications. The specifications must
be imported to a Specification World (SPWL) in the Catalogue World. After
selecting the location, click CE. The selected location is added to the box.
Note: The location for the specifications can be set only to a top level SPWL
element in the Catalogue World.
Page 31
Work Package To Assembly Mapping
The Work Package to Assembly Mapping tab is available in the Hull Design and Outfitting
modules. You can use the tab to map a work package in AVEVA ERM to an assembly in
AVEVA Marine. To map a work package to an assembly, select the work package from the
hierarchy, and select the required assembly in the Assembly Type in AVEVA Planning list
and click Add. The mapping is added to the grid. To delete the selected mapping from the
grid, click Delete.
Page 32
Integration Service
You must configure AVEVA Integration Service to transfer data between AVEVA Marine
and AVEVA ERM.
The Integration Service tab of the Settings screen is used for configuring AVEVA
Integration Service.
Page 33
Integration Service Settings
Service Installed Machine name of the computer on which AVEVA Integration Service is
On installed.
Port Port number to which the Service must connect to.
Service URL The link to the Service used for integration. To validate the Service
URL, click Test.
DataSource Data source type in AVEVA Integration Service. Must be set to AVEVA
Type ERM.
DataSource Name of the data source in AVEVA Integration Service.
Table
Load data If selected, automatically loads data in the Notifications screen if the
automatically if count is less than the number specified. The default value is 200.
elements are
less than
Notification Service Settings
Service Installed
Machine name of the computer on which AVEVA Notification Service
On
is installed.
Port Port number to which the Service must connect to.

Service URL The link to the Service used for sending and receiving notifications. To
validate the Service URL, click Test.
Time Interval Time interval in minutes to fetch notifications. The default value is 1.
(Minutes)
Sent To The application to which the notifications must be sent. Must be set
Application to AVEVA ERM.
Sent From The name of the application from which data is transferred. Used for
Application sending and receiving notifications to and from AVEVA ERM.
Auto delete If selected, handled messages are deleted automatically depending on
when handled the message count set. The default value is 10.
messages are
more than
Page 34
CHAPTER 6 - Configuring Design Application and AVEVA ERM for Integration
6 Configuring Design Application and AVEVA ERM for

Integration
Before using AVEVA ERM-Design Integration, the following configurations must be made
for AVEVA Marine and AVEVA ERM:
For AVEVA Marine:

· Set up Marine project for AVEVA ERM-Design Integration
· Set up AVEVA Administration
· Set up Lexicon
· Install and set up AVEVA Integration Service
· Configure AVEVA Marine for AVEVA Integration Service
· Set up AVEVA Marine - Hull Design to Material Handling mode
· Set up Work Package to Assembly mapping in AVEVA Marine - Hull Design
For AVEVA ERM:

· Configure integration
· Configure material definition
· Configure material control
· Set up external source applications
· Set up AVEVA Integration Service
· Set up drawing catalogue and part list
· Set up projects
· Set up material type defaults
· Set up fabricate types
6.1 Configuring Design Application for AVEVA ERM-Design

Integration
This section describes the configurations that must be made for AVEVA Marine to start
using AVEVA ERM-Design Integration.
Page 35
6.1.1 Set Up Project for AVEVA ERM-Design Integration

The stages in setting up a project are as follows:
· Set the environment variables for the project.
· In AVEVA Administration, launch the Admin module as SYSTEM, and create the
Dictionary database and include it in the MDB in the project.
· In AVEVA Administration, launch the Lexicon module, run the macro scripts
supplied with the product.
6.1.2 Set Up Admin Module

Before running the integration process for the first time, you need to create a dictionary
database in the Admin module of AVEVA Administration to provide necessary data
structures for additional attributes, status and view definitions. You may also need to
perform some fine tuning of the mapping tables and PML scripts.
Page 36
In the Admin module, you need to perform the following tasks to start using AVEVA ERM-
Design Integration:
· Set the access of Properties database to Read/Write to allow for the creation of
CMPW and CMPT objects.
· Create a separate Dictionary database for the user defined attributes (UDAs) and
status definitions for the Catalogue integration.
To set the access of Properties database to read/write:

1. In AVEVA Administration, launch the Admin module as SYSTEM user or
equivalent.
2. Click Project and then select Module Definitions.
Page 37
3. From the Modules area of the Module Definition dialog box, select PARAGON
from the list of available modules.
Page 38
4. From the Settings area of the Module Definition dialog box, click Advanced
Settings. The Advanced Module Settings dialog box is displayed.
5. For the Properties list, select the Read/Write option.

6. Click Apply to apply the advanced module settings.
After the database properties have been configured for read/write access, you must
create a separate Dictionary database for the user defined attributes (UDAs) and status
definitions for the Catalogue integration.
Page 39
To create a dictionary database:

1. Create a new database with name ERM Integration, and then set the type to
Dictionary.
2. Click Modify. The Modify Database: MASTER/<Database Name> window is
displayed.
3. Modify the database as required.

4. Click Apply to apply the changes.
Page 40
5. Select the MDB, and then click Modify.
6. On the Modify Multiple Database: ALLMAS window, make sure the database
created is included in the correct MDBs.
7. Click Apply to apply the changes.
6.1.3 Set Up Lexicon Module

The Lexicon module allows the administrator to take complete control of the
administration of the Dictionary (DICT) database of a project. The Dictionary databases
contain the definitions of User Defined Attributes (UDAs), User Default Element Types
(UDETs), User System Defined Attributes (USDAs) and Database View Element(DBVW) as
set up in Lexicon. The Command window allows the administrator to maintain the
Dictionary database through the use of a command line interface.
Important: If you have upgraded AVEVA Marine, you must rerun the latest Lexicon scripts
to continue to use AVEVA ERM-Design Integration.
Page 41
Notes About DB views and PML functions
To facilitate advanced selection criteria and data output, DB views have been replaced
with PML functions for integrating data. The following points must be noted about the
usage of DB views and PML functions.
New User: If you are a new user of AVEVA ERM-Design Integration, the PML functions are
used for integration by default. To avoid complexities, DB views must not be used for new
installations. For this purpose, you must not run the IntegrationSetup_DbViews.dat
macro even though it is available in the same location as the other macros. If you run this
macro, then DB views are created and the same will be used for integration.
Nevertheless, you can switch back to PML functions if you delete the DB views from your
project location.
Existing User: If you are an existing user, DB views are used for integration by default. To
switch to PML functions, you must delete the DB views from your project location.
When both PML functions and DB views are available for a concept, AVEVA ERM-Design
Integration uses DB views to store and retrieve data. When using PML functions, you
must make sure that AVEVA ERM is configured to work in the PML Safe mode. If using DB
views, then configure AVEVA ERM to work in the Non PML Safe mode. For more
information, see the screen help for s14001 Integration Service in AVEVA ERM.
Page 42
To set up Lexicon for AVEVA ERM-Design Integration:

1. Start AVEVA Administration, and launch the Lexicon module as a SYSTEM user
or equivalent.
2. Click Display > Command Window to display the Command window.
3. Run the following Lexicon macros. By default, these macros are placed in the
C:\AVEVA\Marine\OH12.1.SP5\ERMIntegration\LexiconMacros
location during installation.
Important: If you have upgraded AVEVA Marine, you must rerun the latest
Lexicon scripts to continue to use AVEVA ERM-Design Integration.
i. When using PML functions to store and retrieve data, run the macro
IntegrationSetup_UDAs.dat and restart Lexicon.
ii. When using DB views to store and retrieve data, run the macro
IntegrationSetup_LexiconMacros.dat. This macro will in turn execute
the IntegrationSetup_UDAs.dat and
IntegrationSetup_DbViews.dat macros.
This will create the UDAs, UDETs, Status definitions required for the
integration. The Dictionary Explorer is displayed as follows:
Page 43
4. For data transfers from AVEVA Engineering and AVEVA Diagrams, run the
following macros.
o IntegrationSetup_Engineering.dat
o IntegrationSetup_DiagramSetUp.dat
The Dictionary Explorer is displayed as follows:
6.1.4 Install and Set Up AVEVA Integration Service

Refer to the AVEVA Integration Service Installation Guide and AVEVA Integration Service
Setup Guide for steps on installing and configuring AVEVA Integration Service.
6.1.5 Configure Design Application for AVEVA Integration Service

You must configure AVEVA Integration Service in AVEVA Marine to use the integration
related features. AVEVA Integration Service configuration can be set up using the Settings
dialog box.
Page 44
To configure AVEVA Integration Service for AVEVA ERM-Design Integration:

· On the Settings dialog box, click the Integration Service tab.
Make sure that the elements on the tab are set appropriately. For more information, see
Integration Service.
6.1.6 Set Up AVEVA Marine - Hull Design to Material Handling mode

The FMTRPO element should be created in Hull Design to switch nesting into material
handling mode required to integrate with AVEVA ERM.
Page 45
6.1.7 Set Up Work Package to Assembly Mapping in AVEVA Marine - Hull Design
You must set up Work Package to Assembly Mapping for Steel and NonSteel disciplines.
The root node for this assembly structure is defined in the receiving side (ERM Integration
settings). It is to create the Work Package structure on a sub-assembly node in the
assembly structure. For more information, refer to the user guides of AVEVA Marine.
6.2 Configuring AVEVA ERM for AVEVA ERM-Design Integration

This section describes the configurations that must be made for AVEVA ERM to start
using AVEVA ERM-Design Integration.
Page 46
6.2.1 Configure Integration

You must configure AVEVA ERM-Design Integration in AVEVA ERM to use it with AVEVA
ERM.
Note: Prior to using AVEVA ERM-Design Integration in AVEVA ERM, make sure that the
data source type is defined for AVEVAMARINE or AVEVADESIGN in the s00033 External
Source Applications screen. For more information, see Set Up External Source
Applications.
To configure AVEVA ERM-Design Integration in AVEVA ERM:

1. Start AVEVA ERM.
2. Click Administration and then select Settings.
3. On the d0073 ERM System Settings dialog box, click Integration.
4. For the Integration Service URL box, enter the URL of AVEVA Integration
Service used for integration with AVEVA Marine.
5. For the Notification Service URL box, enter the URL of AVEVA Notification
Service used for integration with AVEVA Marine.
Important: Whenever the URL for AVEVA Integration Service or Notification
Service is modified, you must restart the multi-consumer service running on
the AVEVA ERM server.
6. Select the Enable Integrated Engineering & Design check box.
7. For the Integrated Engineering & Design Import Path box, enter the location
from where the configuration files related to AVEVA ERM-Design Integration
can be imported.
8. Click Apply and then click Install.
Page 47
The following table describes the UI elements in more detail.
Integration · The link to AVEVA Integration Service used for integration with
Service URL AVEVA Marine.
· Updatable
Notification · The link to Notification Service used for integration with AVEVA
Service URL Marine.
· Updatable.
Enable · Check box used to enable AVEVA ERM-Design Integration. If the
Integrated check box is cleared, the functionalities related to AVEVA ERM-
Engineering & Design Integration are stopped. However, the Integrated
Design Engineering & Design custom properties and staging areas are not
removed. This must be done manually by clicking Uninstall.
· Updatable.
· Cleared by default value.
Integrated · The location where the configuration files needed for imports
Engineering & related to AVEVA ERM-Design Integration are available.
Design Import · Updatable
Path · You must click Apply to save the Integrated Engineering & Design
Import Path.
Install Installs AVEVA ERM-Design Integration by performing the following:
· Creates an import staging area with the name “IS” where
configuration files are generated.
· Creates the custom properties related to AVEVA ERM-Design
Integration, such as Design Status, Component Name, Technical
Responsible and so on.
· Creates integration service records that are according to the
integration agreed design and displayed in the s14001 Integration
Service screen. The records created by the installation are marked
as system created, and only few attributes can be updated.
· Creates views and data extraction information needed to export
data from AVEVA ERM to AVEVA Marine.
Uninstall Uninstalls AVEVA ERM-Design Integration by performing the
following:
· Removes configuration files from the staging area that are used for
AVEVA ERM-Design Integration.
· Uninstalls the custom properties used for AVEVA ERM-Design
Integration.
· Removes the integration service records marked as created by the
system.
· Removes the views and data extraction details needed to export
data from AVEVA ERM to AVEVA Marine.
Page 48
6.2.2 Configure Material Definition

To configure Material Definition:
1. On the d0073 ERM System Settings dialog box, click Material Definition.
2. Make the required changes in the General area.
3. Click Apply and then click OK.
Note: This page is used to set up all data related to the Material Definition
module in AVEVA ERM.
The following table describes some of the fields:
Material Type · At the time of setting up AVEVA ERM, you must specify if the
Required Material Type attribute must be mandatory or optional in the
material definition catalogues in s20010 Project Components
and s20011 Standard Materials.
· Updatable.
· Cleared by default.
System Unit for · Mentions the default unit of measure for fabricates and
Fabricate and drawings
Drawing · List of Values. Contains valid units defined in the s00010 screen.
· Updatable.
· Default value is "PCS"
Page 49
Buyer Group · If the check box is selected, the buyer group is a required field
Required when creating or updating standard materials (s20011), project
components (s20010) and hull materials (s30017).
· For AVEVA ERM-Design Integration to successfully transfer
standard materials and project components from AVEVA
Marine, the check box must be cleared before importing
standard materials and project components into AVEVA ERM.
· Updatable.
· Cleared by default.
6.2.3 Configure Material Control

To configure Material Control:
1. On the d0073 ERM System Settings dialog box, click Material Control.
2. Make the required changes in the General area.
3. Click Apply and then click OK.
Important: If the value of the Default ABOM Header Number Setup Method list is set to
Auto, the ABoM header Id is generated automatically. If the value is User, ABoM header
Id must be entered by the user. For the ABoM integration to work as expected, this
setting must be set to Auto.
6.2.4 Set Up External Source Applications

The s00033 External Source Applications screen contains the list of external applications,
AVEVA specific or otherwise, that are recognised as valid sources of data.
Page 50
In the context of integration, the data displayed in this screen indicates the default
application used for integration: either AVEVAMARINE or AVEVADESIGN based on which
application has a value defined for the I.S Data Source Type column. When both
applications have a data source type, then AVEVAMARINE is considered as the default
application.
Note:
· For the installation performed in the d0073 ERM System Settings screen to be
successful, at least one of the two applications (AVEVADESIGN or AVEVAMARINE)
must have a value in the I.S. Data Source Type column.
· To create the expected concept transfer record for ABOM, AVEVADIAGRAM must
have a value in the I.S. Data Source Type column.
The following table describes the columns in more detail.
Column Description
Source App. The code used in AVEVA ERM to identify each source application
and also used as the data source identifier in AVEVA ERM data
import functions.
Status Check box to indicate if the application is an active data source or
not. If selected, the application Id can be used elsewhere in
AVEVA ERM. If cleared, the application Id cannot be assigned to
new records that are being imported into AVEVA ERM.
EDR (External Check box to indicate if the application requires deletion
Deletion confirmation. When selected, delete notifications
Confirmation (CanDeleteRequest, CanDeleteAcknowledgement,
Required) CanDeleteError, Delete) are sent to the external applications and
AVEVA ERM for those components that are ready to be deleted
after they were transferred to the external application.
I.S. Data Source Type The data source mentioned in AVEVA Integration Service. For
example, this should be ‘AVEVA Outfitting’ in the case of import
Part List data from AVEVA Marine to AVEVA ERM.
Page 51
6.2.5 Set Up AVEVA Integration Service

The s14001 Integration Service screen is used to define the Integration Service concepts
that can be transferred between AVEVA ERM and AVEVA Marine. The records
corresponding to the current transfer are created by the system when installing AVEVA
ERM-Design Integration.
The s22050 Data Import and s14002 Integration Messages screens use these definitions
to import data.
The concepts defined in this screen are also used as concept information in the messages
transferred.
The following table describes the columns in more detail.
Column Description
Id · The identifier of the Service Infrastructure concept.
· Required.
· Searchable.
· Updatable.
· The list of valid identifiers to be used when using AVEVA Marine and
AVEVA ERM is as follows:
o ABOM
o ActualSteelMaterialUsage
o DesignSpecification
o ExternalRefSync
o Fabricate
o HullUnit
o HvacSpool
o NestingInfo
o Outfitting
o OutfittingAssembly
o Pipespool
o PlatesProfilesOnHullUnit
o ProjectComponent
o RawPlate
o RawProfile
o StandardMaterial
Page 52
Column Description
o SteelStructure
o SystemHierarchy
o WorkPackageToAssembly
Project · The design project pertaining to the integration transfer record.
· Updatable.
· Searchable.
· The combination of Integration Service Id and Project is unique.
· Is a list of values. Contains the projects that are set up for
integration and defined in the s10001 screen.
Description · Description for the Service Infrastructure identifier.
· Required.
· Updatable.
Direction · The direction of the concept transfers from AVEVA ERM point of
view.
· Can have the values "In", "Out" or "Both".
· Updatable for records not created by the system.
Automatically · Check box indicating if the ‘Update’ notifications for the specific
Picked data transfer should be picked up automatically or not. If selected,
data is transferred without user interaction. If cleared, the ‘Update’
notifications need to be processed manually using the s14002
Integration Messages screen.
· Updatable when the direction is "In" or "Both".
Application · Name of the external source application to which or from where
AVEVA ERM transfers data.
· Required.
· Searchable.
· Is a list of values. Contains all external applications defined in the
s00033 External Source Application screen.
User Name User name to be used for logging on to the external application.
Password Password to be used for logging on to the external application.
Source Table Source table name defined in AVEVA Marine to be used while
querying for data. For the list of source tables used, see List of Source
Tables Used.
Data Type · Data type of the concept to be imported in AVEVA ERM.
· Few examples used in the current integration are:
o ProjComp: To import project components from AVEVA
Engineering – Tags module.
o Fabricate: To import hull steel parts, pipe spool and fabricate
design data from AVEVA Marine.
o PlHdrDraw: To import outfitting design data from AVEVA Marine.
o Section: To import hull blocks from AVEVA Marine.
o SteelTapeHdr: To import profile and plate nesting information
from AVEVA Marine.
Page 53
Column Description
Import Staging Name of the import staging area. The list of values is obtained from
area the s22015 Import Staging Areas screen and contains the list of
different import staging areas used by the import service. This value
must always be "IS" for AVEVA ERM-Design Integration transfer
concepts.
6.2.6 Set Up Drawing Catalogue and Part List

Before transferring steel plates and profiles part list, you need to create a drawing
manually in the s20012 Drawing Catalogue screen. The drawing is used to hold the top
node fabricate on a part list in the s21000 Part Lists screen.
For the defined drawing, you must also create a corresponding part list header.
Page 54
6.2.7 Set Up Projects

The s10001 Projects screen is used for setting up and maintaining a project and its related
information.
Page 55
The following table describes the columns in the screen.
Column Description
Project ID This is the project Id used across AVEVA products. The AVEVA Marine
project that needs to be integrated with AVEVA ERM must be
registered in this screen before using AVEVA ERM-Design Integration.
Include System · Check box indicating if system breakdown number must be part of
Number in the project component identification.
Project · If selected, the system Id is used as part of the project component
Component Id identification and thus becomes mandatory when defining a new
project component in the s20010 Project Components screen.
· If cleared, the project component identification must be entered by
the user.
· The check box must be cleared for importing project components
from AVEVA Marine. The user is then expected to add the system
manually in the project component catalogue from AVEVA ERM.
Hull Drawing · The identifier of the overall hull installation drawing for the current
project.
· This drawing holds all the top node fabricates as a part list in the
s21000 Part Lists screen for the hull structure, i.e. the assembly
level. This will ensure that hull fabricate structure can be planned
and initiated for e.g. material status calculation and for Planning and
Production.
· Is a list of values. The list can be opened only when a project is
available in the “Project” field.
· Valid values are all drawings which comply with all of the following
rules:
o The drawing must be related to the project stated in field
“Project”.
o The status of the drawing must be set to “Fully Validated” in the
s20012 Drawing Catalogue screen.
o The drawing must have a part list related to it, i.e. the Applicable
to Part List and Part List Exists check boxes in the s20012
Drawing Catalogue screen must be selected.
Integration · The name of the project in the AVEVA Design application. This value
Design Project Id is expected in the integration data transferred from AVEVA Design
application. Integration Design Project Id value can be added to the
records defined in the s14001 Integration Service screen, where the
service infrastructure Id and the integration design project Id
uniquely define a service infrastructure record.
· No default value.
· Updatable.
· Unique. The same integration design project Id cannot be added to
more than one project.
· If the integration design project Id is used in a record definition for
integration service on the s14001 Integration Service screen, it
cannot be deleted.
Page 56
6.2.8 Set Up Material Type Defaults

The s20004 Material Type Defaults screen maintains the common material types that are
applicable across application boundaries and that act as common reference attributes
between AVEVA ERM and AVEVA Marine.
For details on how to create a material type in AVEVA ERM, please refer to the screen
user guide.
Important:
· Material Type in AVEVA ERM and Material Category Mapping in AVEVA Marine
must be synchronised before importing and publishing standard materials to and
from AVEVA ERM.
· Material Type in AVEVA ERM and Material type for Project Components in
AVEVA Marine must be synchronised before importing project components into
AVEVA ERM.
Page 57
6.2.9 Set Up Fabricate Types

The fabricate types are defined in the s20018 Fabricate Types screen. The fabricate types
are used when batching the different fabricates that are to be fabricated together.
For AVEVA ERM-Design Integration, the following fabricate types are to be added
manually in AVEVA ERM:
· ASM: Assembly
· FAB: Plain fabricate
· HULLASMBLY: Hull Assembly
· HULLPART: Hull Part
· PSPOOL: Pipe Spool
· HSPOOL: HVAC Spool
Page 58
CHAPTER 7 - List of Source Tables Used
7 List of Source Tables Used

AVEVA ERM-Design Integration uses the following source tables to store and retrieve data
for integration.
Note: When using PML functions for integration, you must make sure that AVEVA ERM is
configured to work in the PML Safe mode. When using DB views, then configure AVEVA
ERM to work in the Non PML Safe mode. For more information, see the screen help for
s14001 Integration Service. Further, integration of bolt part lists is available only through
the PartListDesign PML function, and not through the corresponding DB view.
DB View PML Function Purpose

ABOM_Published ABOM To import the
published ABoM
information from
AVEVA Diagrams
ExternalRefSync_Published ExternalRefSync To synchronise the
external references of
published information
if you are upgrading
from AVEVA ERM 12.2
FabricatePartList_Published Structure To import the
published fabricate
design data from
AVEVA Marine
HullBlocks_Published HullUnit To import the
published hull blocks
from AVEVA Marine
HvacSpoolPartList_Published HvacSpool To import the
published HVAC spool
information from
AVEVA Marine
NestingList_Published NestingList To import the
published nesting
information from
AVEVA Marine
OutfittingPartList_Published PartListDesign To import the
published outfitting
design data from
AVEVA Marine
Page 59
CHAPTER 7 - List of Source Tables Used
DB View PML Function Purpose

OutfittingPartList_Assembly_Pu PartListAssembly To import the
blished published outfitting
part list assembly
information from
AVEVA Marine
PipeSpoolPartList_Published PipeSpool To import the
published pipe spool
design data from
AVEVA Marine
ProjectComponents_Published ProjectComponent To import the
published project
components from
AVEVA Engineering
RawPlates_Published RawPlate To import the
published raw plates
information from
AVEVA Marine
RawProfile_Published RawProfile To import the
published raw profile
information from
AVEVA Marine
StandardCatalogue_Published StandardCatalogue To import the
published standard
materials from AVEVA
Marine
SteelPartList_Published PartListSteel To import the
published hull steel
parts from AVEVA
Marine
Steel_Actualmaterial_Published SteelActualMaterial To import the
published actual
material usage
information from
AVEVA Marine
Page 60
CHAPTER 8 - About Material Mapping
8 About Material Mapping

A standard material, raw plate or raw profile is identified by a material Id in AVEVA ERM
while a standard component in AVEVA Marine is identified by a component name. An
AVEVA Marine component is stored in the catalogue in a structure defined by Section and
Category.
You must map a standard material, raw plate or raw profile in AVEVA ERM to the
standard components in AVEVA Marine. The key to this mapping is the ERM Material
Type which is transferred as part of the fields transferred.
Page 61
8.1 Material Category Mapping

The mapping of a material type to a Catalogue/Section/Category combination is done in
AVEVA Marine through a mapping table.
For every ERM Material Type, a corresponding Section and a Category is assigned in the
AVEVA Marine catalogue. This information is useful when importing the standard
materials, raw plates or raw profiles from AVEVA ERM.
The image shows how a mapping is defined.
The generic type description GTYPE is valid for all components stored in the same
category.
ERM Material Type defines the location where the standard material, raw plate or raw
profile information is stored when importing it from AVEVA ERM into AVEVA Marine.
Page 62
The Auto Generate Mapping button generates the material category mapping for each of
the part elements in the current MDB (Multiple Data base).
When a new standard material, raw plate or raw profile is transferred from AVEVA ERM,
the category for the standard material, raw plate or raw profile found by looking up the
transferred field Material Type in the mapping table. When searching for new or modified
standard materials, raw plates or raw profiles to be transferred to AVEVA ERM, all
categories defined in the mapping table are looked up.
You can store the data (for example, weight) through an associated General Part (GPART)
in Component Data (CMPD) instead of directly storing it in the component. However, in
order to be able to create GPARTs and CMPD definitions, you must first define Part World
(PRTWLD), Part Element (PRTELE), Component World (CMPW) and Component Type
(CMPT).
Most of the shared attributes may be stored as User Defined Attributes (UDAs) together
with the component. You can define PML-scripts for reading and writing all shared
attributes.
8.2 Supporting PML Functions

You can define the names of PML-scripts for setting the attributes for GPART, SCOM,
SPRF, CMPD and find out when a component was modified; an example is supplied for
each PML-script. The Material Category Mapping data is stored in XML format.
Page 63
8.3 Create a New Mapping

To create a new mapping:
1. On the Material Category Mapping dialog box, on the Material Mapping tab,
click Add. The required fields are set to edit mode.
2. Select a GPART. The corresponding fields are automatically populated with
values.
3. Type a name for the ERM Material Type box and click Apply to save the
mapping.
Note: The character length of ERM Material Type cannot exceed the
configured length.
Alternatively, you can auto-generate the mapping by clicking Auto Generate Mapping.
This will create mapping for the available GPARTs, SCOMs and SPRFs.
The image below shows how to create a mapping.
Page 64
Note: The ERM Material Type in AVEVA ERM must be synchronised before importing and
publishing standard materials, raw plate or raw profile to or from AVEVA ERM.
8.4 Material Mapping Settings

The material category mapping settings are used for creating material category mappings.
The following table describes the UI elements in detail.
Material Type Restricts the character length of AVEVA ERM Material Type to the
Max Length specified number while creating mappings. The default value is 10.
Material Type Enables you to read the data ERM Material Type from a PML Script
Auto Generate when generating material type automatically.
PML Note: If no data is provided, the PML function
ermgetmaterialtype.pmlfnc is used by default.
Page 65
8.5 Exporting Material Category Mappings to Excel

You can export material category mappings to an Excel file which can be used by AVEVA
ERM to copy or paste into the Material Category Mapping screen.
To export a material category mapping:

1. On the Material Category Mapping dialog box, click File > Export to Excel.
2. On the Save As dialog box, select the required file location and click Save.
3. After you receive a message that the material type defaults are exported
successfully, click OK.
The exported data is displayed as follows:
Page 66
CHAPTER 9 - Performing Basic Tasks Using AVEVA ERM-Design Integration
9 Performing Basic Tasks Using AVEVA ERM-Design

Integration
This section describes how to perform the following basic tasks using AVEVA ERM-Design
Integration.
· Processing messages in AVEVA ERM
· Importing data in AVEVA ERM manually
· Importing notifications manually in AVEVA Marine
· Navigating to the data in AVEVA Marine
9.1 Processing Messages in AVEVA ERM

The s14002 Integration Messages screen in AVEVA ERM displays all the messages
generated from or for AVEVA ERM. The ‘Update’ notifications generated from AVEVA
Marine are not processed automatically, unless the configuration details from the s14001
Integration Service screen are marked as ‘Automatically Picked’.
To process a message:
1. On the s14002 Integration Messages screen, click Process Messages. The
d0211 Available Messages to Process dialog box that displays the list of
messages to be processed is displayed.
2. Select the required message for Object Name (concept transferred) and design
project and then click Process.
The Count column on the d0211 Available Messages to Process area indicates the
number of ‘Update’ notifications available for the same transfer concept (Object Name)
and design project.
Note: Messages with a topic other than ‘Update’ (for example, ‘Acknowledgement’,
‘Error’, ‘CanDeleteRequest’, ‘CanDeleteAcknowledgement’, ‘CanDeleteError’, ‘Delete’)
are processed automatically in AVEVA ERM.
Page 67
9.2 Importing Data in AVEVA ERM Manually

In AVEVA ERM, you can start an import manually using the s22050 Data Import screen.
To start a manual import:

1. On the s22050 Data Import screen, click AVEVA Integration Service. The
d0177 Run Integration Service import dialog box that displays all the records
defined in s14001 with direction ‘In’ or ‘Both’ is displayed.
2. Select the required record based on transfer Id and Integration Design Project
ID, and then click Import.
9.3 Importing Notifications Manually in Design Application

Notifications received from AVEVA ERM are automatically displayed in the Notifications
window in AVEVA Marine. Additionally, you can also use the Manual Import menu in the
window to import any latest notifications that are not yet displayed in the window.
You can manually import notifications for the following concepts:

· Hull Design: System Hierarchy, Plates and profiles On Hull Unit, Work Package
· Outfitting: System Hierarchy, Work Package
· Paragon: Standard Material, Raw Plate, Raw Profile, Design Specification
To manually import notifications, click Manual Import, and then select the required
concept. The notifications available for the concept are displayed in the window.
Page 68
9.4 Navigating to the Data in Design Application

AVEVA ERM-Design Integration enables you to locate and navigate to the data from the
Publish to AVEVA ERM and Notifications windows.
To navigate to the data, right-click on the element in the Message Details section of the
Notifications window, or in the Preview of data to be published section of the Publish to
AVEVA ERM window, and select Navigate to. The element is highlighted in the Design or
Catalogue Explorer.
Page 69
CHAPTER 10 - Integration with AVEVA Catalogue Manager
10 Integration with AVEVA Catalogue Manager

AVEVA ERM-Design Integration enables you to import specifications from AVEVA
Catalogue Manager. This section describes the workflow for performing this import.
10.1 Overview
AVEVA Catalogue Manager stores, manages and publishes specifications to various
Dabacon products that use the information for designing. By integrating AVEVA Catalogue
Manager with AVEVA Marine, you can make sure that the latest specifications are made
available to AVEVA Marine.
AVEVA ERM-Design Integration follows the same notification workflow that is used for
integrating part list information. When a specification is updated and published in AVEVA
Catalogue Manager, an Update notification is sent to AVEVA Marine. In AVEVA Marine,
the Update notification is received and the updated specification is imported from AVEVA
Catalogue Manager. If the import is successful, AVEVA Marine sends an
Acknowledgement notification; if not, an Error notification is sent. In case of an Error
notification, you must republish the specification.
The following types of specifications can be imported:

· Pipe
· Bolt
· Cable tray
Note: The workflow mentioned in this section is applicable to all types of specifications.
Page 70
10.2 Information Transferred

Through the integration, you can import specifications from AVEVA Catalogue Manager
to AVEVA Marine. As part of this, the SPCO elements are also imported.
Note: On account of a character limit imposed by the Dabacon database, the SPCO name
must not exceed 50 characters.
The following information is imported for every specification:

· Material Description
· Component Weight
· Data from Bolt Table (applicable only for Bolt Specifications)
· Specifications
Important: Before importing bolts or specifications from AVEVA ERM, you must create a
user defined attribute (UDA) by name MATERIAL_ID in the s81060 PDMS Attributes
screen in AVEVA ERM for the import to be successful. An example is shown in the
following image.
After importing the bolts or specifications, the UDA is displayed as attributes (Material_Id
for SPCO elements and Material_Id1 for DTAB elements) in AVEVA Paragon.
10.2.1 Material Description

The following columns are transferred as part of Material Description:
Column Name Description

Project Id Id of the project
Cata Catalogue name
Sect Section name
Page 71

Element Type of element (SMTE, SDTE)
Name Name of the element
External Reference Id External reference Id for the specification
Skey Symbol key attribute of SDTE element type
Spec Hdr Id Specification header Id
Spec Hdr No Specification header number (internal Id in
AVEVA ERM)
Rtext Rtext attribute of SDTE element type
Stext Stext attribute of SDTE element type
Ttext Ttext attribute of SDTE element type
Xtext Xtext attribute of SMTE element type
Ytext Ytext element of SMTE element type
Ztext Ztext element of SMTE element type
The data extract query used for material descriptions is q-para.
10.2.2 Component Weight

The following columns are transferred as part of Component Weight:

Projectid Id of the project
AVEVA ERM)
Element Type of element (CMPD, TUBD)
Name Name of the element
Unit Unit of measurement
Cmpt Component type element in Paragon
Cmpw Component world element inParagon
Value Value of weight
The data extract query used for component weights is q-prop.
Page 72
10.2.3 Data from Bolt Table (applicable only for Bolt Specifications)
The following columns are transferred as part of date from bolt table:

Seq Sequence number
AVEVA ERM)
Field Name of the field (whether UDA, Attribute
and so on)
Field Type Element type to which the field is
applicable
Value Value of the field
Rev Revision number of the element
The data extract query used for bolt table data is q-bolt.
10.2.4 Specifications
The following columns are transferred as part of Specifications:

AVEVA ERM)
Spec Entry No Specification entry number
Spec Component Name of the specification component
Spec Component No Specification component number
Selector Seq Selector sequence number
Field Name of the field (whether UDA, Attribute
and so on)
Field Type Element type to which the field is
applicable
Value Value of the field
Default Default value for selector
Page 73
The data extract query used for specifications is q-spec.
Note: If you are importing a SPCO element whose name has been changed, you can
identify the old name and the new name of the SPCO using the q-spec query. The field
with value "OLDNAME" contains the old name of the SPCO element and the field with
value "NAME" contains the present name of the element. The OLD NAME field displays
the SPREF of the SPCO where the Modeller Status is "Latest Transferred". The NAME field
displays the SPREF of the currently approved SPCO.
10.3 Integration Workflow - Data Transfer from AVEVA Catalogue

Manager
The workflow for importing specifications from AVEVA Catalogue Manager is as follows:
1. Approve or republish the specifications in AVEVA Catalogue Manager.
2. Verify the locations for importing specifications.
3. Import the specifications in AVEVA Marine.
4. View the imported specifications.
5. AVEVA Catalogue Manager receives feedback on import.
10.3.1 Approve or Republish Specifications in AVEVA Catalogue Manager

After a specification has been approved in AVEVA Catalogue Manager, the changes are
automatically published. Additionally, you can use the Republish Spec to Design option
on the s81210 Specifications screen to republish the specification to AVEVA Marine.
Page 74
After the specification is published, an Update notification is sent and can be viewed in
the s14002 Integration Messages screen.
10.3.2 Verify Locations for Importing Specifications

Before importing the specification in AVEVA Marine, verify if the locations set for the
specification are correct. For information on setting the locations for import, see Import
from AVEVA Catalogue Manager.
10.3.3 Import Specifications in Design Application

The Notifications window in AVEVA Marine displays the Update notification received
from AVEVA Catalogue Manager. Select the specification and click Update Database to
import the specification.
The ERM Values column in the Notifications window displays a summary of the changes.
After the import is completed, the Status column displays whether the import is
successful. If the import is successful, an Acknowledgement notification is sent to AVEVA
Catalogue Manager; if not, an Error notification is sent.
Important: If you are importing a specification, say SPEC1, that has a reference to a
bolting specification, say SPEC2, then you must first import SPEC2. If you try to import
SPEC1 without importing SPEC2, the import will fail and an error message is displayed.
Page 75
10.3.4 View Specifications

After the import is successful, you can view the imported specifications at the location
specified in the Settings dialog box.
Page 76
The corresponding SPCO elements for the specifications are also imported at the same
location.
Note: In the image above, the value for the Bltref attribute is displayed as Nulref because
the specification that is being imported is a Pipe specification. If you are importing a Bolt
specification, the Bltref attribute would have a value.
Page 77
For detailed information on Detref, Matxt, Cmpref and Bltref, you must navigate to the
respective attribute as shown in the following image.
10.3.5 Provide Feedback

After the import is successful, an Acknowledgement notification is sent to AVEVA
Catalogue Manager. If not, an Error notification is sent.
The Acknowledgement or Error notification is picked automatically by AVEVA ERM and

the published status of the specification is updated according to the feedback received
from AVEVA Marine. This makes sure that after a specification is published, the same
specification is not sent again until it is changed and approved.
While processing an Acknowledgement notification that has a value for the

ExternalReferenceId field, the specification is assigned the External Reference, and the
same value will be used for further transfers.
In case of an Error notification, you must republish the notification.
Page 78
CHAPTER 11 - Standard Material Integration
11 Standard Material Integration

This section describes the concepts and workflow for standard material integration.
11.1 Concept Description

Standard materials are non-project specific items such as pipe, pipe fittings, elbows,
flanges and so on. Standard materials managed in AVEVA ERM are also defined in the
component catalogue of AVEVA Marine in order to be used in the design process.
Some features of standard materials are needed both in the design process of AVEVA
Marine and in the resource management process of AVEVA ERM. The catalogue
integration shares the standard material information between AVEVA ERM and AVEVA
Marine.
The following diagram illustrates the relationship between standard materials of AVEVA
Marine and AVEVA ERM.
Page 79
11.2 Overview of Transfer Process

When AVEVA Marine publishes the standard materials, an ‘Update’ notification is sent to
the the Notification Service and further to AVEVA Integration Service. The Integration
Service sends this notification further to AVEVA ERM. When AVEVA ERM receives the
notification, it can request the available standard material data published in AVEVA
Marine and import it in AVEVA ERM. The standard material transfer from AVEVA ERM to
AVEVA Marine works in a similar way.
For more information about the notification mechanism, see Notification Workflow
Overview.
AVEVA ERM-Design Integration uses either the StandardCatalogue_Published DB view

or the StandardCatalogue PML function to retrieve standard material data from AVEVA
Marine (Dabacon) database. The DB view or the PML function collects all standard
material data from AVEVA Marine with status “Published”.
From AVEVA ERM point of view, the data published and made available for AVEVA Marine
to fetch and import is available in the following data extraction query:
This data extraction definition fetches data from DEXT_STD_MAT_TO_MARINE view

from database.
Page 80

Catalogue data can be created in either system and transferred to the other. The
following attributes are shared between the AVEVA Marine and AVEVA ERM systems:
· Component Name
· Material ID
· Material Type
· Description
· Technical description
· Design Status
· Manufacturer
· Design Technical Responsible User
· ERM Technical Responsible User
· Weight
· External_Ref
11.4 Integration Workflow – Data Transfer to AVEVA ERM

This section describes the workflow to integrate standard materials from AVEVA Marine
to AVEVA ERM. Here, the sending application is AVEVA Marine and the receiving
application is AVEVA ERM.
The workflow for transferring standard material information from AVEVA Marine to
AVEVA ERM is as follows:
1. Configure a filter for the standard materials in AVEVA Marine.
2. Update the status of the standard materials in AVEVA Marine.
3. Publish the standard materials in AVEVA Marine.
4. Import the standard materials into AVEVA ERM.
5. Verify data in AVEVA ERM.
6. Provide feedback on data processing in AVEVA ERM.
7. Process the feedback in AVEVA Marine.
11.4.1 Configure a filter for standard materials

The Settings dialog box in AVEVA Marine contains the settings to configure the
integration of standard materials.
Page 81
A new filter must be configured in AVEVA Marine before transferring data. For more
information about the Filter Configuration tab, see Filter Configuration.
The Select for Publish check box column allows the users to view the selected
information in the Components Preview. Select the check box for the required rows and
save the settings by clicking Save.
Page 82
11.4.2 Update the status of the standard materials

In AVEVA Marine, a status called “PublishingStatus” is defined for all components. The
status of the GPART, SCOM and SPRF is modified through the Status controller window.
Only approved designs can be published. Therefore, a standard material must be
progressed to ‘Approved’ before publishing.
11.4.3 Publish the standard materials

Components satisfying the selection criteria can be exported to AVEVA ERM. For each
selected row from the Settings dialog box, a tabbed page is created in the Publish to
AVEVA ERM dialog box that displays the elements that satisfy the criteria (considering the
Type of the Element, Defined mapping and Publishing status) in the first grid.
Select the required component and click Publish to expose data to AVEVA ERM. Status of
the GPART is also moved to ‘Published’ and an ‘Update’ notification is sent to AVEVA
ERM.
11.4.4 Import the standard materials into AVEVA ERM

After the components are published by AVEVA Marine, the components are available for
import in AVEVA ERM. An ‘Update’ notification is received in AVEVA ERM and the user
can act on it.
To import the standard materials in AVEVA ERM:

1. In AVEVA ERM, open the s14002 Integration Messages screen and click
Process Messages. The d0211 Process Messages dialog box with the list of
messages that can be processed is displayed.
2. Select the message with object type ‘StandardMaterial’ for the appropriate
design project and click Process. The standard materials from AVEVA Marine
are imported.
Page 83
The import of standard material from AVEVA Marine can also be done without an
‘Update’ notification, using the s22050 Data Import screen. For more information, see
Importing Data in AVEVA ERM Manually.
The information about errors, if any, is displayed in the Audit Summary and Audit Detail
grids.

When standard materials are imported, AVEVA ERM creates or updates the standard
material information accordingly. The standard material catalogues in AVEVA ERM can be
seen in the s20011 Standard Materials screen.
On Integration tab, the identification of the material, as known in AVEVA Marine, is

displayed.

When the import is completed in AVEVA ERM, the system will generate an
‘Acknowledgement’ or ‘Error’ notification according to the result of the import. Although
standard materials is a concept that is not related to a project, the Acknowledgement or
Error notification that is generated as an answer contains the Design Project value as that
was sent from AVEVA Marine.
Standard material import can be done partially as well. This means that the components
that can be imported successfully in AVEVA ERM will be processed, and
‘Acknowledgement’ notification will be generated for these, while for those that could
not be imported successfully in AVEVA ERM are communicated back to AVEVA Marine
with an ‘Error’ notification.
Page 84

After the import of data is complete, AVEVA ERM sends feedback on data consumption
to AVEVA Marine using the notification mechanism. One of the following actions takes
place in AVEVA Marine:
· In case of an ‘Acknowledgement’ notification, the status of the component is
promoted to ‘Imported’ if Promote Status is clicked.
· In case of an ‘Error’ notification, the status of the component is demoted to
‘Rework’ if Demote Status is clicked.
This ensures that after a data transfer is successfully completed, the data is removed
from the source table.
11.5 Integration Workflow – Data Transfer from AVEVA ERM

This section describes the workflow to transfer standard materials from AVEVA ERM to
AVEVA Marine. Here, the sending application is AVEVA ERM and the receiving application
is AVEVA Marine.
The workflow for transferring standard material information from AVEVA ERM to AVEVA
Marine is as follows:
1. Publish the standard materials in AVEVA ERM.
2. Import the standard materials in AVEVA Marine.
3. Verify data transferred in AVEVA Marine.
4. Provide feedback on data processing in AVEVA Marine.
5. Process the feedback in AVEVA ERM.
Page 85
11.5.1 Publish the standard materials in AVEVA ERM

AVEVA ERM-Design Integration allows publishing of standard materials from AVEVA ERM
to AVEVA Marine.
To publish standard materials from AVEVA ERM to AVEVA Marine:

1. On the s20011 Standard Materials screen, expand the Standard Materials
section.
2. Select the standard materials that need to be published to AVEVA Marine.
3. On the Data Management tab on the toolbar, click Publish StdMat to Design.
The standard materials are published to AVEVA Marine.
The Publish action displays a message that mentions how many items of the selected
ones were published. The reasons why some materials cannot be published are as
follows:
· Material type information for the selected standard material is not available.
· Material type information for the selected material is available, but the material
type is not marked as ‘Available in External System’ in the s20004 Material Type
Defaults screen.
When the standard materials are published in AVEVA ERM, an ‘Update’ notification is
sent to AVEVA Marine:
Standard materials are not a project-based concept in AVEVA ERM. For this reason, when
the transfer is initiated in AVEVA ERM, the design project value is empty in the Update
notification. The application to send the notification to (‘Sent to Appl.’) is decided based
on the application that is set in the s14001 Integration Service screen for the record
defined for ‘StandardMaterial’ and with no design project.
Page 86
11.5.2 Import the standard materials

After AVEVA ERM publishes the standard materials, an ‘Update’ notification is sent to the
Notification Service. This notification is fetched by AVEVA Marine and is displayed in the
Notifications screen.
AVEVA Marine fetches the data from AVEVA Integration Service and displays the
components which have been published on AVEVA ERM side.
To import the data to AVEVA Marine:

· On the Notitications screen, select the components that need to be imported
and then click Update Database. The standard materials are imported from
AVEVA ERM to AVEVA Marine.
Page 87
11.5.3 Verify the imported data

After successful update, components are created or updated in AVEVA Marine. GPART,
SCOM/SPRF and CMPD are created in AVEVA Marine according to the mapping defined.

After the data is imported, according to the import result, an ‘Acknowledgement’ or
‘Error’ notification is sent to AVEVA ERM. The notification contains the information for
material identification.

The ‘Acknowledgement’ and ‘Error’ notifications are automatically picked by AVEVA ERM
and the published status of the standard materials is updated according to the feedback
received from AVEVA Marine. This makes sure that after a data transfer is completed, the
same data is not sent again until it is changed and published.
When processing an ‘Acknowledgement’ that has values for External_Ref fields in the
message details, the material is assigned the External_Ref that will be used for further
identification in the integration process.
Page 88
CHAPTER 12 - Raw Plates Integration
12 Raw Plates Integration

This section describes the concepts and procedure for raw plates integration.

The catalogue integration tool shares the raw plate catalogue information between
AVEVA ERM and AVEVA Marine.
The following diagram illustrates the integration for raw plates between AVEVA ERM and
AVEVA Marine.

When AVEVA Marine publishes raw plates, an ‘Update’ notification is sent to the
Notification Service and further to AVEVA Integration Service that in turn sends this
notification further to AVEVA ERM. When AVEVA ERM receives the notification, it can
request for the available raw plates data published in AVEVA Marine and import it in
AVEVA ERM. The raw plates transfer from AVEVA ERM to AVEVA Marine works in a
similar way.
Overview.
AVEVA ERM can also retrieve raw plates from AVEVA Marine without receiving an
'Update' notification by connecting to the Integration Service. To do this, AVEVA ERM
must send a request to the Integration Service and the service, in turn, retrieves data
from AVEVA Marine.
AVEVA ERM-Design Integration uses either the RawPlate_Published DB view or the

RawPlate PML function to retrieve raw plates data from AVEVA Marine (Dabacon)
database. The view or function collects all raw plates data from AVEVA Marine with status
“Published”.
Page 89
This data extraction definition fetches data from DEXT_PLATES_TO_MARINE view

from database.

· Component Name
· Material Type
· Quality Code
· Description
· Technical description
· Height
· Length
· Width
· Density
· Design Status
· Manufacturer
· ERM Technical Responsible User
· External_Ref
Page 90
12.4 Integration workflow – Data Transfer to AVEVA ERM

The following workflow is used for transferring raw plates information from AVEVA
Marine to AVEVA ERM:
1. Configure a filter for the raw plates in AVEVA Marine.
2. Update the status of the raw plates in AVEVA Marine.
3. Publish the raw plates in AVEVA Marine.
4. Import the raw plates into AVEVA ERM.
6. Provide feedback on data consumption in AVEVA ERM.
12.4.1 Configure a filter for the raw plates in AVEVA Marine

integration of raw plates. A new filter must be configured in AVEVA Marine before
transferring data. For more information about the Filter Configuration tab, see Filter
Configuration.
Page 91
12.4.2 Update the status of the raw plates in AVEVA Marine

status of the raw plates is modified through the Status controller window. Only approved
designs can be published. Therefore, a raw plate must be progressed to ‘Approved’
before publishing.
12.4.3 Publish the raw plates in AVEVA Marine

Components that satisfy the criteria are displayed in the data grid. Select the required
component and click Publish to expose data to AVEVA ERM. Status of the raw plate is also
moved to ‘Published’ and an ‘Update’ notification is sent to AVEVA ERM.
When you click Publish, the raw plate data is available in the source table.
12.4.4 Import the raw plates into AVEVA ERM

can act on it.
Page 92
To import the raw plates in AVEVA ERM:

2. Select the message with object type ‘RawPlate’ for the appropriate design
project and click Process. The raw plates from AVEVA Marine are imported.
The results can be verified in screen s20050.
grids.
The import of raw plates from AVEVA Marine can also be done without an ‘Update’
notification, using the s22050 Data Import screen. For more information, see Importing
of Data in AVEVA ERM Manually.

When raw plates are imported, AVEVA ERM creates or updates the raw plate information
accordingly. The steel material catalogue in AVEVA ERM can be seen in the s30017 Hull
Plate and Profile Catalogue screen.
On Integration tab, the external reference information of the raw plate, as known in
AVEVA Marine, is displayed.

When import is completed in AVEVA ERM, the system will generate an
‘Acknowledgement’ or ‘Error’ notification according to the result of the import.
If any record is rejected in this transfer, then all records are rejected. Partial import is
currently not supported for this concept.
Page 93

12.5 Integration workflow – Data Transfer from AVEVA ERM

This section describes the integration workflow for raw plates from AVEVA ERM to AVEVA
Marine.
The following workflow is used for transferring raw plates information from AVEVA ERM
to AVEVA Marine:
1. Publish the raw plates in AVEVA ERM.
2. Import the raw plates in AVEVA Marine.
4. Provide feedback on data consumption in AVEVA Marine.
12.5.1 Publish the raw plates in AVEVA ERM

AVEVA ERM-Design Integration allows publishing of raw plate information from AVEVA
ERM to AVEVA Marine. In AVEVA ERM, the s30017 Hull Plate and Profile Catalogue
screen is used to publish the raw plate information.
Page 94
To publish raw plates from AVEVA ERM:

· On the s30017 Hull Plate and Profile Catalogue screen, select the raw plates that
need to be published, and click Data Management > Publish Plates to Design.
The raw plates are available in a view shared with AVEVA Marine.
The Publish action will display a message that mentions how many items were published
out of the selected ones. The reasons why raw plates cannot not be published are as
follows:
· Selected steel material is not Plate (but Profile)
· Material type information for the selected steel material is not available.
Defaults screen.
When the raw plates are published in AVEVA ERM, an ‘Update’ notification is sent to
AVEVA Marine:
Raw plates is not a project-based concept in AVEVA ERM. For this reason, when the
transfer is initiated in AVEVA ERM, the design project value is empty in the Update
notification. The application to send the notification to (‘Sent to Appl.’) is decided based
on the application that is set in the s14001 Integration Service screen for the record
defined for ‘RawPlate’ and with no design project.
12.5.2 Import the raw plates in AVEVA Marine

After AVEVA ERM publishes the raw plates, an ‘Update’ notification is sent to the
components which have been published on the AVEVA ERM side.
Page 95

· On the Notifications screen, select the components that need to be imported
and then click Update Database. The raw plates are imported from AVEVA ERM
to AVEVA Marine.
Note: While importing raw plates into AVEVA Marine, ensure that the Quality
Code and Density of the raw plates are same. Else, the import is rejected.
12.5.3 Verify data in AVEVA Marine

After successful update, components are created or updated in AVEVA Marine. Raw
plates are created in AVEVA Marine according to the mapping defined.

raw plate material identification.
Page 96

and the published status of the raw plates is updated according to the feedback received
from AVEVA Marine. This ensures that after a data transfer is completed, the same data is
not sent again until it is changed and published.
When processing an ‘Acknowledgement’ that contains ExternalReferenceId in the

message details, the material is assigned the corresponding External reference that can
be used for further identification in the integration process.
Page 97
CHAPTER 13 - Raw Profile Integration
13 Raw Profile Integration

This section describes the concepts and procedure for raw profile integration.

The following diagram illustrates the integration for raw profiles between AVEVA ERM
and AVEVA Marine.

When AVEVA Marine publishes the raw profiles, an ‘Update’ notification is sent to the
Notification Service and further to AVEVA Integration Service that in turn sends this
request for the available raw profiles data published in AVEVA Marine and import it in
AVEVA ERM. The raw profiles transfer from AVEVA ERM to AVEVA Marine works in a
similar way.
Overview.
AVEVA ERM can also retrieve raw profiles from AVEVA Marine without receiving an
'Update' notification by connecting to AVEVA Integration Service. To do this, AVEVA ERM
must send a request to the Integration Service and the service, in turn, retrieves data
from AVEVA Marine.
AVEVA ERM-Design Integration uses the RawProfile_Published DB view or the

RawProfile PML function to retrieve raw profiles data from AVEVA Marine (Dabacon)
database. The DB view or the PML function collects all raw profiles data from AVEVA
Marine with status “Published”.
Page 98

· Name
· Length
· Height
· Width
· DimensionA, DimensionS
· MaterialType
· QualityCode/Matref (Referred as matref in AVEVA Marine and QualityCode in
AVEVA ERM)
· Density
· ERM Technical Resposible User
· KG_M (Weight in kilo per meter of the profile) – mandatory field in AVEVA ERM
· External_Ref
Page 99
13.4 Integration Workflow – Data Transfer to AVEVA ERM

The following workflow is used for transferring raw profiles information from AVEVA
Marine to AVEVA ERM:
1. Configure a filter for the raw profiles in AVEVA Marine.
2. Update the status of the raw profiles in AVEVA Marine.
3. Publish the raw profiles in AVEVA Marine.
4. Import the raw profiles into AVEVA ERM.
13.4.1 Configure a filter for the raw profiles in AVEVA Marine

integration of raw profiles. A new filter must be configured in AVEVA Marine before
transferring data. For more information about the Filter Configuration tab, see Filter
Configuration.
Page 100
13.4.2 Update the status of the raw profiles in AVEVA Marine

status of the raw profiles is modified through the Status controller window. Only
approved designs can be published. Therefore, a raw profile must be progressed to
‘Approved’ before publishing.
13.4.3 Publish the raw profiles in AVEVA Marine

component and click Publish to expose data to AVEVA ERM. Status of the raw profile is
moved to ‘Published’ and an ‘Update’ notification is sent to AVEVA ERM.
When you click Publish, the raw profile data is available in the RawProfile_Published
DBview and RawProfile PML function.
Page 101
13.4.4 Import the raw profiles into AVEVA ERM

Note: Before importing raw profiles from AVEVA Marine, you must synchronise ERM
Material Type in s20004 Material Types screen.
can act on it.
To import the raw profiles in AVEVA ERM:

2. Select the message with object type ‘RawProfile’ for the appropriate design
project and click Process. The raw profiles from AVEVA Marine are imported.
grids.
The import of raw profiles from AVEVA Marine can also be done without an ‘Update’
notification, using the s22050 Data Import screen. For more information, see Manual
Import of Data in AVEVA ERM.
Page 102

When raw profiles are imported, AVEVA ERM creates or updates the raw profile
information accordingly. The steel material catalogue in AVEVA ERM can be seen in the
s30017 Hull Plate and Profile Catalogue screen.
On Integration tab, the external reference information of the raw profile, as known in
AVEVA Marine, is displayed.

If any record is rejected in this transfer, then all records are rejected. Partial import is
currently not supported for this concept.

Page 103

The following workflow is used for transferring raw profiles information from AVEVA ERM
to AVEVA Marine:
1. Publish the raw profiles in AVEVA ERM.
2. Import the raw profiles in AVEVA Marine.
Page 104
13.5.1 Pre-setup steps in AVEVA ERM

You must perform the following tasks before transferring raw profiles from AVEVA ERM
to AVEVA Marine.
1. Define Dimension Code in the s30019 Dimension code – Hull Plate and Profile
screen.
2. Define Quality Standard in the s30018 Quality Standard – Hull Plate and
Profile screen.
3. Define Material Type Default in the s20004 Material Type Default screen.
13.5.2 Publish the raw profiles in AVEVA ERM

AVEVA ERM-Design Integration allows publishing of raw profile information from AVEVA
ERM to AVEVA Marine. In AVEVA ERM, the s30017 Hull Plate and Profile Catalogue
Page 105
screen is used to publish the raw profile information.
To publish raw profiles from AVEVA ERM:

· On the s30017 Hull Plate and Profile Catalogue screen, select the raw profiles
that need to be published, and click Data Management > Publish Profiles to
Design. The raw profiles are available in a view shared with AVEVA Marine.
out of the selected ones. The reasons why raw profiles cannot be published are as
follows:
· Selected steel material is not a profile (but a plate).
· Material type information for the selected steel material is not available.
Defaults screen.
When the raw profiles are published in AVEVA ERM, an ‘Update’ notification is sent to
AVEVA Marine.
Raw profiles are not a project-based concept in AVEVA ERM. For this reason, when the
transfer is initiated in AVEVA ERM, the design project value is empty in the Update
notification.
13.5.3 Import the raw profiles in AVEVA Marine

Before importing raw profiles from AVEVA ERM Material Type, Dimension code and
Quality standards must be synchronised manually.
Page 106
To manually synchronise Dimension Code and Quality Standards:

1. Define raw profile type in AVEVA Marine in the Material Category Mapping
screen.
2. Define Quality Standards in AVEVA Marine in the Properties database.
Page 107
3. Define Material Type in the Material Category Mapping screen.
After AVEVA ERM publishes the raw plates, an ‘Update’ notification is sent to the
Page 108
components which have been published on the AVEVA ERM side.

· On the Notifications screen, select the components that need to be imported
and then click Update Database. The raw profiles are imported from AVEVA ERM
to AVEVA Marine.
Note: While importing raw profiles into AVEVA Marine, ensure that the Quality
Code and Density of the raw plates are same. Else, the import is rejected.
13.5.4 Verify data transferred in AVEVA Marine

After successful update, components are created or updated in AVEVA Marine. Raw
profiles are created in AVEVA Marine according to the mapping defined.
Page 109

raw profile material identification.

and the published status of the raw profiles is updated according to the feedback
received from AVEVA Marine. This ensures that after a data transfer is completed, the
same data is not sent again until it is changed and published.
When processing an ‘Acknowledgement’ that contains ExternalReferenceId in the

message details, the material is assigned the corresponding External reference that can
be used for further identification in the integration process.
Page 110
CHAPTER 14 - System Hierarchy Integration
14 System Hierarchy Integration

This section describes the concepts and procedure for system hierarchy integration.

The Systems are used as vertical cost collectors for values of materials, work hours, sub-
contracted tasks and various expenses assigned to a project in AVEVA Enterprise Resource
Management (AVEVA ERM). Systems are created in the s10002 Systems screen.
Systems are related to a system breakdown structure. The system breakdown structure
can be created with multiple levels (hierarchy) or it can be created with no levels (flat
structure). This can be done in the s10004 Set-Up Project Structure and Systems screen.
Page 111
When using systems for a given project in AVEVA ERM (that is, when relating systems to
material requirements in the s21000 Part List screen) only systems that are related to the
project are valid.
It is possible to import project components with or without system information into

AVEVA ERM. In case project components are imported without system, the system needs
to be set manually for the project component. Then part lists with the project
components can be imported into AVEVA ERM.
The following image shows the system setup in AVEVA Marine.
Page 112

The system hierarchy is defined in AVEVA ERM and transferred to AVEVA Marine. System
Hierarchy is published from AVEVA ERM from s10004 Set-Up Project Structure and
Systems > Data Management > Publish Systems to Design. When AVEVA ERM publishes
a system hierarchy for a project, a notification is sent to the Notification Service and
further to the Integration Service. The Integration Service sends this notification further
to AVEVA Marine. When AVEVA Marine receives the notification, the user can act on it by
importing the data available for the SystemHierarchy concept. After import is done, an
Acknowledgement or Error message, according to the import result, is sent back to
AVEVA ERM.
Overview.
The data published from AVEVA ERM and made available to AVEVA Marine to fetch and
import is available in the following data extraction query.
This data extraction definition fetches data from the DEXT_SYSTEMS_TO_MARINE

view from database.

The following fields are transferred from AVEVA ERM:
· Project
· System or Level Id
· Parent Id
· Description of the Level or System
· Type (System / Level)
Page 113

The following workflow is used for transferring system hierarchy information from AVEVA
ERM to AVEVA Marine:
1. Publish system hierarchy from AVEVA ERM.
2. Import system hierarchy in AVEVA Marine.
4. Process feedback in AVEVA ERM.
Page 114
14.4.1 Publish system hierarchy from AVEVA ERM

To publish system hierarchies from AVEVA ERM:
· On the s10004 Set-Up Project Structure and Systems screen, click Data
Management and then Publish Systems to Design. The systems will be available
in a view shared with AVEVA Marine.
The publish of system structure is done on the project level. The information message
that mentions that ‘1 of 1 records are published’ refers to the project key and it will be
the same irrespective of the number of systems in the structure.
When a system structure is published, an ‘Update’ notification is created and sent to the
Notification Service. The value of ‘Dsg. Proj’ is populated from the ‘Integration Design
Project Id’ attached to the project Id as known in AVEVA ERM.
Page 115
14.4.2 Import system hierarchy

After AVEVA ERM publishes a system hierarchy, an ‘Update’ notification is sent to the
Notification Service. This message is fetched by AVEVA Marine and loaded in the
AVEVA Marine retrieves the data from AVEVA Integration Service and displays the system
hierarchy information which have been published from AVEVA ERM. Select the systems
and click Update Database to import the system hierarchies from AVEVA ERM into AVEVA
Marine.

According to the import result, an ‘Acknowledgement’ or ‘Error’ notification is sent back
to AVEVA ERM. The ‘Acknowledgement’ or ‘Error’ notification contains only the project
information, and not the complete system structure.
Page 116
14.4.4 Process feedback in AVEVA ERM

and the publish status of the project system structure is marked accordingly.
This ensures that after a data transfer is completed, the same data is not sent until it is
changed and published again.
Page 117
CHAPTER 15 - Project Component Integration
15 Project Component Integration

This section describes the concepts and procedure for project component integration.

Project components are the key materials that are critical to the execution of the project
and are usually expensive. Project components are always related to a project. The
project component catalogue (including materials such as equipment, certain valves and
special filters) is created in the design process of AVEVA Marine. Such project materials
are also defined in AVEVA ERM. AVEVA ERM-Design Integration enables transferring the
project components from AVEVA Marine to AVEVA ERM.
The following diagram illustrates the integration for project components from AVEVA
Marine to AVEVA ERM.
Page 118

Project components are defined in AVEVA Engineering, in an Engineering list. This list
contains project items (Tags) that are defined in the project and these concepts are
transferred as project components to AVEVA ERM. Also, equipment materials created in
AVEVA Marine can be transferred as project components to AVEVA ERM.
When AVEVA Marine publishes project components, an ‘Update’ notification is sent to

the Notification Service and further to AVEVA Integration Service that in turn sends this
request for the available project component data published in AVEVA Marine and import
it in AVEVA ERM.
Overview.
AVEVA ERM-Design Integration defines DB view or the PML function to fetch project
component data from the AVEVA Marine (Dabacon) database. The following DB view/
PML function are defined to support project component integration:
· ProjectComponents_Published DB view or ProjectComponent PML function
collects equipment data from AVEVA Marine with status “Published”
AVEVA ERM can fetch project components from AVEVA Engineering by connecting to
AVEVA Integration Service. To fetch the data AVEVA ERM sends a request to the
Integration Service and the service fetches the data from AVEVA Engineering. The
following DB views are defined to support project component integration:
· Equipment_View DB view collects equipment data from AVEVA Engineering
· Released_For_Procurement DB view collects equipment data from AVEVA
Engineering with status “Released_For_Procurement”.
To transfer data from AVEVA ERM to AVEVA Engineering through AVEVA Integration
Service, project components are imported into AVEVA Engineering using the Compare/
Update feature of AVEVA Engineering.
Page 119

Project components are transferred between AVEVA Engineering and AVEVA ERM. The
data transferred successfully can be seen in AVEVA ERM through the s20010 Project
Components screen.
The following columns are transferred for project component integration:

· ID
· Description
· Manufacturer
· System
· MaterialType
· Weight
· DesignProjectId
· Unit
· ExternalStatus
· SpecialGroup
· Status
· BuyersGroup
· External_Ref
15.4 Integration Workflow – Design Application to AVEVA ERM

The integration workflow for project components from AVEVA Marine to AVEVA ERM is
as follows:
1. Set up material type on EQUIPMENT in AVEVA Marine.
2. Set up systems on EQUIPMENT in AVEVA Marine.
3. Configure a filter for the project components in AVEVA Marine.
4. Update the status of the project components in AVEVA Marine.
5. Publish project components in AVEVA Marine.
6. Import project components in AVEVA ERM.
9. Process feedback in AVEVA Marine.
Page 120
15.4.1 Set up material type on EQUIPMENT

Common material types are maintained in AVEVA ERM. These material types contain
common attributes that are referred between AVEVA ERM and AVEVA Marine.
When transferring project components, material type is one of parts of the information
transferred. For this reason, a UDAT (User Defined Attribute) “ProjectComponentType” is
defined in AVEVA Marine. The list of ProjectComponentType is created in AVEVA Marine
and is synchronised with AVEVA ERM so that each ProjectComponentType has a
corresponding material type that can be verified in the s20004 screen.
Equipments must be assigned with ProjectComponentType in AVEVA Marine before

transferring them to AVEVA ERM.
15.4.2 Set up systems on EQUIPMENT

An equipment’s system references attribute (MdSysf) can be set in AVEVA Marine before
transferring them to AVEVA ERM. Systems are created in AVEVA ERM in the s10002
screen and must be synchronised with AVEVA Marine by transferring the project system
structure from screen s10004. For more information, see Concept Description in System
Hierarchy Integration.
Page 121
It is possible to import project components into AVEVA ERM with or without system
information. If project components are imported without system information, the system
needs to be set manually for the project component. Then part list items with the project
components can be imported into AVEVA ERM.
Page 122
15.4.3 Configure a filter for project components

integration of project components. A new filter must be configured in AVEVA Marine
before transferring data. For more information about the Filter Configuration tab, see
Filter Configuration.
information in the Publish window. Select the check box for the required rows and save
the settings by clicking Save.
15.4.4 Update the status of the project components

status of an equipment is modified through the Status controller window. Only approved
designs can be published. Therefore, a project component must be progressed to
‘Approved’ before publishing.
Page 123
15.4.5 Publish the project components

component and click Publish to expose data to AVEVA ERM. Status of the project
components is moved to ‘Published’ and an ‘Update’ notification is sent to AVEVA ERM.
15.4.6 Import the project components in AVEVA ERM

can act on it.
To import the project components in AVEVA ERM:

2. Select the message with object type ‘ProjectComponent’ for the appropriate
design project and click Process. The project components from AVEVA Marine
are imported.
The import of project components from AVEVA Marine can also be done without an
Manual Import of Data in AVEVA ERM.
When the import is completed in AVEVA ERM, the system will generate an
Page 124

When project components are imported, AVEVA ERM creates or updates the project
component information accordingly. The project components can be seen in AVEVA ERM
in the s20010 Project Components screen.


Page 125
15.5 Integration Workflow – AVEVA Engineering to AVEVA ERM

The integration workflow for project components from AVEVA Engineering to AVEVA
ERM is as follows:
1. Set up ERMCategory for Tags in AVEVA Engineering.
2. Set up systems in AVEVA Engineering.
3. Update status of Equipment in AVEVA Engineering.
4. Set up AVEVA ERM to import data from AVEVA Engineering.
5. Import data into AVEVA ERM.
6. Verify the imported data in AVEVA ERM.
15.5.1 Set up ERMCategory for tags in AVEVA Engineering

Common material types are maintained in AVEVA ERM. These material types contain
common attributes that are referred between AVEVA ERM and AVEVA Engineering.
When transferring Project Components, material type is one of the parts of the
information transferred. For this reason, an UDET (User Defined Element Type)
“ERMCategory” is defined in AVEVA Engineering. The list of ERMCategory is created in
AVEVA Engineering and is synchronised with AVEVA ERM so that each ERMCategory has a
corresponding material type that can be verified in the s20004 screen.
Equipments must be assigned with ERMCategory in AVEVA Engineering before

transferring them to AVEVA ERM.
15.5.2 Set up systems in AVEVA Engineering

TagsSystem references attribute (: SystemReference) can be set in AVEVA Engineering
before transferring them to AVEVA ERM. Systems are created in AVEVA ERM in the
s10002 screen and must be synchronised with AVEVA Engineering by transferring the
project system structure from screen s10004. For more information, see Concept
Description in System Hierarchy Integration.
It is possible to import project components into AVEVA ERM with or without system
information. If the project components are imported without system information, the
system needs to be set manually for the project component. Then part list items with the
project components can be imported into AVEVA ERM.
Page 126
15.5.3 Update status of Equipment in AVEVA Engineering

In AVEVA Engineering, a status called “Aveva Integration Maturity” is defined for all
equipments. The status of an equipment is modified through the Status controller
window to move the status to "Released for Procurement".
15.5.4 Set up AVEVA ERM to import data from AVEVA Engineering

In AVEVA ERM, in the s00033 External Source Applications screen, create a Source
Application Definition and configure the integration service type appropriately.
In the s14001 Integration Service screen, create a record with Id as ProjectComponent

and application as AVEVAENG with the corresponding details.
15.5.5 Import data into AVEVA ERM

The import must be started manually using the s22050 Data Import screen. For more
information, see Manual Import of Data in AVEVA ERM.

After the project components are imported, AVEVA ERM creates or updates the project
components according to the data transferred. The project components can be seen in
AVEVA ERM in the s20010 Project Components screen as follows:
Page 127
15.6 Integration Workflow – AVEVA ERM to AVEVA Engineering

The integration workflow for project components from AVEVA ERM to AVEVA
Engineering is as follows:
1. Publish the project components in AVEVA ERM.
2. Import the project components in AVEVA Engineering.
15.6.1 Publish the project components in AVEVA ERM

AVEVA ERM-Design Integration allows publishing of project components from AVEVA
ERM to AVEVA Engineering. In AVEVA ERM, the s20010 Project Components screen is
used for publishing project components.
To publish project components to AVEVA Engineering:

· On the s20010 Project Components screen, select the project components to be
transferred, and then click Data Management > Publish Proj Comp to Design.
The materials will be available in a view shared with AVEVA Engineering.
out of the selected ones. Project components cannot not be published for the following
reasons:
· Material type information for the selected project component is not available.
· Material type information for the selected project component is available, but
the material type is not marked as ‘Available in External System’ in the s20004
Material Type Defaults screen.
15.6.2 Import the project components in AVEVA Engineering

After AVEVA ERM publishes the project components, AVEVA Engineering retrieves the
data through AVEVA Integration Service and imports the data using the Compare/Update
feature.
In AVEVA Engineering, you must create a Compare Update configuration to import data
from AVEVA ERM and update the database of Engineering. For more information, refer to
“Compare and Update” guide of AVEVA Engineering.
Page 128
CHAPTER 16 - Transfer of Advance Bill of Material from AVEVA Diagrams to AVEVA ERM
16 Transfer of Advance Bill of Material from AVEVA

Diagrams to AVEVA ERM
This section describes the concepts and procedure for Advance Bill of Material (ABoM)
integration.

ABoM is used for creating the purchase requirement early in the design phase of a
project. As the actual requirements are created through part lists, these requirements will
replace the ABoM requirements and additional purchase requirement will not be
established before the actual requirements from part lists are higher than the ones stated
in the ABoM.
The ABoM gives a possibility for early estimation of needed materials.

This transfer of data is based on a diagram in AVEVA Diagrams, and exports all data for a
particular diagram.
The data is published either using the ABOM_Published DB view or the ABOM PML
function, which is made available through Integration Service. AVEVA ERM connects to
AVEVA Integration Service and transfers the available data into screen s21002.
Data is available to AVEVA ERM only when the publishing status in AVEVA Marine reaches
the status “Published”. When an ABOM is in status ‘Retired’, no updates are allowed.
After the data is consumed in AVEVA ERM, the publishing status in AVEVA Marine is
changed to “Consumed”. This ensures that the data is not imported again into AVEVA
ERM until it is changed and published again.
On the ABOM transfer from AVEVA Marine, an appropriate configuration is created so

that the information needed to create/update both items and header records are
available.
· ABOM header records corresponding to the information sent are also created.
· Design Ref – Dabacon ID information is mapped to External Reference (on ABoM
Item).
· Diagram Id is mapped to External Group Reference (on ABoM Item).
· TAG Id is mapped to External TAG Id (on ABoM Item).
Page 129

The following columns are transferred from AVEVA Marine to AVEVA ERM:
· MaterialId (material reference)
· Material Type (Std Mat / Fabricate)
· Quan - if no value is transferred, then default value 1 should be used
· Design Ref – Dabacon ID
· Diagram/schematics ID - (In case of multiple information, the primary schematics
ID should be transferred, P&ID)
· Diagram Description
· System ID – (In case of multiple system information, the primary system should
be transferred)
· TAG ID (If exists)
· Project
16.4 Integration Workflow - Data Transfer to AVEVA ERM

The integration workflow for ABoM from AVEVA Marine to AVEVA ERM is as follows:
1. Update status of ABoM in AVEVA Marine.
2. Import ABoM data in AVEVA ERM.
Page 130
16.4.1 Update the status of ABoM

In AVEVA Marine, a status called “Abom_PublishingStatus” is defined for all Diagram
elements. The status of the SCDIAG is modified through Status controller window. The
status of SCDIAG should be moved to ‘Published’ state.
16.4.2 Import ABoM data in AVEVA ERM

Import of data must be done manually using the s22050 Data Import screen. For more
information, see Manual Import of Data in AVEVA ERM.
The imported data is displayed as follows:
Page 131

After a successful import of ABoM data from AVEVA Marine, all standard materials, hull
materials and fabricates published from AVEVA Marine are available in AVEVA ERM in the
s21002 Advance Bill of Material - ABoM screen.
Page 132
CHAPTER 17 - Part List Integration
17 Part List Integration

This section describes the concepts and procedure for part list integration.

Part lists are mainly used to assign materials to drawings in order to define the
requirements for materials needed to produce the construction illustrated by the
drawing. A part list consists of a header which holds the reference to the drawing to
which it is related. Related to a part list header is a list of part list items that holds the
materials.
Note: Currently, AVEVA ERM-Design Integration does not support the transfer of UDETs
of base type ZONE and owner type ZONE to AVEVA Enterprise Resource Management
(AVEVA ERM).
The following diagram illustrates how part lists are transferred from AVEVA Marine to
AVEVA ERM.
Page 133

The part list information in AVEVA Marine is shared with AVEVA ERM through source
tables (DB views and PML functions) that are created in AVEVA Marine. These source
tables are PML scripts which fetch data from the AVEVA Marine database and store the
information required by AVEVA ERM to be able to create part lists.
When the publishing status of the part lists in AVEVA Marine reaches the status
“Published”, the data is available for transfer to AVEVA ERM. After the information is
consumed in AVEVA ERM, the publishing status in AVEVA Marine is changed to
“Consumed”. This ensures that the same data is not transferred again to AVEVA ERM until
it is changed and published again.
Overview.
Page 134
17.3 Pipe and HVAC Spool

This section describes the concepts and procedure for pipe and HVAC spool integration.

In this transfer, AVEVA Marine exports all data for a particular pipe spool or HVAC spool.
The data is published either using the PipeSpoolPartList_Published DB view or the
PipeSpool PML function for pipe spools, and the HvacSpoolPartList_Published DB
view or the HvacSpool PML function for HVAC spool, which are made available through
AVEVA Integration Service, and consumed in AVEVA ERM. AVEVA ERM connects to the
Integration Service and transfers the available data into the corresponding concept
(Fabricate catalogue, Fabricate Part List header and Fabricate Part List items).
· DesignProjectID
· Fabricate ID
· Type (always 'Fabricate')
· Fabricate Type (pipe spool)
· Description
· Weight
· Material Category (S, P, F)
· MaterialId (standard material ID or project component Id)
· DesignUniqueID (Name, or Dabacon Id)
· DrawingQuantity (Quantity w/o excess)
· ApprovedQuantity (Quantity w/excess)
· TechnicalStatus (Currently set to Published)
· Revision
· Unit
· External_Ref

Note: This section describes the workflow for pipe spool integration. A similar workflow
must be followed for HVAC spool integration.
Page 135
The integration workflow for pipe spool from AVEVA Marine to AVEVA ERM is as follows:
1. Configure a filter for pipe spools in AVEVA Marine.
2. Update the status of pipe spools in AVEVA Marine.
3. Publish the pipe spools in AVEVA Marine.
4. Import the pipe spools in AVEVA ERM.
Configure a filter for pipe spools

integration of pipe spool. For more information about the Filter Configuration tab, see
information in the PartList Preview. Select the check box for the required rows and save
Page 136
Update the status of pipe spools

In AVEVA Marine, a status called “PublishingStatus” is defined for all part list elements.
The statuses of the Zone, Fabricate and Pipe spool are modified through the Status
controller window. Only approved designs can be published. Therefore, a pipe spool must
be progressed to ‘Approved’ before publishing.
Publish the pipe spools

Part lists satisfying the selection criteria can be exported to AVEVA ERM. For each
selected row from the PartListSettings dialog box, a tabbed page is created in the Publish
to AVEVA ERM dialog box that displays the elements that satisfy the criteria (considering
the Type of the Element and Publishing status) in the first grid.
Select the required pipe spool and click Publish to expose data to AVEVA ERM. Status of
the pipe spool is moved to ‘Published’ and an ‘Update’ notification is sent to AVEVA ERM.
Import the pipe spools in AVEVA ERM

can act on it.
Page 137
To import the pipe spools in AVEVA ERM:

2. Select the message with object type Pipespool for the appropriate design
project and click Process. The pipe spools from AVEVA Marine are imported.
The import of pipe spool from AVEVA Marine can also be done without an ‘Update’
grids. When import is completed in AVEVA ERM, the system generates an
Verify the imported data in AVEVA ERM

After the pipe spools are imported, AVEVA ERM creates or updates the pipe spool
information accordingly. The fabricate catalogue in AVEVA ERM can be seen in the s20017
Fabricate Catalogue screen.
Page 138
The standard materials or project components added as part list items under the header
PSPOOL elements can be seen in AVEVA ERM through the s21015 Fabricate Part Lists
screen.
Provide feedback on data processing in AVEVA ERM

When import is completed in AVEVA ERM, the system generates an ‘Acknowledgement’
or ‘Error’ notification according to the result of the import.
Process the feedback

Page 139
17.4 Fabricates
This section describes the concepts and procedure for fabricates integration.

This is a part list is based on FABRICATE in AVEVA Marine. This is a UDET of a ZONE type in
AVEVA Marine with base type as ZONE which is intended to contain fabricated items.
When the publishing status of the fabricates in AVEVA Marine reaches the status
“Published”, the data is published either using the FabricatePartList_Published DB
view or the Structure PML function. This data in the source tables is made available
through AVEVA Integration Service, and is consumed in AVEVA ERM. AVEVA ERM
connects to AVEVA Integration Service and transfers the available data into the
corresponding concepts (fabricate, fabricate part list and fabricate part list items).
· DesignProjectID
· Fabricate ID
· Type (always 'Fabricate')
· Fabricate Type (FAB)
· Description
· Weight
· MaterialId (standard material ID or project component Id)
· Revision
· Unit
· OwnedBy
· External_Ref
Page 140

The integration workflow for fabricates from AVEVA Marine to AVEVA ERM is as follows:
1. Configure a filter for fabricates in AVEVA Marine.
2. Update the status of fabricates in AVEVA Marine.
3. Publish the fabricates in AVEVA Marine.
4. Import the fabricates in AVEVA ERM.
Configure a filter for fabricates

integration of fabricates. For more information about the Filter Configuration tab, see
information in the PartList Preview. Select the check box for the required rows and save
Page 141
Update the status of fabricates

In AVEVA Marine, a status called “PublishingStatus” is defined for all part list elements.
The status of the STRUCTURE is modified through the Status controller window. Only
approved designs can be published. Therefore, a STRUCTURE must be progressed to
‘Identified’ before publishing.
Publish the fabricates

Page 142
Select the required STRUCTURE and click Publish to expose data to AVEVA ERM. Status of
the STRUCTURE is moved to ‘Published’ and an ‘Update’ notification is sent to AVEVA
ERM.
Page 143
Import the fabricates in AVEVA ERM

can act on it.
To import the fabricates in AVEVA ERM:

2. Select the message with object type Fabricate for the appropriate design
project and click Process. The fabricates from AVEVA Marine are imported.
The import of fabricates from AVEVA Marine can also be done without an ‘Update’
grids. When import is completed in AVEVA ERM, the system generates an
Verify the imported data in AVEVA ERM

After the fabricates are imported, AVEVA ERM creates or updates the fabricate
information accordingly. The fabricate catalogue in AVEVA ERM can be seen in the s20017
Fabricate Catalogue screen.
The standard materials, project components or fabricates added as part list items under
the header Structure elements can be seen in AVEVA ERM through the s21015 Fabricate
Part Lists screen.
Page 144
Provide feedback on data processing in AVEVA ERM


17.5 Outfitting Part List

This section describes the concepts and procedure for outfitting part list integration.

The Outfitting Part list is based on ZONE in AVEVA Marine. The transfer to AVEVA ERM
exports all data for a particular ZONE.
When the publishing status of the outfitting part lists in AVEVA Marine reaches the status
“Published”, the data is published either using the OutfittingPartList_Published DB
view or the PartListDesign PML function. This data in the source table is made available
through AVEVA Integration Service, and is consumed in AVEVA ERM. AVEVA ERM
connects to the Integration Service and transfers the available data into the
corresponding concepts (Drawing, Part List header, Part List items).
Page 145
· OwningParentDesignObject (ZONE name)
· DesignObjectType (ActualType element in AVEVA Marine, for example PIPE,
FLAN, VALV and so on)
· SchematicUniqueId (Name, or Dabacon Id for linked schematic element)
· DesignProjectID
· Unit
· MaterialId (:MaterialId of catref if available, otherwise object name)
· Revision (Currently 1)
· External_Ref
Handling Bolts Information
The PartListDesign PML function can be used for integrating the bolting information as
well. However, the following tasks must be completed for bolts to be included in the part
list:
· Bolt table is created in AVEVA ERM Catalogue Manager.
· Bolts are published to AVEVA ERM as standard materials.
· Bolt table in AVEVA ERM is synchronised with Design Catalogue.
· Bolt specification is configured for the pipe specification.
· SBOL element has an attribute NSTD and it points to AVEVA ERM Part Ids (that is,
DTAB).
· Nuts and washers are treated as standard materials (and synchronised with
AVEVA ERM) on GPART level.
· CMPREF, MATTXT, DTEXT are configured in the project for nuts and washers.
For more information, refer to the user guide of AVEVA Marine.
Note: Integration of bolt part lists is available using the PartListDesign PML function
only, and not using the OutfittingPartList_Published DB view.
Page 146
17.5.2 Integration workflow - Data Transfer to AVEVA ERM

The integration workflow for outfitting part lists from AVEVA Marine to AVEVA ERM is as
follows:
1. Configure a filter for outfitting part lists in AVEVA Marine.
2. Update the status of outfitting part lists in AVEVA Marine.
3. Publish the outfitting part lists in AVEVA Marine.
4. Import the outfitting part lists in AVEVA ERM.
Configure a filter for outfitting part lists

integration of outfitting part lists.
A new part list setting must be created in AVEVA Marine before transferring data. The
Select for Publish check box column allows the users to view the selected information in
the PartList Preview. Select the check box for the required rows and save the settings by
clicking Save.
Page 147
Update the status of outfitting part lists

In AVEVA Marine, a status called “PublishingStatus” is defined for all outfitting elements.
The status of the ZONE, FABRICATE and PIPESPOOL is modified through the Status
controller window. Only approved designs can be published. Therefore, a ZONE must be
progressed to ‘Approved’ before publishing.
Publish the outfitting part lists

Select the required ZONE and click Publish to expose data to AVEVA ERM. Status of the
ZONE is moved to ‘Published’ and an ‘Update’ notification is sent to AVEVA ERM.
Import the outfitting part lists in AVEVA ERM

can act on it.
Page 148
To import the outfitting part lists in AVEVA ERM:

2. Select the message with object type Outfitting for the appropriate design
project and click Process. The outfitting elements from AVEVA Marine are
imported.
The import of outfitting part lists from AVEVA Marine can also be done without an
grids. Click Show import file audits to view all audit messages for a single file run in a
batch. Click Show all audits to information related to all audits.

or ‘Error’ notification according to the result of the import. An Outfitting import can
generate both Acknowledgement and Error notifications if only few part list headers were
successfully imported. Both Acknowledgement and Error notifications have the Part List
header Id as ID.
Verify data in AVEVA ERM

After the outfitting elements are imported, AVEVA ERM creates or updates the outfitting
information accordingly. The Zones published from AVEVA Marine are added to the
drawing catalogue in AVEVA ERM, and can be viewed in the s20012 Drawing Catalogue
screen.
Page 149
Additionally, AVEVA ERM also creates a Part List header and a list of part list items which
hold the material. This information is displayed in AVEVA ERM on the s21000 Part Lists
screen.
Provide feedback on data consumption in AVEVA ERM

or ‘Error’ notification according to the result of the import. An Outfitting import can
generate both Acknowledgement and Error notifications if only few part list headers were
successfully imported. Both Acknowledgement and Error notifications have part list
header Id as the ID.
Process the feedback in AVEVA Marine

Page 150
CHAPTER 18 - Hull Material Control
18 Hull Material Control

The following diagram describes how the hull concepts are defined in AVEVA ERM and
AVEVA Marine:

The transfer of data is done using AVEVA ERM-Design Integration from AVEVA Marine. DB
views and PML functions are defined on AVEVA Marine to identify the data that should be
transferred. Using Status Control mechanism, the data is progressed to the status needed
for transfer. Hull concept integration is related to all objects below Assembly/Block
having a material/equipment reference.

AVEVA ERM provides specialised functions for defining hull material, parts lists of raw
plates and profiles for sections/blocks and DRLs. Hull material parts lists provide precise
input for the procurement process and surplus hull material is closely managed.
The Hull Material is defined in two catalogues: Plates and Profiles. For each project, a list
of units must be defined and for these units, the estimated requirement of raw materials,
steel profiles and plates that are related to an activity also must be defined to get an
estimated need date. AVEVA ERM calculates the requirements for hull steel and this
information can be used while ordering Hull Plates and Profiles. Once the purchased
materials are received, they can be requested for pick up in production by using the DRL
and Picking List function.
Page 151
The following diagram illustrates the workflow for hull material control.
The following steps are involved in Hull Material Control. For more information about
these steps, see the documentation for AVEVA ERM and AVEVA Marine.
· Define Dimension Codes for Hull Plates and Profiles in AVEVA ERM and AVEVA
Marine
· Define Quality Standards for Hull Plates and Profiles in AVEVA ERM and AVEVA
Marine
· Define Hull Plates and Profiles Catalogue in AVEVA ERM and AVEVA Marine
· Synchronize Hull Plates and Profiles Catalogue between AVEVA Marine and
AVEVA ERM using integration feature
· Define Hull Units in AVEVA ERM or Transfer MANPKG (Hull Manufacturing
Element) from AVEVA Marine
· Define Hull Unit Material List in AVEVA ERM
· Make currently available steel material in AVEVA ERM in screen s30000 Hull Unit
Material List available in AVEVA Marine. Transfer Hull Unit Material List to
AVEVA Marine
o This will provide a list of raw plates and profiles reserved for a Hull Unit
(Block/Section)
o The list will be available for nesting in AVEVA Marine
Page 152
· Transfer Hull Nesting Information from AVEVA Marine to AVEVA ERM after
nesting is completed
· Import Hull Material Delivery Request List from AVEVA Marine into AVEVA ERM
o When performing the nesting in AVEVA Marine, the combination of the
nesting information and reserved plates/profiles will be written back into
AVEVA ERM as a “Hull Material Delivery Request List”
o When nesting has been performed and only parts of a plate/profile has been
used, the “Leftover” or “Rest Plates” should be returned to AVEVA ERM with
the new dimensions and stored as a new plate/profile marked as “Leftover”
The following diagram illustrates the workflow for nesting plates and profiles.
18.3 Synchronize Hull Plates and Profiles Catalogue

Refer to the documentation of AVEVA ERM and AVEVA Marine.
18.4 Hull Units

Hull units are created to handle the material allocation of raw plates and raw profiles
which will be used later by the user for nesting.

The data (list of MANPKG in AVEVA Marine) is published either using the
HullBlocks_Published DB view or the HullUnit PML function, which is made available
through AVEVA Integration Service. AVEVA ERM connects to AVEVA Integration Service
and transfers the available data to the corresponding concepts.
Page 153
· DesignProjectID
· Name
· Description

The integration workflow for hull units from AVEVA Marine to AVEVA ERM is as follows:
1. Configure a filter for hull units in AVEVA Marine.
2. Update the status of hull units in AVEVA Marine.
3. Publish the hull units in AVEVA Marine.
4. Import the hull units in AVEVA ERM.
Configure a filter for hull units

integration of hull units.
Page 154
clicking Save.
Update the status of hull units

There is no need to update the status of hull units as all MANPKG are transferred from
AVEVA Marine to AVEVA ERM.
Page 155
Publish the hull units

All the MANPKG are exported to AVEVA ERM. Status of the MANPKG is moved to
“Identified”.
Import the hull units in AVEVA ERM

can act on it.
To import the hull units in AVEVA ERM:

2. Select the message with object type HullUnit for the appropriate design
project and click Process. The hull units from AVEVA Marine are imported.
The import of hull units from AVEVA Marine can also be done without an ‘Update’
Page 156

After the hull units are imported, AVEVA ERM creates or updates the hull units
information accordingly. The hull units in AVEVA ERM can be seen in the s30001 Hull
Units screen.

After the hull units are imported, an ‘Acknowledgement’ or ‘Error’ Message is sent to
AVEVA Marine depending on the import result. The same message is available in the
s14002 Integration Messages screen

from the source table. Status of the MANPKG is moved to “Work In Progress”.
Page 157
18.5 Allocating Material for Nesting

The following diagram illustrates the workflow allocating material (raw plates, raw
profiles ) from AVEVA ERM to a AVEVA Marine project for nesting.

The following information is transferred while allocating material for nesting:
· Hull Unit (Block Id)
· ProjectId
· Material Category (Plate or Profile)
· Material Id (corresponding to catalogue Id in Paragon)
· Quantity (number of raw plates or profiles with the given material Id and size)
· ERM_PLItemNo - Unique Part List item identification
· MarineUniqueReference
Page 158
18.5.2 Integration Workflow - Data Transfer from AVEVA ERM

The integration workflow for allocating materials from AVEVA ERM to AVEVA Marine is as
follows:
1. Allocate materials to hull unit in AVEVA ERM.
2. Publish hull unit material list in AVEVA ERM.
3. Import the hull units in AVEVA Marine.
4. Verify data in AVEVA Marine.
Allocate materials to hull unit in AVEVA ERM

In AVEVA ERM, the list of hull materials required to build a hull unit is defined and
maintained in the s30000 Hull Unit Material List screen. The purpose of a hull unit
material list is same as that of a part list. Materials of type hull profile (PR) and hull plate
(PL) can be used on a hull unit material list. Only one hull unit material list can be defined
for a hull unit.
The s30000 Hull Unit Material List screen consists of two data grids: Hull Material List
Header and Hull Unit Material List Items. The header holds the reference to the hull unit
which acts as a container holding the material list line items. The materials placed as line
items forms the basis for material requirement which can be viewed through the s50022
Material Status screen.
For more information, refer to s30000 Hull Unit Material List user document.
Page 159
When allocation is done for a hull unit, the following should be checked before publishing
the Hull Unit Material list information to AVEVA Marine:
· Quantity, system and activity should be added on a line item. Activity
information is not transferred to AVEVA Marine, but it is required for the next
step of the integration, when delivery request lists (DRLs) are created in AVEVA
ERM.
· Change the status of the Hull Material Unit using one of the following:
o Workflow > Issue or
o Planning > Totally Planned and Technical > Ready for Production
Publish hull unit material list in AVEVA ERM

To publish the hull unit material list to AVEVA Marine:
· Select the hull unit in the s30000 Hull Unit Material List screen and click Data
Management > Publish Hull Material List to Design.
Note: Information published will overwrite any proposed allocation done in
AVEVA Marine earlier.
The Material List information is available in a view shared with AVEVA Marine.
Along with this an ‘Update’ message is sent to AVEVA Marine with context
PlatesProfilesOnHullUnit.
Page 160
Import the hull units

In AVEVA Marine, an FMTRPO element must be created in Hull design to switch from
nesting mode into material handling mode to integrate with AVEVA ERM.
AVEVA ERM sends an ‘Update’ message with context “PlatesProfilesOnHullUnit” when

the hull material list is published. On the AVEVA Marine side, this information can be
imported through the Notifications dialog box.
To import data, select the Update message and click Update Database.
Page 161
Verify data
After the import of data is successful, the following can be checked in AVEVA Marine:
· Hull unit that corresponds to a manufacturing package in AVEVA Marine
(MANPKG) is created.
· For each manufacturing package, a folder is created (MPKGFL), containing the
allocated raw material .
· For each material Id, a corresponding specification object is created (FPRJPR for
steel plate or FPRJPL for profile).
· Under the specification object, x number of plate or profile instances (FPRJIN or
FPLJIN) objects are created, where x corresponds to the quantity in this record.
For each of the FPxJIN objects, the attribute “Avbity” is set to “Available”.
Provide feedback on data consumption

After the data transferred is imported in AVEVA Marine, feedback on data consumption is
sent to AVEVA ERM. This means an ‘Acknowledgement’ or ‘Error’ notification is sent
from AVEVA Marine to AVEVA ERM using the notification workflow.
Page 162
View the feedback in AVEVA ERM

The ‘Acknowledgement’ and ‘Error’ messages are displayed in the s14002 Integrated
Messages screen of AVEVA ERM.
18.6 Nesting Information

In the s30002 Nesting Information - Hull screen, any necessary weld and cutting
information for each individual nest can be maintained. For more information, refer to
s30002 Nesting Information - Hull user document.
After nesting is completed for MANPKG, the nesting information can be transferred to
AVEVA ERM using AVEVA ERM-Design Integration.

This part list is based on nestings in AVEVA Marine, and all nesting data for a particular
block can be exported. When the publishing status of nestings in AVEVA Marine reaches
the status ‘Published’, the data is published either using the NestingList_Published DB
view or the NestingList PML function, and is made available to AVEVA ERM through
AVEVA Integration Service. AVEVA ERM connects to AVEVA Integration Service and
transfers the available data into the corresponding concept.
Page 163
· DesignProjectID
· NestingId
· MarkingMeter
· CuttingMeter
· BurnerId (Machine identifier)
· PathTime (Estimated time for production)
Important: While creating the nesting information, you must make sure that all
alphabetic characters in the NestingId are in uppercase. If the NestingId is not in
uppercase, the data may not be transferred correctly.
After consuming the data into AVEVA ERM, the publishing status in AVEVA Marine is
changed. This makes sure that the data is removed from the source so that the same data
is not transferred again to AVEVA ERM.

The integration workflow for nesting information from AVEVA Marine to AVEVA ERM is as
follows:
1. Configure a filter for nesting information in AVEVA Marine.
2. Update the status of nestings in AVEVA Marine.
3. Publish the nestings in AVEVA Marine.
4. Import the nestings in AVEVA ERM.
Configure a filter for nesting information

integration of nesting information.
clicking Save.
Page 164
Update the status of nesting elements

In AVEVA Marine, a status called “PublishingStatus” is defined for all nestings. The status
of the assembly, plate and profile nestings are modified through the Status controller
window. Only approved nestings can be published. MPLNST or MPRNST must be
progressed to the defined ‘Filtering Status’ before publishing. Only those items that have
reached the status defined in the filtering status can be selected for publishing. The
publishing status of an item is the status the item reaches when Publish is clicked.
Page 165
Publish the nestings

Select the required nesting element and click Publish to expose data to AVEVA ERM.
Status of the MPLNST/MPRNST is moved to ‘Published’ and an ‘Update’ notification is
sent to AVEVA ERM.
Import the nestings in AVEVA ERM

can act on it.
Page 166
To import the nesting elements in AVEVA ERM:

2. Select the message with object type NestingInfo for the appropriate design
project and click Process. The nesting elements are imported from AVEVA
Marine.

After successful import of nesting information from AVEVA Marine, AVEVA ERM displays
the nesting information in the s30002 Nesting Info Hull screen under the specific project.

After the import is done, AVEVA ERM sends feedback on data consumption to AVEVA
Marine using the notification mechanism. In case of successful import, an
‘Acknowledgement’ is sent, and in case of an error, an ‘Error’ message is sent to AVEVA
Marine.

Page 167
18.7 Publish Actual Material Usage to AVEVA ERM

This section describes the concept and procedure for integration of actual material usage.
18.7.1 Concept Description

After receiving hull unit material, nesting is done on the fabricate unit (FPRJIN or FPLJIN).
When nesting is completed for FPRJIN or FPLJIN of MANPKG, actual material usage for a
MANPKG is calculated and ready to be sent to AVEVA ERM.
Page 168
The following image shows how nesting is performed in AVEVA Marine.
Note: Before publishing the actual material usage, nesting information must be already
transferred to AVEVA ERM.
Page 169

The following information is transferred while publishing actual material usage to AVEVA
ERM:
· Project
· Hull Unit (MANPKG)
· Material Category (Plate or Profile)
· Material Id (corresponding to catalogue item in Paragon)
· Quantity (number of raw plates or profiles with the given material Id and size,
that has been used.)
· MarineUniqueReference (if available)
· ERM_PLItemNo (transferred previously in the Hull Material List)
· Used Nesting Id (filled always for DRL)
· RestPlateindicator
· Originating Nesting Id (if it is a rest plate)
· SizeL (only filled in case of a rest plate)
· SizeB (only filled in case of rest plate)

The integration workflow for actual material usage from AVEVA Marine to AVEVA ERM is
as follows:
1. Configure a filter for actuals in AVEVA Marine.
2. Update the status of actuals in AVEVA Marine.
3. Publish the actual material usage in AVEVA Marine.
4. Import the actual steel material usage in AVEVA ERM.
Configure a filter for actual material usage

integration of actual material usage.
clicking Save.
Page 170
Actual Material Usage is published based on MANPKG and how many quantities of FPRJIN
or FPLJIN is consumed by MANKPKG.
Update the status of actual material usage

In AVEVA Marine, a status called “PublishingStatus” is defined for all hull elements. The
status of the MANPKG is modified through the Status controller window. Only those
items that have reached the status defined in the filtering status can be selected for
publishing.
Publish the actual material usage

Type of the Element and Publishing status) in the first grid.
Select the required MANPKG element and click Publish to expose data to AVEVA ERM.
Status of the MANPKG is moved to ‘Published’ and an ‘Update’ notification is sent to
AVEVA ERM.
Page 171
The following screen shot is an example of the preview of the element with all the
attributes that can be published to AVEVA ERM.
Import the actual steel material usage in AVEVA ERM

After plate and profile nesting has been performed in AVEVA Marine, the actual material
usage is sent back to AVEVA ERM into Hull DRL.
The s30003 Hull Material Delivery Request List screen contains the hull material requests
that can be directed to the warehouse through the s60030 Warehouse Dispatch List
screen.The status of the DRLs after transfer is O-DRL (DRL Not Completed).
Also, in screen s30017, the rest plates that were created based on the information
transferred from AVEVA Marine can be identified.
AVEVA Marine sends an ‘Update’ message when actual material usage is published to
AVEVA ERM.
import in AVEVA ERM. An ‘Update’ notification with context “ActualSteelMaterialUsage”
is received in AVEVA ERM and the user can act on it.
Page 172
To import the actual material usage in AVEVA ERM:

2. Select the message with object type ActualSteelMaterialUsage for the
appropriate design project and click Process. The actual materials from AVEVA
Marine are imported.
The import of actual materials from AVEVA Marine can also be done without an ‘Update’

After import of data is successful, the hull material delivery request list can be verified in
the s30003 Hull Material Delivery Request List screen. In the current transfer, the system
will create one Hull Material-DRL per combination of project, hull unit and activity.
Page 173
AVEVA ERM creates LeftOver (Rest Plates) as Catalogue item if any are transferred from
AVEVA Marine.
There are also created Design Left Over entries that could be used when the actual Hull
Material Left Over is created on screen s30010 later in the process (this is done manually
in AVEVA ERM and it applies to the rules of this screen).

After the data transferred is imported in AVEVA ERM, feedback on data consumption is
sent to AVEVA Marine. This means an ‘Acknowledgement’ or ‘Error’ notification will be
sent from AVEVA ERM to AVEVA Marine using the notification workflow.
Page 174
‘Acknowledgement’ and ‘Error’ messages are displayed in Notifications dialog box of

AVEVA Marine. For an ‘Acknowledgement’ message, AVEVA Marine deletes any unused
plates and promotes the status of MANPKG to “Imported”. For “Error” message, AVEVA
Marine demotes the status of MANPKG to “Rework”.
Left over can be assigned to another hull unit and transferred back to AVEVA Marine.
Page 175
On receiving, AVEVA Marine will move the leftovers to the newly allocated MANPKG.
Page 176
CHAPTER 19 - AVEVA ERM Planning and Assembly Planning
19 AVEVA ERM Planning and Assembly Planning

This section describes the concepts and procedure for AVEVA ERM planning and assembly
planning.

Assembly planning provides the functionality to manage, create and maintain the
complete production breakdown structure. This includes the production hierarchy for the
hull and the installation of equipment, electrical, HVAC and Outfit steel. An assembly
could be a physical steel unit (including outfit installation), but an assembly could also
correspond to a space (e.g. a compartment or a room) and thereby include all the
prefabricated units, material and components to be installed into this space.
The hierarchical assembly tree (the production breakdown structure) is defined and
maintained in parallel with the design and modelling work. The rough build strategy is
defined in the early phase of a project, and further refined into a detailed build strategy
along with the refinement of the model. As soon as model parts are available in Design,
they can be collected to nodes in the assembly tree. Thus, the Assembly view of the
product is available from the very beginning of the design, and is continuously developed
during the design process. Assembly Planning allows the detailed design model to be
viewed as a production mode.
19.2 Transfer AVEVA ERM Work Packages to AVEVA Marine

The transfer of work packages are defined in the assembly structure (AVEVA Planning) on
AVEVA ERM and it is expected to be transferred to AVEVA Marine (Assembly Planning).
Work Packages are published from AVEVA ERM from screen s11001-Project Gantt view.
By using the Notification Service, when AVEVA ERM is publishing a work package for a
project, a notification is sent to the Notification Service and further to AVEVA Integration
Service which in turn sends this notification to AVEVA Marine. When AVEVA Marine
receives this notification, it can act on it by importing the data available for the work
package transfer.
After the import is completed, the assemblies will be created from work packages in
AVEVA Marine based on assembly mapping settings and an Acknowledgement or Error
message is sent back per the import result.
Page 177
The following diagram illustrates the functional workflow of how the work packages in
AVEVA Planning are transferred to Assembly Planning.

The following fields are transferred from AVEVA ERM:
· ASSY_REF
· DISCIPLINE
· WP_NAME
· WP_REF
· DESCRIPTION
· PROJECT_ID
Page 178
19.2.2 Integration Workflow – Data Transfer from AVEVA ERM

The integration workflow for transferring work packages from AVEVA ERM to AVEVA
Marine is as follows:
1. Create a work package in AVEVA ERM.
2. Publish the work package in AVEVA ERM.
3. Import work packages in AVEVA Marine.
4. Verify data in AVEVA Marine.
5. Process Acknowledgement or Error notification in AVEVA ERM.
Page 179
Create a work package in AVEVA ERM

To create a work package in AVEVA ERM:
1. Open Screen s11001 Project Gantt View and select the required project.
2. Click Load. The Project Gantt View screen is displayed.
3. Click New.
4. On the s11001 Planning tab, click Change Type, and then select Production.
5. Mark ‘Publish to Assembly Planning’ and select Assembly Type.
Page 180
Publish work package from AVEVA ERM

To publish the work package from AVEVA ERM:
1. Open screen s11001 Project Gantt View and select Data Management.
2. Click Publish WorkPackages to Marine. The work packages will be available in

a view shared with AVEVA Marine.
Note: The publish of work packages is done on project level. The information
message that mentions that ‘1 of 1 records are published’ refers to the project
key and it will be the same irrespective of the number of work packages.
3. When the work package is published, an Update message is created and sent
to the Notification Service.
Page 181
Import work packages in AVEVA Marine

When AVEVA ERM publishes the work package information, an “Update” notification is
sent to AVEVA Notification Service. This message is displayed in AVEVA Marine in the
Notifications screen. AVEVA Marine retrieves the data from AVEVA Integration Service
and displays the message details of the work packages that are published from AVEVA
ERM.
To import the work packages from AVEVA ERM into AVEVA Marine, select the work
packages and click Update Database.
After importing into AVEVA Marine, an Acknowledgement or Error message is sent back
to AVEVA ERM.
Note: The Acknowledgement or Error notification contains only the project information,
and not the entire work package structure.
Verify data transferred in AVEVA Marine

After a successful update, components are created or updated in AVEVA Marine. ASMBLY
are created in AVEVA Marine per the mapping defined.
Page 182
Process Acknowledgement or Error message in AVEVA ERM

After the data transferred is imported in AVEVA Marine, a feedback on the data
consumption is sent to AVEVA ERM. This means an Acknowledgement or Error
notification will be sent from AVEVA Marine to AVEVA ERM using the notification
workflow. This makes sure that after a data transfer is completed, the same data is not
sent again until it is changed and published again.
Acknowledgement or Error messages are automatically picked by AVEVA ERM and when
processing the notification, the status of the project work package published will be
marked according to the feedback received from AVEVA Marine.
19.3 Outfitting Assembly Part List

Outfitting data can be transferred to AVEVA ERM from the Design hierarchy (SITE/ZONE
and so on) into the ERM part list structure at any time before transfer of assembly
structure.
When the assembly structure is transferred, the Zone based structure is rearranged.
Items previously belonging to a ZONE-based part list are rearranged to belong to an
Assembly-based structure.
When publishing ZONE data, Pipe Spools should be automatically imported into the
fabricate catalogue. If re-transferring the ZONE after spooling, it should rearrange to refer
to spool and previously loose pipe parts will be moved to the spool (fabricate) part list.
Imported work packages generate Assembly structure also for Outfitting. Collect
Outfitting into Assembly structure and transfer to AVEVA ERM as a separate transfer.
When the outfitting in the Assembly is imported into AVEVA ERM, the already transferred
part list based on ZONE, will be deducted and moved to the Assembly based part list.
Data integrity must be ensured so that parts are not counted twice.
Page 183
The following diagram illustrates how outfitting part lists are transferred and work orders
are generated.

Design data is collected into assemblies that are transferred into part list based on
Outfitting Assembly in AVEVA Marine. The transfer to AVEVA ERM exports all data for an
Outfitting Assembly. The data is published into a DB View, which is made available
through the Integration Service. AVEVA ERM connects to the Integration Service and
transfers the available data into corresponding concept from AVEVA ERM (Drawing, Part
List header, Part List items).
The source tables used is either the OutfittingPartList_Assembly_Published DB view

or the PartListAssembly PML function. Data is available when the Publishing status in
AVEVA Marine reaches the status “Published”.
Page 184
· OwningParentDesignObject (Assembly name)
· DesignObjectType (ActualType element in AVEVA Marine, for example PIPE,
FLAN, VALV etc.)
· SchematicUniqueId (Name, or Dabacon Id for linked schematic element)
· DesignProjectID
· Unit
· MaterialId (:MaterialId of catref if available, otherwise object name)
· Revision (Currently 1)

The integration workflow for transferring the OutfittingAssembly PartList information
from AVEVA Marine to AVEVA ERM is as follows:
1. Configure a filter in AVEVA Marine.
2. Update the status for the PartList to Identified.
3. Publish components from AVEVA Marine to AVEVA ERM.
4. Import data into AVEVA ERM.
5. Verify the transferred data in AVEVA ERM.
6. Provide feedback on data consumption.
7. Process feedback in AVEVA Marine.
Configure a filter in AVEVA Marine

integration of outfitting assembly part lists.
Page 185
clicking Save.
Update the status for the PartList to Identified

AVEVA Marine defines a status called “PublishingStatus” for all part list elements. The
status of ASMBLY is modified through the Status controller window. Only approved
designs can be published. ASMBLY should be progressed to “Identified” state before
publishing.
Page 186
Publish components from AVEVA Marine to AVEVA ERM

Select the required ASMBLY element and click Publish to expose data to AVEVA ERM.
Status of the ASMBLY is moved to ‘Published’ and an ‘Update’ notification is sent to
AVEVA ERM.
Page 187
Import data into AVEVA ERM

AVEVA Marine sends an ‘Update’ message when outfitting assembly part list is published
to AVEVA ERM.
import in AVEVA ERM. An ‘Update’ notification with context “OutfittingAssembly” is
received in AVEVA ERM and the user can act on it.
To import the outfitting assembly part list in AVEVA ERM:

2. Select the message with object type OutfittingAssembly for the appropriate
design project and click Process. The outfitting assembly part list items from
AVEVA Marine are imported.
The import of outfitting assembly from AVEVA Marine can also be done without an
grids. Click Show import file audits to view all audit messages for a single file run in a
batch. Click Show all audits to information related to all audits.

Page 188

After the outfitting assembly part list elements are imported, AVEVA ERM creates or
updates the assembly information accordingly. The assemblies published from AVEVA
Marine are added to the drawing catalogue in AVEVA ERM, and can be viewed in the
s20012 Drawing Catalogue screen.
After a successful import of outfitting assembly Part List data from AVEVA Marine, all the
assemblies published from AVEVA Marine will be added on drawing catalogue in AVEVA
ERM which is available on screen s20012.
Additionally, AVEVA ERM also creates a Part List header and a list of Part List items which
hold the material. This information is displayed in AVEVA ERM on the s21000 Part Lists
screen.
If the OutfittingAssembly transfer is done after the Outfitting data was already
transferred to AVEVA ERM, the items from Outfitting Part Lists corresponding to the
ZONEs already transferred are moved to Assembly Drawing Part Lists. In order to identify
the items that should be moved, it uses the DesignUniqueId information mapped in
AVEVA ERM as Model Ref.
Page 189
After the import is done AVEVA ERM sends feedback on data consumption to AVEVA
Marine using the notification mechanism. When the import finished successfully,
‘Acknowledgement’ is sent back to AVEVA Marine. In case of problems during import, an
‘Error’ is sent to AVEVA Marine.

Marine using the notification mechanism. When the import is completed successfully,
‘Acknowledgement’ is sent back to AVEVA Marine. In case of problems during import, an
‘Error’ is sent to AVEVA Marine.
An OutfittingAssembly import can generate both Acknowledgement and Error

notifications if only few part list headers are successfully imported. Both
Acknowledgement and Error notification have the same Id as Part List header Id.
Process feedback in AVEVA Marine

Page 190
19.4 Transfer Hull Plate and Profile Part List from AVEVA Marine to
AVEVA ERM
The following image depicts how hull plate and profile part lists are transferred from
AVEVA Marine to AVEVA ERM.
The following image depicts transfer of hull parts and generations of work orders and
jobs.
Page 191

This part list is based on Production Block in AVEVA Marine, and exports all data for a
particular assembly. When the publishing status in AVEVA Marine reaches the status
‘Published’, the data is published either using the SteelPartList_Published DB view or
the PartListSteel PML function, and is made available to AVEVA ERM through AVEVA
Integration Service. AVEVA ERM connects to the Integration Service and transfers the
available data into the corresponding concepts: Fabricate, Fabricate Part List header and
Fabricate Part List items.
The following fields are transferred from AVEVA Marine to AVEVA ERM:
· DesignProjectID
· Type
· Fabricate ID (Assembly ID)
· Fabricate Type (“Hull unit” or equivalent)
· Description
· Weight
· Material Category (F)
· MaterialId (plate or profile part ID)
· DesignUniqueID (Name, or dabacon Id)
· DrawingQuantity (Quantity w/excess)
· Revision
· Unit
· NestingId (New column in ERM)
· Root fabricate (True or False)
After consuming the data into AVEVA ERM, the publishing status in AVEVA Marine is
changed. This will make the data disappear from the source table so that it is not
transferred again to AVEVA ERM.
Page 192

The integration workflow for hull plate and profile part lists from AVEVA Marine to AVEVA
ERM is as follows:
1. Configure a filter for hull plate and profile part lists in AVEVA Marine.
2. Update the status of the hull plate and profile part lists in AVEVA Marine.
3. Publish components from AVEVA Marine to AVEVA ERM.
4. Perform receiving application steps in AVEVA ERM.
5. Import steel parts into AVEVA ERM.
6. Verify the transferred data in AVEVA ERM.
Configure a filter for hull plate and profile part lists in AVEVA Marine
integration of hull plate and profile part lists.
clicking Save.
Page 193
Update the status of the hull plate and profile part lists in AVEVA Marine
In AVEVA Marine, a status called “PublishingStatus” is defined for all hull design elements.
The status of the Assembly, Plate and Profile nesting are modified through the Status
controller window. Assembly must be progressed to the state defined by the Filtering
Status in the Settings dialog box before publishing.
Publish components from AVEVA Marine to AVEVA ERM

Page 194
Perform receiving application steps in AVEVA ERM

The following screen depicts the hull assembly planning structure in AVEVA Marine:
The top node fabricate is created as a drawing (s20012) and as a Part List in s21000. This
data has to be created manually in AVEVA Marine before transferring steel plates and
profiles part list to AVEVA ERM.
Import steel parts into AVEVA ERM

can act on it.
Page 195
To import the hull plate and profile part lists in AVEVA ERM:
2. Select the message with object type steelstructure for the appropriate design
project and click Process. The hull plate and profile elements from AVEVA
Marine are imported.

After successful import of the SteelPartList_Published DB view or PartListSteel PML
functionfrom AVEVA Marine, all the Hull parts and assembly names are added as
fabricates in the s20017 Fabricate Catalogue screen.
Page 196
All the Hull parts and assembly names are also added to the s21015 Fabricate Part List
screen in the same hierarchy as they are collected in Marine Assembly planning.
Hull Unit Installation Drawing is specified in the current project attributes from AVEVA
ERM. This Drawing is used to hold all the top node Fabricates as a Part List in s21000 for
the Hull Assembly structure, i.e. the assembly level.
Page 197

Marine using the notification mechanism. When the import is completed successfully, an
‘Acknowledgement’ notification is sent back to AVEVA Marine. In case of problems during
the import, an ‘Error’ notification is sent to AVEVA Marine.
Page 198
Process feedback in AVEVA Marine

Page 199
CHAPTER 20 - Deletion
20 Deletion
This section describes the integration process for delete operations standard materials,
raw plates, raw profiles and project components.

The workflow described in this section is applicable to all materials (project component,
raw plate, raw profile and standard materials). The workflow is applicable to cases where
one master record is being deleted.
The following points must be noted while performing the integration of delete
operations:
· To ensure synchronisation between two applications, deletion performed in one
application requires an “approval” from the other if the information has already
been transferred.
· If the information has not been transferred, the application owning the data can
delete the data without any approval workflow.
· An application that does not own the data cannot delete the data. For example,
if AVEVA Marine transfers standard materials to AVEVA Enterprise Resource
Management (AVEVA ERM), AVEVA ERM cannot delete the standard materials,
unless the user has admin rights.
Page 200
The following diagram explains the delete workflow that is applicable when a component
created in System 1 was transferred to System 2, and later, System 1 tries to delete the
component.
Message topics CanDeleteRequest, CanDeleteAcknowledgement, CanDeleteError

and Delete support the delete workflow. These messages contain information about the
components and components can be identified by External Ref, when this has a value in
the notification.
20.2 Delete Workflow (Initiated in Design Application)

This following workflow is followed when the delete operation is initiated in AVEVA
Marine:
1. Design application sends CanDeleteRequest.
2. AVEVA ERM processes CanDeleteRequest.
3. Design application processes CanDeleteAcknowledgement/CanDeleteError.
4. AVEVA ERM processes Delete.
Page 201
20.2.1 Design application sends CanDeleteRequest

When the delete operation is initiated in AVEVA Marine (right-click the element and
select Delete), the system marks the element for delete by appending the element name
with “_ForDelete” and a CanDeleteRequest notification is sent to AVEVA ERM for
approval.
AVEVA Marine sends the CanDeleteRequest only under the following circumstances:
· If the element is already published
· If the element is not used in design
Page 202
20.2.2 AVEVA ERM processes CanDeleteRequest

AVEVA ERM receives CanDeleteRequest and generates one of the following
notifications as a response:
· CanDeleteAcknowledgement if the component is not used in AVEVA ERM.
When CanDeleteAcknowledgement is generated, AVEVA ERM marks the
component with ReadyforDelete status. This ensures that the component will
not be used in the system anymore.
· CanDeleteError if the deletion of the component is not allowed in AVEVA ERM.
When the notification contains the ExternalReferenceId information, the same is used to
identify the data (instead of the Id).
Page 203
20.2.3 Design application processes CanDeleteAcknowledgement/CanDeleteError

When AVEVA Marine receives a CanDeleteAcknowledment notification, it deletes the
component and sends a Delete notification to AVEVA ERM.
20.2.4 AVEVA ERM processes Delete

When AVEVA ERM receives a Delete notification, the record is physically deleted from
AVEVA ERM. When the ExternalReferenceId information is in the notification, the same is
used to identify the component.
Page 204
20.3 Delete Workflow (Initiated in AVEVA ERM)

This following workflow is followed when the delete operation is initiated in AVEVA ERM:
1. AVEVA ERM sends CanDeleteRequest.
2. Design application processes CanDeleteRequest.
3. AVEVA ERM processes CanDeleteAcknowledgement/CanDeleteError.
4. Design application processes Delete.
20.3.1 AVEVA ERM sends CanDeleteRequest

When the delete operation is initiated in AVEVA ERM for the data that is already
transferred to AVEVA Marine, the element status is changed to ‘Ready For Delete’ in
AVEVA ERM and a CanDeleteRequest notification is sent to AVEVA Marine.
Page 205
20.3.2 Design application processes CanDeleteRequest

When AVEVA Marine receives a CanDeleteRequest, it verifies if the component is used
in any design. The Notifications screen provides an option for the user whether to send
the CanDeleteAcknowledgement/CanDeleteError based on user choice.
20.3.3 AVEVA ERM processes CanDeleteAcknowledgement/CanDeleteError

After receiving a CanDeleteAcknowledgement notification, AVEVA ERM deletes the
element and sends a Delete request to AVEVA Marine.
Page 206
20.3.4 Design application processes Delete

When AVEVA Marine receives a Delete request, the element is deleted from AVEVA
Marine.
Page 207
CHAPTER 21 - View AVEVA ERM Data in Design
21 View AVEVA ERM Data in Design

Design in Context allows you to view live data from AVEVA Enterprise Resource
Management (AVEVA ERM) directly from within AVEVA Marine based on the element
selected in the application. It also allows you to view live data as Pseudo Attributes.
Note: You can also view the data for objects that have been created in AVEVA
Engineering, and then published to AVEVA ERM and also imported to AVEVA Marine using
the Compare/Update feature. For such objects, Design in Context uses the object's
reference Id, as known in AVEVA Engineering, to synchronise and display the data in
AVEVA Marine.
21.1 Overview
To view the live data from AVEVA ERM in Design, you must configure ERM settings by
clicking Display > AVEVA ERM Integration and then select the Settings option. Refer to
Dashboard Server in Design in Context help guide for further information.
All the other commands are available on the Display tab.
Associated Information window can be accessed by clicking Browse.
Settings for Click to display the Configuration dialog box. Refer to

Associated Configure in Design in Context help guide for further
Documents information.
Browse Click to display the Associated Documents window. Refer to

Associated Associated Information in Design in Context help guide for
Information further information.
Page 208
21.2 Only ERM configured

The Associated Information window is available in Design in Context only if AVEVA ERM is
set up correctly in AVEVA Integration Service and the AVEVA NET Server URL is not
configured. Refer “Set up Integration service configuration for AVEVA Marine” help guide
for more information.
To view the live data from AVEVA ERM, click the information view icon on the Associated
Information window. The data from AVEVA ERM categorised into Material Information
and Planning Information is displayed.
The data shown here is fetched live from AVEVA ERM. If the connection is down for some
reason, then nothing is displayed.
The data displayed on the Associated Information window, such as Material Information,
Planning Information, can be configured through the DataImportConfiguration file, that is
available at the installation location of the product. A sample location is D:\AVEVA
\Marine\OH12.1.SP5\ERMIntegration\DataImportConfiguration
\DataImportMappings.xml
21.3 Both AVEVA NET and ERM configured

For configuring AVEVA NET Server URL and to know more follow Design in Context help
guide.
Page 209
The Associated Information window appears as follows:
21.4 View Live Data as Pseudo Attributes

The data shown in the Design in Context widget will also be available as pseudo attributes
to the Design applications so that the data can be read and displayed in the Attributes
window in the 3D applications, Engineering lists and in reports created by the systems.
A set of pseudo attributes that will connect through AVEVA Integration Service to display
the mentioned information when displaying attribute data on selected/displayed objects.
The connection to AVEVA ERM will be done once for each object and retrieve all relevant
attribute information at the same time.
Page 210
DB views are created in AVEVA ERM, through the existing the data extraction
functionality. These views can then be accessed through AVEVA Integration Service, using
the integration service to facilitate direct lookup of data between Design/Catalogue and
ERM.
Page 211
Data shared from AVEVA ERM varies depending on the elements queried. The following
types of information are available:
· Planning information
o Work package id
o Scheduled start
o Scheduled Finish
o Actual Start
o Actual Finish
o Resource Work hours (budget)
o Work package status
· Material information
o Requisition id
o Requisition status
o Purchase order id
o Purchase order status
o Received status
o Delivery deadline
o Supplier
AVEVA ERM Information is available as pseudo attributes in the design application.
In the above image, the AVEVA ERM Planning information is displayed on Assembly object
type as pseudo attributes.
Page 212
Print Template A - v2.0

AVEVA ERM-Design Integration User Guide For AVEVA Marine

Uploaded by

Copyright:

Available Formats

You might also like

AVEVA ERM-Design Integration User Guide For AVEVA Marine

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

AVEVA ERM-Design Integration User Guide For AVEVA Marine

Uploaded by

Copyright:

Available Formats

AVEVA ERM-Design Integration

User Guide for AVEVA Marine

6.1.7 Set Up Work Package to Assembly Mapping in AVEVA Marine - Hull

20.2.3 Design application processes

1.1 About This Document

The guide contains information about the following:

§ Hull plate and profile part list integration

1.3 Summary of Chapters

1.4 Product Training Information

1.5 Technical Support

2.1 Overview of AVEVA ERM-Design Integration

Hull Design module

2.2 Integration Supported

2.3 Notification Workflow Overview

Currently, the following scenarios are possible:

· AVEVA ERM to AVEVA Marine

2.4 Integration Concepts

2.4.1 Notification Filtering

2.4.2 Design Project Id

2.4.3 Sent To Application

2.4.4 External Reference Id

Step 3: AVEVA Marine generates an ‘Acknowledgement’ or ‘Error’ notification. Both

Step 4: AVEVA ERM automatically processes the ‘Acknowledgement’ or ‘Error’

3 AVEVA ERM-Design Integration Capabilities

3.1 Handling Multiple Projects

3.3 Partial Import in AVEVA ERM

During a partial import, AVEVA ERM creates two notifications:

3.4 Update/Rework Information on Part Lists

Acknowledgement or Error notifications are generated according to the results of the

5 About Settings Dialog Box

Import & Material Mappings Settings

Import from AVEVA Catalogue Manager

To configure the locations:

Work Package To Assembly Mapping

Integration Service Settings

Notification Service Settings

Port Port number to which the Service must connect to.

6 Configuring Design Application and AVEVA ERM for

For AVEVA Marine:

For AVEVA ERM:

6.1 Configuring Design Application for AVEVA ERM-Design

6.1.1 Set Up Project for AVEVA ERM-Design Integration

6.1.2 Set Up Admin Module

To set the access of Properties database to read/write:

5. For the Properties list, select the Read/Write option.

To create a dictionary database:

3. Modify the database as required.

5. Select the MDB, and then click Modify.

6.1.3 Set Up Lexicon Module

Notes About DB views and PML functions

To set up Lexicon for AVEVA ERM-Design Integration:

6.1.4 Install and Set Up AVEVA Integration Service

6.1.5 Configure Design Application for AVEVA Integration Service

To configure AVEVA Integration Service for AVEVA ERM-Design Integration:

6.1.6 Set Up AVEVA Marine - Hull Design to Material Handling mode

6.2 Configuring AVEVA ERM for AVEVA ERM-Design Integration

6.2.1 Configure Integration

To configure AVEVA ERM-Design Integration in AVEVA ERM: