COMOS Material Management. Operation COMOS. Process COMOS Material Management Operation. Trademarks. Introduction. Definitions

Similar documents
COMOS Material Management. Operation COMOS. Process COMOS Material Management Operation. Trademarks 1. Introduction. Definitions 3

COMOS. Lifecycle Material Management. General information 1. Introduction 2. Definitions 3. Creating material in COMOS 4

COMOS. Lifecycle 3D Integration Operation. COMOS PDMS Integration 1. Material management 2. COMOS 3D viewing 3. References 4.

COMOS. Lifecycle 3D Integration Operation. COMOS PDMS Integration 1. Material management 2. COMOS 3D viewing 3. References 4.

COMOS. Lifecycle 3D Integration Operation. Publisher 1. COMOS PDMS Integration 2. Material management 3. COMOS 3D viewing 4.

Creating the program. TIA Portal. SIMATIC Creating the program. Loading the block library 1. Deleting program block Main [OB1]

Class documentation. COMOSKDictionary COMOS. Platform Class documentation COMOSKDictionary. Trademarks. General. KDictionary. Programming Manual

DANGER indicates that death or severe personal injury will result if proper precautions are not taken.

Siemens Spares COMOS. Operations Inspection. Introduction 1. Working with the "Inspection" plugin 2. Working with the "Inspection diagram" plugin 3

Team engineering via Inter Project. Engineering. TIA Portal. Team engineering via Inter Project Engineering. Basics of "Inter Project Engineering"

Readme SiVArc V14 SP1 Update 6

COMOS. Operations MRO. Introduction 1. Maintenance objects 2. "General maintenance" plugins 3. "Events" plugin 4. "Resources" plugin 5

COMOS. Operations Inspection. Introduction 1. Working with the "Inspection" plugin 2. Working with the "Inspection diagram" plugin 3

Siemens Controls. SAP interface COMOS. Platform SAP interface. Trademarks 1. Introduction. Technical prerequisites 3

COMOS. Automation COMOS Automation Interfaces SPI 1. Generic Excel import 2. Process visualization via OPC client 3.

COMOS. Operations MRO (Maintenance Repair and Overhaul) Introduction 1. Maintenance objects 2. "General maintenance" plugins 3.

COMOS. Platform Class documentation RevisionMaster_dll. Class: RevisionInfo 1. Class: RevisionMaster 2. Programming Manual

COMOS. Operations Shutdown. Introduction 1. Milestones 2. "Shutdown management" plugin 3. "Quick edit" plugin 4. User interface reference 5

Portable & Direct COMOS. Operations Portable & Direct. Trademarks 1. Introduction. Portable 3. "Direct" plugin 4. User interface reference

party software COMOS Platform Third-party software Trademarks 1 Requirements for the system environment Third-party software releases Operating Manual

COMOS. Automation Automation interfaces. Note on file-based data exchange 1 SPI 2. Generic Excel import 3. Process visualization via OPC client 4

MindSphere. Visual Explorer. Introduction. User roles for "Visual Explorer" Connecting "Visual Explorer" to MindSphere data. Creating Visualizations

SIMATIC. STEP 7 PLUS TIA Portal Teamcenter Gateway. Introduction to TIA Portal Teamcenter Gateway 1. System requirements 2

3D Integration Administration COMOS. Process 3D Integration Administration. Trademarks 1. Plant Modeler. COMOS PDMS Integration 3. COMOS 3D viewing 4

COMOS. Automation Logical. Basic principles 1. Configuring function diagrams based on IEC 2. Code generation based on IEC

MRO (Maintenance Repair and. Overhaul) COMOS. Operations MRO (Maintenance Repair and Overhaul) Trademarks 1. Introduction. Maintenance objects 3

DANGER indicates that death or severe personal injury will result if proper precautions are not taken.

COMOS. Operations PQM. Introduction 1. Import 2. Attributed search 3. Check out and check in function 4. Transmittals 5. DVM document package 6

Basic principles 1. Configuring function diagrams based on IEC 2. Administration 3 COMOS. Automation Logical. Operating Manual 04/2015 A5E AD

Class: DocumentManager 1 COMOS. Platform Class documentation DocumentManager_dll. Programming Manual 03/2017 V10.2.

DANGER indicates that death or severe personal injury will result if proper precautions are not taken.

MindSphere. MindConnect IoT Extension Getting Started. Introduction to MindSphere. Prerequisites 2. Preparations 3. MindConnect IoT Extension

COMOS. Lifecycle Project Quality Management. Introduction 1. Import 2. Attributed search 3. Check out and check in function 4. DVM document package 5

DANGER indicates that death or severe personal injury will result if proper precautions are not taken.

3D Integration Administration COMOS. Process 3D Integration Administration. Trademarks 1. Plant Modeler. COMOS PDMS Integration 3. COMOS 3D viewing 4

Class: POptions 1 COMOS. Platform Class documentation POptions_dll. Programming Manual 04/2014 A5E AA

Key Panels Library SIMATIC HMI. Key Panels Library. Preface 1. Installation of Key Panels Library. Working with the Key Panels Library

Logical COMOS. Automation Logical. Trademarks 1. Basic principles. Configuring function diagrams based on IEC

SIMATIC. Process Control System PCS 7 PCS 7 system documentation - Readme V8.0 SP2 (Update 1) Options for Accessing Documentation 1

SIMATIC. Process Control System PCS 7 Advanced Process Functions Operator Manual. Preface. Security information 1. Overview 2. Material management 3

PD PA AP How To Configure Maxum II TimeServer Access

SIMATIC. S7/HMI SIMATIC Automation Tool V3.1 SP1 product information. SIMATIC Automation Tool features 1. Known problems. Product Information

SIMATIC. SIMATIC Logon V User management and electronic signatures 1. Hardware and Software Requirements 2. Scope of delivery 3.

S7-300 Getting Started - Commissioning a CPU 31xC: Closed-loop control

