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

1 COMOS idb 1 Help folder for the cdb and idb databases 2 COMOS Operating Manual Using the COMOS help 3 COMOS menu when using idb 4 Platform 5 Process 6 Automation 7 Lifecycle 8 11/2013 A5E AA

2 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 indicates that minor personal injury can result if proper precautions are not taken. NOTICE indicates that property damage can result if proper precautions are not taken. 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: Trademarks 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. 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 NÜRNBERG GERMANY A5E AA P 11/2013 Technical data subject to change Copyright Siemens AG All rights reserved

3 Table of contents 1 COMOS idb Help folder for the cdb and idb databases Using the COMOS help Copying documentation to the help folder Opening the help Using the HTML help Displaying the COMOS help system online Using the COMOS help system in My Documentation Manager COMOS menu when using idb Platform Information on rights administration COMOS Platform COMOS glossary COMOS Web Security information COMOS Mobile Document Review COMOS Enterprise Server COMOS Platform Interfaces Interface to Teamcenter Process Data Interface (PDI) COMOS Teamcenter interface Process P&ID Automation Logical Cabinet Equipment wizard Lifecycle D Integration PQM Operating Manual, 11/2013, A5E AA 3

4 Table of contents 4 Operating Manual, 11/2013, A5E AA

5 COMOS idb 1 Overview A new database standard is introduced with COMOS 10.1: industrial DataBase (idb). idb is the secure platform for industry-specific data management. With idb you will shorten your development cycles, reduce your development effort, and increase your productivity. Benefit from the advantages of the latest generation of databases: Standardization of data objects Ability to update even a productively deployed database Documentation of the most important database contents, for example, script blocks Current units and symbols This document describes innovations for COMOS 10.1 based on the "idb" database. You will find more detailed information on the features of idb in section COMOS Platform (Page 21). If you are already a customer, you can continue to use your existing databases (database standard cdb) with version Operating Manual, 11/2013, A5E AA 5

6 COMOS idb 6 Operating Manual, 11/2013, A5E AA

7 Help folder for the cdb and idb databases 2 Overview A separate help folder is supplied for the idb and cdb databases as of COMOS version You can see the content of the respective folder in the COMOS "Help" menu depending on the database with which you start COMOS. Contents of the "Help_iDB" folder Help system 10.1 (.chm) (.pdf) COMOS Readme (.pdf) Contents of the "Help_cDB" folder Help system (.chm) Includes the "PQM Configuration Tools" manual It covers the following topics: "Advanced PQM functions", "Test plan management" COMOS 10.1 Updateinfo classic Database (.pdf) "Integrated Engineering" manual (.pdf) See also Copying documentation to the help folder (Page 9) Operating Manual, 11/2013, A5E AA 7

8 Help folder for the cdb and idb databases 8 Operating Manual, 11/2013, A5E AA

9 Using the COMOS help Copying documentation to the help folder Requirements COMOS is installed. Procedure 1. Open the directory in which the help files are located in the file explorer. For example: <COMOS Installation directory>/help/<help folder database>/<language folder> 2. Save your documentation in the respective help folder "Help_iDB" or "Help_cDB". Note "Help" directory Documents that are located directly in the "Help" directory are not displayed. 3.2 Opening the help Overview of the COMOS help The COMOS help consists of the following components: COMOS help system: A library with manuals on COMOS Individual help files in the formats *.pdf, *.pdx and *.doc The PDF files "COMOS - What's new?" and "COMOS Readme" are supplied with COMOS. Note Supplementing the help files You can integrate your own help files in the COMOS "Help" menu. The files are displayed in the COMOS "Help" menu. You can find more information on this topic in the "COMOS Platform Administration" manual, keyword "Central administration of the help menu". Operating Manual, 11/2013, A5E AA 9

10 Using the COMOS help 3.2 Opening the help You can open the COMOS help as follows: COMOS help system: From COMOS Online From the file system Individual help files: From COMOS From the file system Note References to other manuals If other manuals are referenced in the COMOS help, these manuals also form part of the COMOS help. Opening the help from COMOS 1. Start COMOS. 2. To open the COMOS help system, select the menu command "Help > COMOS help system". The help system is opened as an HTML help. See also chapter Using the HTML help (Page 12). 3. To open an individual help file, select the command "Help > <File name>" in the menu. To read the help in a different language, switch the language of the COMOS user interface and call up the help system again. Opening the help online See also chapter Displaying the COMOS help system online (Page 13). 10 Operating Manual, 11/2013, A5E AA

