Increasing functionality and stability with PDI Moving from tailor-made integration to OOTB

Transcription

1 Increasing functionality and stability with PDI Moving from tailor-made integration to OOTB Restricted siemens.tld/keyword

2 Background Siemens Power&Gas/Distributed Generation Division (PG DG) One comos database Small and medium sized gas turbines Finspong (SWE), Lincoln (GB), Hengelo (NL), Mt.Vernon (US) Upgraded PLM solution project From old system since 1999 (TC based, customized) To brand new Teamcenter 11 landscape Lead architect Magnus Blondell New integration Engine from COMOS Comos 10.2 SP1 PDI 2.0 Functionality Page 2

3 Old PLM system XML-based integration Tailor-made webservice Tailor-made API s for Teamcenter Mostly one way communication TeamCenter Comos Page 3

4 Requirements for upgrading Teamcenter and the landscape Requirements for the new landscape New Teamcenter 11 backbone archiving system (documents and parts) COMOS authoring system, among others (NX, PDMS, ) All systems can check out and edit the same objects before sent for approval process Two way flow of data between systems Information should be possible to revise regardless of where it is created Synchronous communication between systems Possibilty to get rid of duplication of business rules Review and approval process in Teamcenter Opens for package release Page 4

5 New PLM system PDI 2.0 (10.2 SP1) Comos Out of the box interface Stable Two-way communication Integration to multiple teamcenter environments Other autoring tools (NX/PDMS/ ) Comos TeamCenter (other instances) TeamCenter Page 5 TC TC

6 Synchronization of items Comos Teamcenter Object Object Part Part Page 6

7 Structures from a purchase / production perspective Comos Teamcenter Object Object Part Part Page 7

8 Structures from a plant perspective Comos Teamcenter Object Object Part Part VendorPart VendorPart VendorPart Page 8 VendorPart VendorPart VendorPart VendorPartVendorPart

9 PDI Basics Typed manually TC SOA URL (Database controlled) Fetched from comos user data Page 9

10 PDI Basics (Document) PDI Module offers basic necessary functionality Allows function calls from own attributes/scripts This is the implemented solution Out of the box interface (interface object) Customized interface (As implemented) (Document tab) Page 10

11 Attribute synchronization PDI Module offers basic necessary functionality Implementation in PG DG through specifications on document (next slide) Page 11

12 Implementation in PG DG through specifications on document Attributes mirrored from TC interface objects (details next slide) TC Interface objects managed via script TC Interface not visible for common users Checks, conversions, other logic Error codes as reported by TC through PDI Displayed in event log Page 12

13 Attribute mirroring Document/Device tab User visible interface Teamcenter interface, Teamcenter revision (Hidden from users) Description (text) P&ID lube oil system Description (text) P&ID lube oil system Author (text) Dennis Nord Length (value, unit) 32 m ECC confirm (checkbox) Synch script Author (text) Dennis Nord Length (text) 32 Length unit (text) metre ECC Class (multi-select combobox) [x] N N [x] 0004C [x] 0005D 0001A 0001B. Mapping table ECC confirmation (text) True ECC Class (text) N N\n0004C\n0005D Page 13

14 Transfer document data to/from teamcenter Page 14

15 Transfer document data to/from teamcenter Approval workflow in TC Page 15

16 Part/structure handling Part handling Very similar setup to document integration OOTB integration on tabs instead of separate integrator object Same philosophy with customer user interface and OOTB hidden for common users Same synchronization script as documents Page 16

17 Part/structure handling User interface Page 17

18 Part/structure handling Transfer part data to/from teamcenter Page 18

19 Part/structure handling Result in Teamcenter Page 19

20 PDI also enable controlling classification of parts in teamcenter Class structure synchronized from teamcenter Page 20

21 Teamcenter view Page 21

22 Part structures Part structures Structures and relations (Part-part, part-doc, doc-doc) Designed in COMOS and transferred to TC Reverse synch is also possible Page 22

23 Remaining work Remaining work to do Feedback from PLM2020 after reject/approve with stamped/redlined pdf Two way flow of document files (office) Synchronize standardtables (list of values from teamcenter) Initiate TC workflow with checkers and approver from Comos Implement attributes for parts Synchronize designation structure (KKS, ISA) Page 23

24 Remaining work Wishlist for SP2 Fetch files from TC to Comos (documents editable outside Comos) Original file and additional files Fetch template from TC (word, excel etc.) when creating document in Comos Possibility to delete datasets (when resending a revision). Workflow handling from Comos Select workflow Validate workflow Assign all tasks (set checkers and approver) Synchronize valuelists eg. checkers, approvers, naming catalog, materials etc. PKI logon to teamcenter (requirement from Siemens security officer) TC plugin for Comos (as demonstrated, nice-to-have) Page 24

25 Remaining work Wishlist for SP2 (continued) Report function to check differences in structures for engineering objects In the logon window, dropdown lists for: Server URL (Lockable) User Group & Role (connected user) Logon response with assigned group and role Information to user, Group and Role selections should be synchronized from TC Page 25

26 Contact page Dennis Nord Siemens Industrial Turbomachinery AB Magnus Blondell Tigerliljan AB Solution Architecht GS IT DE PLM PLA SOL External service provider PG DG PM POI MGT OI Phone: Mobile: Phone: Fax: Mobile: siemens.com Page 26