Performance data abgn SCALANCE W770/W730 SIMATIC NET. Industrial Wireless LAN Performance data abgn SCALANCE W770/W730.

Getting Started - Startdrive. Startdrive SINAMICS. Introduction 1. Connecting the drive unit to the PC. Creating a project 3

COMOS. Process P&ID Administration. Unit structures 1. Configuring pipes 2. Configuring P&IDs 3. Configuring components 4

RF-MANAGER simulator SIMATIC. RFID-Systems RF-MANAGER simulator. Simulating projects. Compact Operating Instructions 06/2010 A5E

Performance data abgn PCIe Minicard MPCIE-R1-ABGN-U3 SIMATIC NET

Validity 1. Improvements in STEP 7 2. Improvements in WinCC 3 SIMATIC. Readme. Readme

COMOS. Process P&ID Operation. Third-party software 1. Preparations 2. Overview of the P&ID solution 3. Using components 4.

COMOS. Process P&ID Operation. Third-party software 1. Overview of the P&ID module 2. Preparations 3. Overview of P&ID objects 4.

MindSphere. Fleet Manager. Introduction to "Fleet Manager" 1. User interface for "Fleet Manager" 2. User rights in "Fleet Manager" 3.

SIMOTION. Motion Control Task Trace. Preface 1. Overview 2. Configuring 3. Working with the SIMOTION Task Profiler 4.

Operator Station (V8.0) SIMATIC. Process Control System PCS 7 Operator Station (V8.0) Preface 1. The PCS 7 Operator Station

MindSphere. Fleet Manager. Introduction to "Fleet Manager" 1. User interface for "Fleet Manager" 2. User rights in "Fleet Manager" 3

Class:ELOLib 1 COMOS. Platform Class documentation ELOLib_dll. Programming Manual. Siemens Distributor 09/2014 A5E AA

SIMATIC. Process Control System PCS 7 OS Process Control (V8.1) Preface 1. Additional documentation 2. Functions of the PCS 7 OS in process mode 3

General Information 1. Connection 2. User Interface 3 ATC5300. Menus 4. Automatic Transfer Controller. Remote Control Software Manual A5E

SIMATIC. PCS 7 Process Control System SIMATIC Logon Readme V1.6 (Online) Security information 1. Overview 2. Notes on installation 3.

Deckblatt. APL Operator Guide SIMATIC PCS 7. Application description June Applikationen & Tools. Answers for industry.

Workflow COMOS. Platform Workflow. Trademarks 1. Overview. Starting example 3. Base data of the workflow 4. Revisions in the workflow

Continuous Function Chart Getting. Started SIMATIC. Process Control System PCS 7 Continuous Function Chart Getting Started.

SIMATIC. Process Control System PCS 7 VT Readme V8.2 (online) Security information 1. Overview 2. Notes on Installation 3. Notes on usage 4.

SITOP UPS1600 under STEP 7 V13. SITOP UPS1600 under STEP 7 V13. Introduction. Safety notes. Description. Assigning the IP address

SFC Visualization (V8.0 SP1) SIMATIC. Process Control System PCS 7 SFC Visualization (V8.0 SP1) What's new in SFV? 1. SFC Visualization (SFV)

SIMATIC. Process Control System PCS 7 Trend Micro OfficeScan (V8.0; V8.0 SP1) Configuration. Using virus scanners 1.

Web Option for OS (V8.0) SIMATIC. Process Control System PCS 7 Web Option for OS (V8.0) Preface 1. Additional documentation

Interfaces COMOS. Platform Interfaces. Trademarks 1. XML connectors. Standard import: Blank for XML

SIMATIC HMI. WinCC V7.4 WinCC/Options for Process Control. Overview of process control system options 1. OS Project Editor 2.

SIMATIC Ident RFID systems MDS D423 Compact Operating Instructions

SIMATIC. Process control system PCS 7 Operator Station (V9.0 SP1) Security information 1. Preface 2

COMOS. Platform COMOS Enterprise Server. Task of the COMOS Enterprise Server 1. Service-oriented architecture 2

SIMATIC. Process Control System PCS 7 OS Process Control (V8.1) Security information 1. Preface 2. Additional documentation 3

SIMATIC. Process Control System PCS 7 Configuration McAfee Endpoint Security Security information 1. Preface 2.

SIMATIC/SINAMICS. Getting started with SINAMICS V90 PN on S Motion Control. Fundamental safety instructions 1. Introduction

Siemens Automation Products

SIMATIC IPC Wizard for. Widescreen devices with multitouch SIMATIC. Industrial PC SIMATIC IPC Wizard for. Preface.

Inheriting, Copying, Deleting COMOS. Platform Inheriting, Copying, Deleting. Trademarks 1. Inheritance. Copying: General Definitions 3

SIMATIC. Process Control System PCS 7 Symantec Endpoint Protection 11.0 Configuration. Using virus scanners 1. Configuration 2. Commissioning Manual

Maintenance COMOS. Platform Maintenance. Trademarks 1. Information on version change. Switching the licensing technique

Process Historian Administration SIMATIC. Process Historian V8.0 Update 1 Process Historian Administration. Basics 1. Hardware configuration 2

Developer Cockpit. Introduction 1. Prerequisites 2. Application Lifecycle in MindSphere 3. User interfaces "Developer Cockpit" 4

Setting up securityglobal FW Rulesets SIMATIC NET. Industrial Ethernet Security Setting up security. Preface. Firewall in standard mode

DI 8x24VDC ST digital input module SIMATIC. ET 200SP DI 8x24VDC ST digital input module (6ES7131-6BF00-0BA0) Preface. Documentation guide

SITOP UPS1600 under STEP 7 V5. SITOP UPS1600 under STEP 7 V5. Introduction. Safety notes. Description 3. Assigning the IP address

SIMATIC. PCS 7 Licenses and configuration limits (V9.0) Security information 1. Preface 2. Selecting the correct license keys 3