11 Using the COMOS help 3.2 Opening the help Opening the help through the file system 1. Open the directory in which the help files are located in the file explorer. For example: <COMOS Installation directory>/help/<database>/<language folder>. 2. Double-click the file "COMOS_HelpSystem_enUS.chm" to start the COMOS help system. The help system is opened as an HTML help. See also chapter Using the HTML help (Page 12). 3. To open a PDF document, double-click the document. Viewing the PDF help To display the COMOS help as PDF files, you require a PDF Reader that is compatible with PDF 1.7 (ISO :2008 PDF). Operating Manual, 11/2013, A5E AA 11

12 Using the COMOS help 3.3 Using the HTML help 3.3 Using the HTML help Requirements Operating system: Windows 98 and higher Procedure 1. Open the COMOS help system in COMOS or the file system as HTML help. See also chapter Opening the help (Page 9). 2. On the "Contents" tab, open the node of a COMOS product family, for example "COMOS Platform". All the manuals that belong to the modules of this product family are displayed. 3. Open a manual and select a chapter. The chapter contents are shown on the right. 4. You have the following options when working with the help system: Search: You can search through the entire help system on the "Search" tab. Displaying related topics: If related topics are available for the chapter currently displayed, these are listed in the menu bar above the chapter contents: The "Manuals" menu contains related instructions; the "Basic principles" menu contains related basic principles. To change to a chapter, select it. Creating Favorites: Select a chapter on the "Contents" tab. Change to the "Favorites" tab and click "Add". Toggling between chapters already displayed: You can use the "History" and "Extras" menu and the buttons "Back" and "Forward" to toggle between the chapters already displayed. Note If you change from one chapter to a different chapter, for example via the links embedded in the chapters, the Favorites or the "History" menu, the node of the currently open chapter is always displayed on the "Contents" tab. 12 Operating Manual, 11/2013, A5E AA

