Best Practices for Teamcenter Site Consolidation

Transcription

1 Best Practices for Teamcenter Site Consolidation Rajkumar Sundaram Mercury PLM 1

2 About Mercury Marine World s Leading Marine Propulsion Manufacturer Mercury Marine is a division of Brunswick Corporation (BC:NYSE) BC is Forbes Best Managed Consumer Durable Goods Mfg (Feb/06) 2

3 About Mercury PLM More than 80 companies have benchmarked our PLM implementation Process-focused PLM solutions include: Best practices PLM visioning Business process development PLM architecture and configuration Implementation support and training Clients include aerospace, automotive, consumer goods, and heavy equipment manufacturing Embrace a human-centered approach based on a real manufacturer s perspective to enable your PLM system. 3

4 Basis for this Presentation Formerly five Teamcenter sites, now four, after consolidation Consolidation was done between Tulsa, OK and Fond du Lac, WI over 3-4 months during last part of 2010 Consolidation between Teamcenter sites at version We are looking at consolidating two more sites in

5 To Consolidate or Not to Consolidate! 5

6 Why Consolidate? - Why Was It Multi-Site? Performance? Performance Improvements might mitigate this reason Truly Independent? Acquisition and Other Reasons? More flexibility in configuration now than before. Requires more detailed evaluation on the pros and cons of consolidation After settling down, is it performance, independence or both? 6

7 Why Consolidate? Improved Performance Support Tier Supported Latency (ms) TC Engineering Unified 2007 Unified 8.3 Performance Metadata (Latency) + File Data (Store and Forward) 7

8 Why Consolidate? Reduced Teamcenter Support Multi-Site Support Activities 5% Day to Day Issues 15% 20% 35% Patches/Upgrades BMIDE Changes 25% Track Share/Sync Training Users on MSC 8

9 Why Consolidate? Reduced Infrastructure Needs/IT Support Servers Licenses Maintenance (Hardware, OS,DB) Backup Infrastructure Skilled Local IT Personnel 0 Multi-Site 4-Tier 9

10 Why Consolidate? Simpler Collaboration Instant availability of Data. No wait for Sync Certainty of latest data Global Workflows before Teamcenter 11(?) Truly Integrated Organization Simpler interfaces to other systems Truly Centralized Item ID generation 10

11 Consolidate? Feasibility Study Identify Key Users, Decision Makers Develop Performance Measurement Plan Establish Acceptable Targets Teamcenter setup should be as close as possible to the end in mind Measure Performance Make Go or No-Go Decision 11

12 Let s Consolidate! 12

13 Plan Teamcenter Team Key Users, Process Owners Consolidation Plan IT Management 13

14 Data Consolidation Data, Cleaner the Better Resolve Ownership Issues before Consolidation MSA (Multi-Site Assist) is a great tool to identify and fix MSC issues Suzhou Motorguide Mercury Mercruiser Juarez We used multiple iterations of MSA (Extract, Analyze, Fix) Concentrate on just source site issues to keep focus Replica Items Distribution Time taken depends on how unclean the data is 14

15 Data Consolidation Data Model Different Templates Model Not a good idea unless necessary Don t trust documented differences Run bmide_comparator for actual differences Superset Templates Model Easier to integrate Verify Siemens and 3 rd party template dependencies database_verify offers additional insights into site differences Type conversions require mapping and is complex Source Template Target Template Source Template Target Template Target Template Source Definitions 15

16 Process Consolidation Owned by Process Owners, supported by Teamcenter team Keep AS-IS on consolidation Phased integration Workflows Processes that were tweaked to work around the system could be changed now Handlers with Source Site specific information had to be changed Template Filters Change Management Ties mostly to workflows Real change types in 8.3 would allow more granular control Organization Functional or Location based organization decision probably made already Access control decisions dsa_util could be useful to replicate organization Classification Ownership of Hierarchy Access to View, Classify etc., 16

17 Consolidation Strategy and Execution Server Relocation Relocated Source server to Target Location* Converted all Source clients to Source Server 4-Tier* Target Readiness Configured Target BMIDE template with necessary changes and deployed Configured Workflows, Accesses, Organization (non-bmide stuff) Groundwork Transferred Ownership of all Items not modified in last 6 months Identified and Cancelled Active Processes not needed anymore 17

18 Consolidation Strategy and Execution (Contd) More Work Iterated transfers (6months 3months 1month) Started Communication to Users on Check-outs and Active Processes Go-Live I Transferred all Items over weekend except those In-Process Source clients were configured for both Source and Target Sites Source Site configured to allow only completion of active processes Go-Live II All active processes completed or cancelled. All Items transferred to target site Source clients have access to only target site 18

19 Wait! There s Cleanup 19

20 System Cleanup Delete Site Definition Delete Site References Delete Stubs Delete Export Records Resolve Source Site Owned Objects Same Cleanup at all sites, not just Target site 20

21 System Cleanup Resolve Source Site Owned Objects Create a query to find any objects owned by Source Site. Mostly Orphans Search Class: Form, Dataset, ItemRevision, Item, WorkspsaceObject, POM_Application_Object, POM_Object Delete them. Any object referenced would throw an error. Resolve and delete More cleaner the data, lesser time on this activity. 21

22 System Cleanup Delete Export Records Target & Other Sites ITEM 001 Source Site ITEM 001 Exported to Source Site Use data_sync assert_extinct_site(aes) - verify to delete the export records Might stop before completion. Just restarting the script works. Iterate until data_sync finds no records to delete Could be time consuming. Took 1 day for =~ Items, 1 Site Better to run over weekend to not disrupt Production performance 22

23 System Cleanup Delete POM Stubs The Stubs are supposed to be gone on either import of the Object or deletion of the object. They don t go ( ). data_sync aes is supposed to delete the stubs along with the export records. It doesn t ( ) We used a script provided by GTAC to delete the Stubs. Should be tweaked to suit your needs. Recommended to run off-hours Target & Other Sites ITEM 001 Source Site Stub ITEM

24 System Cleanup Delete Site References, Site Create a query to find the Source Site Check for any references. Resolve and delete references. Use site_util f=delete to delete the site instead of UI(Organization Application) 24

25 It s Really Over Now! 25

26 Thank You! Siemens PLM Connection 2011 Las Vegas, NV May