SIMATIC HMI. WinCC V7.4 SP1 SIMATIC HMI WinCC V7.4 Getting Started. Welcome 1. Icons 2. Creating a project. Configure communication

Plant Automation Accelerator 2.0

SIMATIC. Process Control System PCS 7 CFC Readme V9.0 (online) Security information 1. Overview 2. Notes on Installation 3. Notes on usage 4.

COMOS. Lifecycle COMOS Walkinside Getting Started. Security information 1. Which functionalities are not covered in this manual? 2

PROFIsafe SITRANS. Pressure transmitter SITRANS P, DS III PROFIsafe series. Product Information 7MF4*34 04/2008 A5E

SIMATIC. Process Control System PCS 7 Licenses and quantity structures (V8.0) Preface 1. Selecting the correct license keys 2

SIMATIC. WinCC Readme Runtime Professional. Validity 1. Improvements in Update 6 2. Improvements in Update 3 3. Improvements in Update 2 4

SIMATIC HMI. WinCC V7.0 SP1 Setting up a Message System. WinCC Alarm Logging 1. Message System in WinCC 2. Principles of the Message System

Settings. Prior information notice 1. Introduction to "Settings" 2. User rights in "Settings" 3. Settings interface 4.

SIMATIC. Communications processor CP First Steps in Commissioning. Getting Started 09/2008 A5E

SIMATIC. Working with STEP 7. Introduction to STEP 1. The SIMATIC Manager 2. Programming with Symbols. Creating a Program in 4

Optional package printer driver V1.4

COMOS What's new? COMOS. COMOS What's new? COMOS idb 1. Help folder for the cdb and idb databases 2. Using the COMOS help 3

Transcription:

COMOS Material Management Operation COMOS Process COMOS Material Management Operation Operating Manual Trademarks 1 Introduction 2 Definitions 3 Creating material in COMOS 4 Importing material from external sources 5 Material documentation and order requests 6 References 7 08/2011 A5E03640142-01

Legal information Legal information Warning notice system This manual contains notices you have to observe in order to ensure your personal safety, as well as to prevent damage to property. The notices referring to your personal safety are highlighted in the manual by a safety alert symbol, notices referring only to property damage have no safety alert symbol. These notices shown below are graded according to the degree of danger. DANGER indicates that death or severe personal injury will result if proper precautions are not taken. WARNING indicates that death or severe personal injury may result if proper precautions are not taken. CAUTION with a safety alert symbol, indicates that minor personal injury can result if proper precautions are not taken. CAUTION without a safety alert symbol, indicates that property damage can result if proper precautions are not taken. NOTICE indicates that an unintended result or situation can occur if the relevant information is not taken into account. If more than one degree of danger is present, the warning notice representing the highest degree of danger will be used. A notice warning of injury to persons with a safety alert symbol may also include a warning relating to property damage. Qualified Personnel The product/system described in this documentation may be operated only by personnel qualified for the specific task in accordance with the relevant documentation, in particular its warning notices and safety instructions. Qualified personnel are those who, based on their training and experience, are capable of identifying risks and avoiding potential hazards when working with these products/systems. Proper use of Siemens products Note the following: WARNING Siemens products may only be used for the applications described in the catalog and in the relevant technical documentation. If products and components from other manufacturers are used, these must be recommended or approved by Siemens. Proper transport, storage, installation, assembly, commissioning, operation and maintenance are required to ensure that the products operate safely and without any problems. The permissible ambient conditions must be complied with. The information in the relevant documentation must be observed. Trademarks All names identified by are registered trademarks of Siemens AG. The remaining trademarks in this publication may be trademarks whose use by third parties for their own purposes could violate the rights of the owner. Disclaimer of Liability We have reviewed the contents of this publication to ensure consistency with the hardware and software described. Since variance cannot be precluded entirely, we cannot guarantee full consistency. However, the information in this publication is reviewed regularly and any necessary corrections are included in subsequent editions. Siemens AG Industry Sector Postfach 48 48 90026 NÜRNBERG GERMANY A5E03640142-01 P 09/2011 Copyright Siemens AG 2011. Technical data subject to change

Table of contents 1 Trademarks... 5 2 Introduction... 7 3 Definitions... 9 4 Creating material in COMOS... 11 4.1 Creating material from P&ID reports...11 4.1.1 Detailing the material...11 4.1.2 Assigning further components...12 4.2 Creating material from isometries...13 5 Importing material from external sources... 15 5.1 CSV import...15 5.1.1 Introduction...15 5.1.2 Importing CSV files...15 5.2 Importing from AVEVA PDMS...16 5.2.1 Basic principles...16 5.2.2 Operating mode...17 5.2.2.1 Overview...17 5.2.2.2 Online mode...17 5.2.2.3 Offline mode...18 5.2.2.4 Batch mode...18 5.2.3 Starting the operation in AVEVA PDMS...19 5.2.4 Importing to COMOS in offline mode...20 5.2.5 Locking status changes in AVEVA PDMS...20 6 Material documentation and order requests... 23 6.1 Creating MTO documents...23 6.2 Creating MPR documents...25 7 References... 27 7.1 exportmto file...27 7.2 User interface reference...29 7.2.1 "MTO documents" tab...29 7.2.2 "MPR documents" tab...31 Operating Manual, 08/2011, A5E03640142-01 3

Table of contents 4 Operating Manual, 08/2011, A5E03640142-01

Trademarks 1 Trademarks Registered trademark: COMOS Operating Manual, 08/2011, A5E03640142-01 5

Trademarks 6 Operating Manual, 08/2011, A5E03640142-01

Introduction 2 COMOS features a Material Management Assistant, which you can use to create revisionbased material documentation and order requests. You can create the quantity-related and type-related data for the Material Management Assistant in COMOS. This data is also called MTO (Material Take Off) data. You can also take MTO-related data from the following COMOS sources: P&ID reports Isometries You can also take MTO-related data from the following external sources: AVEVA PDMS (XML) Other third-party software (CSV) Operating Manual, 08/2011, A5E03640142-01 7