13 Using the COMOS help 3.4 Displaying the COMOS help system online 3.4 Displaying the COMOS help system online The COMOS help system is available free of charge and in multiple languages on the Internet: Open the following Internet page: COMOS documentation ( In the "Overview", you will find the various product areas of COMOS product family. In the "Topics" column, you will find the COMOS Manual Collection or individual help files. The lines contain links to the My Documentation Manager and the SIEMENS Industry Online Support Portal: Clicking on the icon opens the document in My Documentation Manager (MDM). The range of functions in MDM depends on whether you are logged in: Without registration/login: View documents DE, EN, FR, ZH With registration and login: Configure, compile documents, notification function, etc. See chapter Using the COMOS help system in My Documentation Manager (Page 15). Link to the document in the available languages in the SIEMENS Industry Online Support Portal: DE=German EN=English FR=French ZH=Chinese simplified COMOS help files in the SIEMENS Industry Online Support Portal The COMOS help files are also available as PDF files in the Siemens Industry Online Support Portal. In addition, you can display the documents with the My Documentation Manager. To find COMOS help files, proceed as follows: Operating Manual, 11/2013, A5E AA 13

14 Using the COMOS help 3.4 Displaying the COMOS help system online 1. Open the Web page of the Siemens Industry Online Support portal: SIOS ( "Product Support" in the navigation bar "Index (A-Z)" tab "Navigation" tab 2. Click on "Product Support" in the navigation bar. 3. You have three ways to find COMOS help: Open the "Navigation" tab and look for COMOS in the product tree. You can find COMOS help under: "Automation technology > Automation systems > Automation software > Plant Engineering Software COMOS" Open the "Index A-Z" tab. If you click on "C", you will see the COMOS help files in the list. Enter the term "COMOS" in the search box at the top right and click "Search". You can narrow search results by clicking on "Manuals" below "Search area" in the hit list. 4. Select a COMOS help file from the list and click the title. 5. When the selected COMOS help is displayed, you can choose from the following: "Displaying and configuring": Opens the document in My Documentation Manager. "Download": As PDF file 14 Operating Manual, 11/2013, A5E AA

15 Using the COMOS help 3.5 Using the COMOS help system in My Documentation Manager 3.5 Using the COMOS help system in My Documentation Manager My Documentation Manager is a central online database for SIMATIC and COMOS customer documentation. My Documentation Manager allows you to edit the entire customer documentation, reorganize it and export it into a variety of formats if needed. You can assemble documentation corresponding exactly to your system or configuration from the documents that are available. The notification feature informs you by when a document in your collection has changed. Range of functions in My Documentation Manager The range of functions depends on whether or not you are logged in: Functions without login: View customer documentation Open help for My Documentation Manager Additional functions with login: Configuration: Assembly of individual documents in a collection Delete, add, move, copy any document in a collection Send collection to an address as a link Search and assemble documents in one language and then export them to one of the available languages Notification feature is available on all levels: Single page, chapter, manual, collection, etc. Export documents, folders and collections as a PDF, XML, or RTF file Working with My Documentation Manager The following section describes how to open the My Documentation Manager : Displaying the COMOS help system online (Page 13). A comprehensive description of working in My Documentation Manager is available in the help: Help on My Documentation Manager ( DE.htm). Operating Manual, 11/2013, A5E AA 15

16 Using the COMOS help 3.5 Using the COMOS help system in My Documentation Manager Registration and login to My Documentation Manager 1. Click "Full scope of functions after login/registration". The login form for My Documentation Manager opens. 2. Click "Yes, I would like to register now" and fill out the fields in the following windows. 16 Operating Manual, 11/2013, A5E AA

17 Using the COMOS help 3.5 Using the COMOS help system in My Documentation Manager 3. Click the Next button, until your login information is completed. 4. You have now successfully registered and can use all the functions of My Documentation Manager. Operating Manual, 11/2013, A5E AA 17

18

19 COMOS menu when using idb 4 Requirements The COMOS menu changes depending on the COMOS version and the type of database. This section describes the changes under the following conditions: Switching from COMOS 10.0 to COMOS 10.1 And simultaneously from cdb to idb List of unavailable menu commands View > cdb Engineering tasks Extra > Queries > Queries for base objects > Query: cross-project base objects Extra > Queries > Tools > Convert old scripts to script blocks Extra > Queries > Tools > Semi-open connections Extra > Queries > Queries for DVM > My recent documents Extra > Viper 3D Editor > Electrical engineering Plugins > Basic > Unit conversion Plugins > Basic > Pipe spec mapping Plugins > Basic > Material Management Assistant Plugins > Basic > Task Management Plugins > Basic > PDMS PipeSpec Interface Plugins > Maintenance Plugins > Mechatronics Plugins > Automation > Signal name matching Plugins > Automation > IEC to JIC conversion Plugins > Automation > PCS7 interfaces > Create templates Plugins > Automation > PCS7 interfaces > Import/Export PCS 7 Plugins > Automation > Interfaces > EPLAN5 data exchange Plugins > Automation > Interfaces > Ruplan import Plugins > Automation > Interfaces > VNS import Administrator > Base data > Import ECAD components Administrator > Base data > Pipe specs Administrator > Base data > Attribute transfer editor Administrator > System > Database adjustments Operating Manual, 11/2013, A5E AA 19

20 COMOS menu when using idb List of textually changed menu commands Extra > Queries > Queries for engineering objects > Query: cross-project engineering objects Changed to: "Engineering objects query (cross-project)" Extra > Queries > Queries for documents > Query: cross-project documents Changed to: "Query: Documents (cross-project)" Extra > Queries > Tools > Wire list Changed to: "Wire list (via connectors)" Extra > Queries > Tools > Restore COMOS objects Changed to: "Restore COMOS objects" Extra > Queries > Queries for DVM Changed to: "DVM queries" Extra > Queries > Queries for DVM > Bulk checkin/checkout Changed to: "Bulk checkin/checkout" Moved to: "Plugins > PQM > DVM queries" Extra > Viper 3D Editor Changed to: "3D Review" Extra > Viper 3D Editor > 3D Piping Changed to: "3D view" Plugins > Basic > PDMS Interface Changed to: "PDMS Pipe Spec interface" Plugins > Automation > Interfaces > Bulk editing of semi-open connections Moved to: "Plugins > Automation" List of new menu commands Extra > Queries > Queries for engineering objects > Query: Engineering objects (alternative) Extra > Queries > Queries for base objects > Query: Base objects (alternative) Extra > Queries > Queries for attributes > Query: Attributes (alternative) Extra > Queries > Queries for documents > Query: Documents (alternative) Extra > Queries > Queries for connectors > Query: Connectors (alternative) Plugins > Basic > PDMS Engineering Interface Plugins > Basic > Walkinside object assignment Plugins > Basic > Data aggregation Plugins > Automation > Interfaces > STEP7 Interface Plugins > Automation > Interfaces > Cabinet Equipment wizard Administrator > Base data > String rule manager Administrator > Base data > Database update 20 Operating Manual, 11/2013, A5E AA

21 Platform Information on rights administration Adaptation of the documentation for the topic "Administration of rights and roles" For the version COMOS 10.1, additional information was added to the overall help regarding the maximum number of roles and the maximum number of users. 5.2 COMOS Platform idb database COMOS is delivered with the new database type "idb". This documentation describes COMOS used in conjunction with idb. Project properties revised In prior COMOS versions the project properties were stored in three different sources. Now all project properties are combined and are stored in an XML-like structure. Thus all project properties can be queried using a uniform programming syntax. The project properties are no longer displayed in the interface as tabs. Instead, there is a tree-like structure of categories. All project properties were resorted and supplied with more understandable texts as needed. Operating Manual, 11/2013, A5E AA 21

22 Platform 5.2 COMOS Platform Database update The "Database update" tool has the following use cases: Install idb database updates Controlled application of the corrections provided by Siemens to your own database. The idb database updates are cumulative. Update 5 also includes all corrections and updates from updates 1 to 4. The following workflow is offered for this purpose: 1. Preliminary application of changes to a special working layer called the consolidation layer Preliminary application is possible in one or all of the following project types: System project Base project Template project 2. Isolated check of changes 3. Selection of objects to be applied 4. Application of selected objects to the released area Classification method changed COMOS now distinguishes between two types of classification: Classification Hierarchical classification Describes the class structure and therefore the base data structure of a COMOS module. Five hierarchically dependent fields with 1 to 4 characters each. The first layer of hierarchical classification is a three-digit key for the module name (M00 for Basic, M20 for Process, M40 for Automation, and so on). In hierarchical classification, the subsequent layers (2, 3, etc.) can only be set in relation to the layers before them. Functional classification Describes the cross-module function of an object. Five independent fields with 1 to 4 characters each. You can assign any combination of functional classification keys. User classification Is available for your purposes. The functional classification technique is used in the background. Hierarchical user classification Functional user classification 22 Operating Manual, 11/2013, A5E AA

23 Platform 5.2 COMOS Platform For this reason, four basic variants for classifications appear below > A10": Classification key 1: COMOS (hierarchic) Classification key 2: COMOS (functional) Classification key 3: Customer (hierarchic) Classification key 4: Customer (functional) The hierarchic classification with prefix "Z" is no longer reserved for customer-specific classifications. LockLock, system flag The idb contains system-related objects which must not be changed. There are special lock mechanisms to protect these objects. The "Object locking" (system lock or lock-lock) function. This function can only be edited by Siemens employees. For reasons of clarity, the "system object" status is also available. This status shows that the object is a system-related object. This status has no other implications. In practice, the "System object" status is often combined with the "Object locking" function. Script Library All scripts were standardized and stored under a common node. The script blocks are commented and are easy to use or modify. This greatly reduces the effort required for customer-specific modification of the database. Inheriting queries Configure a source query and inherit another query from it, which is in a branch of the structure tree. To inherit a query, proceed as follows: 1. Select the "System" tab in the properties of a query. 2. Drag&drop the source query from the Navigator onto the "Base object" field in the "Reference" control group. A window opens. You have the following options: To change the base object reference and replace your archive settings, click the "Yes" button. To change the base object reference but retain your archive settings, click the "No" button. To cancel the process without making any changes, click the "Cancel" button. 3. Confirm your entries. Operating Manual, 11/2013, A5E AA 23

24 Platform 5.2 COMOS Platform Saving settings for the queries You can disable the permission for saving a query in the base query. When saving is disabled, the following happens: Base query: A security prompt appears. After this, saving is possible. "Save as" is still permitted. Query: The menu command "Save" is disabled. "Save as" is still permitted. The "Load from base object" menu command is disabled. Because the archive of the query cannot be saved, the archive of the base query is automatically loaded every time you open the query. DIN identifier Unit systems are standardized for the different technical areas. To illustrate these standardizations, the "DIN identifier" field is now available. A unit is uniquely identified internationally with a DIN identifier and can be more easily imported or exported. The DIN identifiers are listed in a DIN property list that is available on the Internet. New option for subelements New option "Extend subelements": Only engineering objects which are subelements (child objects) of the base object can be created in the engineering view. Cross-inherited subelements are also created. Script access to standard tables: ItemByValue / ItemByXValue The following functions are now available: ItemByValue(0, const CString& searchvalue) / ItemByXValue(unsigned long index, const CString& searchvalue) Returns the value object for the search value. searchvalue: Search value Index: Search index for XValue Return: The object with the value or NULL Name mask for elements If the "Default" value is selected for elements for the "Virtual" setting, text mask for names that is entered in the base object is evaluated. 24 Operating Manual, 11/2013, A5E AA

25 Platform 5.2 COMOS Platform Extending the "Type" list for connectors In the "Type" field for connectors, two new types are available: Task Used for the definition of engineering tasks FEED Connection for FEED objects (for example, process streams) Monitoring using IsWorkflowReference Monitoring using the prefix "WREFOBS_" has been replaced by monitoring using the "SetWorkflowReference" and "IsWorkflowReference" methods. These properties can be queried at the attribute my means of a script. To do this, create a query and define a new column with the corresponding property. You can then check or edit the property in the query. New script function GetNLSText Customer-specific scripts can now use NLS texts. As a result, all texts and messages (such as a Messagebox) are multilingual. An NLS text is created with one of these functions: GetInternationalTextFromNLSByProjectLanguage GetInternationalTextFromNLSByGUILanguage GetInternationalTextFromNLSByLanguageID Dependency of working layers on report templates Report templates can be customized for each working layer. Various requirements apply to the function "Working layer-dependent report templates". In particular, all template files must be integrated in COMOS by means of document objects. You can find more information on this topic in the "COMOS Platform Administration" manual, keyword "Creating a working layer-dependent template file". Revision archive: Freely configurable revision printer (HARP) A standard configuration was developed for the freely configurable revision printer. The "HARP.ini" file supplied in the default settings uses the following configuration: The OEM PostScript printer driver supplied with Windows COMOSHarp.inf COMOSHarp.ppd The HARP standard configuration requires the following PS converter: GhostScript Operating Manual, 11/2013, A5E AA 25

26 Platform 5.2 COMOS Platform Using the PDF document view With the "Multiple Document Preview" plugin, you can view one or more external PDF documents on the working area of the report. You can change and print the placed PDF document in the view, but not edit it. Logging (TraceListener) The "Trace and debug schema" from.net Framework 4.5 is supported. You can find the documentation for the associated XML schema on the Internet at Microsoft msdn. Logging is switched on as follows: Comos.exe.config under <system.diagnostics><sharedlisteners>: Comment in "ComosTextWriterTraceListener". The listener must then be added to the corresponding trace sources: Comos.exe.config under <system.diagnostics><sources> Object matcher extended The object matcher can be opened via the context menu for an object and in this case compares the status of an individual object in various working layers. The consolidation layer is now also supported. In this case, the object is compared with the current delivery status of the object. This option is only available for objects for which a delivery status is available. In all other cases, the shortcut menu "Working layers/histories > Compare object" is grayed out in the released area. The delivery status of an object is determined by the last idb database update. Language relevant to project This option specifies which languages are relevant for a project. Once this option has been activated, it is only possible to switch between the project-relevant languages in the "Languages" tab. GrayboxSelectionMode Selection behavior for modules can be changed using the system attribute (SYS.GrayboxSelectionMode) in the main document. GrayboxSelectionMode = 0 When you click on an object within the module, the object itself is selected. GrayboxSelectionMode = 1 (default) When you click on an object within the module, the entire module is selected. Only the second click selects an individual object. 26 Operating Manual, 11/2013, A5E AA

27 Platform 5.3 COMOS glossary 5.3 COMOS glossary Revision The terms in the COMOS glossary were revised. The glossaries of the following manuals were moved to the COMOS glossary: PQM FEED Operation 5.4 COMOS Web Security information Data security The "COMOS Web" manual now includes information on data security COMOS Mobile Document Review Saving "COMOS Mobile Document Review" data management in a separate base project In the project settings in COMOS, you set the free saving of "COMOS Mobile Document Review" data management in a base project other than S01. Here you will find the new project option "Base project" under the "Web" category. You can find more information on this topic in the "COMOS Web" manual, keyword "Saving the "COMOS Mobile Document Review" data management in a separate base project". Operating Manual, 11/2013, A5E AA 27

28 Platform 5.5 COMOS Enterprise Server 5.5 COMOS Enterprise Server Release of working layers At the command line, you can now also configure the release of working layers. The following requirements must be met: The working layer exists. The linked working layer corresponds to the linked working layer of the working layer above it. No users are logged on to the working layer. If you cancel the release process via the COMOS Enterprise Monitor, the working layer receives the status "Incorrect release". Deletion of working layers In the command file, you can now also configure the deletion of working layers. The following requirements must be met: The working layer exists. No projects or working layers are linked in a working layer in the base project. No users are logged on to the working layer. No objects are present which prevent deletion. If you cancel the deletion process via the COMOS Enterprise Monitor, the objects are still in the database, but are no longer visible. Therefore, do not cancel the deletion process. You can find more information on this topic in the "COMOS Enterprise Server" manual, keyword "Editing working layers". 28 Operating Manual, 11/2013, A5E AA

29 Platform 5.6 COMOS Platform Interfaces 5.6 COMOS Platform Interfaces Interface to Teamcenter Process Data Interface (PDI) Process Data Interface (PDI) is now available. Objective Pipe parts are transferred from COMOS to NX via PDI. The data is transferred via Teamcenter to NX. Teamcenter is the interface for the data transfer between COMOS and NX. Transfer takes place by means of XML files in which information about pipe specs and pipe parts is collected. Pipe schedules are transferred as PDF. Information about PipeRun and XMplant is also transferred as an XML file. Functional scope PDI comprises the following functions: Connection between COMOS and NX Connection between objects Navigation to 3D objects in NX and COMOS objects on the P&ID Pipe spec export Publishing documents Administration The configuration file "Comos.PDI.config" is available for the administration of PDI. Use the "pipepartfamilies.xml" file to assign pipe parts in COMOS to pipe part families in NX. You can edit the "pipepartfamilies.xml" file in COMOS. The following functions are available for this purpose: Adding attributes Editing attributes Deleting attributes You can find more information on this topic in the "COMOS Platform Interfaces" manual, keyword "Process Data Interface (PDI)". Operating Manual, 11/2013, A5E AA 29

30 Platform 5.6 COMOS Platform Interfaces COMOS Teamcenter interface Synchronizing attribute values You can synchronize attribute values of Teamcenter forms to the engineering and base data with COMOS attributes. Conversely, you can synchronize attribute values from COMOS engineering to Teamcenter forms. You can find more information on this topic in the "COMOS Platform Interfaces" manual, keyword "Synchronizing attribute values". 30 Operating Manual, 11/2013, A5E AA

31 Platform 5.6 COMOS Platform Interfaces Operating Manual, 11/2013, A5E AA 31

32

33 Process P&ID XMpLant export COMOS can now also export files based on XMpLant XMpLant import For the import, COMOS only supports files with XMpLant Version An administrator can enter the subprogram OnXMpLantImportDone on P&ID objects or on P&ID in the script. Once the XMpLant import is complete, the script is executed for each engineering object. You can find additional information on this topic in the "P&ID Administration" manual, keyword "Creating "OnXMpLantImportDone" on COMOS objects". Based on two additional import options, you now have the option to identify changes during a reimport and determine how to handle specific objects. In the "Import and dissolve drawing" window, the following import options were added: "Import into new working layer" option "Remove not contained objects" option You can find additional information on this topic in the "P&ID Operation" manual, keyword ""Import and dissolve drawing" window". PDF import During a PDF import, all texts of a PDF are imported into COMOS. COMOS creates objects for each text in a text field in accordance with the rules defined by an administrator. You can find more information on this topic in the "P&ID Operation" manual, keyword "PDF import". Important terminology changes Old designation "Pipe branch" "Standard pipe banner" "Equipment" New designation "Pipe section" "Standard pipe label" "Equipment" Operating Manual, 11/2013, A5E AA 33

34 Process 6.1 P&ID Script option "SegmentULMode" The "SegmentULMode" script option is now also valid for P&ID. You find more information on this topic in the "COMOS Platform Administration" manual, keyword "Function reference for the options script". 34 Operating Manual, 11/2013, A5E AA

35 Automation Logical Initial step sequencer For function diagrams there is now an object for initial step sequencers: Place the object. An entry step, a transition and a final step are generated and connected on the function diagram and in the Navigator. Improved operation for step sequencers When you insert a new element in a step sequencer, COMOS checks the step sequencer logic: Missing objects are automatically created Example: When inserting a step, a transition is automatically inserted. Violations of the step sequencer logic are marked as inconsistent. Example: If you connect the returning connecting line of a jump with a subsequent step, the connection is marked as inconsistent. 7.2 Cabinet Equipment wizard The wizard for cabinet engineering offers you the following functions: Simple detail engineering List of the placed elements Direct access to all relevant attributes and functions Synchronization of all dependent documents Automatic 3D consistency check of the placed rail elements Operating Manual, 11/2013, A5E AA 35

36 Automation 7.2 Cabinet Equipment wizard 36 Operating Manual, 11/2013, A5E AA

37 Lifecycle D Integration PDMS: New interface "COMOS PDMS Engineering Interface" In addition to the old interface there is now a new interface available. To distinguish between them, the following terminology was defined: Old interface: "COMOS PDMS Interface" New interface: "COMOS PDMS Engineering Interface" Fundamental changes to the old interface: The user works on the PDMS page and can execute all actions from there. With the help of queries, the administrator defines in advance which COMOS objects can be loaded in the interface by a user or user group to read and edit them. The new interface offers a tree view of the loaded COMOS objects and additional options for comparing the objects in the two applications with one another. The interface features the following functions: Create individual objects in PDMS Create hierarchies in PDMS Synchronize and update attributes Assign objects to each other in COMOS and PDMS Navigate between COMOS and PDMS You can find additional information on this topic in the "3D Integration Operation" and "3D Integration Administration" manuals, keyword "COMOS PDMS Engineering Interface". PDMS: Citrix client installation mode (silent mode) Installation in silent mode runs in the background and is controlled by a text file in which the administrator has entered all of the relevant information in advance. You do not need to make any further entries during installation. You can find additional information on this topic in the "3D Integration Administration" manual, keyword "Citrix client (silent mode)". PDMS: Feedback mode If feedback mode is enabled, the two applications can bidirectionally make write access to data. If feedback mode is disabled, only COMOS can make write access to data from Walkinside. Operating Manual, 11/2013, A5E AA 37

38 Lifecycle COMOS 3D Viewing Installation of "COMOS Walkinside Integration" "COMOS Walkinside Integration" is the interface between COMOS and the 3D viewer application, COMOS Walkinside. In order to use COMOS 3D viewing, you must install the interface. You can find additional information on this topic in the "3D Integration Administration" manual, keyword "Installing "COMOS Walkinside Integration"". Assignment of COMOS objects and Walkinside objects Using a new plugin, you can now assign objects in order to make navigation possible. In the plugin, create a unique label for every object of a defined quantity of objects on the COMOS page and on the Walkinside page. The label is created with the aid of scripts. The related objects on the COMOS page and the Walkinside page must have the same label. You can find additional information on this topic in the "3D Integration Administration" manual, keyword "Configuring navigation". Export COMOS objects by means of a query This function is used to collect certain objects in Walkinside, which are already located in Walkinside and for which you have created an assignment. Example scenario: You want to view only those object in Walkinside which have to be maintained. You collect these COMOS objects in a query and export them to Walkinside. In Walkinside, a view of these objects is temporarily displayed. Important terminology changes Old designation Original PDMS interface (no name) "TaggedItem" class "Pipe" class "@PDMSMAP" folder LocObj New designation "COMOS PDMS Interface" "Device with label" class "Cable" class "Y00R00033 folder for class/subclass definitions (PDMS)" object Area pipe Operating Manual, 11/2013, A5E AA

39 Lifecycle 8.3 PQM 8.3 PQM Objective PQM (Project Quality Management) imports and administers external documents in COMOS. PQM supports you here as a document management system (DMS) for all important lifecycle phases of your project documents. Extended PQM functions The extended PQM functions are no longer part of this manual. Test plan management Test plan management is no longer part of this manual. "My recent documents" query The "My recent documents" query is no longer available. Operating Manual, 11/2013, A5E AA 39

40 Lifecycle 8.3 PQM 40 Operating Manual, 11/2013, A5E AA