Integrating Assembly Planning and AVEVA ERM Planning

This section describes the concepts and procedure for assembly planning in AVEVA Marine using AVEVA ERM Planning.

Concept Description

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), or 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 is 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.

Transfer AVEVA ERM Work Packages to Design Application

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 are created from work packages in AVEVA Marine based on assembly mapping settings and an Acknowledgement or Error message is sent back according to the import result.

The following diagram illustrates the functional workflow of how the work packages in AVEVA Planning are transferred to Assembly Planning.

Information Transferred

The following fields are transferred from AVEVA ERM:

. ASSY_REF

. DISCIPLINE

. WP_NAME

. WP_REF

. DESCRIPTION

. PROJECT_ID

Integration Workflow – Data Transfer from AVEVA ERM

The integration workflow for transferring work packages from AVEVA ERM to AVEVA Marine is as follows:

.

.

.

.

.

Create a work package in AVEVA ERM

To create a work package in AVEVA ERM:

Open Screen s11001 Project Gantt View and select the required project.

Click Load. The Project Gantt View screen is displayed.

Click New.

On the s11001 Planning tab, click Change Type, and then select Production.

Select the Publish to Assembly Planning check box and set the Assembly Type.

Publish work package from AVEVA ERM

To publish the work package from AVEVA ERM:

Open screen s11001 Project Gantt View and select Data Management.

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.

When the work package is published, an Update message is created and sent to the Notification Service.

Import work packages in Design Application

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 Design Application

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

Process Acknowledgement or Error message in AVEVA ERM

After the data 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.

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.

Transfer Outfitting Assembly Part List to AVEVA ERM

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.

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.

The following diagram illustrates how outfitting part lists are transferred and work orders are generated.

Information Transferred

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".

The following columns are transferred from AVEVA Marine to AVEVA ERM:

. OwningParentDesignObject (Assembly name)

. DesignObjectType (ActualType element in AVEVA Marine, for example PIPE,

FLAN, VALV etc.)

. DesignUniqueID (Dabacon Reference)

. SchematicUniqueId (Name, or Dabacon Id for linked schematic element)

. DesignProjectID

. DrawingQuantity (Quantity w/o excess)

. ApprovedQuantity (Quantity w/excess)

. Unit

. Material Category (S, P, F)

. MaterialId (:MaterialId of catref if available, otherwise object name)

. Revision (Currently 1)

. TechnicalStatus (Currently set to Published)

. Model Tag ID (defined element name )

. System (value of the System attribute of the element, if present. Else, collected

from the OWNER element)

Note: The UDA :ERM_SYSTEM must be set manually before transferring the information.

Integration Workflow - Data Transfer to AVEVA ERM

The integration workflow for transferring the OutfittingAssembly PartList information from AVEVA Marine to AVEVA ERM is as follows:

.

.

.

.

.

.

.

Configure a filter in Design Application

The Settings dialog box in AVEVA Marine contains the settings to configure the integration of outfitting assembly 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.

Update the status for the PartList to Identified

AVEVA Marine 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.

Publish components to AVEVA ERM

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 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.

Import data into AVEVA ERM

After the components are published by AVEVA Marine, the components are available for 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:

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.

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 ‘Update’ notification, using the s22050 Data Import screen. For more information, see .

The information about errors, if any, is displayed in the Audit Summary and Audit Detail 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.

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

Verify data in AVEVA ERM

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.

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.

Provide feedback on data consumption in AVEVA ERM

After the import is done, AVEVA ERM sends feedback on data consumption to AVEVA 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 Design Application

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.

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.

The following points must be noted while publishing assemblies:

. You can publish an assembly from any level.

. When you publish an assembly, all the parent assemblies up to the root assembly

are published. Further, all the parts of the assembly, including any child assemblies are also published. However, if the child assembly further contains another sub assembly, the sub assembly is not published.

When you publish an assembly, you must make sure that the publishing statuses of all parent assemblies up to the root assembly is Approved to avoid errors during the import process.

. After the import is successful, the information about the assemblies and their

parts is available in the s20017 Fabricate Catalogue, s21015 Fabricate Part List

and s21000 Part List screens in AVEVA ERM.

. After importing the assemblies and their parts, AVEVA ERM rearranges the

hierarchy of assemblies in the s20017 Fabricate Catalogue and s21015 Fabricate Part List screens.

Information Transferred

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 (Dabacon Reference)

. DrawingQuantity (Quantity w/excess)

. ApprovedQuantity (Quantity w/excess)

. TechnicalStatus (Currently set to Published)

. Revision

. Unit

. NestingId (New column in ERM)