Introduction 8 Operating Manual, 08/2011, A5E03640142-01

Definitions 3 Document key A document key identifies a specific MTO document package or an MPR document package and is permitted to occur only once per package. Filters Various filters may be set up for individual MTO documents of an MTO document package. This allows individual MTO documents to contain different information. MPR documents MPR (Material Purchase Request) documents contain data that is shown in the form of order requests. MTO document MTO (Material Take Off) documents contain quantity-related and type-related data which is used here as a basis for order requests, for example. Depending on the objective, a distinction is made between the following MTO types: Estimated: Estimated material that is created from one or more P&ID reports, that is created manually or that is created by means of a CSV import. Current: Material that is produced during planning. Material created from isometries, by an import from AVEVA PDMS or by a CSV import. Released: Released material. Material created after an isometry has been released, by an import from PDMS or by a CSV import. MTO document package When you are working with the Material Management Assistant, various documents are created at the same time. These documents are bundled into an MTO document package. Operating Manual, 08/2011, A5E03640142-01 9

Definitions 10 Operating Manual, 08/2011, A5E03640142-01

Creating material in COMOS 4 4.1 Creating material from P&ID reports You can take material specifications from one or more piping diagrams. Once extracted, you can then add further specifications for the material. Procedure To create material from a P&ID report, proceed as follows: 1. Call the "Plugins > Basic > Material Management Assistant" menu command. 2. Select the "Estimated" tab. 3. Drag&drop the desired object from the Navigator into the "P&ID-Document/Query/Root" field of the "Estimated" tab. 4. To show material that is already available, click on the "Refresh" button. 5. To collect unavailable material or to update available material, click on the "Collect" button. The result is shown in the form of a list. Result The material is collected and stored in the Navigator in folders under the respective pipe. In addition the result in shown in a list in the Material Management Assistant. The pipes are color-coded in the list to indicate whether pipe spec mapping has been carried out for the associated components. Color Red Orange Green White Description Pipe spec mapping has not been carried out for any of the components. Pipe spec mapping has been carried out for some of the components. Pipe spec mapping has been carried out for all of the components. There is no material associated with the pipe. 4.1.1 Detailing the material If you want to provide more detailed specifications for the material, you need to assign pipe spec components to the MTO objects. Operating Manual, 08/2011, A5E03640142-01 11

Creating material in COMOS 4.1 Creating material from P&ID reports Prerequisite You have already extracted information about material from one or more P&ID reports. See also section Creating material from P&ID reports (Page 11). Procedure To add to the desired information, proceed as follows: 1. On the "Estimated" tab, click on the name of a pipe in the list. A menu opens with the entries "Show details for Pipe" and "Navigate". 2. Click on the entry "Show details for Pipe". The "PID Estimation" window opens. The "PID Estimation" window can alternatively be called up by selecting a unit or a pipe in the Navigator, and clicking on the "MTO > Detail Pipe" command in the context menu. 3. In order to show all available pipe spec parts, click on the "Refresh" button. The available pipe spec parts are shown for the material that was selected from the P&ID reports. 4. In the "Shared-Quantity" column, enter the quantity of the components that you wish to assign per pipe. 5. In order to create associated objects under the pipes, click on the "Apply Quantities" button. 6. Close the window with the "Close" button. Result Quantity-specific and pipe spec-specific components are assigned to MTO objects. If no MTO object exists, a new one is created. 4.1.2 Assigning further components On the "PID Estimation" tab you can only assign objects that are present on the piping and instrumentation diagram/piping and instrumentation diagrams. See also section Detailing the material (Page 11). If you wish to assign an object which is not present on the respective piping and instrumentation diagram, use the "Manual Estimation" tab. Procedure 1. Open the "Manual Estimation" tab. All pipe spec components suitable for the respective pipe are displayed as a list. 2. In the edit field under each pipe spec component, enter the desired quantity for each of those components. 12 Operating Manual, 08/2011, A5E03640142-01

Creating material in COMOS 4.2 Creating material from isometries 3. If you cannot find the pipe component that you are looking for in the list, click on the "Add" button to add it. 4. In order to create associated objects under the respective pipe, click on the "Apply Quantities" button. 4.2 Creating material from isometries Prerequisite The configuration object has been configured by an administrator to allow materials to be created. You can find additional information on this topic in the "COMOS Material Management Administration" manual, keyword "Configuring an import from isometrics". Pipe spec mapping has been carried out for all relevant objects. Procedure 1. Select the object in the navigator whose subobjects are to be used to create the material. 2. Select the "MTO > Collect Material" command from the context menu. Result The current isometry object is used as the starting point for identifying the next highest collection folder. The base object required for this purpose can be set in the configuration object. The "Current" and "Released" folders are created here and this is where the MTO objects are stored. Separate MTO objects are created for the planned material underneath the selected objects based on the settings in the configuration object. These objects are then sorted into the "Current" or "Released" folder, depending on where they belong. You can find additional information on this topic in the "COMOS Material Management Administration" manual, keyword ""COMOS MTO" tab". Operating Manual, 08/2011, A5E03640142-01 13

Creating material in COMOS 4.2 Creating material from isometries 14 Operating Manual, 08/2011, A5E03640142-01

Importing material from external sources 5 5.1 CSV import 5.1.1 Introduction CSV files are used to import material from external sources. Workflow 1. Importing a CSV file See also section Importing CSV files (Page 15). 2. Creating an MTO document See also section Creating MTO documents (Page 23). 3. Creating an MPR document See also section Creating MPR documents (Page 25). 5.1.2 Importing CSV files Prerequisite The structure of the CSV file must conform to the COMOS rules. You can find additional information on this topic in the "COMOS Material Management Administration" manual, keyword "Structure of a CSV file". Operating Manual, 08/2011, A5E03640142-01 15

