Transcription
COMOSLifecycleProcess Data Interface toTeamcenter/NXOperating Manual05/2016 V 10.2A5E37098396-AAIntroduction1Terms2Software requirements3Synchronizing project datawith Teamcenter42D-based 3D design5Integrated documentmanagement6Integrated changemanagement7Administration8User interface reference9
Legal informationWarning notice systemThis manual contains notices you have to observe in order to ensure your personal safety, as well as to preventdamage to property. The notices referring to your personal safety are highlighted in the manual by a safety alertsymbol, notices referring only to property damage have no safety alert symbol. These notices shown below aregraded according to the degree of danger.DANGERindicates that death or severe personal injury will result if proper precautions are not taken.WARNINGindicates that death or severe personal injury may result if proper precautions are not taken.CAUTIONindicates that minor personal injury can result if proper precautions are not taken.NOTICEindicates 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 beused. A notice warning of injury to persons with a safety alert symbol may also include a warning relating to propertydamage.Qualified PersonnelThe product/system described in this documentation may be operated only by personnel qualified for the specifictask in accordance with the relevant documentation, in particular its warning notices and safety instructions. Qualifiedpersonnel are those who, based on their training and experience, are capable of identifying risks and avoidingpotential hazards when working with these products/systems.Proper use of Siemens productsNote the following:WARNINGSiemens products may only be used for the applications described in the catalog and in the relevant technicaldocumentation. If products and components from other manufacturers are used, these must be recommended orapproved by Siemens. Proper transport, storage, installation, assembly, commissioning, operation andmaintenance are required to ensure that the products operate safely and without any problems. The permissibleambient conditions must be complied with. The information in the relevant documentation must be observed.TrademarksAll names identified by are registered trademarks of Siemens AG. The remaining trademarks in this publicationmay be trademarks whose use by third parties for their own purposes could violate the rights of the owner.Disclaimer of LiabilityWe 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 inthis publication is reviewed regularly and any necessary corrections are included in subsequent editions.Siemens AGDivision Process Industries and DrivesPostfach 48 4890026 NÜRNBERGGERMANYA5E37098396-AA 04/2016 Subject to changeCopyright Siemens AG 2016.All rights reserved
Table of contents1Introduction.72Terms.93Software requirements.114Synchronizing project data with Teamcenter.134.14.1.14.1.24.1.34.1.4Transferring data from Teamcenter to COMOS.13Basic principles.13Mapping a unit from Teamcenter.13Checking and making settings.14Synchronizing a unit from Teamcenter.144.24.2.14.2.24.2.3Transferring data from COMOS to Teamcenter.15Basic principles.15Checking and making settings.15Synchronizing a unit to Teamcenter.164.34.3.14.3.24.3.3Synchronizing attribute values.16Static and dynamic data.17Forms for static data.18Forms for dynamic data.184.44.4.14.4.2Changes in COMOS.19Creating a mapping object.19Specifying the instance 5.84.5.94.5.104.5.11Configuring the interface to Teamcenter.21Overview.21Workflow.23Naming conventions.25Configuring Teamcenter.25Setting Teamcenter options.26Making changes in the "Default.xml" file.27Configuring a project in Teamcenter.27Specifying resources and types for the assignment.28Creating an "Application Interface".29Creating a "Collaboration Context" for an existing unit.30Creating a "Collaboration Context" for synchronizing a plant from 8Configuring COMOS.31Saving access data for Teamcenter in the project properties.31Installing the buffer component for the COMOS client.32Synchronizing resources.33Calling the properties of synchronized resources.34Assigning units of measurement.34Assigning resources and types.35Assigning attributes.36Synchronizing resource information.37Process Data Interface to Teamcenter/NXOperating Manual, 05/2016 V 10.2, A5E37098396-AA3
Table of contents567842D-based 3D design.395.1Requirements for the connection between COMOS and NX.395.2Exporting pipe specs to Teamcenter.395.3Transferring P&IDs to Teamcenter/NX.405.4Connecting COMOS and NX.415.5Disconnecting the connection between COMOS and NX.415.6Assigning objects.425.7Canceling the assignment.425.8Navigating to the 3D object in NX.435.9Navigating to the COMOS object on the P&ID.43Integrated document management.456.1Assigning a COMOS document to a Teamcenter document.456.2Creating COMOS documents with user-defined settings in Teamcenter.466.3Creating COMOS documents with standard settings in Teamcenter.476.4Assigning a workflow template to a TC document subsequently.486.5Creating revision and transferring documents to Teamcenter.496.6Transferring documents of a revision subsequently.506.7Synchronizing metadata.51Integrated change management.537.1Change management for units.537.2Change management for documents.547.3Submitting Teamcenter tasks to COMOS.567.4Querying change objects from nchronizing project data with Teamcenter.59Adding an attribute.59Editing an attribute.59Deleting an attribute.608.28.2.18.2.28.2.38.2.42D-based 3D design.60Preparing transfer of P&IDs.60XML file "pipepartfamilies".61Editing the XML file "pipepartfamilies".61Configuration of the "Pipe part attribute mapping" window.628.38.3.18.3.28.3.38.3.48.3.5Preparing integrated document management.62Preparing transfer of documents.62Checking the settings of the revision printer.63Importing document types.63Importing workflow templates.64Manually creating workflow templates.65Process Data Interface to Teamcenter/NXOperating Manual, 05/2016 V 10.2, A5E37098396-AA
Table of contents98.3.68.3.78.3.88.3.98.3.10Importing dataset types.65Importing relation types for datasets.66Importing item types.66Configure the "Teamcenter Interface" object.67Setting the direction of the synchronization of .4.8Preparing integrated change management.70Importing workflow templates.70Manually creating workflow templates.70Importing types of change objects.71Configuring change objects.71Configuring "Change management backlog" in the project properties.72Importing relation types for change objects.73Preparing units for change management.73Prepare transfer of Teamcenter tasks to COMOS.74User interface reference.799.1Status area in windows.799.2"Teamcenter login" window.799.3"Synchronize plant from Tc" window.809.4"Synchronize plant to Tc" window.819.5"Element properties" window.819.6"Select Tc resource" window.829.7"Element properties" window in the base objects .839.8"Synchronize resource info" window.839.9"Teamcenter units of measurement" tab.849.10"CTI resource mapping" tab.849.11"CTI attribute mapping" tab.849.12"CTI instance mapping" tab.859.139.13.19.13.29.13.3"XMLViewer" window.86Views.86Calling a view.87Version comparison.87Process Data Interface to Teamcenter/NXOperating Manual, 05/2016 V 10.2, A5E37098396-AA5
Table of contents6Process Data Interface to Teamcenter/NXOperating Manual, 05/2016 V 10.2, A5E37098396-AA
Introduction1Data exchange with TeamcenterCOMOS has an interface to the Siemens PLM software Teamcenter. The interface supportsdata communication in both directions. You can start the exchange from COMOS.The interface with Teamcenter provides you with the following options: You can create plants in Teamcenter and synchronize them with COMOS.See also chapter Synchronizing a unit from Teamcenter (Page 14). You can synchronize your existing COMOS unit with Teamcenter.See also chapter Synchronizing a unit to Teamcenter (Page 16). You can edit a synchronized plant either in COMOS or in Teamcenter and thensynchronized it again. You can submit COMOS documents, revisions and associated documents to Teamcenter.See also chapter Integrated document management (Page 45). Create change requests, problem reports or other objects for change management inCOMOS and export them to Teamcenter. See also chapter Integrated change management (Page 53).Data exchange with NXThe interface allows you to transfer pipe parts from COMOS to NX via Teamcenter.Transferring takes place by means of XML files in which the information about pipe specs andpipe parts is collected.P&IDs are transferred as PDFs. Information about PipeRun and XMplant is also transferredas an XML file.See also chapter 2D-based 3D design (Page 39).Process Data Interface to Teamcenter/NXOperating Manual, 05/2016 V 10.2, A5E37098396-AA7
Introduction8Process Data Interface to Teamcenter/NXOperating Manual, 05/2016 V 10.2, A5E37098396-AA
2TermsMapping objectA mapping object is an engineering object created on the basis of a base object. A Teamcenterresource or a Teamcenter type must be assigned to the base object for this. Mapping objectscan be synchronized between Teamcenter and COMOS.PDIProcess Data InterfacePLMPLM (Product Lifecycle Management) is uniform management of product data throughout theentire product lifecycle.SynchronizationSynchronization is the equivalent of repeated importing or exporting of data. Synchronizationincludes all cases in which only a portion of the data is to be updated.TeamcenterSiemens PLM software TeamcenterAssignmentThe resources and types familiar in Teamcenter are initially independent of COMOS baseobjects. To link the relevant objects, they must be assigned to one another.The resource assignment also determines which base object is used to create an object fromTeamcenter in COMOS.In the opposite direction, instance mapping defines the translation of COMOS engineeringobjects into resources or types that can be understood by Teamcenter.Attributes and units of measurement are translated in both directions using correspondingassignments.Process Data Interface to Teamcenter/NXOperating Manual, 05/2016 V 10.2, A5E37098396-AA9
Terms10Process Data Interface to Teamcenter/NXOperating Manual, 05/2016 V 10.2, A5E37098396-AA
Software requirements3PDITo use the functions of PDI, you need to use Teamcenter version 10.1.1 and NX version 9.0.TeamcenterThe COMOS interface has been designed to interface with Teamcenter Version 10.1.1.Java Runtime Environment for TCCSWhen you use TCCS on the COMOS client, a Java Runtime Environment of version 1.6 22or higher must be installed.Process Data Interface to Teamcenter/NXOperating Manual, 05/2016 V 10.2, A5E37098396-AA11
Software requirements12Process Data Interface to Teamcenter/NXOperating Manual, 05/2016 V 10.2, A5E37098396-AA
Synchronizing project data with Teamcenter4.1Transferring data from Teamcenter to COMOS4.1.1Basic principles4Preparation of data communication by the user If you want to start the transfer for the first time, you must prepare the data communicationin COMOS. See chapter Configuring COMOS (Page 31). If you have already performed a synchronization from Teamcenter or to Teamcenter, usethe prepared settings. In the event of problems during data communication, check that the default settings havebeen made and contact your administrator if necessary.4.1.2Mapping a unit from TeamcenterObjectivePlant data is to be transferred from the Siemens PLM solution Teamcenter to COMOS for thefirst time.Procedure1. Create a new plant below the project node in the "Units" tab in the Navigator.2. To determine the plant type used in Teamcenter, open the "@20 B60 M06 Y30 A20Teamcenter types" node in the "Base objects" tab in the Navigator.The types used in Teamcenter are listed.3. Open the properties of the object matching the type of your plant in Teamcenter.4. To navigate to the corresponding base object, click the "Navigate, properties" button in the"Attributes CTI resource mapping" tab and select "Navigate Object".This object is to be created on the engineering side.5. Use drag&drop to move this object from the "Base objects" tab onto the plant in the "Units"tab.Process Data Interface to Teamcenter/NXOperating Manual, 05/2016 V 10.2, A5E37098396-AA13
Synchronizing project data with Teamcenter4.1 Transferring data from Teamcenter to COMOS4.1.3Checking and making settingsRequirementThe created plant is classified. A Teamcenter integrator object is added.Procedure1. To check the classification, select the created plant in the "Units" tab in the Navigator andnavigate to the base object.2. Open the base object properties.3. Open the "Classification" tab.4. Check whether the "A490 Teamcenter object" entry is set in the "Functional classification"list.If it is not, inform your administrator.5. Check whether the "Teamcenter integrator" object is present in the "Units" tab of theNavigator in the mapping of the unit:– If this object is listed, the interface is ready for connection to Teamcenter.– If it is not listed, add a Teamcenter integrator object:Open the "@20 B60 M06 A10 A10 Teamcenter integrator" node in the "Baseobjects" tab in the Navigator.Use drag&drop to move the Teamcenter integrator object onto the plant in the Units tab.4.1.4Synchronizing a unit from TeamcenterRequirements Your administrator has made the necessary default settings. See also chapter Specifyingresources and types for the assignment (Page 28). The plant from Teamcenter has been mapped in COMOS. See also chapter Mapping aunit from Teamcenter (Page 13). You have checked or entered the settings. See also chapter Checking and makingsettings (Page 14).14Process Data Interface to Teamcenter/NXOperating Manual, 05/2016 V 10.2, A5E37098396-AA
Synchronizing project data with Teamcenter4.2 Transferring data from COMOS to TeamcenterProcedure1. In the "Units" tab in the Navigator, select the mapping of the plant from Teamcenter.2. Select the "Teamcenter Synchronize plant from Tc." command from the context menu.– If there is not an existing connection to Teamcenter, the "Teamcenter login" windowopens. Enter your access details and click "OK" to confirm. See also chapter"Teamcenter login" window (Page 79).– As soon as the connection to Teamcenter is established, the "Synchronize plant fromTeamcenter" window opens.3. Make the required settings in the "Synchronize plant from Teamcenter" window. See alsochapter "Synchronize plant from Tc" window (Page 80).4. To perform synchronization, click "OK".ResultThe plant in COMOS is updated with the data from Teamcenter.4.2Transferring data from COMOS to Teamcenter4.2.1Basic principlesPreparation of data transfer by the userIf you want to start the transfer for the first time, prepare the data communication in COMOS.If you have already performed a synchronization from Teamcenter or to Teamcenter, use theprepared settings.4.2.2Checking and making settingsObjectiveData of a plant in COMOS is to be synchronized to Teamcenter. Synchronization toTeamcenter requires certain settings.Procedure1. Select the plant node you want to synchronize to Teamcenter (along with its content) in the"Units" tab in the Navigator.2. Check whether the "Y00T00128 @Y CTI instance mapping" tab is located below theselected plant.If the tab is not there, contact your administrator.Process Data Interface to Teamcenter/NXOperating Manual, 05/2016 V 10.2, A5E37098396-AA15
Synchronizing project data with Teamcenter4.3 Synchronizing attribute values3. Navigate to the base object.4. Open the base object properties.5. To check the classification, open the "Classification" tab.6. Ensure that the "A490 Teamcenter object" entry has been set in the "Functionalclassification" list.If it has not, inform your administrator.7. To add the Teamcenter integrator object, open the "@20 B60 M06 A10 A10Teamcenter integrator" node in the "Base objects" tab in the Navigator.8. Use drag&drop to move the Teamcenter integrator object onto the plant in the "Units" tab.ResultThe plant in COMOS is prepared for synchronization to Teamcenter.4.2.3Synchronizing a unit to TeamcenterProcedure1. Select the desired plant in the "Units" tab in the Navigator.2. Select the "Teamcenter Synchronize plant to Tc" command from the context menu.– If there is not an existing connection to Teamcenter, the "Teamcenter login" windowopens. Enter your access details and click "OK" to confirm. See also chapter"Teamcenter login" window (Page 79).– As soon as the connection to Teamcenter is established, the "Synchronize plant to Tc"window opens.3. Make the required settings in the "Synchronize plant to Teamcenter" window. See alsochapter "Synchronize plant to Tc" window (Page 81).4. To perform synchronization, click "OK".ResultThe plant in Teamcenter is updated with the data from COMOS.4.3Synchronizing attribute valuesOverviewYou can synchronize attribute values of Teamcenter forms to the engineering and base datawith COMOS attributes. Conversely, you can synchronize attribute values from COMOSengineering to Teamcenter forms.16Process Data Interface to Teamcenter/NXOperating Manual, 05/2016 V 10.2, A5E37098396-AA
Synchronizing project data with Teamcenter4.3 Synchronizing attribute valuesSequence1. You define the Teamcenter forms together with the other resources in Teamcenter andsynchronize these to the base data in COMOS.2. You assign the attributes in COMOS. See also chapter Assigning attributes (Page 36). Todo this, use the "@20 B60 M06 Y30 A40 Y00T00127 CTI attribute mapping" tab.NoteUnits of measurement not supportedThe Teamcenter form attributes do not support units of measurement.4.3.1Static and dynamic dataData typesWe distinguish between two types of data: Static data Dynamic dataStatic dataYou define this data in Teamcenter and synchronize it to COMOS. Do not change the data inCOMOS. See also chapter Forms for static data (Page 18).Examples of static dataTechnical data of manufacturer device definitions: Maximum power Model number Connectors Dimensions WeightDynamic dataDynamic data is predefined in Teamcenter and is part of and a result of the engineeringprocess. This data is synchronized to both COMOS and Teamcenter. See also chapter Formsfor dynamic data (Page 18).Process Data Interface to Teamcenter/NXOperating Manual, 05/2016 V 10.2, A5E37098396-AA17
Synchronizing project data with Teamcenter4.3 Synchronizing attribute valuesExamples of dynamic dataProcess data which is necessary for a particular use of a manufacturer device: Process temperature Pressure Volume flow Medium4.3.2Forms for static dataResourcesForms for static data are attached to the respective resource in Teamcenter. The same objectis also used for later synchronization of engineering data. In COMOS, objects are createdduring synchronization of resources under the following node and attached as elements underthe COMOS base object which corresponds to the Teamcenter resource:"@20 B60 M06 Y30 A40 A10 Static Teamcenter forms"Attribute assignment to the base object assigned to the resource in COMOS takes place fromthe element. See also chapter Assigning attributes (Page 36).4.3.3Forms for dynamic data"Structure Context" type objectYou copy forms for dynamic data in Teamcenter under the object of the type "StructureContext". See also chapter Assigning resources and types (Page 35). When a plant issynchronized, the forms defined in this way are used as templates to create additional formswith the same name and type in Teamc
A mapping object is an engineering object created on the basis of a base object. A Teamcenter resource or a Teamcenter type must be assigned to the base object for this. Mapping objects can be synchronized between Teamcenter and COMOS. PDI Process Data Interface PLM PLM (Product Lifecy