. Root fabricate (True or False)

. Model Tag ID (defined element name )

. System (value of the System attribute of the element, if present. Else, collected

from the OWNER element)

Note: The UDA :ERM_SYSTEM must be set manually before transferring the information.

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.

Integration Workflow – Data Transfer to AVEVA ERM

The integration workflow for hull plate and profile part lists from AVEVA Marine to AVEVA ERM is as follows:

.

.

.

.

.

.

.

.

Configure a filter for hull plate and profile part lists in Design Application

The Settings dialog box in AVEVA Marine contains the settings to configure the integration of hull plate and profile 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.

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

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.

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 ERM before transferring steel plates and profiles part list to AVEVA ERM.

Import steel parts 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 hull plate and profile part lists in AVEVA ERM:

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.

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.

Verify data in AVEVA ERM

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.

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.

Provide feedback on data consumption in AVEVA ERM

After the import is done, AVEVA ERM sends feedback on data consumption to AVEVA 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.

Process feedback in AVEVA Marine

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.

Removing a Part from an Already Published Hull Assembly

After transferring a hull assembly to AVEVA ERM, a part from it can be removed only after receiving an Acknowledgment notification from AVEVA ERM.

To remove a part from the hull assembly:

Open Assembly Planning in AVEVA Marine.

Select the assembly for which you want to remove a part.

Do one of the following:

. If the assembly is not yet transferred to AVEVA ERM, select the part you

want to remove, right-click and select Remove. The part is removed from the assembly. For more information, see the documentation of AVEVA Marine.

. If the assembly is already transferred to AVEVA ERM, go to Step 4 and

complete the remaining procedure.

Note: If the assembly is already published to AVEVA ERM, the publishing status for the assembly is 100 or 110.

Select the part you want to remove, right-click and select Remove. The message Are you sure you want to remove the selected part from its parent assembly? is displayed.

Click Yes. The message Remove Notification is displayed.

Click OK. An Update notification is sent to AVEVA ERM.

Note: At the same time, the hull assembly is saved automatically in AVEVA Marine.

In AVEVA ERM, when the Update notification is processed for the FabricatePartListDelete ID, the part is removed from the assembly in the s21015 Fabricate Part Lists screen. If the part is removed successfully, an Acknowledgment notification is sent to AVEVA Marine. Else, an Error notification is sent.

Note: After removing the part, if the hull assembly does not contain any other parts, both the part and its owner are removed from the screen in AVEVA ERM.

In AVEVA Marine, on the Notifications dialog box, process the Acknowledgment or Error notification.

. In the case of an Acknowledgment notification, click Delete. The part is

removed from the assembly.

. In the case of Error notification, the part is not removed.

Deletion

This section describes the integration process for delete operations standard materials, raw plates, raw profiles and project components.

Concept Description

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.

. The 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.

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.

Delete Workflow (Initiated in Design Application)

This following workflow is followed when the delete operation is initiated in AVEVA Marine:

.

.

.

.

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

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).

Design application processes CanDeleteAcknowledgement/CanDeleteError

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

Note: If AVEVA ERM sends a CanDeleteError notification, the delete workflow cannot proceed.

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.

Delete Workflow (Initiated in AVEVA ERM)

This following workflow is followed when the delete operation is initiated in AVEVA ERM:

.

.

.

.

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.

Design application processes CanDeleteRequest

When AVEVA Marine receives a CanDeleteRequest, the user must verify 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.

AVEVA ERM processes CanDeleteAcknowledgement/CanDeleteError

After receiving a CanDeleteAcknowledgement notification, AVEVA ERM deletes the element and sends a Delete request to AVEVA Marine.

Design application processes Delete

When AVEVA Marine receives a Delete request, the element is deleted from AVEVA Marine.

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.

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 Associated Documents

Click to display the Configuration dialog box. Refer to Configure in Design in Context help guide for further information.

Browse Associated

Information

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

When Only AVEVA ERM is 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\DataI mportMappings.xml

When Both AVEVA NET and AVEVA ERM are Configured

For configuring AVEVA NET Server URL and to know more follow Design in Context help guide.

The Associated Information window appears as follows:

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.

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.

Data shared from AVEVA ERM varies depending on the elements queried. The following types of information are available:

. Planning information

Work package id

Scheduled start

Scheduled Finish

Actual Start

Actual Finish

Resource Work hours (budget)

Work package status

. Material information

Requisition id

Requisition status

Purchase order id

Purchase order status

Received status

Delivery deadline

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.

AVEVA Group pie High Cross Madingley Road Cambridge

CB3 OHB

UK