Importing material from external sources 5.2 Importing from AVEVA PDMS Procedure 1. Open the context menu for an object in the navigator and click on the "MTO > CSV import - owner by subsection" command. With this command, the owner of the MTO objects is identified on the basis of the information in the "Owner" column of the CSV file. Alternatively, open the context menu for an object in the navigator and click on the "MTO > CSV import - owner by selection" command. With this command, the owner of the MTO objects is the object from which you selected the command. The "Select directory" window opens. 2. Select the folder containing the CSV files that you wish to import. 3. Click "OK". Result All the CSV files within the selected directory are imported. "CSV import - owner by subsection" command: The material is created in the navigator in accordance with the configuration of the subsection specified in the CSV file. "CSV import - owner by selection" command: The material is created underneath the object that you used to select the command. The Logfile.xml file is created in the directory from which you imported. Among other things, this log file describes any errors that occurred during the import. 5.2 Importing from AVEVA PDMS 5.2.1 Basic principles Prerequisite To compile a selection set in AVEVA PDMS and transfer it to COMOS, install and activate the AVEVA PDMS interface. You can find additional information on this topic in the "3D Integration Operation" manual, keyword "Activating COMOS PDMS Integration for AVEVA PDMS". 16 Operating Manual, 08/2011, A5E03640142-01

Importing material from external sources 5.2 Importing from AVEVA PDMS Transferring MTO data from AVEVA PDMS to COMOS The MTO operation transfers material from AVEVA PDMS to COMOS. The starting point for the operation is AVEVA PDMS. For this purpose, AVEVA PDMS provides a form which can be used to generate the selection set. See also section Starting the operation in AVEVA PDMS (Page 19). For all objects in this selection set, material files are generated as a first step. These files are evaluated. The result of this evaluation is written to XML files. These XML files can then be read into COMOS. Selection options in AVEVA PDMS When creating the XML files, you can make an assignment in AVEVA PDMS to determine whether this concerns engineering material (current) or released material (released). The XML files are then stored in the corresponding folders and COMOS creates the MTO objects following this. 5.2.2 Operating mode 5.2.2.1 Overview MTO operations can be executed under various operating modes: If there is a connection between COMOS and AVEVA PDMS, the operation is executed in online mode. If there is no connection between COMOS and AVEVA PDMS, the operation is executed in offline mode. It is also possible to write the material to an XML file in batch mode, using a PML macro. 5.2.2.2 Online mode Principle In online mode, start COMOS either locally or via a Citrix server. AVEVA PDMS is running on the same machine. When the XML files have been generated, a command is sent to COMOS. COMOS then fetches the files from the specified directory and imports the MTOs into the COMOS DB. You have the option of viewing the exchange path in the project properties on the "PDMS interface/construction assistant" tab or setting it as an administrator. Transfer directories In online mode, both the material files and the XML files are saved in the exchange path and fetched from there by COMOS. This directory must be known to both systems. Operating Manual, 08/2011, A5E03640142-01 17

Importing material from external sources 5.2 Importing from AVEVA PDMS If, for instance, "pdmswk" is registered as the exchange path, the files are saved as follows: - Material files in the folder "pdmswk/material Files" - XML files for current (preliminary) material in the folder "pdmswk/currentmto" - XML files for released material in the folder "pdmswk/released" 5.2.2.3 Offline mode Principle In offline mode, there is no connection between COMOS and AVEVA PDMS. In AVEVA PDMS, the XML files are created at the push of a button and stored in a specified folder. This completes the operation in AVEVA PDMS. You can then import the XML files into COMOS at any time, using a command in the context menu. In this case the XML files are stored in directories which you define using environment variables in a configuration file. The directories must all point to the document path saved in COMOS. This configuration file with the fixed name "MTOExportSettings.dat" must be accessible to AVEVA PDMS. You can edit the ASCII file "MTOExportSettings.dat" using a text editor. You can find additional information on this topic in the "COMOS Material Management Administration" manual, keyword "MTOExportSettings.dat". 5.2.2.4 Batch mode Principle In batch mode the XML files are created in exactly the same way as in the configuration file. Expand the content of the MTOExportSettings.dat configuration file by adding the names of the pipes to be taken into account in the batch run: // export status of pipes / branches: set R for "released", set C for "current" // path to the material files // path to the current files // path to the released files // path to the temp after iso files // path to the subclass file and the name of it // The following code will be created automatically - do not modify it! // [!START!] The following objects will dealed: =8261/19717 =8261/19730 =8261/19753 The pipes are specified by your RefNo. Here you can also specify the RefNo of a ZONE or SITE. 18 Operating Manual, 08/2011, A5E03640142-01

Importing material from external sources 5.2 Importing from AVEVA PDMS Macro Calling the macro ITExportMTONightjob.pmlfnc creates the material files for the specified pipes. From these files an XML file is then created, which can be read into COMOS at a later point in time. Signature of the macro: define function!!itexportmtonightjob(!isisocall is BOOLEAN) Parameter: If the macro is called in Isodraft:!isIsoCall: True If the macro is not called in Isodraft: False exportmto file You have the option of creating exportmto files that offer access to specific material files that can, in turn, be used to create XML files for each material. See also section exportmto file (Page 27). In the "MTOExportSettings.dat" file, you need to specify the paths to the folders that contain the exportmto files. You can find additional information on this topic in the "COMOS Material Management Administration" manual, keyword "MTOExportSettings.dat". Transfer process: 1. Start of transfer in AVEVA PDMS 2. Preprocessing of the exportmto file The file is checked and is completed where necessary. If there are no material files available, these are created. 3. Processing An XML file is created for each material file. The corresponding MTO objects are created in COMOS. 5.2.3 Starting the operation in AVEVA PDMS The operation is started in AVEVA PDMS using a form that can be found in the PML library supplied. Procedure To start an operation in AVEVA PDMS, proceed as follows: 1. To call the form, click on the menu item "Comos > Interface > Export MTO". AVEVA PDMS checks whether or not a connection to COMOS can be established. The header line shows whether the operation is running in online mode or in offline mode. 2. To create the selection set, click on the "Add all for CE" button. All pipes in the "Design Explorer" under the current element marked are inserted into the "List of Elements". The name of the pipe is displayed in the "Object" column. The quality in which the material for this pipe is created is shown in the "Status" column. Operating Manual, 08/2011, A5E03640142-01 19

