creo 108 globalptcadministration2

Global PTC Administration for Extremely Large Creo Elements/Pro (Pro/ENGINEER) Implementations

Paul Crane, PMP, Deere & Company, IT Team LeaderMichael Holzwarth, Dipl. Ing. (FH), Deere & Company, CAD Leader

06/14/2011

2 2010 PTC

Agenda


> Changing the Process John Deere design environment & history Project objectives & business case

> Standard Architecture Installation process Configuration distribution Launching the application

> Live Demonstration

> End Results & Next Steps

3 2010 PTC

Agenda


> Changing the Process John Deere design environment & history Project objectives

> Standard Architecture Installation process Configuration distribution Launching the application



4 2010 PTC

Changing the Process

John Deere Design Environment


5 2010 PTC

> Many unique Pro/ENGINEER configurations Increased man-hours needed for upgrades Inconsistent testing results Redundancy

> Laptops extremely prevalent (50%+ and increasing)

> Change process Changes not managed globally Reliant upon local administrators


Issues to Address


6 2010 PTC

> Installation Server based installation Local installation

Full install Only copy the files

> Start up with Batch files

with or without selections with own Written GUIs

Deere Pro/INTRALINK Launcher Pro/E Launcher

> Configurations where different Cache location Startup directory


Multiple Methods in Use


7 2010 PTC

> Change control Change control board Testing environment Managed releases

> Common deployment method

> Master John Deere configuration

> Location or Schema specific configuration

> Support all hardware and operating systems


Project Deliverables


8 2010 PTC

> Auto-detect user global location

> Select configuration (SCHEMA) to use

> Select Creo Elements/Pro Version

> Connect network share on startup or reuse existing

> Auto-update changes

> Remember last settings

> Running on Windows XP & Windows 7 (32bit & 64bit)

> Pre-staging software

> Enable pre-production test


Functional Requirements


9 2010 PTC

Agenda



> Standard Architecture Installation process Distribute Multiple Configurations Launching the application



10 2010 PTC

> Create an Custom Installer with the necessary options Have a smaller package for distribution onto the location servers Use only the necessary languages and installation options

> Create a installation trail file Call the PTC Setup with the option uilog and install the software

Set the install path and the options for the installation Dont create a startup command! (this is delivered at startup)

> Create a VBS install script Disk space check requires 5GB on target machine Check for prior installation of same build code Run the installation with local admin rights Run the installation trail file with the -nographics option Copy the startup GUI Write Deere Registry Keys

Standard Architecture Installation Process


Create the installation package for specific maintenance build

11 2010 PTC

> Create a list of the workstations which need Creo Elements /Pro Look on the license Server and get all workstations which requested a license in the last two

months Cross check this list with the SCCM inventory list

To filter out workstations which are no longer in use

> Use Microsoft System Center Configuration Manager (SCCM) for the distribution

Formerly known as Systems Management Server (SMS)

> Start the deployment and review the results Check for successful installations Check why installations failed.

User shutdown workstation during the installation Not enough disk space

Work with local support to resolve the failures

Standard Architecture Installation Process


Deploy the software

12 2010 PTC

Standard Architecture Distribute Configurations


13 2010 PTC

> Required functions Select Sitting location Select configuration (SCHEMA) to use Select Creo Elements/Pro Version Select additional License Options Running on WinXP/Win7 both 32bit/64bit Connect network share on startup or reuse existing Check for Updates on startup Remember last settings Self-updating

> Nice to have functions Preselect Sitting location Show only installed Creo Elements/Pro Versions Detect slow network connection Enable the easy switch to a develop or test system

Standard Architecture Launching the Application

Brainstorming the new PTC Launcher


14 2010 PTC

> Sitting location Geographic location

> Schema Options, toolkits, symbols, notes, config.win

> Pro/ENGINEER Version Creo Elements/Pro maintenance build

> Options: 32bit is visible only if a 32bit is installed on a 64bit OS License Options

Only Chinese Option is shown on the GUI More License Options are available in the File Menu

> Documentation under Help


GUI


15 2010 PTC

> Auto-detection makes tool easy to use

> Sitting location determines Printer configuration CONFIG.PRO settings for PDMLink connection Optional: different server share to connect

> Tools to auto-detect location The infrastructure behind is build with MS Active Directory

and Distributed File System The AD and DFS is setup that the clients get the sitting

location Using the DFSutil command


Sitting Location is Automatically Detected


16 2010 PTC

> Still have the old name in the GUI

> Enables user to select a different Version GUI pre-selects the default build

> Show only installed builds

> Allow only defined builds to show up


Creo Elements/Pro Maintenance Build


Configuration allows: Wildfire 4.0 M160 Wildfire 4.0 M170 Wildfire 5.0 M020

17 2010 PTC

Agenda






18 2010 PTC

LIVE DEMO


19 2010 PTC

Agenda






20 2010 PTC

> User Benefits Faster startup times Location automatically detected Single consistent environment VPN fully supported

> Engineering Department Benefits Consistent design schemas Requests via online software management tool (SCCM)

> IT Benefits Reduce complexity Standard process & rigorous change control Eliminate duplication of effort Allow pre-staging of software upgrades

End Results & Next Steps

Business Benefits


21 2010 PTC

> Solving problems before user notices Exit Logger, Client Inspector, PTC Launcher log Config.pro inspections

> Change control process

> Schema consolidation

> Future deployments Maintenance build pre-staging Global configuration modifications Removal of older versions

> Future software

End Results & Next Steps


creo 108 globalptcadministration2

Documents

ptc auto

useglobal ptc administration

ptc setup

creo elementspro version

deere company

installation options

change process changes

configuration schema