Importing material from external sources 5.2 Importing from AVEVA PDMS 3. To set the MTO type, mark the desired pipes in the "List of Elements" and click on the "Set status current" or "Set status released" button. These buttons may be locked if a configuration object has been created in AVEVA PDMS and certain functions have been called. See also section Locking status changes in AVEVA PDMS (Page 20). 4. Once you have created the standard table, you can then create the XML files. Click the "Export MTO" button to do this. This button is located in within the form. 5.2.4 Importing to COMOS in offline mode Procedure To read the XML data created by AVEVA PDMS into COMOS, proceed as follows: 1. On the "Units" tab of the Navigator in COMOS, right-click on any object. 2. In the context menu, click on the "MTO > Import > From PDMS" command. Result All XML files are read in from the folders "CurrentMTO" and "Released", and the MTO objects are created. To prevent the files from being read in again during the next import, after they have been processed they are moved into the subfolder "Imported". 5.2.5 Locking status changes in AVEVA PDMS Procedure 1. Create the!!itexportmtoconfiguration configuration object in AVEVA PDMS. This object is deleted when you exit AVEVA PDMS. 2. Enter one of the following functions in the command window:.setexportmtostatuscurrent() The status of the material is set to "current". The buttons "Set status to "current"" and "Set status to "released"" are locked..setexportmtostatusreleased() The status of the material is set to "released". The buttons "Set status to "current"" and "Set status to "released"" are locked. 20 Operating Manual, 08/2011, A5E03640142-01

Importing material from external sources 5.2 Importing from AVEVA PDMS Unlocking status changes Enter the function.setexportmtostatusboth() in the command window. The buttons "Set status to "current"" and "Set status to "released"" are unlocked. Operating Manual, 08/2011, A5E03640142-01 21

Importing material from external sources 5.2 Importing from AVEVA PDMS 22 Operating Manual, 08/2011, A5E03640142-01

Material documentation and order requests 6 6.1 Creating MTO documents You can create MTO documents in the following ways: Directly using the Material Management Assistant Via the context menu as an intermediate step Using the Material Management Assistant Creating MTO documents involves making a few settings in the Material Management Assistant. Procedure To create MTO documents, proceed as follows: 1. Call the "Plugins > Basic > Material Management Assistant" menu command. 2. Click the "MTO Documents" tab. 3. Make the required settings here: If you wish to create an MTO document package for the first time, activate the "new Package" option. If you wish to update an MTO document package, activate the "update Package" option. The "Created Document Key" field cannot be edited and displays the current value for the key. If you wish to change the document key shown in the "Document key" field on the right, select a different key from the "Document key" standard table on the left side (if one is available). The key may change while information is being entered in the fields. Mandatory field: In the "MTO level" standard table, select the MTO level for which documents are to be created. The levels "Estimated", "Current", and "Released" are available for selection. See also section Basic principles (Page 16). The content of the "Documents" list is governed by the administrator's configuration entries. If field contents can be edited, you can change them or add to them. In the "Filter" list, you can only edit the last column, "Value". To change or add to the content of text fields, you can edit the columns "Field" and "Value" in the "Text fields" control group. You can only edit the additional "Document" column if it has not been created by the administrator. 4. Click the "Create documents" button. The documents are created and backed up. 5. To confirm, click on the "Apply" or "OK" button. Operating Manual, 08/2011, A5E03640142-01 23

Material documentation and order requests 6.1 Creating MTO documents Via the context menu In this case, in contrast to when you create MTO documents directly using the Material Management Assistant, the following information is transferred from the "MTO Documents" tab of the configuration object to the Material Management Assistant: Data in the "Filter" control group, "Value" column The value in this column is taken from the object whose context menu you used to create the MTO documents. You can find additional information on this topic in the "COMOS Material Management Administration" manual, keyword ""MTO Documents" tab". Data in the "Text fields" control group Prerequisite The Material Management Assistant is open. Procedure 1. In the navigator, select an object that you want to check on the basis of the filter values pre-selected in the configuration object. The selected object must have the base object which is specified in the configuration object on the "MTO documents" tab in the "Baseobject for creating documents via Popup" field. 2. Select the "MTO > Create MTO Document" command from the context menu. 3. Click the "MTO Documents" tab in the Material Management Assistant. 4. Make the required settings here: If you wish to create an MTO document package for the first time, activate the "new Package" option. If you wish to update an MTO document package, activate the "update Package" option. The "Created Document Key" field cannot be edited and displays the current value for the key. If you wish to change the document key shown in the "Document key" field on the right, select a different key from the "Document key" standard table on the left side (if one is available). The key may change while information is being entered in the fields. Optionally, you can select in the "MTO level" standard table the MTO level for which documents are to be created. Default: "Current". See also section Basic principles (Page 16). The content of the "Documents" list is governed by the administrator's configuration entries. If field contents can be edited, you can change them or add to them. In the "Filter" list, you can only edit the last column, "Value". The contents of this column are transferred from the "MTO Documents" tab of the configuration object. To change or add to the content of text fields, you can edit the columns "Field" and "Value" in the "Text fields" control group. These values are transferred from the "MTO Documents" tab of the configuration object. You can only edit the additional "Document" column if it has not been created by the administrator. 24 Operating Manual, 08/2011, A5E03640142-01

Material documentation and order requests 6.2 Creating MPR documents 5. Click the "Create documents" button. If you wish to discard the document packages that were created, click on "Cancel". 6. To confirm, click on the "Apply" or "OK" button. See also "MTO documents" tab (Page 29) 6.2 Creating MPR documents Procedure To create MPR documents, proceed as follows: 1. Call the "Plugins > Basic > Material Management Assistant" menu command. 2. Click the "MPR Documents" tab. 3. Make the required settings here: If you do not wish to use the set of rules for component margins that is displayed, select another set of rules from the "Ruleset" standard table. If you want a document revision to be applied automatically as soon as the MPR document has been created, activate the "make revision" option. If you wish to assign document keys for a new MPR document, activate the "new MPR" option. If you wish to update an MPR document, activate the "update MPR" option. In this case you can actively load a saved MPR revision using the "MPR Revision" standard table. If new keys are available in the "MTO Key" standard table, you can select them and add them to the "Keylist" using the "Add keys" button. When creating a new MPR document, at least one key must be assigned to the "Keylist" (which was initially empty) using the "Add keys" button. In order to select a document key from a list of MTO keys that have not been used up until now, click on the "MTO Key" standard table. To then add a key displayed under "MTO Key" to the "Keylist", click on the "Add keys" button. If you wish to create an order list for an entire unit, for example, but you have created MTO document packages for each subunit beforehand, the keys of all MTO documents in use must be added to the "Keylist". If you are defining a text field and wish to fill it with a particular value, edit the fields "Text" and "Value". 4. To display the elements that can be ordered in the order list, click on the "Refresh" button. 5. If you wish to correct the data shown in the "Margin" column to bring it into line with the margins in accordance with the specified "Ruleset", you can edit these fields. Operating Manual, 08/2011, A5E03640142-01 25

Material documentation and order requests 6.2 Creating MPR documents 6. In order to create the MTO documents in accordance with the default settings, click on the "Create document" button. The documents are created and backed up. 7. To confirm, click on the "Apply" or "OK" button. See also "MPR documents" tab (Page 31) 26 Operating Manual, 08/2011, A5E03640142-01

References 7 7.1 exportmto file The exportmto file must meet the following conditions: A value must be available for at least the <elementref> or <elementname> nodes. All the nodes listed in the example must be available. In order for the file to be recognized, it must be named as follows: exportmto_<yymmdd>_<hhmmss>.xml Example <headerblock> <batchdata> <batchdataname>date</ batchdataname > <batchdatavalue>july 14, 2011</ batchdatavalue > </batchdata> <batchdata> <batchdataname>user</ batchdataname > <batchdatavalue>a_user1</ batchdatavalue > </batchdata> </headerblock> <datablock> <pipedata> <comosstatus>0</comosstatus> <elementref>17385/44062</elementref> <elementname>/p1m1t1/z003</elementname> <comosuid>a2n66274we</comosuid> <currelstat>r</currelstat> <materialfile> D:\MTOExport\MaterialFiles\_P1M1T1_Z003_material.txt </materialfile> <revision>abc</revision> <pdmsstatus>0</pdmsstatus> </pipedata> <pipedata> </pipedata> </datablock> Operating Manual, 08/2011, A5E03640142-01 27

References 7.1 exportmto file Tag <batchdataname> <batchdatavalue> <pipedata> <comosstatus> <elementref> <elementname> <comosuid> <currelstat> Description Name of the batch attribute Value of the batch attribute Contains the data relating to a pipe for which an XML file (containing the MTO-related data) is being created. Completed automatically while data is being transferred from AVEVA PDMS to COMOS. If an entry is made prior to transfer, the <pipedata> block is skipped, because it is deemed to have already been processed. Possible values: 0: MTO transfer to COMOS successful 1: MTO transfer to COMOS not successful 2: The "current" status has been applied automatically. 4: Material files have been created automatically 8: Material file damaged 16: <elementname> determined using <elementref>. 32: <comosuid> determined using <elementref>. 64: <elementref> determined using <elementname>. 128: : <elementref> points to a ZONE or PIPE. New nodes <pipedata> have been created in this XML file for all PIPES in this ZONE or SITE. Reference number for a pipe from AVEVA PDMS. Has to belong to the same object as the entry in <elementname>. If a ZONE or SITE from PDMS is specified instead of a PIPE, a separate node <pipedata> is created for each of the pipes covered. Name of a pipe from AVEVA PDMS. Has to belong to the same object as the entry in <elementref>. If a ZONE or SITE from AVEVA PDMS is specified instead of a PIPE, a separate node <pipedata> is created for each of the pipes covered. UID of the object from COMOS that is linked to the pipe in AVEVA PDMS which is described in <pipedata>. Possible values: C R <materialfile> <revision> <pdmsstatus> If R is entered as the value, a value for <revision> must also be available. If the tag is empty, a value of C is applied. Path to the material file that is to be used. If this is empty, a material file is created automatically for the referenced pipe. Name of revision Ignored in the case of materials with the status C. Value = -1: The current node <pipedata> is skipped. If this is empty, a value of 0 is applied and set. The transfer continues. 28 Operating Manual, 08/2011, A5E03640142-01

References 7.2 User interface reference 7.2 User interface reference 7.2.1 "MTO documents" tab When you call the "Plugins > Basic > Material Management Assistant" menu command, the following control elements are available on the "MTO Documents" tab: Control element "new Package" option "update Package" option List "Created document key" field "MTO level" list "Start object" field "Create documents" button Description Creates a new document package. Updates a document package for an existing estimate. Use this field to select further document keys from a list. It is only possible to make this selection if the administrator has stored further document keys. Shows the current value for the document key. You cannot edit this field. Example: The document key was defined by the administrator. You can find additional information on this topic in the "3D Integration Administration" manual, keyword ""MTO Documents" user interface reference tab". Provided you do not enter a value in the "Value" column in the first line of the "Text fields" control group described here, or in the first line of the "Filter" control group, the following document key is displayed: "MTO--". While the entries are being made, the key changes accordingly in the relevant fields. Mandatory field. The following levels are available for selection: "Estimated" "Current" "Released" See also section Definitions (Page 9). You select the start object for the material lists in this field. After selecting the MTO level, the start object from the associated query is displayed. You can change the start object for the current process here. Creates MTO documents in accordance with the default settings. "Status" control group Here status messages are output after the documents have been successfully created, or if errors occur. Operating Manual, 08/2011, A5E03640142-01 29

References 7.2 User interface reference "Documents" control group If fields in this control group can be edited, you can add to or change the contents of the fields. The fields are preconfigured by the administrator. Field "Master" "Name" "Document Name" "Label" "Description" "Report" "PackageGroup" Description Field that cannot be edited. The assignment as master document (Yes/No) was made by the administrator. Field that cannot be edited. The assignment to the identification name used internally was made by the administrator. Mandatory field. Can be edited. Here you enter or change the name of a document. Field that can be edited. Sets the property "Label" on the document object. Field that can be edited. Here you enter or change a description text. Mandatory field. Can be edited. Here you enter or change the name of the appropriate report template. You can find suitable report templates on the "Base objects" tab in the Navigator under the "@MM Material Management > @D Documents" node. Mandatory field. Can be edited. Here you enter or change the number for the package index, such as 1 or 2. All documents that relate to the same package index later emerge in a single group. "All available documents" control group This table contains all created MTO documents. Column "Document" "Nav" "Open" Description Contains the document key of an MTO document. Double-click to navigate to the master document of an MTO document. Double-click to open the master document of an MTO document. "Filter" control group Column Document Column Operation Value Description Field that cannot be edited. The content is specified by the administrator. Field that cannot be edited. The content is specified by the administrator. Field that cannot be edited. The content is specified by the administrator. Field that can be edited. Example: Enter the value "2". If an equals sign is set as the operand in the "Operation" field, only column contents with the value "2" are shown. 30 Operating Manual, 08/2011, A5E03640142-01

References 7.2 User interface reference "Text fields" control group For changing the attributes of text fields. Column Document Field Value Description The field cannot be edited if the content has been created by the administrator. Field that can be edited. References the text field in the respective document. Entry example: "E-mail" Field that can be edited. This value is shown in the document. Entry example: "Smith@ExampleCompany.com" "Additional filter" control group For adding more filters for document creation. Column Document Column Operation Value Description Enter the internal name of the MTO document for which the filter is defined. Enter the column name in the material list in which the filter is to be set. Select a comparison operator here. Enter a filter value here. Buttons Button "Cancel" "Apply" or "OK" Description Removes even document packages that have already been created. Saves it in the COMOS system. See also Creating MTO documents (Page 23) 7.2.2 "MPR documents" tab When you call the "Plugins > Basic > Material Management Assistant" menu command, the following control elements are available on the "MPR Documents" tab: "Status" control group For outputting status messages after documents have been successfully created, or if errors occur. Operating Manual, 08/2011, A5E03640142-01 31

References 7.2 User interface reference "Document Settings" control group with control elements Control element "Normal mode" option "Extended mode" option "Ruleset" list Description In normal mode, you can enter positive values in the order list in the "Margin" column. If you attempt to enter a negative value, it will automatically be set to 0. In extended mode, you can also enter negative values in the order list in the "Margin" column. This allows you to correct any erroneous data that was included the last time an MPR document was created. Select a set of rules that the administrator has created for calculation of margins. You can find additional information on this topic in the "3D Integration Administration" manual, keyword "Creating and managing MTO sets of rules". "Document key" field The field cannot be edited. Here the document key used in accordance with the administrator's configuration settings is displayed. "Package name" field "Document ID" field "Make revision" option "Create document" button The field cannot be edited. Here the "Package name" used in accordance with the administrator's configuration settings is displayed. The field cannot be edited. The "MPR package ID" used is displayed here in accordance with the administrator's configuration settings. Activated: A document revision is applied to an MPR document as soon as it is created. The revision is assigned the "released" status. Creates MPR documents in accordance with the default settings. "Used document keys" control group with control elements Here you use the keys of the MTO documents. An MTO key can only be used once within an MPR document. Control element Description "new MPR" option Activate this option when creating a new MPR document. "update MPR" option Activate this option when updating a MPR document. "MPR Revision" list If necessary, make a selection from a list of saved MPR revisions. Only active when the "update MPR" option is activated. "MTO Key" list List for displaying keys of MTO keys that have not been used up until now. "Add keys" button Use this button to add document keys to the "Keylist". Button "Refresh" For updating. This button is required for loading the list contents. "Keylist" Mandatory field for at least one entry. When creating a new MPR document, at least one key must be assigned to the "Keylist" (which was initially empty) using the "Add keys" button. For an existing MPR document, shows the key linked to the current MPR document. 32 Operating Manual, 08/2011, A5E03640142-01

References 7.2 User interface reference "Text fields" control group Here you can change the attributes of text fields. Column "Text" "Value" Description Field that can be edited. References the text field in the respective document. Entry example: "E-mail" Field that can be edited. This value is shown in the document. Entry example: "Smith@ExampleCompany.com" "Used objects" control group If you click "Refresh", this order list is filled with material in accordance with the configuration settings. Column Options column "Description" "Eng. Quant" "Margin" "Tot. Purch. Q." "Purch. Quant." Description Option activated: Material is considered when ordering. Option deactivated: Material is not considered when ordering. Following an update, it reappears in the order list. Description text. Planned quantity. Field that can be edited. Here you can make manual corrections to margins which have been calculated in accordance with the settings for the "Ruleset" that is being used. Total purchase quantity. Current purchase quantity. Further columns To display additional columns on your MPR document (for order numbers, for example), please speak to your administrator. You can find additional information on this topic in the "3D Integration Administration" manual, keyword ""Purchase Orders" user interface reference tab". See also Creating MPR documents (Page 25) Operating Manual, 08/2011, A5E03640142-01 33

References 7.2 User interface reference 34 Operating Manual, 08/2011, A5E03640142-01